Ok so i rooted my phone a bit back but i keep getting firmware upgrade notifications so i just wanted to unroot and be vanilla firmware. well i tried with Odin and it didnt work so im stuck in Odin mode and i cant get back to using the phone. Please HELP!
Here is my guide.
http://www.androidfilehost.com/?fid=23501681358538464
This does not seem to be working...
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
techguy2002 said:
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i read at it and did what it said. Instructions werent super clear. Is that for the ME7?
not for ME7 but how to get from nc5 to mk2 and back rooted to nc5. I dont know how you would get back to ME7. I saw the post and made the comment and couldnt delete it.
@Radllik
There is no reason to open two threads on the same subject. This thread since it has replies has been moved to the Q&A section where all questions and request for assistance belong.
Your other thread will be locked, please pay attention to the rules in the future.
EFM
Have a great day!
Same, stuck in odin/download mode
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<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)
I'm pretty sure you couldn't reinstall me7 as its no longer signed? Might want to look for full wipe tars for Odin and try that.
Sent from my SCH-I545 using XDA Free mobile app
Vidanl said:
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<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)
Click to expand...
Click to collapse
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
That link does not work on the page you sent. Also i live in Michigan.
the link isn't working
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Vidanl said:
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Click to expand...
Click to collapse
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
they wont pass in odin
k1mu said:
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
Click to expand...
Click to collapse
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Vidanl said:
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Click to expand...
Click to collapse
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
got it working
k1mu said:
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
Click to expand...
Click to collapse
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Same exact problem!
Vidanl said:
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Click to expand...
Click to collapse
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
cashmoneysalad said:
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
Click to expand...
Click to collapse
Verizon S4 16Gb PIT can be downloaded from here http://www.androidfilehost.com/?fid=23269279319199111
Sent from my SCH-I545 using Tapatalk
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
cashmoneysalad said:
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
Click to expand...
Click to collapse
Fused:6 - your phone has the NC5 bootloader.
Binary:5 but you're trying to flash MJ7/MK2.
At this point you can follow Surge1223's directions to back down to MK2 then upgrade to NC5 rooted. http://forum.xda-developers.com/showthread.php?t=2726868
Or, do the same thing using techguy2002's directions: http://forum.xda-developers.com/showthread.php?t=2763834
Related
Information about my phone first off:
Phone Name: Samsung Galaxy S3
Carrier: T-Mobile
Locale: (US)
Model: SGH-T999
Update (01:38PM EST): ROMs from the list I was using were bad. Loaded a customer ROM and had no issue getting it resolved.
Update (08:54AM EST): I attempted an install and the error that came back when trying to install OTA_T999_UVALJ4_UVDLJA.zip. Said an MD5 file was missing.
Update (08:42AM EST): I'm downloading the OTA Update fro UVALJ4 - UVDLJA and will report back shortly once it finishes downloading.
Worth noting: I have backed up anything important to me from Titanium Back Up so I am not to worried about loss of data.
So I thought I'd finally jump up to Jelly Bean and keep my rooted status on my phone. I initially started out having an issue just downloading an OTA update from T-Mobile thinking my rooting was doing something to prevent it from updating. I searched and found a way to update via Kies, but lost root in the process. I attempted to use a root option which apparently wasn't the correct one and I found myself no longer booting into my phone. It displaying an error about needing to access Kies and trying to the recovery option. I ran its recovery option, but it was not seeing my device on the list so I pulled the software and drivers from my machine, rebooted and tried again to no avail, Kies was still not seeing my phone and any chance of recovering from this felt like it was going down the toilet. I still have access to the boot screen for downloading and my recovery program TWRP on it. I ran into issue attempting to install new firmware with Odin getting failed errors. I looked up said errors relating to ext4 and came up empty. I am certain I deleted something important but I am still in a position to load from my external SD card and Odin on my machine can make attempts to push firmware over, but I am at an impasse here because about most of the way in, it fails. I tried using the root firmware listed here. I downloaded T999_UVDLJA at the top of that list and only had Auto Reboot and F. Reset Time per instructions noted in that topic.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Read ..
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is my first time posting, but I assure you, I spent a lot of time reading through these forums and I'm not sure where I am making a mistake at and I would appreciate any insight others have. Please let me know if there is any relevant information you think I might have left out that would be pertinent to answering this question more thoroughly and accurately.
Currently at this moment of edit, I am attempted to push T999_UVALJ4 to my phone with the same result:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Read ..
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Re: [Q] Tried to update to Jelly Bean with my SGS3, made a mess...
Have you tried flashing a custom ROM based on stock? That way you might be able to re-install the drivers and other such important system files.
Sent from my Xperia Pro using xda app-developers app
ajabhi95 said:
Have you tried flashing a custom ROM based on stock? That way you might be able to re-install the drivers and other such important system files.
Sent from my Xperia Pro using xda app-developers app
Click to expand...
Click to collapse
What drivers? I tried a OTA, but no luck. It complained there was no MD5 file and when I got one with an MD5 file, it says it couldn't open then the zip file.
Re: [Q] Tried to update to Jelly Bean with my SGS3, made a mess...
No man I'm suggesting that you try flashing a ROM based on stock via TWRP
Sent from my Xperia Pro using xda app-developers app
ajabhi95 said:
No man I'm suggesting that you try flashing a ROM based on stock via TWRP
Sent from my Xperia Pro using xda app-developers app
Click to expand...
Click to collapse
How does a ROM vary in comparison to the firmware that Odin uses? I am assuming not, but TWRP seems to use ZIP files to do their installs instead of tar files like Odin. How am I supposed to be packaging these?
MistoRoboto said:
How does a ROM vary in comparison to the firmware that Odin uses?
Click to expand...
Click to collapse
The custom ROMS found the development sections are either based on CM10/AOSP/AOKP or Samsung's Original touchwiz. Most of these ROMS have been modified to improve stability, performance and battery life. They also come prepackaged with SuperSU (root).
Example
Download this ROM:
http://forum.xda-developers.com/showthread.php?t=1804260
Copy it to your sd-card, pop it back into s3, go to TWRP>Mount> Use External SD. Go back to the main menu and Install the ROM. This one comes with an aroma installer so you can further customize what you want to install.
illmatic24 said:
The custom ROMS found the development sections are either based on CM10/AOSP/AOKP or Samsung's Original touchwiz. Most of these ROMS have been modified to improve stability, performance and battery life. They also come prepackaged with SuperSU (root).
Example
Download this ROM:
http://forum.xda-developers.com/showthread.php?t=1804260
Copy it to your sd-card, pop it back into s3, go to TWRP>Mount> Use External SD. Go back to the main menu and Install the ROM. This one comes with an aroma installer so you can further customize what you want to install.
Click to expand...
Click to collapse
Downloading right now, will report back on the results.
MistoRoboto said:
Downloading right now, will report back on the results.
Click to expand...
Click to collapse
Good luck. :good:
illmatic24 said:
Good luck. :good:
Click to expand...
Click to collapse
illmatic24, it appears that ROM I was using was just bad. Though that makes me wonder if I will ever be able to find the original if I ever decide to sell this phone. That ROM you linked me to is amazing, there are more options there than I know what to do with.
MistoRoboto said:
illmatic24, it appears that ROM I was using was just bad. Though that makes me wonder if I will ever be able to find the original if I ever decide to sell this phone. That ROM you linked me to is amazing, there are more options there than I know what to do with.
Click to expand...
Click to collapse
I'm glad it worked. Cheers and don't forget to thank the developer of the ROM.
I am having nearly the same problem with my Samsung SPH-l710. This thread seems to indicate the OP had a bad file download. I may have a new problem.
Today, I tried the process linked here:
http://honai-android.blogspot.com/2013/05/how-to-root-galaxy-s3-sprint-sph-l710.html
I had used a similar one about a year a go and it worked great.
This time, the process failed.
The phone will no longer boot (gets stuck on the logo screen). I can still hold "vol down + home + power".
I did a search and found this thread. I re-downloaded the file hoping my download was bad, same result.
So, then I got the latest stock rom from here:
http://forum.xda-developers.com/showthread.php?t=1737859
It fails also - here is the (last part) of the output window from Odin3:
------------------------------------------------------
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------
I think it said that same thing, or similar, the first time.
It fails here for any rom I try.
What am I doing wrong? Surely all these roms aren't bad?
Thanks for any help.
Also, I have tried several brand new micro USB cables, and different USB ports, as suggested here:
http://forum.xda-developers.com/showthread.php?t=1761870
I tried one more thing - I killed Kies as suggested here:
http://forum.xda-developers.com/showthread.php?t=2082081
STILL it didn't work...
Then I moved to my windows 7 laptop - problem fixed!
I spent like 7 hours on this, and all I had to do was move to my laptop.
What a major pain...I found one more forum for a Samsung galaxy note (can't remember what version) who moved to a laptop and it worked. I will post the link if I can find that thread again.
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
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
EDIT:
I fixed this thanks to k1mu. He gave me this. and it worked great. Use the no-wipe ROM.
spence1322 said:
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
Click to expand...
Click to collapse
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
k1mu said:
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
Click to expand...
Click to collapse
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
First idea would be stop flashing random builds. You need to find out what build you are on, and flash that through Odin. Once you update to a newer build, you cannot revert back to an older build.
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
decaturbob said:
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
Click to expand...
Click to collapse
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
k1mu said:
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
Click to expand...
Click to collapse
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
decaturbob said:
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
Click to expand...
Click to collapse
Look... I'm sorry I don't know everything like you... I'm 15
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
I'm 15 as well, but I also make sure to read up on what I'm doing before I destroy my phone.
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
Don't want to lecture but being your age makes it doubly important to research....that's how you get to have knowledge.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
drunkensunday said:
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
Click to expand...
Click to collapse
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Oh then the first thing I did was try to odin this file: N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5
That failed, then I tried the 2 previously mentioned one click odin stocks.
Oh and I was on TWRP 2.6.1 but now I have no recovery.
drunkensunday said:
Oh and I was on TWRP 2.6.1 but now I have no recovery.
Click to expand...
Click to collapse
Have you tried odin twrp to your phone maybe it doesn't like you not having any recovery?
Cheryl
drunkensunday said:
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Click to expand...
Click to collapse
The MJ4 tar would've worked had you flashed it (you were on MJ4, JellyBean, but on a prerooted rom).
Having failed at MJ4, going with the NAB and NC5 (both KitKat), may have sent your system into a nosedive of confusion.
Tell me if you can get into download mode at all home + power + volume down).
Your version of TWRP is old, but that has nothing to do with this. You need to put your phone back to stock, then upgrade if you want to flash a KitKat rom.
The MJ4 tar file will put stock everything back on your phone, even recovery, so your TWRP will be gone...but you can get it back.
Let me know if you can get into download mode, and we can take it from there.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
drunkensunday said:
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
Click to expand...
Click to collapse
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
kaos420 said:
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
Click to expand...
Click to collapse
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
drunkensunday said:
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
Click to expand...
Click to collapse
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yes, but in a usb 2.0 port if it matters....
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
kaos420 said:
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
Click to expand...
Click to collapse
I think either trying it from a Windows PC (shouldn't matter, but why not try) or carefully selecting a Sprint store (root friendly tech, knows what he or she is doing) for an over-the-wire update, are worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a possibility that you had a bad download and also are you using the odin you from chain fire when you rooted? I had the same problem last month. I spent 5 hours trying to figure it out. Turns out I just had a bad download.
Sent from my SM-N900P using xda app-developers app
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
drunkensunday said:
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
Click to expand...
Click to collapse
did you have tep? did you tell them what you tried?
Here is what has happened:
1. Successfully rooted Note 3
2. Attempted to do WIFI tether hack by changing services.jar and services.odex
3. Rebooted phone and it started up fine but hung on the yellow spring screen (must have downloaded an incompatible version)
4. Tried to reset to factory in recovery mode but it didn't work; still hung on the yellow screen
5. Tried to use KIES to download firmware but it does not recognize the phone with either v2.6 or v3.0
6. Downloaded stock firmware and attempted to flash through ODIN 3.07 but it failed
7. Next I attempted to flash stock FW through ODIN 3.09 but lost power and now I get "firmware upgrade encountered an issue" error
8. It says go to KIES recovery mode but it does not recognize the phone
Here is ODIN 3.9 dialog:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me get this fixed at least to stock?
aksaunders said:
Here is what has happened:
1. Successfully rooted Note 3
2. Attempted to do WIFI tether hack by changing services.jar and services.odex
3. Rebooted phone and it started up fine but hung on the yellow spring screen (must have downloaded an incompatible version)
4. Tried to reset to factory in recovery mode but it didn't work; still hung on the yellow screen
5. Tried to use KIES to download firmware but it does not recognize the phone with either v2.6 or v3.0
6. Downloaded stock firmware and attempted to flash through ODIN 3.07 but it failed
7. Next I attempted to flash stock FW through ODIN 3.09 but lost power and now I get "firmware upgrade encountered an issue" error
8. It says go to KIES recovery mode but it does not recognize the phone
Here is ODIN 3.9 dialog:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me get this fixed at least to stock?
Click to expand...
Click to collapse
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat
Sent from my SM-N900P using Xparent BlueTapatalk 2
Downlloading NC5
Epix4G said:
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am downloading an nc5 .tar now. I am in the middle of the New Mexico desert on military duty so I am connecting to my phone as a hotspot and it takes forever. My DL speed is fluctuating between 185-200 kb/s. Do you know of any private links for either a nab or nc5 that would be faster for me?
Epix4G said:
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Overnight, I downloaded the SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe. This morning, I followed the instruction in that XDA post, plugged the phone, hit start, and crossed my fingers. Fifteen minutes of sweating later I had a factory stock phone again and I let out that big breath I was holding. Now, I am deciding if I want to root again and try another wifi hack. Thanks for the help. You are a lifesaver...a phone save for sure.
aksaunders said:
Overnight, I downloaded the SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe. This morning, I followed the instruction in that XDA post, plugged the phone, hit start, and crossed my fingers. Fifteen minutes of sweating later I had a factory stock phone again and I let out that big breath I was holding. Now, I am deciding if I want to root again and try another wifi hack. Thanks for the help. You are a lifesaver...a phone save for sure.
Click to expand...
Click to collapse
Congratulations! Your Knox flag is still 0x1 though so you are not "factory stock". Once you root and/or install a custom recovery that flag is set and can't be reset, at least not on our phones yet.
Still Happy
JimSmith94 said:
Congratulations! Your Knox flag is still 0x1 though so you are not "factory stock". Once you root and/or install a custom recovery that flag is set and can't be reset, at least not on our phones yet.
Click to expand...
Click to collapse
You are correct but I am still very pleased. BTW, do you know of a wifi tether hack for a build ending in NC5?
aksaunders said:
You are correct but I am still very pleased. BTW, do you know of a wifi tether hack for a build ending in NC5?
Click to expand...
Click to collapse
Go into the Android Dev section for the Note 3. Freeza, Sac23, Joshbeach all have NC5 Roms that have the wifi hack built in. Also, Josh has a Mod section and has the hotspot hack itself.
Nickitt said:
Go into the Android Dev section for the Note 3. Freeza, Sac23, Joshbeach all have NC5 Roms that have the wifi hack built in. Also, Josh has a Mod section and has the hotspot hack itself.
Click to expand...
Click to collapse
But have to be on a deodexed ROM ... there is not one for odexed just stock ROM
Sent from my SM-N900P using Xparent BlueTapatalk 2