Related
Okay I just recently Flashed CM6 Rc2, Everything was working fine. Then I noticed the Market started FC every time I tried to load it. I can't get it to open at all anymore. So I figured I would wipe and reflash, but I when I reboot and hold down HOME AND POWER it just stays stuck on the TMobile G1 Splash screen. But if I pull the battery out and put it back in, I can start up the phone again. Everything else works pretty good besides random things at times. Every now and then it will randomly restart. Also, I tried to factory wipe through the settings, and it just rebooted and then stuck on the G1 screen again.
Can anyone PLEASE help??
Try ADB? Or through the terminal? CMD, lol. I had the same problem with market, so i got tired of it. And flashed Cannon Complete Eclair, It works better than Froyo, and they aren't that much different.
Try using fastboot in the bootloader. That happened to me a couple of times with the Clockwork rom manager and going between roms.
1) Download another copy of the recovery img
2) Rename it something simple like recovery.img
3) boot into the bootloader (Camera + Power)
4) open a command prompt navigate to the directory that you have the image in
5) run this command without the quotes "fastboot flash recovery recovery.img" (if you didn't name it recovery.img then substitute the name you chose)
Hopefully that works for you.
**If you don't have the sdk tools files (adb.exe..., fastboot.exe) copied into your /system32 folder like I do then you will need to put the new copy of your recovery.img into the sdk tools folder and navigate there in the command prompt, coping them into the /system32 folder lets use them regardless of the directory that you are workin.
I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)
I too used a similar process Roadmasta01 and biglo used. I had a buddy that had the exact same problem today. His G1 was progressively getting worse ... pretty soon everything would FC and he couldnt get it to the boot loader and then it just wouldnt boot past teh G1 logo.
Booted the G1 into fastboot
downloaded the latest clockwork recovery image from koush's site and saved it to the folder location adb and fastboot are located in the sdk.
fastboot erase recovery
fastboot flash recovery <recovery you downloaded.img>
rebooted and al was well again.
biglo said:
I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)
Click to expand...
Click to collapse
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.
Roadmasta01 said:
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.
Click to expand...
Click to collapse
Its kool man its always good to hear about users with different experiences on things they try in case we run into that same problem. I'm juust like you I try to figure things out myself before I resort to posting on how to because I know most answers are already out there.
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Good job thinking on your feet!!
i`m having kind of the same problem with my G1 it won't boot all of a sudden and when i try to enter recovery mode it freezez at " Build : " once after about 5-10 minutes it loaded the recovery menu but nothing was working it was extremely slow ... i tried the options above to erase and reflash the recovery.img but it just won't work it does the same thing ... anyone have a solution ? ...
reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Lol I'm glad my problem helped ya out. I actually ended up fixing it myself luckily enough. But thanks to all who posted responses
Sent from my HTC Vision using XDA
powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...
I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
Sent from my Nexus S using XDA App
Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.
Sent from my Nexus S
Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
Sent from my Nexus S using XDA App
You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.
Sent from my Nexus S
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
leyvatron said:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
Click to expand...
Click to collapse
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
kenvan19 said:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
Click to expand...
Click to collapse
Coolest wife ever? haha
risegeek said:
Coolest wife ever? haha
Click to expand...
Click to collapse
hehe why'd'ya think I married her
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.
as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.
Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).
Once in Recovery, try wiping cache from the menu.
Reboot.
If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Van_Dyke said:
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Click to expand...
Click to collapse
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.
Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.
get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug
you can always make your own JIG if you have the materials at home or a nearby Radio shack
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,
If you get any repeat i would take it back to get a fresh battery of course (only right to do so).
here's hoping you never need to though
Van_Dyke said:
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
Click to expand...
Click to collapse
That is scary......
Sent from my Nexus S using XDA App
Bricked
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Noob {MAC User}... Please be gentle
Greetings Everyone,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamara
warrenb said:
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Click to expand...
Click to collapse
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?
If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.
I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).
If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"
Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"
Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.
With any luck, you should be able to boot into a fresh phone.
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.
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.