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?
Related
I got my moto x today, updated it right away to lollipop, then went to work unlocking the bootloader, rooting, and installing TWRP.
All worked great, and then i went into TWRP to do a factory reset so that I could have the setup wizard when i turned my phone back on to set it up.
well after I did a factory wipe in TWRP (now i am thinking maybe i also checked to wipe system as well, but im not positive).
after the factory reset my device boots to the boot screen, and stops on the blue m logo at the end.
So i flashed the stock kitkat images using mfastboot, and it boots to the boot screen and then shuts off, doesnt even hang at the end anymore.
What are my options/ what the hell did i do?
Just got my XT1095 last week and unlocked the bootloader and rooted the phone (still on 4.4.4). Was playing around with the boot animations last night and all of a sudden my phone froze at one frame of the animation. The weird thing is my phone still works, I can feel the haptic feedback when I press buttons and Moto Voice works too, but I just can't see anything on the screen except the frozen boot animation. After restarting the phone several times, the same thing happens.
Tried to push some stuff to phone and realized i might not have re enabled usb debug after unlocking bootloader..
Friend suggested updating to 5.0 and see if that resets boot, but I can't even fully load Moto Device Manager it says "Update is Already in Progress" and closes.
Any ideas how to reset everything or restore stock boot animation?
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
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?