Develop Bugs

[Q] Unable to install CM11 or latest TWRP

I have an Amazon Kindle Fire running FFF 1.4a, TWRP 2.6.0.0 and CM10.
Trying to install the latest CM11 ROM, but when I flash it, the Kindle goes into and endless reboot cycle (It says "Booting" at the bottom, then reboots, and repeats).
So then I tried installing the latest TWRP using the Kindle Fire Utility (also tried with adb) and it appears my Kindle cannot reboot into fastboot mode to allow the upgrade to take place. When the Kindle receives the "reboot into fastboot" command, it reboots, but I just get the TWRP menu with "Normal" and "Recovery" choices.
Luckily I can flash my old ROM and it works fine. ButI would love to upgrade to CM11 if possible.
Is the latest TWRP (2.6.3.1 at the time of this writing) required to install CM11? The post for CM11 states the "latest TWRP" is required.
Thanks!

squiddog said:
I have an Amazon Kindle Fire running FFF 1.4a, TWRP 2.6.0.0 and CM10.
Trying to install the latest CM11 ROM, but when I flash it, the Kindle goes into and endless reboot cycle (It says "Booting" at the bottom, then reboots, and repeats).
So then I tried installing the latest TWRP using the Kindle Fire Utility (also tried with adb) and it appears my Kindle cannot reboot into fastboot mode to allow the upgrade to take place. When the Kindle receives the "reboot into fastboot" command, it reboots, but I just get the TWRP menu with "Normal" and "Recovery" choices.
Luckily I can flash my old ROM and it works fine. ButI would love to upgrade to CM11 if possible.
Is the latest TWRP (2.6.3.1 at the time of this writing) required to install CM11? The post for CM11 states the "latest TWRP" is required.
Thanks!
Click to expand...
Click to collapse
Yes the latest TWRP is required

Is the latest TWRP requirement also necessary is you're trying to install either of the newer HellFire 4.4.xx roms? I'm on 2.2.2.1, (TWRP), and can't seem to get it to work, just pops up an error every time. I had thought about upgrading TWRP, but had read that there were a lot of problems with it. So if I upgrade to the latest TWRP, should this sole my HellFire problem?

So, for some reason, I cannot get TWRP to update. I tried both GooManager and ROM Installer apps. They both try to install TWRP but are unable to get the device to reboot into fast mode. In fact GooManager claims that TWRP was installed successfully, but then the reboot fails. When I go back into TWRP, it is still the old version.
Any ideas how to solve this?
Thanks!

You need to flash the version that hashcode updated specifically for the Fire. Link below, flash like any other zip.
TWRP 2.6.3.1 by Hashcode
It will still say 2.6.3.0 but it is updated and will work with cm11 ROMs
Sent from my Nexus 7 using Tapatalk

That did the trick. Thanks!

[Q] Xposed, TWRP, Bootloop, Help!?!?!?!

Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.

sgtfrnz said:
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
Click to expand...
Click to collapse
Well something was messed up when you flashed xposed installer( i don't know what you mean by automatic method) but do a clean install,since you can get into download mode,grab the twrp img.tar and flash it using pc odin ,then you can access recovery, do all the wipes again by going under "advanced" and reflash your rom.Now to install xposed go to xda thread for it and grab the apk from there (i think it's available on play store as well).You should have no more issues
Twrp

Like the previous post said I'm not sure what you've done. When xposed framework is installed there is usually an unistall zip created on the internal so card. If you can get recovery find it and flash it
Sent from my GT-N7105 using Tapatalk

The device is now fixed.
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.

sgtfrnz said:
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
Click to expand...
Click to collapse
Boot into Download mode and flash philsz touch recovery 6 and reboot device .. Everything will be ok>

Old thread may be old, but it's still relevant.
I just tried to install XPosed as well on my Note II and it did the same thing (mine's AT&T)
Info
Device: Note II
XPosed Version: 2.6.1
Install Method: "Recovery (flash zip automatically)"
Recovery Image: TWRP
Mine exhibited the same behavior as OP's, however after leaving it alone for a while to bootloop recovery as much as it wanted to, I came to my laptop, found this post, grabbed as USB cable, and I was just about to start the process of reflashing recovery when all of a sudden I saw my lock screen.
It took roughly five minutes of bootloop to get it there, but it successfully installed XPosed and my device is running fine.
So, for all the other Googler's out there that landed on this post, leave it alone for a while! See what happens. If it's still bootlooping, like, 30 minutes later, then try reflashing TWRP using ODIN. If that still doesn't work, reflash a new ROM using TWRP.

Cannot install CM11 no matter what

Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.

TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?

Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood

TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?

I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.

Trying to fix a recovery/gapps issue

I have a Samsung Galaxy G4 (T-Mobile version). I had a boot loop on Recovery problem with it. I reflashed the recovery a couple of times, TWRP and CM recovery. Neither wants to start up when I try to boot into recovery. (I have tried adb and using the keys.) Usually when I would flash a new kernel it would drop into recovery. When I upgraded to the nightlies, it went into recovery, installed the kernel, and rebooted.
Now I have a CM 13 kernel, but I am missing the proper gapps package.
Is there a way to install the gapps package with heimdall? Is there a trustable twrp app I can sideload? Is there a trick to get gapps to install with adb?
Looking for a useful solution. Thanks!

After flashing twrp using Odin, are you immediately trying to boot into recovery or are you restarting the phone and booting the rom?

Kindle Fire HD 8.9 (Jem) stuck at TWRP startup screen

I've been using the Fire HD 8.9 (Jem) with CM (a 2015 version of CM 12.1) with TWRP 2.7.0 without much of a problem. Yesterday, I flashed the latest CM12.1 nightly (20161216 version) using the same TWRP successfully. After the initial loading, I tried to factory reset the tablet. Once the pad restarted, it goes into the TWRP startup screen, and doesn't load the touch interface. The startup screen will flash every 5 seconds or so. I can't go back to normal boot either. Can anyone help? Thanks.

Have you fixed this yet?
If not, I'm not certain, but could be a mismatch between your older TWRP version and the most recent CM12.1 nightly. Can you actually use TWRP? Did you make a backup prior to installing the newest CM version (always imperative to do)? If so and TWRP works, simply wipe everything and reinstall your backup. Then first update TWRP (I'm using v 3.0.0) by multiple methods and try again. Does you computer still see your Kindle? If so, download a newer version of TWRP to your computer, transfer it to the Downloads folder of your "SD Card" on internal storage, and flash from there using TWRP. Try to keep plugged in so that battery stays in good shape.
If you can't use TWRP, you'll have use Fastboot to flash a newer TWRP version from your computer. Look for instructions on how to setup and then use Fastboot if you've never used this before. Some drivers that your computer may or may not have will be required. Good luck!

wicozani said:
Have you fixed this yet?
If not, I'm not certain, but could be a mismatch between your older TWRP version and the most recent CM12.1 nightly. Can you actually use TWRP? Did you make a backup prior to installing the newest CM version (always imperative to do)? If so and TWRP works, simply wipe everything and reinstall your backup. Then first update TWRP (I'm using v 3.0.0) by multiple methods and try again. Does you computer still see your Kindle? If so, download a newer version of TWRP to your computer, transfer it to the Downloads folder of your "SD Card" on internal storage, and flash from there using TWRP. Try to keep plugged in so that battery stays in good shape.
If you can't use TWRP, you'll have use Fastboot to flash a newer TWRP version from your computer. Look for instructions on how to setup and then use Fastboot if you've never used this before. Some drivers that your computer may or may not have will be required. Good luck!
Click to expand...
Click to collapse
Can't use TWRP, fastboot don't work, tryed almost everything on this forum.

nickelocene said:
I've been using the Fire HD 8.9 (Jem) with CM (a 2015 version of CM 12.1) with TWRP 2.7.0 without much of a problem. Yesterday, I flashed the latest CM12.1 nightly (20161216 version) using the same TWRP successfully. After the initial loading, I tried to factory reset the tablet. Once the pad restarted, it goes into the TWRP startup screen, and doesn't load the touch interface. The startup screen will flash every 5 seconds or so. I can't go back to normal boot either. Can anyone help? Thanks.
Click to expand...
Click to collapse
I had the exact same problem but I got into fastboot mode by using this adb command
Code:
adb reboot bootloader
have you tried this yet?