Hi everyone. I have an old firetv that I haven't updated ever since I rooted it.
TL;DR: I would like to update the firmware to either the latest rbox custom rom or the latest official to get external USB disk functionality.
Unfortunately, I can't get past the white fire tv logo screen no matter which method I use (both bootleg rom and the official amazon update process).
adb reboot recovery => white logo. There are no USB devices attached to the firetv fyi while I'm booting.
I rooted my device using the adbfire tool and I distinctly remember I never got the clockworkmod and the bootloader unlock steps to work. I figured I don't really need that anyway, so I've been using the device just fine with Kodi. BTW, the device is not bricked. I just have to replug the power when it gets stuck on the white logo screen for it to go back to normal.
I think I somehow corrupted the recovery partition (if that makes any sense?).
Because I wasn't going anywhere with the unlock->bootleg rom process, I decided I don't care about root anymore.
I reenabled updates (pm enable com.amazon.dcp) and let the device download the latest rom though the amazon system menu. I saw the progress bar go 100% and the device rebooted... alas white logo screen. I gave it half hour then hard boot it. I'm back to my old rom... still works just fine but I need this external usb function for my vacation...
Regarding the boot unlock, the "partial unlock" steps work for me. i.e. I get "Attempting to unlock… All done!". However, the full unlock binary doesn't seem to have any affect after the autoreboot. aftv-full-unlock gives me the long random string as expected before it goes rebooting, but after it reboots and I 'adb shell', it gives me the [email protected] instead of root[email protected] (meaning the unlock didn't work).
How can I recover my recovery?
Just an update, I managed to fix this.
In my case, the aftv full unlock did not give me the root prompt (#) on adb shell. I was running 51.1.0.1.
On a whim, I decided to install the stock recovery (because I couldn't get into cwm) and try upgrading to 51.1.0.2 manually using these instructions http://forum.xda-developers.com/showthread.php?t=2796067
As soon as the system update finished and the firetv booted, I adb shell'd in and voila... root shell. I didn't even have to run aftv full unlock again. Apparently it was already fully unlocked, and I just had to upgrade from 51.1.0.1.
From there, I installed the latest ClockworkMod, upgraded to 51.1.4.0, installed the boot menu, then finally upgraded to the pre-rooted 51.1.6.3!
Related
I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.
KoBRaQ said:
I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.
Click to expand...
Click to collapse
Did a little more research.Guess I should try a fastboot cable maybe?
connected for a split sec is all KFU needs to send reboot to fastboot mode command.
Did you try rebooting kindle few time while running KFU?
I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.
clifford25501 said:
I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.
Click to expand...
Click to collapse
which windows version 7, 8...?
I try on win xp and win7. First it was detected as OMAP4320 but after driver installing its detects only as TI BOARD. This happaeds after installing otter x bootloader and tpwr 2.7.0.0. I live it for a night because i couldnt install driver for otterx fastboot. When i check device on the morning it was in this state and do not power on.
HI Guys,
I need some help, i cant peform a factory reset or boot into CWM, i was not able to reboot into CWM after the first installation. I rooted my AFTV these are the steps.
1) block updates on router.
2) fire tv running stock version 51.1.0.1
3) rooted fire tv (installed towelroot, supersu and busybox)
4) disable updates via adb on the fire tv
5) partially unlock boot loader
6) install CWM 6.0.5.1.4a (yes i granted su permission)
At this point fire tv rebooted but it did not bring CWM instead it went to straight to normal amazon boot. I tried alt+printscn approach but didn't work. When i try to get into cwm via adb command "adb reboot recovery" it will reboot and for a split sec i see blue screen and but then it boots up in normal amazon menu.
So i decided to do factory rest and start over.....problem is it is not really resetting the box, it takes me to the initial amazon sign in screen, i enter my login info and bang into main menu and all my apps that was there before are still installed.
Good news is i can still adb to the box and have root access.
any suggestion who to fix this?
I am still running on stock version 51.1.0.1 and i have not installed rbox boot menu. Also, i have done rooted 6 boxes so i am fairly familiar with the process and steps to follow.
Thank you
Try this.....
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
bula1ca said:
Try this.....
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
Click to expand...
Click to collapse
I also tried to upgraded but after the zip file was adb to the box fire tv did reboot but didn't go thru the installation process.
Any other suggestion guys please? I hate to return this box since it has root since it is getting harder and harder to find AFTV which has root able firmware?
I have been trying to get into CWM via "Alt+print Scrn + i" for few days now but without any luck i have tried this with wired and wireless keyboard, I hold these 3 keys simultaneously as soon as i see the white amazon logo and again when i see the colorful amazon log. Am i doing something?
However, when i do manage it get into CWM. What should i do? Should i select wipe data/Factory reset option? Will this take my AFTV to the way it came from amazon? I am still running amazon stock version 51.1.0.1 and fully rooted with Super su and busybox installed.
Thank you
ashsha7877 said:
I also tried to upgraded but after the zip file was adb to the box fire tv did reboot but didn't go thru the installation process.
Any other suggestion guys please? I hate to return this box since it has root since it is getting harder and harder to find AFTV which has root able firmware?
I have been trying to get into CWM via "Alt+print Scrn + i" for few days now but without any luck i have tried this with wired and wireless keyboard, I hold these 3 keys simultaneously as soon as i see the white amazon logo and again when i see the colorful amazon log. Am i doing something?
However, when i do manage it get into CWM. What should i do? Should i select wipe data/Factory reset option? Will this take my AFTV to the way it came from amazon? I am still running amazon stock version 51.1.0.1 and fully rooted with Super su and busybox installed.
Thank you
Click to expand...
Click to collapse
You need to get in CWM to upgrade to a pre-rooted image.
Have you tried to downgrade (reverse) to factory as per above link? That should work without no issues, should bring your box back to stock and you can start from zero again. I done it numerous times however you need to read carefully and follow the guide step by step sending all the commands one by one in ADB
bula1ca said:
You need to get in CWM to upgrade to a pre-rooted image.
Have you tried to downgrade (reverse) to factory as per above link? That should work without no issues, should bring your box back to stock and you can start from zero again. I done it numerous times however you need to read carefully and follow the guide step by step sending all the commands one by one in ADB
Click to expand...
Click to collapse
I tried to revert it back to stock following aftvnews guide step by step, read it over and over before actually doing it but on the final steps, AFTV will reboot but does not install the actual files.
i also rooted another box last night and everything went fine so i am not sure whats up with this box.
Thanks
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.
On my AFTV2 I had flashed sloane pre-rooted 5.2.4.0 and TWRP Recovery V3. I decided I wanted to rollback to 5.0.5 because of FireStarter not working. I checked all the boxes under the Advanced Wipe section of TWRP and got the "Warning no OS installed..." error. I rebooted and I am stuck on the white Amazon logo with a slow flashing white LED. Through several attempts to use rbox's unbrick method, I never get past the "Waiting for preloader" stage. My computer detects the fire box but comes up with an error when installing the drivers. I don't know how to go about any repairs if I can't even get connected to it. I see others out there with issues similar to this but never quite find a solution for the lack of usb connectivity to make repairs.
From what I've read, you never wipe /system and then reboot.
It's a shame you did not read the red bold print on the AFTV2 ROMs page here: https://forum.xda-developers.com/fire-tv/development/firetv-2-sloane-prerooted-stock-images-t3309783
It says: WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER
Everything I've read says if you do this you now have a paperweight.
You are indeed correct on all fronts... Thing is I never got to the rollback point. I never even attempted to install the old version over the new one. I got stuck right after the wipe not being able to do anything else. I would gladly take back what I already installed at this point.
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.
Lesson learned. I thought it would reboot back into TWRP... I guess not.
I think I may be in this same boat. For some reason, my USB keyboard may have wigged out and ticked System, too.
Ugh
So is there really no solution at all, if you reboot after system wipe in TWRP?
Hello, I had the same issue. Wiped system and had to restart, at least I tought I had to.
So there is no solution than to get the fire tv alive again?
So I appear to have a soft bricked phone. It is on stock firmware, although it has been unlocked previously in order to flash that over the Three custom firmware.
It randomly rebooted itself into a boot loop where it would get as far as the Razer logo and restart itself. I got into recovery and tried to factory reset it, at which point it claimed to have formatted /data but then complained it failed to mount /mnt/vendor/persist (no permission).
I can't see it in adb devices unless I put it in sideload mode - I presume I can't sideload anything anyway unless it is unlocked for flashing.
I can reboot to the bootloader and then see it in fastboot but I can't do very much there because the bootloader is not unlocked (so I can use Netflix, my banking app, etc), but I can't boot to the OS in order to unlock it or make sure adb debugging is on. The general instructions on Razer's website to do fastboot flashing unlock or unlock_critical don't seem to work as I think this needs the phone to be in 'download mode' which doesn't seem to be a thing since the Pie update. So if I try to reflash stock firmware it just complains that everything is locked.
Is there any way to get it into a flashable state without booting into the OS, or am I just screwed?