Database Info

Stuck at 1st boot screen

I've looked all over for the answer to this, and I've tried multiple things but nothing seems to be working. Last night my phone froze (for no apparent reason) so I pulled the battery. The first boot screen came and went but the 2nd doesn't show...it stays blank and then eventually I hear the noise my phone makes when it's fully started up, but the screen is still blank. I have to push menu and the home and call keys a couple of times to get the screen to turn on, and then I can see everything seems to be up in the background, but when I go to unlock my phone it doesn't recognize me pressing the buttons (to unlock the SIM) so I can't get any further. When I do home+power combination, the screen with the triangle and exclamation point comes up, but it won't recognize any of my button presses. I tried to use fastboot to bring it back, and it says everything went through but when it starts back up the same thing happens, it won't recognize me pressing the screen to unlock the phone. It will take maybe the first 2 keys I press..and it will lag while it takes them...but after that it doesn't take anything else. I don't know what to do so if anyone can help or might know what could have happened. Like I said, I was just on the browser last night looking around and it froze so I pulled the battery. Oh and I'm running JF 1.50 if that matters. Thanks guys.

Did you install hardSPL?
If not, maybe you can create a goldcard (search in this forum) and flash the basic system on it again!

I have the SPL for Sapphire ported to Dream.
I might have to take it in to T-Mobile because it boots up and just automatically freezes at the main screen.
The only thing I'm worried about is that I changed the first boot screen so if I do end up having to get a new phone I'm going to have to pay for it

wipe wipe wipe
no need to take it to t mob just wipe take the sd card put it in a sd card reader load up the root/hack rom and go from there no need to take it back cause t mob will tell hell no when they try ro boot it up

I don't know how to wipe it without going through the bootloader and that won't load up.
I also don't know how to flash an update without going through bootloader so I'm stuck.

try this
pull the battery hold down power + home put battery in without taking your fingers off thoses buttons wait till bootloader loads. it happent to me an endless loop everytime i pulled the battery it would power up without touching the battery so thats what i did

[Q] My TF101 stuck at EEE Pad Blue Bar screen!!!

Hi All,
I had ICS installed on my TF101. However yesterday it totally discharged when it was asleep and I had trouble turning it on. I never had this happen with HC. So I decided to go back to HC. I had my tablet rooted and su backed up. Had recovery installed.
I flashed official US HC fw and everything went fine until I tried to reboot the tablet. It's now stuck at the EEE Pad loading logo with the blue bar approximately half filled in. No amount of button combinations does anything. I can't enter Vol + & Pow button to enter ADB, and when I try to enter recovery mode, the white text shows up saying searching for OTA recovery and that's it, still gets stuck at the blue bar.
Any ideas or ways to get to my recovery before I return my 2nd tf101? Thanks!!
(Btw, I'm not a newbie, I would NEVER do this whole thing if ICS was stable and worked like it's supposed to, but I refuse to own a 390$ half working tablet that crashes, has battery drain issue and gfx glitches after the FORCED ICS update!)

Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?

Goatshocker said:
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Click to expand...
Click to collapse
Hi Goatshocker!
I have tried to cold boot it, but it does not allow me to get to the 2 icons you're talking about. When I hold down Vol - & Pow, it shows the regular white letters from bootloader, and gets stuck at the blue loading bar EEE Pad screen.
What I meant by force, is that after 4 delays of the update, ICS will install itself automatically! Even when the tablet is in sleep mode. That's what mine did.
In order to avoid this, the user would have to root his tablet and use Titanium Backup Pro, and disable certain system update processes. Which is NOT for the casual user or for anyone who wants to keep warranty intact.
The s/n I have starts with C2O.

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.

Have you tried booting into recovery?

(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

Motorola XT1542 Weird brick, (Please help)

Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)

martiagosantinez said:
Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)
Click to expand...
Click to collapse
So I don't know if this is helpful in anyway, but I'll wait for it to run out of battery and then I'll try to plug it into the computer again, maybe that helps in any way?

I found this reddit thread
https://www.reddit.com/r/MotoG/comments/5iz8fz
Someone had the same issue (Or a very similar one) I had, but I don't know if OP figured out a way to fix it, or if he was able to get into the bootloader.

Update, the phone ran out of battery and it's shows the low battery screen when I try to turn it on, or when I try to enter Bootloader, it's still not recognized by my PC