Related
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
so i thought i figured out what i needed to do to root my evo, and tried using Autoroot 2.3. This didn't work so well for me, and while i'm sure my questions are answered elsewhere, i can't for the life of me find them.
i ran autoroot, it did stuff, got to some point where it made a nandroid backup (i think), but never got past a red triangle with an exclamation point icon. right now i cannot boot into android. i can only get into the bootloader (s-on) and i have no idea what to do. here is my log if you care to see where i am.
so my question is, what is my next step!?
Code:
------------ AutoRoot.bat Begin - v2.3 - Sun 02/20/2011 22:28:22.74 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Ariel\Desktop\autoroot\'
Phone SN is HT12BHL03279
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD data being saved for phone 'HT12BHL03279'
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1: 00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3: 00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5: 0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" '
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 85 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1394 KB/s (767044 bytes in 0.537s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'shell'
Restart ADB Server...
Checking for root...
UID is 'Got Root!'
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='rageit'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1125 KB/s (76044 bytes in 0.066s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1772 KB/s (655360 bytes in 0.361s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1399 KB/s (225014 bytes in 0.157s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1720 KB/s (225551 bytes in 0.128s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
rm failed for -f, Read-only file system
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1490 KB/s (179274182 bytes in 117.454s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot' expected 'recovery'
PING ADB State Changed '450' out of '1250'. ADB State is 'disconnected' expected 'recovery'
PING ADB State Changed '454' out of '1250'. ADB State is 'daemon' expected 'recovery'
------------ AutoRoot.bat Begin - v2.3 - Sun 02/20/2011 23:16:31.26 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Ariel\Desktop\autoroot\'
Phone SN is HT12BHL03279
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'recovery' expected 'device'
Checking for ADB...
PLEN='1' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
Found the phone connected as 'recovery'.
Found the Recovery, proceeding to makenandroid...
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='makenandroid' STEP='recoveryboot'
Pushing amon_ra_1.8-mod to /...
push: amon_ra_1.8-mod/etc/mtab -> /etc/mtab
push: amon_ra_1.8-mod/etc/fstab -> /etc/fstab
push: amon_ra_1.8-mod/res/images/progress_bar_right_round.png -> /res/images/progress_bar_right_round.png
push: amon_ra_1.8-mod/res/images/progress_bar_left_round.png -> /res/images/progress_bar_left_round.png
push: amon_ra_1.8-mod/res/images/progress_bar_fill.png -> /res/images/progress_bar_fill.png
push: amon_ra_1.8-mod/res/images/progress_bar_empty_right_round.png -> /res/images/progress_bar_empty_right_round.png
push: amon_ra_1.8-mod/res/images/progress_bar_empty_left_round.png -> /res/images/progress_bar_empty_left_round.png
push: amon_ra_1.8-mod/res/images/progress_bar_empty.png -> /res/images/progress_bar_empty.png
push: amon_ra_1.8-mod/res/images/indeterminate6.png -> /res/images/indeterminate6.png
push: amon_ra_1.8-mod/res/images/indeterminate5.png -> /res/images/indeterminate5.png
push: amon_ra_1.8-mod/res/images/indeterminate4.png -> /res/images/indeterminate4.png
push: amon_ra_1.8-mod/res/images/indeterminate3.png -> /res/images/indeterminate3.png
push: amon_ra_1.8-mod/res/images/indeterminate2.png -> /res/images/indeterminate2.png
push: amon_ra_1.8-mod/res/images/indeterminate1.png -> /res/images/indeterminate1.png
push: amon_ra_1.8-mod/res/images/icon_install_corrupt.png -> /res/images/icon_install_corrupt.png
push: amon_ra_1.8-mod/res/images/icon_installing.png -> /res/images/icon_installing.png
push: amon_ra_1.8-mod/res/images/icon_firmware_install.png -> /res/images/icon_firmware_install.png
push: amon_ra_1.8-mod/res/images/icon_firmware_error.png -> /res/images/icon_firmware_error.png
push: amon_ra_1.8-mod/res/images/icon_error.png -> /res/images/icon_error.png
push: amon_ra_1.8-mod/res/keys -> /res/keys
push: amon_ra_1.8-mod/sbin/wipe -> /sbin/wipe
push: amon_ra_1.8-mod/sbin/unyaffs -> /sbin/unyaffs
push: amon_ra_1.8-mod/sbin/ums_toggle -> /sbin/ums_toggle
push: amon_ra_1.8-mod/sbin/um -> /sbin/um
push: amon_ra_1.8-mod/sbin/tune2fs -> /sbin/tune2fs
push: amon_ra_1.8-mod/sbin/sdparted -> /sbin/sdparted
push: amon_ra_1.8-mod/sbin/recovery -> /sbin/recovery
push: amon_ra_1.8-mod/sbin/reboot -> /sbin/reboot
push: amon_ra_1.8-mod/sbin/parted -> /sbin/parted
push: amon_ra_1.8-mod/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh
push: amon_ra_1.8-mod/sbin/mkyaffs2image -> /sbin/mkyaffs2image
push: amon_ra_1.8-mod/sbin/mke2fs -> /sbin/mke2fs
push: amon_ra_1.8-mod/sbin/log2sd -> /sbin/log2sd
push: amon_ra_1.8-mod/sbin/fs -> /sbin/fs
push: amon_ra_1.8-mod/sbin/flash_image -> /sbin/flash_image
push: amon_ra_1.8-mod/sbin/fix_permissions -> /sbin/fix_permissions
push: amon_ra_1.8-mod/sbin/e2fsck -> /sbin/e2fsck
push: amon_ra_1.8-mod/sbin/dump_image -> /sbin/dump_image
push: amon_ra_1.8-mod/sbin/busybox -> /sbin/busybox
push: amon_ra_1.8-mod/sbin/backuptool.sh -> /sbin/backuptool.sh
push: amon_ra_1.8-mod/sbin/adbd -> /sbin/adbd
push: amon_ra_1.8-mod/system/bin/sh -> /system/bin/sh
push: amon_ra_1.8-mod/system/bin/linker -> /system/bin/linker
push: amon_ra_1.8-mod/system/lib/libstdc++.so -> /system/lib/libstdc++.so
push: amon_ra_1.8-mod/system/lib/libm.so -> /system/lib/libm.so
push: amon_ra_1.8-mod/system/lib/liblog.so -> /system/lib/liblog.so
push: amon_ra_1.8-mod/system/lib/libcutils.so -> /system/lib/libcutils.so
push: amon_ra_1.8-mod/system/lib/libc.so -> /system/lib/libc.so
48 files pushed. 0 files skipped.
1122 KB/s (3721687 bytes in 3.238s)
sync: not found
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='makenandroid' STEP='makenandroid'
Recovery type is 'stock'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"
'check.bat mtd' returned 'bad'
WARNING MTD does not match info from INI file!
'dev: size erasesize name mtd0: 00600000 00020000 "wimax" mtd1: 00080000 00020000 "misc" mtd2: 00240000 00020000 "recovery" mtd3: 001a0000 00020000 "boot" mtd4: 0af00000 00020000 "system" mtd5: 05000000 00020000 "cache" mtd6: 0d500000 00020000 "userdata" ' mtdINIinfo
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1: 00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3: 00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5: 0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" ' mtdINIdump
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='makenandroid' STEP='makenandroid'
Recovery type is 'stock'
Retrieving MTD data..
dev: size erasesize name
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 9 hard) at 0x00120000
mtd: ECC errors (0 soft, 9 hard) at 0x00140000
mtd: ECC errors (0 soft, 9 hard) at 0x00160000
mtd: ECC errors (0 soft, 9 hard) at 0x00180000
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 9 hard) at 0x00120000
mtd: ECC errors (0 soft, 9 hard) at 0x00140000
mtd: ECC errors (0 soft, 9 hard) at 0x00160000
mtd: ECC errors (0 soft, 9 hard) at 0x00180000
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 10 hard) at 0x00120000
mtd: ECC errors (0 soft, 11 hard) at 0x00140000
mtd: ECC errors (0 soft, 12 hard) at 0x00160000
mtd: ECC errors (0 soft, 13 hard) at 0x00180000
mtd: ECC errors (0 soft, 14 hard) at 0x001a0000
mtd: ECC errors (0 soft, 14 hard) at 0x001c0000
mtd: ECC errors (0 soft, 14 hard) at 0x001e0000
mtd: ECC errors (0 soft, 14 hard) at 0x00200000
mtd: ECC errors (0 soft, 14 hard) at 0x00220000
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 10 hard) at 0x00120000
mtd: ECC errors (0 soft, 11 hard) at 0x00140000
mtd: ECC errors (0 soft, 12 hard) at 0x00160000
mtd: ECC errors (0 soft, 13 hard) at 0x00180000
mtd: ECC errors (0 soft, 14 hard) at 0x001a0000
mtd: ECC errors (0 soft, 14 hard) at 0x001c0000
mtd: ECC errors (0 soft, 14 hard) at 0x001e0000
mtd: ECC errors (0 soft, 14 hard) at 0x00200000
mtd: ECC errors (0 soft, 14 hard) at 0x00220000
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 10 hard) at 0x00120000
mtd: ECC errors (0 soft, 11 hard) at 0x00140000
mtd: ECC errors (0 soft, 12 hard) at 0x00160000
mtd: ECC errors (0 soft, 13 hard) at 0x00180000
mtd: ECC errors (0 soft, 14 hard) at 0x001a0000
mtd: ECC errors (0 soft, 15 hard) at 0x001c0000
mtd: ECC errors (0 soft, 16 hard) at 0x001e0000
mtd: ECC errors (0 soft, 17 hard) at 0x00200000
mtd: ECC errors (0 soft, 18 hard) at 0x00220000
mtd: ECC errors (0 soft, 19 hard) at 0x00240000
mtd: ECC errors (0 soft, 20 hard) at 0x00260000
mtd: ECC errors (0 soft, 21 hard) at 0x00280000
mtd: ECC errors (0 soft, 22 hard) at 0x002a0000
mtd: ECC errors (0 soft, 23 hard) at 0x002c0000
mtd: ECC errors (0 soft, 24 hard) at 0x002e0000
mtd: ECC errors (0 soft, 25 hard) at 0x00300000
mtd: ECC errors (0 soft, 26 hard) at 0x00320000
mtd: ECC errors (0 soft, 27 hard) at 0x00340000
mtd: ECC errors (0 soft, 28 hard) at 0x00360000
mtd: ECC errors (0 soft, 29 hard) at 0x00380000
mtd: ECC errors (0 soft, 30 hard) at 0x003a0000
mtd: ECC errors (0 soft, 31 hard) at 0x003c0000
mtd: ECC errors (0 soft, 31 hard) at 0x003e0000
mtd: ECC errors (0 soft, 32 hard) at 0x00400000
mtd: ECC errors (0 soft, 33 hard) at 0x00420000
mtd: ECC errors (0 soft, 34 hard) at 0x00440000
mtd: ECC errors (0 soft, 34 hard) at 0x00460000
mtd: ECC errors (0 soft, 34 hard) at 0x00480000
mtd: ECC errors (0 soft, 34 hard) at 0x004a0000
mtd: ECC errors (0 soft, 34 hard) at 0x004c0000
mtd: ECC errors (0 soft, 34 hard) at 0x004e0000
mtd: ECC errors (0 soft, 34 hard) at 0x00500000
mtd: ECC errors (0 soft, 34 hard) at 0x00520000
mtd: ECC errors (0 soft, 34 hard) at 0x00540000
mtd: ECC errors (0 soft, 34 hard) at 0x00560000
mtd: ECC errors (0 soft, 34 hard) at 0x00580000
mtd: ECC errors (0 soft, 34 hard) at 0x005a0000
mtd: ECC errors (0 soft, 34 hard) at 0x005c0000
mtd: ECC errors (0 soft, 34 hard) at 0x005e0000
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 2 hard) at 0x00020000
mtd: ECC errors (0 soft, 3 hard) at 0x00040000
mtd: ECC errors (0 soft, 4 hard) at 0x00060000
mtd: ECC errors (0 soft, 5 hard) at 0x00080000
mtd: ECC errors (0 soft, 6 hard) at 0x000a0000
mtd: ECC errors (0 soft, 7 hard) at 0x000c0000
mtd: ECC errors (0 soft, 8 hard) at 0x000e0000
mtd: ECC errors (0 soft, 9 hard) at 0x00100000
mtd: ECC errors (0 soft, 10 hard) at 0x00120000
mtd: ECC errors (0 soft, 11 hard) at 0x00140000
mtd: ECC errors (0 soft, 12 hard) at 0x00160000
mtd: ECC errors (0 soft, 13 hard) at 0x00180000
mtd: ECC errors (0 soft, 14 hard) at 0x001a0000
mtd: ECC errors (0 soft, 15 hard) at 0x001c0000
mtd: ECC errors (0 soft, 16 hard) at 0x001e0000
mtd: ECC errors (0 soft, 17 hard) at 0x00200000
mtd: ECC errors (0 soft, 18 hard) at 0x00220000
mtd: ECC errors (0 soft, 19 hard) at 0x00240000
mtd: ECC errors (0 soft, 20 hard) at 0x00260000
mtd: ECC errors (0 soft, 21 hard) at 0x00280000
mtd: ECC errors (0 soft, 22 hard) at 0x002a0000
mtd: ECC errors (0 soft, 23 hard) at 0x002c0000
mtd: ECC errors (0 soft, 24 hard) at 0x002e0000
mtd: ECC errors (0 soft, 25 hard) at 0x00300000
mtd: ECC errors (0 soft, 26 hard) at 0x00320000
mtd: ECC errors (0 soft, 27 hard) at 0x00340000
mtd: ECC errors (0 soft, 28 hard) at 0x00360000
mtd: ECC errors (0 soft, 29 hard) at 0x00380000
mtd: ECC errors (0 soft, 30 hard) at 0x003a0000
mtd: ECC errors (0 soft, 31 hard) at 0x003c0000
mtd: ECC errors (0 soft, 31 hard) at 0x003e0000
mtd: ECC errors (0 soft, 32 hard) at 0x00400000
mtd: ECC errors (0 soft, 33 hard) at 0x00420000
mtd: ECC errors (0 soft, 34 hard) at 0x00440000
mtd: ECC errors (0 soft, 34 hard) at 0x00460000
mtd: ECC errors (0 soft, 34 hard) at 0x00480000
mtd: ECC errors (0 soft, 34 hard) at 0x004a0000
mtd: ECC errors (0 soft, 34 hard) at 0x004c0000
mtd: ECC errors (0 soft, 34 hard) at 0x004e0000
mtd: ECC errors (0 soft, 34 hard) at 0x00500000
mtd: ECC errors (0 soft, 34 hard) at 0x00520000
mtd: ECC errors (0 soft, 34 hard) at 0x00540000
mtd: ECC errors (0 soft, 34 hard) at 0x00560000
mtd: ECC errors (0 soft, 34 hard) at 0x00580000
mtd: ECC errors (0 soft, 34 hard) at 0x005a0000
mtd: ECC errors (0 soft, 34 hard) at 0x005c0000
mtd: ECC errors (0 soft, 34 hard) at 0x005e0000
---------RECOVERY LOG DUMP BEGIN---------
nandroid-mobile v2.2.1
Using G1 keyboard, enter a prefix substring and then <CR>
Accepting default.
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
done
done
done
done
done
done
done
done
done
done
unmounting system, data and sdcard
Backup successful.
----------RECOVERY LOG DUMP END----------
ROM showing hBoot version '-'
Version Major '-'
Version Minor ''
WARNING Did not recognize hBoot version!
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
-------RECOVERY COMMAND DUMP BEGIN-------
- exec '/system/bin/sh' failed: No such file or directory (2) -
--------RECOVERY COMMAND DUMP END--------
- exec '/system/bin/sh' failed: No such file or directory (2) -
Checking for ADB...
PLEN='40' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflash'
Phone rebooted into recovery mode. Waiting on it to reboot again...
ERROR Timed out while waiting on the phone to reboot.
PING ADB Counter '181' out of '180'. ADB State is 'na' expected 'recovery'
Passed to ERRHANDLER
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='b2bootloader' STEP='autoflash2'
PING ADB State Changed '1' out of '0'. ADB State is 'recovery' expected 'recovery'
Attempting to dump the recovery log.
---------RECOVERY LOG DUMP BEGIN---------
- exec '/system/bin/sh' failed: No such file or directory (2) -
----------RECOVERY LOG DUMP END----------
Killing ADB server...
------------ AutoRoot.bat End ------------
You had a bad flash, you'll need to run the RUU to get a clean install and try again.
http://www.multiupload.com/MU_W679R1W391 - 3.70.651.1 RUU
If you wanted to add (CODE] (/CODE] before and after the log helps make it a little easier to read Just change the ( to a [
Also, you can always attach the file in a zip if you want. Also, after you run the RUU, I reccomend running unrevoked rather than autoroot.
ok im trying to do the RUU thing now, but how do i get the evo to go into usb mode? all i can get into is the bootloader with s-on
Once in the bootloader, use the vol keys to highlight fastboot, then press the power button to select it, then run the RUU exe.
also, about revoked, will that fully backup the wimax key and all that?
Well it won't change them, so you'll be good.
http://forum.xda-developers.com/showthread.php?t=887900
You can do that just to be extra safe. Put it somewhere safe on your computer.
Unrevoked won't break your RSA keys. I just rooted using Unrevoked a week ago and I've had no problems at all.
Unrevoked will flash clockwork recovery, but it is easy to flash RA recovery if you prefer it.
Running Unrevoked will not automatically perform a nand backup, you will want to manually do that afterwards. But both clockwork and RA will backup the wimax.img file
HTC Evo
Rooted, but still stock...for now
----------------------------------------
The program is designed to work, if it's not, we have a problem.
+1
use the unrevoked. just 2 easy steps. instal the usb drivers. plug the phone to pc vea usb, run unrevoked reflash app, kick back and enjoy
Hi,
After typing this command:
Code:
flash_image recovery recovery.img
I got this:
Code:
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00000000
So, what's this block? I mean is it some mount point or bootloader stuffs? According to feedback by terminal it seems like recovery's dead, but it successfully flashed it. How to fix?