[Q] ASUS Eee Pad Transformer TF101 keeps booting to CWM - Eee Pad Transformer Q&A, Help & Troubleshooting

Hello,
After installing and running OTA Rootkeeper on my TF101 B80 with a rooted ICS ROM (http://forum.xda-developers.com/showthread.php?t=1514658), the tablet keeps booting to ClockworkMod Recovery (v3.1.0.1). I searched XDA Developers and tried different solutions (including flashing the stock ROM from ASUS) to no avail. Apparently, I'm not the first one having this problem, but I can't for the life of me find a solution. I'd be grateful for any help and pointers. Thanks!

Try this in recovery.
Advanced -- Wipe Dalvik Cache
Wipe -- Wipe Cache
Wipe -- Factory Reset/Clear Data
Install zip from SD card (Pick any rooted ICS rom, make sure to follow installation carefully)
Then after that hit rebootin cwm recovery
See if that works.

Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot

Hi guys,
Thank you for your replies. I tried to wipe data/cache/Dalvik cache several times and flash different ROMs. Still no dice.
Cold booting didn't work either. The system gets stuck at the "Cold-booting Linux" message.
What else should I try? Thanks!

Full wipe is needed prior flashing a full rom.
In your case, check out wolf's thread in general section about flashing and recovery even without root.. it might be useful there..
Sent from my awesome rooted Defy: 2.3.6

baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
thanks , this worked for me!
for the last week I was stuck manually cold booting every time I wanted to turn it on.

markp1989 said:
thanks , this worked for me!
for the last week I was stuck manually cold booting every time I wanted to turn it on.
Click to expand...
Click to collapse
Thanks so much for this info - I was stuck in a loop of rebooting only to Clockmod recovery and could not get out of it! This worked for me.

fsxpilot said:
Thanks so much for this info - I was stuck in a loop of rebooting only to Clockmod recovery and could not get out of it! This worked for me.
Click to expand...
Click to collapse
I had this issue with CWM 5.5.0.4 a while back, (incidentally also with the most current version of CWM) and the script worked, however.. when i flashed anything in recovery it would revert back to the recovery loop. Let me know if you experience that same issue. I'm having trouble installing a lot of the newer ROMS (JB)

baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
THIS!!!
Worked for me as well!!
THANKS

baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
If i'm not mistaken, this will fix the bootloop issue. but i noticed that it wouldn't boot into recovery with power options or reboot apps. The only way i could get into recovery was using power and vol down then press vol +. I fixed this by flashing a new recovery, cold boot, enter echo boot in cmd, then reboot which installed the recovery. after that it worked normally.

kernel null said:
I had this issue with CWM 5.5.0.4 a while back, (incidentally also with the most current version of CWM) and the script worked, however.. when i flashed anything in recovery it would revert back to the recovery loop. Let me know if you experience that same issue. I'm having trouble installing a lot of the newer ROMS (JB)
Click to expand...
Click to collapse
Install a new recovery... I suggest twrp
Sent from my Transformer TF101 using xda app-developers app

Worked like a charm. Had me going crazy for a while. Thanks

baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
the cold boot option worked for me thanks !!!!

Related

Tf101 always boots to CWM recovery

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....

[Q] Recovery Loop

Okay I was able to fix the boot loop issue temporarily.
http://forum.xda-developers.com/showthread.php?t=1531003&page=2
But if I go back into recovery mode then reboot my device, the recovery mode loop happens again...
how do I permanently remove recovery mode bootloop?
I couldn't find a answer to that yet...
Rom : Android Revolution 3.5.1
Recovery: ClockworkMod Recovery 5.8.3.4
P00t said:
Okay I was able to fix the boot loop issue temporarily.
http://forum.xda-developers.com/showthread.php?t=1531003&page=2
But if I go back into recovery mode then reboot my device, the recovery mode loop happens again...
how do I permanently remove recovery mode bootloop?
I couldn't find a answer to that yet...
Rom : Android Revolution 3.5.1
Recovery: ClockworkMod Recovery 5.8.3.4
Click to expand...
Click to collapse
Change your recovery... my advice is flash TWRP recovery.. link and details are in development thread....
Sent from my Transformer TF101 using xda app-developers app
P00t said:
Okay I was able to fix the boot loop issue temporarily.
http://forum.xda-developers.com/showthread.php?t=1531003&page=2
But if I go back into recovery mode then reboot my device, the recovery mode loop happens again...
how do I permanently remove recovery mode bootloop?
I couldn't find a answer to that yet...
Rom : Android Revolution 3.5.1
Recovery: ClockworkMod Recovery 5.8.3.4
Click to expand...
Click to collapse
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
(TWRP is a one I'm using myself)
boot into recovery and flash the new recovery.
When done don't use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Once it boot to your OS, use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
I tried that but it didnt work, im still stuck in recovery loop. Tried to unroot, still stuck in recovery when i turn on my TF. Tried to fix with '1 click root' but still doesnt work?? So lost
Sent from my HTC Incredible S using xda app-developers app
jojo1419 said:
I tried that but it didnt work, im still stuck in recovery loop. Tried to unroot, still stuck in recovery when i turn on my TF. Tried to fix with '1 click root' but still doesnt work?? So lost
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
What didn't work? did it install a new recovery and failed or the new recovery installed but your getting boot loops with that also?, Peri should temp fix the bootloops also : (http://forum.xda-developers.com/showthread.php?t=1681155). Try using EasyFlasher to install a new recovery: (http://forum.xda-developers.com/showthread.php?t=1688012).
baseballfanz said:
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
(TWRP is a one I'm using myself)
boot into recovery and flash the new recovery.
When done don't use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Once it boot to your OS, use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
Click to expand...
Click to collapse
thank you very much for this. Worked fine.
Thanx a great bunch
baseballfanz said:
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
(TWRP is a one I'm using myself)
boot into recovery and flash the new recovery.
When done don't use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Once it boot to your OS, use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
Click to expand...
Click to collapse
Wow.......really man,how many recovery's,rom's etc etc I have tried,you really don't want to know,every time i got stuck back in that damed bootloop.....so you are the MAN dude.....thank you very much,:good: Gratitude!!!

used "Asus Transformer Recovery Boot -MoDaCo", won't boot normally without cold boot

used "Asus Transformer Recovery Boot -MoDaCo", won't boot normally without cold boot
I used this crap app from the play store called "Asus Transformer Recovery Boot - MoDaCo" when I was having trouble rebooting into recovery a few months ago. It's an app that forces the next boot to go straight to recovery. Unfortunately, it breaks it and now every boot goes straight to recovery unless I intercept it and do a cold boot.
I've tried uninstalling the app, i've wiped my rom multiple times (wiping everything). I'm on an older version of CWM. I tried using goo manager to install the latest version of TWP, but it has to reboot to do it, and as soon as it does, it goes straight into CWM.
Is there a flashable zip I can use to restore the bootloader in this situation?
Link to app: https://play.google.com/store/apps/...S5tb2RhY28udHJhbnNmb3JtZXJyZWNvdmVyeWJvb3QiXQ..
First cold boot into android, hold power and volume down, then allow the tablet to cold boot.
Now you should be inside android. Open terminal emulator and type
Su enter then type
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
NOTE=the 0 are zeros
This will fix the immediate issue. This will remove the boot flag causing the tablet to go into recovery. Unfortunately this will not allow you to boot into recovery normally, only by cold boot then press up to enter recovery.
To fix this issue, personally i flashed Team Win recovery 2.2 i think it is in XDA. Awesome touch recovery!
You will have to download the new recovery, boot into recovery by holding power and volume down, then press volume up when prompted.
flash the new recovery. This will remove the boot Flag fix and it'll only boot into recovery so you'll have to use power and volume trick again.
once in android, run terminal emulator again and insert that command above. Reboot the tablet and you will see the progress bar under the eee pad splash screen. This will update your recovery at that time. Let it reboot.
Now the tablet should be fixed and reboot, and reboot into recovery should work as expected.
Understand i'm not responsible if you break your tablet..Proceed with caution.
This is what i did on my b90 tablet.
Hope this helps. It only took me about 13 hours to figure this out.
itj1228 said:
First cold boot into android, hold power and volume down, then allow the tablet to cold boot.
Now you should be inside android. Open terminal emulator and type
Su enter then type
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
NOTE=the 0 are zeros
This will fix the immediate issue. This will remove the boot flag causing the tablet to go into recovery. Unfortunately this will not allow you to boot into recovery normally, only by cold boot then press up to enter recovery.
To fix this issue, personally i flashed Team Win recovery 2.2 i think it is in XDA. Awesome touch recovery!
You will have to download the new recovery, boot into recovery by holding power and volume down, then press volume up when prompted.
flash the new recovery. This will remove the boot Flag fix and it'll only boot into recovery so you'll have to use power and volume trick again.
once in android, run terminal emulator again and insert that command above. Reboot the tablet and you will see the progress bar under the eee pad splash screen. This will update your recovery at that time. Let it reboot.
Now the tablet should be fixed and reboot, and reboot into recovery should work as expected.
Understand i'm not responsible if you break your tablet..Proceed with caution.
This is what i did on my b90 tablet.
Hope this helps. It only took me about 13 hours to figure this out.
Click to expand...
Click to collapse
You're the man, will try this when I'm back home tomorrow.

[Q] Can not update Recovery

Hello guys,
i have a small problem with my CW 3.1 Recovery. If i try to update my recovery over flashing newer version it does not work. It should be work, but when i restart to recovery, it's the same version then before.
any ideas ?
Virus3003
Try installing TWRP through goomanager (install OpenRecoveryScript). You will need it to upgrade to JB 4.2
Sent from my Transformer TF101 using XDA Premium HD app
Thank you for this fast post, but it did not work. I try to install the recoveryscript over goomanager, but after restart to recovery...same recovery like before.
Any other ideas ?
Try this,
Boot into recovery and flash the new recovery.
When done DO NOTt use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Chose Cold Boot Linux
Once it boot to your OS, use terminal (free in Play Store)*.
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
I use this terminal emulator https://play.google.com/store/apps/...251bGwsMSwxLDMsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
virus3003 said:
Thank you for this fast post, but it did not work. I try to install the recoveryscript over goomanager, but after restart to recovery...same recovery like before.
Any other ideas ?
Click to expand...
Click to collapse
Try it twice. The first time didn't work for me either. Rebooting and flashing through goomanager a second time, then rebooting to recovery worked for me.
Sent from my Transformer TF101 using XDA Premium HD app
Thanks baseballfanz, it works. New Recovery is installed and now it boot direct to the OS.

Unusual bootloop

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?

Categories

Resources