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
Related
Ok long story short, the other day I was doing the steps to get adb wireless working and I accidentally skipped the step after I chmod build.prop where you pull the build.prop and everything went downhill from there, leaving me with a blackscreen when I turn on my OUYA. I just did the alt + sysrq + i combo a bunch of times and got into CWM. I was going to do a backup the other day after getting adb wireless but didn't make it that far so I can't restore a backup, so I'm thinking I have two options. Factory reset, OR I can use the Install zip from sideload to flash the latest OTA. I'm thinking the later of the two would be the step to go, can anyone provide any advice on this? Thanks so much.
good times...
I had the same issue last friday. Black screen, and Ouya was seen as an MTP USB device on laptop. had to reinstall all drivers and such... had an issue when in recovery that changed the driver code this helped...
http://forum.xda-developers.com/showthread.php?t=2352658
I went the route of sideloading the OTA got file from here...
http://forum.xda-developers.com/showthread.php?t=2266629
also this helped..
http://forum.xda-developers.com/showthread.php?t=2344097
This issue has been resolved. I simply selected Install zip from sideload and cd'd to the directory where my current OUYA version's OTA was downloaded and did adb sideload OUYA-1.0.298-r1_ota.zip, rebooted and it worked. The first time I did a factory reset after the sideload due to a recommendation and it didn't work, so I had to do it again. It worked the second time around when I didn't perform the Factory reset.
Hello, I seemed to broke my ouya... I (stupidelly) formated my SD card in recovery... now I can't even get the ouya to be recognized in Windows... I tried sideloading OTA and it says that there aren't any devices connected... I should have just be happy with root access and SU and BusyBox, but no... I wanted to try some custom roms, now I bricked it... FML
Il_Padrino said:
Hello, I seemed to broke my ouya... I (stupidelly) formated my SD card in recovery... now I can't even get the ouya to be recognized in Windows... I tried sideloading OTA and it says that there aren't any devices connected... I should have just be happy with root access and SU and BusyBox, but no... I wanted to try some custom roms, now I bricked it... FML
Click to expand...
Click to collapse
Have you tried the all-in-one tools box that is posted in this forum? It may help in getting your ouya back up assuming you can get into recovery. Although if there is no OS on the ouya, you would not be able to get the init.d process to crash either. What guide did you follow that says to format the SDcard?
mikeones42 said:
Have you tried the all-in-one tools box that is posted in this forum? It may help in getting your ouya back up assuming you can get into recovery. Although if there is no OS on the ouya, you would not be able to get the init.d process to crash either. What guide did you follow that says to format the SDcard?
Click to expand...
Click to collapse
I tought it was like the phones... (stupid, stupid, stupid)
I have recovery, I was wondering if there is a way to install OTA or Custom Roms over OTG...
i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.
adeeb101 said:
i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.
Click to expand...
Click to collapse
You need a factory cable.
soupmagnet said:
You need a factory cable.
Click to expand...
Click to collapse
the problem is i''m not in USA ,its not available here
is there another way to fix it?
adeeb101 said:
the problem is i''m not in USA ,its not available here
is there another way to fix it?
Click to expand...
Click to collapse
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).
soupmagnet said:
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).
Click to expand...
Click to collapse
thank you i'll see what i can do
wait a minute, I rooted mine with a stock micro-USB cable
adeeb101 said:
thank you i'll see what i can do
Click to expand...
Click to collapse
Since I already see this coming, I'll go ahead tell you where you went wrong and how to avoid it in the future.
First off, there's really no need to "root" your Kindle Fire. The steps required to root the Kindle Fire involve installing custom recovery (TWRP in this case) to gain temporary root permissions so you can push Superuser.apk and the SU binary. However, all custom ROMs come pre-rooted, so rooting beforehand is unnecessarily redundant. Even if you wanted to keep the stock OS, there is a stock based ROM called MoDaCo that will give you what you want while saving you pretty much all the work of having to do whatever you wanted to do with a rooted stock device anyway.
Second, with custom recovery already installed, the only reason to install the 6.3.x software update from Amazon, is to revert the device to 100% stock (i.e. no root, no recovery, no custom bootloader). Where you failed is in attempting to install the update.zip without first doing a factory reset in recovery. The resulting problem will leave you with a device that has no working shell, and therefore no ability to change bootmodes or install custom recovery again.
The factory cable (mentioned earlier) puts the device in fastboot mode where you can reinstall custom recovery, custom bootloader, and change bootmodes using fastboot commands (or some script based utility), then you can use custom recovery to properly install a ROM of your choice (remembering to factory reset). It should also be noted, that you should never wipe anything in custom recovery until you have successfully used it to create a backup. Be sure to save your system partition at the very minimum, and you can always go back to delete it afterwards.
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
gk83916 said:
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
Click to expand...
Click to collapse
If you can boot in recovery install 51.1.4.0_514006420-rooted+updated, this is the last firmware that does not required a boot menu. As far as I know 51.1.4.1 requires it so not sure how did you manage to run this rev without the boot menu. Let me guess, did you try installing boot menu using Firetv Utility s/w? After reverting back to 51.1.4.0 follow the guide from AFTnews and install boot menu manual sending one commend at the time.
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
gk83916 said:
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
Click to expand...
Click to collapse
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
KLit75 said:
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
Click to expand...
Click to collapse
So I could just plug a USB drive in there and it would work?!
Thank you so much I will give it a try tonight
alright this is what happened I finial took care of this boot loop thing
the reason is i install boot menu twice so once the first boot menu try
to boot into kernel it goes to the second boot menu and that's how the
boot loop started
luckily i could still get into recovery so from there I tried everything
finally i find the think called advanced putty
from there I was able to load 5140 and removed both menus
reroot busybox did everything and now got a fire tv fully working
rooted and all good
Thank everybody for helping out
good luck
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Wow.. Exactly same result doing exactly same thing!!
Don't have a USB keyboard so haven't tried that yet. Also while searching I came across a method which involve connecting FTV with computer using a A to A type USB cable while power is unplugged and then putting the power cable back on triggers fastboot mode, did you try that?
i am too, now i can not connect:crying:
Unbricked.. Yay!!
omega99 said:
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Click to expand...
Click to collapse
vn_soft said:
i am too, now i can not connect:crying:
Click to expand...
Click to collapse
So I was able to unbrick my AFTV with the same Alt+Prt Scr+i keyboard method already posted before. It took sometime and AFTV rebooted 3-4 times before finally going to recovery, since I had cwm recovery installed, it directly went to cwm.
OP, I dont know why this method didn't work for you.. As i mentioned above, it didn't go to stock recovery but directly to cwm. I guess you should try again.
To anyone who does the same mistake again, I had the soft brick because I missed flashing the FTV boot menu by rbox. I was coming from older version ( 51.1.3.0_513011820), and while I did install the rbox's prerooted stock 51.1.4.0_514006420+updated before flashing the latest update, I missed flashing the boot menu (I did know about it and even moved the .img file to FTV with all other files, somehow just forgot to flash it inbetween the 2 updates).
I have the same issue but managed to get clockwork mod to be displayed. What option did you choose? Install from zip? Clear partions?
jainanshal said:
So I was able to unbrick my AFTV with the same Alt+Prt Scr+i keyboard method already posted before. It took sometime and AFTV rebooted 3-4 times before finally going to recovery, since I had cwm recovery installed, it directly went to cwm.
OP, I dont know why this method didn't work for you.. As i mentioned above, it didn't go to stock recovery but directly to cwm. I guess you should try again.
To anyone who does the same mistake again, I had the soft brick because I missed flashing the FTV boot menu by rbox. I was coming from older version ( 51.1.3.0_513011820), and while I did install the rbox's prerooted stock 51.1.4.0_514006420+updated before flashing the latest update, I missed flashing the boot menu (I did know about it and even moved the .img file to FTV with all other files, somehow just forgot to flash it inbetween the 2 updates).
Click to expand...
Click to collapse
i' ve solved this problem, my AFTV stuck in white logo, after i use "Alt+Prt Scr+i " it came into color logo, then I use "Alt+Prt Scr+i " several time, finally it boot in CMW recovery. I've installed an older rom, it is OK now.
I thinks the newest Rom have problems, so plz wait until the author fix it. TKS for all:good:
vn_soft said:
i' ve solved this problem, my AFTV stuck in white logo, after i use "Alt+Prt Scr+i " it came into color logo, then I use "Alt+Prt Scr+i " several time, finally it boot in CMW recovery. I've installed an older rom, it is OK now.
I thinks the newest Rom have problems, so plz wait until the author fix it. TKS for all:good:
Click to expand...
Click to collapse
Ok I'm at the cwm recovery screen but how can I load up an older firmware? I tried adb to connect to the IP address of the box and it says it cannot connect
Berrybare said:
Ok I'm at the cwm recovery screen but how can I load up an older firmware? I tried adb to connect to the IP address of the box and it says it cannot connect
Click to expand...
Click to collapse
If you in cam recovery screen, you can see your fire tv box's ip at the low left screen. You can not connect cause of your ip has changed (in my ip changes from 192.168.1.103 to 192.168.1.110).
Then you can use adb push to copy rom image to your fire tv and install it. Good luck
vn_soft said:
If you in cam recovery screen, you can see your fire tv box's ip at the low left screen. You can not connect cause of your ip has changed (in my ip changes from 192.168.1.103 to 192.168.1.110).
Then you can use adb push to copy rom image to your fire tv and install it. Good luck
Click to expand...
Click to collapse
Thanks. So I should connect adb using the IP address found on the bottom left of cwm screen?
I have same problem too.
omega99 said:
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Click to expand...
Click to collapse
I have same problem too. Any solution ???
Berrybare said:
Thanks. So I should connect adb using the IP address found on the bottom left of cwm screen?
Click to expand...
Click to collapse
Yes.
1.you can use command adb connect 192.168.xxx.xxx
2. Adb push (your path rom file)
Or use tool http://forum.xda-developers.com/showthread.php?t=2786505
Good luck
I had the same issue with the latest custom firmware soft bricking my device. I managed to get back to recovery screen, then reloaded previous firmware and everything was back as it was.
Can anyone advise on what steps are best to get the newest custom firmware on my device ?
I have read things about re-flashing rbox recovery screen, etc ?
If you are on 51.1.5.0 and you are stuck on the amazon logo and never saw bootmenu, that means you didn't follow the instructions for flashing 51.1.5.0 which say you must have bootmenu.
I just updated last night and it works great--painless process. And I was coming from 51.1.4.0 which on this particular aftv meant unlocking bootloader, installing boot menu, then pushing the rom.zip.
A lot of steps but I thought it was really easy. I followed the guide aftvnews meticulously put together and don't think I strayed from it at all.
*Obviously this post is for people reading about issues other users are reporting and it might give them pause to install it. I don't think it should because its not hard. Take the time to check all md5 sums! It might be worth it...make certain ALL prerequisites are met.
rbox said:
If you are on 51.1.5.0 and you are stuck on the amazon logo and never saw bootmenu, that means you didn't follow the instructions for flashing 51.1.5.0 which say you must have bootmenu.
Click to expand...
Click to collapse
This is where I went wrong. I have 4 fire tv's, and I have always updated them together with no problem. I mistook "boot menu" to think that was a reference to CWM menu. I always thought of that as the "boot menu", when in fact that was my mistake and the cause for bricking the two devices. In this scenario there is no way to unbrick that I can find. The keyboard alt i print screen is a no go, fastboot is a no go, I have tried everything but unless there is something I am missing, I made a mistake and it cost me two firetvs.
crayneogeo said:
This is where I went wrong. I have 4 fire tv's, and I have always updated them together with no problem. I mistook "boot menu" to think that was a reference to CWM menu. I always thought of that as the "boot menu", when in fact that was my mistake and the cause for bricking the two devices. In this scenario there is no way to unbrick that I can find. The keyboard alt i print screen is a no go, fastboot is a no go, I have tried everything but unless there is something I am missing, I made a mistake and it cost me two firetvs.
Click to expand...
Click to collapse
Well that is why the post for the prerooted images links to the boot menu post... but fastboot will only work if you did the full unlock. If you're not fully unlocked and sysrq doesnt work, then you are stuck.
vn_soft said:
Yes.
1.you can use command adb connect 192.168.xxx.xxx
2. Adb push (your path rom file)
Or use tool http://forum.xda-developers.com/showthread.php?t=2786505
Good luck
Click to expand...
Click to collapse
Thank you so much!! just a little heads up, you will need to connect the Fire TV with the LAN cable so this could work, then you could use ADB from your computer to push the correct rom, my mistake was that I installed Boot Menu before updating to 51.1.4.0 and then I updated to 51.1.5.0, big mistake! you need to install Boot Menu before updating to 51.1.5.0 and to fix my problem I just downgraded to 51.1.4.0 from ClockworkMod Recovery
Cheers!!
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!