I was using the July 18 build for awhile now. Today I was trying to upgrade it to the Aug 11 build, and both the twrp and cwm recovery refused to install it, citing incompatibility unless I factory wiped it.
What gives?
TIA.
andtron said:
I was using the July 18 build for awhile now. Today I was trying to upgrade it to the Aug 11 build, and both the twrp and cwm recovery refused to install it, citing incompatibility unless I factory wiped it.
What gives?
TIA.
Click to expand...
Click to collapse
Others have reported this. UseTitanium Backup to backup everything and wipe like it says and install and use TB to restore.
Sent from my SCH-i705 using XDA Premium HD app
I finally figured out why.
I removed a lot of bloatwares from the system apps (camera etc), and trwp and recovery don't like it. Apparently removing apps failed the checksum verification, hence no update.
Maybe the recovery sw should relax a bit .
Related
Hi. I'm currently running a nightly build of CM9 on my Touchpad that's about a month old (07/21, I think). I'd like to update to a newer nightly, but I'm worried about getting Flash. Will I be able to reinstall Flash from the Play Store after I wipe everything and flash a new nightly, or should I be looking at saving the Flash I have installed now? I know it won't work with CM10, I'm just wondering about a newer CM9.
Tired_ said:
Hi. I'm currently running a nightly build of CM9 on my Touchpad that's about a month old (07/21, I think). I'd like to update to a newer nightly, but I'm worried about getting Flash. Will I be able to reinstall Flash from the Play Store after I wipe everything and flash a new nightly, or should I be looking at saving the Flash I have installed now? I know it won't work with CM10, I'm just wondering about a newer CM9.
Click to expand...
Click to collapse
I started on nightly's in June and am now on the latest one and still have flash. Plus my daughter's which has just come back from HP after being repaired and therefore had a fresh install, was able to search and install flash after I put on the latest nightly then ran one of her backups in order to restore her settings and updated again .
Both machine's are/were also backed up to our Google accounts.
I hope this helps.
sstar said:
I started on nightly's in June and am now on the latest one and still have flash. Plus my daughter's which has just come back from HP after being repaired and therefore had a fresh install, was able to search and install flash after I put on the latest nightly then ran one of her backups in order to restore her settings and updated again .
Both machine's are/were also backed up to our Google accounts.
I hope this helps.
Click to expand...
Click to collapse
Did you do full system/data/cache/factory-reset wipes between nightlies (or even just once since Aug 15th), or did you just install them over top of the last one?
Tired_ said:
Did you do full system/data/cache/factory-reset wipes between nightlies (or even just once since Aug 15th), or did you just install them over top of the last one?
Click to expand...
Click to collapse
On mine I installed over and did cache/davlik wipes plus the occasional re-flash of gapps.
My daughter's was a fresh install on Wednesday when I got it back from HP plus I used a backup once to reestablish her settings before again flashing the latest nightly
Trust this helps.
Just had an update notification for flash , nervously hit the update button and all is still good !
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.
The title says it all. Basically, I'm planning on doing an OTA upgrade from CM11 M10 to M11, and I want to know if there's any reason not to do this. I've done OTA for all the M builds since M8, but M11 is still so new that nobody has yet made a thread like this. Literally, googling "m11 ovation" yields nothing useful except the blog post and official download link.
Specifically, are there any driver/app issues, any glitches anywhere that don't appear in M10? Any apps that would interfere with the OTA? Any removed features not mentioned in the changelog or added ones that I might not want? Is there a corrupt package that will brick my tablet, as sometimes happens in the early days of a build rollout? Basically, anything, at all, anywhere that I should know (and the blog post won't tell me) before hitting the download button.
I've checked and even searching "m11 ovation" on CM Jira doesn't return anything newer than M8. My recovery version is the most recent required CWM upgrade for Cyanogenmod, I believe M8 or M9.
There should be no reason you should not be able to successfully update from M10 to M11 using the built in CM update feature. Just make sure that you have CWM version 6045 or newer installed to internal memory. If you don't, go to the dummies guide linked in my signature and install v6046 from post 7 there before attempting the update. And in case you want to revert to M10, boot to CWM and do a backup of M10 before updating.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
There should be no reason you should not be able to successfully update from M10 to M11 using the built in CM update feature. Just make sure that you have CWM version 6045 or newer installed to internal memory. If you don't, go to the dummies guide linked in my signature and install v6046 from post 7 there before attempting the update. And in case you want to revert to M10, boot to CWM and do a backup of M10 before updating.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I just rebooted into recovery and the version number says 6.0.4.6, so its all good. Update is in progress. So far its working, the little blue bar under the spinning Android thing is moving as expected, and the bootloader has successfully passed the baton to the OS, so no signs of a boot loop yet either.
Update is in progress. So far its working, the little blue bar under the spinning Android thing is moving as expected, and the bootloader has successfully passed the baton to the OS, so no signs of a boot loop yet either. The "Android is upgrading optimizing apps" screen has just popped up and is progressing nicely too. So far this is shaping up to be a replica of M10 but with most glitches gone and massively improved (we're talking sub-30secs whereas M10 would take easily 2-3 minutes).
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.
Good Morning Everyone! I decided to open this discussion hoping someone could help me solve or at least understand the problem I have been having on my Nexus 6 with Android N Preview. So, I have the Nexus 6 since April and I got it from a friend who sold it to me. At that moment the phone was already enrolled in the Beta Program, and was running one of the first previews. But here came the problem. In fact I wanted to unenroll the phone but when I enter the Beta Program page, my Nexus does not appear as eligible device nor I can unenroll it from there. I looked at Device Manager and it shows my Nexus 6, but I actually could not do anything to unenroll it. I tried flashing a Marshmallow build with NRT but as soon as I turn on my phone, an annoying notification shows up, saying I can update to the N preview. So, how can I try to uneroll my Nexus 6? My friend says he is not able to do it for me, cause he doesn't see the device on his account anymore. What do you suggest me to do?
Thanks in advance, guys!
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
NLBeev said:
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
Click to expand...
Click to collapse
Thanks for your tips, man! I have some questions about: with this procedure I'm going to install a custom ROM, but if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved in the same way in your opinion or will I get the notification about the preview again? What if I try to access with another different account after that in your opinion?
Ste293919 said:
.... if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved.....
Click to expand...
Click to collapse
You need to delete the current account and do a factory reset.
For going back to stock there is a tutorial,
http://forum.xda-developers.com/showthread.php?p=57063390/
So I managed to go back to android MM after enteting a new account and unenrolling my Nexus 6 from Beta Program. Now everything seemed fine but then after I updated back with the OTA I received, I noticed my device has still July Security patch. I thought Google would have sent me September ones, so I tried to check manually and waited a whole day, but nothing happened. Coukd it be a problem related to bad installation in your opinion? Do you suggest me to restore September build through NRT?
Thanks for all your help man, I owe you and thanks you for your time!