I just flashed from eclair to 1.6 (Cyanogen) and my phone is stuck at the bootscreen.
ddms reports that there is no recovery.img, but I can get into the recovery console, any fixes?
edit:
I did a full wipe, and reparitioned Fat + ext + swap, and I am using ext3.
Did you flash the base rom before flashing the cyanogenmod?
It looks like you somehow deleted your recovery image. Flash Amon_RA's recovery through fastboot. I beieve the code is
fastboot flash recovery recovery.img
and
fastboot reboot
That will replace whatever recovery image you have with amon_RA's.
Related
Hi guys, my phone currently running Amon_RA 1.6.2 and CyanogenMOD 5.0.5. Now I want to upgrade to Amon RA 1.7.0 and CyanogenMod 5.0.5.1. I know how to upgrade the ROM and I can use the updater to do that, but do I upgrade the recovery image first? and how do I upgrade the recovery image?
Thanks
No you do not have to update the recovery image first and
fastboot flash recovery [path leading up to recovery image]/[name of recovery image].img
i.e.
fastboot flash recovery C:/recovery.img
Thanks I just figured it out, and realized it was a dump question to ask...
So I put ClockworkMod Recovery 2.0.1.3 on my G1 yesterday with the app ROM Manager v2.0.0.5
I flashed a ROM using the app... No errors, no bootloop, worked fine..
I now press [HOME] + [POWER] and I get stuck at the G1 screen
I type reboot recovery via terminal and I get stuck at the G! screen
I flash_image recovery /sdcard/cm-recovery-1.4.img and I get a plethora of errors and last line states I am out of memory ????
I erase_image recovery and I get no errors but nothing happens
I go to recovery flasher and get errors if I try to back up or flash my recovery
I go to ROM Manager to flash a recovery and it wont flash CwM recovery
I dont have adb at the moment bc my comp is tanked... any suggestions?
I had Clockwork and I Flashed KenMood 1.9.3 and last night when I tried to boot into Recovery it would just get stuck on the Splash. When I booted up normally, it would just reboot. Now when I try (after charging overnight) it works fine, but still no recovery image. I tried to flash it using ROM Manager Premium and it shows that the flash was successful but it still won't work. Any ideas on what I can do…? I don't have fastBoot setup correctly btw.
I tweeted koush and this was his reply
koush
@JunkDruggler Use erase_image to erase your recovery and flash another one. Or fastboot flash another one on there. about 1 hour ago via Tweetie for Mac in reply to JunkDruggler
So I opened terminal and kept trying over and over
erase_image recovery
flash_image recovery /sdcard/cm-recovery-1.4.img
I noticed less errors and eventually it worked..
I am now back to my obselete recovery with the console nobody uses anymore..
I have a Nexus One phone which was on Vodafone 2.2. I changed it to 2.1 stock, 2.2 and then google updated it to 2.3.4. Next I unlocked the bootloader and flashed it with Amon Ra 2.2.1 cm passion recovery. Then I installed CM7 stable version, and flashed radio to 5.08.00.04. Everything was working fine until the phone started to reboot after 5 minutes of running any app. I pulled out the battery and now it's stuck on colored X. I can access the pwr/trackball but then if go to recovery it goes back to the X.
What should I do?
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
danger-rat said:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Click to expand...
Click to collapse
What recovery image should I use?
I used Amon RA
And it still is stuck on X.
Anything else I could do?
Since you've tried Amon, why not give Clockwork a shot (2.5.1.4)?
I've also found that when you're struggling to get a custom recovery to stick, it sometimes helps to flash a stock recovery and then try again...
What is needed to pull the stock recovery image I already dumped the partition correctly I have root running on stock recovery.
I just need to figure out why i cant boot the stock recovery from fastboot
the screen just gets scrambled. But i mean i do have the recovery.img and boot.img pulled from their respective blocks. and dd'd into imgs
Maybe someone could point me in the right direction and we can have a copy of the stock recovery as well. I don't want to
fastboot flash it in case of bricking the recovery partition(Even though it should be a 1-1 copy)
I wanted to boot TWRP rather then flash it to install super su then boot into system to backup recovery partition using flashify. I can boot into TWRP but then I can't do anything after that.
LarryBoyG said:
I wanted to boot TWRP rather then flash it to install super su then boot into system to backup recovery partition using flashify. I can boot into TWRP but then I can't do anything after that.
Click to expand...
Click to collapse
Ill try with flashify i got TWRP to boot using fastboot boot, but i cant get the stock recovery to work. and dont want to flash without making sure. since the stock recovery when i use dd is 16mb
Hi,
i'm running an rooted Z3+ dual SIM with Nougat 7.1.1 (customizedRU 32.4.A.1.54) with an old 3.0.2 TWRP version
i tried now to update my TWRP with adb flash comands and also with the TWRP.apk from googlePlay store
bothe said succelfull updated, but when i reboot into recovery it still says i have the old v3.0.2 version running
my problem i tried to restore an backup but after the restored my phone keeps always booting into recovery
edit...wenn i tried ti flash an image via Recovery its showing my boot partition only....no recovery partition where i have to flash the new recovery(i know)
on my Xcompact i have an boot and recovery partition.
found this is that still right.???
cause my Xcompact has an recovery partition
Rycon33 said:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
Tapatalked from my TX
Click to expand...
Click to collapse