Hey guys, I tried to unlock my SPH-L720 (Sprint's GS5) so I downgrade baseband to MDC, all good so far, then I tried to upgrade the baseband again after the unlocking process but got an error, and that's it wifi and sound are not working, phone is slow, it has a security notice that something was block, and I can't flash it to stock ROM or anything using Odin, only got errors. Please some advice here and help, thank you
carigm said:
Hey guys, I tried to unlock my SPH-L720 (Sprint's GS5) so I downgrade baseband to MDC, all good so far, then I tried to upgrade the baseband again after the unlocking process but got an error, and that's it wifi and sound are not working, phone is slow, it has a security notice that something was block, and I can't flash it to stock ROM or anything using Odin, only got errors. Please some advice here and help, thank you
Click to expand...
Click to collapse
That's the S4, by the way. But without knowing what the errors are, it's gonna be kind of hard to point you in the right direction. What build version of the Samsung software are you on? What PC OS? What version of Odin?
es0tericcha0s said:
That's the S4, by the way. But without knowing what the errors are, it's gonna be kind of hard to point you in the right direction. What build version of the Samsung software are you on? What PC OS? What version of Odin?
Click to expand...
Click to collapse
My appologies is S4 you're right .
When I'm trying to flash, with either Odin3 v3.09/Odin3 v1.87, the error I get from the phone is "SW. REV. CHECK FAIL: fused : 5, Binary : 1"
I'm using Win Vista Home Premium, and I have Andoid 4.4.2 with software version L720PUEMJA.
Weird fact, I could upgrade to MJA with no problem, using Odin, but can't flash the original stock ROM or fix the wifi and sound errors, also some apps are really dumb like when I try to dial a number, obviously I don't have data conection either
Hope this can help you
carigm said:
My appologies is S4 you're right .
When I'm trying to flash, with either Odin3 v3.09/Odin3 v1.87, the error I get from the phone is "SW. REV. CHECK FAIL: fused : 5, Binary : 1"
I'm using Win Vista Home Premium, and I have Andoid 4.4.2 with software version L720PUEMJA.
Weird fact, I could upgrade to MJA with no problem, using Odin, but can't flash the original stock ROM or fix the wifi and sound errors, also some apps are really dumb like when I try to dial a number, obviously I don't have data conection either
Hope this can help you
Click to expand...
Click to collapse
Seems like you are trying to downgrade or flashing the wrong version and the phone doesn't like that. MJA is the first 4.3 update (think there were a couple) so if you've already been on 4.4.2 official, then you're stuck. You can't go back to 4.3 that I know of. At least not via normal Odin method.
es0tericcha0s said:
Seems like you are trying to downgrade or flashing the wrong version and the phone doesn't like that. MJA is the first 4.3 update (think there were a couple) so if you've already been on 4.4.2 official, then you're stuck. You can't go back to 4.3 that I know of. At least not via normal Odin method.
Click to expand...
Click to collapse
Yeah, I've been trying to downgrade to original stock ROM 4.2.2 when I'm already on 4.4.2.
Is there a way to install another android version or custom ROM via Odin or adb instead? Right now I don't care about the data connection, but with no wifi sound and slow that phone itself is pretty much unless for me
Well consider yourself lucky. Trying to downgrade a Samsung device that has the 4.3+ bootloader has been known to brick devices in certain situations. Just download the 4.4.2 tar and flash with Odin. Should be fine. If it bootloops, just factory reset.
es0tericcha0s said:
Well consider yourself lucky. Trying to downgrade a Samsung device that has the 4.3+ bootloader has been known to brick devices in certain situations. Just download the 4.4.2 tar and flash with Odin. Should be fine. If it bootloops, just factory reset.
Click to expand...
Click to collapse
It worked! I updated the modem to NAE and it worked! It's all good, now it's rooted and working! Thanks man!!!
No problem. Glad all is well!
Related
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good:
My uncle has a SGH-I777 running 2.3.6 and is on straight talk. Was going to update to stock 4.1.2 for him but apparently Samsung (im a moto fan) is a pain to upgrade. OTA says hes up to date even though samsungs official site for this phone says newest ota is jellybean. I installed samsungs crappy kies on my laptop and typed in model and S/N and it downloaded but never would let me install. Im short on time. Does ANYONE have an ota zip that i could load on sd and flash? Please and thanks because I need to get this done ASAP!
Before Someone flips out saying "There's no stock jellbean" like i've seen in a couple other posts.
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00047325&fm_seq=51324
^Yea. On my droid x you could easily find ota zips to flash in stock recovery. I would just flash cm11 on this thing but i'm sort of forbid to "hack" his device. lol but yea if someone could help me...i'd love that..
http://androidromupdate.com/2013/06...2-sgh-i777-official-4-1-2-jelly-bean-upgrade/
^I don't wanna deal with Odin just a simple ota.zip to flash....if I need to do incremental updates like on my droid x i'll need those too please. its running gingerbread 2.3.6 Baseband: I777UCKK6
Oggie7797 said:
My uncle has a SGH-I777 running 2.3.6 and is on straight talk. Was going to update to stock 4.1.2 for him but apparently Samsung (im a moto fan) is a pain to upgrade. OTA says hes up to date even though samsungs official site for this phone says newest ota is jellybean. I installed samsungs crappy kies on my laptop and typed in model and S/N and it downloaded but never would let me install. Im short on time. Does ANYONE have an ota zip that i could load on sd and flash? Please and thanks because I need to get this done ASAP!
Before Someone flips out saying "There's no stock jellbean" like i've seen in a couple other posts.
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00047325&fm_seq=51324
^Yea. On my droid x you could easily find ota zips to flash in stock recovery. I would just flash cm11 on this thing but i'm sort of forbid to "hack" his device. lol but yea if someone could help me...i'd love that..
http://androidromupdate.com/2013/06...2-sgh-i777-official-4-1-2-jelly-bean-upgrade/
^I don't wanna deal with Odin just a simple ota.zip to flash....if I need to do incremental updates like on my droid x i'll need those too please. its running gingerbread 2.3.6 Baseband: I777UCKK6
Click to expand...
Click to collapse
u need to use samsung kies on your pc. download it. plug in. then it will tell ya update is available.
phermey said:
u need to use samsung kies on your pc. download it. plug in. then it will tell ya update is available.
Click to expand...
Click to collapse
Yea i got that much but kies would never connect to his phone even after a reinstall of kies and 3 driver reinstalls lol im not new to android just samsung and their BS. I wiped his cache in stock recovery as a temp fix but iwant him past gb lol thats just sad. Thanks anyway. If I had my way I would unlock it and flash cm10.2.1 and send him on his way, but nope...
Oggie7797 said:
Yea i got that much but kies would never connect to his phone even after a reinstall of kies and 3 driver reinstalls lol im not new to android just samsung and their BS. I wiped his cache in stock recovery as a temp fix but iwant him past gb lol thats just sad. Thanks anyway. If I had my way I would unlock it and flash cm10.2.1 and send him on his way, but nope...
Click to expand...
Click to collapse
yeah kies is a finicky beast. i cannot stand having to use it. this site might help ya. it is a bit more straight forward and the files to root and such are actually there. http://galaxys2root.com/att-galaxy-s2-faq/
hope ya manage to get through it. i have been at it all night. i lost root somewhere somehow. my recovery would not mount any drives etc. had to use odin to go back to ics. then root with ics. now i am trying to get the kit kat recovery installed... blah blah blah. good luck.
phermey said:
yeah kies is a finicky beast. i cannot stand having to use it. this site might help ya. it is a bit more straight forward and the files to root and such are actually there. http://galaxys2root.com/att-galaxy-s2-faq/
hope ya manage to get through it. i have been at it all night. i lost root somewhere somehow. my recovery would not mount any drives etc. had to use odin to go back to ics. then root with ics. now i am trying to get the kit kat recovery installed... blah blah blah. good luck.
Click to expand...
Click to collapse
yea thanks ill check that out. I'm used to devices with locked bootloaders and honestly, i prefer that. it's so easy to experient because worst case if you mess up just flash a .sbf file and you're fine. I get a kick out of LG G3 users and their petition for an unlock code lmao. Odin is neat but I'm not going to ever have to mess with it hoopefully
I don't recommend following the galaxys2root lead.
Kies and ODIN are your only options for flashing stock distribution to the i777 on a windows machine.
I see that you're trying to avoid ODIN, but it's the easier way to solve your current dilemma. As stated, Kies can be finnicky.
The stock UCMD8 4.1.2 distribution can be found in the i777 download repository (see sig), and ODIN is how we get folks back on track (for directions, see sig).
Happy Flashing
-Cyril
Oggie7797 said:
yea thanks ill check that out. I'm used to devices with locked bootloaders and honestly, i prefer that. it's so easy to experient because worst case if you mess up just flash a .sbf file and you're fine. I get a kick out of LG G3 users and their petition for an unlock code lmao. Odin is neat but I'm not going to ever have to mess with it hoopefully
Click to expand...
Click to collapse
cyril279 said:
I don't recommend following the galaxys2root lead.
Kies and ODIN are your only options for flashing stock distribution to the i777 on a windows machine.
I see that you're trying to avoid ODIN, but it's the easier way to solve your current dilemma. As stated, Kies can be finnicky.
The stock UCMD8 4.1.2 distribution can be found in the i777 download repository (see sig), and ODIN is how we get folks back on track (for directions, see sig).
Happy Flashing
-Cyril
Click to expand...
Click to collapse
Wow you remind me of someone from the droid x realm. and his phone isn't with me. Btw i dual boot win8.1 and linux but kies is only available on windows so that's the only reason i was running it at the time of trying this. Honestly, i'm not that worried about it since apparently his problem was fixed. He couldn't send or receive MMS so i done standard trouble shooting and I think what finally got it fixed was wiping cache with sim out of it reinstalling sim and then dumping cache again. Thanks again though guys and i'll refer to the links if he has anymore problems.
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Hello guys, any ideas? Thanks!
jakeortega said:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Click to expand...
Click to collapse
Hello guys, any ideas? Thanks!
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
es0tericcha0s said:
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
Click to expand...
Click to collapse
Thank you es0tericcha0s for this information.
What I'm trying to do right now is updating my SHV-e160s from 4.0.4 to 4.1.2 using Kies v2.6. Unfortunately, I'm getting this error "Failed to run firmware upgrade: unknown error.". Until now, I'm afraid to update my firmware manually as I don't have much knowledge to do that.
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Alright, I'll try these steps immediately and will comeback for the result. Thanks again.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Hello, sorry I forgot to ask, will this root my device? I'm afraid I might bricked it.
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
es0tericcha0s said:
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
Click to expand...
Click to collapse
Hello again es0tericcha0s, I haven't tried the instructions that you gave me yesterday as I'm still downloading the firmware, last night I encountered an issue after enabling my Bluetooth, something like "NFC Service has stopped." just keeps on popping up. So I turned off the bluetooth then restarted my phone, it went well for a while.
After that, I enabled my 3G Cellular Data to check what was NFC service error is, after a few minutes, I lost my signal, phone turned to No Service, then in Settings -> About Phone, I got an Unknown Baseband.
EDIT
I got No Service since last night up until now.
EDIT Oct. 13, 2015 9:49 AM +08:00 Manila Time
I manage to update my phone from ICS 4.0.4 to JB 4.1.2. But still, my baseband is Unknown and I have no signal.
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
es0tericcha0s said:
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
Click to expand...
Click to collapse
I also though of that, hopefully not.
When I first got the phone, my gf sent me our pictures via bluetooth , no issues occured. After a while, I noticed that there are so many photos of the previous owner (around 1000+) and mp3s (around 1000+ also). So I connected the phone via usb to my pc and deleted all those pictures and mp3s inside the My Computer -> SHV-E160S -> Phone (Computer\SHV-E160S\Phone). After doing so, I started to encouter some issues, when enabling the bluetooth, the phone hangs and reboots then the error 'NFC service has stopped' keeps on popping up, until it went Unknown Baseband.
Now, the phone keeps on rebooting similar to the symptoms that it gets when baseband version is unknown.
I'm looking for solutions to fix the unknown baseband and saw the Back up and Restore EFS, I just need to root the device to try this fix. Maybe I'll post an update whether if I manage to solve this problem or not, if it didn't fix the issue then maybe the problem is the baseband chip. what a crap!
This is my reference for the EFS Fix
http://techbeasts.com/2014/07/13/fix-samsung-galaxy-unknown-baseband-version-guide/
Thanks!
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
es0tericcha0s said:
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
Click to expand...
Click to collapse
So I need to install TWRP first before rooting the device? Also I'm planning to use a rooted stock firmware which is 4.1.2, I just don't know the difference between UH24 and MH2, I've read that UH24 is already old and it's better to use a MH2 build and what is the Recovery UH24/MH2?
EDIT:
I forgot, I cannot check my current Baseband since it is still unknown.
EDIT: 12:30PM +8:00
I managed to get my Build#, it is MH2, I'm currently looking for a rooted 4.1.2 MH2 download link.
Way faster and easier to use the method I outlined, but either way should work.
es0tericcha0s said:
Way faster and easier to use the method I outlined, but either way should work.
Click to expand...
Click to collapse
Sorry, I'm really a root virgin here. While following your advise, I'm also currently looking at this guide -> http://forum.xda-developers.com/showthread.php?t=1924535. I'm done downloading Tegrak for MH2, a small problem I encountered here is I don't have a folder named 'sdcard' in my phone, so I created one and copied the 'Kernel' .zip, also I copied it to usbStorage folder.
I'm about to flash the 'Recovery' .tar to my phone. Hoping a success result
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
es0tericcha0s said:
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
Click to expand...
Click to collapse
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
jakeortega said:
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
Click to expand...
Click to collapse
Finally! I'm done rooting my phone, though I encountered another issues again. My Menu Button and Back Button does not work.
UPDATE: 4:08PM +8:00GMT
I think I found the problem as to why my Menu button and Back button doesn't work. I'v check my Baseband and it is -> E160SKSJMH1 and my Build # is -> JZO54K.E160SKSJMH2. Am I using a wrong FW as supposed to what I should be using? Which build should I install, the MH1 or the MH2?
Also, the Tegrak Kernel I've used is Build 48 for SHV-E160S MH2. I've also tried factory resetting the phone but the issue still exists.
Thanks!
UPDATE: 4:41PM +8:00GMT
Managed to fixed the issue by updating my Touch Firmware. Cool!
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this