OK, I have been running recovery-RA-1.5.2 for some time now and I'm using Fresh 1.1. I was trying to update my recovery to 1.6.2 and when I went to flash the recovery it gave me a bunch of errors and now I can't get into recovery at all. My phone boots fine into fresh but I get nothing when I try to boot into recovery either using home+power or adb. I have tried re-flashing the recovery and I even went back and followed the rooting guide from the beginning because I know that worked before. Nothing helped, I'm still getting the read errors. Going back to the old recovery is not working either, although it does show only 1 error instead of the many that 1.6.2 shows. Any ideas?
Here are the errors I got:
# flash_image recovery recovery-RA-heroc-v1.6.2-blue.img
flash_image recovery recovery-RA-heroc-v1.6.2-blue.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
mtd: read error at 0x00180000 (Out of memory)
mtd: read error at 0x001a0000 (Out of memory)
mtd: read error at 0x001c0000 (Out of memory)
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
mtd: read error at 0x00260000 (Out of memory)
mtd: read error at 0x00280000 (Out of memory)
mtd: read error at 0x002a0000 (Out of memory)
mtd: read error at 0x002c0000 (Out of memory)
mtd: read error at 0x002e0000 (Out of memory)
mtd: read error at 0x00300000 (Out of memory)
mtd: read error at 0x00320000 (Out of memory)
mtd: read error at 0x00340000 (Out of memory)
mtd: read error at 0x00360000 (Out of memory)
mtd: read error at 0x00380000 (Out of memory)
mtd: read error at 0x003a0000 (Out of memory)
mtd: read error at 0x003c0000 (Out of memory)
mtd: read error at 0x003e0000 (Out of memory)
mtd: read error at 0x00400000 (Out of memory)
mtd: read error at 0x00420000 (Out of memory)
mtd: read error at 0x00440000 (Out of memory)
mtd: read error at 0x00460000 (Out of memory)
mtd: read error at 0x00480000 (Out of memory)
mtd: read error at 0x004a0000 (Out of memory)
mtd: read error at 0x004c0000 (Out of memory)
mtd: read error at 0x004e0000 (Out of memory)
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
mtd: skipping write block at 0x00000000
mtd: write error at 0x00020000 (Out of memory)
mtd: re-read error at 0x00020000 (Out of memory)
mtd: write error at 0x00020000 (Out of memory)
mtd: re-read error at 0x00020000 (Out of memory)
mtd: skipping write block at 0x00020000
mtd: write error at 0x00040000 (Out of memory)
mtd: re-read error at 0x00040000 (Out of memory)
mtd: write error at 0x00040000 (Out of memory)
mtd: re-read error at 0x00040000 (Out of memory)
mtd: skipping write block at 0x00040000
mtd: write error at 0x00060000 (Out of memory)
mtd: re-read error at 0x00060000 (Out of memory)
mtd: write error at 0x00060000 (Out of memory)
mtd: re-read error at 0x00060000 (Out of memory)
mtd: skipping write block at 0x00060000
mtd: write error at 0x00080000 (Out of memory)
mtd: re-read error at 0x00080000 (Out of memory)
mtd: write error at 0x00080000 (Out of memory)
mtd: re-read error at 0x00080000 (Out of memory)
mtd: skipping write block at 0x00080000
mtd: write error at 0x000a0000 (Out of memory)
mtd: re-read error at 0x000a0000 (Out of memory)
mtd: write error at 0x000a0000 (Out of memory)
mtd: re-read error at 0x000a0000 (Out of memory)
mtd: skipping write block at 0x000a0000
mtd: write error at 0x000c0000 (Out of memory)
mtd: re-read error at 0x000c0000 (Out of memory)
mtd: write error at 0x000c0000 (Out of memory)
I remember when I first loaded the recovery image a long time ago that I got tons of errors, but the instructions said to ignore them.
I know, I am no help on this one.
there is always RUU, root, flash new image, load nandroid backup.
nothing is wrong. reboot and try again. Every now and then you get that error when flashing a recovery. hope you didn't wipe and RUU already.
Had the same issue as above, but mine wouldn't even get past the "htc" screen. Had to pull the battery, do an RUU then re-root using the 1.6.2.img
my advice would be to RUU and go back to "real" stock, then root again using the updated .img then load up your ROM again.
heck no DO NOT RUU as this WILL brick your phone. I had the same issue and tried to RUU. Your phone will be bricked. Just looks like you're going to be stuck using that rom for the rest of your phone life... You can take the risk if you want but don't say I didn't warn you.
~Danny
Bielinsk said:
there is always RUU, root, flash new image, load nandroid backup.
Click to expand...
Click to collapse
+1
10char
he can't even root, flash new image, or even nandroid as he is only able to turn on his phone and it goes straight to the actual android os .. it does not allow him to goto the ra. Like I said I had to return my phone because I tried RUU after this and it bricked.
~Danny
This happened to me today also. I downloaded better terminal and installed old recovery menu through terminal. It worked perfectly.
Try this:
adb shell reboot oem-78
Once the phone shows the HTC logo try this:
fastboot devices
Make sure your device is listed, then flash the recovery:
fastboot flash recovery recovery.img
recovery.img should be the latest recovery image.
i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this:
download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps.
try flashing it again. it should work.
justinisyoung said:
i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this:
download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps.
try flashing it again. it should work.
Click to expand...
Click to collapse
That's why you should reboot into oem-78 and use fastboot, so nothing else is running
justinisyoung said:
i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this:
download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps.
try flashing it again. it should work.
Click to expand...
Click to collapse
EDIT: THAT worked with the old 1.5.2 recovery!!!! Thank you so much!!! I don't know why my phone hated the 1.6.2 recovery. Maybe it just didn't want to be blue.
richse said:
This seemed to almost work. The flash finished without any errors but then when I try to boot into recovery it just sits on the HTC screen forever I tried doing the command "adb shell reboot oem-78" and it just returned a "1" and the phone didn't reboot. Any idea?
Click to expand...
Click to collapse
try this
Code:
adb shell
reboot recovery
try it without combining it all into one line, like adb shell reboot recovery. i found that that doesn't always work. so just separate it into two lines
justinisyoung said:
try this
Code:
adb shell
reboot recovery
try it without combining it all into one line, like adb shell reboot recovery. i found that that doesn't always work. so just separate it into two lines
Click to expand...
Click to collapse
It's back to v1.5.2 with the fix using the task manager. Just gonna have to figure out why 1.6.2 is failing now. Thanks!
I got 1.6.2 working using the one with out a color change. Maybe I just downloaded a bad copy of the blue one from the start. I guess this is how we learn. Thanks again for all the help guys!
i had this same issue, exactly... i did the fastboot flash and now im rocking the blue carebear...
Has anyone tried flashing with flashrec when it fails, a la the original recovery loading?
I got those errors on my first attempt at flashing the 1.6.2 recovery image so I just rebooted then used adb and reflashed the 1.5.2 recovery image, rebooted into recovery just fine and then when I was at the recovery screen I followed these instructions:
make sure the recovery image is already on your sd card.
Code:
Connect your Hero via usb to your pc/mac/... (while at the recovery screen)
adb shell
$su (not required if you have root already)
#mount -a (I got an error on this so just ignored it)
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
everything works great now
navalynt said:
Try this:
adb shell reboot oem-78
Once the phone shows the HTC logo try this:
fastboot devices
Make sure your device is listed, then flash the recovery:
fastboot flash recovery recovery.img
recovery.img should be the latest recovery image.
Click to expand...
Click to collapse
I'm new to this "forum" business, so I don't know how to do this officially... but you, sir, have my thanks. this information was solid.
out of curiosity, how'd you know that special mode to tell fastboot to load up?? as a developer I'm always interested in how people find information like this!
If you can Turn on your phone Normally, just Boot your phone... Then once its Turned on, Install Rom Manager and Flash a Recovery through that app! Then at the Bottom of the Rom Manager app you can Select Flash a Alternate Recovery!
That should Switch your Recovery back to Amon_RA! But if it Doesn't... You'll still be back up and Running with a Working Recovery!
GoodLuck!
Related
Trying to Root my first G1. Having some wierd issues.
Been searching the net for 2 days with no working solution.
Successfully downgraded to RC29, it says so in the settings.
Then working with freshly FAT32 formatted SDCARDs (of sizes 4gb, 1gb and 1/2gb), I attempted these two methods:
Method 1:
Clockwork's Telnet installed
From home screen i punch in <enter><enter>telnetd<enter>
Launch Telnet, connect to localhost:23
Telnet displays: ??[]??[]?? ??[]?? #
From there I type (with no errors): mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
## is now displayed. I CD into sdcard, LS the contents to confirm I'm there. Seems normal.
then...
## flash_image recovery cm-recovery-1.4.img
which returns this:
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000 <-----pauses here for a second, then again...
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
##
Method 2:
Recovery Flasher 1.1.3 installed (Previous versions of this APK come up as unsuccessful installations)
Note, the "Download Recovery Image" button is grayed from the begining.
I type the path/name of the recovery image on the sdcard (Tried both CM's image and RA's image)
The button changes from "Download Recovery Image" to "Flash Recovery Image" as soon as I finish typing the path.
However... The button remains gray and disabled. No explanation is given.
Also as a side note (in case it is relevant), when I hit Backup Recovery Image I get "working do not interrupt", then "Backup FAILED: Image is invalid.
This is all going a little outta my league and is getting real frustrating haha. Any help is reeaaally appreciated.
Bump. I can't be the only one with this problem, anyone?
Don't use the mount command when you telnet in. I haven't seen that on a rooting guide before, and it's definitely not part of Cyanogen's instructions.
As soon as you've opened the telnet connection, cd into the sdcard and run the flash_image command.
There's a link to Cyanogen's installation instructions in his ROM thread. Everything is explicitly spelled out, and easy to follow.
Downgrade Success!
We have a good procedure to allow a downgrade via RUU, which then allows you to use the other root methods again.
Big thanks to Joeball88 for putting in the testing time with me to get the bumps all smoothed out, and for caska who had the epiphany that we should goldcard it before RUUing.
THE SCRIPTS HAVE BEEN UPDATED MANY TIMES! Please be sure to re-download the new hack4legend-v5.zip before you start if you a returning root seeker.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
*updated files to hack4legend-v5.zip @ 7-19-2010 11:35AM Central*
Preliminary things to do.
Download -
hack4legend-v5.zip
RUU 1.31 for Legend
Make a goldcard, these instructions work, but you have to change mmc1 to mmc0
Another goldcard method if the first doesn't work for some reason.
Get the Android SDK (skip if you have a working adb)
Have adb in your path, or move the files contained in hack4legend-v5.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
crackin.sh
or in Windows
Code:
crackin.bat
Your phone will reboot 5 times.
You WILL see several error messages.
Look for this line, if the crwxrwxrwx matches you are ready to downgrade
Code:
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
if it looks like this c---rw----
Code:
c---rw---- 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
You're not.
Power cycle your phone.
If you have trouble, clearing your phone to factory defaults may help.
Put your goldcard in.
You can now downgrade to RUU 1.31, run the RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed.exe that you downloaded earlier.
After that you can follow the other root howto's for the Legend!
caska says this link is faster for the Legend root download.
If for any reason you want to put your old ROM id back in after you've ran crackin, but before you run RUU run uncrackin and it will reinstall your old ROM version number.
If you really love me and want to say thanks, donate some beer money.
(adb push ROM.zip /sdcard)
Sorry to bother,is the command above necesary ?
holy crap. trying this RIGHT NOW
acid74 said:
(adb push ROM.zip /sdcard)
Sorry to bother,is the command above necesary ?
Click to expand...
Click to collapse
It saves a reboot if you're planning on installing a custom ROM.
So technically no.
Joeball88 said:
holy crap. trying this RIGHT NOW
Click to expand...
Click to collapse
I already had to adjust the script. Be sure you use hack4legendv2.zip
wag3slav3 said:
I already had to adjust the script. Be sure you use hack4legendv2.zip
Click to expand...
Click to collapse
Done that ,not working.....
sorry not tried with hack4legend v2.....will update soon.
acid74 said:
Done that ,not working.....
Click to expand...
Click to collapse
Great! Keep me posted. As I said above, the method for this is on the device, so it "SHOULD" work.
with the V1, I get
"Your phone is now rebooting in Rooted Recovery mode...
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
..... etc....
error writing recovery: No space left on device
with the V2, I get:
c:\AndroidSDK\tools>runindos
1605 KB/s (3532800 bytes in 2.149s)
675 KB/s (76044 bytes in 0.110s)
Unable to chmod /sdcard/recovery.img: Operation not permitted
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
"Your phone is now rebooting in Rooted Recovery mode, do a backup and load your
ROMs"
error opening /sdcard/recovery.img: Permission denied
Joeball88 said:
with the V1, I get
"Your phone is now rebooting in Rooted Recovery mode...
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
error writing recovery: No space left on device
Click to expand...
Click to collapse
Damn, the recovery device is a different location. Did it ever say anything about mtd mmcblk? I'm unlocking the wrong location for the flasher. Gimme a few minutes to find out which partition it wants.
You can help me out by dropping to an adb shell and doing a mount and pasting the results.
Also, if anyone has a linux box and wouldn't mind giving me an ssh shell to a legend on adb it would speed it up a bit.
wag3slav3 said:
Great! Keep me posted. As I said above, the method for this is on the device, so it "SHOULD" work.
Click to expand...
Click to collapse
With v2 hack i get this on the end. (Dont know how to copy the whole log)
error opening\sdcard\recovery.img: permission denied
Got a very different error msg with V2.
ADB Shell Mount Below:
c:\AndroidSDK\tools>adb shell
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
Joeball88 said:
Got a very different error msg with V2.
ADB Shell Mount Below:
c:\AndroidSDK\tools>adb shell
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
Click to expand...
Click to collapse
can I get a dmesg too? If it's too long, pastebin.com it.
I just wanna say to wag3slav3 thank you for trying to help all the forgotten Legend community!i'm following this closely as I'm returning home if you guys need assistance i'll be home in 30min.will do What i can to help
Sent from my HTC Legend using XDA App
I posted the dmesg on pastebin:
http://pastebin.com/erj7Wzcn
but my cmd window wouldn't scroll to the very very top, (wierd) so I hope this is all of it.
adb push recovery.img /sdcard/
-> OK
adb push flash_image /data/local/
-> OK
adb shell chmod 777 /sdcard/recovery.img
Unable to chmod /sdcard/recovery.img: Operation not permitted
Click to expand...
Click to collapse
adb shell chmod 777 /data/local/flash_image
-> OK
adb shell rm /data/local/rights/mid.txt
-> OK
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
-> OK
adb reboot
-> OK
adb wait-for-device
-> OK
adb shell /data/local/flash_image recovery /sdcard/recovery.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
error writing recovery: No space left on device
Click to expand...
Click to collapse
masterbalby said:
adb push recovery.img /sdcard/
-> OK
adb push flash_image /data/local/
-> OK
adb shell chmod 777 /sdcard/recovery.img
adb shell chmod 777 /data/local/flash_image
-> OK
adb shell rm /data/local/rights/mid.txt
-> OK
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
-> OK
adb reboot
-> OK
adb wait-for-device
-> OK
adb shell /data/local/flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Can you try running it again with ln -s /dev/mtd/mtd0?
wag3slav3 said:
Can you try running it again with ln -s /dev/mtd/mtd0?
Click to expand...
Click to collapse
after running the command and reboot, when I try 'adb shell /data/local/flash_image recovery /sdcard/recovery.img', error is
error writing recovery: Permission denied.
Get busybox, adb push it to /data/local and do a
/data/local/busybox ls -al /dev/mt* for me.
desiibond said:
after running the command and reboot, when I try 'adb shell /data/local/flash_image recovery /sdcard/recovery.img', error is
error writing recovery: Permission denied.
Click to expand...
Click to collapse
hey! what did I miss?! i'm here and ready for testing!
wag3slav3 said:
Get busybox, adb push it to /data/local and do a
/data/local/busybox ls -al /dev/mt* for me.
Click to expand...
Click to collapse
uh i get a permission denied. I used the adb shell, and the terminal emulator and both gave me permission denied. am I doin' it rite?
Hi,
I got a rogers dream and i tried several ways to root it, but i cannot so far:
1. follow wiki guide, but i cannot got into recovery mode by holding Home key while power on the phone, it hangs on at rogers screen.
2. try goldcard. cannot update, showing Model ID incorrect, failed. i am not sure it is because my card or something else.
3. i tried flashrc(?), it failed updating img.
4. i tried telnet. remote refused.
if you succeed rooting a rogers dream 1.33.0010, please tell me how.
thanks,
Follow this guide
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
thanks for your swift reply. that is the wiki i followed, but when i tried to install DangerSPL, i cannot go into recovery by holding HOME while power on the phone. it hangs at Rogers screen.
i checked radio and it is correct version. should i flash radio still?
any suggestion?
thanks,
Well you certainly need recovery..
The original steps for that process are here: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(as cm wiki sometimes is organized more for maintenance by people who don't use a rogers dream than being user friendly.. and they removed the link to the xda thread with all the q&a on the process)
the error however is either you are flashing the wrong recovery; or the flash of the recovery failed. make sure your flashing one of the '-R' ra-recoverys.
best to take it from the top.. if recovery still fails some people have found re-flashing the e911 rom and trying again helped (see 'Returning to Stock Rogers' on the xda wiki page)
still i cannot go into recovery.
can you tell me how long i have to hold HOME key in order to boot into recovery?
i push HOME and POWER together, and then i can only see ROGERS. it probably stays there forever.
one thing i cannot follow wiki before is LONG HOLD POWER TO TURN OFF PHONE.
thanks,
JaydenCanada said:
still i cannot go into recovery.
can you tell me how long i have to hold HOME key in order to boot into recovery?
i push HOME and POWER together, and then i can only see ROGERS. it probably stays there forever.
one thing i cannot follow wiki before is LONG HOLD POWER TO TURN OFF PHONE.
thanks,
Click to expand...
Click to collapse
If you can boot normally but not recovery (ie you are stuck on the rogers logo and it never changes when you boot holding down home) their is a problem with the recovery you flashed. (We will not move on from this statement unless we find why there is an issue with the recovery or that the incorrect recovery was flashed)
As for long press power or end on the phone that is how you get the shutdown menu in the rogers and other roms.. so I'm not sure what is wrong if that is failing outside user error.
I need you to do the following if you want help:
1) flash (as per the restore stock rogers rom on the xda wiki) the e911 patched rogers nbh file
2) making sure you document every command you run and saving the console output to a text file run the e911 rooting process as per xda wiki
3) if you can't boot recovery post said output here.. however first check it with the sample output
thanks for your patience.
when i say long press power button cannot power off the phone, i mean i cannot turn off the phone by only press it, i have to go through two more windows, one is power down options and another is confirmation.
i will follow the instructions again to see what happen. do you suggest any recovery image? or something else i can do ?
thanks
wait what. power down options?
I don't remember power down options on the stock rom
Sleeepy2 said:
wait what. power down options?
I don't remember power down options on the stock rom
Click to expand...
Click to collapse
Certainly had power off and airplane mode.. probably reboot as well but I forget.
JaydenCanada said:
i will follow the instructions again to see what happen. do you suggest any recovery image? or something else i can do ?
thanks
Click to expand...
Click to collapse
The recovery image with the md5 sum in the instructions is what most people use.
after i run exploid, i can see three files: hotplug, loading, and sim_lock_status were generated, as well rootshell in /system/bin.
i tried to go into recovery, but i cannot, because it hangs on ROGERS screen forever. i have to pull battery out to reboot. then i checked /sqlite_stmt_journals, exploid, loading, hotplug and sim_lock_status were all gone. there were two files there: screen_lock_status and pattern_lock_status.
i don't have sim card in the phone, can it cause the problem?
BTW: i even followed "how to root Droid" to install exploid, using chmod 755 and turn on/off wifi after running exploid.
any suggestion? thanks,
Please don't follow the droidx instructions, and follow the Rogers root instructions.. the root exploit is the same but the hardware and goal is different.
many others hard successfully rooted and some q/a on the process is in this thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638
You have not given the console output to your attempt so as I said earlier I have no additional recommendations than what I have already provided as we do not know what recovery you flashed.
i am very new to this thing. does "console out" mean the screen captures? i will supply tomorrow.
i had tried different recovery image, the results are same. could you send me a known working image for rogers dream?
[email protected]
thanks
please kindly have a look. thanks.
the output shows in the following:
D:\MyDocs\JD\android\adb_1.0.26>adb push spl-signed.zip /sdcard/1_33_2005_spl.zi
p
452 KB/s (0 bytes in 188246.000s)
D:\MyDocs\JD\android\adb_1.0.26>adb push recovery-RA-dream-v1.7.0R-cyan.img /dat
a/local
1159 KB/s (0 bytes in 4712448.003s)
D:\MyDocs\JD\android\adb_1.0.26>adb push exploid /sqlite_stmt_journals
372 KB/s (0 bytes in 11917.000s)
D:\MyDocs\JD\android\adb_1.0.26>adb shell chmod 777 /sqlite_stmt_journals/exploi
d
D:\MyDocs\JD\android\adb_1.0.26>adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
D:\MyDocs\JD\android\adb_1.0.26>adb shell
$ rootshell
rootshell
Password (echoed):secretlol
secretlol
# chmod 666 /dev/mtd/mtd1
chmod 666 /dev/mtd/mtd1
# exit
exit
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
$ exit
exit
D:\MyDocs\JD\android\adb_1.0.26>
this is files under /dev/mtd:
does it have something to do with the "skipping writing"?
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
JaydenCanada said:
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
Click to expand...
Click to collapse
See now we know the error .. well that there was an error anyway.
I'm used to a memory error not the io error. Usually when flash_image fails it skips the block and writes the data in the next block.. if all is well the block is flagged bad and the spl booting the recovery does the same.. seems not all is well in your case.
Before going too crazy. . Lets see if we can make it work.
1) restore the rogers nbh
2) try to boot recovery (hopefully) you will enter stock recovery with the /!\ image.. alt+L will show a short list of options, you may reboot to the rogers rom.. if it fails to boot make a note to inform me in your next reply and reboot into the rogers Tom
3) try the root process again with the 1.6.2R recovery
Amon_RA said:
recovery-RA-dream-v1.6.2R.img (Click here to download from a Mirror) - MD5Sum: b9db12cdd9a1e42b3187425e89c5fbe5
Click to expand...
Click to collapse
3b) if it works you can use fastboot to flash 1.7.0 after installing the 1.33.2005 spl.. I think 1.7.0 will work then..
Report back if it works great. . If not things are a bit more complex. . Particular if the stock recovery also fails.
when you said "rogers nbh", do you mean Bootscreen.nbh?
can i use this: http://forum.xda-developers.com/showthread.php?t=341753
sorry, i am new to this.
really appreciate
JaydenCanada said:
when you said "rogers nbh", do you mean Bootscreen.nbh?
can i use this: http://forum.xda-developers.com/showthread.php?t=341753
sorry, i am new to this.
really appreciate
Click to expand...
Click to collapse
No I mean this: http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
i restore rogers nbh. and i can go into recovery mode. after press alt-L, it shows:
android system recovery utility
there are three options:
reboot system now
apply sdcard:update.zip
wipe date/factory reset
but on the bottom there is warning:
E:Can't open /cache/recovery/command
what i supposed to do next?
thanks,
i tried to go through the instruction. but rootshell won't be generated after run exploid. i can see exploid had run, but in /system/bin there is no rootshell.
i tried
IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
Run "./exploid" and follow directions on screen. Once this completes you'll be back at a shell prompt.
Click to expand...
Click to collapse
rootshell generated. but still i have this:
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
it seemed there is something preventing writing to that block.
thanks
Tbo-rom is my first ROM. It's based on MondoROM and the Orange rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link to Picasa webalbum: https://picasaweb.google.com/106748...authkey=Gv1sRgCN3GhtaNzrX0qwE&feat=directlink
ROM info:
Android 1.6
su + Superuser
Kernel from on MondoROM
Busybox
Apps2SD
Market v2.3.4 patched
White Sense UI
Wireless Tethering
WWE languages
You need Amon-RA recovery to flash it. Remember to do a nandroid and wipe if it is your first time you flash this ROM.
Install at your own risk!
What works and what not:
Camera and FM-radio works because it's an 1.6 ROM
For the Apps2SD you need a EXT3 partition and you can't take the sd-card out of your Tattoo
If the market won't download, just reboot your Tattoo and it will work again.
The bootscreen is almost good. In the next release I have something better.
V0.1
Additional release
Tbo-rom_0.1
Needs to be done:
Fix bootscreen
Make it possible to flash with Clockworkmod so we can use Rommanager.
Let me know what you think of my ROM.
nice rom,so what program you use to take this screenshots from tattoo?
goran95 said:
nice rom,so what program you use to take this screenshots from tattoo?
Click to expand...
Click to collapse
Thanks, it's called drocap2. It's in the market.
Needs to be done:
Fix bootscreen
Make it possible to flash with Clockworkmod so we can use Rommanager.
Click to expand...
Click to collapse
I could write updater script from update script of mondorom and flashed using clock workmod.
Check last post in mondo rom
rallapag said:
I could write updater script from update script of mondorom and flashed using clock workmod.
Check last post in mondo rom
Click to expand...
Click to collapse
Can I just copy the META-INF folder to my ROM?
tbo-art said:
Can I just copy the META-INF folder to my ROM?
Click to expand...
Click to collapse
if you are using the same update script as in mondo rom, yes you can replace META-INF folder.
I have included both update and updater script so can flashed using any recovery.
I am just downloading your ROM so will double check and let you know
EDIT:
There is only one difference between the two,
But i have forwarded you a PM that i have sent to Marko (markokikinda), please explain me so that i can change necessary commands.
EDIT:
Got the answer from Marko, so attached folder contents can be replaced with /META-INF/com/google/android/ contents to work with both amorn and clockwork recoveries
problem
i had to delete at least of 2MB of files, most wallpapers to be able to install.
Other wise i get following error (taken from recovery log)
"minzip: Error writing from zip file : No space left on device"
I was trying to test using clockwork mod
after deleting all the wallpapers from /system/customize/resource folder in the zip
i could install with out problem and boot in to ROM
rallapag said:
if you are using the same update script as in mondo rom, yes you can replace META-INF folder.
I have included both update and updater script so can flashed using any recovery.
I am just downloading your ROM so will double check and let you know
EDIT:
There is only one difference between the two,
But i have forwarded you a PM that i have sent to Marko (markokikinda), please explain me so that i can change necessary commands.
EDIT:
Got the answer from Marko, so attached folder contents can be replaced with /META-INF/com/google/android/ contents to work with both amorn and clockwork recoveries
Click to expand...
Click to collapse
Thank you very much.
rallapag said:
i had to delete at least of 2MB of files, most wallpapers to be able to install.
Other wise i get following error (taken from recovery log)
"minzip: Error writing from zip file : No space left on device"
I was trying to test using clockwork mod
after deleting all the wallpapers from /system/customize/resource folder in the zip
i could install with out problem and boot in to ROM
Click to expand...
Click to collapse
What should I do. It isn't too big is it?
tbo-art said:
What should I do. It isn't too big is it?
Click to expand...
Click to collapse
Well i have a problem with clockwork, that i needed to remove 2MB (so removed wallpapers).
May be it isn't problem with Amron RA (i guess you would know if it had been).
So if you want to get this installed using clockwork as well, then try to reduce contents of system by 2MB.
I don't understand this difference yet, will let you know further when i get the idea
rallapag said:
Well i have a problem with clockwork, that i needed to remove 2MB (so removed wallpapers).
May be it isn't problem with Amron RA (i guess you would know if it had been).
So if you want to get this installed using clockwork as well, then try to reduce contents of system by 2MB.
I don't understand this difference yet, will let you know further when i get the idea
Click to expand...
Click to collapse
Ok will look at it today
rallapag said:
i had to delete at least of 2MB of files, most wallpapers to be able to install.
Other wise i get following error (taken from recovery log)
"minzip: Error writing from zip file : No space left on device"
I was trying to test using clockwork mod
after deleting all the wallpapers from /system/customize/resource folder in the zip
i could install with out problem and boot in to ROM
Click to expand...
Click to collapse
If got a new problem. I can't change my recovery. I want to flash clockworkmod recovery, but it says the device is out of memory. What should I do?
tbo-art said:
If got a new problem. I can't change my recovery. I want to flash clockworkmod recovery, but it says the device is out of memory. What should I do?
Click to expand...
Click to collapse
Possibilities are that mostly it could be root issues or a random error.
Did you try flashing recovery while in recovery, that works better
(remember that you can't use backups from one recovery with other - so far to my understanding).
rallapag said:
Possibilities are that mostly it could be root issues or a random error.
Did you try flashing recovery while in recovery, that works better
(remember that you can't use backups from one recovery with other - so far to my understanding).
Click to expand...
Click to collapse
Will try that. Thanks
It says 'no such file or directory'. What should I do now?
tbo-art said:
Will try that. Thanks
It says 'no such file or directory'. What should I do now?
Click to expand...
Click to collapse
'no such file or directory' does it referring to recovery file or flash_image
are you following some guide
If you want to do manually here is my guide
http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
or use automated flashing from following thread
http://forum.xda-developers.com/showthread.php?t=950759
rallapag said:
'no such file or directory' does it referring to recovery file or flash_image
are you following some guide
If you want to do manually here is my guide
http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
or use automated flashing from following thread
http://forum.xda-developers.com/showthread.php?t=950759
Click to expand...
Click to collapse
It is missing the recovery file. the flash_image is in my rom.
tbo-art said:
It is missing the recovery file. the flash_image is in my rom.
Click to expand...
Click to collapse
Now i get the problem
You have to mount /sdcard
while in recovery
Code:
adb shell
mount /sdcard
flash_image recovery /sdcard/recovery.img
That should do the trick
rallapag said:
Now i get the problem
You have to mount /sdcard
while in recovery
Code:
adb shell
mount /sdcard
flash_image recovery /sdcard/recovery.img
That should do the trick
Click to expand...
Click to collapse
Now I get this:
Code:
adb shell
# mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# flash_image recovery /sdcard/recovery.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
tbo-art said:
Now I get this:
Code:
adb shell
# mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
error writing recovery: No space left on device
Click to expand...
Click to collapse
Are you sure that you are using above commands while booting in to recovery??
rallapag said:
Are you sure that you are using above commands while booting in to recovery??
Click to expand...
Click to collapse
I forgot that. It worked. Thank you very much.
Hi all, here's a custom ClockworkMod recovery I've built, and are using personally. It has advanced backup and a wipe all function, which is useful for completely wiping the phone before flashing a new rom.
It also has support for offmode charging, so you can charge your phone while it's turned off. In addition to this, it fixes the old bug that you couldn't turn on the phone if it was turned off while it was charging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lolz
Anyways, trying this out, should be fine with unrevoked 3.32 right?
Edit: It looks nice too.
doomed151 said:
lolz
Anyways, trying this out, should be fine with unrevoked 3.32 right?
Click to expand...
Click to collapse
Ye it is.
Wipe all formats all partitions, so it's REALLY clean. I always use this before installing from fresh.
NB. You loose Amend scripting and the ability to install Sense based roms, but you can use Rom Manager for that.
arco68 said:
Wipe all formats all partitions, so it's REALLY clean
Click to expand...
Click to collapse
So it wipes ext partitions too?
AND ALL OF SD CARD?
arco68 said:
NB. You loose Amend scripting and the ability to install Sense based roms, but you can use Rom Manager for that.
Click to expand...
Click to collapse
Yeah, I knew that much.
doomed151 said:
So it wipes ext partitions too?
AND ALL OF SD CARD?.
Click to expand...
Click to collapse
Not sd card, but ext yes. Hmm, maybe I should remove wiping of ext from it?
Or maybe not, a wipe data/factory reset also wipes ext.
Cool stuff.
Sent from my HTC Wildfire using XDA App
Seems like unrevoked 3.32 failed at getting root (with both stock Froyo and CM7 RC3), tried out with 3.14 and what came out was a success.
Thanks!
Download unrevoked 3.14 here: http://puu.sh/1ngI/unrevoked_3.14.exe
what are the advanced restore functions?
ramdroid77 said:
what are the advanced restore functions?
Click to expand...
Click to collapse
You can selectively restore stuff (boot, system, cache etc.), IIRC.
Edit: "Mount USB storage" seems to die after a few seconds of file copying, can anyone verify this?
doomed151 said:
Edit: "Mount USB storage" seems to die after a few seconds of file copying, can anyone verify this?
Click to expand...
Click to collapse
I copied around ~10 MB of files using the 'Mount USB Storage' Function. Didn't die for this short while. Will try for some large files later.
Was holding out from updating CWM, but, glad I did it finally.
Somehow, I got another issue though, it seemed to kill the Superuser app. It always FC'ed. Had to remove it altogether and flash it again. (Market download also didn't fix it)
I was actually gonna compile this myself, but thanks arco
Now I need to find Unrevoked 3.14 for OS X
OR maybe I'll just do it from windows xD
nhnt11 said:
Now I need to find Unrevoked 3.14 for OS X
Click to expand...
Click to collapse
You could've just asked me. Uploading it, not sure whether it'll work or not.
Edit: Here you go: http://puu.sh/1nly/unrevoked_3.14_OSX.dmg
doomed151 said:
You could've just asked me. Uploading it, not sure whether it'll work or not.
Edit: Here you go: http://puu.sh/1nly/unrevoked_3.14_OSX.dmg
Click to expand...
Click to collapse
OMG you had it??? THANK YOU!!!!! lolz really... been looking forever for this.. i've been stuck on 3.0.0.5 :/
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# covery /sdcard/recovery-clockwork-3.0.2.4-buzz.zip
flashing recovery from /sdcard/recovery-clockwork-3.0.2.4-buzz.zip
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
failed with error: -1
error writing recovery#
What do I wrong?
I've just noticed that it skips my sd-et partition while making a full nandroid backup. It just displays "no sd-ext found, skipping..." are you having similiar issue guys?
This happens when you Wildfire is not S-OFF thus flashing recovery via Terminal emulator gives failures. Try via unrevoked 3.14.
kingsize1337 said:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# covery /sdcard/recovery-clockwork-3.0.2.4-buzz.zip
flashing recovery from /sdcard/recovery-clockwork-3.0.2.4-buzz.zip
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
failed with error: -1
error writing recovery#
What do I wrong?
Click to expand...
Click to collapse
i'm not sure if anyone can confirm this or weather arco already knows about this or even weather it's just my device only! but since i pushed this recovery with unrevoked a new superuser apk was installed and for some reason seems to be forceclosing everytime i try to open it or everytime something is trying to request $su permissions! meaning my rom has now become unstable as everything trying to request root is failing.
priv8 said:
i'm not sure if anyone can confirm this or weather arco already knows about this or even weather it's just my device only! but since i pushed this recovery with unrevoked a new superuser apk was installed and for some reason seems to be forceclosing everytime i try to open it or everytime something is trying to request $su permissions! meaning my rom has now become unstable as everything trying to request root is failing.
Click to expand...
Click to collapse
Yeah, unrevoked installs superuser so you have 2 conflicting versions. Just reflash whatever build of CM you're using. (Format system first)
nhnt11 said:
Yeah, unrevoked installs superuser so you have 2 conflicting versions. Just reflash whatever build of CM you're using. (Format system first)
Click to expand...
Click to collapse
Thanks again nhnt11 however a simple "adb push Superuser.apk /system/app/" worked fine once i had adb through recovery!
doomed151 said:
You can selectively restore stuff (boot, system, cache etc.), IIRC.
Click to expand...
Click to collapse
Now that's strange. I'm using some old CWM 2.5 version and I already have advanced restore which already allows to selectively restore partitions.