Related
SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps
adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..
Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.
how do i install an apk file right to my phone using the "cmd"
jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk
n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.
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
As i see a lot of threads about wrongly partitioning internal sd card with cwm and having mbr checksum error or lost space in it at it should be 13.02Gb And 1.85gb in system i decided to put a walkthrough as to how to get it fixed once and for all.
Req.ODIN, Android sdk and Samsung usb drivers for Galaxy s Phones+ CWM Recovery.
Ok, lets start
Connect phone to computer via USB lead
Reboot into Recovery Mode
Type: adb shell in the cmd prompt window
Type: parted /dev/block/mmcblk0
Type: print
Type: rm 1 then rm 2 then rm3 erase all partitions on the sd card
Type print and check if there are any partitions left, if so repeat rm x number untill none are there.
Then quit and exit
Download this:
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Regards
looks useful i dont really need this at the moment but im pretty sure this will help alot of people
Demetris,
I will try this fix this weekend old friend, I will let you know!
demetris_I said:
As i see a lot of threads about wrongly partitioning internal sd card with cwm and having mbr checksum error or lost space in it at it should be 13.02Gb And 1.85gb in system i decided to put a walkthrough as to how to get it fixed once and for all.
Req.ODIN, Android sdk and Samsung usb drivers for Galaxy s Phones+ CWM Recovery.
Ok, lets start
Connect phone to computer via USB lead
Reboot into Recovery Mode
Type: adb shell in the cmd prompt window
Type: parted /dev/block/mmcblk0
Type: print
Type: rm 1 then rm 2 then rm3 erase all partitions on the sd card
Type print and check if there are any partitions left, if so repeat rm x number untill none are there.
Then quit and exit
Download this:
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Regards
Click to expand...
Click to collapse
Having the same issue with my galaxy tab. Its showing only 209mb available out of 12 gb plus. Will this work with galaxy tab or do I need to download any other file?
Nope, Tab is another beast to master, just a first name match "Galaxy"
corpsetomb said:
Demetris,
I will try this fix this weekend old friend, I will let you know!
Click to expand...
Click to collapse
Hey buddy, any news?
demetris_I said:
As i see a lot of threads about wrongly partitioning internal sd card with cwm and having mbr checksum error or lost space in it at it should be 13.02Gb And 1.85gb in system i decided to put a walkthrough as to how to get it fixed once and for all.
Req.ODIN, Android sdk and Samsung usb drivers for Galaxy s Phones+ CWM Recovery.
Ok, lets start
Connect phone to computer via USB lead
Reboot into Recovery Mode
Type: adb shell in the cmd prompt window
Type: parted /dev/block/mmcblk0
Type: print
Type: rm 1 then rm 2 then rm3 erase all partitions on the sd card
Type print and check if there are any partitions left, if so repeat rm x number untill none are there.
Then quit and exit
Download this:
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Regards
Click to expand...
Click to collapse
this will remove the MBR Error even though i flash to stock?
Not yet. Haven't had time to try this, inundated with school work. I will keep you posted!
kazumahits said:
this will remove the MBR Error even though i flash to stock?
Click to expand...
Click to collapse
Yeap it will, hopefully.
Don't forget you have to push parted (Thanks to Demetri for this...)
here is parted for you
http://www.multiupload.com/CA5NCRMBPC
adb push c:xxx/sbin
do it for all files in the parted.zip after you unzip it
su for become superuser
then
chmod 0755 /sbin/xxx for every file in parted.
cd /sbin then run parted
you will have this:
>(parted)
type print
>(parted)print ->enter
Now you will see 3 partitions
/system /data /swap
>(parted) rm 2
>(parted) rm 3
You cannot remove system
Then
>(parted)quit
exit
exit
run odin with repartition enabled! <-you need pit file
Enjoy and hit thanks button again lol
Regards
Edit: If this dont work you need cwm then format \system from cwm then re-run odin with repartitions enabled
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
Demetris,
Now I am trying to push parted onto my phone but it gives me the error "cannot push" read only. Ugh.
No need for parted do as i described on the OP
When you are in Recovery you have parted from it
So you dont need to install parted on phone and you are able to delete everything on the Flash because nothing depends on it like parted executed from phone.
So you will be able to delete /system also.
Sweet, thank you! I am not going to try it for a while cause I have my phone setup the way I like it, but when I do I will drop a line!
ok i spent the night trying to do this no luck , i installed the sdk and i dont no how to get it to work i try typing in the window but it doesnt work can u make a video and put it on youtube please kuz i really dont no what else to do i odin 5 times and partition the phone 4 times no luck with any of that
Here is adb for you
http://www.multiupload.com/771UH8720L
Unrar it to c:\
Open cmd window go to \
cd adb
and then adb shell.
demetris_I said:
Here is adb for you
http://www.multiupload.com/771UH8720L
Unrar it to c:\
Open cmd window go to \
cd adb
and then adb shell.
Click to expand...
Click to collapse
just tried it the cmd window says no the system can not find the path specified
start ->run->cmd then
cd \
cd adb
adb shell
If you have 7, start, search bar, write cmd then enter then:
cd \
cd adb
adb shell
Just for your information... In the recent Android SDK (I discovered this recently) the ADB tool isn't installed by default. To install it, follow the directions below.
In Windows Explorer navigate to the Programs Files directory where you installed the Android SDK. Then go to "Android\android-sdk\tools" and then run "android.bat". A window should appear. On the left side of the window you will then find a list with an item called "Available Packages", click it. Under "Android Repository" find an item called "Android SDK Platform-tools, revision (something)", check it and then click the "Install Selected" button below. Once that's done exit out of the window.
Now browse to "Android\android-sdk\platform-tools". You should now see adb.exe. Mind you, the "platform-tools" folder didn't exist before you did the stuff above.
Why they did this, I have no idea other than frustrating us users.
trparky said:
Just for your information... In the recent Android SDK (I discovered this recently) the ADB tool isn't installed by default. To install it, follow the directions below.
In Windows Explorer navigate to the Programs Files directory where you installed the Android SDK. Then go to "Android\android-sdk\tools" and then run "android.bat". A window should appear. On the left side of the window you will then find a list with an item called "Available Packages", click it. Under "Android Repository" find an item called "Android SDK Platform-tools, revision (something)", check it and then click the "Install Selected" button below. Once that's done exit out of the window.
Now browse to "Android\android-sdk\platform-tools". You should now see adb.exe. Mind you, the "platform-tools" folder didn't exist before you did the stuff above.
Why they did this, I have no idea other than frustrating us users.
Click to expand...
Click to collapse
man im sorry i see everything u talking about but the cmd window is still not working at all it says device not found
Hey Demtrius I, I followed your instructions in the post exactly, did parted and rm1 and rm2 but I still get the MBR checksum error.
My phone is showing the System at 1.73gb and the storage at 13.43. I was using voodoo lagfix before.
Can you help me out?
protohamster said:
Hey Demtrius I, I followed your instructions in the post exactly, did parted and rm1 and rm2 but I still get the MBR checksum error.
My phone is showing the System at 1.73gb and the storage at 13.43. I was using voodoo lagfix before.
Can you help me out?
Click to expand...
Click to collapse
You didnt partition the internal sdcard correct, what pit file you use?
Storage cant go 13.43 max i saw is 13.03GB ,this is what is wrong and the MBR checksum error trigger.
Are you sure you removed all the partitions?
Re install CWM and do this from CWM in recovery by adb as OP
Type: parted /dev/block/mmcblk0
Type: print
And post here your output.
Thanks
ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
[COLOR=Black]SETX PATH "%PATH%;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\platform-tools;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\android-sdk-windows\tools" -m[/COLOR]
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. However, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
Reserved
Reserved Once More
Last One
Reserve the guide
install full rom
how to install a full rom from adb?
Pretty sure it's impossible. Sorry.
Sent from my E15i using XDA Premium App
Perfect Guide to use ADB Commands..
It is very clear and perfect guide to use ADB commands.. I tested this all and works fine..
You can use apks to do logcats from the phone too, I use catlog.
About Broadcom being open sourced made me laugh hahaha.
open source broadcomm, i see what you did there .
Updated OP
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Android-fany said:
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Click to expand...
Click to collapse
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
iamareebjamal said:
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
Click to expand...
Click to collapse
I already reinstalled it like 5 times. Still doesn't work.
Android-fany said:
I already reinstalled it like 5 times. Still doesn't work.
Click to expand...
Click to collapse
Which Windows?
Which ROM?
iamareebjamal said:
Which Windows?
Which ROM?
Click to expand...
Click to collapse
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Android-fany said:
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Click to expand...
Click to collapse
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
AW: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
iamareebjamal said:
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
Click to expand...
Click to collapse
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Android-fany said:
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Click to expand...
Click to collapse
Very strange
Download My Phone Explorer and check if its working!!
Its just 2mb-6mb
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Over the last few months development on the LG L90 has made some great strides, up to the point where we can actually install roms! In order to do this, however, you'll need an unlocked bootloader.
The problem that arises is that there are different models of the L90, being the D405, the D405n, the D410 and the D415. For most of the models the unlock process is very similar, but for the D415 another method is needed.
This guide is aimed at explaining the entire unlock process in a complete and simple way, so even if you have no experience flashing custom recoveries or roms at all, you should still be able to follow this guide. If you run into problems, please just post a reply or send me a PM and I'll do my best to help you.
First of all I'd like to note that I did not develop any of the bin files or apks in this guide, I'm only collecting all the unlock methods in one place for easy reference. Therefore I am not responsible for you bricking your device or causing any kind of damage to it. You follow this guide AT YOUR OWN RISK! That being said, let's get to the unlocking!
What you'll need to unlock the bootloader
1. A rooted LG L90
You can root the phone by going to https://towelroot.com in your mobile browser and tapping the lambda sign. Save and install the apk (make sure unknown sources are enabled in "menu > general > security"). Google will warn you about the app, this is because of the exploit which will enable the root access. Execute the program and tap "make it ra1n", then install supersu from the play store. Open supersu and choose to rebuild the binaries. This will fail, but after a reboot supersu should be installed and working properly.
UPDATE: If towelroot doesn't work for you, you've probably got the L90 with an updated firmware. In that case you can follow this guide by @gdjindal to obtain root access. Afterwards you can follow the rest of this guide again.
2. Have adb installed.
just download the Android sdk and install it or, if you don't care about the SDK itself, the minimal adb from the bottom of this post (thanks to @shinobisoft for the upload). Now add the C:/path_to_the_sdk/sdk/platform-tools to your windows PATH variable (Windows 7: right click my computer > properties > advanced system settings > environment variables) or the foler in which adb.exe is located if you downloaded the minimal adb..
On your phone go to "menu > general > about phone > software information" and tap build version a few times untill it says you're a developer, then go to "menu > general > developer options" and enable usb debugging. Connect the phone with your PC and choose to connect in software mode and install the drivers and tools. When you get a message on your phone that your PC want to access usb debugging make sure you check the checkbox and accept. Now open a cmd prompt and type "adb devices" without the quotes. If it shows a series of letters and numbers followed by device, you're good to go. If it says unauthorized, you haven't accepted the prompt on your phone yet. If your device doesn't show up at all you haven't installed the drivers correctly.
3. Find out which device and software version you're running.
Go to menu > general > about phone > Hardware information for your Model number. Mine is LG-D405n, so my model is D405n.
Go to menu > general > about phone > Software information for your Software version. Mine is V10b-EUR-XX, so I've got version v10b.
4.1 If your model number is D405, D405n or D410, you'll need a modified aboot.bin to unlock the bootloader.
Go to the bottom of this post and download the file with your model and software version. I used the L90_D405n_v10b_hack.zip. Extract the aboot.bin in the zip file to a folder on your PC.
4.2 If your model number is D415, you'll need another method to unlock the bootloader, which is explained in this thread made by @aSuperSaiyanG0D.
Unlocking the bootloader on the D405, D405n and D410
1. Open a cmd window an CD to the folder where you've saved the aboot.bin you've downloaded in step 4.1
2. Execute the following commands:
Code:
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Right after the su command, supersu will give you a root request on your phone that you'll have to accept!
This will also make a backup of your current aboot partition as stockaboot.bin on your external SD card. If you don't have an external SD card, this won't work and you'll have to use /storage/emulated/0 (this is a zero, not the letter o) instead of /storage/external_SD/ like this:
Code:
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin 5429599
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3. That's basicly it, you can now install a custom recovery. I suggest downloading the latest TWRP (2.8.0.0 right now) from @shoxxy's thread, which can be found here. Just use ROM Toolbox to install it, choose rom installer, press settings > flash image and select the TWRP image from @shoxxy's thread. Afterwards you can boot to recovery using ROM Toolbox, or by shutting down the phone, holding volume down and power untill the lg logo shows, then releasing and immediately pressing those buttons again. You should get a screen asking to perform a factory reset. Choose yes twice (don't worry, it wont actually perform the reset) and TWRP should boot up. Now you can create backups and install custom roms too!
If you're a fan of cyanogenmod, you should visit @Quarx's thread, which can be found here. His CM11 is already mostly functional (right now on some models the front camera doesn't work and the ir blaster doesn't have any software, but most other functions actually do work very well, while it is faster than LG stock and gives almost twice the battery life), so if you like CM it's a thread worth keeping an eye on.
Flashing back the stock rom (in case of a brick)
If you've bricked your device, or want to revert to stock for any reason, you can follow this guide made by @gdjindal.
Post reserved
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Gabe.INc said:
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Click to expand...
Click to collapse
If you have a problem with step 4.2 only, I assume you have a D415 and you should actually ask this question in the thread that step 4.2 links to. Or isn't that what you meant?
EDIT: please note that step 4.2 is for the D415 ONLY.
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Gabe.INc said:
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Click to expand...
Click to collapse
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
SubliemeSiem said:
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
Click to expand...
Click to collapse
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Gabe.INc said:
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Click to expand...
Click to collapse
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Mind that I've only tested this using the external SD, but it should work both ways.
Error 1
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
BTW: what's the output of
Code:
adb devices
?
SubliemeSiem said:
Gabe.INc said:
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
SubliemeSiem said:
Gabe.INc said:
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Gabe.INc said:
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Where did you get the not found message? And what do you mean you flashed stock again? If you couldn't execute the dd commands then your bootloader is still locked and all you've done so far is root the device..
UPDATE: I don't get a response, but it seems this user previously flashed the wrong aboot.bin (or did something else, unfortunately he's not being very clear on that) so please only follow this guide when you have a stock recovery + aboot partition. If you did try some things before, please flash the stock rom back first and then follow this guide.
Thats awesome! Thank you! :cyclops:
guilherme.fuzo said:
Thats awesome! Thank you! :cyclops:
Click to expand...
Click to collapse
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
SubliemeSiem said:
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
Click to expand...
Click to collapse
I found no problem, but anyway thanks dude! :laugh:
guilherme.fuzo said:
I found no problem, but anyway thanks dude! :laugh:
Click to expand...
Click to collapse
Then don't say thanks, but hit the thanks button on the first post!