Database Develop

[GUIDE] All Tattoo questions and answers see here (from A to Z)!

Hi,
this thread is meant as a starting point for every kind of questions. I will write everything I know into this thread and update it (hopefully) frequently
Here are the topics handled for now (if you have any other questions you want to have answered you can PM me, so I can try to handle it if I know the solution and add this to my to do list in point 5!!! ):
1. How can I root my phone
1.1 General information/Basic adb-commands
1.2 Do I have to create a goldcard?
1.3 Tools you need
1.4 The automated way
1.5 The manual way (recommended by the author)
1.6 Problems and (hopefully good) solutions
1.7 References
2. Flashing images/ROMs
2.1 What is a recovery image
2.2 What is a boot image
2.3 How to flash/tools needed
2.3.1 Creating a Goldcard
2.4 Where can I get an overview of the existing ROMs?
2.5 Problems during flashing and solutions
2.6 References
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
3.2 Can it perform multitouch?
3.3 How to increase battery life?
3.4 Using own ringtones for calls/sms
3.5 How to disable data transfer with a custom ROM?
3.6 How to make the Tattoo ring louder?
3.7 How to replace the home screen?
3.8 Disabling xxx-synchronisation with Google-servers
3.9 Backing up apk's and data to your PC
3.10 How to enable more languages on my mobile?
3.11 How to manually delete system apks? Alternatively with GUI?
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
4.2 Modifying resources in apk-files and resigning them
4.3 Installing apks via adb for getting exact error codes if installation fails
4.4 Everything related to ROM cooking
5. Things I will do better in this thread due to user request
Please note: I won't be giving tutorials about Android-apps usage beside the one mentioned in my tutorial!
Let's start now:
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it ;)
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/showpost.php?p=5179788&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Click to expand...
Click to collapse
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>
Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/su
Also make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
PM me with more questions and I'll post them with the possible solution.
1.7 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
- Coburn64's Newbie guide for manual rooting (recommended reading!)
2. Flashing images/ROMs
2.1 What is a recovery image
A recovery image is not only useful to flash custom ROMs on your device. It also enables you to backup your entire phone contents to restore it completely in case of a brick, if anything should happen...especially SIM-locked mobiles should be backed up as soon as possible. Also many recovery image modders add several non-standard features like mounting the SD card while in recovery mode or enabling adb support, etc.
2.2 What is a boot image
The boot image not only contains the kernel which brings up your Tattoos, it only can be modified to load up modules enabling ext2/3 support, loading camera, remapping read only code to an r/w area (tattoo-hack.ko), etc. Without a working boot.img, don't even bother trying to boot the phone (maybe if you do a logcat it returns something useful to solve this problem )
2.3 How to flash/tools needed
Execute steps 1 to 4 in topic 1.5 first!
5. Now comes the hard part:
- # ./flash_image boot /sdcard/boot.img
- # ./flash_image recovery /sdcard/recovery.img
it can be that flash_image reports errors in the last step (recovery.img step), but another user said it would be still working to boot to recovery...but to be sure (if you got the error!!!) flash maverixx recovery.img and then again the one I supplied in my archive (Amon_RA)
Reboot once and when you connect with adb to your phone you should see the difference
Click to expand...
Click to collapse
2.3.1 Creating a Goldcard
This is a post I took from MiSSigNNo, kudos to him:
Creating the Gold Card:
[...]
4. We need the android-sdk tools, we can find them here: http://developer.android.com/sdk/index.html download them, and unzip in a folder maybe in C:\androidtools
5. Go the the Command line (Start->Execute->write cmd and OK), and there you should find where you unzip the android-sdk tools, example cd c:\androidtools\tools
6. Run this command "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" if you had the microSD in the drive you will find a long number like:
532600bd227d9c0347329407514d5402
7. Go to this page to reverse it: http://hexrev.soaa.me/ and copy the code reversed:
In our example it will be: 00544d5107943247039c7d22bd002653
8. Go to this page to generate your GoldCard image: http://revskills.de/pages/goldcard.html
And put your reversed number and you email. You will receive an email with a file called "goldcard.img"
9. Now you need an Hex editor like HXD. Download it from: http://download.cnet.com/HxD-Hex-Edi...html?tag=mncol
10. Exactly the same as the instructions I pasted above:
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK. (BEWARE, MUST BE UNDER PHYSICAL DISK NOT LOGICAL DISK, THIS MISTAKE MADE ME BIG PROBLEMS)
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset (line) 00000000 till offset (line) 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program. You now have a gold card.
[...]
Click to expand...
Click to collapse
2.4 Where can I get an overview of the existing ROMs?
Look it up here (Excellent work liderzre)
2.5 Problems during flashing and solutions
Q: HEEEEELLLPPP! flash_image says that it couldn't write to some memory addresses! What can I do?
A: Don't panic. First make sure to have loaded tattoo-hack.ko, remounted system and data to r/w and then try again with another recovery.img (either maverixx or Amon_RA). Flashing the same recovery.img again WON'T WORK!!!! That's why you have to take a little detour by first flashing another recovery image.
Q: How do I boot to recovery??
A: Type in your command line while the phone is plugged in:
Code:
adb shell "reboot recovery"
. If this doesn't work, turn off your phone, hold down the home-button and press the power-button. Then when the Tattoo logo can be seen, release the home button and the recovery screen should be seen
2.6 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
Load the busybox binary here (select the one with arm6 at the end). Put this binary onto your data or system partition (I suggest /system/xbin) and now there are two ways to install/enable it. See below
Method 1 (will extract EVERY FEATURE, but consumes A LOT of your disk space so be careful or switch to method 2)
Do this in your command line:
Code:
adb remount (make it r/w if not done already)
adb shell "mkdir /system/xbin" (create dir if it doesn't exist)
adb push busybox /system/xbin (please make sure to have busybox in the same directory as adb ;) )
adb shell
cd /system/xbin
./busybox --install
Method 2 (saves your precious disk space )
Do this in your command line
Code:
/system/xbin/busybox --install -s /system/xbin
3.2 Can it perform multitouch?
Nope, the Tattoo has a resistive touch screen, which is known to be NON-multitouch...newer generation or high-end phones usually have capacitative screens. My suggestion is not taking the Nexus One anymore, since their touch screen type supports only 2 fingers at once, while phones like the Samsung Galaxy S have a SUPER responsiveness and sensibility (and of course 10 fingers support).
3.3 How to increase battery life?
Okay, here are little tips how to increase battery life - mine holds 7 to 8 days and I surf, call ppl and sms almost every day:
1. Flash either fyodor 0.6.4.2 or Abyzou 2.1.9 - my favourite is fyodor ones (if I still would have a Tattoo, of course )
2. Download APNd roid from the market or here and disable your 3G Internet connection (for activating it, just start the program again!)
3. If you see that you have NO RECEPTION AT ALL in one place (at work for instance), turn off your phone as this will DRASTICALLY decrease battery life because the phone tries constantly to search for a network it can log on to.
4. Try to keep your phone in normal temperature areas (between 20 and 27 degrees celsius = 68 - 80.6 degrees fahrenheit)
5. Kill unneeded apps automatically (there are quite a few apps doing this)
3.4 Using own ringtones for calls/sms
Create a folder called "media" on the root of your SD card and a sub-folder called "audio" there you have to create one folder called "notifications" for SMS and "ringtones" for call sounds. Place every desired track into these folders and reboot your phone. You should see the entries now when choosing ringtones. Alternatively just load "Ringo Pro", a really powerful tool also able to display SMS pop-ups and much more.
3.5 How to disable data transfer with a custom ROM?
As already explained above, load APN droid from the market or here.
3.6 How to make the Tattoo ring louder?
There is a little app called "Louder Volume Hack" enabling your phone to ring much louder than normally. You can load it on any popular w*rez-site Unfortunately I cannot enter the link to the app here or PM it. Any questions requesting a link to this app will be deleted instantly, so don't bother trying and use Google. There are several buttons displayed, but for better visibility I suggest enabling the Widget and hacking the system there. Also please note that ROOT access is required!! Refer to section 1 to root your phone.
3.7 How to replace the home screen?
There are two ways to do it. Method 1 is the easier one, but runs the Google Launcher and the replacement laucher in parrallel, which implies more CPU usage and battery drain. Method 2 is the more brutal one, but enables you to run just one launcher.
Method 1:
Install the replacement home app and press the home button. A dialog should appear asking you which Home Launcher should be used.
Method 2:
Put your home replacement apk onto the root of your SD and make sure you have busybox installed and /system mounted as writeable. Rename the Home replacement apk to Launcher.apk and fire up adb shell:
Code:
mv /system/app/Launcher.apk /system/app/Launcher.apk.old && mv /system/app/Launcher.odex /system/app/Launcher.odex.old && cp /sdcard/Launcher.apk /system/app && chmod 755 /system/app/Launcher.apk
Should be a pretty generic approach
3.8 Disabling xxx-synchronisation with Google-servers
Go to settings, data synchonisation and disable the entries you don't want to have synch'ed with Google. Since it's long time ago since I did this (remember that I don't own a Tattoo anymore) the procedure can be slightly different from ROM to ROM.
3.9 Backing up apk's and data to your PC
By popular request, here a topic about how to backup apk's and their corresponding data manually (can be done separately, too if you want just one of the two). Doing it with the tar command HOPEFULLY preserves also all permissions!!! Check it:
Hit up adb shell and make sure have busybox:
Code:
for the apks
# tar -cvf /sdcard/dataAppsBackup.tar /data/app
for the data
# tar -cvf /sdcard/dataDataBAckup.tar /data/data
If you want to decompress these files again do:
Code:
# tar -xvf /sdcard/dataAppsBackup.tar -C /data
# tar -xvf /sdcard/dataDataBackup.tar -C /data
Note that these files won't be compressed! If you want to save some disk space on your SD then add the parameter 'z' (without the quotes) in the tar arguments (e.g. tar -cvfz for compressing and tar -xvfz for decompressing)
3.10 How to enable more languages on my mobile?
There is an app called MoreLocale in the market enabling you to select more languages. Download it, it's free
3.11 How to manually delete system apks? Alternatively with GUI?
For deleting manually you only need root-access. With GUI you need RootExplorer (buy it or do what you need to do to get this app-but with these features I would suggest to buy the app ).
Note: I do not take any responsibility if you delete the wrong apk and you lose any functionality of the phone. Do this only if you know what you're doing!
The manual way:
Connect the phone via USB, fire up adb shell and type:
Code:
insmod /LOCATION TO [URL="http://TATTOOHACK.KO/tattoo-hack.ko"]TATTOOHACK.KO/tattoo-hack.ko[/URL]
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
rm NAMEOFAPK.apk
The GUI way:
Install RootExplorer, open it, navigate to /system/app and press the little "Mount R/W" button at the top of the screen and begin deleting
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
See this thread and get enlightened
4.2 Modifying resources in apk-files and resigning them
Same procedure as above:
1. Extract the file with WinRAR/WinZIP, delete the contents of META-INF and start modifying what you have to modify
2. Pack everything again into a ZIP file and sign it with the signapk.jar file (can be found somewhere in the forum or here). The syntax of how to use this can be found in the last link (yes, it's only 10 KB ).
4.3 Installing apks via adb for getting exact error codes if installation fails
Prerequisites: Either know the exact path to the apk or put it into the same directory as your adb executable and hit up your command line:
Code:
adb install /path/to/apk/file.apk
OR
adb install file.apk (implies that apk is located in same dir as adb)
4.4 Everything related to ROM cooking
Check this link (thanks to Decad3nce) and this one (thanks to mxlaser).
5. Things I will do better in this thread due to user request
- Nothing
The end for now.

Note: If you think that my thread is good, then please rate it with 5 stars
Changelog:
Version 1.0
- Initial draft
Version 1.1
- Added complete topic 1 now
- Fixed layout and some typos
Version 2.0
- Added complete topic 2 and half of 3
Version 2.1
- First prototype with all topics finished (will rework parts which are not quite understandable)
Version 2.2
- Added new question to 1.6
Version 2.3
- Added section 4.4 -> Everything related to ROM Cooking DUDEEEESSSSS
Version 2.4
- Added 3.11 How to manually delete system apks? Alternatively with GUI?
Version 2.5
- attached working su file - thanks to lovenemesis for this
Version 2.6
- added some mirrors for the Tattoo.rar archive - thanks to emb0re for providing some space
Version 3
- added topic about creating gold cards (2.3.1)

hi
very good initiative stuck

Great work
Very intuitive guide for beginner.
Though as an experienced and new android application developer, it really took me a whole afternoon to understand every step of the whole process. I am sure this guide would save many others wonderful Saturday afternoon.

Nice Work
Great Work From You Sir. This Will Be Useful for Beginners I Think This Will Save Lot Of Our Time's. And Mods Too

Thanks for the feedback...I hope that I can fill many topics tomorrow
P.S.: Indeed this is meant for the many unexperienced users who desperately want to flash custom ROMs but don't know how to do it...this also spares a lot senseless thread-posts I hope...^^

Dude
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible

3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
Click to expand...
Click to collapse
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.

jagan_3400 said:
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible
Click to expand...
Click to collapse
You mean getting the apk from your mobile on your PC for example?
lovenemesis said:
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.
Click to expand...
Click to collapse
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.

It might be worth to mention this in 3.1 Busybox installation:
Code:
adb push busybox /system/xbin/
I accidentallly use "adb push busybox /system/xbin" without the ending "/". Well, you know the rest part of the story...

Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)

TheSSJ said:
You mean getting the apk from your mobile on your PC for example?
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.
Click to expand...
Click to collapse
Maybe it's because I am using a Fedora box, which the default permission for files in $HOME does not include execution.

lovenemesis said:
Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)
Click to expand...
Click to collapse
You're right, I added it already in the guide, thanks for the feedback. Well, /system/xbin isn't a "normal" directory indeed, but it was created for extra executables which normally aren't shipped in stock ROMs (like busybox).

4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
Click to expand...
Click to collapse
I suppose after this step the stock ROM is rooted. Right?
But in Android Terminal Emulator gives me $ still. "su" reports an link_image error, which basically said about missing libbinder.so library.
Is it normal or I need to push an libbinder.so to /system/lib as well?
BTW: "adb shell " gives me # straightly.
Regards,

Hmm, I pushed another "su" binary to overwrite the one in Tattoo.rar. And now it works fine in Android Terminal Emulator.
Here is the su binary I use:
View attachment su.zip

Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?

market not working
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls

few questons kindly answer
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance

lovenemesis said:
Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?
Click to expand...
Click to collapse
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
haree said:
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls
Click to expand...
Click to collapse
Do you use MoDaCo ROM or did u switch now to another? Normally the phone asks for log-in credentials when going online. When you enter them correctly, the login window should disappear and you should be able to access market...I know this sounds stupid, but check if you entered you PW correctly!
haree said:
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance
Click to expand...
Click to collapse
1. As I told you via PM already: If the ROM is based on the same source ROM (HTC stock in your case) then a wipe is NOT required, but if you switch android version (AOSP, Vanilla, FroYo, Eclair) then you HAVE TO wipe.
2.
a) I had only problems with Titanium backup concerning restoring contacts. I would suggest using MyBackup Pro
b) Well, if you can sync to outlook, then I suppose yes, but I really doubt that these features are implemented in custom ROMs...
3. Well, if you mean restoring the NAND-backup and then flashing another cooked ROM (which are all rooted by default ), then no - you don't need to re-root. Only if you would flash the original/official HTC ROM which comes shipped as exe-file, but I don't see the sense in flashing this one...use your NAND-backups

TheSSJ said:
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
hi
thanks buddy for patiently answering all my Q
i got it now but i dont know why this Bl***dy market does not work what every i try ie when the net is on and ur browsing u see the E on ur phone screen and then the 2 white arrows flash this it self does not happen when i try to log in to market
just dont know what is wrong
right now im using Modoco and happy with it seems to be real fast and everything is working on this ROM
Click to expand...
Click to collapse

[Solved] The Market issues on JH2

I found a thread over in the I9000 section that may explain our problems with the Market on JH2.
http://forum.xda-developers.com/showthread.php?t=757461
This would seem to suggest that if you are running an unreleased firmware you need to replace the build.prop file from the released version in order to fix the market.
I have not tried this yet, I need to find the build.prop file from the original firmware first.

You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Explorer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.

I found this JF6 build.prop file in the stock system dump here. Let's see how this works:
http://forum.xda-developers.com/showthread.php?t=730226

Uploaded the stock build.prop to /system. It seems to make no difference in terms of availibility of the missing apps (only tried Fandango, but still missing). Grrrrr...need solution.

This did work for me. Thanks for the JF6 build.prop file.
This requires a rooted phone. You can brick your phone messing around with root. Not my fault...
I shut down the Market app, cleared its cache in Settings/Applications/Market (Filter select All Files to show Market app).
I added the JF6 build.prop to /system, replacing the JH2 version. I use root explorer to move the file on and off the SD internal.
Changed the permissions back to rw-r-r, using root explorer permissions. When the file is transferred back to the phone from the SD, the permissions will be rw-rwx-rx. Changed ownership back to root.root on the phone using terminal emulator:
$ su
# chown root.root /system/build.prop
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.

daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?

rajendra82 said:
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
Click to expand...
Click to collapse
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.

dontshakepandas said:
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
Click to expand...
Click to collapse
Working now. This is great. Now with the last issue resloved, I can keep the new firmware around. This needs a sticky, with all these weekly firmware releases from samsung-firmwares showing up.

daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Can you post the commands used to do this for users who aren't as knowledgeable.

yes. walkthrough please?
would love to get this working, I don't want to have to flash back to original.

kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
Edited post with details

kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.

One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.

daverup said:
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
Click to expand...
Click to collapse
Either that, or get a full flash of the newly released Froyo firmware with GPS Fix in September (hoping and praying), and flash it forward to the new stock version. Of course, not all parts of the system are fooled. Checking Settings -> About Phone, still shows the correct JH2 information.

Nice. Seems to have worked. Funny, it didn't work until after i installed/ uninstalled a couple items.

thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.

staySICK said:
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
Click to expand...
Click to collapse
I am guessing that your root privilages are not working. Does you phone give you a popup when you do su in ADB shell. If so, tell the phone to allow su privlages to ADB in that popup. If you do, ADB should not complain. If that doesn't work, you have to redo your rooting procedure, as something might be messed up there.

adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.

staySICK said:
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
Click to expand...
Click to collapse
Probably best to ask about this issue in that thread, as more knowledgeable folks might know how to overcome this.

rajendra82 said:
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app.
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
Click to expand...
Click to collapse
This worked for me, one thing to note, when I ran the last command from Root Explorer "# chown root.root /system/build.prop" Root Explorer responded with
chown: unknown user/group root:root
But after restarting and installing/uninstalling a few apps Fandango shows up where it did not before.
Thanks.

Trouble with script for CPU clock changes

So I have my DX overclocked, but I wanted to be able to change the clock while away from my PC if something goes wrong. Currently on boot it sets the CPU to whatever I had it on before powering the phone off. Now I have all setscaling.sh files on my SD card and can't get a script to copy the files over. I can do this long hand in Terminal. These commands are exactly what I typed into Terminal to get the clock rate to change, but when I throw them into a script exactly as typed below I get all kinds of errors, starting with not being able to mount my SD card.
mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
cp /sdcard/setscaling.sh /system/xbin/setscaling.sh
mount -o ro,remount -t ext3 /dev/block/mcblk1p21 /system
setscaling.sh
EDIT:
So I did a little testing, and it looks like even if I mount the system before running the copy command and setscaling.sh they still don't work. Is this just an anti terminal thing, or what? If I type each command by hand they work, but any of them in a script and it either gives me an error, or doesn't. Either way it doesn't do what I want.

Use root explorer to copy the files over to their appropiate system folders. (Remember to to mount r/w or it wont allow you to make changes to the system folder)...then long press the setscaling.sh and hit execute..Now go to SETCPU->autodetect-> now adjust your frequencies as you wish.

zehkaiser said:
So I have my DX overclocked, but I wanted to be able to change the clock while away from my PC if something goes wrong. Currently on boot it sets the CPU to whatever I had it on before powering the phone off. Now I have all setscaling.sh files on my SD card and can't get a script to copy the files over. I can do this long hand in Terminal. These commands are exactly what I typed into Terminal to get the clock rate to change, but when I throw them into a script exactly as typed below I get all kinds of errors, starting with not being able to mount my SD card.
mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
cp /sdcard/setscaling.sh /system/xbin/setscaling.sh
mount -o ro,remount -t ext3 /dev/block/mcblk1p21 /system
setscaling.sh
EDIT:
So I did a little testing, and it looks like even if I mount the system before running the copy command and setscaling.sh they still don't work. Is this just an anti terminal thing, or what? If I type each command by hand they work, but any of them in a script and it either gives me an error, or doesn't. Either way it doesn't do what I want.
Click to expand...
Click to collapse
Here's what i did after reading the original thread.
1. Go to the market and get "Gscript lite".
2. Run Gscript.
3. Press your hard menu button.
4. Press "Add script"
5. Name it anything in the name field.
6. Make sure "Needs SU" has the green check mark.
7. Ignore "Load file"
8. Enter your script in the field...
Code:
insmnod /system/lib/modules/overclock.ko
setscaling100.sh
do not start your script with "su" or "sh" and do not end with either of those. Of course if your file is named "setscaling.sh" then enter that name in the script.
9. save.
10. Optional and handy - go to home screen. Long press. Add shortcut. Scroll to Gscript. Select it. Select the script you created to place a shortcut on your home screen.
11. When ever you reboot- hit the shortcut and it will start you overclocking.
If you want to check that the script executed properly - using "android terminal" from market you can enter...
Code:
su
cat /proc/overclock/mpu_opps
it will lest your clock speeds for you. You can also use gscript to create a script for this. Leave out "su" and enter only the "cat" line.
good luck.

2.2 available!

So 2 days ago guys from 4pda.ru ported android 2.2 on GT540, it is installed on sd card and you can choose between 2.1 and 2.2.
Here is youtube video:
And here is link on thread on 4pda:
PDA

so why would I need to switch between 2.1 and 2.2? I guess this is just a preliminary POC and a custom rom is now in the works.
can't wait! great job russians!

tong.po said:
so why would I need to switch between 2.1 and 2.2?
Click to expand...
Click to collapse
Maybe cos 2.2 isn't supporting FM/Camera/BT right now and is booted from SD.

Thank god for the Russians! And great job finding this.
Sent from my GT540 using XDA App

woo!
could someone make a tutorial?
as the translated russian is'nt easy.

flyboyovyick said:
woo!
could someone make a tutorial?
as the translated russian is'nt easy.
Click to expand...
Click to collapse
Lol 1+
Sent from my GT540 using XDA App

The Rom is not even released yet, nor it will be released soon. Its in I wouldnt even call it Alpha version yet.

You can find some info there:
http://twitter.com/#!/ZduneX25/status/6643977159708672
__________
Written with Tapatalk on GT540

gonna make a video and read tut of it
and some video of it working ofcourse!

ported only basic functions, engineer version posted atm... No final version...

Direct link to some work and explanation in russian is here: http://4pda.ru/forum/index.php?showtopic=200838 But it is stated as version for developers and professionals only, because it is lacks some functions, half working wi-fi, some problems with bluetooth and it's still in test mode. You will need to format your sd card, make your phone able to load in fastboot mode and one package for dual booting from above link.
You will need following apllications:
Dual boot loader from here: http://narod.ru/disk/122844001/ankuch2.2-oss.img.html
Copy of /system folder: http://narod.ru/disk/41926001/ankuch2.2.tar.html
1. Prepare your sd card
type of disk MBR;
part0/primary - fat16 - sdcard - 128MB+. No reason to create more;
part1/primary - ext2 - system - 256MB+, you can put more if you will put some applications in /system/app;
part2/primary - ext2 - data - 256MB+.
I recommend it to partition in 10/10/80.
If you got a big card and use phone to view video, you can make first partition bigger.
2. After SD card prepare, you will need to load and copy content of /system folder from ankuch2.2.rar archive
Making final phase in 2.1:
1. Mount /system in mode r/w (you can mount it, for example, from RootExplorer - select /system and press button mount r/w)
2. adb shell
3. su
4. mkdir /system/s8
5. mount -t ext2 /dev/block/mmcblk0p2 /system/s8
6. cd /system/s8
7. busybox tar -x -f /data/ankuch2.2.tar
Loading 2.2:
Enter fastboot mode
We load 2.2 - fastboot boot ankuch2.2.img
No loading animation yet, you will need to wait until will be filled content of /data folder
First load can take a long time, you can control it thru adb shell logcat.
adb, btw, I did in first time and from root it loads.
Sorry for mine english Fast translation
Problems and some solutions to avoid them:
1. How to put data transfer?
adb shell
stop ril-daemon
start ril-daemon
-- Can be some problems with APN not loading from SIM card, so you will need to put configuration manually.
-- Connection always will be like EDGE, even if really you getting HSDPA
2. How to get rid of lag in transitions?
Try this:
Spare Parts -> Window animations -> Off
Spare Parts -> Transition animations -> Off
Once I got bugged rild, loaded cpu to 100% and almost halted all apps, thats why from link in russian forum you will see some pics of processes.
You can turn it on:
Dev Tools -> Development Settings -> Show running processes
Changed those options too:
Dev Tools -> Development Settings -> Disable compatibility mode (requires to reboot device)
After this author does not get any hangs.
3. How to connect to Wi-Fi
It is required to copy from your 2.1 file wpa_supplicant.conf to /data/misc/wifi (in this file it is saved all your information about connections)
Change permisions from file chmod 777 /data/misc/wifi/wpa_supplicant.conf (author did not tested more secure permisions) or reboot device
rest in here -> Settings->Wireless & network->Wi-Fi (turn on Wi-Fi)

[Q] Stuck at "Touch Android To Begin" after reboot

I rooted my DS7 and changed the "phone.apk" name, and I couldn't get past "Force Close" message, so I reset (Vol+ + Power?).
I got the option of "0. Boot", "1. Wipe"..., and selected 1.
Rebooted and was stuck at "Touch Android To Begin" - Android turns white, but does not move forward.
I reset and selected a different option of complete wipe of internal and personal data.
Rebooted and am still stuck at "Touch Android To Begin".
Any suggestions?
I have 2 SD7's, so do I need to back up a ROM off the good one and reflash the stuck one? If so, how would I do that?

Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).

Z4nd4r said:
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Click to expand...
Click to collapse
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore/clear cache have changed all of that...by replacing all files/kernal/rom to factory?

S4F4M said:
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore have changed all of that...by replacing all files/kernal/rom to factory?
Click to expand...
Click to collapse
Wipe/restore, if I understand it correctly, only wipes out cache and data; basically, all of your personal information and files for apps and such (not your SD card). This leaves the kernel as it was.
Do you have CWR on there? If so, simply install a new ROM. If not, you can flash it on there via ADB, I think (check the CWR thread).
Your other option is to change the file name via ADB, or push a new one to it. I've uploaded the stock Phone.apk here:
http://www.megaupload.com/?d=EEBPHB4H
You can push it by doing
Code:
adb push Phone.apk /system/app
I think there's an adb command to simply rename, but I don't recall what it is. Once you do this, you ought to be good to go. Get signed in, then change/move both the apps and restart. It might be annoying with the force closes; not sure if you'll have to use the pinhole reset.
Good luck!

Thanks, Z4nd4r! I'll give it a whirl.

I just moved/deleted the files to test it out (and run some battery tests). I had the force close issue to the point that I couldn't do anything, so I used the pinhole reset. Booted up fine and no cell signal, just as it ought to.

What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.

S4F4M said:
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
Click to expand...
Click to collapse
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!

Z4nd4r said:
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Click to expand...
Click to collapse
Oh, I did. What was left out of the procedure I found was the mention of continuous FORCE CLOSE and the use of the pin reset.
I will write up detailed instructions for a new thread in case anyone else wanted to know.

I know this is a really old thread, but I am stuck on this as well in the same situation that the OP had. However, SuperOneClick 2.2 and 1.55 both seem unable to root the streak so I can use the adb server to push the proper apk back! Anyone have any advice? I need to rename or push both TelephonyProvider.apk *and* Phone.apk. I have tried using adb and of course it errors since the device is unrooted.

turn device vertical.
start upper right touch
lower right touch
lower left touch
upper left touch