Related
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?
Hello, when I tried to update my Magic to a new radio something went wrong. Start-up screen freezes. Only fastboot and recovery are available.
Now, when I trie to restore my nandroid backup in recovery I get the message:
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
E: Can't mount SDCARD:/nandroid/
And it's not the SDcard that's malfunctioning...
When I trie it with fastboot I get:
C:\AndroidSDK\tools>fastboot flash system system.img
sending 'system' (80002 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash userdata data.img
sending 'userdata' (132301 KB)... OKAY
writing 'userdata'... INFOsignature checking...
FAILED (remote: signature verify fail)
I've searched everywhere for a solution for this problem, and tried everything but nothing helped. So I hope someone can help me here...
These are the specifications of my phone:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
RADIO-6.35.10.18
The original radio was 3.22.20.17
I had recovery-RA-sapphire-v1.6.2H, but after my failed radio update, it rebootet after 2 seconds...so now I use recovery-RA-hero-v1.6.2 to enter my recovery. This one works, doesn't reboot, but I don't have acces to my SDcard.
Thanks for you're help!
How long are you waiting after booting to Recovery before trying the restore? I think there's an issue with the amount of time it takes to mount the SDCard. Try waiting for a bit. It does work for me, but not if I immediately try to backup/restore after entering Recovery. I usually wait a couple of minutes.
well...I've waited 10 minutes...but still the same response...
If I see your specifications, I see that your phone is OFF and mine ON, in another tread someone said that the "ON"-sign was the reason for not having acces to the Sdcard... :s But I'm not sure this is true...
Even...everything I trie to flash with fastboot (so I don't need acces to my SDcard I guess...) doesn't work...due to that signature verify failure... Maybe there is a solution for that problem...?
Hey it seems you really have a problem.
The hboot version is not right for your radio version. You obviously did not follow the very clear howto by cursordroid, easily found in the android development section. I'm not sure how to solve this, but you must first look for some way to upgrade the SPL to the version that works correct with new radio.
Hi...yes... I updated the radio on a wrong way...
I already thought that this new radio and 'old' SPL were the reason why this doesn't function anymore...
I already tried to update the SPL on different ways... With recovery I don't have acces to my SD card and with fastboot I get the same response as above... I don't think there is another way... :s
I really screwed up this time...I hope someone can help me out... This is the first time this happens to me but it will be the last
Woww you're so lucky you didn't brick. Love it when people fail to follow simple instructions! And how would a nandroid restore help? Since when does that restore radio/spl. Also how did you manage to get the hero recovery on there? Did you flash the recovery then radio?
Since you're using the hero recovery, it takes some time to mount the sd card. SO wait a bit when you try this
Try this,
1) fastboot oem enableqxdm 0
2) If that doesn't work, you're sort of screwed. I'm not sure if it will work since youre s-on
3) If it works, flash the old radio in recovery.
4) I'd try goldcard if none of the above works
Hi...thanks for the help!
Well, I read somewhere that I could use that hero recovery... So I use fastboot to boot the recovery on my Magic, that's the only way to enter the recovery.
I first flashed recovery sapphire 1.6.2H, made a back-up and then I flashed the radio...
I tried what you asked and I got this:
C:\AndroidSDK\tools>fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
So...I guess I'm screwed...?
Re: Huge problem to restore nandroid backup - "can't mount SDCARD:/nandroid/"
If your phone really fails to mount the sdcard in recovery, even after waiting a while, you might still be able to flash a correct engineering spl if your recovery allows you to connect by adb. The idea would be to push the img to /cache and flash it from there, using the adb command line. I have never tried that though so no guarantees.
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
Hi, yes, I waited 30minutes...still no result... should I wait longer?
I found the correct engineering spl and I can connect by adb...
Could you tell me which commands I have to type in cmd to push the engineering spl (.zip) with adb?
Thanks!
PM me if you haven't solved the problem yet.
I haven't solved the problem yet.. Could you tell me which commands I have to type for adb in command prompt? This is the name of the .zip file "update.Engineering-SPL-HBOOT-1.33.2009-signed"
Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
I didn't know for sure what you ment with '(the hboot file must be present in the current folder of course)' so pasted the SPL "hboot-1.76.2007" on my SDcard and in AndroidSDK/tools
Then I did this:
C:\AndroidSDK\tools>adb shell
/ # flash_image hboot /cache/hboot-1.76.2007.img
flash_image hboot /cache/hboot-1.76.2007.img
can't find hboot partition
It could be that you did forget a 'space' between boot and cache so I tried this:
/ # flash_image hboot /cache /hboot-1.76.2007.img
flash_image hboot /cache /hboot-1.76.2007.img
usage: flash_image partition file.img
/ # reboot bootloader
reboot bootloader
When I rebooted in bootloader everything was still the same... Did I do something wrong?
Already thanks for the great help!
janximan said:
Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Click to expand...
Click to collapse
this should be
Code:
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img /cache
when the hboot file is in your tools folder. You got a usage message from the command, that means the command was malformed. So the rest couldn't work either. And no I did not miss any space in the flash_image command.
Damn, sorry to disappoint but I did some more research and I think my idea won't work after all
the Sign is on, and you have to turn it off. Use the goldcard method and use:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
to turn it off, and start the flasshing process again for safe keeping.
Instructions:
http://translate.google.pt/translat...ss.C3.A1rio_para_fazer_o_processo&sl=pt&tl=en
If you want try flash using HTC Magic oficial update and start the process all over again for safe keeping.
Hope it helps
i was reading things better. Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ? If you sucessed you could reverse the process
PS: does anyone know to explain me why did this exacly happened?
Jup...still no difference...
Thanks drbobb for all the effort and time! If there really is no other way to make it work than the goldcard method... I should try this one...but read it first a few times...
Jgcaap... Thanks for the help.. I explained on the first page how I get this far... Updated my radio on a wrong way :s
how did you update the radio ? Sorry to ask again but in the first page isnt expressed if you done by flashing procedure (USB) or by other method (Recovery).
Well...i don't know for sure but I think I just flashed a new radio (.zip) file in recovery... Without using fastboot...
Well according to the studies the most safe is in fastboot, in recovery you can also flash but there is always a risk since the recovery might not be 100% safe to flash. But you still havent done anything else? Please try remember because there must be a way of exploiting to make the phone work again.
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
I can no longer get into recovery mode. It just hangs at the myTouch logo screen indefinitely. I can boot into the Cyanogen 5.0.7 ROM just fine, but I'm missing the Google Apps that I forgot to flash.
I was upgrading my recovery to 1.6.2 when I had a power outage. When the PC came back up, I tried to continue on and I get this dreaded message:
Code:
\tools>adb shell flash_image recovery /sdcardrecovery1.6.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)
^C
I've tried killing all processes and services running. I tried running it in fastboot (but I have the perfected version). I can't flash anything. I'm not sure what to do. I don't have Google Market and I'm missing the default keyboard. I had to download the HTC_IME mod one to type anything. Here's the 'df' output:
Code:
# mount -a
mount -a
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 48880 0 48880 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 92160 86396 5764 94% /system
/dev/block/mtdblock5 302848 54704 248144 18% /data
/dev/block/mtdblock4 81920 33192 48728 41% /cache
/dev/block/mmcblk0p2 468331 115335 328011 26% /sd-ext
/dev/block//vold/179:1
7428816 3285108 4143708 44% /sdcard
#
I tried using Root Explorer to go through and delete audio files and crap inside the /system to free up space, but I'm not sure that's even going to work.
As of now, I have no recovery, no market, my reception is horrible (possibly unrelated), and I'm at a loss of what to do now.
Any ideas would be gratefully appreciated.
Here's the fastboot info if it'll help at all.
Code:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
May 27 2009, 19:06:41
[COLOR="Red"]FASTBOOT USB[/COLOR]
[COLOR="DarkOrange"]<VOL DOWN> HBootMode[/COLOR]
[COLOR="Blue"]<SEND> Reset Device[/COLOR]
[COLOR="DarkOrchid"]<ACTION> Restart to HBoot[/COLOR]
[COLOR="Black"]<MENU> Power Down[/COLOR]
I found this: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
And it seems to work with his own ClockWork recovery image. If I try to flash Amon_RA's image, it doesn't boot. I guess I'll stick with that for now as it's better than nothing. If you guys have any ideas, please let me know as ClockWork's recovery, while nice, doesn't have all the features. The manager is quite nice, but I'm not paying $3 for it.
To further update this. Once I installed the ClockWork's recovery image (read notes below), I was able to flash RA 1.6.2, boot to that, and flash RA 1.7.0.
Note: Sometimes the ClockWork recovery image wouldn't take after some tinkering. I uninstalled it and reinstalled it. I also did the following:
Code:
adb shell
mount -a
erase_image recovery
Once I did that, I was able to install or reinstall the ClockWork recovery image. I used the ROM manager to boot to the recovery image to flash Amon_RA's images. All is well, I think. I hope this helps others.
I'm having issues with the card reader inside of my mytouch. I cannot access the card within Amon Recovery; I receive the following errors:
E:can't mount /dev/block/mmcblk0p1
and
E: Can't mount SDCARD
Troubles started after I updated radio and hboot from this thread http://forum.xda-developers.com/showthread.php?t=831139&highlight=remote.
This SPL, (HBOOT) 1.33.0013d, prevents flashing so I cannot flash another hboot with S-OFF.
Trying the command "fastboot oem enable qxdm 0" results in INFO [ERR] Command Error.
I'm at a loss at how to fix this problem Any ideas?
Thanks for the help