Good morning all.
I need to unroot (or just put stock firmware back on my device). I have Cyanogen 11, and i need to swap phone numbers on my phone. The code Sprint wants me to enter does not work with Cyanogen mod so i need to put stock firmware back on the device so sprint can have me put in the codes they need to change the phones telephone number.
Long story short, i have done a lot of research on Google and on here, and i am running into a problem.
First i am using the original (actually i have tried three different ORIGINAL (white) Samsung) USB Cable, i have tried several different USB ports.
I've have downloaded my drivers (actually had them from when i rooted in the first place), i have odin (several different versions, tried them all same result), and stock firmware .tar.md5.
The problem is after i click START in odin, it does its thing for like 10 seconds, then reports a FAIL, this is what Odin reports (this report is from using an Odin v3.185, i have tried v3.07 and 3.09 as well, same end result, but the oden report is slightly different, as it checks the MD5 in the other versions when you enter the file into Odin, vs checking the MD5 when you hit start):
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> aboot.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the PHONE itself, i get a sliver of the progress bar, and in the upper top left some red text that's very difficult to read, but it says something like:
START [ZZ4.1440]
SV REV. CHECK FAIL : found : 4 . Binary : 1
It says all that in red... i have a suspicion THAT is the problem (my phone) and not Odin.
Any help on this would be appreciated, as this is a WORK phone that i need to get the new number ported to before i give it back to my work! LOL
Thanks in advance.
(After previewing my post in the forum.... WOW that's an OLD signature! LOL please disregard the sig info!)
You're trying to Odin an outdated tar. Go to www.sammobile.com and download the NG2.tar.
Thank You! That worked.
I was under the impression that i had to go back to an older version, then update to the latest version. <Shrug>
Anyhow, the first flash went to about 97,98%, then failed. I cleared everything i was doing on the computer (I was running 6 instances of an MMO i play at the same time on the one computer, plus some other stuff that was taxing my computer), RE-Flashed in ODIN, successful Flash. First boot hung at yellow sprint screen. I Pulled the battery, cleared cache, reset (in recovery), and it was a Success! So again, thank you kindly, i knew i just needed a nudge in the right direction. =)
CASE CLOSED. Heh.
Related
Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?
Your on the mf3 firmware. Odin won't work. I can tell because of the "fused 2" in the Odin printout
Thanks. Is there a way to unroot it?
tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Can you boot now? If you can unroot in super su.
tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Yes there is, I'm guessing you are able to boot to your phone?
Here's a link and instructions you can follow. Good luck and report to us how it goes
http://forum.xda-developers.com/showthread.php?p=45340743#post45340743
It worked! Thanks JD and haremmon. I feel like an idiot for not seeing that thread.
I need some help please?
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.
markdthor28 said:
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.
Click to expand...
Click to collapse
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.
h11wiscan said:
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.
Click to expand...
Click to collapse
At this point, I don't know if you'd be able to fix it that way. The only option that many users have been doing is going to best buy with a Samsung experience area and having them reflash the MF3 firmware.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
tcow24 said:
Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?
Click to expand...
Click to collapse
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.
srikanthkata said:
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.
Click to expand...
Click to collapse
Not trying to be rude but please go post this question under the GS3 forum. The GS3 forum can be found here http://forum.xda-developers.com/galaxy-s3
Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
MrBrickedPhone said:
Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Click to expand...
Click to collapse
Go to this website
You will learn how to unbrick your soft bricked s4
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Lalssa said:
Go to this website
You will learn how to unbrick your soft bricked s4
Click to expand...
Click to collapse
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
MrBrickedPhone said:
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
Click to expand...
Click to collapse
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html
If didnt work try again
angus_mcfisher said:
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
MrBrickedPhone said:
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
Click to expand...
Click to collapse
Download another version of odin
Lalssa said:
Download another version of odin
Click to expand...
Click to collapse
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
MrBrickedPhone said:
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
Click to expand...
Click to collapse
Try flashing using heimdall you can find some interesting tutorials if you google it
Lalssa said:
Try flashing using heimdall you can find some interesting tutorials if you google it
Click to expand...
Click to collapse
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
MrBrickedPhone said:
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
Click to expand...
Click to collapse
Using Heimdall:
As with ODIN, writing the PIT is completed.
Alas, Heimdall cannot write ANY partitions from the extracted .tar files from the GT-I9505-Factory-Firmware-Full-Wipe-DBT ROM.
It does seem that the flash memory is write protected - it certainly cannot be written to.
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Obagleyfreer said:
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for taking the time to provide the advice, I've tried flashing PhilZ recovery via ODIN and it tells me it has been successful, however when i try to boot into recovery it appears it's not flashed at all as I get stuck on the previous recovery TeamWin loading screen - it looks as if the nand maybe corrupted after all.
chickentuna said:
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Click to expand...
Click to collapse
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
MrBrickedPhone said:
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
Click to expand...
Click to collapse
Damn that's quite unfortunate. Sorry mate, I'm out of ideas. I wouldn't actually advise to hard brick the phone intentionally because as far as I know there's still hope as you can still access download mode.
Well if you can't really flash anything it's probably best to just hard brick the phone to the point that the Samsung guys wouldn't be able to revive it then send the phone for repairs than having to send it in it's current state because they'll most likely find out that you've modified your phone. Again I strongly suggest not to do it.
Good luck. Hope you fix it soon buddy.
Sent from my GT-I9505 using Tapatalk 4
Download Kies and install samsung drivers with it. Click on tools tab and click emergency firmware restore. Type in your phone model e.g GT-I9505 and then type in your Serial Number (can be found in the battery compartment of the phone) Kies will then ask you to go to download mode and then it will start downloading firmware and installing it on your device.
The write protection enabled message suggests to me that you've previously had one of the stock firmwares with the new bootloader. Have you had MH8 on there?
If you're desperate you could always try flashing MH8 firmware. The new bootloader won't let you downgrade to an older firmware giving a message as above.
Sent from my GT-I9505 using Tapatalk 4
Had this issue
Hey There, i had this issue last night infact, i had bricked my phone, recovery not accessible and download mode only possible by plugging it in and then starting it, try this put your phone into download mode, via plugging it in then turning it on, when it is in download mode flash PhilZ recovery via the PDA option then turn it off after flashing by taking out the battery (after it has rebooted and flashed), then plug it in again, launch into recovery and wipe/format etc.. install a new MH8 stock firmware (with the new bootloader) then you should be okay.
It should be noted that i did these step and it worked, except i didn't ever install a new rom and kept stock and i used a nandroid backup instead of installing the stock rom
You say twrp logo shows up. Does it start adb ? Maybe u can remount partitions as RW with terminal . manually wipe it. And then try adb sideload to install a .zip
All I can think of as every other suggestions seem to have been mentioned.
Sent from my GT-I9505G using xda app-developers app
I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? I'm getting kind of desperate.
Have you tried another USB cable?.
I have actually. The original cable and just another one I had. Also, tried it on 3 computers.
Should I be loading a PIT file? some places say to do it and others say not to.
marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
You are freaking amazing. That file totally worked. Thanks so much.
marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app
Device: AT&T Galaxy S5 OS 4.4.2 (carrier locked)
Background: Applied AT&T OTA 4.4.4 update (device showed it available from AT&T), once update finished applying the device couldn't connect to AT&T mobile data (WiFi worked and incoming/outgoing calls worked). I tried several different troubleshooting methods and ended up doing a factory reset. This didn't resolve issues. So I tried flashing the ROM; this is where things took a massive turn south.
Issue: Device boots to Samsung logo and hangs (logo partially loads before hanging). I can get to recovery and to download mode for Odin. I've used the following guides for flashing: (I don't have enough posts to set links so I posed them below)
galaxys5root(.)com - Downloaded flashing files and Odin twice to ensure no issues. Got the same result flashing all of these. I couldn't flash blootloader, I assume because it is still locked.
galaxys5update(.)com - I used this guide with files from sammobile(.)com for "AP" on Odin. I'm currently downloading the files hosted on GalaxyS5Update's guide, but I still have another few hours before they finish.
This isn't my first go around with flashing ROMs on Android, however it is my first try with locked Samsung phones (I've always used Nexus devices prior to this).
I'm at a loss where go go from here. I'm not sure exactly what I'm doing wrong nor am I sure where to look to move forward.
I appreciate any help anyone can provide. Let me know if I didn't provide enough information or wasn't clear enough.
Thanks!
J
Just in case the links don't work:
Guide 1 - galaxys5root(.)com/galaxy-s5-unroot/how-to-unroot-galaxy-s5-with-odin-and-stock-firmware/
Guide 2 - galaxys5update(.)com/unbrick-att-galaxy-s5-sm-g900a-soft-brick-fix-restore-to-stock-firmware/
SamMobile - sammobile(.)com/firmwares/download/28224/G900AUCU1ANCE_G900AATT1ANCE_ATT/
Quick update. The download I referenced waiting on in my original post finished and I tried the flash again.
Screenshot of Odin: imgur.com/XaUWQ1V,Tz0EjvM
Image of Odin Mode on Phone: imgur.com/XaUWQ1V,Tz0EjvM#1
Below is the output from Odin:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
jharder01 said:
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
Click to expand...
Click to collapse
Try to do Factory Reset after flashing firmware dedicated to your phone?
To do this - flash STOCK firmware via ODIN again allow auto reboot and ahone get into bootloop again - pull out battery.
Then wait 30 seconds and enter to STOCK recovery - VOL+ + HOME + POWER (Almost the same like download mode but instead vol- is vol+) and do format data and format cache few times.
Try to boot it up, if not work and phone will get into bootloop again, flash stock firmware and try.
jharder01 said:
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
Click to expand...
Click to collapse
Please check the att s5 general section, there are threads with files and instrctions.
Sent from my SM-G900A using Tapatalk
qubbus said:
Try to do Factory Reset after flashing firmware dedicated to your phone?
To do this - flash STOCK firmware via ODIN again allow auto reboot and ahone get into bootloop again - pull out battery.
Then wait 30 seconds and enter to STOCK recovery - VOL+ + HOME + POWER (Almost the same like download mode but instead vol- is vol+) and do format data and format cache few times.
Try to boot it up, if not work and phone will get into bootloop again, flash stock firmware and try.
Click to expand...
Click to collapse
Qubbus,
I tried the same thing minus multiple formats after imaging before. Today, I ran Odin, let it run all its processes until it froze again, then I went into recovery and formatted data and cache both 3 times. Still seeing the same issues however
Thanks for the suggestion though! I feel like I'm one mistake/step from a working phone.
Rakuu said:
Please check the att s5 general section, there are threads with files and instrctions.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I checked around, and didn't see anything for the AT&T variant. Seems most people are posting about F or H models unfortunately.
jharder01 said:
I checked around, and didn't see anything for the AT&T variant. Seems most people are posting about F or H models unfortunately.
Click to expand...
Click to collapse
There is a section specifically for the at&t variant http://forum.xda-developers.com/att-galaxy-s5/general
Sent from my SM-G900A using Tapatalk
Still locked
I'm having the same issue - exactly as defined here... and have tried the same things outlined here and have not resolved my issue. Any progress or success out there??? I've been reading/searching for several weeks now and haven't found a solution yet.
Update: FIGURES - I wait and search for two weeks on a fix... post a message and within 20 minutes, actually find the answer!
HERE is what fixed it for me (for anyone else having this problem):
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
(I had already tried a different Downgrade to NCE file as archie87 wrote in the above - but this one actually worked for me!)
Hi!
!Total Newbie Alert!
I have a Galaxy S5 Active, SM-G870W. It was with Bell, but I unlocked and have been using another provider for some time now. I recently needed to install an app that needs root access, and figured I would be able to do the same.
In the distant past I had rooted some ancient android devices, so I read a bunch of pages, and feeling far too confident I pulled the trigger and tried to root my phone using the CF-Auto-Root tool from the firmware dot mobi website.
I entered SM-G870W, selected the only device option, hit Submit, Selected Android 6.0.1 (Build MMB29M.G870WVLU1CPF6), and continued to download a file:
cfar_samsung_sm-g870w_kltevlactive_mmb29m.g870wvlu1cpf6_t0.zip
I Extracted then launched the root.bat batch file, Odin Launched (Ver 3.12), I pick the AP as specified, and I get the following:
<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 engine v(ID:3.1203)..
<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> recovery.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone stays at "Downloading... Do not turn off target!!"
I pulled the battery and rebooted into download mode again (Vol Down/Home/Power) and retried with the same file, and the same results.
I also tried powering up in recovery (Vol Up/Home/Power), but I get a message
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
Click to expand...
Click to collapse
At this point I am trying to get my device at least usable, I can restart in download mode no issue, but even after regenerating and redownloading, I am not able to get past this error.
I spent the last 6 or so hours going over posts here and elsewhere, with no luck, I tried Kies (Version 3.2.16084_2) and it says "The connected device is not supported by Kies 3" and the link to view supported devices on Samsungs site does not lead to any information. I also read somewhere that you can't root Android 6 images, but that post was 2014, and I found contradicting information elsewhere.
I would appreciate help on where to go from here, my priority is getting the phone working, rooted or not.
Thanks in advance!