Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!
Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.
hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80
baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?
Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?
I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?
Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.
Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?
Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.
Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again
You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Yep. Mine was also barked after I upgraded CWM from ROM-Manager.
mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery
OK, let's start from the beginning. I installed TWRP recovery, EOS 4 and KAT Kernel successfully today and I was quite happy with the results but decided to try Revolution HD. Since I am more used to ROM Manager, I decided to change TWRP to CWM and use it for recovery. After that things got messy. First of all CWM said that it can't find sd card and secondly my TF wouldn't boot up anymore after exiting recovery. I've been messing with it for hours and can't find a solution. It only got worse and for awhile the only way I could access it through ADB was to do a cold boot and it would get stuck at the spinning EOS logo, but atleast it would allow ADB access.
Last thing I tried is this and the tablet reboots, but it's still stuck on spinng EOS logo, but I don't have to do a cold boot to get stuck there anymore
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:
http://forum.xda-developers.com/show...530337&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
Click to expand...
Click to collapse
If I select recovery after reboot, it will get stuck at Booting recovery kernel image. So any ideas what to do next ?
Edit: That's what is visible on my tab from QtADB
OK I've tried everything I could find but nothing
Computer recognizes it fine when it's cold booting and as you can see, ADB works on it but can't get fastboot to work. I guess the solution would be to get a working recovery on it again, but I can't figure out how without fastboot.
http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.
Thing O Doom said:
http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.
Click to expand...
Click to collapse
OK, tried it but I couldn't complete it.
The first part works ok and after reboot I see the blue line filling up and after that the usual EeePad screen and it boots to EOS loading screen and I can get ADB access again.
But after I have to write "adb push recoveryblob /sdcard/" CMD says
Daemon not running starting it nor on port 5038
Daemon started successfully
And after that it just doesn't do a thing and then it reboots and I can't enter the final code. And under directory tree the sdcard is not a folder but it's just a file or smthing like that "sdcard -> /storage/emulated/legacy" is written.
EDIT:
Man, I would kiss you if I could ! Worked, finally it worked !
So the problem was, that it couldn't find sdcard and so it rebooted. Changed the sdcard to another directory, /dev in my case and after that it completed it and booted perfectly into recovery. AWESOME !
I have a Fairphone (original) and I passed the wrong file to adb sideload (yep, feeling dumb right now).
The phone now will not boot. It goes into a boot loop, even if I take the battery out, and then boot while holding power and volume up to get to recovery, it still goes into a loop.
I even tried this script to see if there was a brief window I could get into adb to repair during bootloop, but adb never finishes waiting for the device even after about 5 consecutive reboots.
If I plug the phone in to charge, the empty battery appears, but then after a few seconds it goes into a boot loop too.
Code:
#!/bin/sh
echo "Waiting for device."
./adb wait-for-device
echo "Freeze!"
./adb shell stop
I can get into factory/test mode by holding Volume Down and Power. This seems to be the only state I can get the phone into that doesn't involve a boot loop.
Factory mode looks (mostly) like this picture (my screen shows english translation as well as mandarin):
vi8.info/pic/2014-01/Factory-Mode-Menu.jpg
While in factory mode:
adb can connect
adb shell gives me a shell, but su in the shell gives me permission denied, so no root access it seems
adb sideload says error, disconnected.
fastboot cannot see the device
adb reboot bootloader takes me back into a bootloop
adb reboot recovery takes me back into a bootloop
Is there anything I can do from here to flash a working ROM onto my phone?
I'm on a Mac. I can get access to a Windows machine in a week or so and will try SP FLash when I do, but until then, is there anything that can be done with Mac only?
Hi druids of android,
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I've updated CM via OTA to the latest available snapshot and after that I've done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can't do any fastboot command to flash recovery or system.
Any fastboot call ends with 'waiting for device'. I call it through sudo and I've configured udev according to wiki.cyanogenmod.org/w/UDEV
I've tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I've found /cache/recovery/recovery.log file. (can't attach whole file because I'm a fresh member)
Partitions were mounted and the loop begins after:
Code:
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
I:Boot command: boot-recovery
I'm fighting with it a few evenings and I decided to ask You for help.
I have the exact same problem. Happened last night after the Wipe Data option.
I have since read that that is a horrible thing to do.
I did try this - http://forum.xda-developers.com/showthread.php?p=63269550&nocache=1#post63269550
But I am unable to get to the fastboot screen still after dd-ing. The data partition dd took hours and hours. Left it overnight.
Help would be appreciated.
SOLVED!
Got TWRP working again!!
Follow this post right under the post of which link is above!
http://forum.xda-developers.com/showpost.php?p=64591975&postcount=88
I was unable to get the adb shell commands working separately after going into #.
So I just put in
Code:
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1"
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1"
This should fix it!
Hello guys.Finally i found solve for my TF300T loop on TEAMWIN logo.I read many threads in XDA forum for this problem but nothing happens .I had no fastboot with adb ,no recovery menu with adb and combinaiton keys until get this command "adb shell recovery --wipe_data" found.First you must install naked drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2139767.Then plug usb tablet to pc(windows) and open cmd and enter the command "adb shell recovery --wipe_data"and press enter.
Sorry for my english
Gonna try this tonight. Did the same thing to my tablet yesterday. I am running the latest TWRP(Kang) and Katkiss MM 6.0.1 ver 24 Did a wipe of the cache and dalvik as I was having some issues. It then started random rebooting into Android. So I went into bootloader screen and tried to start recovery and accidently hit wipe data and got the boot loop. Now it just boots and reboots about 3 times and shuts down. I will try the naked drivers and your commands.
To point out ,that before i found solution fo my tablet,i had no fastbout wih comb-keys .My loop was only on the TWRP LOGO and never restarting or closing alone,until to press power button for 20s about to restart tablet or press reset button + power button for 20s to shut down tablet.I hope find solution and sorry fot my english again.
Thanks to tobdaryl member
Hi, I tried to install the OTA lollipop update with USB debug mode, the process did not go thru and the phone rebooted into recovery (teamwin). I did restore my backup with recovery successfully, but every time I rebooted from recovery, it went directly to the recovery again. I could power off my phone from recover, but when I power it on, it goes directly to recovery. I tried power phone off, hold volume up key, plug in USB cable, it does not enter download mode, instead it goes into recovery mode again.
It seems that I do have ADB access, but the devices shows in "recovery" mode and I can't switch to "adb shell"
C:\Users\adb_fastboot>adb devices
List of devices attached
09cb97618d0ae1c6 recovery
Please help!
I searched some old post and did the following to unbrick my phone.
In TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
I had "no space left" type of errors reported after both commands. However after reboot, my phone boots up to normal system! Yeah!
By the way, can someone share a lollipop recovery backup file, so we can just load from recovery? I don't have the courage to go thru that USB debug session once more. Thanks!