So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
If it failed to flash... you rebooted because... The only way to get back to recovery is the printscreen method, but because you have a corrupt system, it's not going to be easy to trigger it.
ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
I had this same issue, I attempted to install using the sideload command and it kept failing. To get the update to install, I pushed the update to the /sdcard/0 and installed from there, and it installed with no dramas.
No help on recovering your device though, just my experience in case it happens again.
Thanks for replies... I guess I'll try to get back into recovery again tonight. When pressing the 3 kb buttons... is it press and hold immediately after plugging the ftv on or is it repeatedly pressing all 3 buttons? If I do trigger recovery and restore, what actually gets restored? Is the the prior working version? Do I need to worry about it updating an losing root?
Btw I did push the rom to /sdcard/0 so not sure why it failed maybe bad download.
Related
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Bad download/corrupted file?
Wait my reading caught up with me. You say it is still booting into stock? That doesn't sound like bad firmware download after all. Sorry... I don't know then! Someone else should have a thought.
I read it once again and realize you restored stock. Lol I go with my original suggestion. Redownload and reflash.
Sent from my GT-p511x
gordonj56 said:
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Click to expand...
Click to collapse
The "weird rotating triangles" is the stock AOSP boot animation. 9 times out of 10, when your device gets stuck on the boot animation, it is from not wiping data in recovery before flashing the ROM. Boot into recovery, factory reset, then reboot to see if it fixes the problem.
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
jonchill said:
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
Click to expand...
Click to collapse
I dont know the fix actually. but its not safe to do an OTA update when you're not in stock(recovery)!
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
bur2000 said:
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
Click to expand...
Click to collapse
Thanks for this worked a treat, never to be repeated.
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
I just received my brand new FireTv and luckily it was on firmware 51.1.0.1. I was able to properly root the device but cannot upgrade or downgrade the firmware using any manual methods or tools/scripts. Every time the FTV tries to boot into recovery it just FREEZES at the white Amazon logo and sits there forever. If I end up unplugging it, it reboots back into the original firmware. Doing a factory reset via the settings menu or remote button combo has the same effect where the FTV again gets stuck on the Amazon logo....
The 2 update addresses are blocked via DNSMasq since the beginning. I've also tried with and w/o PM Disable, loading up a custom bootloader and reinstalling the stock bootloader. Tring to enter recovery by using the keyboard key combo just reboots the device and freezes it again at the Amazon logo. There is also no powered usb hub connected....
Is there any way I can :
1) manually restore the device using ADB (ie. By deleteing folders)
2) force a manual update on the recovery menu
3) correct any recovery boot errors
4) or update firmware without the need of the recovery menu
Willing to try pretty much anything....
Any help would very appreciated.
UPDATE:
Figured out how to manually restore. Unfortunately no impact on the recovery boot freeze:
adb shell
su
wipe data
Over 100 views and no one can help with this? Really?!? Rbox?
qwertywarez said:
Over 100 views and no one can help with this? Really?!? Rbox?
Click to expand...
Click to collapse
did you try with the 2 urls unblocked while using pm disable method ? probably wont help but i thought those urls need to be unblocked on a factory reset?
nhumber said:
did you try with the 2 urls unblocked while using pm disable method ? probably wont help but i thought those urls need to be unblocked on a factory reset?
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried without the 2 URLs and it still hangs at the white Amazon logo when rebooting to recovery. Any other ideas?
qwertywarez said:
Thanks for the suggestion. Just tried without the 2 URLs and it still hangs at the white Amazon logo when rebooting to recovery. Any other ideas?
Click to expand...
Click to collapse
so your rooted and you can boot normally fine, just cant boot into recovery? did you unlock your device prior to installing the newest cwm?
nhumber said:
so your rooted and you can boot normally fine, just cant boot into recovery? did you unlock your device prior to installing the newest cwm?
Click to expand...
Click to collapse
yes I'm rooted and unlocking the bootloader was successful. Just can't get into recovery. I also get the freeze when doing a factory reset from the device. Even on stock recovery.
Seems that the bootloader freezes the command to send to recovery....
qwertywarez said:
I just received my brand new FireTv and luckily it was on firmware 51.1.0.1. I was able to properly root the device but cannot upgrade or downgrade the firmware using any manual methods or tools/scripts. Every time the FTV tries to boot into recovery it just FREEZES at the white Amazon logo and sits there forever. If I end up unplugging it, it reboots back into the original firmware. Doing a factory reset via the settings menu or remote button combo has the same effect where the FTV again gets stuck on the Amazon logo....
The 2 update addresses are blocked via DNSMasq since the beginning. I've also tried with and w/o PM Disable, loading up a custom bootloader and reinstalling the stock bootloader. Tring to enter recovery by using the keyboard key combo just reboots the device and freezes it again at the Amazon logo. There is also no powered usb hub connected....
Is there any way I can :
1) manually restore the device using ADB (ie. By deleteing folders)
2) force a manual update on the recovery menu
3) correct any recovery boot errors
4) or update firmware without the need of the recovery menu
Willing to try pretty much anything....
Any help would very appreciated.
UPDATE:
Figured out how to manually restore. Unfortunately no impact on the recovery boot freeze:
adb shell
su
wipe data
Click to expand...
Click to collapse
From your post above your where at 51.1.0.1_user_510055620 (all my FTV's have been at this FW out the box) all you had to do was ROOT following the AFTV Rooting Guide then then install CWM. Downgrading was not needed. And upgrading was only for after installing CWM. Then you would upgrade with the PreRooted FW.
Y314K said:
From your post above your where at 51.1.0.1_user_510055620 (all my FTV's have been at this FW out the box) all you had to do was ROOT following the AFTV Rooting Guide then then install CWM. Downgrading was not needed. And upgrading was only for after installing CWM. Then you would upgrade with the PreRooted FW.
Click to expand...
Click to collapse
Yes, CWM after my initial root was the first thing I tried but I went back to stock recovery to do a manual upgrade to 51.1.0.2 because CWM recovery wasnt working. i figured CWM preferred stock 51.1.0.2 but could not even upgrade to that on stock recovery due to the recovery freeze.
qwertywarez said:
Yes, CWM after my initial root was the first thing I tried but I went back to stock recovery to do a manual upgrade to 51.1.0.2 because CWM recovery wasnt working. i figured CWM preferred stock 51.1.0.2 but could not even upgrade to that on stock recovery due to the recovery freeze.
Click to expand...
Click to collapse
CWM prefers anything 51.1.0.2 or lower. It makes no difference to it installing it. Are you sure you had rooted it correctly ? I would try to reflash the "recovery-stock-51.1.0" with the AFTV Utility & and after that reflash the 51.1.0.1_user_510055620. DO NOT rename them to update.zip if you are using the AFTV Utility. After that you will need to reRoot again.
Which version of CWM where you trying to install ??
Y314K said:
CWM prefers anything 51.1.0.2 or lower. It makes no difference to it installing it. Are you sure you had rooted it correctly ? I would try to reflash the "recovery-stock-51.1.0" with the AFTV Utility & and after that reflash the 51.1.0.1_user_510055620. DO NOT rename them to update.zip if you are using the AFTV Utility. After that you will need to reRoot again.
Which version of CWM where you trying to install ??
Click to expand...
Click to collapse
Thanks for the assistance.
I rerooted, flashed stock recovery and stock Fw 51.1.0.1 all using the AFTV utility and the re-flash process of the original stock Fw does not complete since it still stays stuck on the white Amazon screen. PS: AFTV utility v0.30 requires the renaming to update.zip else it give an error.
When flashing CWM recovery, I use the latest 6.0.5.1.4a but also tried older versions.
qwertywarez said:
Thanks for the assistance.
I rerooted, flashed stock recovery and stock Fw 51.1.0.1 all using the AFTV utility and the re-flash process of the original stock Fw does not complete since it still stays stuck on the white Amazon screen. PS: AFTV utility v0.30 requires the renaming to update.zip else it give an error.
When flashing CWM recovery, I use the latest 6.0.5.1.4a but also tried older versions.
Click to expand...
Click to collapse
For 6.0.5.1.4a you would of had to unlocked the bootloader first. Try again to do the keyboard reset again.. See if this time it comes thru...
Y314K said:
For 6.0.5.1.4a you would of had to unlocked the bootloader first. Try again to do the keyboard reset again.. See if this time it comes thru...
Click to expand...
Click to collapse
Yes, forgot to mention. The bootloader was unlocked. Still the same problem.
Any other ideas?
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
henningdalgaard said:
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
Click to expand...
Click to collapse
Install 51.1.4.0 from CWM to fix it. Then follow all the instructions/requirements for the latest.
thanks! I installed 51.1.4.0 pre-rooted rom CWM and it worked. I thougt it failed and started the loop again but after a wile it booted into the amazon software.
I used the same one...
SSAPIR11 said:
I installed 51.1.4.0 to un-brick. i followed the guide to install su and busybox, verifited rom. I installed custom rom 51.1.5.0_515030720, rebooted and now stuck at amazon fireTV logo. any suggestions?
Click to expand...
Click to collapse
Seems you followed part of the guide but did you take all precautions? You need boot menu and unlocked bootloader for that fw. If you have these and confirmed they work, plus you checked mdsums...I can't imagine why it's in bootloop.
henningdalgaard said:
I am able to get into CWM with the ALT+i+prt scrn method.
Click to expand...
Click to collapse
What is that method exactly?
Alright, got a question, tried to find an answer everywhere.
Went to update to the newest version through CWM (51.1.5.0_515030720). Forgot to re-install Boot Menu, am now in a brick/bootloop. Despite what I've read, no amount of wiping the data/cache/dalvik cache gives me back the option to simply "reboot." In addition, all the guides tell me that I need to downgrade by installing 51.1.4.0_514006420. That's all well and good, but I have no way to get 51.1.4.0_514006420 onto my Fire TV to install it. Sideloading doesn't work, as ADB isn't functioning properly through CWM. Fastboot doesn't let me install roms or push files on.
Can someone please help me figure out what to do next? I can get to recovery, I have a keyboard, and I don't know how to get this older rom onto the Fire TV.
Neo3D said:
What is that method exactly?
Click to expand...
Click to collapse
there is a guide here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/