[Q] HELP - MJ7 to MK2 to NC5, Hyperdrive, Softbrick - Galaxy S 4 Q&A, Help & Troubleshooting

So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.

bradbb2009 said:
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
Click to expand...
Click to collapse
Nope. No more info needed. you have to follow two easy steps to repair:
1. go here;
2. Ask your question in Q&A section.
sorry, but you posted in wrong S4 thread:highfive:

Related

[Q] S4 Att Soft Bricked Help <ID:0/006> FAIL! (Auth)

Unfortunately when i purchased the S4 it already had the newest firmware on it and the locked bootloader so all i could do was root the device. I was planning on getting rid of it so i wanted to unroot and restore everything back to stock so i loaded up odin3 and tried but ended up soft bricking the phone somehow. I get the firmware upgrade encountered issue on the screen and tried to restore it via kies and it did not work. So i ended up going back to odin3 and loaded up everything in the MF3 TAR. Everything seemed to be going fine until the end i got this message.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Should i just junk this phone because it looks like even with the high bounty the bootloader will never be unlocked and what else can you do all suggestions would be appreciated thank you for your time
Should i get I337MK2_Combined_Odin_Tar.rar instead ? because that would be ok with the locked bootloader
FIXED use MK2
kriticalglitch said:
unfortunately when i purchased the s4 it already had the newest firmware on it and the locked bootloader so all i could do was root the device. I was planning on getting rid of it so i wanted to unroot and restore everything back to stock so i loaded up odin3 and tried but ended up soft bricking the phone somehow. I get the firmware upgrade encountered issue on the screen and tried to restore it via kies and it did not work. So i ended up going back to odin3 and loaded up everything in the mf3 tar. Everything seemed to be going fine until the end i got this message.
<id:0/006> added!!
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> platform_i337ucuamf3_812098_rev06_user_low_ship_multi_cert.tar.md5 is valid.
<osm> checking md5 finished sucessfully..
<osm> leave cs..
<id:0/006> odin v.3 engine (id:6)..
<id:0/006> file analysis..
<id:0/006> setupconnection..
<id:0/006> initialzation..
<id:0/006> get pit for mapping..
<id:0/006> firmware update start..
<id:0/006> singledownload.
<id:0/006> boot.img
<id:0/006> nand write start!!
<id:0/006> recovery.img
<id:0/006> persdata.img.ext4
<id:0/006> system.img.ext4
<id:0/006> fail! (auth)
<id:0/006>
<id:0/006> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1)
<id:0/006> removed!!
Should i just junk this phone because it looks like even with the high bounty the bootloader will never be unlocked and what else can you do all suggestions would be appreciated thank you for your time
should i get i337mk2_combined_odin_tar.rar instead ? Because that would be ok with the locked bootloader
Click to expand...
Click to collapse
use mk2 fixed
kriticalglitch said:
use mk2 fixed
Click to expand...
Click to collapse
There is over 30 amazing custom roms for mk2. And last night, making history, Kit Kat 4.4.2 is also an option with 2 fantastic custom roms posted thus far. I wouldn't junk the phone if I were you. Though other devices with unlocked boot loaders are great, nothing really beats the S4, well maybe the S5 but it's not out till next month. Here is the guide. Be sure to read thoroughly before you do anything. Good luck & also please thank the op in the threads.
http://forum.xda-developers.com/showthread.php?t=2616221

Soft Bricked

Hi all,
Phone is soft bricked, I cant access the recovery, but can access the odin download mode.
The phone came with I337mvluamg1 firmware, Although when i try to reflash the phone with the stock firmware odin fails..
Im using Odin 3.07
And the I337MVLUAMG1 firmware from sammobile but i get this message from odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<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> SingleDownload.
<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)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is day 4 with the phone soft bricked and it just wont budge, ive tried multiple different firmware versions, even back tracking. but nothing.
Any tips? suggestions?
Thanks
sdawg1010 said:
Hi all,
Phone is soft bricked, I cant access the recovery, but can access the odin download mode.
The phone came with I337mvluamg1 firmware, Although when i try to reflash the phone with the stock firmware odin fails..
Im using Odin 3.07
And the I337MVLUAMG1 firmware from sammobile but i get this message from odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<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> SingleDownload.
<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)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is day 4 with the phone soft bricked and it just wont budge, ive tried multiple different firmware versions, even back tracking. but nothing.
Any tips? suggestions?
Thanks
Click to expand...
Click to collapse
Im now getting a pass from I337MVLUAMDJ in odin, but the phone still wont boot to recovery or the OS
Odin back to stock. Don't use what's in my description.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Make sure your trying to flash the same version of firmware.... if the phone was originally on 4.3 you can't flash back to 4.2. You can go up versions but not down... if the bootloader is 4.3 you can't get to 4.2
I tried flashing the stock firmware but it failed, but when i use a version above stock i get a pass from odin, the phone resets but when boots, gets stuck on the samsung galaxy s4 screen, and wont boot to recovery..or the OS....
sdawg1010 said:
I tried flashing the stock firmware but it failed, but when i use a version above stock i get a pass from odin, the phone resets but when boots, gets stuck on the samsung galaxy s4 screen, and wont boot to recovery..or the OS....
Click to expand...
Click to collapse
You need to keep trying to get into recovery. When you do, do a factory reset
Sent from my Nexus 5

[Q] G900f Odin ext4 Fail when downgrading to 4.4.2 from 5

Hello
I recently upgraded my samsung galaxy S5 (G900F) to android 5. I downloaded the firmware from sammobile a few weeks ago and it's been working great. Since I live in South Africa, the updates take quite a while to reach us, and finally they're here. I downloaded the original 4.4.2 firmware so that I can upgrade my firmware from the phone itself (Thinking it would be best that way). The version I'm trying to install is this-
"G900FXXU1ANG2_G900FOXE1ANI2_G900FXXU1ANG2_HOME.ta r.md5"
That's the name of the md5 file I'm using. When I click "Start" in Odin, it takes a few minutes to do a few things and then all of a sudden:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXE1ANI2_G900FXXU1ANG2_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen it says:
ODIN: Invalid ext4 image
Please help!!
I successfully downgraded back to 4.4.2.
Ensure that you are not using an USB HUB nor other cable than original...
S5 tends to be a little stuborn on that LOL

Failed root on SM-N910T now stuck at recovery booting

Bought this to make into a rooted note 4. Not my main phone yet, I have an AT&T version.
Attempted to root following the directions on CFROOT, that got me to this point. Now have spent 2 days searching for solutions and trying things. No progress!
In download mode Using Odin 3.9 and 3.10.7 the CFROOT file report success but stuck in recovery booting. Attempting to reinstall the entire firmware Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Any help would be greatly appreciated!
John
dylistn said:
Bought this to make into a rooted note 4. Not my main phone yet, I have an AT&T version.
Attempted to root following the directions on CFROOT, that got me to this point. Now have spent 2 days searching for solutions and trying things. No progress!
In download mode Using Odin 3.9 and 3.10.7 the CFROOT file report success but stuck in recovery booting. Attempting to reinstall the entire firmware Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Any help would be greatly appreciated!
John
Click to expand...
Click to collapse
You're in the wrong place. These are the S4 forums, not Note 4.
Anyway, AT&T devices have a locked bootloader and I don't think CF-Auto-Root can root those.
So you may have to find another solution to rooting.
But before that you may have to flash the stock firmware again, as the current one is messed up by the failed root flash.
Thank you
I thought I had the right forum. Can I move this to another forum. Or should I start a new thread and delete this?
dylistn said:
I thought I had the right forum. Can I move this to another forum. Or should I start a new thread and delete this?
Click to expand...
Click to collapse
It can be moved. Select the report option and as a reason select thread moving.

Failed root on SM-N910T now stuck at recovery booting

Bought this to make into a rooted note 4. Not my main phone yet, I have an AT&T version.
Attempted to root following the directions on CFROOT, that got me to this point. Now have spent 2 days searching for solutions and trying things. No progress!
In download mode Using Odin 3.9 and 3.10.7 the CFROOT file report success but stuck in recovery booting. Attempting to reinstall the entire firmware Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Any help would be greatly appreciated!
John
I treid to Root a T-Mobile version
Not the AT&T version. The AT&T version is my main phone now. I like the Note 4, But want a rooted version. See the above post about the failed Root.
dylistn said:
Not the AT&T version. The AT&T version is my main phone now. I like the Note 4, But want a rooted version. See the above post about the failed Root.
Click to expand...
Click to collapse
This method for n910t
1,Flash twrp recovery in odin
2,Boot into twrp by pressing volume up+home+power buttons together.
3,flash supersu.zip latest version from twrp
Your phone may reboot couple of times so don't freak out its normal.
Thats it
You will have permanent root and your device will boot fine.
Twrp recovery below
https://mega.nz/#!DIFFVSpQ!bUCEAa-VRdkeT4VgMJ-4cUXuo-ZiYbihOSWiw6Ic_wo
Supersu below
https://mega.nz/#!XAsUjARJ!XqYZkle6wTarq1a8-zAnhwrbd4IdpzpJryNCAU3g9k4
Dont try this on AT&T it will not work and you may brick your device.
Thanks Dubai. But I did some thing wrong! On step 1 above Odin log file:
<ID:0/006> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!

Categories

Resources