yashsingh1/xdaforums huggingface dataset:
[Click Android Development] mrigesh:
@Coburn64 .... yeah i saw that .... i was actually "gaping" at that ... but unfortunately however times and whichever way i tried to get that "recovery" cannot be accessed .... i even tried doing so while in boot menu ... failed .. !! so i am thinking of modifying system files ..... !!

PS .... modifying the system files can result in permanently modifying the system .... even the "factory reset" cannot undo that ....

i got such an issue so i am just giving a suggestion ... !!
[Click Android Development] mrigesh:
@jamezelle ... what script are you talking about ?? if its that init.rc ... i pulled it from my device to see if i can modify it for consistent root access .. !!! i posted it for some suggestions for the same
[Click Android Development] -bm-:
I'm not sure, but I think /init.rc is replaced on every reboot, so it doesn't make an effect if we modifie /init.rc

Where to find the original init.rc?

-bm-
[Click Android Development] mrigesh:
there is no other init.rc ... i couldnt find it anywhere :( ... !! i suppose the system while booting compares and "undo'es" every change made to its critical files .. from the recovery image !! thats a wild guess though !! but then i changed some files in the /data/data folder and its still intact !!
[Click Android Development] mainfram3:
The "original" init.rc is in the ramdisk that's part of boot.img.

What you're trying to achieve _should_ be as simple as:

1. Dump the boot partition (mtd2 IIRC, check in /proc/mtd)

2. Unpack the boot partition you got from 1)

3. Mount the ramdisk, through loopback

4. Pack the new image

5. Flash with "flash_image boot newboot.img"

Link for more details: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images . Grab the unpack-bootimg.pl and repack-bootimg.pl, they help a lot.
[Click Android Development] mainfram3:
Also, while you're at it, don't forget to change default.prop, for extra goodies (mainly having root directly from adb and being able to remount partitions):

cat default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1 [b]<- Extra goodies if this become 0[/b]
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
#
[Click Android Development] mrigesh:
@mainfram3 ... cant that be done from boot menu ... i mean ... using fastboot ... to change that value in the boot menu itself ??
[Click Android Development] mainfram3:
Nope; if fastboot was completely available to us, we would have full access to the Tattoo.

Short from acquiring a S-OFF/ENG SPL (that would allows full and total control over the Tattoo) we're limited to hacking it from inside the running OS.

I'm currently messing with the recovery partition, since I want to create a custom recovery image first. It would be nice if someone took over the task of creating a custom boot image, like in your discussion above ;)
[Click Android Development] mrigesh:
i am downloading roaster for the same purpose ... and with the ROM's availabe .... i think i may b able to create a custom rom withut bricking my device ;)
[Click Android Development] UliJonRoth:
insmod problem

Hello,

same problem here with insmod..it fails with "insmod: init_module '/data/local/bin/tattoo-hack.ko' failed (Exec format error)"...

some way to get this working without flashing ROM?

thanks a lot, :confused:
[Click Android Development] Sashok:
Can someone help me how can i replace the system fonts ?

I performed all the steps to get root, including tattoo-hack.ko.

I copied the fonts to the SD card.

Now, how i copy the fonts to /system/fonts ?

What commands ?
[Click Android Development] jamezelle:
i was talking about this

/system/etc/install-recovery.sh

can someone post that script
[Click Android Development] _yen_:
Hello,

nothing for tatto as install-recovery.sh seems only used to patch boot and recovery during OTAs. Take a look here also, may be something interesting about: hxxp://alldroid.org/viewtopic.php?f=210&t=809&view=next

Bye
[Click Android Development] suoko:
way to upload a rom

can we follow these instructions to upload a new rom to the tattoo ?

http://www.brighthub.com/mobile/google-android/articles/42677.aspx

it uses this

HARD SPL (Secondary Program Loader)
[Click Android Development] suoko:
what about debian on tattoo ?

http://www.androidfanatic.com/cms/community-forums.html?func=view&catid=9&id=251#251

do you think it will install without problems ?

will i be able to have maemo on it then ?
[Click Android Development] jointfull:
Not that I know of, and I tried finding one.

I had:

1.66.728.1 with Kernel: 2.6.29-g5d289ea (htc-kernel@and18-2 #115).

Flashed.. and not I have:

1.67.405.6 with Kernel: 2.6.29-gf922713 (htc-kernel@and18-2 #117).

Not that of a hassle, besides having to get a goldkey, and re-installing everything afterwards....

Now I have hebrew fonts!
[Click Android Development] Ninolina:
Well I did everything from the first post. Before the starting I conect my Tattoo with my PC. How can I check if I really managed to root my Tattoo? I only dont know how to do the Remount of system which is the last step. So, can you tell me how to do that? Because I tried to change my Font and I try that with the app RootExplorer and I can not see whats in Root folder or change the content of system/font folder. Can you please tell me how to change font? Is there any code to type on PC or I can do that with this RootExplorer in my phone? Thanks in advance :)
[Click Android Development] gascharlie65:
I did it:

> adb push su /sdcard/

> adb shell

> while do /data/local/bin/m7 ; done

> /data/local/bin/su

> export LD_LIBRARY_PATH=/system/lib

> export PATH=/system/bin

> on other shell: adb push tattoo-hack.ko /data/local/bin/tattoo-hack.ko

> insmod /data/local/bin/tattoo-hack.ko

> mount -o rw,remount /dev/block/mtdblock5 /data

> mount -o rw,remount /dev/block/mtdblock3 /system

> cd /system/bin/

> mv su su.old

everything was fine up to the last instruction for which I get:

failed on 'su' - No such file or directory

Any idea?

Thanks!
[Click Android Development] vlipper1:
rooted tattoo

I rooted this tattoo sucessfuly whit this howto. is used the m7 file :D

no problem thanks anyway.

but when i reboot my tattoo i can re root it again?

so i desided to put the su and busybox files to /system/bin

3 messages apear

not enough memmory

and no memory allocation are the 2 main messages im stuck whit :|

the 3th message is about read/write problems of /system/bin

also sucessfuly remounted /system but /system/bin keeps getting read only.

when im passed that i get message 2 not enough mermory or the 3th message cannot allocate memory?
[Click Android Development] vlipper1:
failed on '/system/bin/su' - Cross-device link

also i am getting this last message

failed on '/system/bin/su' - Cross-device link
[Click Android Development] iliko:
Why this command is not working in Terminal emulator or in via pTerminal? :eek:
[Click Android Development] vlipper1:
ok done

ok done :D

sucessfuly copy'd su to /system/bin

mounted rw /system

insmod the tattoo-hack.ko

#/data/local/busybox cp -f /sdcard/su /system/bin/su

when i type $ su

i get #

next cp busybox to /system/bin

i think insmod is still loaded

and /system still mountend as rw,remount

so i type

$ su

get

# id

uid=0(root) gid=0(root) groups=1003(graphics),1004(input

15(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)

nice root

#

i use busybox again becouse android does not got CP only MV

so i copy busybox whit busybox :confused:

# /data/local/busybox cp -f /data/local/busybox /system/bin/busybox

# exit

$ busybox

busybox

usybox

usyBox v1.15.2 (2009-11-28 13:06:43 CET) multi-call binary

busybox is working..

(next on my list is to getting SSHD running;)
[Click Android Development] vlipper1:
su /system/bin #

$ su

#

in adb it works.

but in connectbot terminal busybox only works.?

su : uid 10046 not allowed to su

HOW do we change de UID of su so it works on the apk's
[Click Android Development] coolbits:
You need "su" i posted on page 23... it works with all apps.
[Click Android Development] marsdroid:
this is an exelent xp guide...

THX

Marsdroid
[Click Android Development] coolbits:
One post before yours...
[Click Android Development] dom_b:
Just seen this... So do we have to do the M7 exploit, then copy this over and thats it? Root access for apps?
[Click Android Development] vlipper1:
Done

tnks m8 for this SU.

it was a bit of strugle to get the old su removed. or moved.

rm and mv /system/bin/su /system/bin/su.old (cannot remove /system/bin/su folder not empty)

whit the ./m7 i moved it sucesfully to /system/bin/su2 so i still can use this su.

connectbot terminal now says access granted so indead use the root su from page 23 like he sayd :D

connectbot now succesful gets a # tnks for this great forum xda great job (Y)

---------------

HTC TATTOO ROOT'ed whit m7 su and busybox :D

afther

RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe

$ su

# busybox uname -a

busybox uname

Linux localhost Linux localhost 2.6.29-gf922713 #117 PREEMPT Tue Sep 29 18:11:07 CST 2009 armv6l GNU/Linux
[Click Android Development] coolbits:
Its also posted at the end of first post... :)
[Click Android Development] shears:
when i try to get root with Terminal Emulator apk, i get this:

otherwise it works, i can edit and delete files in the /system/ folder using AndroidMate.apk
[Click Android Development] coolbits:
You must:

cd /system/bin

chmod 4755 su
[Click Android Development] marsdroid:
In that init.rc,we'd need to edit the following...........

/init.rc is replaced on every reboot

so we need someone to

change

Code:

mount rootfs rootfs / ro remount...and replace it with

mount rootfs rootfs / rw remount

Code:

mount yaffs2 mtd@system /system ro remount...and replace it with

mount yaffs2 mtd@system /system rw remount

Code:

mount yaffs2 mtd@userdata /data nosuid nodev...to...

mount yaffs2 mtd@userdata /data nodev

1. Dump the boot partition (mtd2 IIRC, check in /proc/mtd)

2. Unpack the boot partition you got from 1)

3. Mount the ramdisk, through loopback

4. Pack the new image

5. Post BOOT.IMG and flash with "flash_image boot newboot.img"

allso in the /default.prop

ro.secure=1

need to be ..

ro.secure=0

can someone help with that ramdisk ??

THX

Marsdroid
[Click Android Development] shears:
nope, i did this, and it still doesn't work in the Terminal Emulator.
[Click Android Development] segway_:
Compiling the htc kernel and tattoo-hack module..

Ok lets start:

1. Download kernel from: hxxp://member.america.htc.com/download/RomCode/Source_and_Binaries/click-656120.tar.gz

2. Download and install compiler: hxxp://codesourcery.com/sgpp/lite/arm/portal/package5355/public/arm-none-eabi/arm-2009q3-68-arm-none-eabi.bin

3. unpack kernel

4. connect your tattoo at usb port and:

adb pull /proc/config.gz .

gunzip config.gz

mv config (kernel_dir)/.config

5. copy tattoo-hack.c to (kernel_dir)/drivers/char

6. edit (kernel_dir)/drivers/char/Kconfig add :

config TATTOO_HACK

tristate "Tattoo hack"

7. edit (kernel_dir)/drivers/char/Makefile add:

obj-$(CONFIG_TATTOO_HACK)	+= tattoo-hack.o

8. make menuconfig and navigate to device drivers -> Character devices -> Tattoo hack

and mark as module

9. uname -a from tattoo shell to see the version of the running kernel (example "2.6.29-gf922713")

10. run from local shell:

make LOCALVERSION=-gf922713 (insert your string from step 9)

11. Wait for compile..... after all is finished go to the (kernel_dir)/drivers/char/ folder

and grab the tattoo-hack.ko.

12. The kernel is compiled too....

You know the rest.....

Cya
[Click Android Development] batusaix911:
Hey,

Congrats to all the devs who made this possible. But I have a doubt. Is it possible to transfer files via bluetooth yet? I dunno if that was an android 1.6 problem or a Tattoo problem in the first place but it is something I'm ashamed of telling anyone who looks at my phone with awe and then realises that it doesn't have what a basic model in most countries would have.

Thx in advance!
[Click Android Development] Ninolina:
Can somebody please help me?
[Click Android Development] UliJonRoth:
it deserved a try, but get same error with tattoo-hack module (tattoo-hack.o)...if i could upload the config, and somebody could waste some time....:)

thanks a lot,
[Click Android Development] segway_:
UliJonRoth,

if you send me your kernel build number (run uname -a from terminal in tattoo and send me

the output) i can compile the module for you.

cya
[Click Android Development] UliJonRoth:
here you are, segway...thanks in advance for your help...:o

# ./busybox uname -a

./busybox uname -a

Linux localhost 2.6.29-g6561203 #131 PREEMPT Mon Oct 26 19:43:18 CST 2009 armv6l GNU/Linux
[Click Android Development] segway_:
Ok here you are... Hope it works.....

If not send me the config file from your tattoo.

cya
[Click Android Development] UliJonRoth:
thanks again for your help...now insmod loads the module with success, but it seems that i'm missing something, or the module doesn't behave as expected..i'm stuck trying to make /system writeable, and the only response to any write attempt is "cannot create /system/bin/su: not enough memory"..:eek:

Thank you again, segway_, for your time,
[Click Android Development] Coburn64:
On a fresh rebooted Tattoo,

Get a root shell,

insmod that hack file

THEN remount /system readwrite. Else, it will fail.
[Click Android Development] UliJonRoth:
that's what i did, but even after that, i'm not able to write or delete on /system..a bit confused...

EDITED:NOW yeeeeeees,WORKED..don't know exactly why this time, but it worked fine, step by step.
[Click Android Development] gascharlie65:
I have the same problem.

These are some example of instruction I gave and the error message I got:

with

dd if=/sdcard/download/busybox.asc of=/system/bin/busybox

I get (after remounting r/w /system):

/system/bin/busybox: cannot open for write: Out of memory

with:

mv /data/local/bin/openvpn /system/bin/openvpn

I get

failed on '/data/local/bin/openvpn' - Cross-device link

with

cat /data/local/bin/openvpn > /system/bin/openvpn

I get

cannot create /system/bin/openvpn: not enough memory

Thanks for your help!
[Click Android Development] marsdroid:
once we have copyed the

su from from this thread

su into /system/bin/

hack from from this thread

hack.ko into /system/lib/modules/

gscript from this thread

Make Root.sh into /sdcard/gscript

factory reset phone .... install gscript

google ppcwarez

run gscript : in gscript load up "make root.sh"

add it on the launcher as widget "root" klik that 1 time each time

u do a factory reset or reboot

and then you have FULL SU access /RW :)

install rootexplorer 2.7 ,2.8 mm

and edit/add/delete both /data + subfolders/files

and /system + subfolders/files

help me flash the recovery plz

how the f*** do i mount the recovery --- ??

its not even added in this su

how do we MOUNT ...and MOUNT RECOVERY RW ???

no reason to keep this info for your self ......

i could dump everything and take the honor...

GO NOW..do it now before its to late...im lot allowed 2 speak!

THX

Marsdroid
[Click Android Development] vlipper1:
rootbooted

if you want root gets booted look at this custom boot.img

http://xdaforums.com/showthread.php?t=640710

its done im running it.

its an other root # but when you type su you get the su # of this post again

adb shell

# su

su

su: access granted, courtesy of www.magicandroidapps.com

#

its on your own risk

first try

adb push boot.img /sdcard/

adb reboot oem-78

fastboot oem boot /sdcard/boot.img

to try if its booting :)
[Click Android Development] maninhas:
so can we modest users do root and have all acess to tattoo ive read it all and its a bit confusion so many things to do.... can someone help :o
[Click Android Development] marsdroid:
THX m8 i have noting to lose trying it...

thx
[Click Android Development] marsdroid:
up UP UP i need the correct info
[Click Android Development] mainfram3:
For what I understand of your post, you want to remount recovery rw ?

You can't.

The recovery partition uses a special format and can't be mounted. You can dump it, copy to your PC and then expand it..
[Click Android Development] mrigesh:
i agree with mainfram3 ..... !! the recovery cannot be mounted !! even the extraction ri8 now seems pretty tricky .... !!! u MUST make a backup of ur mtd1 and mtd2 before trying something like that or u may brick ur device ... :) ....

just a suggestion though ;P ...
[Click Android Development] Blackdragon_860:
hello peoples..

how i can run a update.zip?

i have make something and i will test it.

but i cant find how i can install the update.zip
[Click Android Development] vlipper1:
how do i see boot.img version

how do i see what boot.img version im running
[Click Android Development] mmike21:
... OK CAN SOMone one, organize the hell of this TOPIC about rooting? so many posts, so many treads, what is the Working Rooting tutorial after all??

Mounting not mounting.. someone says this, someone other.. X

I have root acess b simple doing /data/... m7 , and i get the # instantaneously .. but what now!?

keep it clean!
[Click Android Development] vlipper1:
SOLVED IT ALREADY BY REFLASHING THE THING AGAIN

:confused::confused::eek:

http://xdaforums.com/showpost.php?p=5789948&postcount=57

Yes im starting over again i killed my tattooś boot today and need to recover it from rom.zip fastboot mode oem
[Click Android Development] danfuh:
Thank you very much! It works perfect!
[Click Android Development] vlipper1:
update.zip

you can run update.zip

sending 'zip' (88968 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[boot] unzipping & flushing...
INFOstart image[hboot] unzipping & flushing...
INFOstart image[radio] unzipping & flushing...
INFOstart image[recovery] unzipping & flushing...
INFOstart image[sp1] unzipping & flushing...
INFOstart image[system] unzipping & flushing...
INFOstart image[userdata] unzipping & flushing...
OKAY

this is a PART of the Debug i get from this update.zip i posted on this forum :D

afther it say's okay type fastboot reboot
[Click Android Development] vlipper1:
boot.img

o yes for the people who are confused about killing my boot.img i dit it whit a custom myself not the ones on this forum TY for this mail :eek:
[Click Android Development] pacogf:
Unlocking from Vodafone after root?

Hello.

I've a Tattoo Vodafone locked and I gain root access. Is it possible to unlock from Vodafone? Thank you.
[Click Android Development] 5[Strogino]:
No. Root doesn't affect to unlock) They are different things.

To do unlock, you must go to custom service. They will try flash parameter into special area in the phone.

I don't know how Vodafone unlock own phones, but T-Mobile do it via unlock-code (codes from T-Mobile everyone can buy at ebay.com or other sites)
[Click Android Development] mdusan:
mdusan

yeeeaahhhhh, iI made it !!!!!! My phone remains the root, although it is restarted . . . I used procedure from page 27 and it's works !!!! Thanks to everyone who helped make the phones rooted . . . this is great !!!!!
[Click Android Development] ccgg:
making the system writable

Hi all,

i"m viewing this forum all the time for a long time and i want to thank all the good people who are doing this great work !!

the most important thing for me in the tattoo is to be able to add fonts, but i"m afraid i will damage my phone - as the warning in the 1st page of this thread says...

i know A LOT of people are waiting to change the language of their phones, can anyone please make an easier/safer way to do this for all those out there who cant do it by the instructions in this forum?

thanks! (sorry for my english...)
[Click Android Development] coolbits:
For now you can only do it by the instructions here... there is no other way sorry.
[Click Android Development] sancho_sk:
I just wanted to thank everyone involved in the process.

Freat work, thanks for the new options with my device!
[Click Android Development] thebush10:
i recently got a tattoo branded vodafone uk from a friend...put my t-mobile sim in and it worked....im sure they are already unlocked(for any sim)in uk
[Click Android Development] Serris:
Hokay my head will explode, been reading the whole 36 pages, and i got totally confused. At first I kinda knew what was I doing, now no clue.. Could some one help me a bit? So i get root with "m7" now what if I want permanent root i use the "tattoo-hack.ko" and then I put "su" from the "dangerous part" on tattoo? but then what is this customboot.img from mainfram3 and what is busybox? Sorry for all the questons but I am trying to understand all of it but I can't without additional explenation.

THX TO ALL
[Click Android Development] chtamina:
some noobs questions

I've been able to root my phone thanks guys.

I pushed "su" so until reboot it will be easy to gain root privileges.

I've got some questions:

- I'd like to copy some file from /data/app but "cp" doesn't work and adb pull won't work either with that folder (no problem with system/app). I even tried with root explorer but it failed, why ?

- what's the differences between adb-windows.exe (provided from coburn) and normal adb file within the sdk ?

- installed titanium backup and it doesn't work either

update: yes I ran "# mount -o rw,remount /dev/block/mtdblock3 /data"

thanks
[Click Android Development] vlipper1:
rooted phone and market

I did not have any market anymore so i reflashed my devices htc tattoo whit the update.zip again,,

i rooted my phone again whit the su of magicandroidapps on this forumpost.,

and installed setCPU as move cache to SD card for root users

that's all on my device right now,

again market cannot connect whit server.:confused: ???:confused:

before rooting i had a market??
[Click Android Development] TheSSJ:
at least I can answer that one: use

cat /data/app/FILENAME.apk > /sdcard

To copy an apk to sdcard, it's a workaround, not a good one, but at least you won't get the cross link device error...;)

Greets
[Click Android Development] _olimp_:
Compile a file

Hi. Help me please. I need tun.ko file for my TATTOO (kernel 2.6.29-gf922713). If need I send tun.c
[Click Android Development] segway_:
Ok .... here you are....:)

Hope it work...

cya
[Click Android Development] _olimp_:
Thanks

Thanks, but VPNConections d'not work ((

I go ask Google about this trouble ...
[Click Android Development] -bm-:
Some may have noted it already, I didn't post here or updated my thread for some time. I'm facing some very important tests on my way of getting a doctor of medicine in 2011. So I decided to trap myself into a room with my books. I didn't visit the forum for over a week now and I was very happy to see how development speeds up and goes on. I will be back in the mid of april, then I will enjoy to select a custom rom and install it on my tattoo and hopefully find the time to write howtos or develop some stuff.

Have a lot of fun!

-bm-

:-)
[Click Android Development] poisoned:
Hi everyone!

I've rooted my Tatoo successfully, but I am having a problem now.

I was stupid and deleted /etc/wifi/wpa_supplicant.conf and now I cannot copy my backup of wpa_supplicant.conf back to it's place. I have a root access and / is mounted rw.

I get:

# cat /sdcard/wpa_supplicant.conf > /etc/wifi/wpa_supplicant.conf
cannot create /etc/wifi/wpa_supplicant.conf: not enough memory

But I have 24M memory free.

I haven't experienced any problems yet, I am succesfully connecting to all wifis, but I think that file has something to do on phone.

Thanks
[Click Android Development] LordGiotto:
Have you mounted tattoo-hack module?
[Click Android Development] poisoned:
Yes, tattoo-hack module is installed