Hi,
I got some trouble this evening flashing the KITKASS ROM on my TF101
Since then my tablet is loop Rebooting ( only the EEpad logo) over and over again.
I tryed to wipe with the factory reset but it does not help,
My Tablet can be recognized as APX. but i'm not able to access TWRP anymore to try installing a new ROM.
Can someone help me ?
Boot to APX, the use EasyFlasher to flash TWRP again. Then I would update to the latest TWRP and try factory reset and flashing the ROM.
frederuco said:
Boot to APX, the use EasyFlasher to flash TWRP again. Then I would update to the latest TWRP and try factory reset and flashing the ROM.
Click to expand...
Click to collapse
Hi frederuco,
Thanks for replying as quickly !
I did use Easyflasher to flash TWRP in APX mode ... It also says that everything worked fine and that I should reboot in recovery mode.
So after that I rebooted but it still loops over and over again with the EePad logo again =/
Did you see the success messages on the tablet when using EasyFlasher? If not, it didn't work. Check you device manager for the APX device and that you used the naked drivers.
If you did see the success messages, then try flashing stock with EasyFlasher. See if that fixes your boot loop.
If so, then use EasyFlasher to flash TWRP again and then flash KatKiss.
Related
I restored a Nandroid backup within TWRP and now the TF101 is in a TWRP recovery script bootloop.
When I start the I see after the standard ASUS screen the Teamwin screen and after that the text:
"Updating partition details...
Formating cache using make_ext4fs
Done.
Wiping data without wiping /data/media ...
Done."
And than it reboots instantly.
When hold volume down that I see before the Teamwin screen the text:
"Wiping user data and any indicator before cold booting Linux.
Please wait a few minutes ...
Booting recovery kernel image."
With volume up TF101 goes evently off.
When I connect the TF101 to my PC it is recognized, but connection is lost every time it boots.
How can I restore TWRP recovery image?
Possible that your Nandroid backup is corrupted, or maybe a problem with TWRP
Try flashing TWRP again with Easyflasher then try to restore your backup again
If it fails, try flashing a ROM and see if you can get it to boot, if you can, looks like a bad Nandroid backup
I tried both, and both failed. I need to know how to stop the TWRP script from running, because it is keeping wiping something.
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
It is a B70 SBK2.
Joh14vers6 said:
It is a B70 SBK2.
Click to expand...
Click to collapse
I was wrong.
First I was not putting the device really in APX-mode,. Another recent posting made me that clear. Seccond, although it a B70 it seems to be a SBK1.
Only problem now that is not loading the boatloader.bin completely. In succesive tries it random hangs at some point (6%, 27%, 48%, 90%). What can I do to solve this?
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Joh14vers6 said:
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Click to expand...
Click to collapse
Great!
After installing TWRP 2.5.0.0 I've tried to install the latest TWRP 2.6.3.1 for my Asus TF300T in order to try CM11. I tried a number of methods: trough apps like Recovery tools and with my Windows machine using Fastboot. During the flashing process all seems to be fine and after flashing I always get the message that the flashing is successful. In the case of Fastboot the reboot order has no effect on the tablet. When using the Recovery tools App the tablet reboots to TWRP. But in all cases the TWRP version is still 2.5.0.0, so the is nothing that changed. What is going on? Any ideas? What can I try next?
Klussenpunt said:
After installing TWRP 2.5.0.0 I've tried to install the latest TWRP 2.6.3.1 for my Asus TF300T in order to try CM11. I tried a number of methods: trough apps like Recovery tools and with my Windows machine using Fastboot. During the flashing process all seems to be fine and after flashing I always get the message that the flashing is successful. In the case of Fastboot the reboot order has no effect on the tablet. When using the Recovery tools App the tablet reboots to TWRP. But in all cases the TWRP version is still 2.5.0.0, so the is nothing that changed. What is going on? Any ideas? What can I try next?
Click to expand...
Click to collapse
If you cannot issue a fastboot reboot command successfully, it means there's no communication between the tablet and the PC, "flashing is successful" notwithstanding. You have to make sure your PC sees the tab by typing "fastboot devices." If it returns with a serial number, then you're good to go. If not, check your cable and your PC drivers.
Philz CWM Recovery
Klussenpunt said:
After installing TWRP 2.5.0.0 I've tried to install the latest TWRP 2.6.3.1 for my Asus TF300T in order to try CM11. I tried a number of methods: trough apps like Recovery tools and with my Windows machine using Fastboot. During the flashing process all seems to be fine and after flashing I always get the message that the flashing is successful. In the case of Fastboot the reboot order has no effect on the tablet. When using the Recovery tools App the tablet reboots to TWRP. But in all cases the TWRP version is still 2.5.0.0, so the is nothing that changed. What is going on? Any ideas? What can I try next?
Click to expand...
Click to collapse
Check this out Philz recovery is a very nice recovery... Here is link to a flashable zip I made so it can be flashed from your current recovery
http://forum.xda-developers.com/devdb/project/?id=2309#downloads
lj50036 said:
Check this out Philz recovery is a very nice recovery... Here is link to a flashable zip I made so it can be flashed from your current recovery
http://forum.xda-developers.com/devdb/project/?id=2309#downloads
Click to expand...
Click to collapse
Whow. After working for nearly one day of reading the forum and trying things Philz message helped immediately. Flashing form the recovery itself did the trick. Problem solved.
Thanks for that!
Hi I have an Asus MemoPad HD7(ME173X) running stock rom stuck in a boot loop. I tried wiping/factory reset and wipe cache but it didn't fix the problem.
I also have stock recovery so I have no idea how to install a custom recovery without the drivers so I can flash a stock rom.
Tried using flash tool, adb, fastboot method to flash rom/cwm but Windows always fails to install the drivers because of the boot loop.
When I plugin the tablet the computer recognizes it for a bit and it tries to install the driver but it ultimately fails.
I'm losing hope that I can still fix this. Can anyone help me or point me in the right direction? Thank you so much!
anyone know how to install drivers when in a boot loop? If only I can install the drivers I can fix it. Please help..
I've been using the ROM KatKiss - Nougatella for many months and I've always installed every new version without problem. But this time, I was using the TF300T with a common use and I chose the option REBOOT in the power off menu. I had done this before several times. However, on this ocassion, the tablet got stuck in a infinite loop.
Then, I tried to get into the recovery twrp_tf300t_kang_2.8.7.2 that I have always used, but I wasn't able to do it. It started the loop again.
Later, I downloaded the drivers for windows 10 from ASUS website (Splashtop_Streamer_Win_v1704) and the program minimal_adb_fastboot_v1.4.3_setup to use fastboot. Then I pushed the turn-on-button and the vol - and I tried to reinstall the TWRP KANG recovery again through my laptop (Windows 10) with the command: "fastboot flash recovery c:\recovery.img"
The operation was correct and I could get into the TWRP again.
There, I tried to make wipes and install the ROM Nougatella again, but the terminal shows error messages.
In addition, when I turn the tablet off and I try to get into the TWRP recovery again, it begins the loop again.
CONCLUSION: I can reinstall TWRP KANG through fastboot, but there, I cannot make wipes or install things.
Any ideas? Is there any partition corrupt? What commands should I try on the TWRP terminal?
IMAGES ATTACHED.
Can anyone help me to fix it?
Did you ever fix it?
ziggy71 said:
Did you ever fix it?
Click to expand...
Click to collapse
No. I am at the same point.
Have you tried formatting data? What error messages are you getting when you try to wipe or install?
Hello. I have a TF300tg that i recently tried to flash Katkiss nougatella on. It has the correct bootloader and it's unlocked. Unfortunately for me I didn't flash the TWRP Kang recovery, and did it with the TWRP 2.5 that was on it. After that when i boot, it takes me to recovery automatically, and when I try to enter fastboot mode, I see 3 Linux penguins, 2 lines of dialog and then it boots to recovery again. I tried flashing a different rom (Cromi-X) , and still nothing! Please help me :/
4lk15 said:
Hello. I have a TF300tg that i recently tried to flash Katkiss nougatella on. It has the correct bootloader and it's unlocked. Unfortunately for me I didn't flash the TWRP Kang recovery, and did it with the TWRP 2.5 that was on it. After that when i boot, it takes me to recovery automatically, and when I try to enter fastboot mode, I see 3 Linux penguins, 2 lines of dialog and then it boots to recovery again. I tried flashing a different rom (Cromi-X) , and still nothing! Please help me :/
Click to expand...
Click to collapse
Did you try wiping system/cache and flashing another recovery? Or reinstalling recovery with fastboot? My tf300t has been broken for years, so I can't follow along, but that's where I'd start.
Sent from my SAMSUNG-SM-N920A using Tapatalk
cabewse said:
Did you try wiping system/cache and flashing another recovery? Or reinstalling recovery with fastboot? My tf300t has been broken for years, so I can't follow along, but that's where I'd start.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
After flashing a couple of recoveries and roms, it finally opened !!
all ok now
4lk15 said:
After flashing a couple of recoveries and roms, it finally opened !!
all ok now
Click to expand...
Click to collapse
But you always had acces via adb & fastboot?
And installing via sd-card was also possible?
f_lux said:
But you always had acces via adb & fastboot?
And installing via sd-card was also possible?
Click to expand...
Click to collapse
Sd-card install was possible but fastboot was not.
so I flashed a new recovery (Clockwork) and with that a new rom