My wife's 7" Kindle Fire HD keeps rebooting into the TWRP recovery. I had rooted it and installed a custom ROM several months ago, but could never get it stable and working correctly. So I gave up and restored the original images backup and all was well for several months. She used it quite regularly without issues.
Then a couple of weeks ago, she would charge it up 100%, use it to read then go to bed. By the next evening it would be as dead as a door nail. So thinking it was a bad battery I did some investigating and found that when she puts it into standby mode it will eventually reboot and go into TWRP. Of course it never enters sleep mode while on the recovery screen and the battery will eventually run down.
A couple of notes - If I reboot it to the system from TWRP but never unlock the screen it never reboots to recovery. Only when I unlock the screen and enter the Home screen, or open ANY program will it eventually reboot to TWRP.
I am suspecting that some program updated itself and that is causing the problem, but since she has numerous programs and I had auto update installed it is impossible to know which one is the culprit.
It is running software version 7.4.8_user_4849020, TWRP 2.6.3.1
Has anybody seen this issue? Any suggestions?
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
SafinWasi said:
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
Click to expand...
Click to collapse
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
pastorbob62 said:
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
Click to expand...
Click to collapse
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
pastorbob62 said:
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
Click to expand...
Click to collapse
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Bao289 said:
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Click to expand...
Click to collapse
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
pastorbob62 said:
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
Click to expand...
Click to collapse
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
NO one can access Prime videos outside of a Kindle OS. It seems like the one thing devs can't crack yet.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Bao289 said:
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
Click to expand...
Click to collapse
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
pastorbob62 said:
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
Click to expand...
Click to collapse
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Bao289 said:
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Click to expand...
Click to collapse
Can't seem to locate a version of Fire Flash to download. Where might I find it?
pastorbob62 said:
Can't seem to locate a version of Fire Flash to download. Where might I find it?
Click to expand...
Click to collapse
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Bao289 said:
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Click to expand...
Click to collapse
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
pastorbob62 said:
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
Click to expand...
Click to collapse
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Fabulous!! I now have a nice 7" tablet with decent resolution, performance and all of the accessibility to Android apps that my 10.1" tablet has.
Thank you to all for your help.
Bao289 said:
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Click to expand...
Click to collapse
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
No Problem make sure you are updated to the latest cm11.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
SafinWasi said:
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Yup! Been using ART on my TF300T for about six months so I enabled it on this tablet too.
ART runs circles around Dalvik as far as performance is concerned. I've heard that there are some apps that won't run with ART and Xposed Framework is not compatible with it, but I don't use Xposed and I have never run into an app that has caused me any problems.
Hi all,
Let me start off by saying hello. I just joined these forums, and sadly I already have to bother you with an issue. Hopefully you can help me.
Recently, I decided to unlock the bootloader of my Moto G 2014 and install CM12.1. Sadly, Cyanogenmod stopped working after I installed Google Apps (from OpenGApps).
I then installed stock Marshmallow, using this tutorial. It got stuck on the boot animation.
Finally, I installed the stock Lollipop 5.0.2 firmware (the version I came from). It works now, but everytime I power the device up, it boots straight into TWRP. I can boot it normally using the bootloader, though. Also, when I try to lock the bootloader again, it won't boot at all (probably because I have TWRP on it).
This isn't an issue for me, but I upgraded to a Nexus 5X yesterday, and I'm giving my Moto G to my little sister, who is currently using a Nokia Lumia 635. I want the device to function as it should before I give it to her. Therefore, I'd like to do a complete wipe of my phone, and install the stock firmware, just like it was before I unlocked the bootloader. I could use some help with it.
My main concern is the fact that it boots into TWRP. Is there any way to fix this? Can I install the normal recovery mode again?
As for the firmware I was using, it was Android 5.0.2:
System version: 22.21.28.titan_retaildsds.retaildsdsall.en.03
Kernel version: 3.4.42-g48d3b85
Build number: LXB22.46-28
I can provide additional info, as I do have the stock ROM installed atm.
Thanks in advance!
P.S. I do also have SuperSU installed on the phone, but it says there is 'no SU binary installed'. It seems something went wrong there as well. Not too bothered by it, as I don't want it rooted, but I figured it was worth mentioning.
I flashed the twrp recovery through lenovo note manager 3.1 and install the cm 14.1 ROM (unofficial)
But problems starts coming up: After I install CM 14, install root checker and it said my devices is not rooted!
Also the system don't detect my SIM card although I have put in already...., It kind of bothered me cuz I need mobile network much, is there any solution to this???
Also CM waste a lot of battery.....
When will the official CM 14 come up? I am really looking forward to that since it may solve the problem.
And can any tell me why my devices isn't root , I thought there is a built-in root….......
Hi I'm currently running the s9 port oreo rom beta 1 still
It's a bit buggy and a few bits and pieces that annoy me on it
Can I flash a custom nougat rom over it without having to wipe?
I really really cannot be bothered installing all my apps and everything again and signing in again
I'm not rooted also
I do have TWRP installed tho
jacksskinz said:
Hi I'm currently running the s9 port oreo rom beta 1 still
It's a bit buggy and a few bits and pieces that annoy me on it
Can I flash a custom nougat rom over it without having to wipe?
I really really cannot be bothered installing all my apps and everything again and signing in again
I'm not rooted also
I do have TWRP installed tho
Click to expand...
Click to collapse
no, you need to full restore with odin to go from 8 to 7, bootloader etc needs flashed, use smart switch to backup to sd card and restore back when done
Hey guys,
So, I've got a Redmi Note 9, not that I'm not happy with the stock firmware but the reason I got this phone was so I could play around a bit with other ROMs (had a replacement iPhone X and was just bored with it).
So, I'm not exactly new in Android world, all my previous phones were HTC, Samsung, Nexus, and all rooted and running custom roms.
Just so I don't feck up the process, can someone guide me to the process? I'm guessing I need to root it first, then install the custom recovery and go on from there?
Any specific advice ?
Thank you so much in advance.
Just flash the pathed vbmeta.img together the magisk patched boot.img and your device will be rooted.
I assume it's fine that in on miui 12 official & stable ?
Everything is working perfectly on miui 12 android 10 and miui 12 android 11.
Thanks, I'm going to start digging tomorrow.