Sorry, bit of a noob at this. I just installed CWM, about to install the ROM on the below link. I don't want to have to re-configure everything by installing a new ROM once honeycomb is released, if possible. Would his, which is a rooted and slightly modified version of the official Dell update, be able to update to Dell's official Honeycomb automatically, without having to add a new version with CWM and lose all my apps?
http://forum.xda-developers.com/showthread.php?t=1007877 <--- his ROM
You will have to wipe regardless and hc isn't no where near ready yet.
sent from a tower
Hello,
I upgraded to an ICS version 4.0.4 awhile ago through this website and it was a pretty painless process. Though recently I've been wanting a new phone, but looked into Bionic's software development and I see that I might be able to hold off if I can install 4.2.2 which seems to improve the phone a lot. Currently i am on system version 6.7.232.xt875, android version 4.0.4, build number 6.7.2-223_dbn_m4-9. I've tried installing safestrap 3.11 to start the process of installing CM 10.1 but it crashes every time I try to run it. Can someone please provide me with a starting path towards upgrading my firmware.
Thank You
oldboy26 said:
Hello,
I upgraded to an ICS version 4.0.4 awhile ago through this website and it was a pretty painless process. Though recently I've been wanting a new phone, but looked into Bionic's software development and I see that I might be able to hold off if I can install 4.2.2 which seems to improve the phone a lot. Currently i am on system version 6.7.232.xt875, android version 4.0.4, build number 6.7.2-223_dbn_m4-9. I've tried installing safestrap 3.11 to start the process of installing CM 10.1 but it crashes every time I try to run it. Can someone please provide me with a starting path towards upgrading my firmware.
Thank You
Click to expand...
Click to collapse
You need to take the stock OTA (4.1) to get CM to run.
***PLEASE UNLOCK YOUR BOOTLOADER INSTEAD. ***
*** IF ANY OF THE INFORMATION ON THIS THREAD IS MISUSED IT CAN RESULT IN A BRICKED DEVICE ***
Introduction
- BEFORE PROCEEDING READ THROUGH CAREFULLY, IF THERE IS ANY DOUBT THEN ASK BEFORE PROCEEDING
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
- This is for Apollo and Thor devices only.
Known Issues
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot for now
Compatible ROMS
- HDX Nexus ROM v4
- CM-11
- Fire Nexus ROM
Prerequisites for Installation
- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-
- You must have root access
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Thanks to my Testers
- Davey126
- kudoz83
- lekofraggle
- zamtang
- paul26rem
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2019-10-02
Reserved
Is there a possibility of running cm 12 in this recovery?
paul26rem said:
Is there a possibility of running cm 12 in this recovery?
Click to expand...
Click to collapse
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
ggow said:
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
Click to expand...
Click to collapse
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Davey126 said:
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Click to expand...
Click to collapse
I agree. Don't get me wrong, I love cm, but If you want a stable Rom, Nexus is where it's at.
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
thuyrs said:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
Click to expand...
Click to collapse
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.
A few cautions/notes:
- make sure you are working with the correct slot!
- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle
- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4
Please post the results to others can learn from your experience. Thanks!
Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
loco09 said:
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
Click to expand...
Click to collapse
Flash SuperSU after and you have root access.
Also you will need to block ota updates so do not enable WiFi until you have done so.
EDIT: I have just added a note to the OP about this.
Sent from my Nexus 6 using Tapatalk
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
hfpop said:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
Click to expand...
Click to collapse
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Davey126 said:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Click to expand...
Click to collapse
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
ChuTeng said:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
Click to expand...
Click to collapse
Can you still get into Safestrap?
ggow said:
Can you still get into Safestrap?
Click to expand...
Click to collapse
adb driver in my computer is problem, i fixed. Thanks.
ChuTeng said:
adb driver in my computer is problem, i fixed. Thanks.
Click to expand...
Click to collapse
Does that mean you are up and running again?
Awesome job!!!!!!!!!!
Confirmation number: 67M75398MF9375820
I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?
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.
After failing to flash some lineage 14 roms I found here for the device "Ford" I'm not sure whether this is possible. Thought mine is a Ford because it was also mentioned as Fire HD 7 but I actually not sure if mine is a Ford. It seems Fire HD 8 is the Ford. Maybe some wording problems I found in that thread. My model is x43z60. According to Wiki is should be a 4th Gen. Ages ago when I bought this thing..It's for sure a Fire HD.
My plan, let's say wishes, is to run Octoprint and Klipper firmware for my 3D printer on the fire tablet like it's described here where Lineage with CH341 driver seems to be nessarry. Or may this be possible with the Cyanogen Mod 14 rom?
Hope you can lead md into the right direction.
Can someone please help me identify this device? Since I open the thread I was bricking the device, soldered a factory cable and reinstalling to stock several times as there is chaos regarding the model naming and no source where those tate,ford, jemi, soho names get a clear identification. Or at least I'm not able to find it.
For instance I did use CM (cm-11-20150412-NIGHTLY-tate) and a CM-14 rom I can't find anymore which are for the tate which work but tate even on Cyanogen website says its just the Fire 7 from 2012. But mine seems to be the 4th Gen 2014 so it shouldn't work looking at those bold red warning then - but it does. For instance the 2013 model is called SOHO and everywhere it says don't mix up the firmware for the tate. When 2013 has its own name what is the name for the 2014 and why does tate release work on this?
When I try to install lineage-14.1-20180326-UNOFFICIAL-tate.zip which seem to work for people with the 4th gen it freezes on the kindle orange boot logo.
//EDIT: Got it working with lineage-14.1-20180326-UNOFFICIAL-tate.zip. Net says its a ARIEL model idk why this works but idc. What a mess. Seems every household has its own rom
Anyone can help me and say if if it's possible to run a Linux with Linux deploy on the LineOS 14.1 and this kernel 3.0.7?
Getting errors with Linux Deploy "Fatal kernel to old" depending on the distribution and architecture I choose. If don't get this error I get another chroot /bin/su no such file or permission denied. The device is rooted oc.
tarsonis666 said:
Anyone can help me and say if if it's possible to run a Linux with Linux deploy on the LineOS 14.1 and this kernel 3.0.7?
Getting errors with Linux Deploy "Fatal kernel to old" depending on the distribution and architecture I choose. If don't get this error I get another chroot /bin/su no such file or permission denied. The device is rooted oc.
Click to expand...
Click to collapse
You need Kernel 3.2 or newer to run newer distros.
The only 'supported' distro out there that will work for you is CentOS 7, as it shipped with a glibc old enough to run on a 3.0 Kernel.