16 replies to this topic

[BodyMarks]

I’m sorry this is so long. A lot took place, and I will do my best to describe it. Please, help if you have any suggestions on what might be going on. Thanks.

I started by doing a wipe and loading CM6-RC1 and installing all my apps and settings (I had been on BBv0.4). I wanted to backup what I had done so far, but it would not work. When trying to backup or load a different kernel (through Rom Manager,) it looked like it was working, but there was no backup or new kernel after rebooting. I tried every way possible to get into Clockwork Mod recovery: Rom Manager, Quick Boot, holding down x and power but no go. All apps requiring root are working, but I no longer had the ability to get to recovery. Next, I flashed alternate recovery using Rom Manager and tried to go into SPRecovery, but it did the same as Clockwork Mod (long Moto logo then reboot).

* I was able to get to the bootloader, so I went ahead and flashed SPRecovery using RSDLite. Now in SPRecovery, I was able to restore an older backup of BB which loaded no problem.
  
Next, I was able to flash to Clockwork Mod recovery and loaded a wiped and clean copy of BBv0.4, loaded apps and settings and then tried to do a backup. Now I have the same problems with not being able to backup, change kernel, get into recovery that I did after loading CM6.
What took place while flashing RSDLite: After flashing my phone it booted back up with the BB bootanimation. Once it gets past the bootanimation, the phone has a solid red LED and looks like a dead phone after flashing a bad kernel. I waited till RSDLite finished flashing, then I pulled the battery and was able to boot back up into SPRecovery.*

At present my phone is running BBv0.4. I have root, all apps are running correctly but I cannot get into recovery. I don’t understand what has caused this problem or what to do next.  Anybody run into something like this?

[AbsoluteZero]

@PDR447 -> "I had been on BBv0.4"...who said there was no correlation in IRC?

If RomManager is working correctly in your current backup make sure it's up to date...
Connect to Wifi.
Open RM, go to settings, and choose "Erase Recovery" then back out.
Now go to settings and choose "Clear download cache".
Then go to the bottom of the RM list and choose "All ClockworkMod Recoveries" and choose version 2.0.2.0 or 2.0.2.4 and hit OK.
Select Motodroid.
After a short while you should see "successfully flashed"
Now try to boot into recovery by holding Power+X.

If that doesn't work, go back, clear download cache, flash spre, then flash CWMR again.

There's posts about this problem when coming from BB in the forums, I'll see if i can find them.

Also, mods please move to Experimental Forum.

[BodyMarks]

Absolute Zero, on 14 July 2010 - 12:34 AM, said:

@PDR447 -> "I had been on BBv0.4"...who said there was no corelation in IRC?

If RomManager is working correctly in your current backup make sure it's up to date...
Connect to Wifi.
Open RM, go to settings, and choose "Erase Recovery" then back out.
Now go to settings and choose "Clear download cache".
Then go to the bottom of the RM list and choose "All ClockworkMod Recoveries" and choose version 2.0.2.0 or 2.0.2.4 and hit OK.
Select Motodroid.
After a short while you should see "successfully flashed"
Now try to boot into recovery by holding Power+X.

If that doesn't work, go back, clear download cache, flash spre, then flash CWMR again.

There's posts about this problem when coming from BB in the forums, I'll see if i can find them.

Also, mods please move to Experimental Forum.

I followed your directions exactly, each time unable to go into recovery.
Thank you Absolute Zero for your response. I will follow this thread and hope for a solution.

[AbsoluteZero]

BodyMarks, on 14 July 2010 - 01:15 AM, said:

I followed your directions exactly, each time unable to go into recovery.
Thank you Absolute Zero for your response. I will follow this thread and hope for a solution.

Follow the Second Method HERE

[BodyMarks]

Absolute Zero, on 14 July 2010 - 01:18 AM, said:

Follow the Second Method HERE

The links are not working.(Step 1: Download the latest version of ClockworkMod Recovery here;  Download flash_image file here)

[AbsoluteZero]

BodyMarks, on 14 July 2010 - 01:43 AM, said:

The links are not working.

Droid Clockwork Recovery
flash_image file

[BodyMarks]

Absolute Zero, on 14 July 2010 - 01:53 AM, said:

Droid Clockwork Recovery
flash_image file

Thank you so much for your helpfulness, working on it.

[BodyMarks]

Absolute Zero, on 14 July 2010 - 01:53 AM, said:

Droid Clockwork Recovery
flash_image file

I placed a copy of "flash_image" and "recovery.img" on the root of my sd card.
I entered in terminal emulator:
su
cd /sdcard
flash_image recovery /sdcard/recovery.img

I got: mtd: re-read error at "0x0044000"... (Out of Memory)
error writing recovery: No Space left on device
/mnt/sdcard #

Could not go into recovery.

[AbsoluteZero]

BodyMarks, on 14 July 2010 - 02:48 AM, said:

I placed a copy of "flash_image" and "recovery.img" on the root of my sd card.
I entered in terminal emulator:
su
cd /sdcard
flash_image recovery /sdcard/recovery.img

I got: mtd: re-read error at "0x0044000"... (Out of Memory)
error writing recovery: No Space left on device
/mnt/sdcard #

Could not go into recovery.

Reboot your phone and try the commands again. Should work.
Or try ADB.

[BodyMarks]

Absolute Zero, on 14 July 2010 - 02:59 AM, said:

Reboot your phone and try the commands again. Should work.
Or try ADB.

I tried again using virtual emulator; same result "error writing recovery: No space left on device"

I also used ADB but got the same result. Why would it say no space left on device?

Attached Files

•  virtual emulator3.jpg   84.03K   12 downloads
•  virturl emulator2.jpg   351.53K   13 downloads

[bchsun]

BodyMarks, on 14 July 2010 - 03:44 AM, said:

I tried again using virtual emulator; same result "error writing recovery: No space left on device"

I also used ADB but got the same result. Why would it say no space left on device?

I'm getting the same thing. I want to try the fastboot way to fix it, but I can't figure out how fastboot works exactly... Anyone wanna help me with that?

[AbsoluteZero]

BodyMarks, on 14 July 2010 - 03:44 AM, said:

I tried again using virtual emulator; same result "error writing recovery: No space left on device"

I also used ADB but got the same result. Why would it say no space left on device?

Ok...if you get that error, just type the last part again. In other words type "flash_image recovery /sdcard/recovery.img". It should install the next time you enter it after those errors.

Note, you do not have to include the "/sdcard/" since you have already changed directory (cd) into /sdcard. In other words, you can just type "flash_image recovery recovery.img" but either way is fine.

Edit: I tried it and got the memory errors too, but as I stated, on the second run it flashed fine. I was able to go back and forth between CMR 2.0.2.0 and 2.0.2.4 a couple times (booting into each to verify it actually flashed).

[BodyMarks]

Absolute Zero, on 14 July 2010 - 04:50 AM, said:

Ok...if you get that error, just type the last part again. In other words type "flash_image recovery /sdcard/recovery.img". It should install the next time you enter it after those errors.

Note, you do not have to include the "/sdcard/" since you have already changed directory (cd) into /sdcard. In other words, you can just type "flash_image recovery recovery.img" but either way is fine.

Thank you for your continued assistance. I'm afraid I got the same results when entering "flash_image recovery recovery.img" for the second time.

[Firerat]

if your still having problems

http://forum.cyanoge...dpost__p__21996

I posted a script to get round the OOM issues

it should work the same on your phone

[BodyMarks]

Firerat, on 14 July 2010 - 05:19 AM, said:

if your still having problems

http://forum.cyanoge...dpost__p__21996

I posted a script to get round the OOM issues

it should work the same on your phone

The first time I tried it it said something like it could not read "/sdcard/FR-flashRec-v02.txt". I went ahead and rebooted my Droid and tried a second time and it said "sh: can't open '/sdcard/FR-flashRec-v0.2.txt"

I put an extra "." as in -v0.2.txt

i tried it again with correction and ran (see screen shot). It did not freeze and eventually I shut down the Droid and tried to boot into recovery but no go.

Attached Files

•  virtual emulator4.jpg   86.94K   9 downloads
•  virtual emulator5.jpg   272.49K   7 downloads

[BodyMarks]

I tried a number of "solutions" but none of them worked. I ended up using RSDLite to flash SPRecovery. I loaded an old backup and then was able to load BBv0.4, a ChevyNo1 1.2Ghz kernel and 928Droid's Black Glass theme. Why I was able to do all this using SPRecovery when I couldn't using Clockwork recovery? I do not understand what caused the problem.

[Matthew123]

Absolute Zero, on 14 July 2010 - 01:18 AM, said:

Follow the Second Method HERE

I had to reboot a few times (type "reboot" into adb) to get it to work. Was getting the "not enough room" errors. Eventually this method worked for me. Thank you so much.