Hi all !
Two weeks ago I somehow lost my recovery...
I had CWM 6.0.2.1 and decided to flash compatible TWRP zip 2.6.3.0 and switch recovery. I think i forgot to wipe something. It did flash it, but not successfully. When I tried to enter the recovery it stucked in "searching RCK" and didn't enter the costume recovery. I rebooted it and it get stucked on the ASUS screen. So now I have 2 options:
(The tablet is off)
1. Turning on- holding POWER- stucked on ASUS boot screen.
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing- I have two options:
2b.a. cold boot - boots normally to the ROM (CM10)
2b.a. wipe data - haven't tried it, but i belive it will wipe my data XD
I've tried PERI and 1ClickTransformerRoot - no results...
In my opinion, the main problem is that the tablet can't reboot normally...
I need your help, I'll apritiate it a lot !
Sent from my SL101 using xda app-developers app
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
frederuco said:
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
sidneyk said:
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
Click to expand...
Click to collapse
Thanks a lot ! It now boots normally !
frederuco said:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I've tried it before and now - didn't worked for me...
Can I try a similar method with CWM ? :fingers-crossed:
Btw. you two are great !
You can do the same with a CWM blob file.
Also, if you have a TF101 (non 3G) you can boot to APX and install using NVFlash (EasyFlasher).
See here for details on how to use EasyFlasher: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Yeah, we know!
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Should understatements really be allowed? :laugh:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
FIXED
Goggle81 said:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
Click to expand...
Click to collapse
I did what frederuco suggested, just with CWM:
http://forum.xda-developers.com/showthread.php?t=1855686&highlight=cwm
frederuco said:
Download the CWM you want to use.
Unzip so you have the CWM.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/CWM.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
And my slider booted normally :victory:
Good luck mate ! I hope it will work for you :fingers-crossed:
Didn't work for me. Will check it again.
Thanks mate!
Edit: sadly I didn't find the time to do it until know.
Thanks at all! Got recovery back. Now I will flash 4.4.2
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Mirabeau78 said:
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Click to expand...
Click to collapse
Have you tried cold boot?
Read through the OP in order to cold boot into ROM:
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
Click to expand...
Click to collapse
If it worked, download Android Terminal Emulator and type in:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots.
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ su
# dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
# reboot
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery and install KatKiss :highfive:
Big TNX to @frederuco and @sidneyk , if it woks thank them before you thank me, it is their instructions above
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
in my case
2a. it does enter recovery cwm, but cant format and it doesnt see the sd card - cant mount it.
2b. press nothing
2b.a cold boot - doesnt boot normally. it stays on the asus logo page and the bubbles rotates
therefore i dont know where could i install that terminal
is my situation helpless? (
Mirabeau78 said:
is my situation helpless? (
Click to expand...
Click to collapse
While in recovery, are you able to connect to a PC and get adb access from a CMD prompt if in Windows or a terminal if in linux?
Sent from my SM-N900T using XDA Premium HD app
i have windows and i tried using 1click and it cant find the device. old adb base or something even if is completly updated
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Jeretista said:
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Click to expand...
Click to collapse
Rommanager = not good for Asus tf101. Also, you don't need any app for installing twrp. If you have a working, up to date recovery, you should be able to flash the twrp zip directly from recovery. I recommend my builds of twrp, of course.
Sent from my Transformer TF101 using XDA Premium HD app
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Jeretista said:
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Click to expand...
Click to collapse
Congratulations. Way to stick with it!
Related
Hi everyone,
few days ago I flashed Megatron 1.0.1, and I found this ROM very good. But now I have a problem. I'm stuck in the recovery (solarnz-R3-230511-1902).
If I click on "reboot", it reboots on recovery,
if I push the power button for 5 seconds, it reboots to recovery,
if I click on "power off" and then press the power on button, it boots to recovery!
and if I click on "reboot to recovery" it reboots to recovery(this time it's logical ).
The only thing that works (apart the recovery) is the APX mode.
Searching in the forums I found this post : . Sorry to be such a noob, but how can I get it to work? My ADB won't recognise my tab while it is in recovery...
Any solutions for this? Thanks in advance.
Sadmann! ()
Install this recovery
Connect your tab to your pc, and adb push the recovery file
You maybe have to do this for it to work:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
I tried it, but it still rebooted on the recovery. But i found a solution! =D I clicked on power+vol_down button and then waited 5 seconds.! It booted megatron! =D Thanks for your help anyways!
DerSandmann said:
I tried it, but it still rebooted on the recovery. But i found a solution! =D I clicked on power+vol_down button and then waited 5 seconds.! It booted megatron! =D Thanks for your help anyways!
Click to expand...
Click to collapse
But install the recovery I told you, or you may have that issue again. Also it's always good to be up-to-date.
So if anyone has this problem and finds this thread, here's what he has to do.
On your computer you'll need these drivers, and adb download the exe and install. Extract the drivers anywhere, just remember where!
1: While you're in the recovery : Power off.
2: Then start the tab by pressing power+vol_down button. You will be asked if you want to enter rck, but don't press vol_up, just wait.
3: Another screen appears, where you can choose between wipe the data or cold-boot linux. Choose cold-boot linux.
4: Now your tab started normally.
5: In the settings, enable ADB.
6: Connect your Tab to the computer. Normally it won't recognise it. Then go to the device manager, and find the device with a little /!\. Right click on it, there's an option to update the driver. Choose the folder where you extracted the drivers.
7: Then open a windows shell and write :
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools"
.
8: Then write this :
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
.
9: Be happy, now everything is working normally on your tab, just don't do the same error(unless my tutorial is so good you want to do it again)!
So i had the same issue because i allowed rom manager to update my CWM for some reason...
Do they know about this issue and will it be fixed soon?
patriotaus said:
So i had the same issue because i allowed rom manager to update my CWM for some reason...
Do they know about this issue and will it be fixed soon?
Click to expand...
Click to collapse
Koush twitted today that the problem is fixed with his CWM in ROM Manager.
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 am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks
Grem135 said:
I am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks
Click to expand...
Click to collapse
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.
cmendonc2 said:
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.
Click to expand...
Click to collapse
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?
Grem135 said:
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?
Click to expand...
Click to collapse
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.
cmendonc2 said:
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.
Click to expand...
Click to collapse
Thanks for the help. I finally can boot into recovery. It took a bit to realize sdcard meant internal memory not the microsd like on my phone.
Thanks button hit. :good:
Some of you may be wondering by the title of my thread, "Why in the world would you want to do that? Just install TWRP completely!"
The simple answer to that; I simply can't. I am unable to overwrite my recovery using goo manager/recovery flashes/terminal emulator, etc. And now you must be thinking. "Well just reset your tablet using NVFlash or the ADB Toolkit!" But alas, I just cannot for the one reason that has killed me for the past two years:
No computer will detect my Transformer.
That's right, plugging up my tablet to a computer via USB cable does nothing at all. And no, it is not my USB cable, because I have tried multiple. All I have ever wanted to do was upgrade from Android 4.1, but I cannot, because my current CWM image doesn't fully support it. So this brings us to my first question: Is it possible to run another recovery on top of my current one, just so I can flash a kitkat ROM? Is this even possible? Will it prove ineffective because it's running on top of the incompatible CWM anyway? Any and all answers will be appreaciated. I really wish I could simply use an easy Flash tool, but I just happen to be hated by all devices. Any fix to my recovery issue or my NVFlash/USB cable issue will be GREATLY appreciated! Thank you for your time
What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?
doppelhelix said:
What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?
Click to expand...
Click to collapse
I'm running clockworkmod touch (version 5.something) I don't get any progress bar after flashing a new recovery.zip
if I flash a new recovery.zip, it goes through successfully, but it never actually flashes. I can reboot into android via the "cold-boot" method (booting normally takes me to recovery). I don't know about the su command. I'll get back to you on that.
Edit: u0 [email protected]:/ # is what I get, so no root user. Just u0 with the root pound sign after. That's the only change
creed10 said:
That's the only change
Click to expand...
Click to collapse
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.
doppelhelix said:
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.
Click to expand...
Click to collapse
I followed everything step by step, and it all went just how you described! After nearly two years of having a screwed up tablet, you sir, have helped me resurrect it! I see a donation coming around!
Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru
doppelhelix said:
Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru
Click to expand...
Click to collapse
Sounds great! I will be forever in your debt, kind sir