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.)
Related
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!
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!
Is my stock recovery broken? Can't update through about device even with stock non CWM recovery.img. Even with factory restore files from the link below I was unable to get native recovery to work. I get a broken android.
I've been manually updating from the link below and I even tried the stock "recovery.img " on that official site doesnt seem to do the trick.
https://developer.nvidia.com/develop4shield
Below thread doesn't resolve issue.
http://forum.xda-developers.com/nvidia-shield/shield-qa/help-stock-recovery-shield-portable-t2850634
AFAIK the "broken android" screen is expected.
You just have to press the Power and Home buttons at the same time (this sometimes takes multiple tries) again to launch the recovery.
Go here and download this tool
http://forum.xda-developers.com/showthread.php?t=2661067
Once you have that grab the recovery file and the cwm file.
(Not at a computer right now if you need any files, let me know if you need them)
Turn off the Shield
Hold home, back and the Nvidia button all at once, your in fastboot now.
Here on command prompt type "fastboot flash recovery (location of your recovery image)"
Once you did that on the device go to recovery and you should have the android laying on his back, dead, poor little thing.
Hold home Nvidia button and back and once off boot normally.
One in the system update the system as normal once done turn the device back off
Go back in to fastboot and run on your computer "fastboot flash recovery (location of your cwm file)”
One you do that go back in to recovery and you should have cwm now. Reroot using the flash method "supersu has a flashable file you can use to root" one rooted your done till the next system update.
I have done this for the last 3 or 4 updates and works like a charm [emoji2]
Sent from my Amazon OtterX using Tapatalk
Doesnt work for me. I've tried it so many times and although it flashes everything back to (ota 56 I think) recovery stays broken. Then I went as far as replacing the stock recovery with the official one off nvidias development page still no luck. Tried to flash it bone stock (factory) and although the rom reflects the update/downgrade recovery always stays broken.
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
JanSpatschek said:
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
Click to expand...
Click to collapse
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
[deleted]
Ducter said:
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
Click to expand...
Click to collapse
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
JanSpatschek said:
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
Click to expand...
Click to collapse
Another option, if nothing else seems to work is start over. I generally use nexus devices and flash factory images, looks like you can do that also on the one..
Hello,
I have the same problem. I unlocked my OPO, flashed the TWRP 2.8.7.0 and everything went good and smooth. Then I flashed CM12.1 and it worked. Now I wanted to downgrade TWRP to the TWRP 2.8.6.0 because of some issues with the latest version and after flashing the older version it will not boot to recovery at all...
Please help.
Thank you
EDIT: SOLVED!!
Okay, so I managed to get it back working again.
How I proceded:
1. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and do everything that is said in the 3rd point of the first OP post. (+download the file for your OPO - either for 16GB or 64GB model - after you have it downloaded unpack it)
2. flash all the files listed in the 3rd point of the first OP post
3. boot in the OS, enable developer settings and enable USB debugging and allow it
4. get back in the fastboot mode and flash either TWRP 2.8.6.1 or later versions (because of Lollipop compatibility)
5. enjoy!
God bless you.