I have a rooted HDX 7" 3rd gen that I have been running CM 11 on using Safestrap, and I would like to try and get a different rom running on it. I did a factory reset back to FireOS 4.5.2. I'd really love to get CM 13 running, but I'm not sure how to do it or if it's even an option at this point. I am trying to make sense of my different options but I'm pretty confused at this point. Am I stuck with CM 11 for now or is this even possible? If not is CM 12 or Nexus a possibility? Thanks!
You can NOT use CM13 and CM12 with Safestrap v4! Both require an unlocked bootloader, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (attempt would brick the device), thus you can't unlock the bootloader.
You can use CM11 or Nexus for Safestrap v4 only.
matt_2_27 said:
I have a rooted HDX 7" 3rd gen that I have been running CM 11 on using Safestrap, and I would like to try and get a different rom running on it. I did a factory reset back to FireOS 4.5.2. I'd really love to get CM 13 running, but I'm not sure how to do it or if it's even an option at this point. I am trying to make sense of my different options but I'm pretty confused at this point. Am I stuck with CM 11 for now or is this even possible? If not is CM 12 or Nexus a possibility? Thanks!
Click to expand...
Click to collapse
Cl4ncy said:
You can NOT use CM13 and CM12 with Safestrap v4! Both require an unlocked bootloader, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (attempt would brick the device), thus you can't unlock the bootloader.
You can use CM11 or Nexus for Safestrap v4 only.
Click to expand...
Click to collapse
Pretty amazing your device survived the factory reset. In most cases that yields an instant brick when Safestrap v4 recovery is installed/active. Did you have CM 11 installed in the stock slot or a secondary slot (eg: slot 1)?
Davey126 said:
Pretty amazing your device survived the factory reset. In most cases that yields an instant brick when Safestrap v4 recovery is installed/active. Did you have CM 11 installed in the stock slot or a secondary slot (eg: slot 1)?
Click to expand...
Click to collapse
I had the stock rom in the stock slot and had CM 11 in a secondary
matt_2_27 said:
I had the stock rom in the stock slot and had CM 11 in a secondary
Click to expand...
Click to collapse
That's not the recommended configuration and likely contributed to a sub-optimal experience. Issues:
- only 2 of the 4 processor cores can be used (poor performance under load)
- those two core run at 100% all the time (poor battery life)
- device never deep sleeps (variety of issues including thermal)
- wifi radio is slow to engage during power transitions
- limited user space for apps/data
- instant brick if a slot backup is restored to the stock slot or vice versa
Custom ROMs should always be installed in the stock slot (overwriting FireOS) with Safestrap v4 which is exclusive to HDX 3rd gen devices. A safestrap compatible version of FireOS can be flashed if needed allowing the device to return to stock. Secondary slots should not be created/used.
Davey126 said:
That's not the recommended configuration and likely contributed to a sub-optimal experience. Issues:
- only 2 of the 4 processor cores can be used (poor performance under load)
- those two core run at 100% all the time (poor battery life)
- device never deep sleeps (variety of issues including thermal)
- wifi radio is slow to engage during power transitions
- limited user space for apps/data
- instant brick if a slot backup is restored to the stock slot or vice versa
Custom ROMs should always be installed in the stock slot (overwriting FireOS) with Safestrap v4 which is exclusive to HDX 3rd gen devices. A safestrap compatible version of FireOS can be flashed if needed allowing the device to return to stock. Secondary slots should not be created/used.
Click to expand...
Click to collapse
Good to know! There wasn't anything I saw during my research about this when I first set it up with CM 11.
Also, does anyone know of a way to get Wii Remotes to work with either CM 11 or Nexus. I know they don't seem to work with Android 4.2 and higher and since both CM 11 and Nexus are running higher versions am I out of luck?
Related
My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
WnG88 said:
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
Click to expand...
Click to collapse
Is there a particular set of instructions you followed?
Sent from my Nook Tablet CM 10.21
nmyshkin said:
My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Click to expand...
Click to collapse
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
digixmax said:
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
Click to expand...
Click to collapse
Thanks! I've been following a couple of related threads for awhile now. The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
nmyshkin said:
...
The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
Click to expand...
Click to collapse
Unless you plan on using the uSD card also to backup your current ROM and setup for ease in rolling back (which is a good idea), you don't need an external uSD card to upgrade from CM10 to CM11/12.
I recently rooted and installed cyanogenmod with TWRP on my Kindle fire hx 8.9 (3rd gen) , and i've noticed with Cyanogenmod 11, there's a major battery drain, and i can't seem to find any solutions on it, so i thought maybe i should just update to a more stable build, can anyone point me in the right direction, or possibly help me out regarding updating from 11 to a higher version, thanks in advance, if i've missed anything out, let me know
I used this guide http://forum.xda-developers.com/showpost.php?p=62741307&postcount=2
If you used the linked guide, you DO NOT have TWRP, but Safestrap v4, so you can use CM11 or Nexus for Safestrap v4 only. You need the REAL TWRP and an unlocked bootloader (you probably don't have that either?) in order to use CM12/CM13!
It is recommended to use the stock slot, because there're certain issues (incl. battery) when using secondary slots. Note: you MUST NOT restore a backup of a secondary slot to the stock slot! This would overwrite Safestrap files and brick the device!
Create a backup of your stock slot, and the secondary slot (always remember to NOT restore any secondary slot backups to the stock slot!), remove the secondary slot, then install CM11 to the stock slot. Make sure you understand the risks of using the stock slot before you flash anything to it!
Mr Habbz said:
...i've noticed with Cyanogenmod 11, there's a major battery drain, and i can't seem to find any solutions on it
Click to expand...
Click to collapse
Clearly didn't spend much time searching as this issue is discussed in multiple threads and dozens of posts. As noted by @Cl4ncy custom roms must be installed to the stock slot in Safestrap v4. Battery drain is just one of many issues associated with secondary slots.
Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Zathor said:
Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Click to expand...
Click to collapse
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Davey126 said:
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Click to expand...
Click to collapse
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Zathor said:
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Click to expand...
Click to collapse
- hold on bootloader update as there was a recent report of an unfavorable outcome (bricked device); need to see how that plays out
- for 13.3.2.4 root with TowelRoot and then proceed with bootloader unlock; keep device off network (WiFi off) except when rooting to prevent an OTA update; no need to update FireOS for bootloader unlock - root is sufficient
Ok, I will wait with the bootloader update for Thor, for Apollo I have already done it sucessfully yesterday (see first post).
I tried a few additional custom roms:
- cm-11-SAFESTRAP-20161016-UNOFFICIAL-apollo: OK
- cm-12.1-20160922-UNOFFICIAL-apollo: OK
- cm-13.0-20161108-NIGHTLY-apollo: OK
- cm-14.1-20161218-NIGHTLY-apollo: NOT OK
So the screen stuck in one orientation seems to be a CM 14.1 problem only.
To be honest I do not know why, but the problem is solved. After dirty flashing (without wipe) from cm-13.0-20161108-NIGHTLY-apollo to cm-14.1-20161218-NIGHTLY-apollo the automatic screen rotation does work now. Even after a full wipe and a clean installation of CM 14.1 (which I always did before), it does work now.
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Bawdy George said:
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Click to expand...
Click to collapse
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Davey126 said:
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Click to expand...
Click to collapse
Thanks for the reply. Odd, huh? Though... I did just try ggow's 4.05 ROM and that one autorotates just fine on the Thor I'm currently working on. I'll probably just go with that one or the newer with locked rotation. They're both solid, support Xposed, and app compatibility isn't an issue for my use cases... yet. If only BT wasn't such a challenge on later versions, as that LineageOS ROM is looking really really good...
Never seen that error myself , 5 hdx's unlocked either 4.5.5.1 or 4.5.5.2 all with Nexus KK on them. Another two ready to be unlocked when I've time.
Maybe you've been unlucky and downloaded slightly corrupted files that appear to flash ok. Maybe check the hash value of them ?
Hi guys,
I've flashed my Nexus 6 with Stock Lite without encryption and the phone is working very well. I was hoping to find stock like for the nexus 9 but it seems there is no version of it for Nexus 9.
What firmware would you guys recommend that is the closest to stock android, of the less bloated without encryption enforced that I can put on my nexus 9?
My model is the 16GB WIFI only
Thanks!
My AOSP is closest to stock, followed closely by Noobbuilds and Pure Nexus - all excellent, but there are other good ROMs worth checking out too. I recommend Fire-ice kernel
Hmm, I'm having problems trying to install twrp on the nexus. I unlocked the bootloader, then flashed using fastboot flash recovery twrp.img but when I press power and volume up, I can't get to twrp, it keeps booting to the normal android bootloader.
Am I missing something? :/
Mephisto_POA said:
Hmm, I'm having problems trying to install twrp on the nexus. I unlocked the bootloader, then flashed using fastboot flash recovery twrp.img but when I press power and volume up, I can't get to twrp, it keeps booting to the normal android bootloader.
Am I missing something? :/
Click to expand...
Click to collapse
You have to reboot straight into recovery after installing, or it'll be overwritten
I just got myself a Nexus 9 – have been meaning to get one for a while to tinker with, and found one in mint condition for relatively cheap. Got it with stock 7.1.1, but it didn't feel as snappy as I'd hoped, so I flashed Lineage OS and that left me with the same feeling. I'm now running decrypted stock 7.1.1 with magisk for root, and it's pretty much as snappy as my OnePlus 3. Haven't tried any other ROMs decrypted, but I'm pretty sure the same applies. Lacking encryption hardware acceleration, the Nexus 9 just isn't meant for encryption.
To disable forced encryption in stock 7.1.1, I used xda user gladiac's FED-Patcher (should work for any ROM): https://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422
Choochter said:
You have to reboot straight into recovery after installing, or it'll be overwritten
Click to expand...
Click to collapse
yep, that was it, thanks!
olapel said:
I just got myself a Nexus 9 – have been meaning to get one for a while to tinker with, and found one in mint condition for relatively cheap. Got it with stock 7.1.1, but it didn't feel as snappy as I'd hoped, so I flashed Lineage OS and that left me with the same feeling. I'm now running decrypted stock 7.1.1 with magisk for root, and it's pretty much as snappy as my OnePlus 3. Haven't tried any other ROMs decrypted, but I'm pretty sure the same applies. Lacking encryption hardware acceleration, the Nexus 9 just isn't meant for encryption.
To disable forced encryption in stock 7.1.1, I used xda user gladiac's FED-Patcher (should work for any ROM): https://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422
Click to expand...
Click to collapse
But it says 7.1.1 is not supported?
somebody tell how to disable encryption on nougat 1 CM/linage roms. I used WUG toolkit to flash no-encrypt kernel and got twrp bootloop instead, unable to mount storage, system, data