Dear people,
I recently installed Clockworkmod v5.8.3.4 etc. on my TF101. It was working with RaymanFX's ROM: http://forum.xda-developers.com/showthread.php?t=1858295
Like so many others I got the bootloop-problem. My TFT101 didn't want to boot directly into the rom. It didn't really bother me, because I could coldboot and that worked fine.
Recently I wanted to repair this minor issue. After a bit of an internetsearch, I found a solution: http://www.transformerforums.com/fo...tf101-stuck-clockworkmod-recovery-mode-2.html
At least I thought it was the solution.
I did the following:
1. Reboot tablet pressing Power+Vol Down.
When screen becomes blank, release Power but keep pressing Vol Down.
It will propose you to boot into recovery by pressing Vol Up - ignore it.
Then it will propose you to wipe data by pressing Vol Up or skip wiping using Vol Down. Press Vol Down.
This will cold-boot tablet normally without wiping any data.
2. Start Terminal Emulator application wich is a part of CWM. Execute the following commands:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
After reboot, the whole thing doesn't work anymore. The bootloop stayed, but Android itself doesn't start at all... Not even when coldbooting. I can get into ClockworkMod Recovery, but installing the old ROM doesn't fix the problem.
Is there a way to undo step 2 (with the commands) I've mentioned above?
I am pretty sure the 5.8.3.4 recovery is your issue. How did you install it? I am guessing ROM Manager.
Have a look here: http://forum.xda-developers.com/showthread.php?t=1671598
I would use EasyFlasher and install either TWRP or Rogue Touch Recovery. I strongly suggest TWRP, it is much nicer than CWM.
http://forum.xda-developers.com/showthread.php?t=1688012
frederuco said:
I am pretty sure the 5.8.3.4 recovery is your issue. How did you install it? I am guessing ROM Manager.
Have a look here: http://forum.xda-developers.com/showthread.php?t=1671598
I would use EasyFlasher and install either TWRP or Rogue Touch Recovery. I strongly suggest TWRP, it is much nicer than CWM.
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
I installed ClockworkMod via an tutorial I found on the internet. Don't know which one. Later I installed the ROM Manager and updated to the latest version (the one I mentioned above).
ClockworkMod could be te problem. Straingely enough, the EOS-ROM works. I had the bright idea to try to install that one and EOS just works. Then I though I would try again to install RaymanFX's MOD. Didn't work. Apperently ClockworkMOD just sucks in installing ROM's properly...
I'm now convinced that ClockworkMod just isn't the right program for the job on the tf101. Installed EasyFlasher and TWRP and my tablet is back in business, without any bootproblems!
Thank you very much for your help!
Fixed My EOS 4 Boot Loop
"echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0"
Fixed my boot loop even though I was already using TWRP and had never installed EOS 4 with CW. Could CW have left stuff behind?
Related
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.
I recently flashed revolver 4.1.1 and a new kernel but for some reason my tablet always boots to the CWM recovery unless i do the power+vol down then itll go to the wipe or cold boot screenand boot into the OS. This started when the revolver arts downloaded the 4.1.1 patch and booted to recovery and i couldnt find the 4.1.1 patch and rebooted, downloaded it with my browser and installed it.
Any way i can set it back to boot directly to the OS?
Sent from my Transformer TF101 using Tapatalk 2
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
deerhurst said:
I recently flashed revolver 4.1.1 and a new kernel but for some reason my tablet always boots to the CWM recovery unless i do the power+vol down then itll go to the wipe or cold boot screenand boot into the OS. This started when the revolver arts downloaded the 4.1.1 patch and booted to recovery and i couldnt find the 4.1.1 patch and rebooted, downloaded it with my browser and installed it.
Any way i can set it back to boot directly to the OS?
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
What recovery version are you using?
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
batjuh said:
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
Click to expand...
Click to collapse
Revolver used to have the option to reboot to recovery which I used multiple times and never had any issue. I'm currently using Gummy which reboots you to recovery whether you choose normal reboot or reboot to recovery and still no issues otherwise. I just choose reboot in the recovery and it reboots fine from there.
sidneyk said:
What recovery version are you using?
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
Revolver used to have the option to reboot to recovery which I used multiple times and never had any issue. I'm currently using Gummy which reboots you to recovery whether you choose normal reboot or reboot to recovery and still no issues otherwise. I just choose reboot in the recovery and it reboots fine from there.
Click to expand...
Click to collapse
Im on cwm 5.8.3.4. I used the reboot to recovery in revolver parts. Its just annoying but doesnt prevent using the device.
Sent from my Transformer TF101 using Tapatalk 2
deerhurst said:
Im on cwm 5.8.3.4. I used the reboot to recovery in revolver parts. Its just annoying but doesnt prevent using the device.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
That looks like a version that came from ROM Manager and may be your trouble. What happens when you choose normal reboot from the Revolver power menu?
Like hold power button and choose from the menu? Same thing. Next cold boot goes to recovery.
Yup, rom manager updated.
Haven't tried rebooting from revolver parts yet, didn't even think of it.
deerhurst said:
Like hold power button and choose from the menu? Same thing. Next cold boot goes to recovery.
Yup, rom manager updated.
Haven't tried rebooting from revolver parts yet, didn't even think of it.
Click to expand...
Click to collapse
You might try Team Rogue XM Touch Recovery. It will read both internal and external cards and works well. You may need to apply the fix mentioned in Roach's recovery thread first if it still boots to recovery after.
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
batjuh said:
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
Click to expand...
Click to collapse
Finally got a chance to mess with this issue. It wont flash over the current recovery with 3.2.0.1 or .3.1.0.1 or the 5.8.1.8 touch. Getting into recovery by rebooting and letting the messed up recovery thing boot into its self and then selecting the zip to flash.
Sent from my Transformer TF101 using Tapatalk 2
SOLVED
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
[...]
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I only needed this to stop booting directly into recovery. Thanks!
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I have been trying to fix this annoying recovery loop for the last 3 days and this fixed it. Kudos to you good sir :good:
Thanks man!
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
Thanks so much man! Your method really works. It saved me from losing faith entirely in the android community! :good:
karenlightning said:
Thanks so much man! Your method really works. It saved me from losing faith entirely in the android community! :good:
Click to expand...
Click to collapse
it's nice to see you all happy :laugh::laugh::laugh::laugh:
I have the same error but in cwm recovery i have "E:can't mount /sdcard/" issue and then i can't flash new recovery..
thanks
So here's my issue... I'm stuck in CWM 5.8.3.4, can't boot into android, stuck in recovery... wanted to flash different recovery, but unless I'm blind I can't get 5.8.3.4 to see the SD Card (external) to flash a file... any ideas on what my options are...
Can't get to Android either, CM10 splash screen keeps spinning..
Update:Resolved my issue by using EasyFlasher
badbullet said:
seems that you have recovery loop problem so try this: Download clockworkmod recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
in recovery, select flash zip from sdcard and select the recovery zip you downloaded
once it has flashed the zip file, don't reboot but hold power button to shot down
power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Click to expand...
Click to collapse
thank you so much buddy!
Phone is not powering up, i think it is dead.
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I did same but when i tried to power up the at the end, it wont power up neither charge....
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!
I've been running the Revolver ROM on my TF101 for quite a while now, and although I've been happy enough with it, I wanted to try out some others, but I have run into several problems.
1. I currently have ClockworkMod Recovery 5.5.0.4 installed. Whenever I reboot, it goes into CWM Recovery. To boot properly I need to hold the down-volume rocker when I power on, then select the cold boot option. How do I fix this?
2. ROM Manager told me I could upgrade the recovery image to 6.0.1.3, so I did, hoping it would fix the above problem. Now ROM Manager tells me I have 6.0.1.3, but when I boot into recovery, it greets me with a "5.5.0.4" banner - it doesn't seem to have changed, and I still can't boot properly without cold-booting. Why does ROM Manager think I've a newer version of Recovery than I appear to have? How do I update it? I tried installing GooManager, and it installed some OpenRecovery image, but I still get CWM 5.5.0.4 when I boot.
3. I tried installing (via ROM Manager) CyanogendMod 9, but when first booting it displays an animated logo, and gets stuck there (and by stuck, I mean I left it a good 10hrs overnight). I had to restore the backup of the old Revolver ROM to be able to boot again. Same thing happened when I tried the CyanogenMod 10 nightly. What do I need to do to get CyanogenMod installed?
First, there is this: [NOTICE] Don't use ROM Manager! **New to the Transformer? READ**
Honestly, just install GooManager. One installed, open, grant root, then tap the menu button in the top right corner. Install OpenRecovery Script. This will install Team Win Recovery Project.
It is far superior to CWM IMO. Then all your issues will go away.
frederuco said:
First, there is this: [NOTICE] Don't use ROM Manager! **New to the Transformer? READ**
Honestly, just install GooManager. One installed, open, grant root, then tap the menu button in the top right corner. Install OpenRecovery Script. This will install Team Win Recovery Project.
It is far superior to CWM IMO. Then all your issues will go away.
Click to expand...
Click to collapse
I appreciate the input, but:
1. As I mentioned in the OP, I have already tried GooManager - it claims to install OpenRecovery, but it has no effect when I restart - I still get dumped into CWM recovery.
2. If I follow the link about "Don't use ROM Manager", it mentions RecoveryInstaller, but the link to that utility is broken, and I've been unable to locate a credible copy of it elsewhere.
UPDATE: I found a working link for RecoveryInstaller, installed and ran that, clicked the button to install recovery, then my tablet rebooted, straight into CWM Recovery 5.5.0.4 again.
No matter what I do I can't seem to get rid of CWMR5.5.0.4 ...
Oops, i missed the GooManager part. my bad.
Try EasyFlasher. Boot to APX mode and install Rogue Recovery (CWM based) or TWRP.
http://forum.xda-developers.com/showthread.php?t=1688012
frederuco said:
Oops, i missed the GooManager part. my bad.
Try EasyFlasher. Boot to APX mode and install Rogue Recovery (CWM based) or TWRP.
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Thanks - that looks promising. It doesn't help that it's been 18 months since I last played around with flashing ROMs etc, so I've forgotten half the stuff I need to know!
Your EasyFlasher link says "Requrements: APX drivers" with a link to some recommended drivers, and I've installed those OK (eventually! - took me a while to figure out how, because I couldn't find sensible instructions, but I worked it out in the end).
So now I've managed to boot into TWRP (yay!) and have made a backup of everything.
And now it seems to boot normally. Fantastic! Now to see if I can install some other ROMS.
Thanks for the help!
Cool, glad it's working.
I am loving the TeamEOS4 4.2.1 ROM.
The ParanoidAndroid/CM10 hybrid by Mattmanwrx is my favorite 4.1 ROM. Many also like the LiquidSmooth 4.1 but I never tried that one.
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