another problem if you will. when i first tried to root it made me format the sd card because i exjected it wrong or something, that having been said as background i now get this when i try to flash the image.
C:\android-sdk-windows\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.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)
any help would be great
fresh kitchen
install the newest one and use it to root.
Have you tried reboot recovery? I got the out of memory error also but everything went ok. Just hold the home button down and press power. See what happens. If you get a green menu with a black background then your good to go.
thedudejdog said:
Have you tried reboot recovery? I got the out of memory error also but everything went ok. Just hold the home button down and press power. See what happens. If you get a green menu with a black background then your good to go.
Click to expand...
Click to collapse
Same thing happened to me. I got the out of memory error but the recovery was flashed just fine.
limbicsystem said:
another problem if you will. when i first tried to root it made me format the sd card because i exjected it wrong or something, that having been said as background i now get this when i try to flash the image.
C:\android-sdk-windows\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.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)
any help would be great
Click to expand...
Click to collapse
Same thing here. Out of memory (I thought it was because my SD card was full, but it went through fine however. These guys know what they are talking about... haven't steered me wrong yet!
I had errors like that when I tried to root the first time. I solved mine by restarting the phone and trying again. Like someone else mentioned, have you tried using fresh kitchen?
Really need some help guys. I have no recovery at all...
So i used the root in 1 click option... seems like I have root on my tattoo as I see # in adb shell (id shows root uid 0)... but I think I saw some error when it installed the custom recovery image and I can't seem to get access to it.
When I try to reboot into recovery it just freezes on the Tattoo-logo.
If I try to install recovery again with RecoveryTattoo.bat it just says that the header is fine and won't overwrite.
I got ahold of a flash_image binary from mainfram3 that overwrites even though the header is fine but this is the results:
Code:
# cd /data/local/bin
# ./flash_image recovery /sdcard/recovery1click.img (recovery.img from rtattoo\sdcard)
No luck there... I get the message:
Code:
mtd: erase failure at 0x001c0000 (Input/output error)
mtd: erase failure at 0x001c0000 (Input/output error)
mtd: skipping write block at 0x001c0000
Any help is appreciated. I have root but no recovery and I want that so I can put in a new ROM.
Did you try to boot to recovery, what happens?
Try to flash the recovery image again...
http://forum.xda-developers.com/showthread.php?t=649276
coolbits said:
Did you try to boot to recovery, what happens?
Try to flash the recovery image again...
http://forum.xda-developers.com/showthread.php?t=649276
Click to expand...
Click to collapse
When I try to boot to recovery the screen freezes at the Tattoo-logo (not HTC).
Same error with the recovery-RA-tattoo-v1.6.2.img...
Seriously... I tried to re-flash it with RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe and it just got stuck on the htc-logo.
I cant get custom recovery and I can't restore to stock... I'm stuck with root and therefore no warranty... I need all the help I can get!
Okay, I got one step further. The reason that it stopped at the htc-logo is that I had the wrong drivers for my Win 7 x64 (usb 171 error) but I changed the driver to My HTC on BOTH bootloader and phone.
Now I tried to flash with RUU again (with gold card of course) and surprise! it went beyond the htc-logo and REBOOTED less than a second later... nothing happened.
I'm STILL stuck with no recovery... any help is appreciated.
EDIT: Succesful RUU-flash. Don't know why but I tried a second time and then it worked. I hate when things change their mind on their own... but oh well, I'm back to stock at least. Giving root + recovery another try.
EDIT 2: Ok, back to first problem. It still get the erase failure at 0x001c0000 so i guess it's hardware related? I do get a regular reboot at every 3rd or 4th day if that matters...
EDIT 2: Ok, back to first problem. It still get the erase failure at 0x001c0000 so i guess it's hardware related? I do get a regular reboot at every 3rd or 4th day if that matters...
Click to expand...
Click to collapse
Got same error at address 0x00260000...
Have you solved it?
did you try to flash RUU via hboot ?
Power on your phone while holding down the Volume Down button and the pressing the trackpad.
and then double click the exe file on the desktop ? usb has to be attached of course
Musenkishi said:
Okay, I got one step further. The reason that it stopped at the htc-logo is that I had the wrong drivers for my Win 7 x64 (usb 171 error) but I changed the driver to My HTC on BOTH bootloader and phone.
Now I tried to flash with RUU again (with gold card of course) and surprise! it went beyond the htc-logo and REBOOTED less than a second later... nothing happened.
I'm STILL stuck with no recovery... any help is appreciated.
EDIT: Succesful RUU-flash. Don't know why but I tried a second time and then it worked. I hate when things change their mind on their own... but oh well, I'm back to stock at least. Giving root + recovery another try.
EDIT 2: Ok, back to first problem. It still get the erase failure at 0x001c0000 so i guess it's hardware related? I do get a regular reboot at every 3rd or 4th day if that matters...
Click to expand...
Click to collapse
that was exactly the problem I have. sometimes it loop at the logo sometimes it freeze at htc green robot. I just keep flashing again and again and it worked.
LosLanges said:
did you try to flash RUU via hboot ?
Power on your phone while holding down the Volume Down button and the pressing the trackpad.
and then double click the exe file on the desktop ? usb has to be attached of course
Click to expand...
Click to collapse
yes...i've flashed official RUU in hboot putting CLICIMG.zip in sdcard cause a 170 error using .exe. but then when i ran 1click the same error appear.
niruzz said:
that was exactly the problem I have. sometimes it loop at the logo sometimes it freeze at htc green robot. I just keep flashing again and again and it worked.
Click to expand...
Click to collapse
i've already tried several time but nothing...
Flashed correctly boot, i have # su grant but can't flash recovery
LosLanges said:
did you try to flash RUU via hboot ?
Power on your phone while holding down the Volume Down button and the pressing the trackpad.
and then double click the exe file on the desktop ? usb has to be attached of course
Click to expand...
Click to collapse
yes...i've flashed official RUU in hboot putting CLICIMG.zip in sdcard cause a 170 error using .exe. but then when i ran 1click the same error appear.
niruzz said:
that was exactly the problem I have. sometimes it loop at the logo sometimes it freeze at htc green robot. I just keep flashing again and again and it worked.
Click to expand...
Click to collapse
i've already tried several time but nothing...
Flashed correctly boot, i have # su grant but can't flash recovery
maybe you need to remound partitions first
try from adb shell:
mount -o rw,remount /dev/block/mtdblock3 /system
first and then:
flash_image recovery /sdcard/recovery.img
doramon said:
yes...i've flashed official RUU in hboot putting CLICIMG.zip in sdcard cause a 170 error using .exe. but then when i ran 1click the same error appear.
Click to expand...
Click to collapse
you need to boot in HBOOT mode than press BACK key to get to Fastboot USB Mode (USB connected) and than run the downloaded RUU with double click on the desktop (laptop or PC). and the RUU should be installed from PC. no need to put RUU on SD card.
dancer_69 said:
maybe you need to remound partitions first
try from adb shell:
mount -o rw,remount /dev/block/mtdblock3 /system
first and then:
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
[1 Click Root and/or Recovery]Root and ClockWorkMod 3.0.0.5 mounts both data and system partition in r/w
LosLanges said:
you need to boot in HBOOT mode than press BACK key to get to Fastboot USB Mode (USB connected) and than run the downloaded RUU with double click on the desktop (laptop or PC). and the RUU should be installed from PC. no need to put RUU on SD card.
Click to expand...
Click to collapse
I've flashed official RUU in fastboot mode. but when i use [1 Click Root and/or Recovery]Root and ClockWorkMod 3.0.0.5 script it gives me mtd erase failure at 0x00260000....
why
Same problem but i don't know why!
I've also tried Rom Manager but nothing. tattoo stucks on logo when reboot to recovery.
doramon said:
[1 Click Root and/or Recovery]Root and ClockWorkMod 3.0.0.5 mounts both data and system partition in r/w
(
Click to expand...
Click to collapse
I know that should mount them but maybe failed.
Doesn't hurt to double check it.
I don't remember well, but I think that some similar problems which had in the past caused to wrong tattoo-hack.co version.
You can try also to do the rooting manually or using another root app.
Well, go back to stock again.
Then use Universal Androot to root your device.
After that, if u wish to use a custom recovery, grab flash_image and the tattoo_hack.ko .
Reboot your Tattoo. Connect it to PC. Start ADB.
Type:
adb shell
su
The SuperUser app might ask for permissions. Check remember and hit allow. You will get a #
Then type:
mkdir /data/local/bin
exit
adb push (path to flash_image on PC) /data/local/bin
adb push (path to tattoo_hack.ko on PC) /data/local/bin
adb push (path to Clockwork recovery on PC) /sdcard
adb shell
su
You will get a root shell again
Now type:
insmod /data/local/bin/tattoo_hack.ko
lsmod
If you see 'tattoo_hack' anywhere in the line that follows, then all is well!
Just type then:
/data/local/bin/flash_image recovery /sdcard/recovery.img
Wait. If there are no errors, the recovery is correctly flashed. Reboot to recovery and flash custom ROMs. Enjoy!
sunitknandi said:
Well, go back to stock again.
Then use Universal Androot to root your device.
After that, if u wish to use a custom recovery, grab flash_image and the tattoo_hack.ko .
Reboot your Tattoo. Connect it to PC. Start ADB.
Type:
adb shell
su
The SuperUser app might ask for permissions. Check remember and hit allow. You will get a #
Then type:
mkdir /data/local/bin
exit
adb push (path to flash_image on PC) /data/local/bin
adb push (path to tattoo_hack.ko on PC) /data/local/bin
adb push (path to Clockwork recovery on PC) /sdcard
adb shell
su
You will get a root shell again
Now type:
insmod /data/local/bin/tattoo_hack.ko
lsmod
If you see 'tattoo_hack' anywhere in the line that follows, then all is well!
Just type then:
/data/local/bin/flash_image recovery /sdcard/recovery.img
Wait. If there are no errors, the recovery is correctly flashed. Reboot to recovery and flash custom ROMs. Enjoy!
Click to expand...
Click to collapse
First of all Thank You!!
i've just tried your method and:
Code:
# insmod /data/local/bin/tattoo_hack.ko
insmod /data/local/bin/tattoo_hack.ko
# lsmod
lsmod
tattoo_hack 1480 0 - Live 0xbf12e000
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image: permission denied
# chmod 755 /data/local/bin/flash_image
chmod 755 /data/local/bin/flash_image
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.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)
flashing recovery from /sdcard/recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00000000
#
then i retried with another recovery and got:
Code:
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.img
flashing recovery from /sdcard/recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00320000
mtd: successfully wrote block at b10c00340000
mtd: successfully wrote block at b10c00360000
mtd: successfully wrote block at b10c00380000
mtd: successfully wrote block at b10c003a0000
mtd: successfully wrote block at b10c00000000
#
doramon said:
First of all Thank You!!
i've just tried your method and:
Code:
# insmod /data/local/bin/tattoo_hack.ko
insmod /data/local/bin/tattoo_hack.ko
# lsmod
lsmod
tattoo_hack 1480 0 - Live 0xbf12e000
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image: permission denied
# chmod 755 /data/local/bin/flash_image
chmod 755 /data/local/bin/flash_image
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.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)
flashing recovery from /sdcard/recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00000000
#
then i retried with another recovery and got:
Code:
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.img
flashing recovery from /sdcard/recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00320000
mtd: successfully wrote block at b10c00340000
mtd: successfully wrote block at b10c00360000
mtd: successfully wrote block at b10c00380000
mtd: successfully wrote block at b10c003a0000
mtd: successfully wrote block at b10c00000000
#
Click to expand...
Click to collapse
Yes, you went the right way. Now that you have a different recovery flashed, try flashing clockworkmod again.
If that doesnt help, reboot your Tattoo, insert tattoo_hack.ko and try flashing clockworkmod again.
Out of memory occurs when the phone's RAM is full. Rebooting will solve the problem.
Repeated procedure...Same error
doramon said:
Repeated procedure...Same error
Click to expand...
Click to collapse
There are possibly two reasons for this:
1. You do not have the correct tattoo_hack.ko version.
2. Your internal storage is full.
Possible solutions:
1. Get the correct module again, this time mount /system as RW, before flashing.
2. Try uninstalling some apps to free memory.
3. Try using the tattoo_hack.ko and flash_image present in maverixx's one-click root tool and push those two to the Tattoo and retry the method.
Note: I didnt have to do all of this as I used tattoo_hack.ko from maverixx's tool. For me, everything worked in the first try. I have an Indian Tattoo with original firmware version 1.67.720.8
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)
Click to expand...
Click to collapse
Just an idea of whats happening when i run the
adb shell flash_image recovery /sdcard/recovery.img/
command.
Any ideas?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I believe you are trying to install the recovery image from http://theunlockr.com/2010/03/19/how-to-load-a-custom-rom-on-the-htc-droid-eris/
Try this:
every time you enter a command wait for a minute (especially after pushing files over to the phone)
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard (wait for a minute)
adb push flash_image /system/bin (wait for a minute)
adb shell chmod 755 /system/bin/flash_image (wait for a minute)
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
I think this is what your are talking about. Just try again with these instructions. Hope i helped you out.
Well, it didn't give me the errors.
I'll try putting on something cooked.
Sweet, so far so good..
Seems setting up a .bat file for the ADP commands was a little impatient of me
shame on me
ichbin said:
Sweet, so far so good..
Seems setting up a .bat file for the ADP commands was a little impatient of me
shame on me
Click to expand...
Click to collapse
lol! I hoped it worked for you and for everyone who reads this post with the same issue.
ichbin said:
Sweet, so far so good..
Seems setting up a .bat file for the ADP commands was a little impatient of me
shame on me
Click to expand...
Click to collapse
The workaround is to make a bash script on the phone, chmod +x it, then run it from adb shell
Ok, so i flashed a bad rom and my phone stopped recognizing my sdcard in any shape or form. my PC recognizes the card fine, i've formatted, tried different SD CARDS, etc.
the ONLY way it even shows a hint of recognizing it is if i put on a sappimg.nbh file on the sdcard from my PC, i was able to get my phoen back to stock, BUT it ended up being one of the "perfected SPLs" so that i can't do anything from fastboot. the sappimg also took away my amon RA recovery. so now i can't use a recovery or fastboot to install anything.
so i wanted to create a gold card and install a sappimg.nbh that will allow fastboot functioning. but i can't create a gold card since it does not recognize that i have an sd card inserted. SOMEONE PLEASE HELP!! i've searched the forums endlessly and no one has been able to explain to me how i could create a gold card if the phone isn't recognizing the sdcard...
here are phoen specs:
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.23.02
MAY 27 2009, 19:06:41
ok so i found a way to create a gold card... installed a sappimg.img that lets me use fastboot now. but i still can't install a recovery image from fastboot, is there anyway i can do it?
fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
please note the phone still does not recognize the SDCARD
have tried installing from adb using flash_image :
2) run the following command from the adb directory to mount the cache to the sdcard directory: adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
3) push the normal non Rogers 1.5.2 recovery to the phone: adb push recovery-RA-sapphire-v1.5.2.img /sdcard/r.img
4) flash the non Rogers recovery to the phone: adb shell flash_image /sdcard/r.img -d
but it gives me:
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)
So I have root on the Tattoo following the guide here: http://forum.xda-developers.com/showthread.php?t=716282
Code:
C:\Tattoo>adb shell
# id
id
uid=0(root) gid=0(root)
and I have flashed the boot.img ok I think.
but when I flash the recovery.img I get the following:
Code:
# insmod ./tattoo-hack.ko
insmod ./tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock5 /data
mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# ./flash_image recovery /sdcard/recovery.Tattoo.alpha2b.Mvx.img
./flash_image recovery /sdcard/recovery.Tattoo.alpha2b.Mvx.img
flashing recovery from /sdcard/recovery.Tattoo.alpha2b.Mvx.img
mtd: erase failure at 0x00040000 (Input/output error)
mtd: erase failure at 0x00040000 (Input/output error)
mtd: skipping write block at 0x00040000
#
I have tried about 3 diffrent recovery.img files and after this output reboot and try recovery and I just get the "TATTOO" boot screen forever untill I pull the battery then I can boot back to the OS but I never get recovery. I also tried using adb to boot to recovery and get the same results.
Any idea what I can try?
this is driving me nuts.
Thanks!
And from ROM manager?
lemmymet said:
And from ROM manager?
Click to expand...
Click to collapse
The phone has the stock rom on it, trying to do the initial root/flash so I don't have rom manager yet. I also havent been able to find the .apk of rom manager that will work from the stock rom.