I was running Cyanogen Mod on my phone, but my camera was acting odd, so I decide to flash back to stock to see if this would fix the issue.
I downloaded a stock firmware, and went through the steps to flash my phone. It seemed to work, but after completion, my went into a reboot loop.
When I try to flash again, i get the following output from odin
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Download mode screen reads the following:
ODIN MOde
PRODUCT NAME: SCH-I605
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
RP SWREV: A3
I tried this with a few firmwares, and a few versions of ODIN. I can get into download mode, but holding power, menu and volume up won't get me into recovery mode.
Did I just kill my phone?
I wanted to add a small tidbit. Could a reboot loop, and the error in ODIN be caused by a low battery?
I managed to make progress, but I am not quite there yet.
I flashed the PIT file from here downloadandroidrom [dot] com/file/GalaxyNote2/rooting/GalaxyNote2UnlockVerizon.zip (sorry, can't post a real link yet)
And after that, I was able to get past the failed step, and ODIN actually completed. However, right now, when I try to turn on my phone, nothing happens. When it's plugged in, it's just showing the battery icon, and the charging light is not on.
I ordered an external battery charger from eBay, to make sure that I have a full battery, but is there anything else I can do in the meantime?
EDIT:
I managed to fix it. Flashing the PIT file, and then flashing an official firmware did the trick. I think the first ROM that I tried was the problem.
Related
Model: SGH-T999V (Wind Mobile)
Firmware Rom: Cyanogenmod 10.1.3 (IIRC, might have been 10.1.2)
So, last night I plugged my phone in to my computer to charge. I walked away to do some other things, and when I came back a few minutes later I found it rebooting, or at least trying to. It seemed to be stuck in a loop. It would vibrate and show the Samsung logo, and then show the model logo (in my case "Samsung Galaxy SIII" with the cyanogenmod logo on the bottom half of the screen). After this, it would vibrate twice with around a two second delay between each vibration. Then it would show the Samsung logo, the model logo, and vibrate twice again, repeating indefinitely. The only thing that stops the loop is pulling the battery.
At this point I'm thinking that there's a problem with the battery. I kept it plugged in to my computer for a little while while it tried to boot, hoping that it just needed to be charged. After this didn't work, I tried charging it with a portable battery pack I had and used a different cable. Still nothing. Then, I found a spare battery that I had and replaced the one I had been using. That didn't work either, the phone continued doing the same boot loop.
I don't believe that the problem is a faulty power button, since it doesn't start trying to boot until I either plug it in to charge or I press the power button myself. I can't seem to enter recovery mode. Whenever I try, it shows the initial Samsung logo screen with "Recovery Booting...." in small blue text in the top left corner of the screen, but then proceeds to reboot again.
I am, however, able to enter download mode. I decided to try and flash my stock firmware, hoping that would fix the problem. I put my phone in download mode, opened odin, and it seemed to recognize my phone. I loaded the .md5 file and hit start, but almost immediately it showed 'FAIL'. This is what it said in the message box:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
At this point I have no idea what else I can do. I hope it's not a hardware failure, but it's starting to look like that's the case. Is there anything else I can try, or is my phone just dead? And, if it is dead, does anyone know the exact cause?
CM is your rom, not your firmware. The firmware is what we generally refer to as everything but system, kernel and recovery. Do you know what your current firmware build is?
Are you certain you downloaded the Wind version of the firmware?
I could be wrong but from the Odin output it looks like you have pre 4.3 firmware. If so, try using any other build and see if it flashes.
Judging from the symptoms you described, it is possible you could be looking at a hardware failure. Possibly the SoC, but more likely the memory. If you cant get Odin to flash anything the possibility of this becomes greater.
Try other firmware with Odin. Try with and without re-partition checked. (This will wipe all your data)
Try flashing TWRP via Odin. If that makes recovery work you may then be able to factory reset and flash a rom again.
Try different usb cables and ports. Try another computer as well if nothing else is helping.
Beyond all of that, im not sure theres gonna be much you can do.
Argh, I always seem to get ROM and firmware mixed up. Anyway, If I'm understanding this correctly I'm pretty sure that my firmware was 4.2.2. I definitely downloaded the wind version of my stock firmware. I also found on my computer 4.0 firmware that I'd downloaded a couple years ago. I tried flashing that with odin and got the same result. Then I tried it with re-partition checked and it failed again with this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I guess that's that then. Luckily I had backed up all my photos last week on a whim.
Out of curiosity, did you use a PIT file when repartitioning, or did it use the one in the device? Whichever it is, try the other as well. I believe the pit files are in the General section.
I used the PIT file on my device when I first tried to repartition. I downloaded the PIT file that you were talking about and tried again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you try flashing recovery only? And does odin see the devices COM port in the top left?
Did you try different ports and cables?
Odin does see the COM port. I just tried flashing TWRP and odin said that it passed, but I'm still not able to boot into recovery mode. I have tried using another port but I don't have another cable on me.
Well if it said it passed the recovery flash, the cable and port are probably ok.
Im not really sure there is much else you can do tbh. Its sounding more like a hardware problem at this point.
Sorry I dont have anything better to tell you, but if I think of anything else you could try ill let you know.
My phone randomly stopped working the other day. When its off, it'll start up on its own (without the power button being touched) but only get past the "samsung" screen a couple times and then shut back off. I tried flashing the stock firmware via odin but it fails every time (I've used versions 1.86, 3.04 and 3.09). As of now, my phone is totally useless. All I can do is put it into download mode. Any ideas?
This is what odin says every time
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Screen:
ODIN MODE
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Odon is failing because you are trying to downgrade the firmware. After 4.3 you cannot do this anymore. It looks like you probably updated to 4.4.2 via ota. Correct? If so there is no firmware you can flash as att refuses to release it.
Take your battery out and put it back in. If it tries to turn on by itself your power switch is bad and needs replacing.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
My Samsung Note II suddenly couldn't boot. It stays on the splash screen showing GT-N7105.
So I downloaded the stock ROM and tried the instructions at http://forum.xda-developers.com/showthread.php?t=2032849. I can connect, and the top left of the phone shows:
ODIN MODE
PRODUCT NAME: GT-N7105
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: 02
The Odin I am using is 3.09. There is no indicator of the progress of any download. I let it run for eight hours. Nothing seems to be happening. The Message box shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXUFNJ1_N7105OLBFNJ1_N7105XXUFND3_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> SingleDownload.
<ID:0/003> sboot.bin
Then when I finally unplugged the phone:
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
How long does the download normally take and is there progress or status shown somewhere?
Thanks.
SimpleSimon2 said:
My Samsung Note II suddenly couldn't boot. It stays on the splash screen showing GT-N7105.
So I downloaded the stock ROM and tried the instructions at http://forum.xda-developers.com/showthread.php?t=2032849. I can connect, and the top left of the phone shows:
ODIN MODE
PRODUCT NAME: GT-N7105
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: 02
The Odin I am using is 3.09. There is no indicator of the progress of any download. I let it run for eight hours. Nothing seems to be happening. The Message box shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXUFNJ1_N7105OLBFNJ1_N7105XXUFND3_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> SingleDownload.
<ID:0/003> sboot.bin
Then when I finally unplugged the phone:
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
How long does the download normally take and is there progress or status shown somewhere?
Thanks.
Click to expand...
Click to collapse
If you suddenly can't boot or even flash, then read about SDS.
yaro666 said:
If you suddenly can't boot or even flash, then read about SDS.
Click to expand...
Click to collapse
The phone boots but is stuck with the "Samsung Galaxy GT-N7105" screen. And I can see the download screen (Vol Down, Home, Powerr). Is this still considered a SDS?
SimpleSimon2 said:
The phone boots but is stuck with the "Samsung Galaxy GT-N7105" screen. And I can see the download screen (Vol Down, Home, Powerr). Is this still considered a SDS?
Click to expand...
Click to collapse
you mean it powers on, but doesn't boot. You can't flash, so compare to SDS.
If you can't do anything then emmc swap is the solution
This is not SDS. I had the same issue with my N7100. I flashed it with odin with the latest 4.4.2. Find the latest o.s for your phone and region. and follow the instructions word by word. Also, try changing the cable and the usb port on your computer.
You can see a green droid picture and a progress bar under it in your phone screen, while the flashing process is going in your phone. I think, the cable may be faulty or change the usb ports and redo it again. Good Luck....
Hey,
I have some old samsung ace 2 that I was experimenting around with, wanted to try and get some 5.1.1 ROM on it. But first I figured I needed to get some kernel on it, though I did something which now means that during bootup it is stuck on the samsung galaxy ace 2 logo. I can access ODIN mode, though cant access recovery mode. The battery mode also seems to be broke too as it just displays a loading symbol. So far I have flashed the EK kernel on it with what seems to be a success according to ODIN mode. Also note that Samsung KIES tries to connect to my device in ODIN mode but it never connects and troubleshooting doesnt do anything.
I tried to flash stock firmware to it through the odin software whilst my phone was in odin mode, though it displays a bunch of stuff in the odin pc software then attempts to reboot my phone though it just gets stuck on the boot logo again without odin really doing much here are the logs:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8160XXLD8_ready_to_root_ANT.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> kernel.bin.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Reckon my device is still salvagable from this hole I have dug myself in?
i am also having the same problem. tried to flash stock firmware with and without pit, still can't work :crying:
and i don't have jtag and don't know how to use it even if i have jtag :crying:
Need help recovering SM-T310 8", stuck at boot screen, Odin won't load TWRP onto it
I've been trying to get this tab back in working order for several hours now - When I first started working on it, all it showed was the "Samsung Galaxy Tab 3" screen, going right back to that when I turn it off (not even staying off.) I tried putting it in download mode (Power+Down+Home, it does work) and loading TWRP 3.1.1 with Odin (tried both 3.07 and 3.12.3) and it fails almost immediately after hitting Start, Kies won't recognize it over USB, and when I put in the model and S/N it says it's "not eligible".
Also, I've tried using the stock recovery mode, but the factory reset doesn't help, and it doesn't recognize the format of the only rom I could find for it (that doesn't require a premium membership.) It's a .tar.md5, TWRP is supposed to be able to handle it, but the system recovery doesn't see it at all.
(click for big)
Here's the Odin log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T310.TWRP.3.1.1-0.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Help, please? I've gone through multiple past threads here and on other sites I found on Google to get this far, but I've been unable to make any appreciable progress.