I have CM 12.1 currently install on my Amazon Fire tablet could I flash Fire Nexus Rom on it or will it end up bricking?
clittlej said:
I have CM 12.1 currently install on my Amazon Fire tablet could I flash Fire Nexus Rom on it or will it end up bricking?
Click to expand...
Click to collapse
Shouldn't be a problem. Include a partial wipe (system/dalvik/cache) as the *first* action in the FlashFire operations sequence. If necessary relocate wipe to the top of the queue (long press and drag) as other actions are added. After flashing Nexus should boot up with your existing apps/data portfolio intact.
In some cases the user/data partition must also be wiped when switching roms. This is particularly true going to/from FireOS. That said, you should be ok transitioning between the Lollipop builds of Nexus and CM on this device.
i have swapped between fire nexus and cm 12.1 and back with no problems, as davey126 said wipe system, davlik and cache and there shouldn't be a problem
Related
Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
kaceps said:
Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
Click to expand...
Click to collapse
I personally never had this happen to me but it seems you forgot to flash gapps and the rom seperately. If you need a backup of the amazon os I have one because, I switch every 15min to check performance. I can give you a twrp backup it will work though. Also what guide did you use because I think you should have used this one http://forum.xda-developers.com/showthread.php?t=2271909 I used to root and install CM10. I encounter the same problem when trying to mount to the computer in twrp, its an issue, but not the main problem. Is it a problem currently or is it working? But use that guide and tell me how it works for you.
I flashed ONLY the rom ... the gapps where on the memory for later flashing.
But guesss what, I just randomly succeded.
Here is what I did
- Wipe cache / davlik cache / system / factory reset (in that order)
- Flash EVERYTHING at the same time. Meaning a rom (the 514 from hashcode) gapps, and the 2 zip for acid audio. I put them all in install before flashing.
- Do NOT re-wipe anything after flash. Just reboot
And it worked ...
After a lot of reading and research, I got root/twrp/cm11 on my new kindle. It originally was on 7.4.7, but I thought I had to downgrade. After forgetting to turn off OTA updates it upgraded to 7.4.6.
I don't know if this is a factor, but after I got CM11 running, I tried to flash the corresponding GApps in TWRP. After flashing I got stuck in the blue bootloop. I reflashed the ROM and got it working again, but I'm without the play store. Any tips?
Make sure you flashed the right gapps, and when you came from amazon is to cm make sure you had first factory reset and wiped system, then flashed cm11 then gapps, and then reboot and see what happens. If you do that it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Make sure you flashed the right gapps, and when you came from amazon is to cm make sure you had first factory reset and wiped system, then flashed cm11 then gapps, and then reboot and see what happens. If you do that it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Can't remember if I did the factory reset, but I wipe the cache, etc after flashing every time.
Can I just go into TWRP and factory reset, then reflash CM again? Or do I need to start over and reflash the 2nd bootloader again?
Thanks for your help, I'm new to the Android/rooting world.
Just factory reset and wipe system then reflash cm then gapps and reboot. That should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Worked like a charm! Thanks for your help!
If I don't see superuser, do I need to run bin4ry's root again or am I rooted and I just don't see it?
Cm is already rooted, its built into the os, look. Under settings u will see a superuser section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
downgraded my nook from cm12 to cm11 and now am getting "Encryption unsuccessful"
i have 2 nook hds and were running lollipop on both units before going back to cm11 the install on my nook hd worked perfectly. however on my wifes nook hd i get an error saying "encryption unsuccessful" when i installed cm11. i used the the lastest available cm11 nightly on both installs and followed the steps. i am at a loss right now as to why my unit works great and im getting an error on my wifes. anyways, i have twrp installed and tried to wipe all data off the the tablet with the advanced wipe and format data functions to try and clear everything off and start again. wondering if ther is a more complete formatting tool that i can use to wipe everything off the tablet and start clean again? any help or direction is appreciated.
thanks everyone!
wigglesrewind said:
i have 2 nook hds and were running lollipop on both units before going back to cm11 the install on my nook hd worked perfectly. however on my wifes nook hd i get an error saying "encryption unsuccessful" when i installed cm11. i used the the lastest available cm11 nightly on both installs and followed the steps. i am at a loss right now as to why my unit works great and im getting an error on my wifes. anyways, i have twrp installed and tried to wipe all data off the the tablet with the advanced wipe and format data functions to try and clear everything off and start again.
Click to expand...
Click to collapse
Which version of recovery did you use to re-flash CM11 on the 3 tablets?
wondering if ther is a more complete formatting tool that i can use to wipe everything off the tablet and start clean again? any help or direction is appreciated.
...
Click to expand...
Click to collapse
You should never wipe any partition other than the /data and /cache partitions (the /system partition automatically gets wiped on flashing a new ROM image). In particular the two partitions /bootdata and /factory which contain factory-installed individual device data must never be reformatted/wiped (without first backing up their content in a restorable form) lest you permanently brick your tablet.
I believe I loaded twrp 2.8.7.4 on both. Thanks for the helpful info. Your greatly appreciated.
wigglesrewind said:
I believe I loaded twrp 2.8.7.4 on both.
Click to expand...
Click to collapse
I'd suggest you try using the older but well-proven recovery for CM11 -- CWM v6.0.4.6.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for the advice. It worked with CWM!
I am really enjoying my Kindle Fire HD (2012) with CM12 except for the fact that it seems that I can only boot successfully every third try or so. The other times, it freezes at the CM boot screen and then I power off and restart. I had this problem, then wiped the system, re-flashed the OS, and am still having the same problem. I searched and didn't dind any relevant posts. Does anyone have any thoughts on this?
Thank you.
Perhaps your battery's low? Try leaving it to charge overnight.
monster1612 said:
Perhaps your battery's low? Try leaving it to charge overnight.
Click to expand...
Click to collapse
Thanks. A numer of times it happened when the battery was highly charged.
When did your issue first start occurring? and does it only act up with CM12.1 or any lollipop-based ROM, or does it occur with all ROMs? Also, are you using any custom mods (like Xposed) or kernels?
monster1612 said:
When did your issue first start occurring? and does it only act up with CM12.1 or any lollipop-based ROM, or does it occur with all ROMs? Also, are you using any custom mods (like Xposed) or kernels?
Click to expand...
Click to collapse
It began pretty much after I first installed CM12 (a previous build, I think from November). I haven't tried any other ROMs. I am not using any custom mods either. Thanks.
Pickngrin said:
It began pretty much after I first installed CM12 (a previous build, I think from November). I haven't tried any other ROMs. I am not using any custom mods either. Thanks.
Click to expand...
Click to collapse
Try a newer CM build (wipe the system, data, and cache partitions before you flash).
monster1612 said:
Try a newer CM build (wipe the system, data, and cache partitions before you flash).
Click to expand...
Click to collapse
I did the dalvik/cache wipe last night (still running the build from 12/30/15) and I've been able to successfully reboot numerous times. Hopefully the problem is resolved.
Thanks again.
Ugh... the problem is not fixed. Another data point.... I was able to successfully reboot numerous times last night. I got home from work this evening (Kindle was off all day), and it froze at the CM boot screen again. I just rebooted into recovery, again did the dalvik and cache wipe, and then it booted (after optimizing numerous apps).
Any more ideas?
Thanks again.
Is it possible that I need to reflash the bootloader or some file other than the actual ROM? It is freezing on boot more times than not.
I would try that - just be careful with flashing.
So I successfully rooted my Fire 7 Gen 5 5.3.1 and flashed the nexus rom with flashfire. However, the instructions I got were bullocks and the gapps I installed, well, didn't install. Through some finagling I managed to get a browser, amazon store, and ez explorer installed, but for the life of me I can't get the play store to work. More specifically, the google play services crash whenever I've installed them. This also has the side effect that every time I try to start flashfire, it also crashes just as it checks for pro...
I've tried a dozen different trouble shooting temps, reinstalls, and cache wiping. They say I need to reflash gapps, but the flashfire doesn't work and I was told the twrp won't work? So how do I get google internet services back up running? Can I use twrps now that it's no longer fire 5.3.2.1? I wasn't very clear on that and I don't want to have an accident brick.
Any help would be appreciated, thanks!
elementalcobalt said:
So I successfully rooted my Fire 7 Gen 5 5.3.1 and flashed the nexus rom with flashfire. However, the instructions I got were bullocks and the gapps I installed, well, didn't install. Through some finagling I managed to get a browser, amazon store, and ez explorer installed, but for the life of me I can't get the play store to work. More specifically, the google play services crash whenever I've installed them. This also has the side effect that every time I try to start flashfire, it also crashes just as it checks for pro...
I've tried a dozen different trouble shooting temps, reinstalls, and cache wiping. They say I need to reflash gapps, but the flashfire doesn't work and I was told the twrp won't work? So how do I get google internet services back up running? Can I use twrps now that it's no longer fire 5.3.2.1? I wasn't very clear on that and I don't want to have an accident brick.
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
If you can't get FlashFire launch/run your only recourse is to reinstall FireOS 5.3.1 via the stock recovery menu (adb sideload) and redo all previous steps (root, flashfire, etc). Be aware GAaps and SuperSU are integrated with Fire Nexus. No need to flash anything but the ROM zip itself.
elementalcobalt said:
So I successfully rooted my Fire 7 Gen 5 5.3.1 and flashed the nexus rom with flashfire. However, the instructions I got were bullocks and the gapps I installed, well, didn't install. Through some finagling I managed to get a browser, amazon store, and ez explorer installed, but for the life of me I can't get the play store to work. More specifically, the google play services crash whenever I've installed them. This also has the side effect that every time I try to start flashfire, it also crashes just as it checks for pro...
I've tried a dozen different trouble shooting temps, reinstalls, and cache wiping. They say I need to reflash gapps, but the flashfire doesn't work and I was told the twrp won't work? So how do I get google internet services back up running? Can I use twrps now that it's no longer fire 5.3.2.1? I wasn't very clear on that and I don't want to have an accident brick.
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Try wiping the data for Google play services.
Sent from my Amazon Fire using XDA Labs
You most likely have used an older release of the nexus rom with the play store incompatibility. Use lastest nexus rom dated feb 8th 2017 from here - https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714 . No need to flash gapps as its in the package. The flashfire error I've seen on version 0.53 which is included in supertools. Use the latest version of flashfire version 5.5 to solve that problem. Place nexus ROM in the tablets internal storage and reflash. I advise no SD card in the tablet or USB cable connected to it. Do a clean flash
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear