Good Day!
I have a kcc-cmm-sec-shve330k 32GB that i flashed using odin 3.09 and E330KKKUBML1_FULL_20140103.tar but it failed!
here is what happened with odin,
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E330KKKUBML1_FULL_20140103.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sdi.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> recovery.img
<ID:0/008> NON-HLOS.bin
<ID:0/008> modem.bin
<ID:0/008> hidden.img.ext4
<ID:0/008> boot.img
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) i dont have any clue why it works with others and not with my cp
this fw (E330KKKUCNC1_PROXYME20140319.tar) is ok and it works for me and im using it but this has issues with apps working on 4.2 and not working in 4.4. like my navigator sygic. any suggestions guys ???
Another question is, Is it normal that after flashing for few times testing 4.3 & 4.4 FW that when it done, all my sms, apps, name of carrier Oleh is there and not erased?
Thanks in advance!
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
es0tericcha0s said:
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
Click to expand...
Click to collapse
E330KKKUCNC1
KERNEL 3.4.0-683274
[email protected]#1
Many thanks for the quick reply
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
es0tericcha0s said:
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
Click to expand...
Click to collapse
Thanks again for the info. i guess I'll stick to 4.4 for now
ricotek14 said:
Thanks again for the info. i guess I'll stick to 4.4 for now
Click to expand...
Click to collapse
No problem. Yea, it sucks. Stuff like that is actually a deal breaker for me and makes me not near as interested in Samsungs (see my sig for phones I've used - many Samsungs) as I used to be, no matter the specs / features. If I wanted to be locked in like that, I'd probably be more interested in iPhones. You'd probably have more luck trying to sort out why the certain apps aren't working for you or wait for the developers to upgrade for KK - which is kind of ridiculous they haven't yet as it has been out since November.
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.
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
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
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