Hey everyone.
I'm helping fix my friend's GS3 (SGH-i747). He said that he ran out of battery, and then went into a bootloop. He's running on one of the CM Nightlies from a while back.
We've tried to wipe cache, dalvik cache, factory reset, etc, but nothing works because internal storage fails to mount. I've tried flashing stock via Odin, but with no success. When I flash a recovery however, it says it was successful but when I boot into the phone, I still have the old recovery.
The phone is on TWRP. When I go into "mount", internal storage is shown having 0mb. I cannot click on anything else (data, cache, etc) except system and external sd card (when it is present).
I've tried flashing the CM zip that was on the external SD card but had no success either.
No idea what to do from here. Any help would be appreciated. Thanks!
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
!
audit13 said:
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
Click to expand...
Click to collapse
I get "NAND WRITE START!!" and then FAIL. It shows that the phone is connected to my PC. I've tried flashing CWM. It says it's successful, but when I boot into recovery, the recovery is still TWRP.
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
audit13 said:
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
Click to expand...
Click to collapse
I kinda figured that too. I tried flashing a pit file for the sgh-i747 16gb alongside a stock ROM but nothing happened. How should I go about finding one for the phone?
Btw, the internal storage was already at 0mb before I tried flashing a pit file.
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I'd try it but I don't have access to a 16GB or higher SD card. How do I go about getting a pit file for the phone?
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Thanks for the link. To be sure, I flash this along with a stock rom right? Is there a specific stock rom that I have to use? I got one from Sam Mobile.
audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Here's the log in Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
That's what I usually get.
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
audit13 said:
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
Click to expand...
Click to collapse
Should I flash stock 4.3 then? Unless this phone has Kit Kat (I think the CM version my friend was using is Kit Kat)
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Pretty sure that I had put Stock 4.3 at one point. Thanks for the info, I'll try finding a stock 4.3 for Odin and report back.
audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Okay so I tried flashing stock 4.3 and Odin fails at system.img.ext4
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I747UCUEMJB_2024954_REV04_user_low_ship.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
I got the stock 4.3 from here: http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/
I tried the .pit file included in that as well as the .pit file from the other thread you linked.
Also, the phone was on CM11 4.4.2 before all of this happened. No idea if that makes a difference, but if I recall correctly, the phone did have stock 4.3 at one point.
If you manage to get the thing booted then you might want to run a memory test to see if all the nand is still good
Did you check re-partition?
audit13 said:
Did you check re-partition?
Click to expand...
Click to collapse
Yep
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
audit13 said:
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
Yep, I downloaded that exact one and I get the error. What should I do now?
Related
I downloaded 4.1.1 from Samsung-Updates.com and then extracted it and tried to flash it in Odin but the program is saying,
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is recognizing the phone and the drivers are installed. The phone, AT&T GS3 I747, is currently running Android 4.3 w/root and custom recovery. The phone is stock otherwise but it is failing for some reason.
***UPDATE*** I just found out from another thread that when you try to downgrade from 4.3 to 4.1.X it WILL BRICK. Dang you Samsung!! >=(
***UPDATE-2*** I would like to know if there's a fix or recovery method for this issue: can't flash ROMs, can't flash with Odin, stuck at AT&T logo, nandroid restore doesn't fix issues.
What I did to cause this issue:
1. Installed 4.3 OTA
2. flashed desamsungnizer knox removal
3. Try to flash 4.1.1 with Odin(failed)
4. reboot phone, stuck at AT&T logo.
5. restore nandroid, reboot, stuck at AT&T logo.
Nabbu said:
I downloaded 4.1.1 from Samsung-Updates.com and then extracted it and tried to flash it in Odin but the program is saying,
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is recognizing the phone and the drivers are installed. The phone, AT&T GS3 I747, is currently running Android 4.3 w/root and custom recovery. The phone is stock otherwise but it is failing for some reason. I'm trying to send it in for warranty for defective volume rockers and headphone jack so I need it stock asap any help is appreciated.
I just found out from another thread that when you try to downgrade from 4.3 to 4.1.X it WILL BRICK. Dang you Samsung!! >=(
Click to expand...
Click to collapse
did yu get it fixed cuz sammy is pulling alot of [email protected] with this 4.3 update for the S3
winosxbuntu said:
did yu get it fixed cuz sammy is pulling alot of [email protected] with this 4.3 update for the S3
Click to expand...
Click to collapse
Unfortunately I haven't found a fix for it and no one else seems to notice it except for the thread in General that says [WARNING].
I would like to know myself if someone knows why the phone boots up but is stuck at the AT&T logo and cannot flash ROMs or Odin files and that Nandroid restores don't fix the "damage".
Nabbu said:
Unfortunately I haven't found a fix for it and no one else seems to notice it except for the thread in General that says [WARNING].
I would like to know myself if someone knows why the phone boots up but is stuck at the AT&T logo and cannot flash ROMs or Odin files and that Nandroid restores don't fix the "damage".
Click to expand...
Click to collapse
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....
winosxbuntu said:
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....
Click to expand...
Click to collapse
I'll give it a shot and get back with you if my phone is revived. Thanks!
winosxbuntu said:
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....
Click to expand...
Click to collapse
You still cannot downgrade from 4.3 and you cannot flash 4.3 because the official software is not yet available, only the OTA patch.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
You still cannot downgrade from 4.3 and you cannot flash 4.3 because the official software is not yet available, only the OTA patch.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah I just figured that out but I was thinking of flashing a 4.3 custom rom or even 4.4 to see if it revives the phone.
I'm trying it today I'll update if it works.
Was able to restore 4.3 from SamMobile with Odin 3.09
I foolishly tried to downgrade from 4.3 OTA to 4.1.1 using Odin and bricked the device. After much testing, I was able to use Odin 3.09 and the 4.3 firmware posted on SamMobile (in my case the Rogers version). All other attempts with other versions led to the "Fail auth" in Odin.
Hope that helps some people who have bricked inadvertently.
sabrinaela said:
I foolishly tried to downgrade from 4.3 OTA to 4.1.1 using Odin and bricked the device. After much testing, I was able to use Odin 3.09 and the 4.3 firmware posted on SamMobile (in my case the Rogers version). All other attempts with other versions led to the "Fail auth" in Odin.
Hope that helps some people who have bricked inadvertently.
Click to expand...
Click to collapse
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it: http://forum.xda-developers.com/showthread.php?t=2539313
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.
Nabbu said:
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it: http://forum.xda-developers.com/showthread.php?t=2539313
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks for the log and instructions, this is helpful for anyone that has bricked their phones
Again thanks
Same issue, but my Note hasn't root
Nabbu said:
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it:
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.
Click to expand...
Click to collapse
Same issue, bricked my Note II after trying downgrade. Problem is that my Note wasn't rooted. So i guess trying to install TWRP will not work, right? Any ideas???
mikrax said:
Same issue, bricked my Note II after trying downgrade. Problem is that my Note wasn't rooted. So i guess trying to install TWRP will not work, right? Any ideas???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2549068
Thanks! Unbrick done!
BCSC said:
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Thanks i just fix my phone installing original firmware 4.3 from sammobile trough Odin. And it worked!
Ok so here is the situation. I have a GS3 i747. About a week ago it randomly shut off and entered a bootloader loop. I went into CWM and tried to flash to a new rom and I kept getting a Status 7 error. So I edited the ROM to not check for assets and I eventually got the ROM to install... Everything was going fine until last night. The phone entered another loop and this time when I go into CWM I get lots of errors...
E: can't mount /cache/ recovery/ command
E: can't mount /cache/ recovery/ log
E: cant open /cache/ recovery/ log
E: can't mount /cache/ recovery/ last_log
E: can't open /cache/ recovery/ last_log
E: can't mount /cache/ recovery/ last_install
E: can't open /cache/ recovery/ last_install
In addition I cannot mount cache or data but I can mount system.
When I try to install a ROM via CWM it gives a status 7 error even with I delete the assets.
When i try to flash using ODIN it gets to NAND write start --> failed
I did get a pass when I ran a new pit and re-partitioned however it didn't do anything on the phone (i'm not sure if i would notice a difference or not though.)
Oh and the download on the phone still lists the model number and everything, if that is helpful...
If anyone has any idea what I can do to fix this I would greatly appreciate it!
Status 7 error can happen if your recovery is out of date. If you are flashing KK ROMs, you need the latest CWM. I like Philz Touch which can be installed via Odin.
What error are you getting in Odin? If you have a 4.3 bootloader and you are trying to install a stock ROM, the stock ROM will try to downgrade the bootloader which may brick the phone. The AT&T 4.3 bootloader cannot be downgraded so do not attempt to flash with Odin until you confirm your bootloader version.
audit13 said:
Status 7 error can happen if your recovery is out of date. If you are flashing KK ROMs, you need the latest CWM. I like Philz Touch which can be installed via Odin.
What error are you getting in Odin? If you have a 4.3 bootloader and you are trying to install a stock ROM, the stock ROM will try to downgrade the bootloader which may brick the phone. The AT&T 4.3 bootloader cannot be downgraded so do not attempt to flash with Odin until you confirm your bootloader version.
Click to expand...
Click to collapse
I am on the latest CWM listed for my phone, 6.0.4.7 I believe. The last ROMs I had installed were KK and CM 11, which I assume means my bootloader is 4.4? All that is happening in Odin is when I try to flash a ROM it starts normal but once it gets to the "Nand Write start" part it says failed.
In addition if I try to flash CWM via Odin. It says passed, but I don't think it's actually changing. For example, i tried to change the CWM that i have which is the touch version into the non-touch version and it says passed but when I go onto the phone touch still works.
Flashing a 4.4 custom ROM does not update your bootloader.
Boot into download mode. What is shown on the download screen?
Did you select re-partition in Odin or just Auto-Reboot and F.Reset?
audit13 said:
Flashing a 4.4 custom ROM does not update your bootloader.
Boot into download mode. What is shown on the download screen?
Did you select re-partition in Odin or just Auto-Reboot and F.Reset?
Click to expand...
Click to collapse
Download mode says:
Odin mode
Product Name: SGH-I747
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: enable
and has the android icon in the middle. With "Downloading...Do not turn off target!!"
Only Auto-reboot and F. reset.
Based on the download screen, it does not look like you have the 4.3 bootloader.
Did you get the stock ROM from here: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269060210 ?
audit13 said:
Based on the download screen, it does not look like you have the 4.3 bootloader.
Did you get the stock ROM from here: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269060210 ?
Click to expand...
Click to collapse
No should I try to install that one?
I'm having the exact same issue, only I don't have a ROM on the device to try and install from CWRM. No luck loading the factory recovery with odin (says success, but still have CWRM). I can't see the phone with adb or fastboot either so I feel like I'm SOL. Hopefully someone knows a fix.
I was running CM11 before it quit working.
Similar problem. Was on 4.3 official then installed CM11 4.4.2. Now when trying to go back to 4.3, process fails using twrp or cwm. I also tried odin to flask the tmo 4.3 md5 file but it fails.
Please help.
ctbartolillo said:
No should I try to install that one?
Click to expand...
Click to collapse
Make sure you install the ROM that is for your carrier and phone.
audit13 said:
Make sure you install the ROM that is for your carrier and phone.
Click to expand...
Click to collapse
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
ctbartolillo said:
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
Click to expand...
Click to collapse
Is the phone an i747 from AT&T?
audit13 said:
Is the phone an i747 from AT&T?
Click to expand...
Click to collapse
Yes it is.
If you have the 4.3 att bootloader on your phone, you can't use Odin to flash a stock ROM.
ctbartolillo said:
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
Click to expand...
Click to collapse
Dude I am pretty much in the same situation. This thread is probably our only hope now.
http://forum.xda-developers.com/showthread.php?t=2658486
UPDATE: Tried today and worked perfectly!!!! Give it a shot.
Deleted.
I tried but it didn't work. I got Symlink: some symlinks failed, status 7
i have a Samsung S4 that i bought from a friend of mine couple weeks ago. It was working fine until recently it starting doing this:
https://www.youtube.com/watch?v=ZjJH...=youtu.be&hd=1
As you can see it boots up but doesnt go to the main screen and then restarts. I hard resetted it. I tried to install stock rom using odin but i get an error and it fails. Its a Samsung M919 from tmobile. I have no idea how to fix it. I tried different battery but same problem. I would really appreciate some help.
i downloaded the rom here: http://galaxys4root.com/galaxy-s4-stock-firmware/
this is the error i get with Odin. I tried different usb cables and computers but same error
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/017> Removed!!
Thanks
can somebody please help
You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.
PanchoPlanet said:
You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.
Click to expand...
Click to collapse
thx for your reply. So i got Odin 3.07. Is this stock rom u talking about: http://samsung-updates.com/device/?id=SGH-M919. So all i have to do open ODA and put this into PDA and start?
i thought stock meant going back to the origal firmware wht the phone came with which would be androind 4.2?
also is there a better download link where i dont have to wait 6 hours?
thx
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
whts the difference between NK2 and NH7?
thx for all your help so far
PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
it failed again.
i followed all your steps:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Where you able to do a factory reset?
Can you access recovery stock /custom?
What rom was running on phone before first flash attempt?
Was phone running properly when you got it?
You sure it's a t-mobile version M -919?
What color is the phone?
Pp.
PanchoPlanet said:
Where you able to do a factory reset?
YES
Can you access recovery stock /custom?
Not sure what you mean?
What rom was running on phone before first flash attempt?
I have no idea as i am not into flashing or installing "roms"
Was phone running properly when you got it?
Yes
You sure it's a t-mobile version M -919?
Yes as it says on the back of the phone
What color is the phone?
Black
Pp.
Click to expand...
Click to collapse
....
If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.
PanchoPlanet said:
If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.
Click to expand...
Click to collapse
I see stock recovery and i already tried wipe data/factory reset many times but same problem
So, I had flashed CM12 and was unable to send text messages.
> Wiped Data / Everything
> Opened ODIN
> Flashed Stock Note 4 Rom
> Fail right away.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any reason why ODIN would be failing to flash back to Stock?
My battery should be at least 60%+, I can enter download mode etc.
I'm just confused on whats going wrong.
Any help would be appreciated it.
Thank you.
Sorry but most likely you can't go back to KitKat. What is your current bootloader version?
You can still restore your CM backup or flash back and check it with Galaxy Tools or Phone Info in Google Play.
If bootloader is OE1 or higher, you might just as well Odin the OJ6 stock tar, wiping as you did, power down, pull battery minimum 30 seconds. Odin with latest 3.10.7 using default options.
BTW, there's usually a messaging fix posted in OP or nearby post by OP in CM threads.
Sent from my SM-N910P using Tapatalk
Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!
Rooness said:
Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!
Click to expand...
Click to collapse
I saw ANIE in the fail log you posted. That was the original Sprint Note 4 tar from KitKat.
Do you have the OJ6 full tar?
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
That tar should flash; wipe everything but extSdCard, power down, pull battery 30 seconds and boot into download mode using latest Odin defaults should do it.
Sent from my SM-N910P using Tapatalk
Oh thank you for noticing that!
Swore I was using the proper one.
That is probably why it was failing in the first place.
Downloading now and I'll try in the morning!
Thanks once again, I really appreciate the help.
NP. Verify the md5 against the zip and you should be fine.
Sent from my SM-N910P using Tapatalk
I have a Galaxy Note 2 SGH-T889. I have spent the past week reading and trying suggestions on this forum. I downloaded kies but it gets stuck connecting to the phone. I have tried several versions of odin. It gets to sboot.bin and write fails. I have tried the original firmware which took 2 hours to download. I refuse to pay for the upgrade in download speed for something I only need one time. I have tried the pit and firmware combination. The only thing that seem to register anything on the phone was when I tried the modem.bin.....it had a blue progress line but then it failed. I am starting to think it is a hardware problem.
How did it start? The phone was sitting on the desk when it came on and restarted. Then it stop when it got to the Galaxy Note II logo. I can get it into Download Custom OS mode but it will not go into recovery mode. Prior to that I had to data wipe and factory reset because it was having the logs process stopped and other processes popups. I had to wipe and reset about 3 times prior to the failure.
I was using the plain old firmware. I think the phone auto updated to the 4.3. I did not install any custom os. I just use the phone as a phone, the calendar and the camera pretty boring stuff. Did not know anything about odin, kies, soft brick, hard brick, jtag, emmc or sds prior to the failure. Not sure exactly what the difference is between t889, n7100, n7105 or n7108. I have downloaded the android toolkit and tried several of those options but it says to enable debugging but I have no access to the settings on the phone to enable debugging.
The way the phone crashed makes me think it had a hardware failure. If there is anything else I can try, I am willing to try anything.
Eva
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
andytiedye said:
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I am wondering if the phone was doing an auto update and got stuck in the process. I had my phone set to auto update. Maybe that is a mistake...I guess I should have made it ask before it updated at least then I would know what cause the problem.
Eva
Note 2 sgh-t889 boot.bin error
audit13 said:
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
zevacat said:
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
Click to expand...
Click to collapse
Ok it finished downloading. I ran it with odin 3.12. This is the results.
<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> Added!!
<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> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
audit13 said:
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
Click to expand...
Click to collapse
That try was with the odin 3.12 using the ap slot. I did try 3.07 pda and the 1.87. Yes it is a a tar.md5 file.
Had an interesting occurrence. I restarted the laptop while the phone was connected to the laptop and the laptop went into an infinite start loop. At first I thought, oh great now the laptop is broken....:crying: But then I unplug the phone and the usb cable. The laptop started normal. I plugged the cable in and it still restarted without problem so whatever black hole the phone is in....it will pull in all connected device into the abyss.
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
audit13 said:
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
Click to expand...
Click to collapse
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
I recommend flashing the most recently released stock rom, not earlier releases.
zevacat said:
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
Click to expand...
Click to collapse
I can't seem to find an earlier versions all the 4.1. All the links come back as file not found. They did have a gt n7100 unbranded 4.4.2 kit kat N7100_ITV_N7100XXUFOE1_N7100ITVFOF1.zip so I am waiting for it to download. It says it will take about 2 hours. Or is there some other version that would be better? and where can I find it. Rapid Gator really stinks as far as downloads.
Eva
Flash the latest 4.4. Try updato.com.
audit13 said:
Flash the latest 4.4. Try updato.com.
Click to expand...
Click to collapse
They don't have a 4.4 for the sgh-t889 so which one would work best out of the other options 7100, 7105 or 7108?
Eva
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
audit13 said:
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
Click to expand...
Click to collapse
4.3 gets stuck after the sboot.bin. audit13 said "the bootloader in the ROM is not compatible with the phone "....so if the bootloader in the sgh-t889 is not compatible then I need a different bootloader don't I? Not sure where to find a different bootloader.
Eva
The only thing I can suggest is taking it to a cell shop that can flash it via jtag.