Hello everyone
I have a unique issue with the G2 that I have not really seen before. I rooted my G2 and flashed CM 12 onto it with TWRP. This was about 6-8 months ago. Then, I saw the 12.1 update so I tried to flash it and it failed. I kept trying different nightly builds and none of them worked. Then one day, I could not boot into TWRP at all. The TWRP version has not changed since the day I put it on 2.6.0 and I have not changed anything else. Can anyone please help me to solve this issue because my CM build is starting to show issues and I really need to update it.
Can someone please help me with this???
Related
Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Coxie said:
Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Click to expand...
Click to collapse
If you can enter fastboot mod, just download sbf form http:?/sbf.droid-developers.org/smi/list.php (sorry for the link...) and RSDlite 6.1.4,
Make sure you have drivers installed, enter to fastboot mod, wait untill phone is detected, choose your sbf and let RSD do his job.
Enter in the CWM and try to make a full wipe.
Hi, first off I want to introduce myself since I have been lurking in the forums for some time now but never posted anything. (I am not a developer).
My name is Nicolas, and currently I own a Moto X 2014. (XT1097)
I bought it recently, with lollipop out of the box, and updated via OTA to MM, since I wanted to check what was available to flash I unlocked the bootloader and flashed TWRP to then get root.
All up to this point it was all normal. I proceed to flash CyanPop 4.8 via TWRP, again all normal.
The problem begun when i wanted to flash a MM Stock ROM back, flashed via TWRP and as soon I hit reboot it gets stuck in the M logo with the white backgroud and bootloops there.
I reflashed Stock ROM XT1097, still bootloops, flashed Stock ROM Lite XT1097, still bootloops, flashed Stock rom XT1095, bootloops.
I ended up returning to CyanPop 4.8, (btw, I say its a hybrid in the title because as soon I installed CyanPop, the setup screen told me it was a XT1095)
and cant get out.
I know its kind of messy, but if anyone could bring light to what is going on, I would be extremely grateful, or if anyone knows what to search for to point me in the right direction, also i would be extremely grateful.
Anyway, thanks for all the work you guys do, and for this awesome forum :good::good::good::fingers-crossed:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.
Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.
sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?
istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!
sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.
Hi Guys,
I really need help here. I am using Huawei P9 EVA-L19.
I once unlocked bootloader, installed TWRP and rooted my phone. After 1 day I using it, I tried to flash to unofficial emui 5 which is follow the instruction from here; https://forum.xda-developers.com/p9/how-to/huawei-p9-eva-l19-android-7-0-nougat-t3532649
However, after I done flash it. I found out that there's a lot of application I can't access including my camera ( which totally gone from my phone ). I decided to flash back to emui 4.1.
The issue that I'm facing right now is, I can't even access to TWRP. I tried a lot of ways to install TWRP and try to boot. Nothing happen. I've tried to use Dload, I tried using CMD it seems never success.
Now, I really need someone to help me on this issue. I know there's a lot of people who facing the same issue that I'm facing right now. Or someone who already solve this issue please assist me. I'm already give up on this.
Thanks in advance.
Hi all, just downloaded the most recent update for Lineage, can't seem to be able to use TWRP anymore.
I tried multiple versions of twrp, all resulted in phone not booting.
@LuK1337 any idea what could be the problem?
Xanth0k1d said:
Hi all, just downloaded the most recent update for Lineage, can't seem to be able to use TWRP anymore.
I tried multiple versions of twrp, all resulted in phone not booting.
@LuK1337 any idea what could be the problem?
Click to expand...
Click to collapse
The same thing happened to me. I could not contact the developer.
I will install the stock ROM again. This phone has hardly any development, it's not worth the hassle.