Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
Hello. About a month ago I rooted my phone using this guide http://forum.xda-developers.com/showthread.php?t=2189646. Everything went great until today. Few hours ago I received a system update (about 10MB) and installed it. And since then every time I reboot my phone I get ClockworkMod recovery menu showing up on my screen. I tried pulling out the batery, I even made a factory reset, but it still gives the the CMW menu every time I reboot my device. Maybe anyone of you could tell me what to do? Cause I'm kinda panicking right now
P.S. I also made such thing as "format /system" through "mounts and storage" menu. I don't know why, but I think it should be mentioned (just in case)
Well the best way now will be to download CWM backup for your phone from this thread, send it to sdcard and just recover using CWM. This way you won't lose root and CWM. If it won't work just you use KDZ to flash ROM from scratch. Check this thread too: http://forum.xda-developers.com/showpost.php?p=36352031&postcount=3
anirion said:
Well the best way now will be to download CWM backup for your phone from this thread, send it to sdcard and just recover using CWM. This way you won't lose root and CWM. If it won't work just you use KDZ to flash ROM from scratch. Check this thread too: http://forum.xda-developers.com/showpost.php?p=36352031&postcount=3
Click to expand...
Click to collapse
Thanks you. One more question. How do i know which CWM recovery to download? There are two Jelly Bean ones
Feero21 said:
Hello. About a month ago I rooted my phone using this guide http://forum.xda-developers.com/showthread.php?t=2189646. Everything went great until today. Few hours ago I received a system update (about 10MB) and installed it. And since then every time I reboot my phone I get ClockworkMod recovery menu showing up on my screen. I tried pulling out the batery, I even made a factory reset, but it still gives the the CMW menu every time I reboot my device. Maybe anyone of you could tell me what to do? Cause I'm kinda panicking right now
P.S. I also made such thing as "format /system" through "mounts and storage" menu. I don't know why, but I think it should be mentioned (just in case)
Click to expand...
Click to collapse
Feero21 said:
Thanks you. One more question. How do i know which CWM recovery to download? There are two Jelly Bean ones
Click to expand...
Click to collapse
If you share which L9 variant you have, which country rom you flashes or stay, then people will be able to help/tell you, which cwm backup is suitable to your L9.
Update your profile with your country name (if u r not criminal? lolz kidding), operator name and add L9 variant in your signature. at the moment, your profile is completely naked.
Ok, I managed to deal with my problem. Firstly I tried using cmahendra's guide on installing KDZ offline, but after aproximately 2 hours of complete failage I began searching for other ways. Luckily user edriskus answered to the message I sent him and suggested me doing the same as I tried to do before. He didn't mention the offline version so I thought that I should try the "online" one. And it worked! I don't really know how it sounds in numbers, but now my phone says that it has 4.1.2 version of android (hopefully the latest one available for L9).
There are few questions left:
1. Does my phone remain rooted or I have to root it once again (since I have reinstalled the software)
2. This one confuses me the most. Now my phone feels very laggy (which is strange, because it was factory reset previously and there aren't any apps here). I feel it from sliding menu/photos, surfing the settings and other similar actions. Maybe there is a way to fix it?
Nevertheless, my phone is working again and I really appreciate your help, fellows!
hello
Hello! I have exactly the same problem! Can you please explain to me how you manage to deal with it? I tryed to flash after this method http://forum.xda-developers.com/showthread.php?t=2085344 but i stuck at step 6 at the Post-JB issue, since every time I reboot my phone I get ClockworkMod recovery menu. Its a dead end for me. Pls help and thank you very much!
I finally succeded! Thx Feero21 for helping me, i followed your advice by trying it in "online" method. But there is one more problem, after i flashed the Rom i saw that i have only 1 gb free on my internal storege and another one occupyed. In total i have 2 gb instead of 4. I belive that the old Rom wasnt deleted and its still their and its occupying my also too small space. what can i do? Thanks!
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Htc ONE X+ Help!!
7virage7 said:
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Click to expand...
Click to collapse
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
thacruz said:
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
Click to expand...
Click to collapse
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Htc ONE X+ Help!!
7virage7 said:
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Click to expand...
Click to collapse
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
thacruz said:
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
Click to expand...
Click to collapse
Thanks for ideas, but it still does not work. Phone reverts its state. It's trully magical. Every time it reboots to the moment just after rooting. I have never seen anything like it before. Bootloader is always unlocked and memory chip state cannot be changed.
At least I haven't figure out how to do it yet
Anyone, please help!
EDIT:
A tried ADB sideload today, but after the file is sideloaded it can't be flashed - TWRP considers it corrupted and it vanishes after rebooting - AS EVERY CHANGE
I hope I didn't ruined my phone the first hour I got it, and XDA members could still help me. PLEASE
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi, I think also it's is the explanation for HOX+ radio lacks, permanent screen locks after the sleep, etc... fails in my AT&T's unlocked HOX+, defective emmc or emmc firmware.. It´s possible?
You also can see it: http://forum.xda-developers.com/showthread.php?t=2404393
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!
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.