Related
I was running ParanoidAndroid perfectly until it crashed and not it gets stuck at the loading screen of the ROM (not the Google logo). I'm able to turn it off and get into Bootloader. From there if I choose Recovery mode, it gets stuck at Google logo.
If I plug it into the PC while in booatloader, it gets detected as "Android" but no driver (I'm sure I installed it before with the Toolkit). Toolkit just won't detect the device anymore, keeps getting stuck at the <waiting for device> command.
If I plug it into the PC while stuck at the ParanoidAndroid loading screen, I see MTP and Nexus in Device Manager but w/o drivers.
What can I do now? Any input is appreciated.
Thanks.
Bump.
Itaintrite said:
Bump.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Xentar712 said:
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Click to expand...
Click to collapse
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Itaintrite said:
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Click to expand...
Click to collapse
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Xentar712 said:
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Click to expand...
Click to collapse
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Itaintrite said:
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Click to expand...
Click to collapse
It worked for me only once after reflashing the recovery. Never again after that. Hopefully it gets fixed soon, but until then, I carry my USB cables with me if I'm flashing new roms
Sent from my Nexus 7 using Tapatalk 2
This will only work with system versions 5.0.X , will not work with Fire tablets on System version 5.1.1or higher
Required
PC/Mac/Linux although I will only cover PC
Can ADB/Fastboot be used on Linux and Mac?
You will need a way to copy Stock Firmware file to a SD Card
You will need a few files
Drivers
Stock Firmware
update-kindle-37.5.2.2_user_522054520.bin.zip - AFH -
Custom recovery I used Twrp
UPDATE-SuperSU-v2.46.zip if you want to root
Open Gapps zip if you want Google Services (I suggest ARM/5.1/pico)
Instructions
Install Drivers
Change Stock Firmware file extension from .bin to .zip
Copy Stock firmware to sd card
Insert SD Card in the KFFOWI/Ford
Boot to Fastboot Mode
Boot Custom Recovery
In Custom Recovery, Install Firmware.zip, SuperSU.zip, GApps.zip
Reboot
I covered most of these steps in
2015 Fire: Booting TWRP, Rooting, Installing Gapps with Video
Tomsgt Video also covers most of this using Amazon-Fire-5th-Gen-SuperTool.zip in
How to install CM12.1 rom on the Amazon Fire 5th gen
Note: I have tested this method by
Installing CM12.1, Booting cm12.1, Factory Reset in twrp, Rebooted, Installed Stock Firmware (nothing extra), Booted Stock Rom. It is possible that this method does not restore everything or reflash all partitions, but everything appears to work correctly.
Alt method: using Stock Recovery
If you do not have a way to get the Firmware file to the SD Card
try [HOWTO] How to restore firmware on your device + Amazon Firmware by Awesomeslayerg
[Video]How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tabletor
If you have a pc but not a sd card reader, you can try
adb sideload with
Cyanogen Recovery (2015-11-04) by ggow
If you don't have a pc, you can try
[Guide][Script]Fire Mobile Boot Helper - Boot imgs without your PC using android! by Harry44
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
sd_shadow said:
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
Click to expand...
Click to collapse
awesome write up buddy love it. you are all over this device thats for sure
Can I perform a full, stock recovery on 5.1.1?
I lost some stock Amazon apps (launcher, Amazon Video) during Root using AutoRootScriptFirev4.12.
I have used ADB to restore the 5.1.1 Update but it returns still missing the apps deleted during Root and no Launcher.
Both factory reset & sideloading the 5.1.1 Bin restore my tablet still with missing components.
Is 5.1.1. only an update and not the full restore?
ArmandSalmon said:
Can I perform a full, stock recovery on 5.1.1?
I lost some stock Amazon apps (launcher, Amazon Video) during Root using AutoRootScriptFirev4.12.
I have used ADB to restore the 5.1.1 Update but it returns still missing the apps deleted during Root and no Launcher.
Both factory reset & sideloading the 5.1.1 Bin restore my tablet still with missing components.
Is 5.1.1. only an update and not the full restore?
Click to expand...
Click to collapse
I think there isn't any way on 5.1.1 bud
Sent from my KFFOWI using Tapatalk
plase hlep me dump backup emmc
i need dump 1G or 4G, please root and dump file,
adb shell su -c " dd if=/dev/block/mmcblk0 of=/sdcard/fire.img bs=1024 count=4194304"
Please have a few questions please, I hope not bother anyone
sd_shadow said:
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
Click to expand...
Click to collapse
hi Please have a few questions please, I hope not bother anyone, I have two kindles 5th gen 5.1.1 full root, block OTA upgrade and install nova all with supetool then I try to install CM12 With flash fire apk but i got stuck in CyanogenMod logo, my pc recognizes mtp as fire and adb and fastboot working perfect but I can not boot intro stock recovery in any way, when I try to enter to stock recovery fire gets stuck in (amazon logo) forever and when I type (adb devices) adb show fire as fastboot device, I do not understand, is there any way to fix this?
jonathanjr321 said:
hi Please have a few questions please, I hope not bother anyone, I have two kindles 5th gen 5.1.1 full root, block OTA upgrade and install nova all with supetool then I try to install CM12 With flash fire apk but i got stuck in CyanogenMod logo, my pc recognizes mtp as fire and adb and fastboot working perfect but I can not boot intro stock recovery in any way, when I try to enter to stock recovery fire gets stuck in (amazon logo) forever and when I type (adb devices) adb show fire as fastboot device, I do not understand, is there any way to fix this?
Click to expand...
Click to collapse
did you try
fastboot.exe oem reboot-recovery
Sent from my Motorola XT1060 using XDA Labs
Yep keep stuck in (amazon logo forever) and when i tipe adb devices keep showing fire as fastboot devices, I read all your recommendations all very good to be honest with u and thanks to u and root jonky have two fires 5.0.1 With CM12 working well,thanks u all!!!
jonathanjr321 said:
Yep keep stuck in (amazon logo forever) and when i tipe adb devices keep showing fire as fastboot devices, I read all your recommendations all very good to be honest with u and thanks to u and root jonky have two fires 5.0.1 With CM12 working well,thanks u all!!!
Click to expand...
Click to collapse
if you can't get to recovery, there is no known fix
Sent from my Motorola XT1060 using XDA Labs
THANKS
sd_shadow said:
if you can't get to recovery, there is no known fix
Sent from my Motorola XT1060 using XDA Labs
Click to expand...
Click to collapse
is ok, thanks to u guys I know u all working hard here that helped me to get a lot experience
I tried to install TWRP. It won't boot into TWRP. Nor will it boot into stock recovery. All I am able to do is get it to FASTBOOT mode. I current'y have Slim rom on it. It stopped loading as well. It just sits there with the Slim logo rotating. Any help will be great.
musiqlives said:
I tried to install TWRP. It won't boot into TWRP. Nor will it boot into stock recovery. All I am able to do is get it to FASTBOOT mode. I current'y have Slim rom on it. It stopped loading as well. It just sits there with the Slim logo rotating. Any help will be great.
Click to expand...
Click to collapse
if it won't boot to stock recovery, there is no fixing
I installed the OS from Amazon OS 5.1.2 to Android 5.1.1. (Lollipop). It worked a few days and started intermittently working sensor and I decided to reinstall another Android 5.1.1. After reinstalling the tablet does not turn on. Then I went in fastboot and through ADB installed Amazon OS 5.1.1.
The result: the tablet when turn on does not show screen AMAZON, that is does not react to pressing the power button. When connected to the computer constantly appears and disappears "PreLoader USB VCOM Port".
Tell me, please, how can I restore the tablet after that?
[email protected] said:
I installed the OS from Amazon OS 5.1.2 to Android 5.1.1. (Lollipop). It worked a few days and started intermittently working sensor and I decided to reinstall another Android 5.1.1. After reinstalling the tablet does not turn on. Then I went in fastboot and through ADB installed Amazon OS 5.1.1.
The result: the tablet when turn on does not show screen AMAZON, that is does not react to pressing the power button. When connected to the computer constantly appears and disappears "PreLoader USB VCOM Port".
Tell me, please, how can I restore the tablet after that?
Click to expand...
Click to collapse
i have the same problem. So far the only fix is to order a used motherboard on the web and hope it isn't bricked. Amazon should really release a program to return the device to stock from the PreLoader USB-MTP mode.
There is this thread for the possible solution:
https://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747/
goldenpipes said:
Amazon should really release a program to return the device to stock from the PreLoader USB-MTP mode.
Click to expand...
Click to collapse
Amazon has a generous 'no questions asked' exchange policy during the warranty period which runs 90 days to 2 years depending on model and region. Device is not intended for enthusiasts as evidenced by aggressive lockdowns. Why would any company in their right mind release such a tool given the target audience?
Bricked my tablet but I'm able to boot into fastboot mode
Hello,
I have just softbricked my tablet because the wrong OpenGapps were flashing.
The problem is I can't start a custom recovery because the boot loader is too new
And I can't access my stock recovery because I've tried flashing TWRP from it in the past.
What can I do now? As I said earlier, I can access the device using Fastboot commands, but I don't know how to get at least one ADB interface working on the tablet so that I can upload the stock image to the device.
Thanks for any help!
TheGoliath said:
Hi,
I just softbricked my tablet 'cause of flashing wrong gapps?
The problem is, that I can't boot into a custom recovery (bootloader to new)
And I can't access my stock recovery because I tried to flash TWRP over it in the past.
So what can I do now? As I said, I'm able to access the device with fastboot commands but I don't know, how to get at least a adb interface running on the tablet so I can sideload the stock image.
Many thanks for any help!
Click to expand...
Click to collapse
You will not be able to reload stock FireOS from fastboot as the necessary commands have been disabled by Amazon. Pretty much game over if you can not access stock recovery and bootloader version is >5.0.x.
Can you describe "softbricked" symptoms in more detail? At what point during boot process does device hang/loop?
Davey126 said:
You will not be able to reload stock FireOS from fastboot as the necessary commands have been disabled by Amazon. Pretty much game over if you can not access stock recovery and bootloader version is >5.0.x.
Can you describe "softbricked" symptoms in more detail? At what point during boot process does device hang/loop?
Click to expand...
Click to collapse
OK. So I wanted to install the new Fire Nexus Rom and I may have installed the wrong package or something, but the symptoms are the following:
When I press the power switch, it turns on. Then the Amazon logo appears and after about 10 seconds the screen goes black again. The whole thing then repeats itself in a boot loop
i flashed stock update-kindle-37.5.2.2_user_522054520.
following a link in the forums
had to do it for pokemon
can i just flash any newer version as well this way or will ability to fastboot boot twrp then be gone?
thanks for any help
After some help
The other night my MOJO just reboot itself when I clicked on an App ( KODI ) and since then won't boot past the Mad Catz logo. I hadn't had it long and it wasn't rooted or modified in anyway. I'm looking for some way to do a hard reset either by attaching a keyboard or connecting it to a PC. Any advice is appreciated.
Install the fastboot drivers and the TWRP image on a PC, see the development section and the TWRP thread. Connect the booted PC to the MOJO with a USB male2male cord then power on the MOJO. Following the directions in the thread boot the MOJO to the TWRP image and do a factory wipe. If that doesn't do it then reinstall the firmware or a custom ROM.
kevinthefixer said:
Install the fastboot drivers and the TWRP image on a PC, see the development section and the TWRP thread. Connect the booted PC to the MOJO with a USB male2male cord then power on the MOJO. Following the directions in the thread boot the MOJO to the TWRP image and do a factory wipe. If that doesn't do it then reinstall the firmware or a custom ROM.
Click to expand...
Click to collapse
I've think I've managed to wipe the OS off my Mojo - I get back into fastboot but it says drivers not found, any idea how I can get back into TWRP as I know it is on the system
Msr Blobby said:
I've think I've managed to wipe the OS off my Mojo - I get back into fastboot but it says drivers not found, any idea how I can get back into TWRP as I know it is on the system
Click to expand...
Click to collapse
So far you're good. "Key driver not found" is normal, don't worry about it. Copy the TWRP .img to the same folder ON YOUR PC as the fastboot command. Now it depends on which fastboot you are using but you need to enter a command on the PC like:
fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
See the recovery thread:
http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
So you're actually booting to an image on the PC, not on the MOJO.
kevinthefixer said:
So far you're good. "Key driver not found" is normal, don't worry about it. Copy the TWRP .img to the same folder ON YOUR PC as the fastboot command. Now it depends on which fastboot you are using but you need to enter a command on the PC like:
fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
See the recovery thread:
http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
So you're actually booting to an image on the PC, not on the MOJO.
Click to expand...
Click to collapse
Thanks - it worked! I managed to reboot into TWRP and then ADB sideload the CM12 build onto my SDCard (it wouldn't let me access the ext sd where all the files were stored). Then recovery was pretty easy. Thanks. However, I'm still having problems with the CM12 build and wifi dropping out.....still that's another story.
Shield has Android TV 2017
I am following this process and the shield is not working.
—–
fastboot oem unlock
twrp boot (fail)
Infinite reboot
(controller a,b key pushing
power cable in)
hw mode bootloader connect to pc
(pc recovery img “fastboot-all.bat” Execution)
error devices not connect after install 2 things finished
—
shield tv Does not wake from sleep mode
pc to connect (pc devices manager display others-apx)
hw mode is not working
How can I recover it?
If your shield TV doesn't boot correctly, fastboot-all.bat won't work because you need to have adb working.
You should indeed rather follow the instructions given on Nvidia website, i.e. for Shield TV 2015 16GB with Marshmallow or newer installed:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Before that, be sure you use a good quality USB OTG cable.
Sounds like you can't boot into fastboot or bootloader mode.
If you can't, it means that you are hard bricked.
If you already had latest Nvidia experience version 5.1, there was no need to reflash the whole recovery image, PLUS you don't mention what recovery image you flashed.
To sum up your error was eather a bad usb cable (this a very known issue now, shield is picky) AND/OR wrong blob (which is the bootloader and it comes in all nvidia recovery image packages) flash.
What makes the device brick is a corrupted bootloader.
If bad USB and fail while flashing blob (which again is the bootloader), it gets corrupted.
If wrong blob flash (by using one that is not for you device model OR when attempting to downgrade to MM or lower bootloader), it gets corrupted.
Moral of the story:
Never mess with the bootloader a.k.a blob if you dont know what you're doing.
I know there are many hard bricked users around so better start reading. Take your time and make sure you understand all the instructions and also the pros and cons of the restore/unbrick method.
NOTE: just so you know next time for Shield TV 2017 , when you unlock bootloader and flash TWRP recovery or custom firmware you must root, because root with SuperSU disables some checks Nvidia run at boot. If you don't root, then your Shield will be stuck at boot.
- Sent from my Tapatalk Hub -
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Hello.
I attempted to root my Onn 7" (100015685-E). After flashing vbmeta.img and magisk_patched.img, I rebooted. NOw the tablet only boot loops, showing the attached image and rebooting repeatedly. I have tried pressing and hold Vol+ and Power simultaneously to no avail.
Are there other button-pressing combinations that can cause this to into recovery/bootloader mode?
Thanks!
snottzoid said:
Hello.
I attempted to root my Onn 7" (100015685-E). After flashing vbmeta.img and magisk_patched.img, I rebooted. NOw the tablet only boot loops, showing the attached image and rebooting repeatedly. I have tried pressing and hold Vol+ and Power simultaneously to no avail.
Are there other button-pressing combinations that can cause this to into recovery/bootloader mode?
Thanks!
Click to expand...
Click to collapse
I was able to recover my tablet. However, in attempting to get root, I think I accidentally flashed -A stock images onto an -E device. Does anyone have the 100015685-E stock images that I may flash with SP flash tool? (I have looked back through the threads. There are links to the files that probably worked sometime in the past, but not now).
snottzoid said:
I was able to recover my tablet. However, in attempting to get root, I think I accidentally flashed -A stock images onto an -E device. Does anyone have the 100015685-E stock images that I may flash with SP flash tool? (I have looked back through the threads. There are links to the files that probably worked sometime in the past, but not now).
Click to expand...
Click to collapse
I ran to the same situation you did. Have you but any change came across the stock images that is no where to be found not even here thought I ask seem no one want to share it
this might help https://www.getdroidtips.com/download-onn-surf-7-firmware-flash-file/ i just had a similar issue with my Surf 8 100011885 but i was able to find a stock rom and re-flash everything. here's the link i used https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file . i installed the rom on my 100011885 with no problems
snottzoid said:
I was able to recover my tablet. However, in attempting to get root, I think I accidentally flashed -A stock images onto an -E device. Does anyone have the 100015685-E stock images that I may flash with SP flash tool? (I have looked back through the threads. There are links to the files that probably worked sometime in the past, but not now).
Click to expand...
Click to collapse
You should mention how you recovered so others searching for solution can read. If the links you referred to were for first gen 7" google trashed half my stuff and yes those links are dead. The 7" when I rooted it did not have a ramdisk in the boot partition and had to be rooted by patching recovery.img. If anything happens to recovery, any corruption of recovery.img you lose ability to enter recovery or fastboot on that tablet from what I can remember anyways.
I'm in a looping orange state on an 8 inch ONN tablet. How'd you get it out of the loop? I've put it into flashboot, but flashboot on the cmd line returns
<waiting on device>
any ideas?
art1999 said:
I'm in a looping orange state on an 8 inch ONN tablet. How'd you get it out of the loop? I've put it into flashboot, but flashboot on the cmd line returns
<waiting on device>
any ideas?
Click to expand...
Click to collapse
Instead of using Flashboot try following the guide I used. Also, if you already have the boot image you might want to try this command: fastboot flash boot boot.img. that will only flash the boot partition. The same goes for any other partition you have; Utility=fastboot, Cmd=flash, Partition=boot, recovery, system, etc and Flash file=.img. Sometimes you have to use adb to reboot your device into the bootloader in order to use fastboot to flash a partition.
Eg:
adb reboot bootloader
fastboot flash boot boot.img
Here's a post of mine that may help:
(HELP NEEDED) Onn 8" gen 2, 100011885 no boot
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold...
forum.xda-developers.com