Related
As the title says, just updated my z3tc(4g) to lollipop and wanted to reset it with stock recovery but I cant boot into it. Any advices? Booting and tapping vol up or down does nothing. Am I doing something wrong?
maybe try from adb with debugging turned on:
adb reboot recovery
Bruce666 said:
maybe try from adb with debugging turned on:
adb reboot recovery
Click to expand...
Click to collapse
Thanks but tablet just reboots normally, any other ideas?
vesu said:
Thanks but tablet just reboots normally, any other ideas?
Click to expand...
Click to collapse
There is currently no lollipop compatible recovery for the Z3TC. If you want to do a factory reset you need to do it from within android.
lowtraxx said:
There is currently no lollipop compatible recovery for the Z3TC. If you want to do a factory reset you need to do it from within android.
Click to expand...
Click to collapse
Thanks, I was already thinking about broken recovery but this explains it all.
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,
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!
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
First of all, Thank you for read this post.
Second, Please watch my video on the link below:
To be honest, I have change a few handset before but never seen problem like this before.
So, I'm actually have difficulty to boot into recovery again everytime I like to reboot recovery from TWRP itself.
Not just reboot recovery, but also bootloader. So, the one that normal only reboot system option. Even when I try to clicked the reboot recovery or bootloader, it straight goes to system when it start to booting.
I also already try to install the default recovery (the one that only show phone and USB cable) from my phone in order to erase the previous recovery.img, and after that reinstall the TWRP recovery mode. But the problem is never dismiss. Its back, I still cannot access the recovery mode from the TWRP itself.
So, what should I do if I want my TWRP normal again? The only installation method that I still haven't to try yet is fastboot method from PC because I'm using macintosh and didn't have windows PC at my home.
So, if there anyone here know what should I do to fix it, please let me know. If u can't download the video, please also have a look to this picture...maybe it will help you to understand what I mean
brittown said:
First of all, Thank you for read this post.
Second, Please watch my video on the link below:
To be honest, I have change a few handset before but never seen problem like this before.
So, I'm actually have difficulty to boot into recovery again everytime I like to reboot recovery from TWRP itself.
Not just reboot recovery, but also bootloader. So, the one that normal only reboot system option. Even when I try to clicked the reboot recovery or bootloader, it straight goes to system when it start to booting.
I also already try to install the default recovery (the one that only show phone and USB cable) from my phone in order to erase the previous recovery.img, and after that reinstall the TWRP recovery mode. But the problem is never dismiss. Its back, I still cannot access the recovery mode from the TWRP itself.
So, what should I do if I want my TWRP normal again? The only installation method that I still haven't to try yet is fastboot method from PC because I'm using macintosh and didn't have windows PC at my home.
So, if there anyone here know what should I do to fix it, please let me know. If u can't download the video, please also have a look to this picture...maybe it will help you to understand what I mean
Click to expand...
Click to collapse
No one has answer about this?
brittown said:
No one has answer about this?
Click to expand...
Click to collapse
Hello.This is a common problem for redmi 3.Press volume up+volume down and power button to enter TWRP
gilardino33 said:
Hello.This is a common problem for redmi 3.Press volume up+volume down and power button to enter TWRP
Click to expand...
Click to collapse
Have u seen my video?
Of course I can enter to TWRP by pressing the hard key. That's never be a problem for me.
My problem is, when I'm in TWRP, i never can booting into recovery again. Instead of go to recovery. It always booting to the system. Is that a common?
Before no but after 7.3.9 ROM and until now for me yes.
gilardino33 said:
Before no but after 7.3.9 ROM and until now for me yes.
Click to expand...
Click to collapse
Really? Wow thanks. I didn't know that. So if I try to change to other ROM which not based on china dev, it will help the TWRP back to normal?
Maybe.This problem with TWRP it's common in 3 latest dev roms in redmi 3 and redmi note 3.
gilardino33 said:
Maybe.This problem with TWRP it's common in 3 latest dev roms in redmi 3 and redmi note 3.
Click to expand...
Click to collapse
OK. Thanks for the information. I hope I can find a solution on this kind of problem...
Have a nice weekend