Develop Bugs

Accidental Double Install of AOKP M1

Hi,
I tried searching the forums for this but could not find an answer. I had just installed Milestone 1 for AOKP. I was in the process of flashing Franco Milestone 6 when I accidentally flashed AOKP Milestone 1 again. (yes, i wasn't paying attention). Now, phone is stuck in a loop at the AOKP boot screen.
I tried using ADB but no device is recognized. If I try to Volume Down/Power, I get stuck in an ODIN page where all I can click on is Start, which throws me in the loop again.
I found posts that said flashing a rom without wiping should not cause issues so am at a loss at what to do.
Hope I can get some help!
Thanks,
Marc
Note: I actually just got a new GN this AM because my old GN (with LiquidSmooth and Franco kernel) finally decided to stop working after a nasty fall.

lestat832 said:
Hi,
I tried searching the forums for this but could not find an answer. I had just installed Milestone 1 for AOKP. I was in the process of flashing Franco Milestone 6 when I accidentally flashed AOKP Milestone 1 again. (yes, i wasn't paying attention). Now, phone is stuck in a loop at the AOKP boot screen.
I tried using ADB but no device is recognized. If I try to Volume Down/Power, I get stuck in an ODIN page where all I can click on is Start, which throws me in the loop again.
I found posts that said flashing a rom without wiping should not cause issues so am at a loss at what to do.
Hope I can get some help!
Thanks,
Marc
Note: I actually just got a new GN this AM because my old GN (with LiquidSmooth and Franco kernel) finally decided to stop working after a nasty fall.
Click to expand...
Click to collapse
yeah reflashing rom should cause that...if you can get to odin maybe try to odin the stock tar or if you can get to fastboot flash the factory image in fastboot mode, and adb is probably not getting recognized cuz you have usb debugging off

nvm

Just reflash another rom.
Data pull using ADB if necessary.

Just tried Odin3 1.3 and it failed (http://forum.xda-developers.com/showthread.php?t=1426207). Also tried this (http://www.galaxynexusforum.com/for...how-return-stock-using-odin-vzw-lte-only.html) and failed.
Do I need to use the latest Odin. Also, not sure if those were the latest TAR files.
I cant flash other ROMs because I'm stuck in a loop and can't get into recovery or use fastboot.

lestat832 said:
Just tried Odin3 1.3 and it failed (http://forum.xda-developers.com/showthread.php?t=1426207). Also tried this (http://www.galaxynexusforum.com/for...how-return-stock-using-odin-vzw-lte-only.html) and failed.
Do I need to use the latest Odin. Also, not sure if those were the latest TAR files.
I cant flash other ROMs because I'm stuck in a loop and can't get into recovery or use fastboot.
Click to expand...
Click to collapse
Volume up and volume down plus power button...
You do not need Odin and double flashing a rom will not cause a bout loop
Sent from my Galaxy Nexus

Pirateghost said:
Volume up and volume down plus power button...
You do not need Odin and double flashing a rom will not cause a bout loop
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Unfortunately, when I do "Volume Up/Down + Power," I still get the 3 image icons (phone, yellow flag with exclamation and monitor).
Just FYI, I tried this ODIN method (and still failed): http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> bootloader.img
<ID:0/008> radio.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!

[Q] Bricked and tips aren't working so far. Help, please!

Well, dang... I've tried everything I can think of and am stuck. If any of you have suggestions, I'll be forever in your debt.
So I was trying out a few ROMS on my I747. The last working one I had was LiquidSmooth Android (v2.1 I believe) but it was rebooting on me more often than I'd like, so I tried booting into TWRP to restore my last Nandroid of the rooted stock ROM I had been running fine. I know that Nandroid backup was a good one because I have restored it before. So anyway, I boot into TWRP and suddenly TWRP asks me for a password, which it has never done before. It almost looked like TWRP thought my device was encrypted, which it wasn't. But then when I hit "cancel" and tried to use the TWRP Factory Reset wipe, all of the attempts to mount the partitions failed! So I decided to let TWRP reboot the device, thinking something weird was going on with TWRP that would be fixed the next time I loaded it (DOH!) and I've been hosed ever since.
I am in a stange position with my I747 now. The OS won't boot at all. It forces the phone to try to boot into recovery, which is the latest TWRP. Unfortunately that just hangs at the "teamwin" screen and never goes on. First thing I decided to try was to flash a fresh TWRP thinking my TWRP had gotten mucked up. When got the latest TWRP tar from your Toolkit "recovery" folder (I am a donator from a day or two ago) it looked like it successfully flashed the TWRP to the phone, although I'm a bit worried maybe I don't understand Odin's output. Here is what it shows when I flash the TWRP:
------
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
------
The phone reboots like the re-write of TWRP was successful, but then it just hangs at the "teamwin" screen again. So then I thought I'd try flashing CWM instead.. The output from ODIN looks basically the same, but when I reboot into recovery I again am stuck at the "teamwin" screen from TWRP! WTH?
Why am I still seeing the "teamwin" screen if I just flashed CWM and Odin says it succeeded? I'm guessing it has something to do with the "RQT CLOSE !!" line in the log above. Is that actually a failure message that I thought was a success message? It isn't real clear..
So then my last fall back was just to flash the whole stock ROM again. Sadly, that didn't seem to work either. It actually gives me a WRITE (Fail!) message. Here is the output of Odin when trying to write the stock ROM to the phone in Download mode. I'm trying to flash the files called "I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5".
----
Code:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
----
As you can see, the MD5 checks passed with no problems, but the actual writing of the code to the NAND fails immediately. At this point I have no idea what to try next.
And for the record, I also tried flashing back the original boot image from your Toolkit called "boot-stock-dlk3-SGHI747.tar". Here is what I get when I try to flash that with Odin.
----
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
-----
Any suggestions anyone might have for what to do next would be most appreciated. Sadly, this is my only phone, and my employer pays for it. I need to get it up and running as soon as I can, if it is possible. Probably shouldn't have been messing with it in the first place, but I'm a tinkerer at heart.. What can I say?
Thanks for taking the time to read this and thanks for any tips any of you can share!!
MrSimmonsSr

Are you using the automated process from the toolkit?
Try using odin alone and flashing back to stock
http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/

MrSimmonsSr said:
Well, dang... I've tried everything I can think of and am stuck. If any of you have suggestions, I'll be forever in your debt.
So I was trying out a few ROMS on my I747. The last working one I had was LiquidSmooth Android (v2.1 I believe) but it was rebooting on me more often than I'd like, so I tried booting into TWRP to restore my last Nandroid of the rooted stock ROM I had been running fine. I know that Nandroid backup was a good one because I have restored it before. So anyway, I boot into TWRP and suddenly TWRP asks me for a password, which it has never done before. It almost looked like TWRP thought my device was encrypted, which it wasn't. But then when I hit "cancel" and tried to use the TWRP Factory Reset wipe, all of the attempts to mount the partitions failed! So I decided to let TWRP reboot the device, thinking something weird was going on with TWRP that would be fixed the next time I loaded it (DOH!) and I've been hosed ever since.
I am in a stange position with my I747 now. The OS won't boot at all. It forces the phone to try to boot into recovery, which is the latest TWRP. Unfortunately that just hangs at the "teamwin" screen and never goes on. First thing I decided to try was to flash a fresh TWRP thinking my TWRP had gotten mucked up. When got the latest TWRP tar from your Toolkit "recovery" folder (I am a donator from a day or two ago) it looked like it successfully flashed the TWRP to the phone, although I'm a bit worried maybe I don't understand Odin's output. Here is what it shows when I flash the TWRP:
------
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
------
The phone reboots like the re-write of TWRP was successful, but then it just hangs at the "teamwin" screen again. So then I thought I'd try flashing CWM instead.. The output from ODIN looks basically the same, but when I reboot into recovery I again am stuck at the "teamwin" screen from TWRP! WTH?
Why am I still seeing the "teamwin" screen if I just flashed CWM and Odin says it succeeded? I'm guessing it has something to do with the "RQT CLOSE !!" line in the log above. Is that actually a failure message that I thought was a success message? It isn't real clear..
So then my last fall back was just to flash the whole stock ROM again. Sadly, that didn't seem to work either. It actually gives me a WRITE (Fail!) message. Here is the output of Odin when trying to write the stock ROM to the phone in Download mode. I'm trying to flash the files called "I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5".
----
Code:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
----
As you can see, the MD5 checks passed with no problems, but the actual writing of the code to the NAND fails immediately. At this point I have no idea what to try next.
And for the record, I also tried flashing back the original boot image from your Toolkit called "boot-stock-dlk3-SGHI747.tar". Here is what I get when I try to flash that with Odin.
----
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
-----
Any suggestions anyone might have for what to do next would be most appreciated. Sadly, this is my only phone, and my employer pays for it. I need to get it up and running as soon as I can, if it is possible. Probably shouldn't have been messing with it in the first place, but I'm a tinkerer at heart.. What can I say?
Thanks for taking the time to read this and thanks for any tips any of you can share!!
MrSimmonsSr
Click to expand...
Click to collapse
Flash a rooted stock Rom and reinstall recovery. I would recommend using root66 rooted stock by mr. Robinson.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Or rooted stock...I have had luck in the past going to pure stock and starting over. When your restored use the beginners guide to rooting in the general section. Once root is achieved....use the goo.im app to install most current version of TWRP.
Sent from my SGH-I747 using XDA premium

Sorry for not being more clear.. I was using the various tar files, and the Odin exe file from the Toolkit, but I was using them on their own. I would go into the Toolkit install folder and crank of Odin binary by itself, outside of the other tools..
And when I tried flashing a Stock ROM, it would give me the "WRITE (FAIL!)" error.. When I tried re-flashing any recovery, CWM or TWRP, it would say success but when I booted into recovery it would always be TWRP and it would always freeze at the "teamwin" screen and never get past it.
Thoughts?
Thanks!
thegodsquirrel said:
Are you using the automated process from the toolkit?
Try using odin alone and flashing back to stock
http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
Click to expand...
Click to collapse

dima470 said:
Flash a rooted stock Rom and reinstall recovery. I would recommend using root66 rooted stock by mr. Robinson.
Click to expand...
Click to collapse
If you read my post again you will see that I have tried both flashing a stock ROM (non-rooted, got a WRITE error) and flashing a recovery (seems to be successful, but doesn't actually change the recovery on my phone), and neither seem to be working.
Is there any way you guys know of to get passed the messages I'm seeing in ODIN?
Thanks! Much appreciate you guys taking the time to respond!
MrSimmonsSr

MrSimmonsSr said:
Sorry for not being more clear.. I was using the various tar files, and the Odin exe file from the Toolkit, but I was using them on their own. I would go into the Toolkit install folder and crank of Odin binary by itself, outside of the other tools..
And when I tried flashing a Stock ROM, it would give me the "WRITE (FAIL!)" error.. When I tried re-flashing any recovery, CWM or TWRP, it would say success but when I booted into recovery it would always be TWRP and it would always freeze at the "teamwin" screen and never get past it.
Thoughts?
Thanks!
Click to expand...
Click to collapse
I would bet it is a case of goofy android device hijinks. If you have another cord use that (this has worked for me in the past). Use that tutorial I linked and see if you can get it back to stock stock stock.
Sent from my SGH-I747 using xda premium

thegodsquirrel said:
Or rooted stock...I have had luck in the past going to pure stock and starting over. When your restored use the beginners guide to rooting in the general section. Once root is achieved....use the goo.im app to install most current version of TWRP.
Click to expand...
Click to collapse
You are right and I don't mind going back to stock ROM at all. I downloaded the stock ROM and tried to flash it with ODIN directly. As you will see in my original post, I got a message from ODIN saying the NAND write had failed.. No idea why! That is why I'm stuck and not sure what to try next.
I have a good Nandroid backup that I could restore if I just had access to TWRP, but it seems hosed up and won't get past the "teamwin" screen, but when I try to reflash TWRP, or CWM Recovery for that matter, it looks like ODIN says it was successful but I always end up stuck right back at that teamwin screen. Even after I just flashed CWM Recovery!! So something isn't right.
Any other ideas?

I don't think you are going to get back in to the recovery. Pull the battery and sim. Let it sit for a while. Did you go and download the tar from link I provided? It could be that the one you have is corrupted. I dunno. Good news is you are not bricked, just soft bricked. We just need the right combo to get it back into the os. It sounds stupid but try another USB cable if you have one.
Sent from my SGH-I747 using xda premium

I have tried multiple USB cables but that didn't help. The tutorial you linked was actually what I was reading last night to try to fix this myself without bothering anyone here. Unfortunately I get down to step 11 and that is where the problem happens. Odin gives me the output in my oringinal message and tells me the stock ROM could not be written to the NAND. That is why I'm stuck. If you look at my original post, it is in the second quote of ODIN output, and it says:
Code:
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
I always thought if I could get back to download mode, I'd be able to recover, but unless I can figure out why ODIN can't write the stock ROM to my NAND, I do not know what to try next..
Thanks! Any other ideas?
MrSimmonsSr
thegodsquirrel said:
I would bet it is a case of goofy android device hijinks. If you have another cord use that (this has worked for me in the past). Use that tutorial I linked and see if you can get it back to stock stock stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Son of *****...well if you haven't tried it yet pull battery and sim. Let it sit for an hour
Sent from my SGH-I747 using xda premium

I did download the same Stock ROM referenced and that is what I've been trying to load. The TAR file seems fine because ODIN says it passes the MD5 checks before it tries to flash it. I have tried it after pulling the battery for a while. Will pull the SIM also, just in case..
Thoughts?
thegodsquirrel said:
I don't think you are going to get back in to the recovery. Pull the battery and sim. Let it sit for a while. Did you go and download the tar from link I provided? It could be that the one you have is corrupted. I dunno. Good news is you are not bricked, just soft bricked. We just need the right combo to get it back into the os. It sounds stupid but try another USB cable if you have one.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

For the record, here is a screenshot of what ODIN looks like when I try to flash the stock ROM..
I'm starting to wonder if I need to start using some of the other options in ODIN. Obviously need to understand what they do much better before I start trying things. I don't want to hard brick the device. At least I can still get into download mode at this point!
Any other suggestions? Thanks for the help!
MrSimmonsSr

Make sure you are using the stock usb cable that came with the phone. Most micro usb cables are 5 pin, whereas the GS3 has an 11 pin connector and usb cable.

suprtrukr425 said:
Make sure you are using the stock usb cable that came with the phone. Most micro usb cables are 5 pin, whereas the GS3 has an 11 pin connector and usb cable.
Click to expand...
Click to collapse
Hmm.. That is interesting. I don't know if I have the original cable or not. Is there a marking on the original that will let me know. I have some many USB cables laying around from Blackberries and other devices, I'm not sure which one is which anymore..
I have successfully flashed stuff with these cables before.. Thoughts?
Del

Unchecked auto reboot and f. Reset time. Let it sit. Then button combo into recovery.
Sent from my SGH-I747 using xda premium

Any time I try to go into recovery I just hang at the TWRP startup screen that says "teamwin".. Even after ODIN tells me "success" on flashing CWM Recovery!! Obviously the flashing of recovery isn't really working even though ODIN is telling me it is a success.
I'm starting to think I have NAND corruption and need to repartition. Does anyone know where to find a STOCK ROM file that is safe to use with the ODIN repartition option?
Thanks!
thegodsquirrel said:
Unchecked auto reboot and f. Reset time. Let it sit. Then button combo into recovery.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Edit: nm checked the setup looks good.
I wouldn't completely give up...yet. Are you using the stock cable?
Sent from my SGH-I747 using xda premium

I have so many microUSB cables lying around here from various devices (BB 9800, Playbook, etc..) I don't know which one is the one that came with the GS3 anymore. Is there a way to tell?
That having been said, aren't they all the same as long as they were made for data sync and power?
And I'm not giving up, I'm just pretty sure I am suffering from what I see referred to in other threads as NAND Corruption. I think I might need to re-partition in order to get it resolved. But in order to do that, of course, I need a good PIT file for my device. Anyone know where I can find a PIT file that is made for this phone (SGH-I747)? I'm not worried about loosing any data. I have a good Nandroid I know I can recover with if I can just get TWRP working again..
thegodsquirrel said:
I wouldn't completely give up...yet. Are you using the stock cable?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Yea...that's got to be it. Gs3 cable all black with a black shiny micro SD connector. Keep us up to date if you fix it.
Sent from my SGH-I747 using xda premium

[Q] Major issues flashing new ROM, help needed badly!

Hi.
First off, I've had my sgh-t999 since launch. I rooted it, and put TWRP recovery on it. I have used multiple roms over the past year with no problems at all.
I recently went to switch to a new rom. (new version of IOKP, upgrading from old infamous rom)
steps I took:
1. Placed rom on SD
2. Booted into Recovery
3. Wiped dalvik, and did full data wipe
4. flashed rom, success
5. Rom got stuck loading and wouldn't work.
Figured I needed to reinstall the rom, as this has happened to me before on previous phones.
6. Tried to reboot into recovery, Phone would not allow me to go into recovery, the blue text appeared at the top, but the phone would reboot itself after a second of the blue text leaving. (I tried adjusting the length of time I kept the buttons pressed down, both shorter and longer, to no avail.)
7. I looked up how to fix this. I used odin and the stock T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 to flash it back to stock.
8. The phone booted fine and I was back like normal. HOWEVER, I had no 4g, no wifi, my home button didn't work, and I had a lot of other errors.
9. I figured I should try to use a different stock rom, however ODIN began giving me error messages.
<ID:0/007> boot.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> recovery.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> system.img.ext4
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what USB port I use I get the same error. I even downloaded a .PIT file and tried to flash again. Same error message.
10. Now my phone is stuck. I cannot get into the phone, I cannot get into recovery, and when in download mode it reads "Firmware upgrade encountered an issue."
11. Kies doesn't even recognize my phone.
I am at a loss for what I need to do.
In case it helps my "download mode" screen says
sgh-t999
6 counts
binary:samsung official
status:custom
secureboot:enable
warranty bit:1
bootloader ap swerv: 1
Does anyone have any idea where I should go from here? I hate being stuck. I also use my phone for work, and am losing money the longer I go without it. If anyone can provide help, I would be forever grateful.

What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk

serio22 said:
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Stock 4.3: T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 was the file I had flashed. My phone booted up, but I had no 4g and no wifi. I hooked it up to odin again to reflash the same firmware, and my phone is now stuck at the black screen that says firmware update error.
Every time I use odin it returns an error no matter what stock firmware I try and use. I tried a .PIT file in combination with T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5, and it still returned an error.

[Q] Odin will not flash Galaxy S3

Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.

sdw8253 said:
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
First thing, most of the time we moderators don't have time to go through every thread and post on XDA. Rather than asking us to delete a post in an obscure thread we may not see it would be helpful to us if you report it. I'm mobile right now so I can't do it but please report the other thread and make your request in the report.
Second, Odin isn't working because you're on a new bootloader. This one-click comes with the newest. Try flashing it. http://forum.xda-developers.com/showthread.php?t=2755793
Good luck!

If you were on KitKat 4.4.2 nd8 and tried to Odin the mk3 stock tar you've probably bricked your phone. Once on the nd8 boot loader and modem you cannot revert to an older version.
Many devs have bricked there phone with the new nd8 build.
I know I haven't answered all your w
Questions but I hope I've helped you understand what happened.
Luckily for you @rwilco12 has a solution for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

FIXED!
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!

How do you force into download mode
badmojorayman said:
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
Click to expand...
Click to collapse

sparks.calvin said:
How do you force into download mode
Click to expand...
Click to collapse
Press and hold down Volume down and Home button.
While holding both the above keys press and hold the power button, then you will see the disclaimer.
Let go of all the buttons and press Volume up to accept the disclaimer.
The phone goes directly into ODIN/Download mode right after this. You will see a green droid which indicates you’re in ODIN/Download mode.

sdw8253 said:
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?

6th_Hokage said:
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
Click to expand...
Click to collapse
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.

sdw8253 said:
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
Click to expand...
Click to collapse
ohhh okay well that's good; you got it sorted out

SM-T210R Bricked; Odin won't work

Hello, I hope you are having a good day,
I have a SM-T210R (Galaxy Tab 3 WiFi) that is bricked. It was not leaving the "Galaxy Tab 3" screen at boot-up and I determined that it was bricked. I looked at other forums on fixing a bricked tablet with the stock ROM and they didn't work AFTER I attempted to use Odin when it disconnected. At first, it seemed like it was working in Odin, but it said that my device had disconnected in the middle of the operation. The message that it now displays after it turns on, says that there was an error in updating and that it needs to be updated with Kies (I have tried both the recovery and updating it. The connection screen on it just appears and disappears and it doesn't recognize the device in recovery.) Now, if it even gets to this point, I keep getting to "Write NAND start" and then it tells me that there was a write error. Is there any way that I could possibly fix my device? I am using Odin3 v1.85 and I have tried other versions too, but this was the recommended one. I also have to uninstall the device and disconnect it every time I try. The
It is an old device and there is not much point to fixing it. It would be nice if I could fix it, but I understand if it can't be fixed.
Thank you.
EDITED

freonman said:
Hello, I hope you are having a good day,
I have a SM-T210R (Galaxy Tab 3 WiFi) that is bricked. I looked at other forums on this topic and they didn't work AFTER I attempted to use Odin. At first, it seemed like it was working in Odin, but it said that my device had disconnected. Because of this, I keep getting to "Write NAND start" and then a write error. Is there any way that I could possibly fix my device? I am using Odin3 v1.85.
It is an old device and there is not much point to fixing it. It would be nice if I could fix it, but I understand if it can't be fixed.
Thank you.
Click to expand...
Click to collapse
Odin can be finicky. I suggest trying a different USB cable. Post back and let me know. Also, not sure what your initial problem was, but I did quite a bit of work on the 210R and quite a few people still tinker with them. We should be able to get you going as long as the hardware is still working properly.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
Odin can be finicky. I suggest trying a different USB cable. Post back and let me know. Also, not sure what your initial problem was, but I did quite a bit of work on the 210R and quite a few people still tinker with them. We should be able to get you going as long as the hardware is still working properly.
Click to expand...
Click to collapse
I have now tried multiple cables and computer ports and it did the same thing. Now, it says there is no PIT partition. I found one online and it does nothing.

I have something for you to try I just have to find it. In my time creating a custom ROM for this device I bricked it a bunch of times. I was always able to get it back though. One of the times it bricked it did exactly as you were describing. The kies software doesn't do anything anymore, but when the tab is on that screen ODIN will work. One of the times I bricked it, it was due to shrinking the system partition. When the partition was the incorrect size, stock ROM files would fail. I made a fix for it that saved me twice and might save you... But I have to see if I still have it. I think it's on my Google drive, though.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I have something for you to try I just have to find it. In my time creating a custom ROM for this device I bricked it a bunch of times. I was always able to get it back though. One of the times it bricked it did exactly as you were describing. The kies software doesn't do anything anymore, but when the tab is on that screen ODIN will work. One of the times I bricked it, it was due to shrinking the system partition. When the partition was the incorrect size, stock ROM files would fail. I made a fix for it that saved me twice and might save you... But I have to see if I still have it. I think it's on my Google drive, though.
Click to expand...
Click to collapse
Thank you. I wish you luck!

I can't find the file I was looking for, but I think if you flash TWRP through Odin and then boot into TWRP we can fix it. I'll link the TWRP to try flashing with Odin.
TWRP
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
Report back and we'll keep going down the rabbit hole until we hit wonderland. If it successfully flashes TWRP you will have to hold vol+, power, and home until it goes off and into recovery.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I can't find the file I was looking for, but I think if you flash TWRP through Odin and then boot into TWRP we can fix it. I'll link the TWRP to try flashing with Odin.
TWRP
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
Report back and we'll keep going down the rabbit hole until we hit wonderland. If it successfully flashes TWRP you will have to hold vol-, power, and home until it goes off and into recovery.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I have to tell you, it now boots in ODIN mode every time, with this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Also, I tried the file in the BOOTLOADER and the PDA section and neither worked. Is there something I'm missing?
(This is the try in BOOTLOADER)
<ID:0/004> Added!!
<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> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)

freonman said:
I have to tell you, it now boots in ODIN mode every time, with this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Also, I tried the file in the BOOTLOADER and the PDA section and neither worked. Is there something I'm missing?
Click to expand...
Click to collapse
NVM had that backwards. I'm thinking of what to try next.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I'm not sure if this will actually help or not, but PDA was a slot in older versions of Odin. On the newer versions it is AP. Which version are you using? Maybe a newer version will pass.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I tried a newer version as well. ODIN3 V.1.85 is what I was recommended for KitKat.

What does it do when you have it powered off and use the button combination to try to get to recovery? (vol+, home, and power) Does it still just load to Odin? Also if you don't use any buttons and it goes into Odin, I think the drivers don't work right. Try using vol-, home, and power. It will still go into download mode, but it might allow Odin to see it correctly.
Sent from my LM-Q720 using Tapatalk

<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

RealWelder said:
What does it do when you have it powered off and use the button combination to try to get to recovery? (vol+, home, and power) Does it still just load to Odin? Also if you don't use any buttons and it goes into Odin, I think the drivers don't work right. Try using vol-, home, and power. It will still go into download mode, but it might allow Odin to see it correctly.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
It does the same "Firmware upgrade encounter an issue..." thing, whether or not I hold the ODIN mode buttons down. But, I got a new thing;
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It almost looked like it had worked. Do you have any ideas yet?

freonman said:
It does the same "Firmware upgrade encounter an issue..." thing, whether or not I hold the ODIN mode buttons down. But, I got a new thing;
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
recovery.img
NAND Write Start!!
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
It almost looked like it had worked. Do you have any ideas yet?
Click to expand...
Click to collapse
That does look like it almost worked. If we could get to TWRP or even get a rooted shell we could manually flash. Do you have adb and everything setup on your PC? If so try adb shell. If adb doesn't work I'd keep trying to flash the stock firmware and the TWRP back and forth. I feel like if I had it in front of me I could figure it out. Don't give up on it.
Also does it just have stock recovery?
Sent from my LM-Q720 using Tapatalk

RealWelder said:
That does look like it almost worked. If we could get to TWRP or even get a rooted shell we could manually flash. Do you have adb and everything setup on your PC? If so try adb shell. If adb doesn't work I'd keep trying to flash the stock firmware and the TWRP back and forth. I feel like if I had it in front of me I could figure it out. Don't give up on it.
Also does it just have stock recovery?
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I have ADB setup on my computer, but there are no "List of devices attached".
And yes, it does have the stock recovery.

Picture for visualization
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

freonman said:
I have ADB setup on my computer, but there are no "List of devices attached".
And yes, it does have the stock recovery.
Click to expand...
Click to collapse
I just had thought. Which firmware are you trying to flash? This device originally came with JB but got a KK upgrade. When it did the bootloader also got updated. You might try flashing stock 4.2 and see if it will pass. If it does then you can upgrade to 4.4. A few people ran into issues flashing my ROM because they were still on the old bootloader.
Also, I'll link my ROM's thread and you can post your issue there also. There's quite a few people that follow my thread and they might be able to help. I haven't messed with the device in 2 years and I forget a lot of the intimate details.
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-release-t210r-t3510449/amp/
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I just had thought. Which firmware are you trying to flash? This device originally came with JB but got a KK upgrade. When it did the bootloader also got updated. You might try flashing stock 4.2 and see if it will pass. If it does then you can upgrade to 4.4. A few people ran into issues flashing my ROM because they were still on the old bootloader.
Also, I'll link my ROM's thread and you can post your issue there also. There's quite a few people that follow my thread and they might be able to help. I haven't messed with the device in 2 years and I forget a lot of the intimate details.
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-release-t210r-t3510449/amp/
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I can't find a JB tar.md5 file for it. I tried to convert a .img file that was JB to tar.md5, and that didn't work. It did the same exact thing as the TWRP and the KK tar.md5.