I had Cyanogen's 1.4 recovery image and one day it suddenly just wasn't there. I hadn't even rebooted to recovery mode in weeks and have no idea how it happens. Now I have the red, white, green screen and can't flash anything.
This randomly happened, I hadn't flashed anything or even messed with the phone in a long time. Anyway, how can I get my recovery image back? Since I need a new one I might as well upgrade to RA's.
I'm pretty sure I have root, since it says I have CM 4.2.12 and all the root functions still work. I'm just missing the recovery image.
Any ideas?
Dunno what you did, but to flash RA's image..
http://forum.xda-developers.com/showthread.php?t=530492
read instructions in the thread, take about 2 minutes. Do it through adb since there's c+p
Can't do it through adb since I don't have any recovery image
Lemeja said:
Can't do it through adb since I don't have any recovery image
Click to expand...
Click to collapse
As long as you still have root you should be able to do it using adb while you're phone is running ie: not in recovery
This is strange...I can't even run fix_permissions, it says access denied.
Related
So . i am trying to install the CyanogenMod. I had rc30, downgraded, rooted (by doing this: http://bit.ly/vk4n). then i made the flash_image recovery /sdcard/cm-recovery-1.4.img thing. finally i started up in recovery mode, applied the DRC83 file and the rom. I restarted the phone, i could see the "T-Mobile G1"-logo, then it disappeard, then CyanogenMods' blue logo appeared.. After a while, it disappeard and a blank, black screen appeared, and nothing happend since then..
So, i would like to try again, i installed the RC29 again, but now, i cant attach the phone to my computer, it simply doesnt detect it. (cant connect to adb shell to do the wi-fi registering). So i tried to boot up in recovery mode again, but this is what i get:
http://i154.photobucket.com/albums/s242/xabdullahx/Billede0253.jpg
What is this?
How do i fix the phone so i can try to put the CyanogenMod rom again.
BTW. this is my first flashing attempt
XabdullahX said:
So . i am trying to install the CyanogenMod. I had rc30, downgraded, rooted (by doing this: http://bit.ly/vk4n). then i made the flash_image recovery /sdcard/cm-recovery-1.4.img thing. finally i started up in recovery mode, applied the DRC83 file and the rom. I restarted the phone, i could see the "T-Mobile G1"-logo, then it disappeard, then CyanogenMods' blue logo appeared.. After a while, it disappeard and a blank, black screen appeared, and nothing happend since then..
So, i would like to try again, i installed the RC29 again, but now, i cant attach the phone to my computer, it simply doesnt detect it. (cant connect to adb shell to do the wi-fi registering). So i tried to boot up in recovery mode again, but this is what i get:
http://i154.photobucket.com/albums/s242/xabdullahx/Billede0253.jpg
What is this?
How do i fix the phone so i can try to put the CyanogenMod rom again.
BTW. this is my first flashing attempt
Click to expand...
Click to collapse
If you reinstall the RC29 you lose root and you didnt install the radio needed for custom roms.
i installed a file called "DRC83_base_defanged" . what is it?
and how do i install the radio?
Btw. I followed this guide: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Bump.
What should i do :/
My computer doesnt detect my phone, i cant do the registering via wifi trick :S
I just want my phone back to its normal state with rc30, able to connect to computer and able to go to recovery mode.
I installed the rc30, but cant figure the other things out
------
Figured it all out
XabdullahX said:
Bump.
What should i do :/
My computer doesnt detect my phone, i cant do the registering via wifi trick :S
I just want my phone back to its normal state with rc30, able to connect to computer and able to go to recovery mode.
I installed the rc30, but cant figure the other things out
Click to expand...
Click to collapse
You should follow 1 click root guide..its pretty simple..
when you see that screen. hit alt+l i think to pull up the recovery menu.
if you don't have a card reader, you can mount your g1 through the console on your recovery menu. just google "mount g1 through console" for directions. hope that helps you get the right files on your phone to flash.
good luck!
Hey all, Im on Firerat's version of CyanogenMod 5 (latest), same SPL and radio in my sig. I tried to flash Amon's latest recovery, but i got an "Out of Space" error in terminal, so i tried to clear up things on /system, and flashed it through adb. I rebooted into recovery by holding power and home, and it took me to a black screen and it kept rebooting constantly into the black screen, i had to pull my battery out for it to stop. However, the ROM loads just fun with no problems...I tried reverting to my old version Amon RA 1.6.2, and i got no error on terminal, strange thing is the newer Amon Recovery is a smaller filesize...I tried redownloading and installing it but not luck...when i rebooted into recovery, same thing. Am I doomed to a recovery-less G1 or is there hope? =O
Thanks everyone!
If you already have ADB access on your computer
Flash the recovery through fastboot or Droid Explorer
thanks for the suggestion, tried that and same as before it still shows the g1 logo then a black screen, then the g1 logo and logo fades away to a black screen and it goes into a loop where its constantly vibrating and rebooting and showing a black screen the whole time. im confused..
while in adb did you try to command it to reboot to recovery or explore and see if you indeed still have a recovery or not?
Kemekill Products said:
while in adb did you try to command it to reboot to recovery or explore and see if you indeed still have a recovery or not?
Click to expand...
Click to collapse
i rebooted into recovery with adb but it was corrupt. i actually solved the problem. i searched deeper and deeper and got creative with search terms to find out that some people have had a similar experience flashing Amon 1.7, the easy solution was to download rom manager from market, flash the clockwork recovery, then from the app flash amon 1.7. all is well again, thanks for chiming in guys
Next time, to avoid any mistakes, flash it through fastboot.
It's the safest/best way to do it.
AustinAce said:
Next time, to avoid any mistakes, flash it through fastboot.
It's the safest/best way to do it.
Click to expand...
Click to collapse
yeah lbcoder was talking about that with spls i had no idea same went for recovery images. but next time ill play it safe. i heard it was actually a terminal problem with CM5
i accidentally installed the wrong recovery image onto my g1. it was sapphire. now i cant even enter my recovery mode. i can still enter into my phone like normal but recovery mode, it will get stuck onto the G1 screen forever. let me know THANKS!
anybody? a little help here
you could probably try loading the right recovery img through the terminal, since your phone boots like normal. Just a suggestion though.
josh84 said:
you could probably try loading the right recovery img through the terminal, since your phone boots like normal. Just a suggestion though.
Click to expand...
Click to collapse
i tried that method already. still nothing. i even used the right image this time lol
got it. had to put new fastboot image. so im just rerooting my phone again thanks anyways !
Alright, so I'm having an issue with CM 6.0.0 on my CDMA Hero. A few weeks back it started not letting me install apps 90% of the time. I figured I would just wait for the 6.1.0 release to come out and flash that and see if it fixed it before completely wiping my phone. Well, it came out, I moved the zip to my phone (after fighting with it to let me turn on USB storage), I go to reboot into recovery AND....it sticks on the HTC screen for 15 minutes. I unplug the battery put it in again and attempt again...nothing. Since then my phone has been restarting at random times. I can't do much of anything to phone if I can't get into recovery. I'm lost.
It will however boot into bootloader, if that helps anybody.
wh1terav3n said:
It will however boot into bootloader, if that helps anybody.
Click to expand...
Click to collapse
bootloader -> ruu -> root -> ... is what id do...
If you can boot into whatever ROM you're running, just flash the recovery again. Either using the android debug bridge:
Code:
adb shell
su
flash_image recovery /sdcard/NameOfRecoveryHere.img
or terminal emulator
Code:
su
flash_image recovery /sdcard/NameOfRecoveryHere.img
I figured it out. Reflashing did nothing, so finally I downloaded the Amon-Ra recovery instead of using the Clockwork Mod Recovery I had been attempting. It did finally boot to the recovery.
Oh I assumed you were already using Amon since it is the better one of the two in my opinion.
I've never had problems with it so far
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.