Related
Last night I went to reboot into recovery and my phone now sits at the Galaxy S2 splash screen and won't boot up. Tried plugging it in powered off and it won't even go into charging mode. The battery picture just comes up and the little spinning wheel keeps going.
So Ive been trying for the last hour to reflash the phone back to stock using both Entropys return to stock guide as well as the 'How to return your phone to the store' guide too and no luck.
Heimdall of course as always just flat out doesn't work so I hooked it up to my laptop and ran Odin. Odin connects to the phone fine and the box turns yellow, but the minute I hit start, it just gives me this:
<ID:0/008> SetupConnection..
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)
I even tried the one click ICS leak from Rootzwiki and the same thing.
I can get the phone into Download mode no problem but man I cannot get it to flash ANY of these rome!!
Any advice or should I just take it to an ATT store on the way home from work??
I got it around the second week of February so hopefully worst case scenario I can still exchange it..
Im at my wits end here, can't do anything with it!!
I had same problem with my sprint Gs2, I took it into the store they told me since I rooted they couldnt help me. But the guy said go into download mode and root it again, it will remove anything and everything off it. Idk if that's what you want though. It got my phone back up and running
Sent from my SPH-D710 using xda premium
Ahh forgot to add I can't get into Recovery anymore.
No clue what happened. I can get it into Download mode but not Recovery.
If I could've gotten into Recovery I could've just flashed my Nandroid last night and fixed it hehe..
ODIN requires Download mode, not recovery mode. If your phone can indeed go into download mode as you claimed, you should be able to flash any ODIN flashable ROMs.
Try flashing just a kernel with recovery
Sent from my GT-I9100 using Tapatalk 2 Beta-2
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
creepyncrawly said:
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
Click to expand...
Click to collapse
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Slavestate said:
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Click to expand...
Click to collapse
Add me on gtalk and we can see what we can do [email protected]
At this point I don't know if anything will help heh.
All it will do is either sit on the GS2 boot screen, or it will go into Download mode.
Download mode though, no luck so far. Odin just won't flash it for some reason. It sees it, the COM port box lights up yellow, but the minute you hit Start, it just goes right to that error message I posted above. After this, I have to close both Odin and disconnect the phone and reboot it into Download mode.
I went through the Download Repo. Tried I777UCKH7-CL503881-Full.7z, and even the param.ifs by itself but everything just gives the same result. I didn't try Entropys DD though since I was running the stock ICS and didn't want to really mess anything up. Only thing I can think of left to try is flashing Task/Fennys CWM modded stock ICS kernel but after all this I doubt its going to work. I tried the stock rooted GB kernel earlier and it didn't bother flashing either.
Am I maybe connecting it wrong? I have the battery pulled and am going into Download mode by holding the vol buttons and connecting the usb cable to the laptop. I don't want to kill the battery power I have left as it won't charge now either. Basically I just fire up Odin, connect the phone and put it in Download mode, select my tar file and put it in the PDA slot, hit Start and go.. Should I be doing anything differently??
Whenever I've had a problem with Odin like that, it has always been that some partition got flashed wrong/partially/corrupted, and the only fix was to reflash the damaged partition. As long as Odin is seeing the phone, then it must be either a software/firmware problem or a hardware problem. I'm still thinking it is firmware, but it seems to be outside my experience.
I havn't been playing with ICS yet, but I have noticed that there have been a number of reports similar to yours, where people have flashed some flavor of ICS. This supports the idea that it is firmware. I have always understood that if the problem is firmware, and if the phone can boot into download mode, it can be recovered.
Yeah Im wondering if I should try flashing the PIT file I have for the phone, but I don't know crap about partitioning these things and didn't want to really mess it up.
Guess at this point its worth a shot. I was about to go sit and chat with the warranty folks at ATT (mines a refurb so Ive only got til the end of the month before warranty s up). Maybe Ill try the pit file and let Odin repartition the thing. I can't flash a firmware back onto it anyways.
EDIT: Holy crap progress.. I flashed the stock secondary boot loader with Odin (in the Bootloader slot) and that actually flashed. Now I just reconnected it and decided to try the ATT ICS leak one click from Rootzwiki and it appears my phone is now flashing!!!!! As long as my crap is still on the internal usb storage today is gonna be a good day hehe! Yep all is well so far! Phone just rebooted and its now at the ICS setup screen! WOOHOO!!! Crisis averted!! Thanks guys for the comments and help! Creepy thank you for reminding me we have that repository!!
I finally decided to update my AT&T Galaxy Note this Sunday. I already had a root on GB, so I decided to update to a ROM with root. I chose bigfau's {ROM}{UCLF6} Official ICS Stock Odexed, Deodexed, Rooted, Zipaligned, CRT ROM for the Note. However, when I went to update via Odin, I found out that I needed CWM.
Therefore, I found a GB rom with CWM, and installed that via Odin.
Then the phone restarted. It started just as normal, and I placed the ICS ROM (see above) on the internal SD card. I then restarted to CWM (this was the first time I had started CWM on this phone). I went and installed the ICS ROM via CWM. Apparently it came out fine (according to the screen). So I went all the way up, back to the original menu.
I chose the reboot option.
It rebooted, and the Samsung logo appeared.
The logo disappeared. And reappeared with more brightness.
So far, still normal.
Then the screen went black. No buttons I pushed did anything, no matter how long they were held. Only a battery reset would let me do anything with the phone. I took out the battery and put it back in, and restarted it in download mode, then re-flashed it with GB. Nothing happened. I re-flashed GB w/ CWM. Then I went back to CWM and tried installing ICS again. Same thing happened.
I went around looking for some helpful post on AndroidAuthority and XDA. Nothing.
I've run out of ideas.
So today, I ask for help.
Any help leading to a solution is appreciated.
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
The file is zipped!
gregsarg said:
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
Click to expand...
Click to collapse
Thank you, however, the file from samfirmware.com is a zip file, which I believe I'd need CWM to install (Odin only accepts tar files, as far as I can tell). However, when I unzipped it, I found a .tar.md5 file and a dll. What should I do now?
For clarification, I can't access the internal SD without it functioning, and I don't have access to a microSD card.
Unzip the file you got. The .tar file is in there.
I already did that.
I already did that. Like I said in the previous post, it contains a .tar.md5 and a .dll. What should I do next?
(Thanks for the suggestion, anyways)
the .tar.md5 is called a tarball and has the pda file, csc file, and modem file. just put the tarball in the pda section of Odin3 and flash. Make sure Kies isn't running in the background. Reboot is checked but nothing else is.
Just getting back ...
Many thanks for jumping in ranger ....
It sounds like the OP has it now ??
Time will tell I suppose ....g
This is a special case that requires extensive help from you guys (hopefully).
Problem: According to the ATT Samsung specialist the Bootloader I am using is corrupted
Attempted Solution: I have attempted to flash the stock SBL onto my phone but after trying every version of Odin3 (1.83-3.09) it did not work.
**The bar was entirely GREEN but it never finished**
Suggested Solution: Flash the stock ROM back onto the phone using Odin3
Outcome: After trying three different ROMs, all downloaded from Sammobile, using every version of Odin3 (1.83-3.09) only seemed to reach the end then fail at Modem.bin
I was wondering if anyone has any idea how to fix my phone, the original issue was that it never made it past the Samsung logo (not the Galaxy S2 Logo but the actual Samsung logo) the new issue is that it has the Samsung Galaxy SII Logo with the wrong model name (international model) and the small yellow triangle.
If my phone is permanently broken that's fine because I have a temporary phone I just want to get my files off of the phone before using my new one
I have a Jig
I can get it into Odin mode
I cannot get it into Recovery mode
I can get it into Factory mode
Help me please, I have no idea what else to do
Use this version of Odin, or just do more Google fu and find another place to download it from. [ http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 it may be the version of Odin you're using that's messing you up.
The link Phalanx7621 posted was supposed to point to the Download Repository (link is in my signature.)
The preferred version of Odin is 1.85. If you need it, the download link for Odin3 v1.85 at the top of the Download Repository is a working link.
If the boot loader was corrupt, the phone would be a true brick (no sign of life.) If the secondary boot loader was corrupt, the phone would not boot as far as the Samsung logo. It sounds to me like the AT&T Samsung specialist you received that information from was not fully informed.
The I9100 splash screen with the yellow warning triangle is due to flashing a custom kernel, so nothing to worry about. It can be cleared by flashing a stock kernel. Using the following procedure would have put that on your phone anyway by flashing the Siyah kernel, and then will removed it when stock Gingerbread is flashed.
Please note: The link in the Download Repository for the stock Gingerbread that you need to flash is not working, and I have yet to re-upload all these items to a new host. You will have to download this from the sammobile firmware page. It is the I777UCKH7 / I777ATTKH7 dated 2011 August. You'll need to sign in to download it. The registration is free. Edit: sammobile has not uploaded this file to a new host yet either. I will have to upload it and the sbl for you, but since today is Christmas, you may have to wait a day or two. At least you know that there will eventually be something to try.
Edit: The required files are now available with Dev-Host links in the Download Repository.
I think you will probably recover the phone by assuming it has nand read/write corruption and following this sequence:
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Attempt #1
When attempting to flash the Kernel in Odin3 v1.85 the bar was fully green but the program never said complete (I left it going for a few hours to no avail)
I tried flashing the SBL and the same issue happened, the bar was fully green but it never said complete (I had previously downloaded the SBL)
When attempting to flash the Gingerbread stock it does not even go past the SBL1 part, the bar does not have any green within it and the program still says NAND Write Start.
I'm not the best with this sort of thing but from observation it seems that my NAND is corrupt and isn't allowing anything to be properly flashed.
By the way: the Custom Binary Download now says: Yes (5 counts) which tells me that the phone recognizes that something is being flashed but it's not working properly
I'm back to being stuck and I think this phone may be truly broken :/
I don't think ur phone is broken.
Try a different usb/micro usb cable. Try a different usb port on ur pc (don't use a usb hub). Make sure the phone's micro usb port is clear of dirt/debris, etc.
Usually when i've had problems with Odin flashes it is something as simple as doing these things that results in a successful flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Same Issue
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
androidrequest said:
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
Click to expand...
Click to collapse
Did you follow exactly the sequence in post #3? If not, please try that.
creepyncrawly said:
Did you follow exactly the sequence in post #3? If not, please try that.
Click to expand...
Click to collapse
Yes, I tried that sequence exactly. It actually won't advance past #1. The green bar loads in Odin under kernel, but stops working at NAND Write Start. And trying the sbl ends with the same result (I believe it's the first download in the Download Repository). All of the flash attempts have failed or frozen, but the Custom Binary Download count is at 3.
Guess I'll start at the beginning so nothing gets left out. I was rooted on OC1, downloaded FlashFire to update to OF1 . Flashed it, the phone rebooted and got stuck on the black Samsung Custom screen. I've tried to flash tar files of OC1 and everytime I put it or any kind of tar file in the AP slot of Odin, Odin becomes unresponsive and closes. I tried to load up the SD Card with OC1 and OF1 Roms and tried to flash those to see if that would do anything. The phone always says (in recovery at the bottom of the screen)- Manual mode, applling multi-csc...applied the csc-code-vzw. Then says below that, remove failed file '/system/csc_contents'(read-only file system. At the top it says Android system recovery so I'm assuming that's custom, I know its not Safestrap so I guess its FlashFires recovery? Anyway, when I try to flash a ROM it says,E:footer is wrong E:signature varification fail. I'm at a loss as to how to get the phone back, if its possible. I was always told that if the phone powers up, its recoverable, just not sure how. Any advice would be awesome, I've been messing with this thing since early yesterday and I really need my phone back!
....It seems as though I have stock recovery. Is there a way to flash a recovery through Odin?
have you tried using ODIN with I545_Downgrade_tC1.tar from [How-To] Update to I545_OF1 - 5.0.1 and KeepRoot by muniz_ri? ODIN tends to get stuck for a bit while loading the tar, as it is reading a 2gb file. You should probably leave ODIN alone for a few minutes after loading, and if it still has problems, maybe re-download ODIN or use a different comp.
Thanks for the response. I did try that file, actually that was the first one I tried but it didn't work. Actually while I was typing this I downloaded another Odin, put the OC1 neutered tar file and did what you said, left it sitting in AP. After 5 mintues or so it worked!!! I've been messing with this phone going on 3 days now and as I'm typing the phone has rebooted and now is in the setup wizard!! Thanks for the reply!
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.