Database Users

[Solved] Recovery Issues with my Transformer

I have rooted my device without issue but now I would like to install CWM. I tried it once before but picked the Xoom rom before I knew there was a custom recovery for the transformer. When I try to go into recovery now, it does not work. I have read that adb reboot recovery does not work. I have also tried putting EP101_SDUPDATE.zip on an sdcard to flash but it won't work with the latest android update. Is there a way to flash it either through adb or console? I am familiar with the dangers of typing incorrect commands in linux (I use Arch Linux on my home PC) so any hard command to manually overwrite such files is cool with me.
Thank you for your help in advance.

just use RecoveryInstaller by Gnufabio
Sent from my Transformer TF101 using Tapatalk

That fixed my issue. Thank you very much! Now... if only I had an extra microsd card lying around.... hmmm...

[Q] Booting into recovery shows "no command"

Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks

CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app

n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse

has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app

It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app

New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !

excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)

n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable

CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440

6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7

Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)

I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?

k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.

k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD

No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?

[Q] Question about CWM Recovery

Since none of the Root Toolkits were working for me, I've gone ahead to try to root through the command prompt.
I have a question about CWM Recovery though. I've flashed it on my Nexus 7, but not permanently since adb always hangs. (Which is why the toolkits weren't working for me). Everytime I reboot my Nexus 7, I have to re-flash the recovery.
My question is: Is there another way to make the CWM Recovery permanent? Not through adb? Would I be able to first root my Nexus, and then make the CWM permanent another way?

You're losing cwm every reboot because you happened t to overlook the fact that, to make it permanent, you need to delete the script that reverts you to stock recovery upon reboot. Read one of the routing guides stickied in the dev forum and follow the instructions. Easy as pie.
Sent from my Nexus 7 using Tapatalk HD

well, you dont use ADB to install recovery, you use FASTBOOT
once you are rooted, you could go the easy way and install GooManager and use TWRP instead of CWM...or use ROM Manager to flash cwm
*hint: the reason its not sticking is because of a file you didnt delete in the /system partition.....

najaboy said:
You're losing cwm every reboot because you happened t to overlook the fact that, to make it permanent, you need to delete the script that reverts you to stock recovery upon reboot. Read one of the routing guides stickied in the dev forum and follow the instructions. Easy as pie.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was following this thread here: http://forum.xda-developers.com/showthread.php?t=1741395
In order to make it permanent, I need to run adb which always hangs on me as stated above. Hence why I was looking for an alternate route.
Pirateghost said:
well, you dont use ADB to install recovery, you use FASTBOOT
once you are rooted, you could go the easy way and install GooManager and use TWRP instead of CWM...or use ROM Manager to flash cwm
*hint: the reason its not sticking is because of a file you didnt delete in the /system partition.....
Click to expand...
Click to collapse
I know you use Fastboot to install the recovery, though you use adb to make the recovery permanent.
I think I might try out GooManager and flash TWRP after I am rooted. Thanks!

Daniuhl said:
I was following this thread here: http://forum.xda-developers.com/showthread.php?t=1741395
In order to make it permanent, I need to run adb which always hangs on me as stated above. Hence why I was looking for an alternate route.
I know you use Fastboot to install the recovery, though you use adb to make the recovery permanent.
I think I might try out GooManager and flash TWRP after I am rooted. Thanks!
Click to expand...
Click to collapse
You don't need adb to make it permanent. Use a root file explorer or a terminal emulator
Sent from my Nexus 7 using Tapatalk HD

Help: Lost Root after 4.2.2 Upgrade

I upgraded to 4.2.2 and it seems I have lost my Root Access. I has SuperSU Pro with OTA Survival mode on installed as a system app before the upgrade but it seems it did not keep Root access. I used Root Checker and it's telling me I am not rooted. I am still seeing the unlock Icon at boot so I assume my boot loader is still unlocked.
Is there an easy way to get my Root access back?
Thanks.

Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app

Thanks for your reply. I will try to follow the steps you outlined however, most of what you said is new to me. I initially rooted my device with the Nexus 7 Toolkit so it was a fairly simple procedure. I have never used the SDK or twrp are there any tutorials on how these work on 4.2.2? Also they will probably update Nexus 7 toolkit to support 4.2.2 eventually, so if I can't figure out the steps indicated I may have to wait.
Another noob question: After the update I can still open busybox and SupeSU, how come these apps still run if I am no longer rooted?
gastonwalpole said:
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse

hey man yeh i didnt get how i still had supersu but i definitely wasnt rooted. its all a bit complicated aye, basically you need to download the andriod sdk bundle [now called adt bundle] for whatever you have eg. windows 7 32/64, and the jdk java development kit, look for guides on these, there two youtubers who have helpful channels: driodmodderx and wwjoshdew. also search threads here. you want your device to be recognized by the comp, sdk and jdk do this. twrp is a custom recovery that you can use to flash roms zips etc, you use your comp to send this custom recovery to your device. i would have stayed on 4.2.1 because i dont think you can use custom roms on 4.2.2 bootloader, still 4.2.2 is very smooth, i like it.
Sent from my Nexus 7 using XDA Premium HD app

gastonwalpole said:
Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb.
Click to expand...
Click to collapse
Boy did your post make me happy! I had the exact same problem. Managed to install 4.2.2 with modified OTA update (original was failing due to some discrepency in GoogleCalendar.apk) but even though I had SuperSU in survival mode, I lost my root. I've been trying all afternoon to connect via adb to my Nexus and just couldn't - it was always offline.. I tried 3 different computers and my SGNII phone (which worked) but N7 just wouldn't stop being offline...
I hope this is the solution! Thanx a BUNCH!
One question - my bootloader is unlocked telling by the icon on boot "google" screen - will I lose my apps and data after "re-rooting" that is, after flashing custom recovery and SuperSU?
THANX!!!!!!!!!!!!!

you won't lose anything by flashing recovery or su

I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.

burnitdown said:
you won't lose anything by flashing recovery or su
Click to expand...
Click to collapse
Great, managed to do it, everything fine. Thanx again!

SimonP2 said:
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
Click to expand...
Click to collapse
And if you can't wait, the workaround is there on http://www.wugfresh.com/nrt/ under IMPORTANT NOTICE.

[Q] Do i have this order correct to update?

So i have an A500 i rooted awhile ago.
It runs android 4.1.2
CM10
cwm bootloader 5.5.0 x thor2002ro rev 1.7
i think i installed it from cm10-flex_v6Supercharged_rev2.3_gappsIncl_public....
now i'm thinking about upgrading to android 4.4, as there seems to be one out for A500.
of course it says i need to upgrade my CWM to 6.0.4.5...
this file of course says i need to install Skrilax bootloader.
And skrilax says i need nvflash to install it.
so considering what i currently have installed, is this the correct and easiest way to go about installing a new rom`?
(i keep getting dizzy every time i try upgrading my tablet, because all these guides are soooo confusing, always referring to something that's not explained in the guides.)

well made it as far as getting the skrilex loader installed..
now i'm trying to fastboot in, and it returns
? fastboot
googling it haven't found any idea as to what is wrong

took a leap of faith.. the ? still allowed it to work..

duckforceone said:
took a leap of faith.. the ? still allowed it to work..
Click to expand...
Click to collapse
The ? means you have a connection between your pc and tab.
You are able to issue fastboot commands from yr pc. If you have a recovery.img file you can ' fastboot flash '.
The other way to flash a custom recovery is to use a 'flashable zip'. You could have used this method, by copying the zip to yr sdcard and booting to your cwm RECOVERY and using the flash zip option in the menu.
No matter tho, u sussed it out yrself, sweet
dibb
Sent from my HTC_PN071 using Tapatalk