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
Verizon's third 4G Android smartphone is out today. I think that it is worth having a separate for development here, eh?
I second this request
I agree. This is a solid phone.
I also agree to it's own forum
agreed, especially with the fact that it's rooted now, def needs an area here!
stetsonaw said:
agreed, especially with the fact that it's rooted now, def needs an area here!
Click to expand...
Click to collapse
How hard was it to root? Was the bootloader unlocked or just an easy unlock?
I was trying to decide between the Thunderbolt and the Revolution(not a samsung fan).
LG doesn't seem or want to lock anything down! Hurrah!
How is the battery life on that phone compared to the thunderbolt? Better, worse, or indistinguishable?
This device was so easily rooted. Time for the custom ROM's for this device...
Sent from my Droid using XDA App
Windows ADB Root Method
Speaking of easily rooted...
Remember, I am not at fault if you brick your phone, now, proceed.
I updated the Rootzwiki page with the same info found below for rooting via Windows... see the rootzwiki for the Linux steps.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb user' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/rage
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
(permissions name access filesize date time filename)
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out!
One the Revo gets its own section, I'll post this there.
qipengart said:
Verizon's third 4G Android smartphone is out today. I think that it is worth having a separate for development here, eh?
Click to expand...
Click to collapse
I totally agree
Does SuperOneClick rootig method work on this particular device?
Sent from my DROID2 using XDA App
From what i've been told, yes it does... newest version using the gingerbreak exploit. (gingerbreak app does not work)
Or you can do it the long way...
LG Revolution Root the Windows ADB way
Played with this device and actually thinking about procuring it. After all, since rooting is so easy, wifi tethering should be easy to procure and with 4G blazing fast.
An answer would do me great justice....thanks!
We want a section for the lg revolutionaires!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!yeah!!!!!!!!!!!!!!!!!!!!!!!:d:d:d:d:d
Revolution section likely coming soon. It's "likely" and not "definite" because we're still trying to determine whether there's enough interest towards this device.
svetius said:
Revolution section likely coming soon. It's "likely" and not "definite" because we're still trying to determine whether there's enough interest towards this device.
Click to expand...
Click to collapse
That's good to hear! I will voice my support for a Revolution forum. I'm loving the device so far - it's a solid phone that seems to be more than the sum of it's specs, and honestly I like the hardware build more than my OG Droid.
not sure if where allowed to post links, but androidcentral has a little community going already. The root thread has over 2k views alone. Seems like that should be good enough sign for a thread started here.
http://forum.androidcentral.com/lg-revolution/
Its definitley a solid device.
I upgraded from the Droid1 to this, and this phone is great! Loving it so far. I don't know if I want to go the custom rom route with this phone, but it would be nice to have some developer interest and some options down the road. I sure hope the Rev picks up interest because it really is a good device. With that said, I think the Rev having its own section can only help to increase awareness and interest in this phone.
svetius said:
Revolution section likely coming soon. It's "likely" and not "definite" because we're still trying to determine whether there's enough interest towards this device.
Click to expand...
Click to collapse
I went from a G2x to the Charge and finally settled on a Revolution. I guess I was just spoiled by those phones having their own forums... I am totally lost now... no home. Anyways, yes there is interest.
RE: Possible New Rooting Method!
can't post to thecubed's original thread on the development subforum (not enough posts)....
http://forum.xda-developers.com/showthread.php?t=1127223
received replacement phone yesterday (had usb issues). it did not yet have the update installed....was still running V4. performed these steps...
1. installed verizon usb drivers
2. obtained adb access (needed to toggle usb debugging--device originally showed as offline)
3. verified # (see thecubed's post)
4. adb push su /system/bin/su
5. adb shell
6. # mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
7. # chmod 6755 /system/bin/su
8. verified correct permission on su
9. # reboot
10. downloaded superuser from market
easy as pie....no exploit required!
Only workrd on v4 though? Not v6?
i unfortunately did not attempt it on my original phone....only the new (v4) one.
I tried it on a version 6 phone and it does not work.
Ahh shucks....
Sent from my VS910 4G using xda premium
Help!
Hi all -I have been up all night , I will admit I am new at this , and I have been reading and researching on this forum for a bit now -but I need a hand if anybody is interested in helping....I am mid-trying to root my LG revolution , V6.....I have gotten into a few different steps/methods and I think they are correct for the most part - but I am a little hazy about a few things.... I installed android-sdk-windows , then opened up the .exe SDK manager, and installed some revisions? Then went into cmd and did a few steps theads- I did the shortcut posted on this thread - and then tried the longer version and now I am stuck in the middle of both! LOL
mikeymax said:
Hi all -I have been up all night , I will admit I am new at this , and I have been reading and researching on this forum for a bit now -but I need a hand if anybody is interested in helping....I am mid-trying to root my LG revolution , V6.....I have gotten into a few different steps/methods and I think they are correct for the most part - but I am a little hazy about a few things.... I installed android-sdk-windows , then opened up the .exe SDK manager, and installed some revisions? Then went into cmd and did a few steps theads- I did the shortcut posted on this thread - and then tried the longer version and now I am stuck in the middle of both! LOL
Click to expand...
Click to collapse
You cannot root your v6 phone at this time. You will have to down grade the phone to v4 then root it. Every attempt to root the v6 with the v4 methods results in "permissions denied"
v6 fixed the exploit used to allow root.
This guide will show you how to install the V6 SuperCharger script on the Ideapad K1. This script was created by zeppelinrox. I am in no way responsible for any part of this script. This guide is just how I chose to install and configure the script on my K1. Please feel free to experiment with different options, this was meant as a basic setup.
This will work on
Ideapad K1 Honeycomb Rooted 120109 R2 (Must have the R2 update)
http://forum.xda-developers.com/showthread.php?t=1564002
-or-
Ideapad K1 CM9 port
http://forum.xda-developers.com/showthread.php?t=1528775
Before starting please read the entire first post here:
http://forum.xda-developers.com/showthread.php?t=991276
If you like the script make sure you hit "Thanks" on that thread
Keypresses will be in BLUE
Honeycomb specific instructions will be in RED
CM9 specific instructions will be in GREEN
Download the latest version of the V6 SuperCharger script here:
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
If using CM9, download the modified services.jar file and flash via recovery before starting the guide:
http://goo.im/devs/khanning/k1/modded_services-jar_K1_CM9_ALPHA-1.6.zip
1.
If using adb
Code:
adb remount
adb push V6_SuperCharger_for_Android-Update9_RC8.2.sh /system/xbin
adb shell
If using a terminal emulator
Code:
su
mount -o rw,remount /system
mv /sdcard/Download/V6_SuperCharger_for_Android-Update9_RC8.2.sh /system/xbin
2.
Code:
chmod 755 /system/xbin/V6*
3.
Code:
/system/xbin/V6*
--
Is Home is Locked in Memory?
If it is, Enter Y for Yes, any key for No...
Just say "No" if you don't know: [ENTER]
--
Press the Enter Key... and Come Get Some!! [ENTER]
--
Scrolling Speed Options...
==========================
1 (fast), 2 (normal), 3 (slow)
Please select scrolling speed (1 - 3): I chose 2 here, but you can select any [2] [ENTER]
--
Do you want to use Build.prop...
...or create /data/local.prop?
Enter (B)uild.prop or any key for local.prop: [ENTER]
--
Run Fix Emissions on boot?
Enter N for No, any key for Yes: [ENTER]
--
Press The Enter Key... [ENTER]
--
Integrate? Enter Y for Yes, any key for No: [y] [ENTER]
--
Enter Y for Yes, any key for No: You decide, this is the V6 SuperCharger animation when you run the script
--
...Press the Return or Any Key: [ENTER]
--
Apply SuperMinFree Calculator Settings?
Enter Y for Yes, any key for No: [y] [ENTER]
--
Press The Enter Key... [ENTER]
--
================================================
...SuperClean & ReStart!
================================================
Press The Enter Key... [ENTER]
--
Do you want to SuperClean & ReStart now?
Enter Y for Yes, any key for No: If your using Honeycomb you MUST follow the step below before saying yes here. [y] [ENTER]
FOR HONEYCOMB
if using adb
Open another terminal window and run
Code:
adb shell rm -r /data/firstboot
if using a terminal emulator
Open another terminal tab by tapping the "+" in the top right corner and run
Code:
su
rm -r /data/firstboot
Now go back to the first terminal window and press [y] [ENTER] to run SuperClean and reboot
Click to expand...
Click to collapse
Thats it!! The V6 SuperCharger script should now be enabled.
To check that it's running:
The script sleeps for 90 seconds before it starts the service so make sure the system has been fully loaded for at least 90 seconds.
1.
Code:
adb shell
or
open a terminal emulator then
Code:
su
2.
Code:
/system/xbin/V6*
--
Is Home is Locked in Memory?
If it is, Enter Y for Yes, any key for No...
Just say "No" if you don't know: [ENTER]
--
Press the Enter Key... and Come Get Some!! [ENTER]
Click to expand...
Click to collapse
3. Now make sure you see:
================================================
SuperCharger Level: 100% SuperCharged!
================================================
If so, your all set. If not, smack your face against the keyboard and come join me in freenode IRC room #ideapad-k1
Thanks to zeppelinrox for creating the V6 SuperCharger script. Please be sure to hit "Thanks" at this thread if you like his work.
Can you notice a difference? It was debatable if it helped on the Nook Color, how's it look on the K1 with much better hardware.
Thanks a lot....I just ****ed up my K1 with this **** a second time.
I did stick 100% to your directions....all went fine till the reboot...and then I get thousands of force closes....cant do anything.
I did it the original way in the v6 topic.
I did it your way.
Edit:
Damn I forgot this:
FOR HONEYCOMB
if using adb
Open another terminal window and run
Code:
adb shell rm -r /data/firstboot
if using a terminal emulator
Open another terminal tab by tapping the "+" in the top right corner and run
Code:
su
rm -r /data/firstboot
Now go back to the first terminal window and press [y] [ENTER] to run SuperClean and reboot
---------- Post added at 11:21 PM ---------- Previous post was at 10:41 PM ----------
Update:
thanks it runs....the last part was the problem....will test over the weekend.
Does this really work? That original thread reads (and looks) like an infomercial, LOL. Does your Google Play Store still work properly afterwards?
I installed RAM Manager Pro on mine and was using it for a little while, but then I started noticing that I couldn't update any of my apps through the Play Store. They would constantly say "Downloading..." and nothing would happen. They never got to a KB download counter. When I uninstalled RAM Manager Pro, app updates started working again for me.
ssl123 said:
Does this really work? That original thread reads (and looks) like an infomercial, LOL. Does your Google Play Store still work properly afterwards?
I installed RAM Manager Pro on mine and was using it for a little while, but then I started noticing that I couldn't update any of my apps through the Play Store. They would constantly say "Downloading..." and nothing would happen. They never got to a KB download counter. When I uninstalled RAM Manager Pro, app updates started working again for me.
Click to expand...
Click to collapse
Yes, it works fine. I just installed 1 app and updated a bunch
send by K1
It works. I also just updated some apps and installed a new game from play store (yes I did force the update). Firefox runs faster. Everything "feels" more fluid.
sent from my Ideapad K1 with Tapatalk v2
Twist79 said:
Firefox runs faster. Everything "feels" more fluid.
Click to expand...
Click to collapse
Thanks for the info and thank you Khanning for everything you've done to make the K1 a better device!
Makes a great differance even with rooted HC rom which is already very stable and fast.... Thanks KHanning
************
This mod' has been updated to support AOSP only if you are running freeza's latest BEAST MODE KERNEL which contains a folder named "gnfre3" in the /system/etc directory. The methods of installation are the same. The file you are replacing for AOSP (after flashing his kernel) is /system/etc/gnfre3/war_mods.sh
So, see below for instructions. And any commands applicable to file paths for the /system/etc/init.qcom.post_boot.sh file, just change to the AOSP-specific ones above.
Make sure you download the correct variant... for both AOSP and stock ROMs, you'll have a 4 GB and 6 GB option
***************
Well, this device is a breath of fresh air? Wouldn't you guys say? 128 GB ROM, 6 GB RAM and a monster of a processor!
That being said, custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the ZTE Axon 7 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled.
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
The above command can also be executed in recovery terminal.
IT IS IMPORTANT THAT YOU USE THE CORRECT VERSION (RAM), AS THIS COULD HAVE UNDESIRABLE PERFORMANCE IMPACTS OTHERWISE... however, nothing will be permanently damaged, this won't turn your device into a paperweight.
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters - disabled
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio and dirty_background_ratios, set swappiness value to 100, and other parameters of the virtual machine have also been adjusted, such as vfs_cache_pressure.)
- (Above) you will have as much available RAM as possible for your apps. This will reduce redraws if you are a heavy user. If you'd like to test this, reboot, and check your available RAM in the settings
- Enabled zRAM for all variants
- remapped minfree parameters for LMK (low memory killer) for 6 GB variants only
- Set scheduler to CFQ
- Tuned CFQ scheduler for flash storage devices
- Turned off core_ctl for BEAST MODE kernel.. you can enable this if you'd like, just know what you are doing. There are commented out lines of code near the bottom of my scripts to enable or disable it.
- Added an option to change GPU governor to simple_ondemand (again there is a commented out line at the bottom of each script, just remove the "#" symbol and blank spot right before the line. simple_ondemand is more power-friendly GPU governor, with a very small hit on performance
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
There are two main folders found in the unzipped package. One for the 4 GB variant, one for the 6 GB variant. Only use files from the appropriate folders for your device. Each of those two folders has 3 sub-folders: ondemand, conservative, interactive… this is where you will find the various init.qcom.post_boot.sh files
Note: magisk users, see this post https://forum.xda-developers.com/showpost.php?p=72144888&postcount=286
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the zip file to your device, open up a file explorer (must have root capability) unzip the package, grab the file you want to use, navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
Links below
STOCK
6 GB
4 GB
AOSP (Using Latest Beast Mode Kernel with the /System/etc/gnfre3 folder present)
6 GB
4 GB
This is absolutely awesome! I have the 4GB model so I'm curious to take it for a spin once you upload. Happy to see devs cranking out goodies for this device! Thank you sir!
Sent from my ZTE A2017U using Tapatalk
dcscorpio76 said:
This is absolutely awesome! I have the 4GB model so I'm curious to take it for a spin once you upload. Happy to see devs cranking out goodies for this device! Thank you sir!
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Gotcha, bro. Its up... check it out
warBeard_actual said:
Gotcha, bro. Its up... check it out
Click to expand...
Click to collapse
Awesome. I'm on it. I'll report back tomorrow! Thank you bro!
Sent from my ZTE A2017U using Tapatalk
warBeard_actual said:
Well, this device is a breath of fresh air? Wouldn't you guys say? 128 GB ROM, 6 GB RAM and a monster of a processor!
That being said, custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the ZTE Axon 7 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
IT IS IMPORTANT THAT YOU USE THE CORRECT VERSION (RAM), AS THIS COULD HAVE UNDESIRABLE PERFORMANCE IMPACTS OTHERWISE... however, nothing will be permanently damaged, this won't turn your device into a paperweight.
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience)
- disabled zRAM (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power)
- remapped minfree parameters for LMK (low memory killer)
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
6GB VARIANT
4GB VARIANT
Click to expand...
Click to collapse
This will compliment my kernel nicely bro. Thanks.
freeza said:
This will compliment my kernel nicely bro. Thanks.
Click to expand...
Click to collapse
My bro freebro over here just quoting entire OP because he literally just doesn't gaf.
I swear if you don't drop me a link tonight we're fighting to the death, bro.
Dont have the file .I have only this file init.qcom.bt.sh .Is it right?
Thank you , Getting excited about all Devs coming to this device
Kevinkuensken said:
Dont have the file .I have only this file init.qcom.bt.sh .Is it right?
Click to expand...
Click to collapse
same here
Guido83 said:
same here
Click to expand...
Click to collapse
Are either of you on LOS? If so, that could be why.
warBeard_actual said:
Are either of you on LOS? If so, that could be why.
Click to expand...
Click to collapse
Resurrection Remix
Guido83 said:
Resurrection Remix
Click to expand...
Click to collapse
Well that's why. The file doesn't exist on that build. You won't be able to use it, unfortunately.
Im on aokp
Installed via ssh.
Everything seem to work great. i didn't really see a difference till now. But i'm sure it's a good mod. Thank you
awesome! glad to see more devs on this device. also, funny line you added at the beginning of the file. thanks? i guess....
after this command "mount -o remount,rw /system", the terminal says "mount:Read-only file system"
I don't know if my unit was rooted systemless or not. does it matter?
update: nevermind post above.. i just did the steps using TWRP terminal..
Thanks OP!
BTW, will this mod affect AKT Profiles? I am using project zhana battery atm.
@warBeard_actual could it work if put on /data/local renamed as userinit.sh? Seems on LOS (and other maybe based on aosp) there is a file in /system/etc/init.d/*userinit that would run that script post boot - http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Or this script should work only on official ROM? Thanks
I'm curious about the AKT as well. I'm also on Zhana project?
Sent from my ZTE A2017U using XDA-Developers Legacy app
Does this work on LineageOS? or only on B15(stock)?
I immediately notice snappier response from phone. Number of my apps open much more quickly