Blade won't boot into recovery mode, boots normally - Blade General

Hi,
I have a Gen1 Blade running custom 2.2 ROM, that I have flashed on it and it also has the latest Clockwork Recovery (via ROM Manager app).
I want to at least do a factory reset, but preferably flash a new, better ROM so that I can give it to another family member.
The problem is that it won't boot into recovery, not by holding the volume bottom down, nor by telling it to reboot to recovery. What it does is just show the green android logo and that's it.
It does boot normally, and everything is working as it should.
When I tell it to do a factory reset and the confirm it, the phone restarts and it is the green logo again. After a while I just have to remove the battery and it just boots up normally without anyting changed.
Is there a way to flash a new ROM without recovery, via PC and adb or something?

Latest gen1 supported CWM is 3.0.1.4 so you'll need to use that or update to gen2 to use the latest CWM
Sent from my ZTE-BLADE using Tapatalk 2

matt4321 said:
Latest gen1 supported CWM is 3.0.1.4 so you'll need to use that or update to gen2 to use the latest CWM
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
This
You'll be better off with Gen2 anyway
Sent from my Ouya

QuantumFoam said:
This
You'll be better off with Gen2 anyway
Sent from my Ouya
Click to expand...
Click to collapse
That's all good, but how do I update to Gen2 if it won't boot into recovery?
I think I had an old version of CWM on which didn't work the last time I checked and that's when I upgraded CWM with ROM Manager which I assume flashes a compatible version, doesn't it?
I'll try 3.0.1.4 just to be sure

You don't need recovery for a tpt. Just place the tpt on the root of your sdcard and power on holding volume+
Sent from my Ouya

QuantumFoam said:
You don't need recovery for a tpt. Just place the tpt on the root of your sdcard and power on holding volume+
Sent from my Ouya
Click to expand...
Click to collapse
I'll try that thanks

My CWM-6.0.1.1 and 6.0.1.2 (if you're up for testing, i'm pushing it because i need testers) support gen1/2/3 AND Chinese blades.
You can flash it by booting normally, then using adb and fastboot (search and download/install).
After installation it's as simple as typing:
adb reboot bootloader
fastboot flash recovery [name of the recovery]
fastboot reboot
That's it. Everything is intact and you have a working recovery.
If you're running Linux, make sure you're running as root before executing and add "./" at the beginning of each command.

Jinxxed said:
My CWM-6.0.1.1 and 6.0.1.2 (if you're up for testing, i'm pushing it because i need testers) support gen1/2/3 AND Chinese blades.
You can flash it by booting normally, then using adb and fastboot (search and download/install).
After installation it's as simple as typing:
adb reboot bootloader
fastboot flash recovery [name of the recovery]
fastboot reboot
That's it. Everything is intact and you have a working recovery.
If you're running Linux, make sure you're running as root before executing and add "./" at the beginning of each command.
Click to expand...
Click to collapse
i have dell xcd35 gen2. its running on cm7. cwm is 5.0.2.0.. i want to upgrade to cm9. but wen i reboot into recovery it just hangs on the dell logo.plz help..if i have to use the above mention method or somthing else, please explain in detail

Related

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.
So I can literally flash a different recovery from within another?
jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium
Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks
Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk
I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.
Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.
Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

Can't boot in recovery, can't ADB too..

I have a little problem,
i flashed the 5.5.0.4 CWM.
My issue however, is that i can't boot in recovery. Whenever i use an app to boot in recovery and just straight boots Android. Im not experiencing the recovery boot-loop.
The other problem is that i can't use ADB either, i have the stock ICS that can't recognize a PC connection via USB.
SBK2 so NVflash is out of the question.
Help
i want to get another recovery on there and flash another rom to avoid all these issues
Which app are you using exactly? Not all of them work correctly on the tf.
Have you try using the button combo method?
Hold down Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec should take you to recovery
As for ADB, do you have correct driver install?
Did you install ASUS PC sync?
kriEv said:
I have a little problem,
i flashed the 5.5.0.4 CWM.
My issue however, is that i can't boot in recovery. Whenever i use an app to boot in recovery and just straight boots Android. Im not experiencing the recovery boot-loop.
The other problem is that i can't use ADB either, i have the stock ICS that can't recognize a PC connection via USB.
SBK2 so NVflash is out of the question.
Help
i want to get another recovery on there and flash another rom to avoid all these issues
Click to expand...
Click to collapse
Had the same issues and installed an app called "Transformer reboot to Recovery" that worked!
Humm disregard this issue..
I wasn't pressing the VOL+ key to get in recovery.. strange because it never happened before but anyways..
should i still walk away from 5.5.0.4? Because i did some test and i have no issues with it..
kriEv said:
I have a little problem,
i flashed the 5.5.0.4 CWM.
Help
i want to get another recovery on there and flash another rom to avoid all these issues
Click to expand...
Click to collapse
See the following thread where this is discussed in detail. It is three posts down from yours on the first page.
http://forum.xda-developers.com/showthread.php?t=1530337
kriEv said:
The other problem is that i can't use ADB either, i have the stock ICS that can't recognize a PC connection via USB.
SBK2 so NVflash is out of the question.
Help
i want to get another recovery on there and flash another rom to avoid all these issues
Click to expand...
Click to collapse
I just used the SDK version ADB and Drivers to get ADB working fine. Just used it to put Revolver on.

Can't get into recovery mode after changing bootloader

I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
guitarguy6 said:
I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
Click to expand...
Click to collapse
1. Make sure you have the Android SDK installed to your PC.
2. Boot the tab to fastboot using PWR and Vol+
you should get a menu
Select Fastboot Mode. Should say it at the top center when in fastboot
3. Download your CWM image file and copy it to your C:\Program Files\Android\Android-sdk\platform-tools folder. (might be in Program Files (x86).
in that folder you will see a file called "fastboot.exe"
Wait, plug your tab in.
4. Open a command window in that folder (shift + right mouse click)
in the window, type fastboot flash recovery nameofyourrecover.img (where nameofyourrecovery is what the recovery image file is named.
5. Hit Enter
Should flash your CWM recovery image back. I advise you use the latest CWM recovery. 1.7.2 or 1.7.3 you can get at tegraowners site
MD
If I don't have a recovery image am I SOL? Can I download one from somewhere?
guitarguy6 said:
If I don't have a recovery image am I SOL? Can I download one from somewhere?
Click to expand...
Click to collapse
tegraowners.com is one place.
The other recovery, is PublicRecovery which you can find in the Dev Forum.
Both are good recoveries. Albeit the CWM one is notorious for not revealing source code on his kernels. Non-GPL, which is why he is not allowed to post his kernels or roms at XDA. Might be sending your usernames and login's for all anyone knows,
The CWM "is" GPL compliant. So no needs to worry.
The "search" button, is such an easy thing to use.
MD
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
guitarguy6 said:
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
Click to expand...
Click to collapse
Yeah, keep forgetting about that one. But, just make sure the Recovery you installed is a recent one. Not sure how often that app gets updated.
Some of the older versions have issues with ICS sometimes, especially TWRP. So check versions.
MD

[Q] Can't boot into recovery, even with USB cable - but everything else is fine

The title says it all. In fastboot, selecting recovery shows "Google", then a black screen for a moment, then "Google" again, then the tablet boots normally. I am aware that there's a problem with booting to recovery if you don't hook up a USB cable during Fastboot mode, but I've done that and I still can't get to recovery. I've tried it with stock recovery and after flashing CWM recovery, but no dice on either.
Thanks for any advice you can provide!
Edit: For anyone wondering, this is a 16gb wifi-only Nexus 7 running unrooted 4.2.1.
Have you tried...
adb reboot recovery
or
adb reboot bootloader
Sent from my Nexus 7
veeman said:
Have you tried...
adb reboot recovery
or
adb reboot bootloader
Sent from my Nexus 7
Click to expand...
Click to collapse
I had to down grade to the 3.34 recovery image to get my N7 to boot into recovery and it only does so from an app licate Quick Boot.
do you have the correct bootloader? if not, flash the appropriate version of the bootloader. also try the goomanager app from the market, it installs a (in my opinion at least) better recovery call twrp, or team win recovery project.
veeman said:
Have you tried...
adb reboot recovery
or
adb reboot bootloader
Click to expand...
Click to collapse
The exact same thing happens with reboot recovery - shutdown, Google logo, black screen, Google logo, normal boot. With adb reboot bootloader, I get into fastboot mode, then selecting Recovery does the same thing - Google logo, black screen, Google logo.
Billchen0014 said:
do you have the correct bootloader? if not, flash the appropriate version of the bootloader. also try the goomanager app from the market, it installs a (in my opinion at least) better recovery call twrp, or team win recovery project.
Click to expand...
Click to collapse
This happens with the stock recovery from the Google Nexus 7 Toolkit and with CWM. I believe I did install twrp earlier but the fact remains, I cannot access any recovery under any circumstances, they just progress to a normal boot.
Maybe do a fresh setup(Stock Rom) with nexus 7 toolkit and then try to flash the recovery(again), just an idea.
bigmike87 said:
Maybe do a fresh setup(Stock Rom) with nexus 7 toolkit and then try to flash the recovery(again), just an idea.
Click to expand...
Click to collapse
Did that before posting on this thread, but sadly, no dice.
Billchen0014 said:
do you have the correct bootloader? if not, flash the appropriate version of the bootloader. also try the goomanager app from the market, it installs a (in my opinion at least) better recovery call twrp, or team win recovery project.
Click to expand...
Click to collapse
How do I determine the bootloader version? And why would this cause a problem?
shellsonthefloor said:
How do I determine the bootloader version? And why would this cause a problem?
Click to expand...
Click to collapse
Bootloader 3.41 was problematic (for some) in earlier versions of CWM and TWRP. The correct bootloader version for JOP40D is 4.13. Use this with CWM 6.0.1.9 or TWRP 2.3.2.1
To determine the current version reboot in fastboot mode - power off device, hold vol down + power. Your device should then look like this

Categories

Resources