Related
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
***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***
***IMPORTANT: YOU PERFORM THIS AT YOUR OWN RISK, THIS MAY VOID YOUR WARRANTY, I NOR ANYONE ELSE IS RESPONSIBLE IF YOU BRICK YOUR DEVICE.***
UPDATE ( 07.28.2010 ) ( for missing command line)
1. first you need to root your Samsung, You can find how on this forum ( search for : Root your Vibrant )
2. download the font package hebdroid_fonts.zip, unzipr it and put on your SD card
3. download terminal emulator from the market.
4. check that you have root access by typing " su " and hit enter. (it will return a " # " if you have access.
5. now the hard part and the long.... you need to type all the following commands on the terminal emulator
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cat /sdcard/DroidSans-Bold.ttf > /system/fonts/DroidSans-Bold.ttf
cat /sdcard/DroidSansMono.ttf > /system/fonts/DroidSansMono.ttf
cat /sdcard/DroidSans.ttf > /system/fonts/DroidSans.ttf
cat /sdcard/DroidSerif-Bold.ttf > /system/fonts/DroidSerif-Bold.ttf
cat /sdcard/DroidSerif-Regular.ttf > /system/fonts/DroidSerif-Regular.ttf
cat /sdcard/DroidSansFallback.ttf > /system/fonts/DroidSansFallback.ttf
reboot
5. be now you should have Native Hebrew support on your Samsung Galaxy ,( web, email, contact , sms, more...)
6. to be actually have the Hebrew Keyboard and able to type Hebrew Letters you need to download AnySoftkeyboard from the market and then the Hebrew add on of the AnySoftkeyboard.
7. confing AnySoftkeyboard to be set up to your language and Hebrew or other multy AnySoftkeyboard language support.
Copy rights for the fonts are in side the ZIP file.
it didnt work for mw, it said in the terminal that no file was found
Sorry I was wrong before, I didnt do it right. I left all the files in the folder instead of in the root. Toda achi
where are you using it? in israel? or USA?
where are you using it? in israel? or USA?
Im using it in the US
Can I use same methods with arabic?
I belive you can.... you Just need the android fonts that have arabic support
I belive you can.... you Just need the android fonts that have arabic support.
and.... than follow that steps... and in the end download the arabic version of the keybord.
good luck
Thank you very much.
Did you forget DroidSansFallback because I didn't see it in code?
best wishes...
i update the guide...
alsatea said:
Thank you very much.
Did you forget DroidSansFallback because I didn't see it in code?
best wishes...
Click to expand...
Click to collapse
thanks....i over look it
i update the guide...
what do you do if you dont have permission?
Hello,
i followed all the instructions and when i tried to install it said i don't have permission. is there a way to get over it?
Thank you.
efisal said:
***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***
***IMPORTANT: YOU PERFORM THIS AT YOUR OWN RISK, THIS MAY VOID YOUR WARRANTY, I NOR ANYONE ELSE IS RESPONSIBLE IF YOU BRICK YOUR DEVICE.***
UPDATE ( 07.28.2010 ) ( for missing command line)
1. first you need to root your Samsung, You can find how on this forum ( search for : Root your Vibrant )
2. download the font package hebdroid_fonts.zip, unzipr it and put on your SD card
3. download terminal emulator from the market.
4. check that you have root access by typing " su " and hit enter. (it will return a " # " if you have access.
5. now the hard part and the long.... you need to type all the following commands on the terminal emulator
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cat /sdcard/DroidSans-Bold.ttf > /system/fonts/DroidSans-Bold.ttf
cat /sdcard/DroidSansMono.ttf > /system/fonts/DroidSansMono.ttf
cat /sdcard/DroidSans.ttf > /system/fonts/DroidSans.ttf
cat /sdcard/DroidSerif-Bold.ttf > /system/fonts/DroidSerif-Bold.ttf
cat /sdcard/DroidSerif-Regular.ttf > /system/fonts/DroidSerif-Regular.ttf
cat /sdcard/DroidSansFallback.ttf > /system/fonts/DroidSansFallback.ttf
reboot
5. be now you should have Native Hebrew support on your Samsung Galaxy ,( web, email, contact , sms, more...)
6. to be actually have the Hebrew Keyboard and able to type Hebrew Letters you need to download AnySoftkeyboard from the market and then the Hebrew add on of the AnySoftkeyboard.
7. confing AnySoftkeyboard to be set up to your language and Hebrew or other multy AnySoftkeyboard language support.
Copy rights for the fonts are in side the ZIP file.
Click to expand...
Click to collapse
you need to root your Samsung
you need to root your Samsung, You can find how on this forum
( search for : Root your Vibrant )
is it possible to copy the files with the help of an app like Root Explorer?
or do i need to follow the steps with the terminal?
thanks
if you can do that so yes...
if you can do that so yes...
the terminal is just a command line to copy the fonts on the existing ones.,,,
i am rooted and copying your commands word for word and it keeps telling me:
/sdcard/DroidSans-Bold.ttf: No such file or directory
What am I doing wrong here?
vega89xi said:
i am rooted and copying your commands word for word and it keeps telling me:
/sdcard/DroidSans-Bold.ttf: No such file or directory
What am I doing wrong here?
Click to expand...
Click to collapse
i bet you had the fonts file in the galaxy internal memory and not in the sd card.
put the font files in sd card !
you must run the command line and point it to the fonts location... in my way i had the fornts in the sd card and pointed the commandline to the sd card.
let me know.
efisal said:
i bet you had the fonts file in the galaxy internal memory and not in the sd card.
put the font files in sd card !
you must run the command line and point it to the fonts location... in my way i had the fornts in the sd card and pointed the commandline to the sd card.
let me know.
Click to expand...
Click to collapse
Figured it out...... yes the files were on the SD card. I may not have a high post count but i have been doing this for a while and know the difference.
I had to edit the string after using a root file explorer to find the exact location.
/sdcard/sd/DroidSans-Bold.ttf
Worked after that.
Still having issues though as it seems that only the bold font copied over as the general font is just showing as squares still....
Hi,
I followed the guide and it works flawlessly - Thank you !
Although I can see, read and write in Hebrew, there are still 2 issues that I am not able to solve:
1) Email subject in Hebrew (when viewed) come up in reverse order.
2) Audio files tagged in Hebrew are presented in gibberish. (In the player)
Anyone else witnessed these issues ? and more importantly, has anyone found a solution for it ?
Thanks !
Worked for me - used adb shell instead of typing into terminal
same problem in subjects of emails - the bodies are presented correctly
I appreciate your work but... It's a very old solution.
can you do it this way:
before all. your device must be rooted!
http://www.mediafire.com/download.php?q18y6ttlrl9h78r
Method 1:
download this file and flash it into the recovery.
Method 2:
search for rom manger in the market and install it
flash the recovery of amon ra.
now select "flash from sd card" and navigate to .zip file
and we finish.
*this Method work for all devices*
Sorry for my English
Archived in the directory
hey did anyone manage to get the keys work with these kernels (KERNELS WITH KEYPAD DRIVERS AS MODULES) in any CWM build?
I try to load it using terminal like before but its not working
even the Gscript method is not working anymore, is there any other solution than restarting the device with KERNELS WITHOUT KEYPAD DRIVERS AS MODULES after each freez, the freez mostly happen after pressing the right option in the keypad or using setCPU
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
saobang3886 said:
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
Click to expand...
Click to collapse
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
kerfooly said:
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
Click to expand...
Click to collapse
OPP!
First, you should boot with kernel without modules keyboard, it easy to setting in first time. try setting all thing who make that build recommend!
Second, in stall Autostart and gScript app. copy autostart.sh to root of your sdcard. open terminal, remove old modules and copy autostart.sh to /data/opt like this post http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
Then open restart keyboard script in your computer, open Gscipt in your phone, add new script, tip name is restart keyboard. Script like the file you open in computer!
after that, restart to window mobile, copy kernel with keyboard as module to your boot folder, replace old file, then reboot and it will work!
Well, after setting up all the scripts for loading and reloading of the kernel modules and then removing all kernel-modules of the old kernel (that without the drivers als module), you have to reboot your device. As part of the boot process, the new kernel modules are copied from the tar.gz-file, without deleting the old modules, this step will be skipped from the boot script.
So.
1. prepare all scripts
2. remove the old modules
3. boot the new 'KEYBOAD-AS-MODULES' kernel with it's module-archtive in place
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory ... the works quite nice and is much cooler that trying to press vol-down in the right moment ... i renamed it then to no_recovery.txt ... makes getting to recovery quite relaxed ...
Ciao
Kurt
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
hopsakee said:
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
Click to expand...
Click to collapse
Yep, here's the code from the init script that's in rootfs.img:
if [ -f /sdcard/npkboot/recovery.txt ]; then
so ... have fun with Android on your X1 .
Ciao
Klaus
Kurt Krummbein said:
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory
Click to expand...
Click to collapse
Ik works. I start into CWM. But the volume buttons still don't respond, and I need those to navigate through CWM.
Anyone a solution other than switching back to standard kernel without seperate modules?
when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
This guide is to show you how to mount network shares using the CifsManager and cifs module for the Galaxy Tab 10.1. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
Any custom ROM using Pershoot's kernel
Superuser access (should be included on a custom ROM because you are rooted)
The CifsManager from Market
The Android Terminal Emulator from Market
The cifs module--->http://droidbasement.com/galaxy/kernels/2636/23/lib-2636.4.tar.gz
Steps:
1. Extract lib-2636.4.tar.gz on your computer
2. Navigate to lib/modules/2.6.36.4-cyanogenmod+/kernel/fs/cifs/
3. Copy cifs.ko to a folder on your tablet (/mnt/sdcard/cifs/ or create a folder that you want)
4. Make sure the CifsManager has the correct path to the location of the cifs module in Settings (e.g. /mnt/sdcard/cifs/ or the folder you created)
5. Launch Android Terminal Emulator
6. Type su (make sure it changes from a $ to #, if it fails check the Superuser app)
7. Type cd /path/that/you/created (e.g. cd /mnt/sdcard/cifs/)
8. Type insmod /path/that/you/created/cifs.ko (e.g. insmod /mnt/sdcard/cifs/cifs.ko)
9. Verify module load, Type lsmod
10. Should be good to go!!
Any questions, let me know!
Ummm...
I don't think steps 5-10 are needed. If you copy the cifs.ko to your SD card and then check "Load cifs module" and check "Load via insmod" and then set the path correctly it works without the rest.
Maybe your way is doing something different?
Yes exactly, loading the kernel module is exactly what cifsmanager is for.
I have a problem.
I want to install AX8MT.Ko but I have to change the modules permission because every time when I write on terminal "insmod/system/lib/modules/ax8mt.ko telling me operation not permitted
I want a step-by-step tutorial for changing modules permission.
I will press thx button!
Sorry for my English!
fuuuuuuuuuuuuuuu said:
I have a problem.
I want to install AX8MT.Ko but I have to change the modules permission because every time when I write on terminal "insmod/system/lib/modules/ax8mt.ko telling me operation not permitted
I want a step-by-step tutorial for changing modules permission.
I will press thx button!
Sorry for my English!
Click to expand...
Click to collapse
You have to enter "su" first - only root is allowed to load or unload kernel modules!
B.Jay said:
You have to enter "su" first - only root is allowed to load or unload kernel modules!
Click to expand...
Click to collapse
I write but the same result
You need Root Explorer for doing this.
You can buy it on the market, or search on google for a cracked apk.
In RE, you go to the folder and long-press on the module, and in the menu choose "change permissions".
I did this but don't work, any ideas?
In Root Explorer, you need to mount the /system partition as rw first.
To do this, click on the small button in the right corner of your screen.
After that, you can set the permissions, delte or edit files and other things you can do in a file explorer
codfreak said:
In Root Explorer, you need to mount the /system partition as rw first.
To do this, click on the small button in the right corner of your screen.
After that, you can set the permissions, delte or edit files and other things you can do in a file explorer
Click to expand...
Click to collapse
I did this because I can't. change permission if I don't press the little button. I want a master member
You know, all you have to do is READ ...
1. Copy ax8mt.ko to your SD card
2. Start Root Explorer and navigate to /sdcard
3. LONG press ax8mt.ko and select "MOVE"
4. Navigate into /system/lib/modules
5. Press "Mount r/w"
6. Select "Paste"
7. LONG press ax8mt.ko and change permissions to
r w -
r - -
r - -
8. Exit Root Explorer
9. Open the terminal
10. Type (followed by enter after each line)
su
insmod ax8mt.ko
Alternatively you can do the whole thing in just the terminal (assuming you already copied ax8mt.ko to your SD card):
Type:
su
cp /sdcard/ax8mt.ko /system/lib/modules
chmod 644 /system/lib/modules/ax8mt.ko
insmod ax8mt.ko
If you can't get this simple thing done you better don't even keep on trying.
B.Jay said:
You know, all you have to do is READ ...
1. Copy ax8mt.ko to your SD card
2. Start Root Explorer and navigate to /sdcard
3. LONG press ax8mt.ko and select "MOVE"
4. Navigate into /system/lib/modules
5. Press "Mount r/w"
6. Select "Paste"
7. LONG press ax8mt.ko and change permissions to
r w -
r - -
r - -
8. Exit Root Explorer
9. Open the terminal
10. Type (followed by enter after each line)
su
insmod ax8mt.ko
Alternatively you can do the whole thing in just the terminal (assuming you already copied ax8mt.ko to your SD card):
Type:
su
cp /sdcard/ax8mt.ko /system/lib/modules
chmod 644 /system/lib/modules/ax8mt.ko
insmod ax8mt.ko
If you can't get this simple thing done you better don't even keep on trying.
Click to expand...
Click to collapse
do you know another mod to enable dualtouch for games.