**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
Related
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
I was on MI1 rooted, I flashed the factory MI1 back to my phone via odin so I could download the update OTA.
The downloaded the update, it installed and my phone rebooted. On the reboot, I got a message saying the "UIDs on the system are inconsistent" but that was covered by non-stop failed processes. Every time I clicked okay, more processes would fail, leaving the phone unusable. I plugged it into my computer and using Verizon Repair assistant I try to do a factory restore. The restore stopped at 83% and said "device unexpectedly unplugged" and would not go any further.
I have tried several times to do a restore but without any luck. The phone will only boot to a "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE" then it tells me to connect to kies. It will not boot into recovery and KIES will not allow me to access the "firmware upgrade and initialization" because i cannot find a serial number. I spoke to a verizon rep, they gave me a serial number, it didn't work.
Any ideas? I have tried to ODIN the MI1 again, but it fails:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The phone's screen says: CHECK FAIL FUSED 5 BINARY 4
anyone have any thoughts?
Is there a .tar out for the new MJ7 update? maybe i could flash that?
You Sure you grabbed the ml1 image? When trying to flash a previous firmware (which you cant do) it fails at aboot like yours did.
Edit:
Nevermind I now see you did after re reading your post. Havent seen an mj7 download mode image but someone posted the update.zip for stock recovery.
villainous said:
Is there a .tar out for the new MJ7 update? maybe i could flash that?
Click to expand...
Click to collapse
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I've checked the MD5 and it matches, I've tried several different versions of MI1.
When I connect to the Verizon Repair Wizard, it shows my version as MI1, however I did install the OTA update today, shouldn't it say MJ7?
Also, since I installed the update, when I try to ODIN MI1 it should fail, is there any way to do a recovery any other way?
Ideally i would like a flashable MJ7 tar file
It is frightening how upsetting it is to be without a phone.
Verizon is sending me a replacement, but any help in recovering this phone so that I can retrieve my files would be greatly appreciated.
villainous said:
Verizon is sending me a replacement, but any help in recovering this phone so that I can retrieve my files would be greatly appreciated.
Click to expand...
Click to collapse
I think you'll need to wait for a mj7 tar file. Your Odin output shows "fused 5" which I think means mj7 loaded far enough to blow a qfuse.
jd1639 said:
I think you'll need to wait for a mj7 tar file. Your Odin output shows "fused 5" which I think means mj7 loaded far enough to blow a qfuse.
Click to expand...
Click to collapse
What is the usual wait time for these files to become available after it is released from Verizon?
As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Working from this thread: http://forum.xda-developers.com/showthread.php?t=2578209
Started with a phone that had the OTA Kitkat update. Tryed this from Surge1223 http://forum.xda-developers.com/showthread.php?t=2726868, didn't work. ended up downgrading (trying) to back MK2 and ended up with phone with no sound.
Came to the " [ODIN][TAR] VRUEMK2 Emergency and No-Wipe Odin tars" thread and tried that. Odin failed on the tar.md5 full wipe file "ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5" as shown in the log below. Tried the pit file too "JFLTE_USA_VZW_16G.pit" just to get the phone to reboot.
At this point I just want a unrooted stock phone. Kitkat would be fine with me, wanted to root for some stuff, but it's not that important right now. Waited for the PASS in ODIN, phone boots fine, still no sound.
Looking for help, thanks.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You're using the mk2 tar not the nc5 tar, use nc5
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Sorry, I linked to the wrong original thread. I was trying to get back to MK2. I corrected the title and link to the thread I was using.
The phone is now on MK2, but with no sound.
Surge1223 said "Flash the NC2 hlos for sound to work and use bypasslkm for wifi" in this thread http://forum.xda-developers.com/showthread.php?t=2726868, but I've not found a real clear (for me) description on how to do those. I was hoping to ODIN back to stock and get the sound back.
thanks.
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
montejw360 said:
KitKat OTA keeps failing. Most likely because of what I've already tried and failed to make work.
Click to expand...
Click to collapse
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
montejw360 said:
Thanks. Went through this thread [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars and got the phone working again.
Tried the Verizon Software Upgrade program, but the links to it always took me to a blank page.
Where is the "Verizon Mobile" folder? On verizonwireless.com, or here on xda?
Click to expand...
Click to collapse
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
k1mu said:
On your phone. Plug it in, and the drive will appear. Windows and Mac apps.
Click to expand...
Click to collapse
saw that come up many times, just never looked at it. good to know, thanks.
k1mu said:
OTA won't work if you've got a phone with modified files. You've got to return to factory stock before an OTA.
If you're desperate, use the Verizon Recovery agent to wipe and re-flash. Plug your phone into your PC, then open the Verizon Software Upgrade Assistant in the "Verizon Mobile" folder.
Click to expand...
Click to collapse
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Ovreel said:
Can you go into some detail on this? How would the process go with this tool? And why is it a desperation move?
Click to expand...
Click to collapse
It's a "desperation move" because it wipes everything on the phone, downloads a factory stock image, then flashes it. Basically, it's a emergency recovery tool that shouldn't be used if you care about what's on your phone.