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!
Related
Hello all,
Im trying to flash a new recovery image, but none seem to be working. Im not sure if you're familiar with the file names, but Ive tried "recovery-clockwork-3.0.2.4-crespo.zip" and "3101-orange.img"(j_rodd's modification of koush's). I tried to go to the source but it seems koush's site is down right now.
The phone is unlocked, however when I select recovery from the bootloader the phone shows a package unboxing image and then an android next to an exclamation in a triangle. Regular boot is fine.
Thanks in advance.
you're doing this in bootloader, right?
You have to be in bootloader, open cmd on computer and flash through there.
You can find 3.1.0.1 here http://forum.xda-developers.com/showthread.php?t=988686
outamoney said:
Hello all,
Im trying to flash a new recovery image, but none seem to be working. Im not sure if you're familiar with the file names, but Ive tried "recovery-clockwork-3.0.2.4-crespo.zip" and "3101-orange.img"(j_rodd's modification of koush's). I tried to go to the source but it seems koush's site is down right now.
The phone is unlocked, however when I select recovery from the bootloader the phone shows a package unboxing image and then an android next to an exclamation in a triangle. Regular boot is fine.
Thanks in advance.
Click to expand...
Click to collapse
Are you on stock rom? if yes, then no matter how many times you flash the custom recovery(cwm or jrodd), once you reboot your phone and enter recovery, you'll always end up with stock recovery.( the image you are getting android next to triangle is that of the stock recovery)
what you should do is enter bootloader, fastboot flash ur recovery, and from there (without reboot) enter recovery directly. i would recommend you flash a custom rom.
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!!!!!
Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...
Please steps
JacKJodel23 said:
Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...
Click to expand...
Click to collapse
How did you do that? could please put steps or that alike? I rooted my a700 and put the iconian rom but i wanted to put Cyanogen but it gets stuck like you said, I also installed iconian using Rom managerm please help!
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.)
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
MrSeler said:
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
Click to expand...
Click to collapse
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
gsmyth said:
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
Click to expand...
Click to collapse
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
MrSeler said:
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
Click to expand...
Click to collapse
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
gsmyth said:
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
Click to expand...
Click to collapse
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
MrSeler said:
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
Click to expand...
Click to collapse
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
gsmyth said:
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
Click to expand...
Click to collapse
Im doing what Im told, so - After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode.
Wish I wasnt so braindead on this field =/ and the cyanogen recovery welcomes me every time
okay so instead of fastboot reboot command i should write the one you gave me? gonna try
EDIT: ERROR, DEVICE NOT FOUND
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
MrSeler said:
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
Click to expand...
Click to collapse
Your boot loader shouldn't be touched.
gsmyth said:
Your boot loader shouldn't be touched.
Click to expand...
Click to collapse
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
MrSeler said:
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
Click to expand...
Click to collapse
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
oasisdave said:
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
Click to expand...
Click to collapse
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
MrSeler said:
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
Click to expand...
Click to collapse
Yeah, that's not working for me, still goes straight to Cyanogen Recovery.
See last question in FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon