I woke up this morning and turned on my tablet, upon each startup it rebooted. What I have tried:
Fastboot
Recovery img used: NVIDIA SHIELD Tablet K1 Recovery OS Image 5.2.0 2017/06/28
Upon doing the steps:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
I then tried to use Recovery Mode in fastboot, it reboot then goes to the android "No Command" Screen. After holding vol up + power my tablet will blackscreen. On my PC my tablet is recognized as "APX" with "Unavailable Drivers". I left it for like 20 minutes and tabet still blackscreened and PC still showing my device as APX. Force is back into fastboot and my PC then recognizes as fastboot again.. I am at a loss for what to do any suggestions as I'm not the most literate person when it comes to technical android issues, ADB and controlling my device via the terminal.
Note: Prior to this my tablet has been working fine, unrooted, and the device was only unlocked after the issues of this morning
Cause
I have now gotten my tablet out of the bootloop. When going into recovery after the android "No Command" I held vol + up and got a blackscreen, i found what the recovery menu is supposed to look like and tried navigating blind and hope for the best... That worked and I managed to get the factory reset after just waiting at a black screen.
Now that I managed to get out of the bootloop, I've gone back into fastboot recovery for the hell of it and I'm still getting blackscreen instead of the recovery menu. How does one go about fixing that, because knowing my luck I'll have issues again and not have a recovery menu.
All that aside, I'm pretty certain the cause was Kodi v18.2. My FireTV Stick also running the same version of Kodi is currently stuck in a bootloop now and both devices were loaded up with Kodi 4 days ago. Not sure why now both devices were affected but given the circumstances I figure Kodi was probably the cause
Related
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
timandjulz said:
Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
Click to expand...
Click to collapse
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Bricked!
TheYoz said:
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Click to expand...
Click to collapse
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
timandjulz2 said:
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
Click to expand...
Click to collapse
No bootloader menu at all now ?
flumpster said:
No bootloader menu at all now ?
Click to expand...
Click to collapse
Nope. Based on what I have read, it is now thoroughly bricked.
Asus TF201 stuck on Asus Logo screen + "this device is unlocked" -- Newbie here!
Hi guys,
First off- I have to clarify that I don't know squat about Android..
I got this TF201 tablet from a technology-ill friend who asked if I can do something about it.
I've encountered many posts of people with this issue:
* Powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner (and the nVidia Logo on the bottom right).
* Trying to power off the tablet only causes a power cycle, and it gets stuck in the same screen all over again.
* Trying to boot into fastrecovery (I think that's how it's called? - pressing the down volume button+power button) gets to the same stuck on screen as mentioned.
* Only way I got it to power off (I think) is by pressing the up volume button+power button and then first releasing the power button after the screen is blank (and only after the volume button).
* Connecting the tablet to the computer doesn't seem to work - it won't recognize the USB device (I do see "APX" under the list of Other Devices on the Device Manager) - can't seem to find (working) drivers.
I've read that there's a way to solve this using NVFlash -- don't think I have that..
Found other workarounds, but as I mentioned - I don't know how to get around much in this territory.
Anyone who's patient enough to help me out (if such thing is even remotely possible) ?
It will be much appreciated !
help?
I tryed install the v30, and later v26 version, but do not work.
When powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner and the nVidia Logo on the bottom right.
Trying start with power mode, but boot do not start, only RCK mod recovery/fastboot started.
I think, that device is not unlocked. How to check/verify the device really unlocked? Or any idea? Please help me. Thanks.
Have one pf you @msarg77 or @skew01 got the tablet working again?
I am stuck with a tf201 which has TWRP 2.8 but after installing Katkiss 6 it won't boot; keeps rebooting...
deltabet, Can you get into the TWRP console?
NP
I'am sorry Nektopoli that i did not answer you any sooner.
The original fault was that i had formatted the tab with the wrong file system; it should have been f2fs.
After that is was Murphy, i run into other problems ending up with no fastboot, no adb, no TWRP only APX mode.
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6, but had to reinstall the original Asus firmware with the nvflash backup i had made.
An other problem i run into was that my tablet had an older bootloader 10.4.2.15 and this should have been 10.4.2.18.
With the reinstall of the latest Asus firmware (from support site Asus) i received the correct bootloader.
Anyhow, I am glad the tab is working again. And i have learned a lot about installing a rom on an Android tab.
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Same Problem... Different Day...
Nektopoli said:
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Click to expand...
Click to collapse
Hya Gang... I seem to have the same problem.....
The good news here is that I am able to get into the bootloader, and I do have BootLoader: 10.6.1.27.1 and I am able to fastboot into my windows computer... I have tried fastboot flashing both the flatline TWRP and the latest TWRP but here is my problem..
It will start into the TWRP recovery screen for a few seconds... then goes black. This computer was working fine running KatKiss a few weeks ago, then one night just crashed, went into the above described bootloop and got me stuck in this situation...
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\BLOB.FILE <TWRP zip file
fastboot -i 0x0B05 reboot
Good Luck
NP
Nektopoli said:
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
fastboot -i 0x0B05 reboot
Good Luck
NP
Click to expand...
Click to collapse
Regarding this line:
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6 said:
what did you use to restore your id files?
Click to expand...
Click to collapse
Krysiul said:
Regarding this line:
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Click to expand...
Click to collapse
Yes, but I made a mistake, it needs to be flashed to the recovery partition NOT system
NP
asus tf201 stucked on "the device is unblocked"
I seem to have the same problem with my asus tf201
Have you solved this problem?
shehada said:
I seem to have the same problem with my asus tf201
Have you solved this problem?
Click to expand...
Click to collapse
You need a computer or laptop (windows 7 or XP is preferred) with;
Universal_Naked_Driver_0.72: https://forum.xda-developers.com/attachment.php?attachmentid=1489873&d=1353190173
and
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Then you can plug the TF201 into the computer and see if you can receive fastboot commands like: adb reboot
NP
hello
Yesterday my WileyFox Spark+ came in, which is still equipped with COS13.0.1, based on Android 6.0.1 and encrypted.
For disable encryption,i had followed the following process:
- factory reset whith sitting and recovery mode,
but without result because turned out the phone was encrypted with a startup pattern already from the box.
As I was unable to root my device, I have used adb and fastboot to install twrp with the commands :
adb reboot-recovery
fastboot flash recovery twrp.img
fastboot reboot
Then I press to volume down button to display the recovery menu but, instead of displaying the menu, the device boot again and again until I'm tired and I release the button. Then the phone boot normaly on Android...
Any idea how i should progress further?
Thanks for the help.
Hi,
yesterday my Honot 8 worked fine. THen in the night it began with a bootloop, so that battery can't be loaded anymore. Now only possibility to switch it on is put a cable on it. But there is a bootloop, so that Android is starting with boot image and restarts after some seconds.
I can't get into recovery mode (Vol up + Power). Only get into fastboot mode.
Phone Locked
FRP Unlocked
IN Windows 10 i get access to fastboot.exe and the device is recognized. COmmands like "fastboot erase cache" doesn't work -> remote command not allowed.
Any chance to get it run again without factory reset? What can i test now?
Br
Mr.Vain