Database Info

[Q] Help! "no boot or recovery img"

I've been trying to flash a new rom, and I can't. Fastboot pops up every time I try to boot recovery saying "No boot or recovery image"
My phone still boots it's rom normally and can connect to the computer via usb just fine, but I've tried flashing several different CWM recoveries and none of them work, it all just gives this same error. I can't re-flash now, and this rom is not working well. What do I do?

iamtheculprit said:
I've been trying to flash a new rom, and I can't. Fastboot pops up every time I try to boot recovery saying "No boot or recovery image"
My phone still boots it's rom normally and can connect to the computer via usb just fine, but I've tried flashing several different CWM recoveries and none of them work, it all just gives this same error. I can't re-flash now, and this rom is not working well. What do I do?
Click to expand...
Click to collapse
are you spelling the name of the recovery correctly? is the recovery file(.img) in the same folder in your computer as fastboot is?

Search "flash image GUI" I think, here on xda, on the thread download the apk, then install on your phone, then go to rom manager the WEBSITE, find a recovery image that corresponds with your phone then download it. Now go to flash image gui and flash the CWR image you just got like 2 or 3 times just so it sticks now see if it works.

Nevermind, as simms said (didn't read properly). You can use the tab key to autofinish the name of the recovery.

Hi guys, I found the problem, but thank you all for your suggestions. the problem was my fastboot was still locked! (I'm not sure how I got this far without unlocking it, but now it's moot) Anyways, it works now, and all is well. Thanks!

[Q] Asus bricked, wiped system and data, no fastboot, working adb, cant mount sd card

First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.

Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:

[Q] Recovery mode hangs

When booting into recovery mode, the system hangs.
(It can boot normal without a problem)
The device had JB without root, so did the following:
1. Installed the ASUS bootloader unlock utility
2. Installed TWRP 2.3.1.0
3. Installed CleanROM 2.4
Now, when booting into recovery mode:
Via the shut-down menu, the system reboots into the white ASUS logo screen and hangs
Via power+volume Up, and selecting the [RCK] icon, the system hangs (the top left of the screen says "Booting Recovery kernel image")
I'm guessing the system is looking for a ROM file and simply can't find it.
Do you guys ROM experts know what I did wrong and what the fix might be?

After reinstalling TWRP - Recovery mode is working again!
I'll leave this post up in case it happens to anyone else.

I need help with this tablet - few questions

Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?

stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS

Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.

Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)

Need help flashing Katkiss 6.0.1 , Recovery Partition Not Found / Nothings Working

So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.

Did you already solve that problem? I also need a solution.Thanks