I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?
john2166 said:
I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?
Click to expand...
Click to collapse
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well
twistedillutions said:
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well
Click to expand...
Click to collapse
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.
john2166 said:
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.
Click to expand...
Click to collapse
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!
Mtsprite said:
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!
Click to expand...
Click to collapse
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.
john2166 said:
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.
Click to expand...
Click to collapse
If you remove the battery and put it back in does it auto turn on?
I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.
ThePagel said:
If you remove the battery and put it back in does it auto turn on?
Click to expand...
Click to collapse
Kind of. It shows the Samsung logo when I put it it in. It only goes into a bootloop if I hold the power button for a few seconds.
vax1170 said:
I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.
Click to expand...
Click to collapse
Thanks. I've tried what you asked with and without the battery, and the warning screen stays on for about 3-7 secs for both circumstances. I also tried replacing my battery with another one lying in my house. The battery compartment and the power button is seemingly normal.
Doesn't help ... but this other thread sounds a little bit similar to your download mode issue ... http://forum.xda-developers.com/showthread.php?t=2608201
Sounds like you have a very small window of opportunity before the download mode reboots. Maybe try this just to see:
- make sure your windows (assuming) drivers are all set up. Hopefully if you had ODIN working already, then you are set
- get a copy of heimdall command line version
- get the command ready to execute: heimdall print-pit --no-reboot
- In the small window of opportunity you have ... enter download mode, confirm, press enter on heimdall command and see if anything interesting happens
See if you get anything. If you do you might try to quickly use up-arrow on the CMD line to recall that command and run it again. If you know anything about windows batch scripting, you might try scripting the heimdall command above in a loop.
My thought here is that if heimdall cannot initiate anything useful, then your software is probably lost. If heimdall can output the PIT data, could be that download mode software is good, but the hardware is bad. If rapidly executing heimdall keeps your device active longer than usual, that might be an interesting tid-bit to know.
I am no expert here, so please seek other's more expert advice before trying anything. If your boot mode is screwed, perhaps the thread on [GUIDE] Debrick your bricked s3! [BOOTLOADER/HARDBRICK] might work, but again unless someone else confirms this, I would not try that until you are about ready to accept total loss.
Related
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
mex2309 said:
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Click to expand...
Click to collapse
U should definitely go back to stock via odin first before even trying to install cwm and flashing a custom rom.
Sent from my SGH-I727 using xda app-developers app
T.J. Bender said:
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
Click to expand...
Click to collapse
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
I think its a gonner...
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
mex2309 said:
I think its a gonner...
Click to expand...
Click to collapse
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
mex2309 said:
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
Click to expand...
Click to collapse
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
Sounds similar to what I just went through... Except I didnt do anything in recovery before mine started looping. Curious to know what rom you were running as well.
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
mex2309 said:
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
Click to expand...
Click to collapse
I'm trying to wrap my head around that, and not coming up with anything valid. Wiping the caches would cause a much longer boot time, battery stats, at most should only cause you to need to remove and reinsert the battery.
Just about the only thing I could come up with would be that when you wiped the caches, was that your phone was trying to reload all that data back into the cache and was getting brain dead.
More information is needed from others that have had the same issue, on the same ROM, or different does not matter, but detailed info as to what exactly was done prior to the boot loop issues.
If my phone gets stuck in a boot loop, usually after I flash someting in Odin or whatever, if I hit factory reset it fixes itself.
It doesn't bother me since all my stuff is backed up though.
You should Odin back to stock then flash cwm
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
just got a phone off of craigslist.. saw that it booted up, so i figured i might be able to fix it. cost me $100.
just finished ODINing it, but it just continues to bootlop. not sure what to do next.
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
hechoen said:
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
Click to expand...
Click to collapse
already did that.. flashed CWM, ran recovery and installed rom. no go. now i see the cyanogen boot screen, but it won't get past that. this is kind of strange.
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
mistabeo said:
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
Click to expand...
Click to collapse
I did what I could to try to replicate your situation. Which version of CWM are you installing? I went through several different versions up to the latest and found that the phone was having an issue with CWM itself. (possibly corrupted driver, but not 100% sure on that, as the phone does get recognized by the computers.)
But when I got to the latest CWM, and it started doing similar to yours, what I did was the following.
#1 : reinstall drivers
#2 : plugged the phone into the USB 2.0 slot on my laptop.
#3 : removed the battery, sim card, SD card
#4 : tried to power on the phone holding the power button for approximately 20 seconds. (nothing)
#5 : put in the battery while still plugged in, and powered on.
#6 : After phone booted up, and computer recognized the phone, I removed the battery. Phone stayed on.
#7 : waited while the computer re installed the ADB drivers, after driver install success, I unplugged the phone. Of course it powered down.
#8 : Restarted the laptop, put the battery back in the phone, and held vol + and - and power. Phone rebooted into recovery, but got into a boot loop when trying to recover.
#9 : downloaded TWRP recovery and put it on the SD card for the phone. Restarted the phone into recovery and installed TWRP recovery.
#10 : Rebooted phone into TWRP recovery. wiped all cache, installed latest STOCK ROOTED ROM.
The phone has been stable and working just fine, no wifi or blue tooth issues, calls are as normal, texting is as normal. LTE speeds as normal.
I have since switched all my devices over to TWRP recovery and have had ZERO issues.
My phone has been all screwy for months. I recently given up on it and bought a new phone but it irritates me that I still cannot fix this old phone.
After attempting to flash a new rom onto my phone everything went wrong. When I attempted to reboot the phone the phone showed the SAMSUNG screen then goes to CWD for recovery. I cannot fix this at all. Eventually I decided to run GTG's Ultimiate Unbrick thinking that Odin3 would fix my situation. It continuted to give me FAIL with every attempt. Now, the phone won't even show the SAMSUNG screen or the recovery screen. It just stays black... What can I do? Junk it? Is it permanently broke.. This is so upsetting.
Are you still able to access download mode? If so then i would try Heimdall this time using THIS flash file. Flash it once, let it reboot, then shutdown and go to download mode again. Flash once more with the "flash bootloaders" box checked. Has always worked for me when i screw something up due to not paying attention.
If you cannot access download mode WHAT-SO-EVER, i'm afraid i am unable to help.
Good luck
DarK_DemoN said:
Are you still able to access download mode? If so then i would try Heimdall this time using THIS flash file. Flash it once, let it reboot, then shutdown and go to download mode again. Flash once more with the "flash bootloaders" box checked. Has always worked for me when i screw something up due to not paying attention.
If you cannot access download mode WHAT-SO-EVER, i'm afraid i am unable to help.
Good luck
Click to expand...
Click to collapse
Tried today to put it into download mode. The screen flashes on completely white and back off. I can hear it connecting and disconnecting from the computer repeatedly. Im guessing there is nothing at all I can do from here. This really sucks.
mramazingpanda said:
Tried today to put it into download mode. The screen flashes on completely white and back off. I can hear it connecting and disconnecting from the computer repeatedly.
Click to expand...
Click to collapse
Does it connect and disconnect by itself? If it does then sounds like a hardware issue. If you can get it to connect to your computer open the JAR flash file which will open Heimdall after a few seconds (10-20). Once it's open press the Vol-Up button on your phone and see if Heimdall can see it (should say "Connected" in green at the bottom right).
Give it to me lol I'll fix it
Sent from my dr0id running Liquid Smooth r0m
I had something similar happen to me a long time ago. I would try to put it in download mode and the screen would do something but then just shut off. I pulled up heimdall and it said it was connected. I might have just gotten lucky. Give it a try though.
Hi I want to know how can I unbrick my Samsung galaxy s 4g. I believe I bricked because now when I turned on only stock in the logo. Please can you help me with this. I'm leontx's wife. Thanks
If it's just showing the logo and it's there for over 15 minutes, you'll probably need to reflash something.
I'd suggest using one of the one-clicks from http://forum.xda-developers.com/showpost.php?p=19601810&postcount=2 and I'd probably suggest the second (Basic with a Twist) choice.
First, you need to get the phone into download mode. Easiest way to do that is to unplug USB cable, pull the battery out, plug the battery back in, and plug the phone back to the computer. Hold the volume buttons on the left and turn on the phone (while holding down the buttons). It should ask you if you want to go into download mode. Press volume+ to confirm, then unplug the phone from your computer and plug it back in (to make the computer realize that there's a device there). Now run the one-click to reflash your phone. If the flash fails, restart the phone and try again. If the phone reboots to a screen showing a little phone and a yellow warning sign, perfect... just flash it again. That's the alternate download screen, and I get it everytime I use Heimdall/Odin/Kies to flash it.
couldn't get into download mode
Hello,thanks for you help,I'm trying to fix my wife's galaxy s after she wiped and factory reset the phone when tried to recovery by herself.Now the phone is stock in the galaxy s 4g logo forever,I tried to get into recovery or download mode but i couldn't.She told me that the phone was giving her a error message about the keyboard app,then she removed the batt and put it back, the battery showed her almost dead like 1% when was like 79% few seconds before,then she called t-mobile and the person told her to do the recovery mode with the bottoms, she did it and the person ask how much batt the phone had, she said 79%.then the person sugested to full charge the batt,and call them(tmobile) back.So here we go... lol:laugh:.She tried to fix it and got into recovery mode and wiped and factory reset the phone,I dont know what she was doing and removed the batt to reboot the phone.and here we are now.When try to get into download mode the pc not recognize it say USB device not reconognized and the phone just show a loading logo but nothing happen.I just want to know if is possible to fix this or toss it,the phone is rooted with a custom rom,I tried with another batt but the same results.Im realy want to recover this phone to give it to my mother in law thank you so much
Leontx said:
Hi I want to know how can I unbrick my Samsung galaxy s 4g. I believe I bricked because now when I turned on only stock in the logo. Please can you help me with this. I'm leontx's wife. Thanks
Click to expand...
Click to collapse
i soft brick may phone yesterday, i use to flash my current rom and then reflash it again [clean flash] i just reflash it to save my game replay..
if you can boot into recovery mode, reflash your current rom and then backup and wipe everything exept sdcard then flash again.
Sounds like the battery crapping out on you & crashing while it was doing something important. Usually, a factory reset and new battery can fix. But, If the reset failed, it's not a biggie. find any of the one clicks that you might like to try (lumin30 has a awesome guide/thread w/ links). Batteries are cheap. Sometimes they will swell up when they die. If it spins easy when placed on flat surface is an easy check. There are a couple threads with links to 10 buck replacements around too.
Sent from my NookTablet using xda app-developers app
eureka !!!
my phone is alive.I could put it in download mode by removing the batt,put it back then holding both volumes bottoms,then connecting the phone to my pc(USB),no power bottom.and voila after putting this in download move everything else is piece of cake thank yall.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Hi,
Apologies if this has been asked before, but I've done a relatively thorough search and I can't find a solution to this problem.
I have an S6 (SM-G920F), It was playing up for a few weeks before this, not charging well, and what not, thought it was a cable/hardware issue. Then it stopped working entirely. Initially when it was plugged into the wall it would say it was 91% charged, but if you tried to turn it on it would turn off, and reboot into the charging screen.
I've done quite alot of reading and I've ended up flashing it with Odin (I have a single .md5 file, which i've loaded onto the phone via AP) using the most recent FIrmware UK EE for the SM-G20F. This was successful, however now it only loads the Black screen with white text Samsung S6 powered by android screen and then goes blank and back to the white text screen.
I downloaded an alternative firmware (the one previous version), but this has had the same effect. I've tried to repartition with odin, but this fails.
1.) Is there anyway I can fix this?
2.) If not Is there anyway to remove files whilst in downlod mode?
3.) If I cannot fix it or recover my data, is there anyway to wipe the data securely from my phone so I can sell it for parts?
At present, I can't access recovery mode, only download mode. But whilst Odin communicates with the phone in download mode, I can't seem to access my files from explorer?
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
King-V said:
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
Click to expand...
Click to collapse
Thanks for your reply! So after flashing it goes straight back into the boot loop. Weirdly if its plugged into my laptop it spend about a second or two on the "Samsung Galaxy S6: Powered by Android" screen before plunging into darkness and shortly after repeating the same message. However if I plug it into the wall it spend over twice as long on that screen before repeating the cycle. It never goes any further.
I've tried your suggestion about perhaps its timing for recovery mode, but even if I go straight from cancelling download mode to trying the power, up and home key it doesn't go to recovery. I've tried a variety of timings both plugged into my laptop and plugged into the wall to no avail. If the phone isn't plugged in, it literally won't do anything whatsoever, won't even hint at turning on.
So Next I tried flashing it with TWRP via Odin and nothings changed, exactly the same bootloop and I still can't get into recovery mode.
I'm starting to think that sadly this phone my be beyond repair! Thanks for your help though, much appreciated.
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
vinicius_guerra said:
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
Click to expand...
Click to collapse
Hi Vinicius,
Thanks for the suggestion. Unfortunately it didn't work, I even tried flashing it back to a standard ROM from TWRP, but it still didn't do anything, just back to the Samsung logo and the loop continues ever more!
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Melioetta Zyguard said:
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Click to expand...
Click to collapse
Same experience. For all those 6 years that I used this device, the wifi was okay until now. It (wifi) is very buggy (turning on and off, and sometimes won't turn on at all) so I restarted the device, then bootloop happens. I flashed the stock rom via odin and clear data and cache. But it is still bootlooping. I think this is the sign that I need to replace my phone IF I couldn't find a fix to this.