yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] vange:
You did make sure you had the new radio before flashing the rom right?
[myTouch 3G, Magic Android Development] Filgaliel:
I have similar difficulties. I have tried all three versions of the ROM and the initial boot loops on Planet Max..
[myTouch 3G, Magic Android Development] vange:
I haven't tried the latest version, but the first version for me worked with radio 08.29 & 10.18...

Dunno if having 07.29 makes a difference
[myTouch 3G, Magic Android Development] Filgaliel:
OK. Will try installing a newer Radio..
[myTouch 3G, Magic Android Development] thematrix2:
Guys, it's because of the EXT partition!

Use ONLY EXT2 partition on SDcard!!! Do NOT upgrade the partition to EXT3 or EXT4!!!

Next versions of AME2.1 will have support for EXT3 and EXT4.
[myTouch 3G, Magic Android Development] bigballa:
just install the rom again...

if u based of someone elses build it could have apps2sd cards scripts etc etc which caused the phone to mess up a bit

just wipe and reflah
[myTouch 3G, Magic Android Development] thematrix2:
LOL... that has nothing to do with the loop of Planet Max logo... and rom not starting! I am a friend of ahmgsk and it told me that it's because his rom only supports EXT2 partitions! That's all! I had the same problem :)

Users with the boot animation loop error should:

1. Enter recovery and partition SD card. Default settings! DO NOT UPGRADE TO EXT3!!!

2. Wipe factory, dalvik and sdcard.

3. Flash the ROM again.

It will work 100% GUARANTEED! :D
[myTouch 3G, Magic Android Development] Filgaliel:
I wiped and reflashed several times without success. I only have one partition on the SD card..

Edit: Upgraded the Radio, still not working..
[myTouch 3G, Magic Android Development] thematrix2:
Do the steps above and it will work!

Also, make sure you have the radio and spl in my signature below!
[myTouch 3G, Magic Android Development] LoGaY:
i have already solved my problem...

WIPE the HANDSET,and FORMAT the SDCard....now working NORMALLY..heheheh

ooo...

i should do the partitions before i flash the ROM of Eclair 2.1 [MADE BY ME]...is that true?

can i make the partitions after i Flash my ROM of Eclair 2.1 [MADE BY ME]?

any turorials?hehehe
[myTouch 3G, Magic Android Development] thematrix2:
I told you guys it will work :)

You should do the partitions BEFORE flashing the ROM! ALWAYS :D
[myTouch 3G, Magic Android Development] Filgaliel:
I just tried this. Wipe, partition, flash.

I now get past the Planet max logo but it now freezes on black screen..
[myTouch 3G, Magic Android Development] LoGaY:
owww....

maybe,i'll trying this partitions latter,hee...

until someone success....

hee
[myTouch 3G, Magic Android Development] ahmgsk:
Hi people u should hav pm me or -> come on gtalk

i hav never declined any persons request

Anyways -> my rom works only with ext2 patition

so please follow the guide

Swap + Ext2 + Fat32 (96mb Swap + 512 Mb Ext2 + Remaining fat32 ) (For 8Gb Card)

Step 01: Turn Off Ur Device

Step 02: Press Home Key and Power Key At The Same time

Step 03: Go To 6th Option 'Partition sdcard'

Step 04: Select Partition SD

Step 05: Press Home To Confirm

Step 06: Set Swap Size as per required Using -> Trackball OR Volume Key at Left of your Device

Step 07: Set Ext2-Size as per required Using -> Trackball OR Volume Key at Left of your Device

Step 08: Confirm your Action By using Home Button

Your Memory Card Partition Is Created

Now flash the rom

Step For Installation: -

Step 00: Check The SPL required for ROM.zip matches Your PHONE

Step 01: Turn Off Ur Magic

Step 02: Press HOME + POWER (To Enter Recovery)

Step 03: Go To Option 2 ' USB-MS toggle'

Step 04: Paste the ROM.zip in root of your SD-Card

Step 05: Hit Back Button to Return Back to Recovery Menu

Step 06: Go To Option 5 'Wipe'

Step 07: Preform Wipedata/factory reset

Step 08: Perform Wipe Dalvik-cache (If U don't have Partitions On SD-Card This will Give adb error)

Step 09: Perform Wipe SD:ext partition (If U don't have Partitions On SD-Card This will Give adb error)

Step 10: Hit Back Button to Return Back to Recovery Menu

Step 11: Go To Option 4 'Flash zip from sdcard'

Step 12: Choose The ROM.zip, Hit Home to Flash The Rom

Step 13: Select 1st Option 'Reboot system now'

Now -> u should get it working

for more tutorials -> check here

if not come on gtalk -> ahmgsk.mod@gmail.com
[myTouch 3G, Magic Android Development] fabioccoelho:
Hi @ahmgsk, i'm using ur ROM and no have ext*/swap partitions and for me works fine!

Thanks.
[myTouch 3G, Magic Android Development] LoGaY:
Thx God.....

The Masters Give Us The Informations.hee

Great....
[myTouch 3G, Magic Android Development] ahmgsk:
LOL hahaha
[myTouch 3G, Magic Android Development] LoGaY:
sorry last questions....

can i use it for my 2GB MicroSD?

or just for 8GB MicroSD or Higer?
[myTouch 3G, Magic Android Development] ahmgsk:
for 2 gb 96swap + 384mb ext2 + remaining fat32
[myTouch 3G, Magic Android Development] LoGaY:
okay...

after i finished the partitions and finished the flash.... is my handset already activated the APPS2SD?

or I should install or set any software?
[Touch Pro2, Tilt 2 Themes and Apps] ctbear:
I have a Chinese book I want to read on my phone

I tried the reader tab on manila 2.5 but I think it doesn't support Chinese...tried calibre with all possible settings and still getting "????" characters

So does anyone know of a good ereader that supports Chinese characters?

Thanks! :D
[Omnia II General] Freduy:
hi, is this compatible with the omnia pro b7610?
[Omnia II General] iltorvo:
Sure, as you can see.
[Omnia II General] Ryrzy:
Nice work !

Will you GinKage continue this project ? or 0.26 is the last version ?
[Omnia II General] chelsea_fc:
ginkae please fix HTC Sense v2.5 landscape mode :)
[Omnia II General] donrafael:
Here's what I have observed after I installed the OpenGl 1.0 in my M900.

1) xtrakt and testOpenGL works fine with the current drivers.

2) When .net compact framework 3.5 is installed both applications crashed.

3) After unistalling .NET compact framework 3.5 still both xtrakt and testOpenGL crashes. Thus leaving me no choice but to hard reset the phone and re-install the drivers.

I am not sure what i am doing wrong but i wanted to know if there are known issues running both .NET framework and the openGL drivers in M900.

BTW, i am using daskalos custom lite ROM

THanks.
[Omnia II General] ginkage:
Can't say anything about M900, as I neither have one neither do I have any friends who has it.

And, as for Sense 2.5, I'll wait a bit, as I don't want to reflash right now, because I've finally found a good and stable firmware, and tweaked it all the way through. I'll wait for an official 6.5.3 ROM: someone says it may also have issues with Opera 9.7, so I'll have to dig through those sources once again anyway.

So, 0.26 is probably not the last version. Although I'm just not sure what else can I squeeze out of this project apart from fixing some annoying bugs.
[Click Android Development] mainfram3:
I'm starting this thread to document the work on creating a custom recovery image for the Tattoo.

The main goal is to provide a recovery image that will serve as the launchpad for flashing custom roms.

The Tattoo Custom Recovery Image will provide:

1) A way to use an update.zip signed with test-keys (

already accomplished

);

2) A way to perform a full backup of mtd2,mtd3,mtd4 and mtd5 (boot,system,cache and data).

3) A way to perform a full restore of the backup achieved by 2);

4) Adb support (

already accomplished

);

4.1) Adb shell support.

I'm open to input about using nandroid. Right now, without a S-OFF/ENG SPL this looks useless.

Also, if you have any other special need for recovery, please feel free to express it :)
[Click Android Development] mainfram3:
Alpha release

Tattoo's Custom Recovery Image, Alpha Release

This first release includes:

- ADB enabled recovery

- ADB enabled root shell

- Accept update.zip signed with test keys

- All partitions mounted

- Custom recovery program (the last two options are stubs, not really working yet)

- Included in /sbin: busybox, flash_image and BART

- I've not used BART and, at the moment, cannot attest if it works or not.

- Backup script in /sbin/backup.sh

- Restore script in /sbin/restore.sh

With this custom recovery you can now do a full backup of your unit, by dumping the mtd block devices to your sdcard. Afterwards, you can use flash_image to recover your Tattoo to it's previous state.

I'm releasing this image as is. This is not a point-and-click recovery tool. If you don't know what you're doing, you can seriously damage your unit. The only reason I'm releasing this is in an effort to provide other devs with a way to easily recover their units, back to day-to-day configuration, while experimenting with them.

To flash:

Copy TCRI.alpha.img to /sdcard.

Run "flash_image recovery /sdcard/TCRI.alpha.img"

To reboot into recovery (quickest way)

adb reboot recovery

Please comment :)
[Click Android Development] chusen:
thanks for you work
[Click Android Development] chusen:
i try to flahs and get permission denied, do you know why?
[Click Android Development] leon1984:
flash_image: permission denied
[Click Android Development] -bm-:
Partition remounted writeable from a fresh rebooted system with the tattoo-hack.ko module inserted??

But I'm sure you did that before because of:

;-)

-bm-
[Click Android Development] HTCDevil:
Thank you very much for your excellent job ;)
[Click Android Development] leon1984:
Someone could install custom alpha recovery?

thx
[Click Android Development] chusen:
@-bm-:yes I will try that way since the beginning. i mount with rw permissions /system and /data. i know is not a point-and-click recovery tool but i think i need more permissions but where?
[Click Android Development] mainfram3:
Where did you guys get your flash_image binary from ?

The error you're getting is from flash_image, not from my recovery image.

I'll attach the flash_image I've been using to this post.

Please tell me if this solves your problem. You need tattoo-hack.ko module inserted, if you're using a release kernel.

Edit: You have the correct permissions in your flash_image binary, right ? After pushing it to the device, don't forget to chmod 755 :)
[Click Android Development] leon1984:
It works;) I like drawing, jejeje.

Backup and Restore functionality appears to have no further

The adb root shell is perfect

Very good Work

for when the beta version? and the final version? lol
[Click Android Development] chusen:
I try to dump the system userdata and boot.img and when i try to extract with unyasffs and i get this when i try to extract system.img

4 [main] unyaffs 3940 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
644 [main] unyaffs 3940 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump

and this with others

broken image file
[Click Android Development] mainfram3:
mainfram3@cardbox:~/Tattoo/images/boot/1$ ../../unpack.pl ./boot.1.img

Page size: 2048 (0x00000800)
Kernel size: 1899580 (0x001cfc3c)
Ramdisk size: 160952 (0x000274b8)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.1.img-kernel ... complete.
Writing boot.1.img-ramdisk.gz ... complete.
528 blocks

[ boot.1.img-ramdisk.gz decompressed to boot.img-ramdisk ]

My image dumping script is OK :D

Take a look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

The boot.img is not a yaffs2 image. It's a special format, comprised by a 2k header, a kernel image and a ramdisk.

The system.img is a yaffs2 image. From unyaffs's homepage: "Unyaffs is a program to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image."

Chusen, I think it would be better to create a new thread for this, since it doesn't concern the custom recovery image directly.
[Click Android Development] Coburn64:
Thank god for custom recovery!

Now we can really start cooking ROMs... gonna break out the tools tonight and get Android 1.6/2.1 sources ready to compile.
[Click Android Development] mainfram3:
You tell me :)

Next in line is to tie the backup/restore scripts to the UI, which won't be too hard.

Later, I may mess around with nandroid and bart, to see if they provide something more than my scripts.

Afterwards, when we have some custom roms available, I may create a downloader/updater option, to make it easier to install those.

Also, I'm taking requests for new features :)
[Click Android Development] cn.fyodor:
suggestions about scripts

Excellent work, mainfram3. Thank you.

I have extracted the img file, and check backup.sh and restore.sh scripts. The code for checking sdcard remaining space is done. Here it is:

## TEST: Check free space in sdcard
NEED_KB="200000"
REM_KB=`du /sdcard | awk '{print $6}'`
if [ ${REM_KB%K} -lt $NEED_KB ]; then echo "Not enough space in /sdcard, exiting"; exit; fi

backup space min set to 200MB. :D

There is another suggestion about restore.sh. Because of backing up img to /sdcard/Backup, $1 might not be needed, right?
[Click Android Development] jamezelle:
and if you want to extract the boot.img here are the two scripts you need to fully extract the kernel(zImage) and ramdisk

split_bootimg.pl

and

extract-ramdisk.sh

they are attached below
[Click Android Development] cn.fyodor:
jamezelle:

extract-ramdisk.sh missed #!, and the ramdisk zip file should be passed to $1 of this script. :)
[Click Android Development] bftb0:
Hi mainfram3,

I don't want to jack your thread - could you add a little elaboration on this point, or provide a URL so I can learn a little more? The SPL on the phone (oem-78 or fastboot mode) accepts updates signed with the test key from the SDK? (Or some other key?) (On the Eris, the "rom.zip" files unpacked by the RUU are prepended with a mystery blob of 256 bytes - s'pose it could be a mic/sig, but if that's what it is, it don't appear to be in a standard DSA/RSA format, and those .zip files are not signed using the .apk/.jar manifest-signing method)

FYI here's an entertaining story of an epic fail in a related area. After reviewing the fastboot sources from the android tree, I decided that I wanted to spy on the (Windows) RUU update program by sniffing the USB bus - in particular to see if it was explicitly passing signatures in .sig files. (That's an undocumented command-line behavior in fastboot.)

Turns out that recent versions of libpcap and Wireshark allow for USB bus capture on Linux - and using the "usbmon" kernel module in Ubuntu 8.04 LTS, sniffing the USB (5k packet size) seems to work without hitch, even at USB 2.0 speeds. So I took it one step further, and installed WIn Xp SP3 in a QEMU VM on the Ubuntu machine, with the intention of running the RUU updater inside the Xp VM and sniffing the USB bus in the host OS (Linux) machine.

The result? QEMU/Win Xp VM can talk to the phone in either fastboot or adb mode, but bluescreens as soon as you start to move data at any appreciable rate. Doesn't seem to be dependent on whether monitoring is taking place. I might try putting the phone behind a cheapo USB 1.1 hub, and see if that helps, but for the moment I am stopped out on this hack.

bftb0
[Click Android Development] jamezelle:
it works ;) yea sorry about the

#/bin/sh :p

i didnt write the scripts btw
[Click Android Development] coolbits:
Thanks for this... great work :)

But i have a problem...

i put flash_image to /system/bin and chmod 755

but when i try to use it i get:

flash_image recovery /sdcard/TCRI.alpha.img

header is the same, not flashing recovery

#

where did i go wrong?

will reboot and try again...

same after reboot... hmm

same error in recovery console...
[Click Android Development] Coburn64:
Hm, odd...

Is this normal?

I hope i didn't brick the phone... Heh, one way to find out I guess...

EDIT: The Tattoo lives to meet another hack! It flashed successfully! Now, time to change the bootup sound with one from the PlayStation BIOS... Mwhahaha :D
[Click Android Development] coolbits:
"Cannot allocate memory" comes because you didnt run tattoo-hack.ko before to make /system writable... ?

I did it but get another error i posted...
[Click Android Development] Coburn64:
I did run the insmod step.

Reboot into recovery and see if it's flashed, if you're getting that error, it's likely that flash_image already flash it for you, it's a speed demon. :)
[Click Android Development] coolbits:
Strange because i dont see backup and restore scripts in /sbin

Maybe just header flashed?
[Click Android Development] zbrahead91:
Hey again guys. I have been emailing the dev of Titanium Backup, and he has released it for the Tattoo Market :D!

To run this properly, ENSURE you have busybox single call binary and the magical su in /system/bin/.

Then backup ytour stuff flash away re-install and restore! :)
[Click Android Development] mainfram3:
Nice work fyodor, thanks :) That's the true spirit of opensource. Crack it open, hack it up and return it to the community :D

About the script, the backup.sh creates a timestamped dir in /sdcard/Backup. That's why I ask the directory as an argument to restore.sh. I like to create several backups, so that I can rollback to whenever I want. When I tie the scripts to the recovery binary I may simplify it though.

To get images accepted by fastboot we would need a Security-Off / Engineering SPL. Unfortunately, we still don't have any of those :(

My recovery image has the public key of the test keys in /res/keys. This means that you can create your own update.zip file, sign it with the test keys and have it accepted by the standard update.zip mechanism.
[Click Android Development] gaolizhou:
thank you for you wonderful work

could you write the details about how to make a tattoo rom?

I really need it :)
[Click Android Development] -bm-:
To be the last one on the list: Worked for me without a problem :-)

If anybody wants to restore the original recovery use the attached image.

Thanks mainfram3 for the work!

-bm-
[Click Android Development] coolbits:
Uh thanks for this :D
[Click Android Development] suoko:
great recovery !

just backupped the system to sd

i found a complete guide in a mixed english/italian language

http://www.androidworld.it/wiki/Recovery.Img_(HTC_Tattoo)

exit adb shell and run

adb reboot

to exit recovery mode
[Click Android Development] vlipper1:
done

flashed whit tattoo-hack.ko insmodded.

flashed whit /data/local/bin/flash_image -d /sdcard/TCRI.alpha.img

rebooted to recovery screen and i have your recovery chill keep on the good work :D
[Click Android Development] darkandroid:
Hello I would like to know how to put the file in the flash_image tattoo thanks

sorry for my bad English :o :o
[Click Android Development] Exit93:
What's the command to apply update.zip?
[Click Android Development] marsdroid:
provide us a amon_ra like recovery ...

this is not for newbies.

THX

Marsdroid
[Click Android Development] tranmynhquan1991:
Please anyone make a guide for newbie about how to install that recovery image from the begining , after booting and the # appear . I just have rooted my Tattoo and I'd like to install AzusaRom to repair Wifi problem . Plz help me .

after I type : "flash_image recovery /sdcard/TCRI.alpha.img" , it report : flash_image : not found . If there is a video , that is better
[Click Android Development] dthomasen:
Never mind guys.. Figured it out! Finally!

Thx for all your hard work! And looking forward to a lot of nice custom roms :D
[Click Android Development] huetson2:
hi whooper90, can you please advise. i have followed everything to the letter, but am getting the error about no space left on device.

can you please let me know how to work around this?

thanks in advance
[Click Android Development] dthomasen:
You have to follow the instruction under "New: Make /system writeable" http://xdaforums.com/showthread.php?t=635961 . this is to get tattoo-hack.ko :)
[Click Android Development] huetson2:
am getting flash_image not found.

i have root and have pushed the tattoo_hack.to

so stuck, please kindly help someone
[Click Android Development] dthomasen:
And you've changed the directory to where you've put the flash_image binary?
[Click Android Development] huetson2:
not sure to be honest, am having problems. rooting was and is fine, just really really struggling with this part though.
[Click Android Development] dthomasen:
Make sure the recovery image is on the root of the SDcard.

Push the flash_image binary to /data/local/bin/ on the phone.

Then use "cd /data/local/bin" to change to the directory.

Type "flash_image recovery /sdcard/TCRI.alpha.img"

That should do it :)
[Click Android Development] coolbits:
dont forget to:

chmod 755 /data/local/bin/flash_image

and the do:

cd /data/local/bin

./flash_image recovery /sdcard/TCRI.alpha.img
[Click Android Development] dthomasen:
Oh yeah.. My bad..

Don't think I can repeat the process.. Just glad that it's done :D
[Click Android Development] huetson2:
whooper90 - superb thank you very much, and coolbits thank you very much too for your excellent input.

nearly swapped back to the magic with the wife, was doing my head in - chomd 6755 - was copying/pasting and had stuck a 6 in there for some unknown reason!
[Click Android Development] darkandroid:
I did as you said whooper90 just that I always say that he is not space in the tattoo as you first ...

sorry for my bad English
[Click Android Development] pper:
when I boot into recovery, I can only see an Android image, how can I fix it?
[Click Android Development] Coburn64:
You need to press and release HOME + END + BACK quickly or you'll reboot the phone.
[Click Android Development] dancer_69:
I've flashed this recovery image without errors. Now I can boot to recovery and I see the new recovery image, but nothing else, and device doesn't reboot or something. This is normal? I thought that I'll get a menu with some options or something. And I suppose from what you say, that device must reboot if I don't press the button combination, but in my case it stucks in this screen.
[Click Android Development] coolbits:
When in recovery open console ./adb shell

you get #

Now you can do:

/sbin/backup.sh

This will make a backup of your phone to /sdcard

and if you screw up something go in recovery again and do

/sbin/restore.sh

This is main reason for recovery for now...
[Click Android Development] dancer_69:
So, it's normal what I get.

Thank you very much.
[Click Android Development] tranmynhquan1991:
how can I fix this error . I have this and when i flashed , it report : No such file or directory :|
[Click Android Development] segway_:
ok... possible you have other kernel...

run uname -a and post the result to compile the module for you.

cya
[Click Android Development] tranmynhquan1991:
I'm just a newbie . can you explain more detail . type : "uname -a" after # ???
[Click Android Development] segway_:
yep

or /data/local/bin/busyclick uname -a

send the result...

cya
[Click Android Development] tranmynhquan1991:
/data/local/bin/busyclick uname -a : not found

that is the result . I have installed Busybox yet
[Click Android Development] marsdroid:
MORE ... MORE ... more
[Click Android Development] liderzre:
c:\rtattoo>adb shell

# chmod 755 /data/local/bin/flash_image

chmod 755 /data/local/bin/flash_image

# cd /data/local/bin

cd /data/local/bin

# ./flash_image recovery /sdcard/TCRI.alpha.img

./flash_image recovery /sdcard/TCRI.alpha.img

header is the same, not flashing recovery

#

Is that OK?
[Click Android Development] milos11136:
When I type /sbin/backup.sh , I'm getting :

# /sbin/backup.sh

/sbin/backup.sh

/sbin/backup.sh: not found

#
[Click Android Development] coolbits:
You need to flash recovery image from mainframe before this.
[Click Android Development] pper:
can i skip the header check, if i want to flash the same recovery again?
[Click Android Development] coolbits:
no... flash the original recovery back... it somewhere in this thread.

Then flash the modified again.