i have a galaxy s 4 verizon i have mdk and i have tried unrooting it because my friend tried rooting it while i was gone and messed up the process but im using odin3.07 and im getting this.
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
my phone says start [224,1440]
sw rev. check fail : fused 5, binary 1
and ive tried 2 other stock files and i still get the same thing i even tried a Me7 to please help
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_u ser_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im using Odin v1.85
this what i get from trying mdk and me7
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
he said he followed this youtube video https://www.youtube.com/watch?v=uii_mYm8IGE
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
A1C_Malone said:
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
Click to expand...
Click to collapse
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
scryan said:
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
Click to expand...
Click to collapse
where can i download mj7 or mk2 stock i have a verizon s4
Sounds like you may want to follow this... If a newer firmware was attempted to be flashed..http://forum.xda-developers.com/showthread.php?t=2579278. IF NO LONGER MDK AVAILABLE FOLLOW THOSE STEPS.
A1C_Malone said:
where can i download mj7 or mk2 stock i have a verizon s4
Click to expand...
Click to collapse
use Kies and get a factory clean install
Related
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dmonger11b said:
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2280680
Sent from my SCH-I605 using XDA Premium HD app
dmonger11b said:
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Click to expand...
Click to collapse
It's been a while since I've done any troubleshooting, but 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's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
larry_thagr81 said:
It's been a while since I've done any troubleshooting, but 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's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
Click to expand...
Click to collapse
Awesome thank you. Worked perfectly. I feel kinda embarrassed I didn't look in Adam's thread. But the issue was caused by something a little different than what he warned against. Either way phone booted back up. Definitely irritated I didn't look better,
Glad I could point you in the right direction.
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ArcelasTheNoob said:
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I605_VRALJB_Restore.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
cache.img
hidden.img
modem.bin
FAIL!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hey bro, have you unlocked the bootloader? if so and you're trying to go back to stock try the alternative stock odin file from imnuts.
EDITuno: http://www.androidfilehost.com/?fid=9390225151984927096
theres the link to his alt restore odin package. idk if that'll help fix the modem.bin failure, but it should help someway. hope it does! if you need anymore help you can pm me if you need to.
I'm curious to what rom you flashed. Was it for a Verizon note 2? If you get no network, try flashing the modem in recovery. That should solve it
Link for modem download.
http://www.androidfilehost.com/?fid=22946563261203878
Follow droidstyle's guide. Read his thread.
http://forum.xda-developers.com/showthread.php?p=34891181
EDIT: Just realized you are making multiple threads for the same question. Sorry dude, that's my only rule. No more help. Also noticed that you flashed an international rom. Good job :thumbup: This is why you are supposed to READ before flashing
Sent From My Sticky Note, Too?
Not needed
I apoligze if it looks like I posted this question multiple times. I was told to post in a different forum, but figured more info=better.
I returned my phone to Best Buy, replacement in a few days. So thank you for all the help, next time I'll be more careful.
Update: Root has been achieved, and Safestrap works - See here
This is a new update for SCH-1545 taking users to VRUDMI1. This is the stock factory image, taken straight from Kies. At this point only download for research or curiosity because this build has not been tested again for root access and you very well may loose both root and custom recovery by flashing this. So far I see a lot of Knox related stuff. Also, If you need to go back to stock for whatever reason I suggest using the VRUAME7 (or MDK) factory image instead. Both VRUAME7 and VRUAMDK stock Odin tars contained 14 partitions over which they would write over. However, in the newest build VRUDMI1, only 13 partitions are wrote over because it doesn’t contain a persdata.img.ext4.
Changes so far in this build:
1. VRUMDI1 DOES NOT WIPE THE PERSDATA PARTITION! (persdata.img.ext4)
2. ROOT METHOD FOR VRUAME7 NO LONGER WORKS ON THIS BUILD! - NEW ROOT METHOD here
3. New system apps are included, read more here
Nonetheless, if you want to rose root and recovery (maybe forever) then,
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA and keep Odin's default settings
3. Click start and wait for it to say pass
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5:8335da10191b0e2ce84a701b8e5249b4
Mirrors:
https://db.tt/Q6EVK0bY
https://db.tt/qZupCjFT
https://db.tt/XwsbAHdL
http://www.androidfilehost.com/?fid=23159073880936987
Your Dropbox link has been disabled.
Sent from my SPH-L720 using Tapatalk
ChadH42 said:
Your Dropbox link has been disabled.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm putting a mirror up soon.
I would guess that whatever exploit is used in ME7 to get root is fixed in this build.
*Fingers crossed*
Another mirror :good:
http://www.androidfilehost.com/?fid=23159073880936987
toadlife said:
I would guess that whatever exploit is used in ME7 to get root is fixed in this build.
*Fingers crossed*
Click to expand...
Click to collapse
why? That would totally suck lol
Sent from my SCH-I545 using XDA Premium HD app
elliwigy said:
why? That would totally suck lol
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
I meant fingers crossed that it isn't.
Kinda sad that we have to hope our devices are vulnerable.
Has anyone odined this over a phone with dmi1 already on it? I remeber folks with the international version having issues tripping the knox counter.
Sent from my SCH-I545 using xda app-developers app
Has anyone attempted flashing the radios only? I'm happy on CM 10.2, I just want the improved radios in the new TW build.
Edit: I found a thread. Sorry for taking up your precious space.
Can I use this on a currently bricked device or do I have to use the stock version?
sethjk said:
Can I use this on a currently bricked device or do I have to use the stock version?
Click to expand...
Click to collapse
This is the stock version.
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2. Here is Odin log:
Code:
<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/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
xxxtncxxx said:
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2. Here is Odin log:
Code:
<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/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is from last year man.
Sent from my SCH-I545 using xda app-developers app
xxxtncxxx said:
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2
Click to expand...
Click to collapse
Once you are on MK2, you can't flash an older release. MI1 is older than MK2, so you're trying to flash backwards.
What are you trying to accomplish? Since you're on MK2, root it, install Safestrap, then flash a custom ROM.
I suggest you read the following sticky thread: http://forum.xda-developers.com/showthread.php?t=2606501
And this thread as well http://forum.xda-developers.com/showthread.php?t=2578569
Flashing without understanding what you're doing will quickly brick your phone if you're not careful.
Good god I'm ashamed... I thought it was a newer build LOL explains alot!
Sent from my SCH-I545 using Tapatalk
Believe it or not I know what I am doing, I miss read something and thought I1 was above K2, and thinking that I couldn't understand what was happening. It's very hard to really brick an S4 if u are moderately educated in the subject you can get out of most situations. Even doing numbskull things like what I did. Was a long bad day of work, working on old out of date servers for 12 hrs can really melt your brain.
Sent from my SCH-I545 using Tapatalk
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?
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!