[Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe? - Eee Pad Transformer Q&A, Help & Troubleshooting

Flashed latest stock firmware 9.2.2.6 ww
Rooted using 1-Click Transformer Root http://forum.xda-developers.com/showthread.php?t=1689193
Flashed cwm from rom manager with no errors or smth.
Then decided to restore to factory defaults the usual way, through settings.
Now I can't boot the usual way (continous asus ring) & can't boot to recovery - green android robot with blue sphere rotating.
Still adb sees the device in recovery mode & I can push files, but can't do anything because can't flash these files
Is there a way to flash recovery without fastboot or flash a rom?

First, ROM Manager does not work with recovery installation on the Asus tablets. There is a warning in one of the forums here about it.
I would use PERI to push a new working recovery via ADB. Then push your ROM to the internal memory and flash it.
http://forum.xda-developers.com/showthread.php?t=1681155

frederuco said:
First, ROM Manager does not work with recovery installation on the Asus tablets. There is a warning in one of the forums here about it.
I would use PERI to push a new working recovery via ADB. Then push your ROM to the internal memory and flash it.
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
Used OneclickrecoveryV0.4.
Now I cannot get access to adb: Volume Down + Power = Booting recovery kernel image
Also usual boot doesn't progress to Asus rotating ring, only Eee Pad logo.
Is there any way out of this "booting recovery kernel image"?

I left it turned off on a charger for several hours & decided to take a look once again before putting it into the box. Suddenly it just turned on & booted normally, wow!! )

Hey folks,
I'm currently facing the same problem.
I tried to root with 1-Click Transformer Root Tool v1.1. I received an error stating that busybox failed to install, also SuperSU wasn't installed. I started the 1-Click Tool again and it said that the Transformer is rooted. So I chose to install the CWM recovery but the script stated that the device was offline. That happened a couple of times, so I decided to install recovery via GooManager, which also failed ("no recovery was found for your device") and finally tried to flash twrp recovery using the terminal emulator - which worked - and rebooted the pad.
Since this reboot, it is not possible to boot the OS normally. It always gets stuck on the EEE pad splash screen, as cordlesspass describes. It's not possible to boot into recovery. I tried to fix this problem with PERI's tool which pushed and flashed the new recovery, but no change.
The only way to boot the OS is a cold boot. This works and the device behaves normally. I also tried to let it charge a couple of hours and then boot again, but no change. It still gets stuck.
I'm using no custom rom, only the latest stock fw.
Do you have any idea how to fix this problem?

AW: [Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe?
So, for all those who have the same problem as I had, I found a solution and its a pretty easy one!
In my case, it seemed to be a permission problem concerning /dev/block/mmcblk0p3. So, I went through different threads and found a suitable solution here:
forum.xda-developers.com/showthread.php?t=1530337&page=20.
All you have to do is to enter terminal emulator on your device (or use adb alternatively) and enter:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
You should see the asus eee pad screen with a blue progression bar and then it should boot normally. Thanks to partio for this hint! :thumbup:
Sent from my Transformer TF101G using xda app-developers app

Related

[Q] [q]Cannot boot into recovery

I have a new Transformer TF101 that I rooted with vipermod.
I tried installing CWM using the recovery installer at http://forum.xda-developers.com/showthread.php?t=1346180, but it kept giving me parsing errors when I tried to run the apk. This happened when I copied over the su from bin to xbin.
So I tried Rom Manager to install the CWM there, but when I try to boot into it, it would get stuck saying Booting recovery kernel image.
If I try to use the Transformer Reboot to Recovery app, it gets stuck at the boot screen and goes into a semi reboot loop where If I try powering it off, it automatically powers on again and I had to do a data wipe to recover.
Does anyone have any idea how I can solve this? I really don't want to be stuck on Android 3.1 forever since it won't update to ICS with the stock update either now.
The android version is 3.1, Build is 8.4.4.11.
Thanks!
I know you already tried this installer, but check out this link.
You could also try using ADB to install the CWM recovery: link.
Read through there and follow the instructions around step 6 since you're already rooted.
If this doesn't work:
Does the ASUS recovery not work at all? As in holding vol-down while powering on then pressing vol-up to enter recovery? If it does you could try an update.zip to flash back to the old stock version that supports old razorclaw and use that to flash recovery reroot and pop a ROM on there (stock rooted ICS or otherwise) I'll give further help if you have to resort to this. ToD
xelloss12 said:
I have a new Transformer TF101 that I rooted with vipermod.
I tried installing CWM using the recovery installer at http://forum.xda-developers.com/showthread.php?t=1346180, but it kept giving me parsing errors when I tried to run the apk. This happened when I copied over the su from bin to xbin.
So I tried Rom Manager to install the CWM there, but when I try to boot into it, it would get stuck saying Booting recovery kernel image.
If I try to use the Transformer Reboot to Recovery app, it gets stuck at the boot screen and goes into a semi reboot loop where If I try powering it off, it automatically powers on again and I had to do a data wipe to recover.
Does anyone have any idea how I can solve this? I really don't want to be stuck on Android 3.1 forever since it won't update to ICS with the stock update either now.
The android version is 3.1, Build is 8.4.4.11.
Thanks!
Click to expand...
Click to collapse
Your firmware is to old for RecoveryInstaller to work. Manually update to latest ICS, root with ViperMod and use RecoveryInstaller for CWM.
Thing O Doom said:
You could also try using ADB to install the CWM recovery:.
Read through there and follow the instructions around step 6 since you're already rooted.
Click to expand...
Click to collapse
This worked! Thank you very much!

[Q] Cannot Enter Recovery!!!

Hi.
Just rooted my TF101 (B80) using ViperMod V4,5.
SU working fine, got root access and everything.
My only problem is that i cannot enter recovery mode. I get the android with the red triangle.
I press Volume- + power, then volume+ and it says:
"booting recovery kernel image"
After that i get the android with the triangle.
Any idea how to solve this problem?
What you see is the recovery, only it's the stock recovery.
To get cwm recovery, use RecoveryInstaller by Gnufabio. Just look in the theme app section
baseballfanz said:
What you see is the recovery, only it's the stock recovery.
To get cwm recovery, use RecoveryInstaller by Gnufabio. Just look in the theme app section
Click to expand...
Click to collapse
I have used the recoveryinstaller.apk and still the same result. Then i tried installing a recovery using rom manager but still the same.
Can i use adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 command?
P.S. I forgot to mention that i am on stock ICS ww.9.2.1.17
read the (epic noob guide) by luna_C666 in the general section.its got all the answers and more!
Sent from my Transformer TF101 using xda premium
original21 said:
I have used the recoveryinstaller.apk and still the same result. Then i tried installing a recovery using rom manager but still the same.
Can i use adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 command?
P.S. I forgot to mention that i am on stock ICS ww.9.2.1.17
Click to expand...
Click to collapse
is your tf rooted?
baseballfanz said:
is your tf rooted?
Click to expand...
Click to collapse
Yes (I think). I used basic root checker and it says that is rooted. It also ask for super user access for it.
Ok. Solved.
I re-downloaded the recovery installer and everything is ok now. Thanks
I had the issue where I had the constant recovery loop and had to manually cold-boot linux every time. Then I followed all the directions that supposedly fixed that and it seemed to work (I could boot straight to android from power off). Now I can't boot into recovery at all. It just hangs at the Asus logo if I choose "reboot into recovery" and it hangs at "booting recovery image" if I use volume down. CWM shows that my recovery image is installed but there is something preventing it from launching.
Is there a way to format the recovery partition and flash it again? I tried the CWM "erase recovery" and that didn't work.
Sent from my Transformer TF101 using XDA Premium HD app
I've got the same issue, can do what I want, but can't boot to recovery ... grrrr
Same issues with boot and recovery
I am experiencing the same issue too, except I can't boot into the OS either so I am not sure what to do... I'll read the epic noob guide as described above and if I don;t come right there i'll post a thread as my challenges are slightly different to what is already posted.
Enigma_2k4 said:
I am experiencing the same issue too, except I can't boot into the OS either so I am not sure what to do... I'll read the epic noob guide as described above and if I don;t come right there i'll post a thread as my challenges are slightly different to what is already posted.
Click to expand...
Click to collapse
You have to hold the volume down at boot like you are booting to recovery, but then don't do anything and a menu to coldboot linux or to erase userdata comes up. Just wait and it will boot android.
Sent from my Transformer TF101 using XDA Premium HD app
original21 said:
Hi.
Just rooted my TF101 (B80) using ViperMod V4,5.
SU working fine, got root access and everything.
My only problem is that i cannot enter recovery mode. I get the android with the red triangle.
I press Volume- + power, then volume+ and it says:
"booting recovery kernel image"
After that i get the android with the triangle.
Any idea how to solve this problem?
Click to expand...
Click to collapse
After being rooted and flashing CWM instead of holding volume down+power.. just download this app from the market. Called: Transformer reboot to Recovery.
The app in your drawer icon is two blue arrows instead of orange and blue like the developers picture.
https://play.google.com/store/apps/...recovery&rdid=com.transformer.recovery&rdot=1
Ive noticed alot of people having issues booting with Clockworkmod into recovery or using power down and selecting recovery. (unless its done by hand). That app is a direct way into recovery. Most ROMs ive seen do not enter recovery even when the option is present.
Here is gnufabio, Recovery Installer - flash CWM with a Click
http://forum.xda-developers.com/showthread.php?t=1346180
after flashing use the Transformer reboot to Recovery app i listed above. Ive used it and it works.. i use the app to enter recovery all the time.

[Q] Can't boot into recovery after rooting

Hi, I'm attempting the root my asus transformer tf101.
I used RootToolkit from here: http://forum.xda-developers.com/showthread.php?t=1688447
To do so, everything went well, I now have root, the trouble is that I cannot reboot into recovery.
I tried adb reboot recovery but all it does is reboot the system.
Volume Up + Power button access APX mode.
I tried flashing recovery using EasyFlasher tool http://forum.xda-developers.com/showthread.php?t=1688012
And Rogue MX Touch revcovery, it claimed to have flashed it succesfully, but still I can't boot into the recovery, it boots
into the system...
No idea what can be done :/ any help would be greatly appreciated.
Thanks!
Never mind, managed to do it using a tool from the market
GoatHunter said:
Hi, I'm attempting the root my asus transformer tf101.
I used RootToolkit from here: http://forum.xda-developers.com/showthread.php?t=1688447
To do so, everything went well, I now have root, the trouble is that I cannot reboot into recovery.
I tried adb reboot recovery but all it does is reboot the system.
Volume Up + Power button access APX mode.
I tried flashing recovery using EasyFlasher tool http://forum.xda-developers.com/showthread.php?t=1688012
And Rogue MX Touch revcovery, it claimed to have flashed it succesfully, but still I can't boot into the recovery, it boots
into the system...
No idea what can be done :/ any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hey, never mind, I've succesfully managed to boot into recovery using
Transformer Recovery reboot tool
https://play.google.com/store/apps/...recovery&rdid=com.transformer.recovery&rdot=1

[Q] Asus bricked, wiped system and data, no fastboot, working adb, cant mount sd card

First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:

[Q] TWRP Reboot Loop but TWRP won't load

So I have a transformer running android 4.1. I tried to boot into the twrp recovery (that is installed and I have used previously) from goo manager. Now, the twrp splash screen shows, flickers, then goes tries to boot into twrp again, but twrp never loads. If I cold boot the tablet I can get into the main operating system. Any help on this? I tried these commands:
Now, enter “su” to get root access. Superuser might ask you for authorization.
Then enter “echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0”
But it didn't work. Thanks in advance
So does anybody have any suggestions? This is really a pain to have to cold boot it everytime it is re-loaded. Thanks.
Tried installing TWRP from GooManager again? Happened to me a couple of times that I had to flash it twice for it to work.
Try flashing via GooManager.
If that does not work, try using EasyFlasher to install TWRP 2.X via APX mode.
primetime34 said:
So I have a transformer running android 4.1. I tried to boot into the twrp recovery (that is installed and I have used previously) from goo manager. Now, the twrp splash screen shows, flickers, then goes tries to boot into twrp again, but twrp never loads. If I cold boot the tablet I can get into the main operating system. Any help on this? I tried these commands:
Now, enter “su” to get root access. Superuser might ask you for authorization.
Then enter “echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0”
But it didn't work. Thanks in advance
Click to expand...
Click to collapse
I had to download TWRP 2.2, copy and paste using my computer and install using the CWM revovery version that was installed when I rooted it. Aferwards, I re-booted, shut down, and booted back into recovery, and voila!! It was there. Hope this helps.
frederuco said:
If that does not work, try using EasyFlasher to install TWRP 2.X via APX mode.
Click to expand...
Click to collapse
This is what finally worked. Thank you so much!

Categories

Resources