Hello. I have Kindle Fire HDX with NexusROM firmware (1.4.3), Anroid version: 4.2.2, Kernel version: 3.4.0, Safestrap Recovery v3.72(TWRP v2.7.0.0) and my ROM slot is stock
I want to upgrade my firmware to CM13 without bricking my device.
The steps are:
1) Rollback to .3.2.4 (.3.2.4 Rollback Images) (replace stockrom slot?)
2) Install .3.1.0 stock update firmware. (But where can i take it?)
3) Unlock bootloader with 1-Click bootloader.
4) Install TWRP 3.0.2.0 using Flashify
5) Flash CM13
Does this steps are correct?
n1cklan said:
Hello. I have Kindle Fire HDX with NexusROM firmware (1.4.3), Anroid version: 4.2.2, Kernel version: 3.4.0, Safestrap Recovery v3.72(TWRP v2.7.0.0) and my ROM slot is stock
I want to upgrade my firmware to CM13 without bricking my device.
The steps are:
1) Rollback to .3.2.4 (.3.2.4 Rollback Images) (replace stockrom slot?)
2) Install .3.1.0 stock update firmware. (But where can i take it?)
3) Unlock bootloader with 1-Click bootloader.
4) Install TWRP 3.0.2.0 using Flashify
5) Flash CM13
Does this steps are correct?
Click to expand...
Click to collapse
Looks good, however use 14.3.2.3.2 instead of 14.3.1.0. The reason been graphical glitches, installation issues etc can be avoided.
Let me know if you can't find the stock firmware. I can post it when i am at my PC next time.
ggow said:
Looks good, however use 14.3.2.3.2 instead of 14.3.1.0. The reason been graphical glitches, installation issues etc can be avoided.
Let me know if you can't find the stock firmware. I can post it when i am at my PC next time.
Click to expand...
Click to collapse
Thanks for reply!
How do you know that I have Apollo device?)
I found 14.3.2.3.2 firmware in Stock firmwares for Kindle Fire HDX (Thor-Apollo).
So, i need wipe all partition, then install 14.3.2.4 firmware in my safestrap?
n1cklan said:
Thanks for reply!
How do you know that I have Apollo device?)
I found this firmware in Stock firmwares for Kindle Fire HDX (Thor-Apollo).
So, i need wipe all partition, then install .3.2.4 firmware in my safestrap?
Click to expand...
Click to collapse
Jedi mind trick ?
Just used the 14. Prefix accidentally.
Related
I tried to do a clean factory reset and activated the stock rom to do so (dumb idea, I guess).
Now it's stuck on the "Deleting..."-screen with the Kindle Fire logo visible.
Tried to hard reset device to access safestrap and restore the backup stock rom, but Safestrap doesn't show up anymore. Instead it shows the "Deleting..."-screen again.
Have I screwed up my Kindle by trying to reset my device with stock rom activated? Or is there any way to access safestrap again?
jsboy said:
I tried to do a clean factory reset and activated the stock rom to do so (dumb idea, I guess).
Now it's stuck on the "Deleting..."-screen with the Kindle Fire logo visible.
Tried to hard reset device to access safestrap and restore the backup stock rom, but Safestrap doesn't show up anymore. Instead it shows the "Deleting..."-screen again.
Have I screwed up my Kindle by trying to reset my device with stock rom activated? Or is there any way to access safestrap again?
Click to expand...
Click to collapse
Which version of safestrap recovery is installed on your kindle? By hard factory reset you mean factory reset in FireOS recovery? Or did you use advanced wipe in safestrap and wipe /system?
jeryll said:
Which version of safestrap recovery is installed on your kindle?
Click to expand...
Click to collapse
I think it was 3.75. I intended to update it to 4.01.
jeryll said:
By hard factory reset you mean factory reset in FireOS recovery? Or did you use advanced wipe in safestrap and wipe /system?
Click to expand...
Click to collapse
I did it via FireOS (ver 3.2.4).
EDIT: Now it went on and rebooted the Kindle Fire HDX. Everything fine now, Safestrap shows up again at startup.
But now I have got the Problem that the Kindle does not recognize the update file for 3.2.5. I put it in the \sdcard folder.
EDIT2: Alright... Figured this one out meanwhile. For anyone with the same problem: The Kindle not detecting the update file. If you disabled OTA via "Kindle Fire HDX Toolkit 0.95" you need to re-enable OTA in KFHDX Toolkit even if you did a factory reset. Otherwise it will block any update files - both over the air from Amazon and locally on your \sdcard folder.
jsboy said:
I think it was 3.75. I intended to update it to 4.01.
I did it via FireOS (ver 3.2.4).
EDIT: Now it went on and rebooted the Kindle Fire HDX. Everything fine now, Safestrap shows up again at startup.
But now I have got the Problem that the Kindle does not recognize the update file for 3.2.5. I put it in the \sdcard folder.
Click to expand...
Click to collapse
I'm glad it's booting... Try put update file to root directory, should recognize it...
If you're on 3.2.4 you sure you want to upgrade? Why not downgrade to 3.2.3.2 and use TWRP? You should stay on 3.2.4 then though, and use the downgrade images provided by ggow.
And DO NOT wipe System in Safestrap v3.x! V4 prevents to do so.
Cl4ncy said:
If you're on 3.2.4 you sure you want to upgrade? Why not downgrade to 3.2.3.2 and use TWRP? You should stay on 3.2.4 then though, and use the downgrade images provided by ggow.
And DO NOT wipe System in Safestrap v3.x! V4 prevents to do so.
Click to expand...
Click to collapse
I wanted to install CM-11. I thought this requires Safestrap v4.01 which requires a rooted 4.5.2. Or am I wrong?
jsboy said:
I wanted to install CM-11. I thought this requires Safestrap v4.01 which requires a rooted 4.5.2. Or am I wrong?
Click to expand...
Click to collapse
This ROM? Well, as it's mentioned there, it will work with TWRP and an unlocked bootloader as well.
I can see that the procedures to downgrade, install TWRP and unlock the bootloader are risky, so you decide. If in doubt ask first, i.e. before you brick your HDX.
Cl4ncy said:
This ROM? Well, as it's mentioned there, it will work with TWRP and an unlocked bootloader as well.
I can see that the procedures to downgrade, install TWRP and unlock the bootloader are risky, so you decide. If in doubt ask first, i.e. before you brick your HDX.
Click to expand...
Click to collapse
Yes, that's the one I would like to install. So do you have a link, where the whole downgrade, installing TWRP and unlocking Bootloader is explained?
jsboy said:
Yes, that's the one I would like to install. So do you have a link, where the whole downgrade, installing TWRP and unlocking Bootloader is explained?
Click to expand...
Click to collapse
So you're still on 3.2.4? Then you can use the rollback Images provided by ggow. Read the description carefully!
On 3.1.0 you can install TWRP, if you haven't done already you should install minimal ADB and fastboot on your PC, you will need it for TWRP Installation (if you don't want to use Flashify), and the bootloader unlock procedure. After the Installation of TWRP you should backup your Fire OS from TWRP and move it to your PC.
Then update to 3.2.3.2 (you can do this in TWRP), then unlock your bootloader, the description is here. Again: if in doubt ask first.
After that you should backup your 3.2.3.2 FireOS and move it to your PC, then you can install the CM11 ROM via TWRP.
Cl4ncy said:
So you're still on 3.2.4? Then you can use the rollback Images provided by ggow. Read the description carefully!
On 3.1.0 you can install TWRP, if you haven't done already you should install minimal ADB and fastboot on your PC, you will need it for TWRP Installation (if you don't want to use Flashify), and the bootloader unlock procedure. After the Installation of TWRP you should backup your Fire OS from TWRP and move it to your PC.
Then update to 3.2.3.2 (you can do this in TWRP), then unlock your bootloader, the description is here. Again: if in doubt ask first.
After that you should backup your 3.2.3.2 FireOS and move it to your PC, then you can install the CM11 ROM via TWRP.
Click to expand...
Click to collapse
Thank you very much for these detailed instructions!
jsboy said:
Thank you very much for these detailed instructions!
Click to expand...
Click to collapse
Tapeinos gave the info that if you install TWRP on 3.1.0 and update to 3.2.3.2 afterwards, you have to re-root (that should be obious, 'cause the 3.2.3.2 update is the official UNrooted Amazon file), but you probably have to re-install TWRP, too. So suggestion would be to update from 3.1.0 to 3.2.3.2, root, disable OTA/stay off WLAN, and install TWRP then, so you don't have to install TWRP twice.
Cl4ncy said:
Tapeinos gave the info that if you install TWRP on 3.1.0 and update to 3.2.3.2 afterwards, you have to re-root (that should be obious, 'cause the 3.2.3.2 update is the official UNrooted Amazon file), but you probably have to re-install TWRP, too. So suggestion would be to update from 3.1.0 to 3.2.3.2, root, disable OTA/stay off WLAN, and install TWRP then, so you don't have to install TWRP twice.
Click to expand...
Click to collapse
By cause I already did it exactly the way you describe it. It worked very well, I'm on CM11 now with an unlocked bootloader.
jsboy said:
By cause I already did it exactly the way you describe it. It worked very well, I'm on CM11 now with an unlocked bootloader.
Click to expand...
Click to collapse
Wow, thanks for the info, you didn't hesitate at all, huh? Great it worked, enjoy CM11.
I successfully unlocked bootloader and rooted my nexus 9 wifi currently on 6.0.1. I've been trying to flash a custom rom to downgrade the android software to either 5.0.2 or 5.1. I would wipe the cache data etc and flash the ROM and 5.x gaaps. When I reboot I get stuck on the Google screen forever.
What I'm I missing or need to do in order to downgrade?
Thank you for any help in advance!
Bump. ..anyone?
Flash the factory image for the version your trying to downgrade to.
Your bootloader and vendor images probably need to be at the same version as your rom.
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
You need this update file. Because rooted your opx!
http://forum.xda-developers.com/showpost.php?p=68655787&postcount=49
Zat.o.ichi said:
You need this update file. Because rooted your opx!
http://forum.xda-developers.com/showpost.php?p=68655787&postcount=49
Click to expand...
Click to collapse
What about the system font? And will I get OTA updates as I have unlocked my device's bootloader?
mukul2259 said:
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
Click to expand...
Click to collapse
Download your current version oxygen os rom put it in sd card and flash it via stock recovery, once u done that it ll again make ur phone us unmodified system now then download oxygen os 3.1.3 from oneplus website and and flash it by stock recovery this time it ll work cos of unmodified system.
Flash this first it ll work Oos 2.1.4 download link https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlusOxygen_14_OTA_007_all_201512161752.zip
Boot into system reboot flash oos3.1.3
Marshmellow oos 3.1.3 download link https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
Doubts? Feel free to ask
I suggest you go step by step, from 2.1.3 upgrade to 2.1.4, move to 2.2.2 then 2.2.3, finally the MM, It worked in my case, I was also on 2.1.3 and faced trouble.. Hope it helps you.
Infact, after upgrading to 2.2.2, the system should have been unrooted. Just flash stock Lollipop recovery and leave it. You should get the rest of the updates as OTA immediately.
mukul2259 said:
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
Click to expand...
Click to collapse
Did you check that the OEM unlocking was enabled after you unlocked the bootloader? Maybe that can be a problem. And I guess flashing the OOS Marshmallow build is possible only with the stock recovery (if you do not want to delete some lines from the code). So I'd stick to stock recovery if I want to update the OOS.
aamodjoshi23 said:
Did you check that the OEM unlocking was enabled after you unlocked the bootloader? Maybe that can be a problem. And I guess flashing the OOS Marshmallow build is possible only with the stock recovery (if you do not want to delete some lines from the code). So I'd stick to stock recovery if I want to update the OOS.
Click to expand...
Click to collapse
Yes, I did check it. It is enabled.
sagar2208 said:
I suggest you go step by step, from 2.1.3 upgrade to 2.1.4, move to 2.2.2 then 2.2.3, finally the MM, It worked in my case, I was also on 2.1.3 and faced trouble.. Hope it helps you.
Infact, after upgrading to 2.2.2, the system should have been unrooted. Just flash stock Lollipop recovery and leave it. You should get the rest of the updates as OTA immediately.
Click to expand...
Click to collapse
I guess this is more logical to do right now. Maybe it's something in the system that can be overwritten after upgrading to OOS 2.2.2. Because when I flashed the beta testing ROM on my device when I had the OOS 2.2.2, it worked just fine. But I guess it won't work if you don't have an older version of OxygenOS because of the small tweaks
aamodjoshi23 said:
I guess this is more logical to do right now. Maybe it's something in the system that can be overwritten after upgrading to OOS 2.2.2. Because when I flashed the beta testing ROM on my device when I had the OOS 2.2.2, it worked just fine. But I guess it won't work if you don't have an older version of OxygenOS because of the small tweaks
Click to expand...
Click to collapse
So, I should flash 2.1.3 via stock recovery and then go to 2.2.2, right?
mukul2259 said:
So, I should flash 2.1.3 via stock recovery and then go to 2.2.2, right?
Click to expand...
Click to collapse
You could just update the ROM by checking for updates in the about phone
Hi everyone.
I have some questions about the necessary steps for an update to mm_nexus-rom from my HDX 7 with Safetrap 4.x.x and kk_nexus-rom.
In the forum are too much information and I do not know which of them are still current and which instructions should not be used.
My original HDX 7 had the latest Fire OS 4.5.5.x Version. I used Kingroot and Safetrap 4. to install the kk-nexus-rom. So my bootloader is still locked.
Now i want to update to the mm-fire-nexus-rom withour breaking it, for this i need to unlock my bootloader.
Are the following steps correct?
1: Roll back to 3.2.4 with the steps from .3.2.4 Rollback Images
(Qustion to step 7. Copy the .3.1.0 stock update file to the root of your sdcard: Where do i Find the stock 3.1.0 updatefile)
2: User Flashify to install TWRP 3.0.2.0 from [RECOVERY][UNLOCKED BL] TWRP 3.0.2.0
3: Install mm-nexus-rom from TWRP
Or do i have to use :
[Thor][Apollo] Unlocking bootloader with any firmware
blackson2c said:
Hi everyone.
I have some questions about the necessary steps for an update to mm_nexus-rom from my HDX 7 with Safetrap 4.x.x and kk_nexus-rom.
:
[Thor][Apollo] Unlocking bootloader with any firmware
Click to expand...
Click to collapse
Above procedure is relevant as you can now unlock the bootloader on ANY rooted 3rd gen HDX including those currently running Safestrap v4; risky rollbacks are no longer required. Be aware your device will be wiped during the unlock procedure (not always true but assume it will). Read through the unlock thread; ask questions as needed.
So do I need to downgrade or what? How do I root kindle fire os 5.3.3.0? My kindle fire is hd 6 4th gen
Yep. There's a thread around here somewhere outlining the process. The basics are: Set up ADB on Kindle and PC. Sideload Fire OS 4.5.3 to your Kindle via ADB. Block OTA updates. Root via your preferred method. Install TWRP. Use TWRP to flash 5.3.3.0 bootloader and ROM back to your Kindle. Done.
I know it's a pain in the arse to go through all that, and in the end you don't even get to keep TWRP, but as far as I know it's the only possible way to get root on the HD 6 and 7 4th gen right now. At least until Kingroot is updated.
You can't flash twrp right after flashing 5.3.3.0? Or will the kindle not boot?
Sent from my VS990 using Tapatalk
No. Your Kindle would still boot, you just wouldn't have a recovery anymore. For whatever reason TWRP doesn't play well with bootloaders above 4.5.x. So if you were to flash TWRP in 5.x, you overwrite the stock recovery. Upon reboot, TWRP won't work since you have 5.x bootloaders, and your stock recovery is gone since it was overwritten by TWRP. So you're in the nasty situation of having no recovery and no way to get one back.
Somewhere in the rooting thread there is mention of an automated script that will flash 4.5 bootloaders for you and then boot into TWRP. Once you're done just flash your 5.x bootloaders back and reboot. Not a permanent fix, but at least it's all done on the Kindle itself (no need for a PC once it's set up) and there's no chance of ending up without a recovery since TWRP is ran in memory and not flashed so your stock recovery stays intact.
There's a detailed tutorial that I've updated and simplified for 5.3.3.0 here: https://forum.xda-developers.com/showpost.php?p=72466867&postcount=540
Hi all, sorry to jump in here, but does Fire HD 6 have OTG support for flash drive?