So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
michigan66 said:
Use this guide to flash back to the appropriate version.
http://forum.xda-developers.com/showthread.php?t=2024207
It's a great guide. Saved me last week after I flashed the wrong file in Odin.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Moridin68 said:
yea i did that already to no avail.... used odin to flash the pit and root66... doesnt boot...
Click to expand...
Click to collapse
Have you tried using a different image? What version of stock was on it before you messed with it?
Edit: If the stock version wasn't MJ9 or above then don't flash those. There currently isn't and probably won't be a way to unlock the bootloader on MJ9 and above.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Have you tried using a different image? What version of stock was on it before you messed with it?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
i have recently read on a site that offers a bootloader downgrade service that if it has a knox counter, then it was updated to a version with a 'permalocked' bootloader... and if this is referring to the counter on the ODIN screen that says KNOX WARRANTY VOID:0 then this one is such a device.....
Moridin68 said:
well, thats a good question... it was already in a messed up state when i got ahold of it... i tried flashing root66 and it kept failing, i checked NAND ERASE ALL and flashed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar
as per a suggestion i read on xda.. it too failed as well, but then when i flashed root66 again (also i think with NAND ERASE on) it booted up beautifully...
Click to expand...
Click to collapse
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
When you enter download mode does it say anything about Knox?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
on the download screen there is a line that says KNOX WARRANTY VOID:0
BluGuy said:
When you enter download mode does it say anything about Knox?
Edit: I didn't see your last post. Since it had the updated firmware with Knox, you should be at least able to get the phone working again by flashing that version of the firmware in odin. If it was on Android 4.3 then you should be able to odin MJ9 and it will work again. If it was on 4.4.2 then using odin to flash the ND7 image should fix it.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Moridin68 said:
So I have been working on a friend of mines Verizon Note 2 (SCH-I605) and have run into an issue... I had rooted it successfully to root66 VZW stock sys, then attempted to unlock the bootloader according to the [email protected] galaxynote2root(dot)com/galaxy-note-2-tutorials/how-to-unlock-bootloader-on-verizon-galaxy-note-2-sch-i605.... without reviewing the multiplicity of comments below the article which should have caught my attention and let me know that many people were unsuccessful with that method.
So now i appear to be screwed because it will boot into ODIN but thats it. I cant even get into stock recovery. Upon boot the Galaxy Note 2 splash stays on indefinitely, as it does when i follow the instructions on this site to restore it from a failed unlock, or unroot...... ODIN 3 + sch-I605-16gb.pit + Root66-VZW-stock_sys, when it reboots following flash the splash screen stays on. I have checked the NAND erase All as suggested on this site, and it makes no difference.
When vol up/home/power is pressed it says something to the effect that 'you are a dumb*ss and have screwed up your firmware dipsh*t'....
So what now? Id hate to have to replace my buddies Note 2.... and I had absolutely 0 difficulties unlocking and rooting my HTC One, so this sucks....
Click to expand...
Click to collapse
Did ID:COM turn blue in Odin? . You might have a driver problem.
doctor-cool said:
Did ID:COM turn blue in Odin? . You might have a driver problem.
Click to expand...
Click to collapse
no driver problem... it recognizes the device.... it is blue
Moridin68 said:
he hadnt had service on that phone for several months so i guess ill try the older one first. 4.4.2.
and do i flash the pit file with those as well?
this bs is so much more tedious than working with my HTC One.
Click to expand...
Click to collapse
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
The older one would be 4.3 which is MJ9. And yes use the pit file with it.
And just in case, I know you probably don't need it, the instructions for flashing with odin are in the return to stock section of the first post in this thread: http://forum.xda-developers.com/showthread.php?t=2024207
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Moridin68 said:
right you are about 4.3 being older... i was looking through the stock roms in that very guide and saw 4.1.2 and thought that was the one you had mentioned... im downloading MJ9 now..... thanks... hope this works...
so let me ask you this, if i get it back to stock, and rooted again... even though i cant unlock the bootloader, can i get it network unlocked? this entire dilemma occurred because he wants to be able to throw a straight talk sim in this phone.
i had intended to try this www(dot)scottsroms(dot)com/showthread.php?2786-How-I-turned-my-Verizon-Note-2-into-a-World-capable-GSM-phone
once i fixed the disaster....
Click to expand...
Click to collapse
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Once you get the phone working you can use Saferoot to root it, that is as long as it's working on MJ9. If the phone had been updated to ND7 which is Android 4.4.2 then there currently isn't a way to root it.
Remember even if you get root you won't be able to use a custom recovery to flash stuff.
Also the sch-i605 is already Sim unlocked from Verizon. You just have to be able to edit the apn settings.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Moridin68 said:
ok one last thing before i try this MJ9.... if it had been updated then how was i able to flash it to root66 prior to attempting to unlock the bootloader?
i really appreciate your time bro..thanks btw..
Click to expand...
Click to collapse
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool then.. thanks...
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Moridin68 said:
booting up on MJ9... nicely done.
so ill check out saferoot as you said, and then edit the APN
Click to expand...
Click to collapse
Glad it worked.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
Sorry it took so long to get back to you. I don't know a lot about root66 so I can't help you much there, but I do know that while in download mode if it says something about Knox warranty then the bootloader had been updated to a version with Knox which started with mj9 for the i605.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so now i have stock recovery menu and download menu and it boots and then hangs at the white verizon screen... i have already done a factory reset, and it still hangs.
Related
Let me give some info on my situation:
The phone has unlocked boot loader
I got a replacement phone and wanted to odin back to stock to send back my original phone.
I used Odin to flash back to stock but the phone will not boot and I cannot get into recovery.
I am able to use Odin with success every time. I have followed instruction on how to return to stock and everything goes perfectly until I try to reboot or go into recovery. I just get the Samsung splash screen and it blinks every couple of seconds.
Any ideas?
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
correct, I am able to get into download mode but not into recovery and I have tried everything. I am not a noob but am totally lost here.
I can use Odin without any issue.
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
mzimand said:
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
Click to expand...
Click to collapse
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
kintwofan said:
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
Click to expand...
Click to collapse
I just tried this and got the same results. I got the "PASS" in Odin after flashing the PIT and the stock JB Image. I am still stuck at a slow blinking Samsung screen.
I am open to any ideas
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
droidstyle said:
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
Click to expand...
Click to collapse
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
ahh thanks for clearing that up.
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
mzimand said:
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I had a feeling that is was bricked as I have tried everything I could to fix it. It is not that big of a deal because the screen was shattered on it last week and I paid the insurance for a replacement and was sending it back anyways.
Hey guys, I sent my Note 2 into Samsung in Texas to repair it since the wifi was not connecting. Prior to sending it in, I had it rooted and unlocked based on the instructions on this site, but I put it back to stock (using those same directions) to limit the chance that sammy would screw me on my warranty.
I checked the status of my repairs today and it says they replaced the mainboard, so now I am wondering what I will have to do to get it back to its rooted and unlocked state the way it was before sending in. I am guessing that all I will have to do is boot into recovery and flash a rom, but maybe the stock process did more than that.
If anyone could walk me through the steps it takes to get from where it is to where it was, that would be great. Again, it was rooted and unlocked, then I used Odin to go back to stock (which I think means rooted stock, so simply the stock software while still being rooted and unlocked), and now I want to send it back to rooted/unlocked. Also, remember that the mainboard was replaced, and I am not sure if that matters to the whole process.
Thanks!
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Mandroidified said:
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
But do I need to reroot it? I guess I assumed that putting it back to stock meant rooted/unlocked stock, or stock software. No big deal, I can just reroot/unlock it like I did the first time, but I assumed it was something different.
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
kimdoocheol said:
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
Click to expand...
Click to collapse
Can you explain triangle away? Is that short for odin and what not?
Mindstar1 said:
Can you explain triangle away? Is that short for odin and what not?
Click to expand...
Click to collapse
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
kimdoocheol said:
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
Click to expand...
Click to collapse
Yes I'm sure. The bootloader had to be unlocked for triangle away to work (see screen shot from triangle away OP). So when he uses odin and re locks it's to late. Also, flashing stock firmware doesn't trip the flash counter.
Sent from my SGH-T889 using xda app-developers app
Mindstar1 said:
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Mindstar1 said:
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Im not sure if it's rooted already or not. If it is then install a recovery and flash a ROM. If not then reroot with root 66 odin install a recovery and flash
Sent from my SGH-T889 using xda app-developers app
My solution
OK, so I got the phone back and ran into a few hiccups but got it worked out.
Basically I got the phone and re-rooted it and when I tried to install a new recovery I got an error telling me that I am using bad software and I should take the phone to VZW (yeah right).
I then hopped back on ODIN and went back to stock, same way I did before sending it in to Sammy. Once I did that, I went back to the thread about rooting/unlocking and found that there was an update since I last visited. Now, there was a one click method so I decided to give that a shot. I plugged her in, had some issues with drivers but got it worked out, then ran the process. Once it was finished, all was well.
I am not sure if the phone was still rooted/unlocked or not, but either way the one click method appeared to straighten it out.
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
Safestrap doesn't root, so there's things that you've done that you're not telling us. How did you root your phone? What else did you do after you rooted?
The "firmware detected issues" usually means that you tried to flash recovery, custom kernel, etc. Did you try to flash custom recovery?
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
How did u root your phone?
safestrap enabled, Hyperdrive driven
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Why were you in odin? What were you flashing?
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Click to expand...
Click to collapse
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app[/QUOTE]
james581 said:
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
[/QUOTE]
a sticky thread is set up and is a WIP for S4 people in the general section to assist those who wish to mod their phones
http://forum.xda-developers.com/showthread.php?p=49335074
Have a verizon s4 that was originally on mdk. I rooted, and have been using hyperdrive for some time. After many sudden random reboots, I decided to change to another rom, Gdux. When I lost wifi, it was recommended to flash a new kernel to restore this functionality. As soon as I did this, I got some screen that said return your phone to verizon, something about unauthorized software.
Searched and searched the net and found that I could odin back to stock again. I followed all instructions,but now phone won't boot past verizon splash screen, and it gets hot. REALLY hot while sitting there on verizon splash screen. I can't get to recovery, only download mode after I pull battery. Going to "lose" phone for warranty replacement if I can't get it to work. Please help!!!
Flash an MDK stock odin tar in download. You'll be good as new and be able to do what you want again
aidankiller4 said:
Flash an MDK stock odin tar in download. You'll be good as new and be able to do what you want again
Click to expand...
Click to collapse
Ive tried for 2 days to find one in tar format. Only found one and it won't download on my computer. Know where to find file?
Try this http://www.androidfilehost.com/?fid=22979706399752783
Tried that and get stuck on Verizon screen
Sent from my SM-G730V using xda app-developers app
aidankiller4 said:
Try this http://www.androidfilehost.com/?fid=22979706399752783
Click to expand...
Click to collapse
The phone boots to verizon splash screen and sits there, gets almost too hot to hold, and still nothing. I pulled battery after 30 minutes. Should I try to flash this and then another kernel tar?
Yeah
Make sure you're checking the .tar files MD5 for accuracy. Make sure it's compatible with your radio/baseband version as well.
Sent from my SCH-I545 using xda app-developers app
RBarnett09 said:
Make sure you're checking the .tar files MD5 for accuracy. Make sure it's compatible with your radio/baseband version as well.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I know that I originally started with MDK, there's no way to check anything now because it won't boot. I rooted the day I got the phone and haven't taken an OTA.
Still doesn't work, any other files I can try?
bjlandt said:
I know that I originally started with MDK, there's no way to check anything now because it won't boot. I rooted the day I got the phone and haven't taken an OTA.
Still doesn't work, any other files I can try?
Click to expand...
Click to collapse
If you haven't taken any OTA's or flashed any radios, then you don't need to worry about that part.
Flashing the .tar file SHOULD have the kernel included... or at least I'm thinking it would. It should.
But after It flashes in Odin, let it sit for a good 20 minutes after it says success. Just so you can be assured that it had the time to flash successfully.
Sent from my SCH-I545 using xda app-developers app
RBarnett09 said:
If you haven't taken any OTA's or flashed any radios, then you don't need to worry about that part.
Flashing the .tar file SHOULD have the kernel included... or at least I'm thinking it would. It should.
But after It flashes in Odin, let it sit for a good 20 minutes after it says success. Just so you can be assured that it had the time to flash successfully.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a way to flash a twrp recovery through odin? I have several backups on my sd card, and I think there is one on there where I backed up everything when I first got it.
Yes.
Here's a link to some instructions and and a page that can send you to the TWRP Odin compatible file.
http://www.theandroidsoul.com/latest-twrp-recovery-for-verizon-galaxy-s4-android-4-4-compatible/
Sent from my SCH-I545 using xda app-developers app
RBarnett09 said:
Yes.
Here's a link to some instructions and and a page that can send you to the TWRP Odin compatible file.
http://www.theandroidsoul.com/latest-twrp-recovery-for-verizon-galaxy-s4-android-4-4-compatible/
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!! Found a file that worked!!! Thanks for all the help!
bjlandt said:
Thank you!!! Found a file that worked!!! Thanks for all the help!
Click to expand...
Click to collapse
Yes sir. Glad I could help.
You're welcome.
Sent from my D2LTE (D2VZW) using XDA app-developers app
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
jeffysonp said:
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
Click to expand...
Click to collapse
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
aircooledbusses said:
Alright, I know this is not the help/question/noob thread, but I'm I'm a pickle. Redirect me if you must. Verizon s4 that was on nc5 baseband-i don't know the bootloader, but it was 4.4.2 if that helps. Rooted with towel root and twrp through too manager. Yeah, I know that's where the problem came from. So now the phone is (hopefully) in a soft brick state stuck in down load or Odin mode. Odin recognizes the phone. I don't care to keep DAT or retain root, I just was it to function. Is the nc5 full wipe with the pit my correct next step? Thank you in advance, razz me if you must, I deserve it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's definitely hope. If Odin can't bring you back I bet Heimdall could. It's a little more involved but obviously worth it.
Sent from my SCH-I545 using Tapatalk
Awesome! I've never used hemidal yet, but have recently been doing much better with adb commands, so I'm totally willing to learn. I'll post back here in a few days
Sent from my Nexus 7 using XDA Premium 4 mobile app
I was trying to flash Hyperdrive and ended up having to update to NC5, I can't remember what my phone was out of the box, I will be able to tell you in a few hours when I get my box. I just got the phone last week, so probably 4.3.
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
decaturbob said:
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
also odin is very touchy with using usb cables, usb ports and computers
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
Yep, from the thread you suggest.......... "The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases."
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NC5 is in this thread
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Slowbalt said:
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
jeffysonp said:
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
Click to expand...
Click to collapse
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Also once you're back to stock run Tri Angle Away to get rid of that annoying CUSTOM screen at boot lol can't stand that thing and on my phone it can make getting into CWM a pain as well.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't seem to get into stock recovery either. I tried re-flashing and I still get the same results, when I try to boot into recovery I get the Samsung logo with the unlocked padlock, and then it just shuts down. :/