[DROID] Root instructions (UPDATED) - Motorola Droid Android Development

The following is a guide for how to obtain root access within an ADB shell, then locally on the device.
UPDATED TO SIMPLE VERSION WITHOUT ADB
--------------------------------------------------------------------------
Credit:
- embeem for bringing the Eclair signature check hole to attention.
- For creating the exploited update package: Zinx Verituse (initially posted here)
- mjxg for writing a complete guide which I have modified and reposted here (original thread here
- Cyanogen for providing Superuser.
--------------------------------------------------------------------------
THIS WILL NOT UPDATE YOU TO 2.0.1. If you would like to end up with a rooted 2.0.1 and haven't been pushed the update OTA yet, then please follow this (http://alldroid.org/viewtopic.php?f=210&t=568) guide THEN follow the directions below.
--------------------------------------------------------------------------
1 - Download the droid-super_user.zip file from: http://alldroid.org/download/file.php?id=659 (md5sum cf653352967253e99d967498ffd9ce69).
Do not extract.
2 - Rename the file to "update.zip".
3 - Plug your Droid into your computer via USB. On the Droid go to the Notifications bar and select "USB Connected" then press "Mount".
4 - Once the device is mounted, the SD card will show as a removable device on your computer
5 - Put the "update.zip" file you just renamed into the Root (top) directory of your SD Card.
6 - Unmount the device from your computer, and turn the Droid off.
7 - Hold down the "X" key on the physical keyboard and while doing so press the power button. Hold both of them down until you see a Triangle with an !.
8 - Press the Vol+ and the Camera button together until you get a menu.
9 - Using the D-pad on the physical keyboard, select the option to update with the update.zip file.
10 - This should take a little bit. Once it's done select the option to reboot the phone.
Now you can download a root application, or terminal emulator and try out your new found root access.
This works with 2.0.1
Please do not start removing any applications just yet. You will run into problems trying to flash anything. Wait until we have a recovery image made.

can some one dump the phone?

Looking at the change in Gerritt:
https://review.source.android.com/#change,12807
It has not been approved yet, although that doesn't prevent Mot from cherry picking it.
I just tried the droid-root.zip update on my Droid, worked great. The only thing I might add is to rename the otakeys.zip from /system/etc/security/otakeys.zip to prevent future OTA updates.
Don't want to lose root now that we have it.
-Howard
http://www.magicandroidapps.com. - Home of Better Terminal Emulator Pro, the best terminal emulator for Droid.

With root, you can dump out the MTD partitions to /data/local, ie:
adb shell
$ su
# cd /data/local
# cat /proc/mtd
Use this output to figure out which partitions are what, and then dump them out, ie:
# cat /dev/block/mtdblock0 > pds.bin
Then 'adb pull' the /data/local/*.bin files to your PC.
-Howard
http://www.magicandroidapps.com - Home of Better Terminal Emulator Pro, the best terminal emulator for Droid.

There is now a more streamlined way of going about this. I need to update the guide.

NEWEST METHOD that DOES NOT require adb
New exploit zip, including Superuser from CyanogenMod
First you have to update your phone to 2.0.1. If you have already done this manually, or if your phone has already received the OTA update, move on to the next section.
First, download this attachment ( http://alldroid.org/download/file.php?id=646 ) and rename it to "update.zip".
Copy update.zip to the SDcard in your phone.
Reboot your phone to recovery mode by holding down x while the phone turns on. once you see the /!\ emblem, press the Volume Up and Camera buttons at the same time.
Select Install update.zip from the menu.
Reboot once it is done.
Now your phone is updated to 2.0.1
Now, to root the phone.
download this attachment ( http://alldroid.org/download/file.php?id=659 ) and rename it "update.zip"
Copy update.zip to the phones sdcard
reboot phone to recovery mode (hold x while turning phone on, press volume up + camera button)
install update.zip
reboot
and you are done.
all credit to Zinx Verituse over on Alldroid.org

su works but apps still say I don't have root?
I'm an IT Professional not a newb, but not super great on Linux either.
I've followed the rooting steps, after updating manually to 2.0.1
The issue is, I can go: su using a term emulator on my phone and it says "access granted courtesy of magicandroidapps" (something like that).
I can do things through the term emulator, but for some reason when I download apps that require root and try to use them it still says I don't have root access? What gives? I couldn't even rename a file in /etc/bluez using ROOT EXPLORER (a file manager).
It's like root works on term emulator but not through GUI apps? Am I missing something?

Disregard, problem solved
Disregard.

Updated to new, simple, one flash instructions.

i cant get this to work for nothing. when i download the files i extract them to the desktop then put them into one folder named update.zip is this wrong?

dabo318 said:
i cant get this to work for nothing. when i download the files i extract them to the desktop then put them into one folder named update.zip is this wrong?
Click to expand...
Click to collapse
It never said to extract. Rename the .zip to update.zip (make sure it's not update.zip.zip) then carry on.

I've got a question. This is a hole found in android, so this should work for any android device, as long as you append the original exploit.zip to that devices update.zip, correct?

ok i finally got the zip on the phone and trying to setup metamorph now. its been setting up file: zip for about five min is this normal?

Here is a link to a tutorial on how to create your own update.zip in order to deliver whatever you may need to (with a size limitation).
http://alldroid.org/viewtopic.php?f=210&t=626
Please note this is exclusive to the current Android 2.0

cellulararrest said:
Here is a link to a tutorial on how to create your own update.zip in order to deliver whatever you may need to (with a size limitation).
http://alldroid.org/viewtopic.php?f=210&t=626
Please note this is exclusive to the current Android 2.0
Click to expand...
Click to collapse
And 2.0.1 ... thanks though, that pretty much answered my question. So any device that gets pushed 2.0/2.0.1 ota update and on before this hole is patched up this should work on. Let's hope they don't patch it before we get a hold of a milestoine update.
Btw- someone should check out the 2.1 sense dump and see if this hole is still present.
Oh and sorry about getting slightly off topic, just seemed the most revelent place to ask.

Yeah that would be good to check 2.1. But I don't think anyone is actually using that recovery image. If it's even available. Everyone has fancy dancy custom recovery images.

COMPREHENSIVE HOWTO "ROOT YOUR DROID" (my best attempt anyhow)
*deleted* per a noobs request (cuz I've heard from others as well that my directions were outdated even though they use super-root from Cyanogen).

Rainabba, Please delete that post. it's out-of-date and incorrect.

i just installed a terminal app from the market, type su and hit enter, it asked to allow or deny, so i believe just a terminal app will give you SU also, correct?
im an idiot when it comes to adb. also just a reminder to the root nobbs, if your using vista, just name the update, update dont add the .zip to it, or it wont work.

Correct. Please don't start removing apps from your system. A few people have been doing that just because they can and are causing themselves real problems. Hold off until someone succeeds in their endeavors for a custom recovery image.

Related

Step by Step How-To get Modify RC30

I would like to give thanks to JesusFreke who helped me to understand this process !!!! Please show him some love and make good gestures for his work….. Also to all the other people and sites who made this possible including Koush !!! I take no credit for this just posting it to help people like me, who dont know to much about this.
First…. You need to install a google android usb driver so you can use the adb program. (It lets you push and pull files to/from the phone, and you can open up a shell with it to).
Download the driver file (http://dl.google.com/android/android_usb_windows.zip) and
unzip it to the desktop.
On ur G1… Go menu > Settings > Applications > Development then enable the
USB debugging button.
Then connect your Android device via USB. When the Found New Hardware Wizard
appears, you'll be asked if you'd like Windows Update to search for software,
select No, not this time and click Next. Select Install from a list or specified location
and click Next. Select Search for the best driver in these locations. Browse and
select the unzipped file (android usb windows.zip). Click Finish.
Second…. Setting up the SDK
Go to http://code.google.com/android/download_list.html and download the
SDK
Unzip the file to the desktop and rename the folder to sdk
Open your command prompt (Windows Key and R)
Type “cmd” (Without the quotations)
Then "cd desktop"
Then “cd sdk”
Next “cd tools”
Now type “adb devices
After that it should say some thing like… List of devices attached HT845GZ21370
Device. If u see this abd sees your device.
Third…. Writing JesusFreke’s Recovery image
Download the zip file from this thread... http://forum.xda-developers.com/showthread.php?t=443041)
Unzip the files to the SDK tools folder
Now, in the command window, type
"adb push recovery_testkeys.img /data/local/recovery.img"
(This will copy the recovery image files to the phone)
Fourth…. Get Root working on ur G1
Download the Android Telnet Client from the Market or get it here…
http://www.koushikdutta.com/2008/11/android-telnet-client.html
Turn on your phone's WiFi. This gives your phone an IP you can reach it at.
Restart your phone
Once restarted type telnetd at the home screen and press enter – Yes….. it will
start up a Contact search, do not worry about this, just type “telnetd” and press
enter (the enter button on the keypad).
Now press connect to localhost……. (You now have root!)
Now put in this command….
“mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system”
Then “cd /system”
Then “cat /data/local/recovery.img > recovery.img”
Finally “flash_image recovery recovery.img” (Your Recovery Image is now writen)
*To make sure your Recovery Image was written…. Reboot your phone in Recovery
mode and press Alt+L. At the top it should say "using test keys" If so its written. Go
ahead and Reboot your phone by pressing the Home and Back buttons.*
Fifth…Apply JesusFreke’s modified RC30/RC8/ADP1
Go here http://forum.xda-developers.com/showthread.php?t=475381 and Download the ZIP
Now once the ZIP is downloaded rename it to “UPDATE”
Put it on the storage card
Last but not least Power off your G1 and Power it on by pressing the home key and power key
Press Alt+L (to turn on text)
Press Alt+S (to update)
And Bam you have yourself a modded RC30 G1 !!!!!!!!
ANOTHER Step by Step How-To get Modify RC30
Per user- "brandenk"
I think you need root to make the changes which is why you need to downgrade from RC30 to RC29 to take advantage of the root bug.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Engineering bootloader for G1: http://forum.xda-developers.com/showthread.php?t=455860
Follow those steps, for #2 you dont need to do the beatbox mod and for step #3 use JKv1.3 instead of 1.2, then I added a step, flashing the Engineering Bootloader. Once you do those steps you will be good to go, I did this for the first time ever last night following those directions and it worked for me, and thats with my changes to the process. It took me reading through the directions like 50 times before I tried it but I went slowly and carefully and it went flawlessly.
Complete instructions for RC30 -> JFv1.3
Per "JesusFreke"
"I saw someone post this over on saurik's G1-hackers mailing list, and thought it would be useful to some of you.
It gives complete step-by-step instructions (all 23 of them ) for going from RC30 to JFv1.3.
http://www.webnetta.com/2009/01/02/t...rc30-to-jfv13/
__________________
"Whether You Think You Can or Can't, You're Right"
--Henry Ford
T-Mobile G1 - modified RC30 with root access !!!
Thanks for the step by step instructions. Been looking for something like this!
would i get brick if i unlock it with a code for ATT?
step three link should be the following:
http://forum.xda-developers.com/showthread.php?t=443041
thanks for the walk through
also the link for the modded RC30 is:
http://rapidshare.com/files/162035634/update-RC30-fullupdate-modified-testkeys-v1.1.zip
I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?
will this work even if your phone has already been updated to the stock rc30?
i dont think so. because they patched it
johnny13oi said:
I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?
Click to expand...
Click to collapse
yup "open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke
Still at risk??
A bit of a noob here... but check my thinking:
True/False:
1. Flashing the new recovery image will prevent any further OTA updates from being loaded unless they are signed with the test keys.
2. If 1 is true, then Google/Tmobile can still push a forced update to us if they sign it with test-keys?
If both above are true, maybe we need to look at disabling OTA updates altogether?
anyone want to make a how-to for ubuntu/*nix users?
I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? Is it supposed to say "E:Can't open /cache/recovery/command"? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??
xavier6303 said:
I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??
Click to expand...
Click to collapse
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.
mack said:
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.
Click to expand...
Click to collapse
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure
Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?
xavier6303 said:
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure
Click to expand...
Click to collapse
congrats...you now have modded RC30
donutman said:
Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?
Click to expand...
Click to collapse
A quote for a quote
"open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke
What are the modified recovery image and modified RC30 update? What it the difference? Why the original onces do not work?

****ROOT EVO After July 1 OTA Update

I tried every method, read every thread in every forum in an effort to root my EVO. Nothing worked. I was driving myself mad and spending tons of time. I Eventually I came across a post which directed me to XDA Developers Thread ---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT, post 579 by SharkUW . I have used this on my own phone and I don't see a reason why it wouldn't work. I modified some of the instructions to make it clearer. The instructions may not be exact, and there is some seat-of-the-pants involved, but I got it to work. Use it at your own risk.
Prerequisites (follow in order)
Android-SDK developers program. I loaded it to C:
JAVA SE Development (use correct bit – 32 or 64). loaded in C:
Microsoft .NET Framework V 4.0
Reboot your phone and do a factory reset. Erase everything
Set phone to Charge Only and USB debugging
Open the stock browser and sign-in with your PCS phone number. Leave running.
Shutdown the phone, then restart
Make sure ADB is functional on your computer. You should be able to "adb shell" (confirming adb is working, exit shell if you're in it).
Extract the Do_root.zip (link below) and place all these files into the SAME folder as adb.exe. I have not included the appropriate PC36IMG.zip. Get it here. http://forum.xda-developers.com/showthread.php?t=701835 Leave the name as "eng-PC36IMG.zip". Place that in the SAME directory as well as the .zip.
Open a command prompt on your computer. point directory to Android-SDK directory\tools and a list will come up… click on "root.bat” and click RUN.
If it hangs for more than 30 seconds with the browser ****, CTRL+C, yes to kill the bat and just run it again.
Follow the directions. Your phone is going to reboot. It is then going to do a little **** and reboot into the boot loader. Keep track of the Command screen and wait because some steps take a while and there is no way of telling if it’s working. Nothing lasted more than 5 minutes. Eventually it will be in a "bootloader" and ask if you want to reboot. Say Yes with a Volume UP.
The .bat is now done. You have root. (not sure if next part is true) You now need a custom recovery to flash a proper ROM beyond the scope of this guide.
In original instructions but I’ve found the following Recovery step and code is not necessary: Now take the last step and flash the recovery.img that will already be on the root of your sdcard. To do this, after the PC36IMG flash:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
To check for root do ADB Shell and should get #.
If you're all advancedy you can put on a different recovery image.
IMPORTANT If you get a message here about "not writing bad block", flash it again until you get 0 errors. I don't know how common it is, but personally my recovery has issues with flashing. Do NOT let that be a bad flash.
Attached Files
do_root.zip (4.07 MB, 49 views)
________________________________________
Last edited by SharkUW; 7th July 2010 at 01:06 AM.
Going to try it tomorrow and hope it works. Thanks
Where are the attached files?
Can't find the do_root.zip file. Seems there is no attachment, please re-post. Thanks.
I tried to attach the do_root.zip file and a link to Toast 2 file. If that doesn't work, go to the referenced post #579 here: http://forum.xda-developers.com/showthread.php?t=718889&page=58.
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Vivix729 said:
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Click to expand...
Click to collapse
Simpleroot ftw.
mattrb said:
Simpleroot ftw.
Click to expand...
Click to collapse
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
gmanvbva said:
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
Click to expand...
Click to collapse
I did simple root and it worked fine too. I don't think the issue is adb being setup since he has an adb file in his download.
Update from a few days ago.
Just got a new SDHC card and simpleroot worked. The SDHC that came with my phone died. I placed a spare in there that was a 2gd regular micro and Hboot would not ready the IMG for nothing.
If simple root is not working then it's the Sh!tty card acting up.
Happy ending for me.
I just got my phone yesterday did the ota simpleroot and seems like it worked fine
but now i dont know what to do next
to get custom roms or froyo 2.2 or anything lol
Awesome post |OP|.
My desktop is Windows 7 x64 and doesn't play nicely with the standard tools.
I was forced to adapt your root.bat script to an OSX friendly BASH script.
The only requirement is that you download the android SDK from developer.android.com/sdk/index.html (apparently, I'm too new to post links).
The steps I took to get root:
Unzip the android SDK
follow |OP|'s instructions, unzipping the contens of do_root into [sdk-root]/tools/
unzip the attached bash script to the [sdk-root]/tools/
run my bash script from the [sdk-root] folder instead of root.bat - type "./root.sh" without the double-quotes
Grab a copy of Froyo while your phone is being rooted

GUIDES & FAQs [Android]: ADB Workshop by Adrynalyne and Guide by Captainkrtek

DO NOT POST IN THIS THREAD BEFORE READING THE WHOLE POST
PLEASE ADD GUIDES TO COMMON ISSUES YOURSELVES
To my recollection, the previous WM Guides thread was successful.. so we'll be moving on to android as well - from beginner to pro.
I hope this thread will provide answers to a decent percentage of your questions.
Please hold until guide collecting is finished..
In the meanwhile you are ALL invited to send me links or full guides to add to this thread.. remember, we are all about sharing.
COMING SOON! (in the meanwhile, you've got a great battery life guide at http://forum.xda-developers.com/showthread.php?t=471521 - be sure to thank BruceElliot for it!)
also, if you decide to post a guide, please keep the guide as neat as possible, with a title containing the LEVEL ([BEGINNER], [INTERMEDIATE], [PRO]) and the commonly searched words so that people who look for it can find it easily. (if you can, use the same color (dark orange) and same size (4) and Bold.. for the main title.. tho that's not a must )
post #2. [BEGINNERS+INTERMEDIATE] Replacing System Files using Android Commander
post #3. [EVERYONE] ADB Workshop by Adrynalyne and Guide by Captainkrtek
post #4. [QUICK FAQ's] Common QnA's for beginners by Timmymarsh (work in progress)
[BEGINNERS] Replacing system files using Android Commander
Replacing system files using Android Commander:
(This post was formally based in the HD2's RTL support thread and revolved around our need to replace frameworks)
so:
1. Download the android SDK from: http://dl.google.com/android/android...08-windows.zip
2. EXTRACT(!!!) the android-sdk-windows to c:\
(make sure you extract the dir - not run the setup from inside the zip file)
3. install Android Commander from http://androidcommander.com
4. Connect your device and make sure it's set to Debugging mode in /settings/applications/development/
5. You might have to set a dir containing your adb.exe file. set it to c:\android-sdk-windows\tools\
6. You will see a Total Commander-like interface. you can then copy the framework.jar file to the correct directory (there's no difference between SD android builds and androids in ROM - the system dir will be shown the same way)
a. Yes, you can replace/delete system files while android is running.
b. (for androids running from SD) Any file copied to /sdcard/android/root/system/X will be copied to /system/X in the system file. The sdcard/android root dir is JUST LIKE your root in ROM androids.
c. Make sure you either created a backup or verified a match in any other way before replacing files like frameworks, zimage, modules, etc.. your android might not boot afterwards (I keep all system.ext2 files backed up so that i can restore them incase i screw something up.)
enjoy
[EVERYONE] ADB Workshop by Adrynalyne and Guide by Captainkrtek
This following guide was rewritten by Captainkrtek, please make sure to thank him for it
Original Post:
(http://forum.xda-developers.com/showthread.php?t=879701)
This workshop was held in #android-learning on irc.freenode.net by XDA Member Adrynalyne. All credit to him for this guide, I simply am taking it and turning it into a guide. Here we go!
You can find the raw IRC log here
Good evening folks, and welcome to my ADB workshop. This is by no means a full explanation on the subject, but more of a crash course to help folks get up to speed, and get more from their devices. There may be some things you already know here, so please be patient and respect those who do not.
Reference Files
http://adrynalyne.us/files/How to install adb.pdf
http://adrynalyne.us/files/Using ADB.pdf
So, lets just start with the basics.
What is ADB?
ADB stands for the android debugging bridge and is used for testing and debugging purposes by developers.
However, we like to get more out of our devices, and its a great way to fix things.
Knowing adb can mean the difference between a paperweight and a working phone.
So, to start with, we will look at installing ADB.
Generally speaking, the Sun/Oracle JDK is required to run all SDK functions.
ADB is but one tool in the SDK arsenal.
So, we begin by downloading and installing the JDK. This can be found here:
https://cds.sun.com/is-bin/[email protected]_Developer
Choose your OS, download and install. I recommend that 64 bit users use the regular x86/32 bit version as well.
Moving ahead, we download the Windows sdk from here:
http://dl.google.com/android/installer_r08-windows.exe
Due to already installing JDK, you won't be stopped by the install process.
Now, if you notice, I installed it to:
C:\android-sdk-windows
I did this because it makes things easier when setting up path variables.
I encourage everyone to do the same, but obviously it is not required.
So, this SDK is handy, but is only good up to 2.2. We want the latest and greatest! (Well I do)
So, we navigate to:
C:\android-sdk-windows\
and we run SDK Manager.exe
If you notice in your PDF file for installing adb, you will notice that you can update, and I made a choice not to include earlier sdk versions.
I won't go into full detail on that, but depending on the version of SDK you have, 8 or 9, it WILL make a difference in using adb.
By default, for version 8 adb.exe resides in C:\android-sdk-windows\tools
By default, for version 9 adb.exe resides in C:\android-sdk-windows\platform-tools
We will assume version 9 in this guide
Really, the SDK is installed and adb is usable right now, but in my humble opinion, its not enough
I like the ability to use adb in ANY directory on my machine.
To do this, we edit Windows's environment variables.
Specifically, the system path.
To do this, we click on start, or the orb (depending on OS), and right click on Computer, left clicking on properties in the menu.
If its windows XP, I believe it brings you into advanced system properties immediatly. Vista and 7 need a second step.
On the left hand side, as you notice I have highlighted in the pdf, left click advanced system settings.
Under advanced tab, we left click environment variables...
There are two boxes here.
We are concerned with system variables, however.
So we scroll down the list and highlight path and click edit.
Ignoring all the extra stuff in here, make sure you are at the end of the line, and type
Code:
;C:\android-sdk-windows\platform-tools
The semicolon allows us to separate it
from the previous path statement.
Click ok all the way out.
We now have ADB setup globally. We can use cmd.exe (I use powershell) and no matter what directory we are in, adb is recognized.
If it is not, make certain you entered the path into system variables, and made no typos.
If you installed to a different location, you will need to adjust the path accordingly.
This concludes the section on installing the Android SDK to use ADB.
This next section will be on using ADB, so please open that pdf now.
Now, this applies to any OS, not just Windows.
Well, with the exception of the USB drivers.
I will not go too much into that, but if you take a look at the PDF, it goes through installing usb drivers for the sdk, and how to download them.
Fiarly straightforward, in that rspect.
Now, to setup our phones to use with the SDK and ADB, we must change some settings.
First, we go to menu softkey, then settings.
We scroll down to Applications and tap it.
Under Development, we will check Enable USB Debugging. Please note the SGS phones are different in this respect.
The USB cable must be unplugged before enabling or disabling this setting.
Once this is done, we are now ready to play with adb
One quick note: If you get device not found/conencted, please reboot your phone. DJ05 has a quirk in it where ADBD randomly crashes on boot.
A reboot will fix this
ADBD= ADB Daemon
Ok, continuing on.
Lets look at installing applications. This is also known as sideloading.
Unlike installing from the SD card, it does not require unknown sources to be enabled.
The command for this is
Code:
adb install packagename
This assumes that you are working from the directory where the file is located.
This will install the application to /data/app.
It will also show sometimes useful errors if install fails.
That is not something you will see from the Android GUI.
Now, a lot of us have probably deleted files with apps like Root Explorer. While this isn't really a bad thing, it leaves behind databases and data for the application removed.
This is where the 0kb applicaiton entries come from.
If you take that application entry name, you can uninstall the extra data via adb.
First we go to the adb shell which logs into the phone.
Code:
adb shell
If we end up with a $, we will want admin rights, in many cases. This is not one of them, I don't beleive.
To get admin rights, you want to type
Code:
su
Look at your phone if this is the first time, it may prompt you to allow access. Else you will get permission denied.
If you are not rooted, this will not work either.
Ok, now that we are logged in, we will type
Code:
pm uninstall packagename
where packagename is the name of the 0kb listing.
Now this seems like a pain in the a** and I agree.
HOWEVER
There will be a time where Manage applications crashes when you try to uninstall it from the phone. In this case, a factory reset, or this method is the only effective way to fix the problem.
Moving on.
How many of us have removed system applications or renamed them? Did you know that you can simply disable them from the system?
Code:
adb shell
su
pm disable appllicationname
This will disable it, and the system will ignore it.
This can be seen as safer than deleting or renaming things, but your mileage may vary.
On the other hand, you can also re-enable these applications.
Code:
adb shell
su
pm enable applicationname
Please note: Not all applications will properly re-enable. I believe a factory reset or reinstall of said application will fix the issue.
Also, application names are absolutely case sensitive.
*nix based Operating Systems see the letter 'a' and 'A' as two different things.
when you log into adb shell, you are playing by android rules
Ok, a lot of us tweak and mod our phones and turning off the device to get to clockwork recovery, or battery pulls, or multiple button holds to get into Download mode are troublesome and annoying at best.
ADB can help us here.
Here, we do not need to be logged into the shell
If we want to merely reboot the phone:
Code:
adb reboot
If we want to go to recovery (works well with voodoo5)
Code:
adb reboot recovery
If we want to go to Download Mode because we need Odin, heaven forbid:
Code:
adb reboot download
Its instant. No waiting on animations or anything else.
Its also handy if Android has locked up, but yet still works in adb.
I for one hate taking my case off to battery pull.
So now we move on to pushing and pulling files.
Sometimes, I don't feel like mounting my sd card to copy a file over to my phone.
I can use this command to push a file straight to my sd card:
Code:
adb push filename /pathtodirectoryonphone
So for instance, if I have test.txt that I want to send, I would type:
Code:
adb push test.txt /sdcard/
and there it goes.
Ok moving on
Pushing files can be done to any directory, however, some are protected.
For instance, /system is going to give you a permission denied or a read only filesystem error.
To get around this, the easiest thing to do is push the file to your sdcard, then log into the shell:
Code:
adb shell
Code:
su
We will then mount the system as writable
Code:
mount -o rw,remount /dev/block/stl9 /system
Then we can use something like
Code:
cp /sdcard/test.txt /system/app/test.txt
cp stands for copy
and it requires the path of the file and destination path. The name of the file is optional
When you copy it, you can rename it to whatever you like.
For instance, if we wanted to backup a file
Code:
cp /sdcard/test.txt /sdcard/backuptest.txt
Now, lets assume you do not have busybox installed.
You non rooted users will not.
Then you must use a slightly more complicated command called dd
This is used like this:
Code:
dd if=/sdcard/test.txt of=/system/app/test.txt
if is for inputfile
of= output file
Not every user friendly, but probably one of the safer copy commands.
Ok, moving on to pulling files.
Lets say you want to get a file from your phone, to modify, backup, etc.
To do this, we simply use adb in this manner:
Code:
adb pull /pathtofile/filename destinationname
For instance, if I wanted to backup ADW launcher in system/app
I would do this
Code:
adb pull /system/app/ADWLaucnher.apk ADWLauncher.apk
And it will pull the file from the phone and put it in the current directory.
Like above, you can specifcy where it goes.
pushing files to the sdcard, it seems prudent to talk about changing permissions.
sdcards are typically fat32, which destroys permisisons, and Android is heavily permission based.
So if you push an application to your sd card, then try to copy it to /system/app/ bad things are going to happen, or the app may not even show up.
So in that case, we use something called chmod.
This is used in this manner
Code:
adb shell
su
chmod 755 /pathtoapplication/applicationname
Keep in mind
you dont want to do this while its still on your sd card.
an example
Code:
adb shell
su
chmod 755 /system/app/ADWLauncher.apk
755 is good for applications and script files.
Just a couple more topics to cover.
Lets go over deleting files.
This becomes especially handy for removing rogue applications.
To do this, we must be in the adb shell.
Code:
adb shell
su
rm /system/app/ADWLauncher.apk
You may need to remount system as writable with:
Code:
mount -o rw,remount /dev/block/stl9 /system
That applies when using chmod as well.
So what I did above was delete ADW Launcher from system/app
However, what if I wanted to delete the entire contents of a directory?
Same thing as before, except
Code:
adb shell
rm -f /data/dalvik-cache/*.*
I just cleared my dalvik-cache with that command
very quick, very effective.
If you just tried that, please reboot your phone now
Ok....this leaves us with the final topic: logcat
logcat allows us to log what the OS is doing, and possibly delve information for when things are not working
its quite simple Reading it is another.
To use logcat
Code:
adb shell
logcat
To logcat to a certain file do
Code:
adb shell
logcat > /sdcard/logcat.txt
Now we let the log settle down to a reasonable amount of data coming in and not a wall of scrolling, then start the app in question. When it gives an error, we hit ctrl-C and kill the adb shell session.
This should have captured enough data to see the error. Now, I prepared an example. A user came to me on IRC, and Google Maps was force closing. Clearing data didnt fix it, Clearing dalvik-cache, and fix permissions did not fix it. In this case, the user did not know how to use adb So I had him grab an app called alogcat from the market and email me the log. This is also a very valid method.
this file explains what the problem was, and highlights what to look for as an example.
http://adrynalyne.us/files/logcat.pdf
___________________________________________________________________
This concludes the guide from Adrynalyne, there will be more workshops such as this one in irc.freenode.net #android-learning.
Thanks to everyone in #samsung-fascinate !
QUICK FAQ's
sources: Q&A Section, The Weekly Q&A Section by XDA News Writers (thanks guys)
Q: ‘Is there any way to block specific apps from using my data connection?’
A: Try the Droid Wall application.
Q: ‘I read how you can make changes in the build.prop file on my Android device. How exactly do I get to it?’
A: Install ASTRO file manager, browse to /system, long press on build.prop – Edit – Copy. Press on the home icon then Edit icon – Paste. Connect sd card, edit it, and paste it over from where you copied build.prop
Q: What happens if I update my phone? will I need to re-root it and get the ROM again? will all of my applications get erased? If so, is there a way around this?
A: You will lose your root, but not apps if it is just an update.
Q: I just tried to flash a ROM from recovery on my Android phone and got “Verification Failed, Installation Aborted” What happened?
A: Before you can flash a custom ROM the .zip file must be digitally signed in the ROM kitchen, if unzipped and re-zipped it will lose its verification, this happens often using the Safari browser as it likes to decompress .zip’s. Or if your download is corrupted (download the ROM again) it will fail the Verification.
Q - HTC Location Widget shows "map data unavailable"
A - On the widget, click the pin/then click the windows button/click get more/scroll to download maps/download relevant map (care, maybe a big file). Now exit and click onto map, your location should now be visible :)
Q:So, I moved all the apps on the SD, but is still not enough. How can I free some memory? I could delete the cache of the older upgrade or something else?
A:Do you have pictures and videos? If so, check if they are on the SD card and not on your internal memory. Cleaning your cache helps, and try deleting your text messages threads.
Q: ‘What exactly is a kernel and what are the benefits in changing it?’
A: A kernel is a bridge between the applications and the actual data processing done at the hardware level. The kernel’s responsibilities include managing the system’s resources – the communication between hardware and software components. Flashing different kernels gives you different operating speeds, better battery life, the ability to overclock, and more.
Android control other device with IOIO Board.
It use ADB.
http://androidcontrol.blogspot.com/2011/10/ioio-board-for-android-control-io.html
timmymarsh said:
QUICK FAQ's
sources: Q&A Section, The Weekly Q&A Section by XDA News Writers (thanks guys)
Q: ‘Is there any way to block specific apps from using my data connection?’
A: Try the Droid Wall application.
Q: ‘I read how you can make changes in the build.prop file on my Android device. How exactly do I get to it?’
A: Install ASTRO file manager, browse to /system, long press on build.prop – Edit – Copy. Press on the home icon then Edit icon – Paste. Connect sd card, edit it, and paste it over from where you copied build.prop
Q: What happens if I update my phone? will I need to re-root it and get the ROM again? will all of my applications get erased? If so, is there a way around this?
A: You will lose your root, but not apps if it is just an update.
Q: I just tried to flash a ROM from recovery on my Android phone and got “Verification Failed, Installation Aborted” What happened?
A: Before you can flash a custom ROM the .zip file must be digitally signed in the ROM kitchen, if unzipped and re-zipped it will lose its verification, this happens often using the Safari browser as it likes to decompress .zip’s. Or if your download is corrupted (download the ROM again) it will fail the Verification.
Q - HTC Location Widget shows "map data unavailable"
A - On the widget, click the pin/then click the windows button/click get more/scroll to download maps/download relevant map (care, maybe a big file). Now exit and click onto map, your location should now be visible :)
Q:So, I moved all the apps on the SD, but is still not enough. How can I free some memory? I could delete the cache of the older upgrade or something else?
A:Do you have pictures and videos? If so, check if they are on the SD card and not on your internal memory. Cleaning your cache helps, and try deleting your text messages threads.
Q: ‘What exactly is a kernel and what are the benefits in changing it?’
A: A kernel is a bridge between the applications and the actual data processing done at the hardware level. The kernel’s responsibilities include managing the system’s resources – the communication between hardware and software components. Flashing different kernels gives you different operating speeds, better battery life, the ability to overclock, and more.
Click to expand...
Click to collapse
Thank you for your patience and taking the time to answer those questions. I loved your simple and easily digestible format.
There is a note
*nix based Operating Systems see the letter 'a' and 'A' as two different things.
when you log into adb shell, you are playing by android rules
Click to expand...
Click to collapse
this note is all wrong..
1. linNUX is not *NIX.
2. Mac OS-X is a *NIX OS, it is based upon UNIX, they use their own variant called Darwin. Darwin does not require capitolization.
3. The word should be POSIX. Linux is POSIX compliant and POSIX defines the capitolization standardards
soft brick
Taioba said:
Is there any way to use ADB even though I can not enable USB debugging by the android?
I have an Atrix with soft-brick. How can I restore a file (framework-res.apk) knowing that my USB debugging is off?
I can enable ADB via fastboot?
Thanks!
Click to expand...
Click to collapse
I found this for atrix 4g....
http://forum.xda-developers.com/showthread.php?t=965546
hope it helps
knoknot said:
i have a bricked s2 not so sure how to go about reviving it via adb
Click to expand...
Click to collapse
check this thread
http://forum.xda-developers.com/showthread.php?t=1237815
thanks. searched for that
Thanks for it.
Great Guys............ :good:
Thanks for sharing.
Thanks for sharing this guild :d, i am new member for reccod
Great job~ Sometimes could be used this.
I'm using Windows 10 RTM and I've set the path, yet I still get the "unrecognized application" error in the command console. What am I missing?
Nevermind, a restart fixed it. Used to be you didn't have to.... sheesh.
nir36 said:
Replacing system files using Android Commander:
(This post was formally based in the HD2's RTL support thread and revolved around our need to replace frameworks)
so:
1. Download the android SDK from: http://dl.google.com/android/android...08-windows.zip
2. EXTRACT(!!!) the android-sdk-windows to c:\
(make sure you extract the dir - not run the setup from inside the zip file)
3. install Android Commander from http://androidcommander.com
4. Connect your device and make sure it's set to Debugging mode in /settings/applications/development/
5. You might have to set a dir containing your adb.exe file. set it to c:\android-sdk-windows\tools\
6. You will see a Total Commander-like interface. you can then copy the framework.jar file to the correct directory (there's no difference between SD android builds and androids in ROM - the system dir will be shown the same way)
a. Yes, you can replace/delete system files while android is running.
b. (for androids running from SD) Any file copied to /sdcard/android/root/system/X will be copied to /system/X in the system file. The sdcard/android root dir is JUST LIKE your root in ROM androids.
c. Make sure you either created a backup or verified a match in any other way before replacing files like frameworks, zimage, modules, etc.. your android might not boot afterwards (I keep all system.ext2 files backed up so that i can restore them incase i screw something up.)
enjoy
Click to expand...
Click to collapse
Thanks, this Guide is very informative
Help with LG D722
I'm using LG D722 phone and I somehow unlocked bootloader and installed twrp recovery. I backed up Lollipop that's what I'm using and i want to restore custom ROM
I know I need to install Google Apps after installing Custom ROM. But Do I also need to install Modem files on my device ? Because I can't find them on XDA Forums. Please give me a link or something. The help is not just appreciated but seriously needed.
Success. Thanks
Hello, I walk testing one recovery but I'm booting before flashing, the question is, will the recovery feel same when booted vs flashed? I've booted and used to flash a pair of zips but felt very laggy and bugged although did the work right. Thanks
Edit: solved, tried myself
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app
http://forum.xda-developers.com/showthread.php?t=872128&page=2

[How to] Everything I know about the Gooapple 3g and Gt-6

Hi Everyone,
Sorry for the discombobulation of this post, but I have been adding to it non stop.
This thread covers all I have learnt from this model phone;
Root procedures for both Gooapple and iorange GT-6
ADB access (no USB adb so need to use over WiFi), - ADB WORKING NOW!!
Secret reset button location,
Recovery mode,
Download mode,
Drivers,
How to (and not to) theme framework-res.apk with uot kitchen
Flash tool
Change Boot animation
Upgrade External storage.
GPS server change.
Battery Info.
Serial No. Location
Quick access to the Camera
Mayiandjay on the Gooapple 3g on Youtube
Creating an extracted system.img
Dump recovery.img / boot.img
Alternate ROM dumping method (Thanks Dastin1015)
Flash a recovery image (Thanks Dastin1015)
Full Market on the Goo
ROOT;
I have purchased one of these and they are quite easy to get root using Visionary+ for temporary root option to push su and Busy Box, then use Z4root for permanent # works quote well and easy and
Checkout the rooting video here (http://www.youtube.com/user/mayiandjay) for an easier way just using z4root.
ADB OVER Wi-FI;
once you can get adb to recognise it (using terminal emulator on the phone
"setprop service.adb.tcp.port 5555"
then
"stop adbd"
"start adbd"
from there you can use your pc to run
"adb connect *insert IP address here*"
UPDATE: I found how to get ADB access over USB... I just insta;;ed the PdaNetA302.exe file from http://www.alcatel-mobilephones.com/global/content/view/full/25287
and then disconnected when advised to, reconnected when advised to, then BAM!!! working ADB..
I wish I had known about this a week ago...
From here you can have access to all supported adb commands including shell for # access, also for pushing and pulling files from the goo,
UOT KITCHEN; (Be careful dangerous)
I used the "ADB PULL" command to pull "/system/framework/framework-res.apk"
from the device, I then used the UOT Kitchen to modify it to my liking once I got the uot .zip file, I extracted the framework-res.apk file and used "adb push" to overwrite the one inside /system/framework/ dir.
(use a pc to push, not the phone explorer copy paste... Lol I bricked mine by using the file explorer, see the rest of the post for more info....)
RECOVERY MODE, DOWNLOAD MODE and BOOT ANIMATION;
some other usefull info is that you do not have to wait for the phone to run dead if you use the wrong key combo whilst booting ( trying to get into recovery hold home button whilst turning on then 5 seconds after "gooapple" appears let go of home and then press it again) you will get recovery console, where you can change the boot animation to the static apple or the gooapple animation, you can also do a factory reset or clear cache, from here you can also run an "update.zip" file but unfortunatly after i 1/2 bricked mine i stupidly did a factory reset and lost rw on /system (loosing bus box and su) (CRAP!!!) i was using the above mentioned method to use the "uot kitchen" to retheme the framework-res.apk file of the goo, and it was working fine when pushing the framework-res.apk to the phones /system/framework/ dir using a pc, but I got lazy and stupidly did a copy / paste using the phone to return to the original framework-res.apk (i know dumbass right) and then she rebooted to infinate bootlooping (F#@K!!!) I can now get into recovery mode and unfortunatly I cannot get my update.zip that pushes busybox and su etc to sign properly so that I can copy via update.zip the backed up version of framework-res.apk back to the now read only /system/framework dir.... (possible Brick anyone?)
SECRET (hidden) RESET BUTTON;
So... continuing on... to reboot the phone if it locks up and stops responding, you need either the original simtray pin or something like a multimeter probe and stick it down the headphone jack, down there there is a hard reset button, (get a torch and look for yourself if you don't believe me) hope this helps people...
DRIVERS;
Also I downloaded the qualcomm MSM drivers from 4shared and can now connect to the phone cos I noticed that if you boot the phone using the down volume key (i think) with the USB connected you can get nothing come up onscreen on the phone but the PC picks up a new device, the 4shared drivers worked but unfortunately that's where my knowledge stops...
FLASH TOOL;
I downloaded the flash (or google translated "brush") tool from mobileuncle but untill I find someone sharing the rom, or system.img it is usless to me...
UPGRADING EXT. STORAGE;
Something interesting for the rest of you is that the Gooapple 3g ( shows as A4-3G) and the preproduction iOrange Gt-6 (also shows as A4-3G) seem to look the same on the inside, I have both ( but liked the good ol F#@K you Apple, with the apple eating an android boot animation and apple in a android symbol on the back of the device ) I have opened both of them up (use a very small screwdriver on the screws between the speakers and 30pin dock connector on the base, remove these screws and slide the back plate up towards the power button (gentle no to break the retaining nuts on the back plate), from here you can undo the bit of tape and lift the battery up out of the way ( its soldered in so be careful, seeing as its always powered and easyier to short something out ) then next to where the battery sits you will see the back of a micro SD card (this is you external storage) if you get your nail and press on the back of it you will notice it is held by a spring retainer and will pop out a bit, from here press it in half way again with your nail and slip your nail off it, releasing the spring tension, flicking the micro sd card out into the casing (and hopefully not across the room)
you should now find either a 4GB, 8GB, 16GB or possibly a 32GB micro SD card came out depending on the model you chose, if you chose a 4GB or 8GB like i did you can replace it with an inexpensive 16GB Micro SD card put it back together and reboot, This is how I have tried copying my "update.zip" with Busybox and Su files (see above, that wont sign!!! GRRRR) the recovery console recognises the file but says signature authentication fail....
I could sign my "update.zip" for my framework-res.apk file but without Busybox or system RW it is useless.. it passes authentication but without rw on system it is useless....
GPS SERVER CHANGE;
Also, using faster fix off the market (need root) you can change the GPS server for better GPS performance.
BATTERY INFO;
Stamped on the Battery is
PL402874 1000mAh
3.7V 3.7WH
SERIAL NO. LOCATION.
Under the back cover there is a Version (mine is v2.3) and Serial number sticker
QUICK ACCESS TO THE CAMERA
Double click Home on the unlock screen to have quick access to the Camera.
USEFUL YOUTUBE VIDS
Check out mayiandjay on youtube (http://www.youtube.com/user/mayiandjay), he has done videos covering the stuff I am trying to explain, Thanks deepakpitrola333 for pointing this out
CREATING A EXTRACTED SYSTEM AS SYSTEM.IMG
for windows pc,
Go to http://db.tt/GAyvuDE (thanks Dastin1015) download and extract to your sdk/platform-tools folder
Rename mkfs.yaffs2.arm to mkfs.yaffs2 (delete the .arm extension)
open up command prompt (if you don't know how to do this in your current windows environment by now then just give up now)
change dir to the platform-tools dir in the sdk,
TYPE: adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
then pick up your shinny gooApple device;
open root explorer and navigate to mkfs.yaffs2 select and hold, change to have execute permissions
Back on the PC;
adb shell
su
# cd /data/misc
# ./mkfs.yaffs2 /system /sdcard/system.img
# exit
adb pull /sdcard/system.img ./system.img
I got a 176Mb system.img with "Build ok."
DUMP RECOVERY and BOOT IMAGES
you'll need dump_image from http://db.tt/9EANtEX (Thanks Dastin1015)
copy to your platform-tools folder in your androidsdk dir
do the same as above and push to /data/misc
then as before, change permissions of dump_image in root explorer to have execute. reboot device
Then you can run command prompt
go to your sdk platform-tools directory
run;
adb shell
cd data/misc
./dump_image boot /sdcard/boot.img
./dump_image recovery /sdcard/recovery.img
exit
adb pull /data/misc/boot.img ./boot.img
adb pull /data/misc/recovery.img ./recovery.img
ALTERNATE ROM DUMP METHOD (Thanks Dastin1015);
To do any flashing to the phone you must be rooted.
Rooting:
1) Download z4root and hit the permanent root option: http://db.tt/Bltsa73
2) Once rebooted you will have root.
Dump ROM:
~Prerequisite is that you have root~
{Non ADB method}
1) Download romdump and place it on the root of your SD card: http://db.tt/kXTaCDF
2) Download Terminal Emulator from the Market if you haven't already.
3) Open Terminal Emulator and issue these commands:
Code:
$ su
# cp /sdcard/romdump /system/bin
# chmod 747 /system/bin/romdump
# romdump
4) Now on your SD card under the romdump folder you will find you recovery.img, boot.img and system.tar. Backup these files to your computer for safe keeping.
{ADB method (Must have Android SDK installed)}
1) Open up command prompt and issue these commands:
Code:
C:\Users\Your_Name> cd ..
C:\Users> cd ..
2) Navigate to your installed Android SDK (Mine is under the Program Files (x86) folder):
Code:
C:\> cd Program Files (x86)
C:\Program Files (x86)> cd Android/android-sdk/platform-tools
3) Connect your device to your computer and make sure you have USB Debugging enabled on your phone.
4) Issue this command to verify that your computer recognizes your phone:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices
5) If you see your phones serial then it is connected.
6) Download romdump and place it in the platform-tools folder: http://db.tt/kXTaCDF
7) Issue these commands:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb push romdump /system/bin
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell chmod 747 /system/bin/romdump
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell
# romdump
you should get the following;
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : GOOAPPLE 3G QUALCOMM-Android2.2.3-IOSUI-eng.autobuild.20110729.144151
Creating required files... done.
Opening mtd table... done.
Dumping kernel config... done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
8) When done your ROM dump will be in the romdump folder on your SD card.
/sdcard/romdump
boot.img
checksum.md5
config.gz
recovery.img
system.info.gz
system.tar
DONE.
INSTALL CLOCKWORK RECOVERY (orange lantern recovery) ( Tested on my GT-6, that is basicly the same as the gooapple but has the apple symbol on the back, and now my Gooapple 3g,both successfully)
Flashing custom recovery image:
{Non ADB method}
1) Download flash_image and place it on the root of your SD card: http://db.tt/flHRxiG
2) Download recovery.img to the root of your SD card: http://db.tt/uy56zhj
3) Open Terminal Emulator and issue these commands:
Code:
$ su
# cp /sdcard/flash_image /system/bin
# chmod 747 /system/bin/flash_image
# flash_image recovery /sdcard/recovery.img
4) If you see a bunch of successful on your screen then it has flashed properly.
{ADB method}
1) Open up command prompt and issue these commands:
Code:
C:\Users\Your_Name> cd ..
C:\Users> cd ..
2) Navigate to your installed Android SDK (Mine is under the Program Files (x86) folder):
Code:
C:\> cd Program Files (x86)
C:\Program Files (x86)> cd Android/android-sdk/platform-tools
3) Connect your device to your computer and make sure you have USB Debugging enabled on your phone.
4) Issue this command to verify that your computer recognizes your phone:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices
5) If you see your phones serial then it is connected.
6) Download flash_image and place it in the platform-tools folder: http://db.tt/flHRxiG
7) Download the recovery.img and place it on the root of your SD card: http://db.tt/uy56zhj
8) Issue these commands in command prompt:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb push flash_image /system/bin
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell chmod 747 /system/bin/flash_image
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell
# flash_image recovery /sdcard/recovery.img
9) If you see a bunch of successful on your screen then it has flashed properly.
boot into recovery, hold home whilst powering on, after 5 long seconds, let go of home and then push home again, you will need to put the volume/menu-back toggle to "volume" mode and according to deepakpitrola333, you need to cycle the list 3 times using volume to allow selection.
Video by mayiandjay;
http://www.youtube.com/watch?v=B_dX9Ruoljo
ENABLE FULL MARKET ON THE GOO
Thanks to Smith, we can have the full google market on our Goos
http://forum.xda-developers.com/showthread.php?t=1133702
IF I OR ANYONE ELSE EVER HELPS YOU, PLEASE CLICK THANKS... Its not that hard....
Done.
CHEERS!!! - KEG.
Thanks for info on the gooapple, its good stuff.
Any idea on how to do any of the following:
- restore original recovery screen
- get a clockworkmod recovery image to work
- do a nandroid backup
i have managed to get the applestyle home apks and the keyboard and stuff and so want to install another rom. I flashed a random clockworkmod image but now i dont get any recovery screen at all, its gets stuck on apple every time on every button combo/method.
if its not too much to ask, could you check if you can run fpse the psx emulator on your gooapple, it crashes to home straight after loading a game even tho i have a bios. psx4droid works but is choppy, similarly specd phones like the wildfire s and legend can play fpse games like ff7 very well.
Gooapple GPS
Do you now how to acivate the GPS on the gooapple.
Have this phone a GPS chip like SiRF III chip?
Is it possible to use it with navigation software?
Did you purchase it? If you did that, please, send me link to rom dump after you dump it or you know already existing link?
Sent from my IDEOS S7 Slim using XDA App
this phone has a sirf III and installing a gps program makes the gps work.
i cant dump the rom without getting a clockworkmod recovery image that works for this phone, unless you know of a way jon2555.
Hey guys, the best way I found to toggle gps on (because it does not show up in networks) is by installing go launcher so you get a shortcut to it in your apps, the press home and set applestyle as default again, then go through your drawer and select the go launcher shortcut, from there add the power control widget, from there you can toggle gps...
Also I have been nagging the people at the gooapple factoryand they advised they may add a downloadable firmware upgrade soon...., fingers crossed as mine is currenly half bricked, I got access to the fastboot by downloading the microsoft mobile drivers update, that lets fastboot recognise it when you reset with the vol down button, but need to read up on how to use it....
I had a quick readup on fastboot commands, and I have written an update script (The one that I cant sign), and I'm going to try to run it with fastboot as my limited and unexperienced understandung is that through fastboot you dont need signed updates...., unfortunatly I left my goo at work on wednesday and I was in Sydney all day today, so i wont be able to try it out untill I return to work in freezing Canberra tomorrow... Fingers crossed, and if I can successfully get it working again I will try to find a way to dump the partitions and make an update.zip that rewrites all of /system (if possible), so next time i kill it, I may have a better chance recovering from my mistakes (or pure lazyness....)
jon2555, no rom yet, but Hat007 did previously do an app dump of all the apps on gooapple 3g here,
http://forum.xda-developers.com/showthread.php?t=1245655
(thanks hat007)
and as deepakpitrola333 said, until somebody can put a working clockwork on it, we are out of luck regarding nandroid backups.... and my goo is currently bricked so i cant do much with it, and i gave my gt-6 to my daughter already, so no chance of getting that back......
Gooapple Firmware ROM Update
Hi All,
I'm New to this. Is there going to be a ROM or Firmware Update? if so how is it going to be done? Which Website??
I've bought mine from Android-Sale.
Has anyone else bought there's from Android Sale?
Also Is there a FIX to Make the Unlock Slider Back to English without the Stupid Chinese Symbol TXT??
Also Is anyone having Trouble with there Built-In GPS?? I cant get mine to Work??
I Look Forward to your Comments.
Cheers.....
hey spookie,
kegatron has said to toggle the gps from go launcher, which enables an android style interface with power options for bluetooth, gps, wifi etc by widget or otherwise. I assume you can do this with the stock froyo launcher too.
Home key can select the launcher after a third is installed.
I got mine from fastcardtech as they gave a discount over android sale, however it will be gooapple themselves releasing the update and or rom in the future.
With so many units sold, there is gonna be stuff up soon.
If someone knows how to make thier own clockworkmod recovery, the rom can be uploaded by anyone with the phone. I have no clue who to ask to do this tho.
The chinese in the lock screen is not something i know how to change but as i said a stock froyo launcher and lock screen can be used instead. Helps with the long icon name problem too.
If its not too much to ask can you check if fpse, the psx emulator, works on your phone. It crashes straight away on mine but all psx4droid versions work but as it is known, psx4droid is considerably slower, like 10-20 fps slower making final fantasy games run 50fps max and 35-40 normally which is too choppy.
I hope what i have said helps, gps isnt on all the time so try to toggle it like keg said and if you know anyone who can write custom recovery images, get them over here
i also assume you have rooted to get rid of all chinese from system icons/folders
Hey Spookie,
With the GPS, I was still using the applestyle launcher but one of the good things about go launcher is the fact that it has a app link in your app drawer, meaning you can select the applestyle launcher as the default and still have access to go launcher without too much hassle (just select it in the apps on your home screen)
So with that said I assume you have root?, if not... get it... Lols..
from there you can get rid of the standard Chinese crud that I cant read like baidu input or whatever its called, QQ (whatever that is...) etc. using Titanium backup (CAREFUL FOR WHAT YOU UNINSTALL, and batch backup everything first!!!), I'l put up a list of what can be uninstalled safely once I get mine working again. and you can fix the server your GPS is looking for by using FasterFix from teh market (you need root for this)
And the gooapple webpage is quite easy to find.... I just googled gooapple and funnily enough the webpage's name wasn't too cryptic (its www.googapple.com lol) just use the google chrome browser to automaticly translate the Chinese and for most of the bad translations you can still work it out..
Hope this helps...
BTW, I'm looking into rewriting my update.zip file for my framework-res.apk file as the scripting is different using fastboot and I need to read up on it.. give me time
I need to work out what needs to be in the android-info.txt and android-product.txt files....
Hi Guys,
Thanks for all you Help & input.. However I'm Very Confused and Lost?? Yes I've installed Z4Root.
But Now That I've installed this App. How can I BACKUP the Whole ROM as it is before I Start to Uninstall all thoses Chinese APPs etc??
Also What Input Keyboard do I install? Which one is the Chinese Keyboard??
I'm Wanting to keep the Stlye of the Phone as it is when I bought it but wanting to Take Out the Chinese Junk, and Install just want I want in English.
As for the GPS, is there a Way to Keep it always Switch on From First turning on the Phone??
I do hope you dont think I'm a Stupid Person??
I dont want to Brick or Destroy this Phone?? Just want the Chinese Junk Out and GPS & the Unlock Slider Fixed?? Do hope they Bring out Firmware or ROM Update? I'm picking it's going to be on here once it's Relesed??
Look Forward to your Comments.
Regards
Spookie...
Gooapple Camera & YouTube
Hi Again,
I was meant to also ask in my Last Post
Can anyone if Possible post a Photo on here taken Directly off there gooapple device? Ans is it a True 3.2mb Camera? And Also is the Front Camera 1.3mb?? I'd be glad to have a look and you image....
I cant get youtube to work with the Youtube App? I've tried all sorts of Differnt Apps (apk files), and still NO Luck with youtube??
Any Thought's Or Comments??
Thanks...
SpookieNZL
Hey Spookie,
Sorry champ, if I misdirected you, what I ment by batch backup all the apps first was to do with "Titanium Backup" from the market, it requires root access
to test for correct root access, you should get # when you type su in a terminal emulator.
try this once you have it installed,
Download the Iphone keyboard from the market, the go to settings, keyboard, and enable the iphone keyboard (tick box) then, find any text box and press and hold the box untill "input method" comes up select iphone keyboard
Once you have the iphone keyboard working, you can then delete the baidu (or whatever it was called) keyboard, by opening Titanium backup, accept super user access, then go to "backup / Restore" then press the menu key (vol up) then select "Batch" then select "backup all user apps +system data", then once completed, you can then go back to "backup /restore" and find Baidu input and select it, and then "uninstall"
Congrats you have now deleted the Baidu input,
I would recommend NOT uninstalling anything that you don't know if it is crucial or not, as if you delete the wrong thing you can get major "Force close" issues and make the phone 100% unusable until a ROM has been released to re-write the partition and start again...
With the Camera, I will post a heap of photos up when I get mine working again, I have taken lots of photos of pulling it apart and upgrading storage etc. I am in the progress of putting all the info from this post into a full guide with photos of step by step how to do everything that I know of, as I can't find anything from anyone else posted on the net regarding most of the things i have covered, I might just step up to the plate and do it
With Youtube, I installed the tubemate app from market, worked fine for me.., try it an let me know
Hope this helps!!!
Also, for those who didn't know, when you have the slide to unlock screen, if you double click home you will get a camera icon pop up (on an Iphone / ipod this is to access the music menu) that way you can get quick access to the camera to take a photo
hey keg why are you telling him to uninstall baidu input, on its last setting it is a perfect iphone input keyboard completely in english, the one on the app market is not good looking or accurate.
also, on youtube this guy, mayiandjay, has good videos on some of the stuff your trying to explain so maybe skip this to save time.
lastly i hope you get your phone back to working, as i have the phone working and sort know what im doin, feel free to ask for anything from it.
spookie, ill get some daylight pics up in the morning, at night the camera looks more grainy but is still good.
Hi deepakpitrola333,
Sorry I never really gave the Baidu input a real go, I found it slow unresponsive, and sometimes would revert back to converting whatever I was trying to write into Chinese, so it got the ass, I did get swype working on it, but I'm used to my Galaxy S and didn't find it that good on this device.
I suppose my guide to deleting the Baidu input was reversable if you did it step by step, you can go into titanium backup, go to backup / resore, and go right to the bottom, select baidu input that should have a line through it, and select restore.
BAM!!! Bauidu is back, though you will have to enable it again through the keyboard s option in settings, then press and hold a text box and select it again....
Sorry for the confusion.
yea it took me a while to set it to how i like, iphone style full english with predictive, wild guesses from the options list when holding down the circle key.
it is faster than the 4-5 keyboards ive used and looks the best in caps with no numbers to ruin the look.
it wont help you keg because yours is unfortunately bricked but spookie, on baidu after getting the keyboard up (press home a few times), hold the circle (world?) key, then select last, (keyboard will close) then hold bottom left key after getting it back up then first option, then second to last for predictive or last for non predictive.
Got the Goo Going again!!!
WOOOO!!! I'm soo happy
here's how I did it, (and I will add this to the first post)
When my device was bootlooping (the gooapple animation was playing over and over) I connected it to my computer, noticed that once again I got the unknown devices (4x qualcomm HSUSB interface) pop upagain and after giving up trying to find the Qualcomm HSUSB Driver prviously I decided to go on the hunt as this was close to my last resort before giving up for the day, well guess what!! I found it!!
I downloaded a file called PdaNetA302.exe and it installed the correct drivers for me!!! from there I could finally see the device in the Android Debug Bridge (especially whilst it was was booting!!) from there I could push the framework-res.apk into the /system/framework/ dir on the goo!!! WOO HOO!!
I'l play with it for a while and start ripping everything off it tonight, see what I can do about making a backup of some sort.... or if anything a listing of all dirs and files in each partition.
Thanks everyone who is reading this for your support during these "goo-less" times
Hi! I am the youtube member "mayiandjay" that has been posting some videos on how to work around with the gooapple 3g.
Recently I tried flashing clockworkmod recovery but now I get stuck on the "gooapple" logo.
How can I restore the original recovery Image or get one that works for this unit. ANY HELP WILL BE GREATLY APPRECIATED!! THANKS IN ADVANCE.
Hi! I am the youtube member "mayiandjay" that has been posting some videos on how to work around with the gooapple 3g.
Recently I tried flashing clockworkmod recovery but now I get stuck on the "gooapple" logo.
How can I restore the original recovery Image or get one that works for this unit. ANY HELP WILL BE GREATLY APPRECIATED!! THANKS IN ADVANCE.

[ROOT] G2X Gingerbread 2.3.3. stock ROM with flashable zip in Clockworkmod Recovery

Update on 9/11/11: Thanks to phburks there is now a flashable zip to root the G2X stock rom. He figured out that the update-binary we were using was not compatible with the G2X. He found the compatible binary that allows us to create flashable zip files. Hats off to phburks. This is an unsigned zip and you should not be required to toggle signature verification. Of course the files required to root the phone (su and Superuser.apk) were created by Chainsdd.
There are two flashable zip packages. The first one roots the G2X. You simply flash it with Clockworkmod Recovery. The second zip unroots the phone for those who wish to unroot their device for whatever reason.
After rooting go to the Android Market and get the Busybox installer referenced below. Use that to install and keep Busybox updated.
Root Zip for G2X: http://www.mediafire.com/?92qpr525ztblh8w
Unroot Zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
HOW TO ROOT
1. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
2. Download the root zip package referenced above.
3. Put the zip package on your internal or external sd card on your G2X. Do not unzip the package.
4. Turn off phone and boot into Clockworkmod Recovery by pressing volume down and power and hold until the fancy LG (second one) appears.
5. Select install zip from sd card. Select and flash the root zip package. Note: You navigate in Clockwordmod Recovery by using the volume keys up and down and commit the action by pressing the power button.
6. Reboot your phone. You are now rooted.
NOTE: THE FOLLOWING BELOW IS OBSOLETE. IT IS LEFT FOR HISTORICAL PURPOSES ONLY.
Original post made on 9/9/11:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Reserved for future use.
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Paul Nur said:
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Click to expand...
Click to collapse
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Wow, I've been waiting fire this thanks jboxer.
Sent from my LG-P999 using XDA App
jboxer said:
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Click to expand...
Click to collapse
Ohhhhhhhhhhhhhhh, I got it lol thanks for showing me it from a different angle
still realy no point xboarders is more stable and much faster then stock and all u need to do is flash his rom then go to advanced restore and only restore data ive gotten away with that doesnt always work though
Always good to have more options.
phburks said:
Always good to have more options.
Click to expand...
Click to collapse
Damn straight. Keep it up, jboxer.
Sent from my LG-P999 using xda premium
Very nice! Thanks man, much appreciated.
Sent from my LG-P999 using XDA App
awesome i tried it on another g2x phone running 2.3.3 root the phone so fast plus with no lost data
thread rated 5 stars ^-^
Change Directory
jboxer said:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Click to expand...
Click to collapse
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
yogieajuz said:
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
Click to expand...
Click to collapse
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Thank you for quick reply
jboxer said:
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Click to expand...
Click to collapse
Thanks jboxer, work like charm....
but when i did back up they said error can not back up image data ???
whats wrong???
never mind, i found out i run out of space on my sd card
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
phburks said:
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
Click to expand...
Click to collapse
Thanks to phburks for the good work in figuring out why our update zip packages were being rejected by Clockworkmod Recovery. We now have flashable zips to root the G2X (works on stock GB rom) and to unroot it. They are listed in the first post that I have edited.
http://forum.xda-developers.com/showthread.php?p=17398464

Categories

Resources