Hi,
I rooted using:
OneclickrecoveryV0.4.2
Didn't backup my original stock OS, and couldn't book into an OS.
It was stuck in a loop, used OneclickrecoveryV0.4.2 to fix the loop.
Then it still did not boot into an OS. I put cm-10-20130929-NIGHTLY-tf101.
Worked fine. Wanted to try Katkiss 6.0. Did not seem to work with TWRP 2.5.
Download signed_twrp-2.8.1.1_tf101.zip. Installed it after booting into TWRP 2.5.
It looked successful and rebooted into OS fine. However, after I rebooted it, it is stuck now.
I can't boot into TWRP. It gets stuck at "booting recovery kernel image".
Help...please! I am not tech savvy at all... it took me hours researching to even get to this point...
Did I brick it?
My girlfriend will be throwing pots and pans at me if I can't fix this
Thanks in advance...
i have exactly the same problem, i used easyflasher to flash twrp and tablet says ok, but dont enter in twrp. only says "booting recovery kernel image".
anybody? U_U,
Same issue here, any help?
please help us sombody!
Anybody have a solution? My tablet is still dead in the water.
you guys didn't look hard enough, the solution was on the thread for the twrp that you were trying to use. (2.8.1.1 unofficial thread) read the post
Originally Posted by sidneyk
OK, try this. If you are still in boot loop or regular reboot takes you back to boot looping then hold volume down and power button until white text appears and then release buttons and allow OS to cold boot. That should get you back to Android. If so, then either from a terminal or through adb shell with USB connected to pc, type:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot normally. That should get you out of boot looping. Then download this blob:
And move it to the root of /sdcard. Then, either from a terminal or adb shell type:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally. You should see the blue-green flashing bar and then Android should boot. Then reboot to recovery to see if it took. I've had to do the same thing with experimental builds that didn't work out and it works like a charm.
http://forum.xda-developers.com/showthread.php?t=2434422&page=70
this solution has been there since may I just ran into this problem today and had it fixed in a few hours after finding that post, i knew it was an issue with the unofficial twrp but i was just trying to find a way to manually flash an older recovery since flashify didn't work and twrp manager didn't work, i ran into this solution by searching for the partition name of the recovery partition which is mmcblk0p4 and tf101.
Thank you for the information but that has not solved my issues. When I attempt to get to recovery the screen goes black and I can't see the menu...when I boot I get android error and the screen will go black so I can barley see the menu...I can't get the computer drivers to recognize in apx mode..basically stuck.
Related
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
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!
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?
Is my device soft bricked?
I flashed PhilZ-cwm6-XXLTA-ATL-5.15.0.tar which worked, then I started up the phone and tried to flash CWM 6.0.4.3 touch using ROMManager, the process was a "success" but after the reboot attempt the phone was unable to boot OS nor is it able to go to Recovery mod. I am still able to enter download mod.
I tried flashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar again, but it didn't work. I can detect my phone in ADB devices and in Odin3. I am currently searching for a stock ROM for my device.
If anyone has experienced this before and knows the result already, could you tell me whether my device is lost or I can revive it somehow? Thanks in advance.
EDIT: My phone doesn't seem to go into recovery, stuck at manufacturer Logo(Not restarting); but in ADB devices I can see it in recovery mod and can see its contents in adb devices.
Solved: It booted normally after deleting update.img and cache via ADB.
Thread completed as user already founded the solution.
Thread closed
hey,
so I guess I made a major mistake. I wanted to flash twrp recovery with this ramdisk.img , it all worked fine, I could flash it and then I entered the recovery mode via adb with the command adb reboot recovery. The recovery mode twrp logo popped up and all I can see is the name teamwin and the project version, which says 3.2.1-0 btw and the names of the developers nothing more, the screen is frozen and I can't do anything else.
I tried to reboot into fastboot and bootloader with adb but all I does is, that the screen turns off then on and then it says "your device is booting now…" and it leads me back to the teamwin logo and freez again.
I can't do a normal reboot and I can't flash another .img recovery..
I hope someone can help me please..
There must be a way to get out of this.
MrSYS said:
hey,
so I guess I made a major mistake. I wanted to flash twrp recovery with this ramdisk.img , it all worked fine, I could flash it and then I entered the recovery mode via adb with the command adb reboot recovery. The recovery mode twrp logo popped up and all I can see is the name teamwin and the project version, which says 3.2.1-0 btw and the names of the developers nothing more, the screen is frozen and I can't do anything else.
I tried to reboot into fastboot and bootloader with adb but all I does is, that the screen turns off then on and then it says "your device is booting now…" and it leads me back to the teamwin logo and freez again.
I can't do a normal reboot and I can't flash another .img recovery..
I hope someone can help me please..
There must be a way to get out of this.
Click to expand...
Click to collapse
Were you on android 9 or 8, prior to flashing twrp?
Android 9.1, however I did this but I could get back to eRecovery after I pressed the volume up key and on/off key several times. I normally rebooted my phone and now I can use it again ?
But its still frustrating that it didn't work