Hello,
I recently was running Cyanogenmod 10.1.3 (i think... it was the latest stable build) when I got a notification to update to 10.2.1. I did so through the cyanogen updater and it seemed to work fine but the phone would randomly reboot. Finally it did so but remained at the initial loading screen. I then booted into TWRP and flashed the 10.2.1 again. Same deal it just wouldn't boot it remained frozen. I then tried to reflash 10.1.3, the previous version I was running. The phone imediatley booted into fastboot with a flash failure indicator despite TWRP saying it had been sucessful. I have since tried to install the Mototola's OEM firmware, as well as do a restore from a backup I had made in TWRP. nothing works and I can't move past fastboot. Im interested to know why this is happening and how I can reflash properly without getting an error? Any replies will help. Thanks.
-Justin
Related
Randomly crashed this morning, now it is in a perpetual bootloop no matter what I do.
I have a Nexus S 4g
I did a factory reset and that didn't work.
I tried to use CWM USB mounting to copy over a new rom and that didn't work.
I updated CWM to the latest version and sideloaded CM10.1.2 and the latest gapps, and yet the bootloop persists. I'm positive that it installed both of these zips successfully.
My last resort was trying to return it to stock using a a 2.3.4 image and relocked and unrooted. Still won't boot up.
What can I do to fix this? I'm confused. Is it possible that my phone is entirely broken?
When I received my phone a couple weeks ago, I unlocked the bootloader and installed TWRP. DIdn't root, as I had already updated to 33R. A few days ago I decided to encrypt the phone, which went smoothly. The only issue is that now when I attempt to boot to recovery, I get the stock CM recovery, not TWRP. Yes, I unchecked the update CM recovery in developer options. I tried to re-flash TWRP this morning, and it appeared to work fine, ADB indicated success, but upon reboot again I still only boot to CM recovery, not TWRP.
I've seen some anecdotal evidence that encryption does indeed mess with the recovery and make it less usable, but I thought that TWRP was one of the exceptions to this. Just curious for others' experiences with this.
I'm running TWRP 2.801 with encryption and it works fine, doesn't revert on reboot. Not sure if it matters, but I'm running CM11 nightly and applied TWRP via fastboot
I rooted my phone by unlocking my bootloader, putting philz touch recovery, and flashing superSU.zip. After using my phone with root for a while, i noticed that some things were really unstable and buggy, such as it wouldn't charge, so i decided that i might as well flash cyanogenmod 12 since i have a recovery. This was my first mistake, as flashing cyanogenmod put my phone into an infinite boot animation screen. I then used adb to sideload the official Motorola 5.1 update. But this also gave me an infinite bootloop. I tried flashing cyanogenmod 12.1, that also didnt work. I tried flashing stock android 5.1, also bootlooping. I did some searching and i found that my bootloader was not recent enough to flash lollipop roms. So i tried again after updating my bootloader, and now its even worse. It doesn't even attempt to start up, it just goes straight into recovery mode as soon as i boot it up. It also has this strange screen flickering/glitching going on, like this. I don't even know where to go from here so any help would be greatly appreciated.
Some extra info:
I did clear all cache before flashing.
Model number is XT1032
Bootloader version is 4118, before it was 4113.
I recommend flashing a stock 4.4.4 ROM to your phone using fastboot commands. Do no flash anything older than 4.4.4.
Flash cm11 first. I had the stuck at bootanimation. On cm 12.1 flashed 11 then wiped and flashed 12.1 and all is Good
Good Afternoon!
Here's the story:
I encrypted my phone.
I installed TWRP 2.8.6.1 Official.
I (tried) unsuccessfully to dirty-flash a ROM to fix a systems partition problem.
My phone gave me an encryption error and told me to format my phone.
I formatted my phone using TWRP and installed OxygenOS again.
My phone is now bootlooping into TWRP.
I've tried downloading OxygenOS again.
I tried formatting my phone again.
I tried a different OxygenOS Rom.
I tried CyanogenMod 12 Nightly.
Everything bootloops back to recovery.
I'm currently trying to find a Factory Image for the O+O and go back to CyanogenMod 11S to (try) and get it to just boot.
Is there anything I haven't tried? Any advice?
Thanks.
I flashed 11S via fastboot and then upgraded to a version of Cyanogenmod12.1 I found via the forums.
The stock CyanogenMod kept getting stuck in the middle. OxygenOS won't install, period.
My phone hates me.
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
ali4ek said:
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
Click to expand...
Click to collapse
Not sure I got any advice since you've already tried what I would've suggested. I sideloaded SuperSU-v2.79-201612051815.zip by booting into TWRP through fastboot and it worked for me. I read in another thread that some people were stuck on the nvidia logo for a good 15 mins and then it was fine. How long did you wait? I flashed TWRP after rooting because flashing it through fastboot wouldn't stick, but I can't see how that could matter.
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Sokraates said:
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Click to expand...
Click to collapse
I've been following the threads throughout the day and it seems to be a common problem after using flashfire. There's a thread on a potential fix here:
https://forum.xda-developers.com/shield-tablet/help/k1-fix-able-to-charge-tablet-ac-adapter-t3554261