Anybody know what causes this? And it's not the boot screen but the Motorola logo because the software starts to boot. I can reboot and usually it comes back to normal but it does this and sometimes I will sleep another 7+ hours and not have the phone on in case an emergency
Sent from my Nexus 7 using Tapatalk HD
radzer0 said:
Anybody know what causes this? And it's not the boot screen but the Motorola logo because the software starts to boot. I can reboot and usually it comes back to normal but it does this and sometimes I will sleep another 7+ hours and not have the phone on in case an emergency
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Are you using Custom ROM? Nearest bet is, it might be ROM or Kernel issue. Would be good if you reflash another ROM or go back to stock firmware to see if that's the case.
It did this before I unlocked the bootloader and all. Doesn't do it every time but based on times I see on it it happens around the same time as full charge would come around. Also I have changed rooms a few times since and it continues. Wouldn't the room try to boot and lock? Because it's not even getting to the boot logo it's hanging on Motorola.
Sent from my Nexus 7 using Tapatalk HD
radzer0 said:
It did this before I unlocked the bootloader and all. Doesn't do it every time but based on times I see on it it happens around the same time as full charge would come around. Also I have changed rooms a few times since and it continues. Wouldn't the room try to boot and lock? Because it's not even getting to the boot logo it's hanging on Motorola.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Which is your phone? Does it have a forum here in XDA? If it has a forum, it might be good to post this issue over there, as you would get more feedbacks from the users using this phone.
From the problem you explained, its getting stuck into bootloop after getting fully charged that's why no boot animation. It should be a software/ROM/Kernel related issue I guess, though not sure.
RAZR maxx hd.. I figured maybe they released a new main firmware that's non rom related and since I don't run stock I didn't get it..
Sent from my XT926 using Tapatalk 2
Related
This is the first time have i downloaded a rom and so i got cm10 and now it's just stuck at the boot animation. PLEASE HELP!!!
Make sure you did not skip factory reset before flashing the rom.
Might be redundant but you gotta do a battery pull to get out of boot loop.
Sent from my Nexus S using xda app-developers app
Is it stuck on the google logo with the unlocked padlock below? If so try pulling the battery and retrying. If it gets stuck after that then you have yourself a booting problem.
I have a similar one (with phone getting stuck on google logo at start up), and I get passed it by heating the phone using a blowdryer (battery out). I'm on Jellybean and rooted and it's an gt-i9020T model. If everything about your problem is like mine, you can try the same solution, maybe it'll help get passed the frozen screen? P.S this solution only helps you boot one time, if you reboot it'll get stuck again (at least it does for me).
Never heard that about the hair dryer. Sounds scary. Follow this http://forum.xda-developers.com/showthread.php?p=20629823
And hopefully you downloaded the correct rom 4 your phone. Then reflash rom in recovery
Sent from my Nexus S 4G using xda app-developers app
LOL what is this blow dryer method?! I see the same user posting about it on other threads.
Guys,
Have been running MIUI V5 on my d2vzw (ported from d2spr) for a couple of days now. Noticed today that the videos were playing reversed (probably due to the ROM running on sprint kernel, correct me if i am wrong). So i flashed one of the kernels for vzw and had a bootloop.
So, in a moment of inspiration :crying:, i restored the boot partition from my MIUI v4 backup in TWRP (thinking that must be the kernel part) and the phone wont boot. No Download mode, no vibration, get the red indicator on for some seconds but thats it. I get QHSUSB_DLOAD error when connected to my computer.
Guess this is a hard brick. Would i be able to get into download mode with USB JIG (i would need to make one, if there is no chance i will not try it). Is JTAG my only option? I have no warranty between since i am using this phone in India.
Guys,
Any Help??
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever.
Sent from my SCH-I535 using Tapatalk 2
What is the reality of this thought anyone have the truth?, ThanksQ
Is this statement TRUE for certain? Quote: "I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever."
Thanks in advance! moi
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
Pull battery and let sit an hour so everything discharges and try again. If still blacked out most likely J-Tag. QHSUSB_DLOAD error is a bad sign.
For about a month now my phone has been randomly restarting into qhsusb_dload.
I flashed the international ICJ, bricked my phone, sent it away for repairs. I sent it to mobiletechvideos, they repaired the brick and gave me s-off.
After the repairs it worked fine for ~1 month.
Now, the phone will almost always boot to qhsusb, though I can get it to boot into the rom/recovery/bootloader.
I've tried changing roms and even hboot versions but I'm too inexperienced to track down the problem.
I'm confused as to your problem... qhusb_dload is a complete brick, yet you say that you can fix it?
Sent from my evita
I'm just as confused as you.
My phone will spontaneously shut down, no lights or anything. When I plug it in and check device manager I see the qhsusb_dload.
But then after I give it some time and fondle the buttons just right it reboots and I'm back to my bootloader.
I can boot into a rom but it usually doesn't last very long (~1hour) before I get a reboot.
The phone isn't always completely bricked...just sometimes?
It is possible to enter that mode without bricking. Typically holding volume up instead of volume down which goes in to recovery, when booting.
How often does it happen?
Sent from my One X using xda app-developers app
It happens about half the time when at boot it and then frequently at rom startup. I've never had any trouble booting into recovery or the bootloader, and it does seem more frequent when the battery is under 40% (but that just may be me.)
I'd say it's down 75% of the time.
Is your phone s-off?
Sent from my One X using xda app-developers app
Yes, but I paid to have it done so I don't know how it was s-offed
So long as its soff in the boot loader that's all that matters. Its a pain in the ass but I would ruu and stay stock to see if it keeps happening.
Sent from my One X using xda app-developers app
Ran the RUU, now my phone won't boot to a rom. I can still get to the bootloader and the recovery though. All I get is a boot loop to the htc white screen if I let it do it's thing.
Ruu and stay stock for a while to see if it keeps happening while stock.
Sent from my One X using xda app-developers app
Today I recieved new nexus 5 32gb. After first steps, google account setup, auto upate 4.4.2, I put phone on charger. After 2 hours I unplug phone from charger, and screen goes black. I tried reboot, and always after google logo screen goes and stays dark. From bootlader I have flashed stock 4.4 and 4.4.2 image and screen stays dark.
When I try from bootlader to recovery, screen stays black too.
What could be wrong with my phone?
Sent from my GT-I9300 using Tapatalk
I am thinking that there is no recovery. Are you able to get into bootloader? As long as you can get into bootloader you are good to go. Id say just flash something through fastboot.
Yes, I can get in fastboot, but in recovery not. I have try to flash from fastboot with flash-all method the stock image 4.4 and 4.4.2. So flashing procedure goes well, after flash phone restarts it self, but stays the same problem with black screen.
So if there no recovery in my phone, should I flash it standalone, or is it included in the stock image?
Sent from my GT-I9300 using Tapatalk
Call google I think they'll replace it since it hasn't been 15days yet
I'm from Slovenia, here is no support from Google. Phone have buy from eBay Germany.
Is there something else what should I try too bring phone back to life?
Sent from my GT-I9300 using Tapatalk
jusko said:
I'm from Slovenia, here is no support from Google. Phone have buy from eBay Germany.
Is there something else what should I try too bring phone back to life?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
is you need to flash the stock images.
there is about 4 toolkits that will do this in the dev section and original dev
Hey guys,
my brother owns a Nexus 5 (duh, otherwise why would i be here )
but anyways, his phone is just stuck at the boot screen. As in as soon as you try powering it on, it shows the Google sign but then it just continually restarts after that. I've tried entering the bootloader but as soon as I access it, it just forcibly reboots without me pressing anything. I'm kind of stuck here as I can't really do anything.
Does anyone have any clue what to do?
Edit: forgot to say he's full stock as in no root, no unlocked bootloader, no recovery etc.
Hi,
Keep the turned off for a bit and then try accessing the bootloader.. From there, go to the recovery and perform a factory reset.
If you can't access the bootloader or it keeps restarting again and again in bootloader, it might be a eMMC failure..
- Sent from an IceCold Hammerhead!
Could the power button be stuck?
Sent from my Nexus 5 using XDA Premium 4 mobile app
vin4yak said:
Hi,
Keep the turned off for a bit and then try accessing the bootloader.. From there, go to the recovery and perform a factory reset.
If you can't access the bootloader or it keeps restarting again and again in bootloader, it might be a eMMC failure..
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
I have certainly tried this. At the moment, im charging it. So let me get this straight, the only way around a dead eMMc chip would be
To RMA and request replacement?
korockinout13 said:
Could the power button be stuck?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have also considered this as well. Is there anyway to get around this? Or perhaps fix this even?
Perhaps its also worth to note that it will only do this when its connected to a charger but when disconnected, it wont even turn on (as in no google sign or bootloader)
Sent from my Nexus 5 using XDA Free mobile app
If it's stock, what happened to cause the situation?
Sent from my Nexus 5 using Tapatalk
Same here - phone was in my bag overnight and off this morning (battery full).
When I started it up it went into boot loop.
Stock ROM, no modifications whatsoever, 2 weeks old phone.
Anybody else?
072665995 said:
I have certainly tried this. At the moment, im charging it. So let me get this straight, the only way around a dead eMMc chip would be
To RMA and request replacement?
Click to expand...
Click to collapse
Yes. Motherboard needs to be replaced in the case of a dead eMMC.
fkoehn said:
Same here - phone was in my bag overnight and off this morning (battery full).
When I started it up it went into boot loop.
Stock ROM, no modifications whatsoever, 2 weeks old phone.
Anybody else?
Click to expand...
Click to collapse
Phones are not meant to be kept in the bag.. May be the bag hit somewhere and the phone took a brunt of it? Who knows??
Or it could also be a random failure..
Can you access the recovery? If so, try a factory reset from there and see whether it boots up?