My phone died last night, and today when I through it on the charger it turned itself on and it's been stuck on the flying dots boot screen and will not fully boot. I've tried a factory reset and nothing. Rooted with Chainfire's CF-AutoRoot, maybe that has something to do with it?
Any help is appreciated. Going to flash the factory images via fastboot shortly.
CaptainSpazzz said:
My phone died last night, and today when I through it on the charger it turned itself on and it's been stuck on the flying dots boot screen and will not fully boot. I've tried a factory reset and nothing. Rooted with Chainfire's CF-AutoRoot, maybe that has something to do with it?
Any help is appreciated. Going to flash the factory images via fastboot shortly.
Click to expand...
Click to collapse
It takes a long time to boot after rooting. I think it has to do with the encryption
Sounds like you have a bootloop. Try to wipe from recovery
How long u let it sit? Mine take a few mins
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
CaptainSpazzz said:
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
Click to expand...
Click to collapse
Yeah that's too long
CaptainSpazzz said:
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
Click to expand...
Click to collapse
Mine did that once. I just held down the power button until it rebooted again and then everything was fine.
Just had this issue again. Shut the phone down, turned it back on, stuck on flying dots for 20 minutes. Maybe its root related. Reflashed stock images again. I won't root again to see if the problem persist.
Related
Hi guys, i have a weird problem here.
I have updated my phone to 5.1 a couple of weeks ago and on friday 08/08 i let the phone discharge completely , put on charger and went to sleep.
When i woke up, tried to power up the god **** phone and it just froze at Motorola Screen, then boot it up to fastboot and tried to Factory Reset him.
Dont know why, it didnt worked, then i unlocked the boot loader and tried to flash via RSD with a Stock firmware of the same version xt1058_ghost_retbr_5.1_lpa23.12-15_cid12_cfc
After flashing everythink looked normal, but the problem persists, Manually flashed GPT.BIN, still doesnt work.
It start, goes to the animated moto logo and later the screen goes off and nothing happens. PLEASE GUYS HELP ME HERE!
(Sorry for the worst english that you ever seen here in xdaforum)
Was running stock 6.0.1 in unlocked mode, and applied the 7.0 OTA Tuesday AM. Phone booted fine, with the exception that the 6.0.1 boot animation displaying. Phone booted into 7.0, so whatever. worked great for 2 days, when i woke up yesterday screen wouldn't turn on, so hold the the power button and re-start. Phone got to boot animation and stayed there for an hour until i shut it off, never got to the pattern unlock screen. I've tried wiping it, factory resetting it, installing TWRP to wipe and install, nothing, still stuck at the boot animation, no matter how long i let it sit. I've tried flashing other roms, with the same results. I can get into bootloader and recovery without issue, and can flash without errors (that i'm aware of) but always have the same result. Any thoughts? Or am i going phone shopping today?
Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Ditto
FUZER384 said:
Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Click to expand...
Click to collapse
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
hypervi said:
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
Click to expand...
Click to collapse
infamous bootloop, hardware issue.?
raptorddd said:
infamous bootloop, hardware issue.?
Click to expand...
Click to collapse
How can i tell if this is indeed a hardware issue ? I am guessing it is though also the serial number falls in the problem range.
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10
Hi, I have an unrooted, unmodified RP2. Out of nowhere, while browsing twitter, the phone shut down and attempted to reboot, but got stuck on the animation right after the Razer logo for hours. I tried shutting it down and starting it up again, letting it run out of battery, and starting again, but nothing seemed to work.
I decided to just factory reset it from the Android Recovery menu, but booting it up again after that gave me a "Your device is corrupt. It can't be trusted and may not work properly" warning. After pressing power to get past that menu, it tries to reboot over and over again with no success. Has anyone else had this problem?
I have had this problem too, it just booted recycle endless. At that time my RP2 is stock Pie MR2 with Trinitykernel, rooted by Magisk.
I turned off it for minutes(10~30 guessed), It can boot successfully.
Now I switched to arter97 kernel, it only happened one time. Wonder it's kernel or system or device problem?
StarHelel said:
Hi, I have an unrooted, unmodified RP2. Out of nowhere, while browsing twitter, the phone shut down and attempted to reboot, but got stuck on the animation right after the Razer logo for hours. I tried shutting it down and starting it up again, letting it run out of battery, and starting again, but nothing seemed to work.
I decided to just factory reset it from the Android Recovery menu, but booting it up again after that gave me a "Your device is corrupt. It can't be trusted and may not work properly" warning. After pressing power to get past that menu, it tries to reboot over and over again with no success. Has anyone else had this problem?
Click to expand...
Click to collapse
Is this resolved?
Can you get to bootloader?