Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!
Related
Hi everyone
I own an Amazon Fire HD 6 and I love it. It's a powerful little machine, but Fire OS 4.5.3 sucks. I've been looking to root it and run a custom ROM on the device since I got it in December 2014, but I never got around to doing it until now. (And there weren't instructions back then.)
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
bibikalka said:
[DONE] 0) get ADB drivers working on your PC, etc:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Tip: A quick way to debug your adb connectivity issues is to use USBDeView : http://www.nirsoft.net/utils/usb_devices_view.html
[DONE] 1) Determine your FireOS version, versions up to 4.5.3 are rootable, 4.5.4 will need to be upgraded to 5.0.2 and then downgraded to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
[DONE, WITH EXCEPTION] 2) Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater" http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ),
sideload Kingroot ( http://androidxda.com/download-kingroot-application ),
and let it root. Don't bother with SuperSu at this stage, you'll get it done later.
Click to expand...
Click to collapse
My Fire HD 6 shows up without error in
Code:
adb devices
but when I attempted to sideload Kingroot via
Code:
adb reboot recovery
I got the following error:
Code:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible. But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Thanks in advance.
Is recovery gone?
pantyman said:
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
My Fire HD 6 shows up without error in . . . adb devices . . . but when I attempted to sideload Kingroot via . . . adb reboot recovery . . . I got the following error:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
Click to expand...
Click to collapse
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
Click to expand...
Click to collapse
(2) I assume you got above error again. This is where you need someone else's help.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
Click to expand...
Click to collapse
(3) Not a big deal. You got it installed.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible.
Click to expand...
Click to collapse
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Click to expand...
Click to collapse
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
DoLooper said:
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
(2) I assume you got above error again. This is where you need someone else's help.
(3) Not a big deal. You got it installed.
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
Click to expand...
Click to collapse
Thanks a lot for all of your advice, @DoLooper. I've since actually gotten everything to work by following instructions by @r3pwn on his alternate unbricking method for the Kindle Fire HDX 7" & 8.9"
No issues for me any more! The only thing I have to look for now is a good launcher for this thing. I'm not a big fan of the Vire Launcher.
I'm having this same problem but was unable to fix via the thread linked.
Help please?
Hello there,
so after reading a lot on the forums, I want to give it a try and install a custom rom on my hdx7 thor with unrooted stock 4.5.2 (13 Dec 2014). I also already downloaded the downgrade firmware 3.2.5 from amazon in case that makes it easier. But I figured I could just start with Safestrap v4.0.1 to put one of the two available KitKat ROMs in slot 1. I think I might prefer flashing TWRP and then CM12 though. I do not have OTAs disabled yet, so I'm afraid of enabling the WiFi.
My question is what would I have to do to install TWRP (unlocking Bootloader, rooting, then flashing?) or if that is not recommended, how do I install the APK as the tablet doesn't come with a file explorer (adb, fastboot?).
I would appreciate some assistance as I don't want to hurry and brick anything. Any help would be nice! Thank you so much in advance
Stop! You can NOT downgrade to 3.2.5! From 4.5.2 you can downgrade to 3.2.8 only, which actually doesn't make any sense. So you can NOT use TWRP! And you can NOT unlock the bootloader!
Recommendation for you:
Root 4.5.2 with Kingroot, disable OTA by renaming the .apk, install Safestrap v4, and use either Nexus or CM11 for Safestrap v4. Note that CM12 is NOT Safestrap compatible! Read the installation notes and requirements carefully!
And if you're unsure ask before you brick your HDX, please.
Two more things:
CM11 works in secondary slots in Safestrap v4 (i.e. you could Keep Fire OS with OTA disabled in the stock slot then, if you want).
And be sure to make a backup of Fire OS via Safestrap and copy it to your PC before you flash anything, especially to the stock slot.
Okay, that's why I didn't start yet. After reading through here, I already felt like the Amazon devices are especially difficult when it comes to Android modifications! Now I have a few questions left:
1. Where do I get kingroot? (I can only find the homepage in chinese)
2. How can I install APK-Files like Safestrap without File explorer?
3. Is it important to know the exact firmware version? I can only find the short one under settings (so 4.5.2)
OdlG26 said:
Okay, that's why I didn't start yet. After reading through here, I already felt like the Amazon devices are especially difficult when it comes to Android modifications! Now I have a few questions left:
1. Where do I get kingroot? (I can only find the homepage in chinese)
2. How can I install APK-Files like Safestrap without File explorer?
3. Is it important to know the exact firmware version? I can only find the short one under settings (so 4.5.2)
Click to expand...
Click to collapse
1. Try this site.
2. You can install apps via adb, see this post from @ggow. You should install Minimal ADB and fastboot.
3. I'm currently not sure where to find the exact version, but it shouldn't be a problem if it's 4.5.2. Just be sure to keep WLAN off/flight mode active, so it won't get updated by Amazon. And disable OTA by renaming the .apk after rooting, so you can use WLAN.
And yes, Amazon removed important things like a real recovery, so if you screw up, there's a certain likelihood of a bricked device.
Thank you for your support! Here is what I did so far:
- Installed Minimal ADB+Fastboot along with the Kindle ADB Drivers (googled it as it would say "waiting for device")
- Copied kingroot.apk and safestrap.apk into the Minimal ADB+Fastboot Folder
- Used the command "adb install ***.apk"
- Then rooted the device with kingroot app
It succeeded. Now as I havent used Safestrap before, do I now download one of the two ROMs, copy them to the kindle memory and install it with the app safestrap?
Edit: Also, what is the biggest difference between CM11 and Nexus? Both seem to be very alike
Edit2: I installed the recovery in safestrap app and downloaded Nexus ROM 4.05. I suppose it is now like TWRP etc so I just copy the ZIP-Files and then install and wipe?
OdlG26 said:
Thank you for your support! Here is what I did so far:
- Installed Minimal ADB+Fastboot along with the Kindle ADB Drivers (googled it as it would say "waiting for device")
- Copied kingroot.apk and safestrap.apk into the Minimal ADB+Fastboot Folder
- Used the command "adb install ***.apk"
- Then rooted the device with kingroot app
It succeeded. Now as I havent used Safestrap before, do I now download one of the two ROMs, copy them to the kindle memory and install it with the app safestrap?
Edit: Also, what is the biggest difference between CM11 and Nexus? Both seem to be very alike
Edit2: I installed the recovery in safestrap app and downloaded Nexus ROM 4.05. I suppose it is now like TWRP etc so I just copy the ZIP-Files and then install and wipe?
Click to expand...
Click to collapse
Did you disable OTA in Fire OS 4.5.2 after rooting (IMPORTANT!)?
Ok, you want to use Nexus, so note that it doesn't work (yet) in secondary slots (WLAN won't work), so backup your stock slot, copy the backup to your PC, then install Nexus to the stock slot. Flashing is similar to TWRP, yes. Note that Safestrap v4 has a built-in protection to wipe system (which usually shouldn't be wiped).
Thanks for the hint! Weirdly, it was already renamed to "Disable***.apk_off" so it is not recognized as apk anymore. Don't know if maybe the previous owner did that. Also found the google play store in the app list so he probably did that before.
Now gonna try to make a backup and then install Nexus, GApps and SuperSU
Edit: After Rebooting into Safestrap Recovery, it seems stuck on grey kindle fire logo... What should I reinstall to fix that? Also says Safestrap Disabled on startup. Reinstalling the recovery doesnt help. Also, SuperSU says that the binary needs to be updated
OdlG26 said:
Thanks for the hint! Weirdly, it was already renamed to "Disable***.apk_off" so it is not recognized as apk anymore. Don't know if maybe the previous owner did that. Also found the google play store in the app list so he probably did that before.
Now gonna try to make a backup and then install Nexus, GApps and SuperSU
Edit: After Rebooting into Safestrap Recovery, it seems stuck on grey kindle fire logo... What should I reinstall to fix that? Also says Safestrap Disabled on startup. Reinstalling the recovery doesnt help. Also, SuperSU says that the binary needs to be updated
Click to expand...
Click to collapse
I'm sure what happened here. Which Nexus ROM did you flash, and what did you wipe in Safestrap?
Could be the Fire OS was rooted already, otherwise the OTA apk couldn't have been renamed.
Cl4ncy said:
I'm sure what happened here. Which Nexus ROM did you flash, and what did you wipe in Safestrap?
Could be the Fire OS was rooted already, otherwise the OTA apk couldn't have been renamed.
Click to expand...
Click to collapse
I didn't flash anything so far as I couldnt access the recovery. the tablet freezes when i try to boot into it. also, the google play store that the previous owner installed cannot connect with my google account so something seems fishy here... Should i uninstall safestrap recovery and do a firmware reset in fireos recovery?
OdlG26 said:
I didn't flash anything so far as I couldnt access the recovery. the tablet freezes when i try to boot into it. also, the google play store that the previous owner installed cannot connect with my google account so something seems fishy here... Should i uninstall safestrap recovery and do a firmware reset in fireos recovery?
Click to expand...
Click to collapse
The Fire OS factory reset should be considered the last resort, therefore you should use it if all other options failed only. It'd be required to un-install Safestrap, enable OTA, and un-root FireOS . Be sure to keep WLAN off/flight mode active so Amazon won't update to 4.5.5 if you try a factory reset.
So to understand what you've done yet:
Rooted with Kingroot, installed Safestrap v4 (Safestrap v3.7x is NOT compatible), and after reboot Safestrap is disabled and Fire OS doesn't load either?
I'm not sure what's happening, as your device seems to have been rooted before you did it (again)?
So priority should be to get the system working again, you could try to un-install Safestrap, enable OTA (re-re-name the .apk), and un-root with Kingroot, then see if Fire OS comes up, if not try a factory reset. Again: stay of WLAN/keep flight mode active.
You should try to make SU happy frist, as @Davey126 suggested here.
Cl4ncy said:
The Fire OS factory reset should be considered the last resort, therefore you should use it if all other options failed only. It'd be required to un-install Safestrap, enable OTA, and un-root FireOS . Be sure to keep WLAN off/flight mode active so Amazon won't update to 4.5.5 if you try a factory reset.
So to understand what you've done yet:
Rooted with Kingroot, installed Safestrap v4 (Safestrap v3.7x is NOT compatible), and after reboot Safestrap is disabled and Fire OS doesn't load either?
I'm not sure what's happening, as your device seems to have been rooted before you did it (again)?
So priority should be to get the system working again, you could try to un-install Safestrap, enable OTA (re-re-name the .apk), and un-root with Kingroot, then see if Fire OS comes up, if not try a factory reset. Again: stay of WLAN/keep flight mode active.
Click to expand...
Click to collapse
Cl4ncy said:
You should try to make SU happy frist, as @Davey126 suggested here.
Click to expand...
Click to collapse
I installed Kingroot and Safestrap via adb (newest versions, so 4.5 and 4.01 or so). Then I rooted with Kingroot (didn't say it was rooted yet, iirc it even said something with error). After that I started safestrap and installed the recovery. Then got a file explorer via adb and checked the OTA file (was already renamed). Then tried both, rebooting into recovery from the app and from a shut down device. In both cases, the tablet freezes with a black screen or at the grey kindle fire logo. FireOS still loads and works fine.
I just really don't know what to do as the HDX is so different from my past android devices. So I'm sorry for not being a good help
OdlG26 said:
I installed Kingroot and Safestrap via adb (newest versions, so 4.5 and 4.01 or so). Then I rooted with Kingroot (didn't say it was rooted yet, iirc it even said something with error). After that I started safestrap and installed the recovery. Then got a file explorer via adb and checked the OTA file (was already renamed). Then tried both, rebooting into recovery from the app and from a shut down device. In both cases, the tablet freezes with a black screen or at the grey kindle fire logo. FireOS still loads and works fine.
I just really don't know what to do as the HDX is so different from my past android devices. So I'm sorry for not being a good help
Click to expand...
Click to collapse
Well, if Kingroot didn't root it could explain why it doesn't work, Safestrap requires a rooted device.
Did you get ES File Explorer? Try to enable Root Explorer in its options, if that fails your device is not rooted.
Cl4ncy said:
Well, if Kingroot didn't root it could explain why it doesn't work, Safestrap requires a rooted device.
Did you get ES File Explorer? Try to enable Root Explorer in its options, if that fails your device is not rooted.
Click to expand...
Click to collapse
Sorry, I wasn't clear, Kingroot showed an error on first start. Rooting itself was successfull and since then I get a log of what apps successfully got the root permission. So that seemed to work now. But SuperSU was being weird.
Edit: I uninstalled Recovery, then Safestrap App, then unrooted in Kingroot Settings menu, then pushed Kingroot, Safestrap and ES Explorer via adb again. Kingroot started rooting process. Says it fails (and needs Wifi enabled for some reason), but when I restart the app, it says Root enabled. Once I go to Root File Explorer and rename the DisableOTA, it succeeds. Very weird...
Also there is a SetupWizard.aok_off in priv apps (Google Play?)
I just started Safestrap and installed recovery after this weird "root process failed" with root explorer working anyway. It actually booted into the recovery and I made a backup of my system!
Now I just install the Custom ROM in Slot 1? (along with GApps and SuperSU)
Can you please give me step by step instructions for safestrap? After this success I really don't want to mess up anything!
Edit: I followed these instructions (but with Nexus ROM) and it worked! Thank you so much for your help. Dealing with amazon devices definitely is frightening!
Code:
• Open SafeStrap from the app drawer
• Tap 'Reboot to recovery'
• You may be asked to grant root access, grant it
you should now be in recovery mode
• some have suggested a backup. If you desire, create a backup from *'Backup' button now, when done return to the main screen to continue*
• Tap 'Wipe'
• Swipe from left to right on the slider at the bottom to perform a factory reset
• Tap 'Home' when done
• Once at the main screen, tap 'Install'
• Scroll down to the folder 'Download', tap on it
• You should see the following three files:
cm-11-20xxxxxx-UNOFFICIAL-kodiak.zip
pa_gapps-modular-pico-4.4.4-20xxxxxx-signed.zip
UPDATE-SuperSU-vx.xx.zip
• Tap on cm-11...
• Tap 'Add More Zips'
• Tap on pa-gapps...
• Tap 'Add More Zips'
• Tap on UPDATE-SuperSU...
• Swipe from the left to the right on the bottom slider
After it's done loading, tap on 'Reboot System'
After the pre-initialization of apps, you are done! If you want root access, open SuperSU and follow the prompts.
Great you got it working! Enjoy Nexus.
Hi. I some how (wiped system like an idiot) erased the os from my son's fire hd 6 4th gen. I have the TWRP custom recovery, when I put the tab into adb sideload in twrp, and run the adb sideload for the update 4.5.3 bin file from cmd line I get errors. Any thoughts?
BELEAVAH316 said:
Hi. I some how (wiped system like an idiot) erased the os from my son's fire hd 6 4th gen. I have the TWRP custom recovery, when I put the tab into adb sideload in twrp, and run the adb sideload for the update 4.5.3 bin file from cmd line I get errors. Any thoughts?
Click to expand...
Click to collapse
There is a version of Cyanogenmod 11 (Stock android mod not FireOS) that you could transfer and install. It has google play too.
no amazon but you can download the amazon app store
BELEAVAH316 said:
Hi. I some how (wiped system like an idiot) erased the os from my son's fire hd 6 4th gen. I have the TWRP custom recovery, when I put the tab into adb sideload in twrp, and run the adb sideload for the update 4.5.3 bin file from cmd line I get errors. Any thoughts?
Click to expand...
Click to collapse
If you still get access to TWRP by power + Vol Up combo when booting, then flash the 5.2 bootloader so as to be able to sideload the 4.5.3 firmware as explained here http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267
Link to 5.2 stock firmware : http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
The Wizus said:
If you still get access to TWRP by power + Vol Up combo when booting, then flash the 5.2 bootloader so as to be able to sideload the 4.5.3 firmware as explained here http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267
Link to 5.2 stock firmware : http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
Click to expand...
Click to collapse
Thank you for your response. I attempting to sideload: I check to make sure the pc can detect the fire and I get it showing in the list. But when I attempt the sideload it doesn't work. Any thoughts?
BELEAVAH316 said:
Thank you for your response. I attempting to sideload: I check to make sure the pc can detect the fire and I get it showing in the list. But when I attempt the sideload it doesn't work. Any thoughts?
Click to expand...
Click to collapse
You need to install drivers for sideload mode. After going into sideload mode, look at device manager and find KFARWI(?) under Other Devices. Right-click, hit update and install drivers just as you did for "OS" mode.
It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.