Hi Folks,
I had a CyanogenMod-6.1 for Nexus One :: V6.1.0-RC1 (10/28/2010) installed on my Nexus 1.
Prior to that i was using CM6.0 RC1 stable release. Did an upgrade (with full void and nandroid backup) to try out the new features.
However this afternoon, out of nowhere, my volume buttons and trackball started to malfunction.
i.e to say : I cannot adjust volumes in any part of the apps/phone and i can't select/click stuffs with the Trackball.
Hence, I thought of removing CM6.1. Here's the problem started.
#1. I can't boot into recovery. The phone itself will be stuck at the big "X" screen. After 5mins, it will boot into CM6.1
- Using ROM Manager i tried to reflash Clockwork Mod 2.5.1.0 for a couple of times but i still cannot get into Recovery.
Be it powering up with trackball held down, booting into recovery up via Rom Manager. Surprisingly, volume down was working together with power down was able to go into Bootloader
for me to select "Recovery", however, i still can't access Recovery.
#2. I tried using ./fastboot-mac flash recovery updatedclockwork.img also can't.
#3. I tried using Amon-RA. ./fastboot-mac flash recovery Amon-RA.img also to no avail.
#4. i used ./fastboot-mac update to load a StockFRF91 Froyo also can't get into recovery.
As of now, my phone is stuck continuously in bootloop, cannot access Recovery. I've tried almost 30+ fixes on XDA and other Android Forums but i still can't fix it.
Is there anyway, i can wipe everything inclusive of the "Corrupted Recovery" files and restore back my Nexus One?
Thank you all please save my phone! :'(
Dude I feel your pain. I have the exact same problem. I wonder if it is a CM6 issue?
Related
I have a Mytouch 3G running test 7 on my phone, and i just installed the clockworkmod rom manger. After, installed it i wanted to flash a new rom, so flashed the clockwork mod recovery, and when i tried to install the new rom from the sd card, it keeps on getting stuck on the mytouch screen, and nothing happens. How do i get into the recovery screen? thanks
First: This belongs in Q & A !!!!111
Which ROM did you flash? Maybe you had to wipe before
right now, i'm running cyanogen test-7, but when i go into the clockworkmod rom manger app and pick the flash rom from sd card, it just says it has to go to the recovery, and then my phone will reset and it would just get stuck on the mytouch screen. So, i just pull out the battery and reset the phone again, and i realized if i press the end button, it will go the rom that is already on the phone. I'm i suppose to push some buttons or something to get to the recovery screen?
No it should flash the rom you select and reboot the phone to boot the new rom without keypress needed.
maybe the wrong device was selected when downloading the recovery image? Try reinstalling clockworkmod recovery from rom manager.
Mod edit: not dev related, moved to q&a
I have the same problem.
I downloaded and installed Rom Manager from the Market and it has completely screwed up my recovery (I can't get into it at all). I tried flashing Amon's again (through Rom Manager) and it still doesn't work.
HTC G1. CM5.07 test 7 (trying to go to stable!).
Your recovery has been corrupted, you will need to flash it through fastboot.
JAguirre1231 said:
Your recovery has been corrupted, you will need to flash it through fastboot.
Click to expand...
Click to collapse
Yes thank you. I erased recovery partition in fastboot then reflashed Amon's.
Working now.
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
illmatic282 said:
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
Click to expand...
Click to collapse
Connect to your PC via USB, and from the command line issue "fastboot erase recovery" and then "fastboot flash recovery filename.img"
More on common fastboot commands here can be found on these forums, i'm not allowed to post links.
i connected my phone to my computer but nothing on my computer pops up. only the new hardware wizzard pops up. what do i do from here? im i suppose to get a adb popup? how do i set up the fast boot? i'm so confused..thanks
some one, please help..i want to be able to flash new roms in the future...thanks in advance
Can I sugges that you try this sticky thread at the top of this forum board.
It contains all you need to know on who to set up fastboot and how to use it - there are a couple of tutorials on it if you read through the thread.
CM 5.0.7 for Dream/Sapphire introduced a bug in flash_image. It causes recovery flashes to fail. It has since been fixed in the latest test of 5.0.8 I believe.
Man i have the same darn bug cant get back into recovery for nothing, and i dont have a pc to fastboot i have a non intel based mac so no adb or fastbooting, i have been doing fine for forever without adb or fastboot but is there any way around this one, i need help bad, im on HTTClay Superbadv1.3 and it has all sorts of bugs but i cant nandroid or bart or flash any rom without recovery, can someone please help!!!
Also is there another way to erase the recovery partition?
I have searched other posts and not found my same problem, so excuse me if I repeat another thread.
I have a rooted g1 running superfly v1.2 D/S. I tried to use Rom Manager to flash another ROM, but upon reboot it never flashed, it just stayed at the T-mobile/G1 boot screen.
I then took out the battery, and tried to do a manual reboot to recovery (power+home) and I never got into recovery mode, it just stayed at the G1 screen again.
I then tried fastboot (power+camera) but that took me no where. My only options were to shutdown, go back to hboot, reset data, and one other thing I can't remember.
When I take out the battery and then power back on again, it boots up the superfly ROM and starts up normally.
My Question is how can I get into recovery mode to flash a different ROM, and why doesn't it work through ROM Manager?
Looks like your recovery got erased...you have two options....
1. Setup fastboot on you PC, flash a new recovery from fastboot. this is the best and safe method...
2. flash a recovery from terminal...you might have to do this step multiple times...flash recovery...power off the phone, power on holding home button and see if you have working recovery...if not restart the phone and flash again...
I would go with 1st option.
mbh8280 said:
I have searched other posts and not found my same problem, so excuse me if I repeat another thread.
I have a rooted g1 running superfly v1.2 D/S. I tried to use Rom Manager to flash another ROM, but upon reboot it never flashed, it just stayed at the T-mobile/G1 boot screen.
I then took out the battery, and tried to do a manual reboot to recovery (power+home) and I never got into recovery mode, it just stayed at the G1 screen again.
I then tried fastboot (power+camera) but that took me no where. My only options were to shutdown, go back to hboot, reset data, and one other thing I can't remember.
When I take out the battery and then power back on again, it boots up the superfly ROM and starts up normally.
My Question is how can I get into recovery mode to flash a different ROM, and why doesn't it work through ROM Manager?
Click to expand...
Click to collapse
Most likely your recovery is corrupted. Flashing a recovery from within CM5/CM6 is not working well, so you need to flash a new recovery using fastboot.
When in fastboot mode, you can "control" your phone from your pc using the fastboot command. For this you need to connect your phone to your pc by USB.
Search here for the ADB/Fastboot threat, where you will find further information.
Sent from my Htcclay's Superfly G1 BTX using XDA App
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
Hi
I successfully flashed Froyo onto my stock Captivate yesterday using Odin in download mode - but it was not w/o a a hiccup or two.
I wanted to to try the Paragon ROM but it appears that the only way is flash it is to place it in the SD of the phone and then boot into recovery, then choose reinstall packages.
So, reading I found that I would need to flash back to stock to do this, so that is what I did. Then I copied the files I needed to the phone and rebooted into recovery mode. Thats when the fun started.
No matter what, I could not select anything using the power button and went into the reboot loop for a while. I was very frustrated. Finally, I figured out how to get into Download mode using the adb reboot download trick and successfully flashed back to stock.
So my question is - Is there anyway to flash those new custom ROMs with Odin?
Odd issue, after second stock flsh had problem continued
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.