Related
no space left on device. It's the error I get when trying to flash the recovery onto my evo 4g since the rom manager recovery does not boot up. All i get is the image of the smartphone with the triangle. How do i fix this?
# flash_image recovery /sdcard/recovery-RA-evo-v1.7.0.1.img
flash_image recovery /sdcard/recovery-RA-evo-v1.7.0.1.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000a0000 (I/O error)
mtd: erase failure at 0x000a0000 (I/O error)
mtd: skipping write block at 0x000a0000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x000e0000 (I/O error)
mtd: erase failure at 0x000e0000 (I/O error)
mtd: skipping write block at 0x000e0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00160000 (I/O error)
mtd: erase failure at 0x00160000 (I/O error)
mtd: skipping write block at 0x00160000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001a0000 (I/O error)
mtd: erase failure at 0x001a0000 (I/O error)
mtd: skipping write block at 0x001a0000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002a0000 (I/O error)
mtd: erase failure at 0x002a0000 (I/O error)
mtd: skipping write block at 0x002a0000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00320000 (I/O error)
mtd: erase failure at 0x00320000 (I/O error)
mtd: skipping write block at 0x00320000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00360000 (I/O error)
mtd: erase failure at 0x00360000 (I/O error)
mtd: skipping write block at 0x00360000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003a0000 (I/O error)
mtd: erase failure at 0x003a0000 (I/O error)
mtd: skipping write block at 0x003a0000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x003e0000 (I/O error)
mtd: erase failure at 0x003e0000 (I/O error)
mtd: skipping write block at 0x003e0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004a0000 (I/O error)
mtd: erase failure at 0x004a0000 (I/O error)
mtd: skipping write block at 0x004a0000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device
#
1) Does your phone have the latest update?
2) What root method did you use?
3) Have you unlocked NAND?
The devil is in the details
+1 doesn't look like you have done part 2 to unlock nand.
Sent from my EVO from atop Candy Mountain....Charlie.
Something similar happened to me and it was because I used the wrong pcimg during part 2 of root. I accidentally used the first pcimg instead if the engineering build so when I went to flash a recovery it gave me a similar error
lostinroot:) said:
+1 doesn't look like you have done part 2 to unlock nand.
Click to expand...
Click to collapse
+1
I completely agree.
elegantai said:
Something similar happened to me and it was because I used the wrong pcimg during part 2 of root. I accidentally used the first pcimg instead if the engineering build so when I went to flash a recovery it gave me a similar error
Click to expand...
Click to collapse
I believe doing that would mean NAND won't be unlocked
I found a thread that says to use Rom manager and select "flash alternate recovery." The problem is, its grayed out. I have the recovery-RA-evo-v1.7.0.1.img file on the root of my SD card. I also tried putting it in the /mnt/sdcard/clockworkmod directory. It still wont let me flash it.
I'm pretty new to android, so any help would be greatly appreciated.
In Rom Manager, press "Flash ClockworkMod Recovery". (Yes you do have it flashed for Clockwork, but let it do its thing.
Then after that installs, scroll to bottom and "Flash Alternate Recovery" should be lit and under it, it should say "RA Recovery v1.7.0.1"
Hope this helps!
That did it. Thank you sir!
I flashed the recovery image from ROM manager and it said it was sucessful, but when I hold down the down volume button, and select recovery, it boots into clockworkmod still. Any suggestions?
I just tried installing amon ra from the guide on his page here http://forum.xda-developers.com/showthread.php?t=705026
I used Terminal Emulator. Here is the output
$ export PATH=/data/local/bin:$PATH
$su
# flash_image recovery /sdcard/recovery-RA-evo-v1.7.0.1.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000a0000 (I/O error)
mtd: erase failure at 0x000a0000 (I/O error)
mtd: skipping write block at 0x000a0000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x000e0000 (I/O error)
mtd: erase failure at 0x000e0000 (I/O error)
mtd: skipping write block at 0x000e0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00160000 (I/O error)
mtd: erase failure at 0x00160000 (I/O error)
mtd: skipping write block at 0x00160000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001a0000 (I/O error)
mtd: erase failure at 0x001a0000 (I/O error)
mtd: skipping write block at 0x001a0000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002a0000 (I/O error)
mtd: erase failure at 0x002a0000 (I/O error)
mtd: skipping write block at 0x002a0000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00320000 (I/O error)
mtd: erase failure at 0x00320000 (I/O error)
mtd: skipping write block at 0x00320000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00360000 (I/O error)
mtd: erase failure at 0x00360000 (I/O error)
mtd: skipping write block at 0x00360000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003a0000 (I/O error)
mtd: erase failure at 0x003a0000 (I/O error)
mtd: skipping write block at 0x003a0000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x003e0000 (I/O error)
mtd: erase failure at 0x003e0000 (I/O error)
mtd: skipping write block at 0x003e0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004a0000 (I/O error)
mtd: erase failure at 0x004a0000 (I/O error)
mtd: skipping write block at 0x004a0000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device
#
Try flashing it via adb. Amon_RA's full instructions are located here : http://forum.xda-developers.com/showthread.php?t=705026&highlight=[recovery]
In ROM Manager, try to back up your current ROM, if it lets you, Amon didn't flash properly. I'd suggest reinstalling ROM Manager.
Are you fully rooted or did you use unrevoked method? If you did, do a proper root and unlock...unrevoked isn't all its cracked up to be, IMHO.
@ beatblaster I think our posts may have crossed. I tried that
oRAirwolf said:
@ beatblaster I think our posts may have crossed. I tried that
Click to expand...
Click to collapse
I think our posts crossed too. I'm with booyakasha on his thinking..... oRAirwolf, what method did you use to root? That should help clear a few things up.
I did the simple root process. First I used the Simpleroot OTA to downgrade and then used the regular Simple Root to root it.
phantomevo77 said:
In Rom Manager, press "Flash ClockworkMod Recovery". (Yes you do have it flashed for Clockwork, but let it do its thing.
Then after that installs, scroll to bottom and "Flash Alternate Recovery" should be lit and under it, it should say "RA Recovery v1.7.0.1"
Hope this helps!
Click to expand...
Click to collapse
Thanks, I have been asking this in other forums and got no reponce. Thanks!
I originally used simple root to install clockworkmod recovery instead of RA. Can I simply re-run it and choose RA this time?
Thanks
edit: All Praise be to Ra
I deleted and reinstalled ROM manager. I clicked flash clockworkmod recovery. It completed successfully. It then said that current and latest recovery are clockworkmod 2.5.0.1. Then I clicked flash alternate recovery. It completed successfully and now says "current recovery: RA Recovery v1.7.0.1"
Now when I boot into recovery, its STILL clockwork!
*pounds head on desk*
oRAirwolf said:
I deleted and reinstalled ROM manager. I clicked flash clockworkmod recovery. It completed successfully. It then said that current and latest recovery are clockworkmod 2.5.0.1. Then I clicked flash alternate recovery. It completed successfully and now says "current recovery: RA Recovery v1.7.0.1"
Now when I boot into recovery, its STILL clockwork!
*pounds head on desk*
Click to expand...
Click to collapse
Not that you want to hear this, but I did the steps outlined above and I successfuly overwrote my simpleroot created clockworkmod recovery (although I think my cwm recovery was at 2.0.x
Good luck
Why do the Android gods hate me?
volwrath said:
edit: All Praise be to Ra
Click to expand...
Click to collapse
You're a nut... bwahahahh
oRAirwolf said:
I deleted and reinstalled ROM manager. I clicked flash clockworkmod recovery. It completed successfully. It then said that current and latest recovery are clockworkmod 2.5.0.1. Then I clicked flash alternate recovery. It completed successfully and now says "current recovery: RA Recovery v1.7.0.1"
Now when I boot into recovery, its STILL clockwork!
*pounds head on desk*
Click to expand...
Click to collapse
Damn dude, I'm stumped. Are you rebooting into recovery from ROM manager or vol down + power?
vol down + power
phantomevo77 said:
In Rom Manager, press "Flash ClockworkMod Recovery". (Yes you do have it flashed for Clockwork, but let it do its thing.
Then after that installs, scroll to bottom and "Flash Alternate Recovery" should be lit and under it, it should say "RA Recovery v1.7.0.1"
Hope this helps!
Click to expand...
Click to collapse
Thanks for the tip.....but after doiing the "Flash ClockworkMod Recovery" the "Flash Alternate Recovery" option is greyed out, and can't be used
I'm using the Pinky Desire 1.8 custom ROM
phantomevo77 said:
In Rom Manager, press "Flash ClockworkMod Recovery". (Yes you do have it flashed for Clockwork, but let it do its thing.
Then after that installs, scroll to bottom and "Flash Alternate Recovery" should be lit and under it, it should say "RA Recovery v1.7.0.1"
Hope this helps!
Click to expand...
Click to collapse
Awesome, it worked for me. I'm in Ra v1.8.0. thx
Hi,
I'm trying to roll my own boot image to install on my rooted htc desire running TMOD/froyo 2.2, I used the guide "HOWTO: Unpack, Edit, and Re-Pack Boot Images" at android-dls.com using the correct base address ( 0x20000000 ) passed to mkbootimg. This all goes fine but every time i try flash the image i just rolled i get this;
Code:
sh-3.2# flash_image boot boot-new-2.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000a0000 (I/O error)
mtd: erase failure at 0x000a0000 (I/O error)
mtd: skipping write block at 0x000a0000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x000e0000 (I/O error)
mtd: erase failure at 0x000e0000 (I/O error)
mtd: skipping write block at 0x000e0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00160000 (I/O error)
mtd: erase failure at 0x00160000 (I/O error)
mtd: skipping write block at 0x00160000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001a0000 (I/O error)
mtd: erase failure at 0x001a0000 (I/O error)
mtd: skipping write block at 0x001a0000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
error writing boot: No space left on device
sh-3.2# flash_image
What am i doing wrong?
Side note: flashing the extract of /dev/block/mtd2 back to mtd2 works perfectly, i just dont understand.
Correct me if I'm wrong, but you can't directly write boot images to the Desire.
Not entirely sure, but that is my understanding
acolwill said:
Correct me if I'm wrong, but you can't directly write boot images to the Desire.
Not entirely sure, but that is my understanding
Click to expand...
Click to collapse
You're right, you'll have to flash it via recovery ...
*I bought the pro version of twidroyd
*Bit later noticed some big battery drain
*Rebooted
*Had a ton of process.acore FCs
*Uninstalled twidroyd
*Continued to have issues
*Cache/dalvik wipe
*Issues remained
*Attempted nand restore to one I made earlier today
*Had error "Error: run 'nandroid-mobile.sh restore' via adb"
*Phone rebooted and would not go past the splash screen...20+ minutes
*Reboot into recovery, factory wipe
*Phone not going past splash screen
*Tried another nand restore with one I made last week....failed with previous error
*Phone not going past splash screen
*Tried restoring with my oldest nand...the one I made after the 'starting over' method from a couple months ago. After about 15 minutes (and 10 lines of "..............") it finally finished and rebooted
*Phone not going past splash screen
*Battery pull
seems like this thread may hold a clue: http://forum.xda-developers.com/showthread.php?t=608400
well i dont know if its a problem with the sd card. i put the latest nand on a different sd card, popped it in and still giving me the "Error: run 'nandroid-mobile.sh restore via adb" msg and wont boot up past splash screen
Are you using clockwork? If so you need to do the wipes through adb since clockwork does not work the greatest. I prefer RA recovery.
Personally I would just wipe the data and reflash my rom. I always have my apps backed up with Titanium, not sure if you do or not.
using RA
wiped data multiple times and tried reflashing rom, nothin doin
im going to try the full starting over method with the pc136 img in the bootloader now
Okay, huge progress.
I did the Starting Over method: http://forum.xda-developers.com/showthread.php?t=715915
Phone booted, never thought I'd be so damn happy to see that sprint bootscreen.
However: Rebooted back into recovery, attempted nand restore again, and got the adb error. I noticed though that the phone has RA version 1.7.0.1 which I think is outdated. Also noticed my radio was 2.05.00.06.10 which i know is outdated so my wimax radio is probably as well.
Now attempting to re-flash Fresh3.3 and going from there.
I have cross-posted this thread over to androidforums.com for those tuning in. link
Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.
Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.
_MetalHead_ said:
Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.
Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.
Click to expand...
Click to collapse
yea i did, the starting over method i linked is based on the 1.47.651.1 RUU. Its old, but it got the phone booted.
I might have to try that one.
I flashed 3.3, rebooted and im back stuck on the bootscreen for 15 minutes so far. 5 more minutes of this and I'm going to try a battery pull because one time that worked for me after a hangup trying to flash a new ROM
ah crap, know what? i forgot to full wipe before flashing 3.3. dammit.
Not sure if this pertains to you but I got this error run 'nandroid-mobile.sh restore' via adb" when I tried to do a nand restore and my battery was low
playya said:
Not sure if this pertains to you but I got this error run 'nandroid-mobile.sh restore' via adb" when I tried to do a nand restore and my battery was low
Click to expand...
Click to collapse
in the big battery drain i mentioned in the OP, it brought me down to 10%. I powered down, popped in a battery with a good charge and booted up. I dont remember whether I wiped cache/dalvik as i booted up the first time with the good battery or not, or whether that matters
_MetalHead_ said:
Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.
Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.
Click to expand...
Click to collapse
whoa whoa whoa...was i really supposed to flash this, or do it through the bootloader? I just did it through the bootloader, and after it was done and i loaded into clockwork and selected reboot system...it reboots, splash screen, back into clockwork with E: Invalid command argument.
Here's where im at:
Used bootloader to install the PC36IMG Metalhead suggested
Phone wouldnt boot despite multiple restarts, took me right back to clockwork
Tried flashing fresh3.3, but reboots still took me right back to clockwork
Decided to try and flash PC36IMG
Phone booted up into fresh 3.3.
Wow.
Last step of the puzzle is to get back to RA recovery and restore my nand. I grabbed ROM manager from the market and it says I have RA already, but when I boot into recovery its clockwork. Lil confused about that, I can't restore till I get RA back.
ROM Mgr said clockwork wasnt even installed when I opened it, just said I had RA. But when I reboot into recovery, it still brings me to clockwork. I tried flashing clockwork so ROM Mgr would recognize it had it, then re-flashed RA over it and rebooted into recovery, but still bringing me to clockwork. I tried using the QuickBoot app from the market to reboot into recovery, still clockwork. Just need to get RA back and not sure how.
sigh...tried to flash RA manually via fastboot, per this thread: http://forum.xda-developers.com/showthread.php?t=705026
this is what happened.
c:\sdk\tools>fastboot flash recovery recoveryRA1.8.img
sending 'recovery' (3750 KB)... OKAY [ 1.069s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.582s
Click to expand...
Click to collapse
cabbieBot said:
whoa whoa whoa...was i really supposed to flash this, or do it through the bootloader? I just did it through the bootloader, and after it was done and i loaded into clockwork and selected reboot system...it reboots, splash screen, back into clockwork with E: Invalid command argument.
Click to expand...
Click to collapse
You did it right, it's supposed to be done through the bootloader. I don't know why you're continuing to have issues. Are you currently still able to boot into a ROM?
Per the thread for Amon_RA, it looks like the commands you entered for fastboot were incorrect. That could be why you got that error.
i changed the filename but ill try redownloading and leaving it exactly as is
tried both the fastboot and terminal method and i still cant get off clockwork. im stumped.
I'm just tried this method and got the result quoted after:
1. Boot your phone into recovery mode
2. Plug your phone into your PC
3. Open cmd on PC and change directory to your androidsdk/tools folder
4. Run the following command(s):
adb shell
$su (not required if you have root already)
#mount -a (You might get some error messages, ignore it, keep going)
#flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img
reboot recovery
Click to expand...
Click to collapse
C:\sdk\tools>adb shell
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
~ # flash_image recovery /sdcard/ra18.img
flash_image recovery /sdcard/ra18.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000a0000 (I/O error)
mtd: erase failure at 0x000a0000 (I/O error)
mtd: skipping write block at 0x000a0000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x000e0000 (I/O error)
mtd: erase failure at 0x000e0000 (I/O error)
mtd: skipping write block at 0x000e0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00160000 (I/O error)
mtd: erase failure at 0x00160000 (I/O error)
mtd: skipping write block at 0x00160000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001a0000 (I/O error)
mtd: erase failure at 0x001a0000 (I/O error)
mtd: skipping write block at 0x001a0000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002a0000 (I/O error)
mtd: erase failure at 0x002a0000 (I/O error)
mtd: skipping write block at 0x002a0000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00320000 (I/O error)
mtd: erase failure at 0x00320000 (I/O error)
mtd: skipping write block at 0x00320000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00360000 (I/O error)
mtd: erase failure at 0x00360000 (I/O error)
mtd: skipping write block at 0x00360000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003a0000 (I/O error)
mtd: erase failure at 0x003a0000 (I/O error)
mtd: skipping write block at 0x003a0000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x003e0000 (I/O error)
mtd: erase failure at 0x003e0000 (I/O error)
mtd: skipping write block at 0x003e0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
error writing recovery: No space left on device
~ # reboot recovery
reboot recovery
/sbin/sh: reboot: not found
~ #
Click to expand...
Click to collapse
im wondering if the flash_image file is in the wrong place. I flashed this rom before fresh 3.3: http://forum.xda-developers.com/showthread.php?t=791019
A search using root explorer for 'flash_image' revealed two results:
/data/data/com.koushikdutta.rommanager/files/flash_image
/system/xbin/flash_image
hmmm...?
sonofa....
i took a look in the bootloader and I have S-ON. No wonder this is giving me crap. now i got to figure that out how to turn it back off then try this again. Lost my engineering bootloader, it seems ;( My fault for not reading enough
ive never used unrevoked, but is it possible for me to use unrevoked forever to turn S-OFF even though i never use unrevoked3
I cannot root my Incredible. I keep getting the Backup CID Missing in unrEVOked.
So I tried do following this guide to fix it. And resulted in this error.
Code:
# ./flash_image misc misc-inc.img
./flash_image misc misc-inc.img
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00000000
error writing misc: No space left on device
After, if I do a "cat /dev/mtd/mtd0". It is totally blank. A good one should show something like this:
Code:
VZW__001..........
..............
DeviceWarmBoot..
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
CE Serial InUse.
Debug Cable Ena.
CE USB InUse.................
ClearAutoImage..
3.26.605.1......
Any ideas how to fix this?
Anyone ...?