Related
I did root Amazon Kindle HDX THOR successfully with: [TOOL] HDX ToolKit v0.94:ROOT UPDATE
http://forum.xda-developers.com/showthread.php?t=2665683
And I disabled the air updates according to the instructions. Later I tried to reset the update to 13.3.1.0.
http://forum.xda-developers.com/showthread.php?t=2782159&page=10
It worked allright, until I tried to do the manuel update. But because I disabled air update earlier, Amazon Kindle couldn't find any update the manual update failed. How do I do to enable the update again, is there anything else I can do to solve this?
Is it possible to reset to 13.3.2.3.2 again?
Thanks!
umm
Atise said:
I did root Amazon Kindle HDX THOR successfully with: [TOOL] HDX ToolKit v0.94:ROOT UPDATE
http://forum.xda-developers.com/showthread.php?t=2665683
And I disabled the air updates according to the instructions. Later I tried to reset the update to 13.3.1.0.
http://forum.xda-developers.com/showthread.php?t=2782159&page=10
It worked allright, until I tried to do the manuel update. But because I disabled air update earlier, Amazon Kindle couldn't find any update the manual update failed. How do I do to enable the update again, is there anything else I can do to solve this?
Is it possible to reset to 13.3.2.3.2 again?
Thanks!
Click to expand...
Click to collapse
Rerun the tool kit it has a reenable option. Just out of curiosity did you ask this question back in the HDX utility thread? Nevermind it might not of let you post their.
Anyway if as long as you are using version .94 should work fine for you. And make sure that you have Wi-Fi disabled and even forget your network as you are planning on doing a manual update. If you plan on trying to rollback we advised not to at this time just wait till safestrap is updated and works with the newest firmware... Way too many people are breaking their devices by trying to do the build prop modifications necessary to do these manual updates.. If you want the latest firmware just let it up to Wi-Fi nHit check for updates then you can wipe it root it or whatever... But just to let you know currently safestrap does not work on newest firmware..yet. Just do your homework because there are a ton of brick devices right now that are getting sent in for BS warranty claims.. And I have to emphasize yet again there is no easy way to recover this device at this time if you mess something up unless you are using safestrap and on slot 1 ect...NO fastboot capabilities at this time..And bootloader is locked
Thanks
jimyv said:
Rerun the tool kit it has a reenable option. Just out of curiosity did you ask this question back in the HDX utility thread? Nevermind it might not of let you post their.
Anyway if as long as you are using version .94 should work fine for you. And make sure that you have Wi-Fi disabled and even forget your network as you are planning on doing a manual update. If you plan on trying to rollback we advised not to at this time just wait till safestrap is updated and works with the newest firmware... Way too many people are breaking their devices by trying to do the build prop modifications necessary to do these manual updates.. If you want the latest firmware just let it up to Wi-Fi nHit check for updates then you can wipe it root it or whatever... But just to let you know currently safestrap does not work on newest firmware..yet. Just do your homework because there are a ton of brick devices right now that are getting sent in for BS warranty claims.. And I have to emphasize yet again there is no easy way to recover this device at this time if you mess something up unless you are using safestrap and on slot 1 ect...NO fastboot capabilities at this time..And bootloader is locked
Click to expand...
Click to collapse
Thank you for your help!
Atise said:
Thank you for your help!
Click to expand...
Click to collapse
My advise, don't try rolling back, most likely you will brick your device. Search for an app called kindlefree if Google play is what you want.
btw, thank you for posting in Q&A.
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
I can't seem to find any working root for my kindle and i'm need help to root this darn thing.
I really want to Get rid of amazon and go get Android kit-cat and use the Google play. Your answer will be thanked if your answer works.
i heard about roll backing my kindle fire hdx but i need more info on how to get into the internal storage folder.
My kindle runs Fire os 4.5.4
I have no idea how to find the firmware...
As of now, it cannot be done yet. Sorry.
lekofraggle said:
As of now, it cannot be done yet. Sorry.
Click to expand...
Click to collapse
Oh ok..
Its been a long while though.
I guess amazon won the war against rooting...:crying:
This is a brand new update. So, it actually has not been that long. There has been a root found for almost every other release including 4.5.3, but I think they patched it with this new release.
lekofraggle said:
This is a brand new update. So, it actually has not been that long. There has been a root found for almost every other release including 4.5.3, but I think they patched it with this new release.
Click to expand...
Click to collapse
4.5.3? You sure because i Looked everywhere for answers only to find out the roots does not work... But i hope they find a root.
By the way can you reply to me when they have a root out for my 4.5.4 Update. make sure to give me the link. That will be really Nice.
You should be reading through the boards yourself. If you had, you would know they found a root option in China which worked on 4.5.3. It did take a while to find, but they found one.
I can't just hotlink to a file or post because this device is so fickle, you need to understand what you are getting into when you root. I have been on Android since 2.0 and I have never seen a device so easy to ruin and difficult to fix. Sorry.
That Chinese root also doesn't work 100% of the time. It didn't work on my Saturn(HDX 8.9). That said, I seemed to be the only one who had trouble with it.
The update for 4.5.4 came out in the last week.
XxD34THxX said:
That Chinese root also doesn't work 100% of the time. It didn't work on my Saturn(HDX 8.9). That said, I seemed to be the only one who had trouble with it.
The update for 4.5.4 came out in the last week.
Click to expand...
Click to collapse
I actually did get root to work with Kingroot, prebuiltgmscore apk downloaded separately here and minimal google bundle here
I have a 8.9 HDX 4th generation also called Saturn.
Did Kingroot work with 4.5.4?? If so, I will try it again.
XxD34THxX said:
Did Kingroot work with 4.5.4?? If so, I will try it again.
Click to expand...
Click to collapse
No, my device is a kindle fire hdx 7, it runs 4.5.4 and it seems like kingroot does not work.
When it fails it gives me this Email Icon with a check mark
and then a number 13096
i even checked it with a root checker and it said no Root access
So that's the error screen. Hope they find a root for 4.5.4 Soon!
XxD34THxX said:
Did Kingroot work with 4.5.4?? If so, I will try it again.
Click to expand...
Click to collapse
I'm on 4.5.3 sorry....
There is a way: downgrade to 3.5.8 (there is a thread for it) then upgrade to 4.5.3 then root it with kingroot.
herophuong93 said:
There is a way: downgrade to 3.5.8 (there is a thread for it) then upgrade to 4.5.3 then root it with kingroot.
Click to expand...
Click to collapse
Use great caution if going this route. There are numerous reports of bricked devices following 3.2.8 rollback apparently due to an immediate ota push of 4.5.4 which renders the device unusable. To date there is no known recovery method. If you opt to downgrade you must either block the ota mechanism via HDX Toolkit (other methods do not work) or take steps to prevent network connectivity until 4.5.2 is successfully installed.
wonder
wonder if there is a way to downgrade back to is 4.5.3
Braders2345 said:
wonder if there is a way to downgrade back to is 4.5.3
Click to expand...
Click to collapse
Not at this time. Nor is there a benefit relative to 4.5.2. If you are on 4.5.4 you can roll back to 3.2.8 then upgrade to 4.5.2. However, there are risks involved (unrecoverable brick); procedures must be followed exactly.
Davey126 said:
Not at this time. Nor is there a benefit relative to 4.5.2. If you are on 4.5.4 you can roll back to 3.2.8 then upgrade to 4.5.2. However, there are risks involved (unrecoverable brick); procedures must be followed exactly.
Click to expand...
Click to collapse
Davey, I am willing to give downgrade a shot, I just need to know the correct link to use. Will you please post the correct link to downgrade, I have a 4th Gen HDX 8.9 Saturn....just a FYI....Thanks
chargedbird said:
Davey, I am willing to give downgrade a shot, I just need to know the correct link to use. Will you please post the correct link to downgrade, I have a 4th Gen HDX 8.9 Saturn....just a FYI....Thanks
Click to expand...
Click to collapse
Sorry - Saturn devices can not be rolled back. The OTAs used are specific to Apollo and Thor. Amazon never offered rollbacks for Saturn thus no one was able to capture the rollback file. The internals are sufficiently different that you'd likely build a brick if you tried to 'force' an Apollo update. Apologize if I missed a prior reference to Saturn and falsely got your hopes up.
[Solved] Manual install CM11 & Original Thread: How to install CM 11.1 on Fire HDX 7?
Hello,
as I just managed to install CM 11 on my Fire HDX 7 (3rd Gen) (thanks a lot to @Cl4ncy, @Davey126 and @EncryptedCurse) I want to share the information I got during the process.
Note: This manual might be outdated if you read it. So check if there is a newer manual You could break your device if you dont do everything correctly. I am not responsible for breaking your device! If you have a question just ask! It could be that i forgot something.
When I started my Fire HDX 7" had Fire OS 4.5.5.
Note: CM 12 is not available yet for Safestrap v4. If you want CM 12 you need an unlocked bootloader. You can't do it if your version is above Fire OS 3.2.3.2. And you are not able to downgrade below 3.2.8 due to rollback protection by Amazon.
Some preperations:
- connect your Fire HDX to your PC (if your PC doesnt recognize your Fire HDX then install the USB drivers. If that doesn't work deinstall the actual Fire HDX driver and try it again.)
- copy every folder from the Fire HDX storage to your PC (backup music, ....)
- install (Holo Backup and click on every Backup Button (in my version there were 5 buttons))
- install minimal adb + fastboot
Download these files and save them on your PC:
- ES Explorer
- KingRoot
- Safestrap v4
- a Safestrap v4 compatible ROM (CM11 or Nexus v4)
- SuperSU if you want root - Download the .zip file from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip //Check if there is a newer Version
- GApps if you want the Google Apps (the right things should be already selected. If not select: ARM, 4.4, nano) -> the name should be sth like: "arm 4.4 nano 30 September 2015"
Thanks to @Davey126 and @Cl4ncy:
- Turn Wifi Off and flightmode on (you might need to enable Wifi, when you root your device with KingRoot)
- rollback to FireOS 3.2.8
// you do that by copying the file into the 'Internal storage folder' of your Fire HDX (not in a subfolder, just copy it where the DCIM, Document, Download, kindle, ... folder are.). Now wait a few minutes and go to Settings -> Device -> System Updates -> Tap Update
- upgrade to FireOS 4.5.2
// do it as before
- install ES Explorer and KingRoot with minimal ADB + Fastboot
- make sure that only the Fire HDX 7" is connected
- run this Code to see the connected devices
Code:
adb devices
- install the ES Explorer and KingRoot by using minimal ADB + Fastboot
- replace "C:\users\p-4\es.apk" with your own path and do the same for KingRoot
Code:
adb install C:\users\p-4\es.apk
- root with KingRoot or another method (i didn't find another one) //if it doesn't work directly just try it again (I tried it 10 times). If it still doesn't work just try another Wlan (that nothing gets blocked) or wait a week.
- block OTA (over-the-air updates) - only step#1 //you don't have to install the GApps because you will flash them with the ROM
- install Safestrap v4
- Copy the installation files (ROM, SuperSU, Gapps) to your Fire HDX into the /sdcard folder. (There the files won't get deleted if you wipe). If there folder isn't available then create one. But normally there should be one. Make sure you have your Fire HDX rooted. Only then you can see the folder with ES Explorer. In my case the "/sdcard" folder was the normal one, where i stored my Music, Documents, ... so had didn't have to do sth.
- Reboot
- Make a backup of the 'Stock-Slot'
- Copy the backup to your PC
- flash a Safestrap v4 compatible ROM to the ROM-Slot-1 , 2, 3 or 4 (currently CM11 or Nexus v4)
Safestrap v4 Tutorials:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
Notes: If you use a secondary slot the biggest possible Data Size is 16GB and your battery won't last long. You have to charge the Fire HDX very often.. If you use the Stock Rom Slot you will have the whole storage of your device.
Congratulations you successfully installed CM11 if you did everything right.
But as I mentioned before the performance is not very good, because the ROM is installed on a secondary slot.
--------------------------------------------------------------------------------------------------------------------------------------
To get the best performance and a very good battery life you have to install the ROM on the 'stock-slot'.
Thanks to @Cl4ncy and @Davey126 :
For that just:
- Reboot and go to the Safestrap Menu
- check if the installation files (ROM, Gapps, SuperSU) are in the "/sdcard" folder press "..." in the installtion menu to go up the path. There should be the "/sdcard" folder.
- Delete the secondary ROM-Slots
- Go into the Wipe Menu and Swipe to perform a factory reset (only a simple one - no advanced wipe)
- Go to install and add the ROM File
- add Gapps
- add SuperSU if you want root
- perform the flash
- if it was successfull Reboot otherwise DON'T Reboot. Just wipe again and flash the files again.
Note: If something went wrong with the stock-ROM don't reboot directly. Just install a ROM on a secondary slot and reboot then.
// The Original Post:
Hello,
since it is possible to download prime videos on any android device i would like to install Cyanogenmod 12.1 on my fire hdx 7.
I found this Cm 12.1 Port.
Is there a step by step manual how to install such a rom, because i never did that before and i have heard that if you do something wrong your device is broken.
Because I neither know how to get an unlock bootloader or what a TWRP is. Furthermore i also dont know how to flash the ROM.
In some forum posts i read, that it is possible to go from Cyanogenmod back to FireOS (unbrick). For now i dont want to go back from Cyanogenmod to FireOS, but i think it would be good to have such a possibility.
Do I have to take precautions for that?
And how do I make backups?
Info:
Kindle Fire HDX 7" (3. Generation): Fire OS 4.5.5
Thanks a lot
p-4
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12. You can also NOT use TWRP recovery.
Reason: Rollback protection by Amazon, preventing downgrading to Fire OS versions below 3.2.8
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Thanks for this answer
Cl4ncy said:
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12.
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Click to expand...
Click to collapse
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
You can NOT use TWRP (see above), TWRP is available for Fire OS below 3.2.4 only. You must use Safestrap v4 (i.e. NOT Safestrap v3.72/3.75!).
I can't give you any recommendation, but you can try Nexus and CM11 after you installed Safestrap v4. You can even (depending on the size of your sdcard/storage) set up secondary slots and use dual boot with Safestrap installed.
But you should focus on downgrading to 3.2.8, then updating to 4.5.2, rooting, disabling OTA, and installing Safestrap first - that will be difficult and risky enough for the time being.
And note that CM12 is not an option for you. This could change in the future, but I wouldn't count on it.
And one other thing:
If you've Safestrap installed, NEVER use the factory reset in Amazon's stock recovery! You will most likely brick your HDX.
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
Nexus is basically an AOSP-based ROM (i.e. stock, just like Google intended).
CM11 should be self-explanatory.
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Or is it possible, after I installed CM 11, to upgrade to CM12? (Has Cyanogenmod an Over the Air update possibility?)
p-4 said:
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Click to expand...
Click to collapse
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Cl4ncy said:
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Click to expand...
Click to collapse
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
p-4 said:
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
Click to expand...
Click to collapse
Enable USB debugging, install Minimal ADB and fastboot, put the kingroot.apk into the adb directory, open a DOS box, change dir (cd) to your adb directory (e.g. enter cd\adb), then enter "adb install kingroot.apk" (without the quotes). This will install Kingroot on your HDX. Then do the same with ES Explorer.
The HDX must be connected to your PC by USB of course (should be obvious).
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
p-4 said:
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
Click to expand...
Click to collapse
As long as you're still on 4.5.2 you can try to root, just ensure 4.5.4 won't be installed. After successful root you can disable OTA, and delete the update file. Also ensure you have the latest Kingroot version - 4.50.902 I believe.
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
p-4 said:
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
Click to expand...
Click to collapse
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Cl4ncy said:
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Click to expand...
Click to collapse
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
p-4 said:
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
Click to expand...
Click to collapse
I'm afraid no.
Kingroot fails always between 53% and 55%. Once I got over 60%.
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
p-4 said:
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
Click to expand...
Click to collapse
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Cl4ncy said:
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Click to expand...
Click to collapse
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
p-4 said:
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
Click to expand...
Click to collapse
Ok, enable flightmode to avoid getting updated further to 4.5.5 then.
And good luck, I'm really not sure about this.
Does someone know if this root app works normally? (click)
After a few tries I can now locate to /system/priv-app/DeviceSoftwareOTA.apk but I am not able to rename this apk.
Can I also try these ways to root the Fire HDX 7" or will i brick my device then? (click)
//edit I just enabled wrong locations and it worked with kingroot
// edit now i got cm11 installed Can I also try other roms like CM12 and insert them in the Rom-slot 2? If it fails, my device isn't bricked, because i only have to restart and load rom-stock or rom slot 1, right?
The only big problem I noticed so far is the battery. After 8 hours in sleeping mode (only screen off) the battery status sank from 90% to 55%. How can I fix this problem?
Hello everyone, I've been very tempted to root my kindle fire hdx 7 and I've finally decided to do it, but there is still one thing stopping me. Let's say I want to go back, no root and update to the latest version of Fire OS. How do I do this? If I do root, I will be running 4.5.2 with SuperSU from this thread: http://forum.xda-developers.com/showpost.php?p=59156161&postcount=56
Thanks!
There's an unroot option from within SuperSU.
EncryptedCurse said:
There's an unroot option from within SuperSU.
Click to expand...
Click to collapse
after unroot?
being on 4.5.2 and recieve update trough OTA, by renaming the DeviceSoftwareUpdate apk?
or download and put it in internal storage?
EncryptedCurse said:
There's an unroot option from within SuperSU.
Click to expand...
Click to collapse
I'm in a crisis right now where I just want to go back to the default fire os. I rooted and installed gapps, but I want to go back. Could you help me out with the process?
Thanks
Giraffackle said:
I'm in a crisis right now where I just want to go back to the default fire os. I rooted and installed gapps, but I want to go back. Could you help me out with the process?
Thanks
Click to expand...
Click to collapse
Hi friend!!
My long-short story:
1. New kindle fire hdx 7 on 4..5.5.
2.Rollback to 3.2.8.(only one rollback method now I think). (unable OTA updates if not bricked!)
3.Upgrade to 4.5.2 (root with cve method or king root)
4.there I try to install Gapps, too many error on the forum so I didnt! sideloaded netflix stoped working.
----------------your part here----------------
5. disable wifi, reactivate OTA. unroot on SU options.
6. enable wifi and start all the updates, this way you are back to 4.5.5 without brick and with easy.
alberto1414 said:
Hi friend!!
My long-short story:
1. New kindle fire hdx 7 on 4..5.5.
2.Rollback to 3.2.8.(only one rollback method now I think). (unable OTA updates if not bricked!)
3.Upgrade to 4.5.2 (root with cve method or king root)
4.there I try to install Gapps, too many error on the forum so I didnt! sideloaded netflix stoped working.
----------------your part here----------------
5. disable wifi, reactivate OTA. unroot on SU options.
6. enable wifi and start all the updates, this way you are back to 4.5.5 without brick and with easy.
Click to expand...
Click to collapse
Did this remove gapps? Congrats on getting it to work for you btw!
Giraffackle said:
I'm in a crisis right now where I just want to go back to the default fire os. I rooted and installed gapps, but I want to go back. Could you help me out with the process?
Thanks
Click to expand...
Click to collapse
Responded in another thread:
http://forum.xda-developers.com/showthread.php?t=2901813