Related
Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\platform-tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> <path where you want to save it>- Example: adb pull /data/app/Stock.apk C:\
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
[GUIDE] Fastboot for Noobs
Fastboot
Like My Guide(s)? Donate
Things you need:
New SPL - Download
New Radio - Download
Your Current ROM - CyanogenMod 3.6
SD Card Reader
Rooted G1 Phone
Computer
USB Cable
Patience
---------------------------------------------------------------------------------------
Install Radio FIRST
Download the Radio Update
Rename it to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off)
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
When done reboot by pressing Home and Back
You should be able to access your Home screen (If its stuck on the Google G1 screen dont panic, just remove your battery for now)
---------------------------------------------------------------------------------------
Installing the new SPL
Note: To update you must have a PVT board. To Check go into fastboot (Power and Camera and check)
Take your SD Card out again and plug it into the pc
Remove the update.zip that you put in there
Download your current Rom or any other ROM that you want. I suggest CyanogenMod 3.6
Download the SPL Update
Rename the SPL Update to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off) or put your battery back in and turn it on
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
Now it will reboot on its own back to recovery
Reboot again by pressing Home + Back
Your phone will be stuck on the T-Mobile G1 Screen (Again DONT FREAK)
Remove the battery from your phone
Remove your SD Card and plug it back into your computer
Take the ROM that you downloaded and rename it update.zip
Remove the update.zip that was on your SD Card and put this new one it
Put the battery back into your phone
Enter recovery (Home + Power)
Press Alt+s to update
Let it finish
Press Home + Back to reboot
Thats it! You now have your new SPL and Radio
---------------------------------------------------------------------------------------
Getting into Fastboot
Turn off your phone
Hold the back button and keep holding it while turning your phone back on
You should see 3 Android guys on skateboards
You should now be in Fastboot mode!
---------------------------------------------------------------------------------------
Setting up fastboot to work with your computer
Plug your phone in to your computer through USB
You should get a popup that your computer found the ADB Device for fastboot
When it asks you for drivers, make sure u select the option to locate the drivers from your computer yourself
Since you already have your Android 1.5r2 SDK installed, the drivers are in the same place where the ADB drivers are
C:\android-sdk-windows-1.5_r2\usb_driver
Make sure you choose the correct folder depending on your OS
Press ok to install the drivers
Fastboot should now be up and running
---------------------------------------------------------------------------------------
Make sure Fastboot is working
Open up Command Prompt
type the following
Code:
cd C:\android-sdk-windows-1.5_r2\tools === Press Enter
fastboot devices === Press enter, your device should be listed
fastboot shell === You should see a # in the next line
type fastboot and press enter for general commands
---------------------------------------------------------------------------------------
When Typing just fastboot in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
For more fastboot Commands go - Here
---------------------------------------------------------------------------------------
Congrats! You now have Fastboot and ADB up and running!!!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Nandroid Backup and Restore
Whats is a Nandroid Backup?
Like My Guide(s)? Donate
Nandroid Backup is a tool allowing all rooted g1 users to create a full system backup and restore which, when flashing and testing different roms can be very useful.
----------------------------------------------------------------------------
What You Will Need
A Rooted G1 phone, I suggest with the latest SPL (Guide above to install latest Radio and SPL)
Cyanogen's Pimped Out Recovery Image 1.4 - Download (IMG)
An SD Card with 100mb of free space
A Computer
SD Card reader or USB Cable
----------------------------------------------------------------------------
Installing the New Recovery Image
Download the recovery image from above, you will want the Download (IMG) download
Place the cm-recovery-1.4.img file in the root of your SD Card (Root = not in any folder)
Go back to your phone (Dont forget to unmount)
Open terminal and type in the following
Code:
su (wait for a screen to popup and press "allow")
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a "no space on device" error, try using fastboot and erasing first:
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
----------------------------------------------------------------------------
Creating a Backup using Nandroid 2.1
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
You will now see your new Cyanogen 1.3.1 + JF recovery screen (YAY!!! )
Scroll down to "nandroid v2.1 backup" and press on it to create your Backup
Let it work, it should take a minute or so
Once its done, your backup is complete and is saved on your sdcard in the "nandroid" folder
Recovering to Your Nandroid Backup
Option 1 (Without a Computer)
Note: This recovery will only recover your latest nandroid backup (the one with the newest timestamp)
Make sure u made a backup and its in the nandroid folder on your sdcard
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
Scroll down to "restore latest backup" and press on it
Let it work
Once its done reboot your phone and you backup will now be restored!
Option 2 (With a computer)
Note: With this option, you can use any nandroid backup that you have made, not just the latest one
1) First go in to your tools folder where you put your SDK 1.5r2 (C:\android-sdk-windows-1.5_r2\tools as reference)
2) Take the files adb.exe fastboot.exe and AdbWinApi.dll (found here - http://sharebee.com/16a06ebb) and place them in C:\WINDOWS\system32
3) Download the Nandroid Backup and Restore GUI made by Markazeh - Here
Extract the folder to your desktop or where ever you can easily find it (I put mine in the SDK folder for easy access)
4) You will need 4 files: Boot.img, System.img , Data.img, and Recovery.img
Place those 4 files in the same folder as the Nandroid Recovery GUI folder you just extracted in step 3
5) Boot your phone into fastboot mode (Turn off the G1 and turn on while holding the BACK button. If you have an older SPL then hold the CAMERA button and press POWER)
6) Once in fastboot (you should see a white screen with three androids on skateboards) plug your phone to your computer via USB. You might have to press the BACK key to turn it into FASTBOOT mode, or follow the on screen prompts.
NOTE: If you dont have the drivers installed please look one post above to setup fastboot
7) Open NANDROID_Recovery_GUI.exe, everything on the left hand side should be "found!"
8) Choose an option from the right to Restore All, Restore all except Recovery, or Restore Data Only. Let the program do its thing.
Once its done you can reboot and all your info from your backup should be restored!
----------------------------------------------------------------------------
Congrats! You now Backed up your phone and will/have restored it!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Credit:
Haykuro
Cyanogen
JacHero
NeoBlade
Markazeh
makethetick
XDA Community for your support and help
If i have forgot anyone, i am sorry, please tell me and i will add you
Excellent Guide bro. Although I have no need for it, still A++. Might want to include how to do a nandroid restore just a suggestion!
[EDIT]: I think this guide is worthy of a sticky! What do you guys think? ^^
You are the man!!!
Short simple and to the point!!!
0nly if all the guides were like this...
Thanks man!
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
PlatinumMOTO said:
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers and the USB Storage devices. That fixed it for me
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Mikey1022 said:
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Click to expand...
Click to collapse
yes I did I've had adb since sdk 1.0 and never had a problem like I said I actually have 1.0 and 1.5 on my computer so that when I root or re root other g1s I do adb but I noticed adb only works on it's version if I had a 1.5 g1 then the 1.0 won't work and same with the other way but that's not the problem I think I found it it's the clock switcher with 361 of Cyan because now I deleted it and restarted and it works just fine and I just tried to do the clock switcher and now it doesn't recognize either g1 again.
push apk via abd while in recovery mode?
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
ADB Commands...
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
ccunningham83 said:
Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
Actually, you can access fastboot from the bootloader, so it's available even if the recovery console isn't.
heldc said:
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
Click to expand...
Click to collapse
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
ccunningham83 said:
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
If you type "adb" in terminal you get a whole list of the options and what they do Also what part of nandroid backup don't you understand? Its just booting into recovery and alt+b. I assume you mean nandroid restores right? Drop me a PM maybe I can help you
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Its because the boot loader is dependent on the SPL and if you flash the "Danger" SPL which is basically the only one that causes problems, then you have a chance of bricking your phone. In that case, brick = no bootloader no recovery
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Well, actually, I recently had just this happen. My fiance got a g1, and somehow in flashing it for him, it ended up without a working recovery console. It wouldn't flash the recovery image from within the OS, so I had to use fastboot to flash the recovery image. So, it's quite possible to have a bootloader and no recovery console.
alritewhadeva said:
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
Click to expand...
Click to collapse
Ah ha, that's likely the problem, thanks!
Like I said, I want to overwrite a system app, the calendar. Every time I've done this with the phone "fully functional", the app ends up constantly force closing. I suspect this might be due to corruption from overwriting the app while it's running. I'm hoping that if I replace the app when the OS isn't on, the replacement app will work properly.
No problem You could also try replacing the calender app in a ROM and resigin it and then flash it. Have you tried rebooting after replacing the Calender app when the phone is I quote from myself " fully functional "?
I trying to extract the LiveWallpapers.apk from ctso's snackpack rom, and install it onto cyanogen's latest rom. I tried following the directions laid out by another member, but just can't get it to work. can anyone help me out with this. I'm just trying to learn what I can about flashing, cooking, and general tweaking of the android OS. there's a lot of great help here, but I'm having some trouble when it comes to breaking down the inner workings. any help is greatly appreciated. If you don't feel like typing a novel out, even a push in the right direction, for getting more into the inner working of This phone and android would be great.
EDIT: intstruction in fourth post.
nevermind, I should have kept trying stuff. figured it out.
Feel free to delete post.
hurrycaine3000 said:
nevermind
Click to expand...
Click to collapse
Instead of "nevermind" how about posting the method here to benefit others?
AndyBurns said:
Instead of "nevermind" how about posting the method here to benefit others?
Click to expand...
Click to collapse
good point, I guess if we all did that, it wouldn't have been as hard for me to figure out. Here we go then, I wanted to install the Nexus live wallpaper from ctso's Snackpack ROM, which by the way is now avaliable as a free download on the market. here's what I did
You need to have Root
Download Snackpack ROM from xda
Extract files (in this case LiveWallpapers.apk
Placed folder in Android Sdk-tools folder
open command window (Shift-right click in tools folder window)
plug in phone
Enter Recovery ( turn on phone while holding vol. down, navigate to recovery )
This is a good point to do a nandroid backup
turn on usb within recovery
in command window type
adb devices (press enter)
adb shell (press enter)
mount /system (press enter)
exit (press enter)
adb remount (press enter)
adb push LiveWallpapers.apk /system/app (press enter)
adb shell reboot (press enter)
once phone boots up you should be all set.
This process works for pushing any file to phone, from what I understand.
If I am wrong on any part of this please correct me, as I am still pretty new to the android back end. If you have any questions, let me know and I'll try to help. That's what it's about.
hurrycaine3000 said:
good point, I guess if we all did that, it wouldn't have been as hard for me to figure out. Here we go then, I wanted to install the Nexus live wallpaper from ctso's Snackpack ROM, which by the way is now avaliable as a free download on the market. here's what I did
You need to have Root
Download Snackpack ROM from xda
Extract files (in this case LiveWallpapers.apk
Placed folder in Android Sdk-tools folder
open command window (Shift-right click in tools folder window)
plug in phone
Enter Recovery ( turn on phone while holding vol. down, navigate to recovery )
This is a good point to do a nandroid backup
turn on usb within recovery
in command window type
adb devices (press enter)
adb shell (press enter)
mount /system (press enter)
exit (press enter)
adb remount (press enter)
adb push LiveWallpapers.apk /system/app (press enter)
adb shell reboot (press enter)
once phone boots up you should be all set.
This process works for pushing any file to phone, from what I understand.
If I am wrong on any part of this please correct me, as I am still pretty new to the android back end. If you have any questions, let me know and I'll try to help. That's what it's about.
Click to expand...
Click to collapse
Is there a Terminal Emulator with virtual keyboard support yet? If so, it's even easier that way... It takes three or four commands and done.
uansari1 said:
Is there a Terminal Emulator with virtual keyboard support yet? If so, it's even easier that way... It takes three or four commands and done.
Click to expand...
Click to collapse
There is one built into Cyanogen's ROM. What are the different steps? I was not 100% on how to use this.
hurrycaine3000 said:
There is one built into Cyanogen's ROM. What are the different steps? I was not 100% on how to use this.
Click to expand...
Click to collapse
Command lines should look as follows assuming you have the apk on the root of your SD card... make sure you figure out the correct command to mount /system first, as I can't remember it off the top of my mind:
su
mount XXXXXXXXXXXXXXX
cp /sdcard/xxxx.apk /system/app/
That's it.. That last command copies the file to /system/app and overwrites any file with the same name. All you need to do is reboot and you're done.
First I want to apologize for the double post (post in General)
I used odin to get froyo on the Captivate. That worked fine. When I try and root 2.2, the phone froze and now it won't get out of recovery mode. I have tried every combination I can think of to reboot the phone short of throwing it down the street, but I cannot get out of recovery mode. I am also unable to use the power button (ok key?) to select anything. I can use the volume keys fine for up and down.
One of the errors says:
"(Unknown error: 0) ensure_root_path_unmounted++
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
unmount(/mnt/internal_sd) attempt 1 (unknown error: 0)
Install default apk-files. finished.
Mind you, I have already tried to put the rooted 2.2 files on the sd card, but still to no avail. Any suggestions? I am really hoping this phone isn't rooted.
So you have a european firmware? Which one is it?
Sent from my phone so excuse the spelling errors
I just fixed it. Reinstalled the firmware with Odin and it's working fine now. Thank you.
dude how did you do that.. I have the same friggin issue and I can't fix it. I'm stuck in recovery mode all the time, as soon as I plug the phone in to charge, or plug it in the computer via usb, or push the power button, the damn thing goes into recovery mode and stays there. I can use the volume buttons to navigate up and down through the options and if I hold the power botton down long enough the phone will turn off and back on again. But if I press the power button once (as in select an option) it doesn't do anything. I tried every single option out there to get into download mode with the battery out and usb in and volume buttons then put bat in....etc nothing works. I need to get into download mode
anyone?................
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
What he said. Plus, I have had it happen sometimes that no matter what I always reboot into recovery. At that point I just adb reboot download and re-flash.
ok thanks. I know I said I have tried everything before but I wasn't completely truthful. I did try ADB though, but I don't think I was doing it right. I downloaded the SDK thing and started a command prompt from "start menue, accessories, and command prompt" but when I type the command "adb reboot download" nothing happens and the command prompt disappears. I don't have much experience with ADB, is there anyway you can give step by step instructions on how to do this? I would very much appreciate it.
Thanks
I found this thread on here "http://forum.xda-developers.com/showthread.php?t=517874" but still didn't help me much. Everytime I type cd c:\Android or any other command I get The system cannot find the path specified.
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
thanks I'll try that when I get home. I think this might take care of the problem, because I did keep the folder on the desktop and did not move it to C: folder. Although when I plug in the phone via USB, I still can't establish connection between phone and computer, but I will let you know how it goes after I get home tonight. and I did find some stuff about ADB through google so I might be able to do something with it tonight.
Thanks for the help though
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
bobbylx said:
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hi, so I did all that heres a copy and paste of what I did and results I got
"Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Shahed>cd c:\
c:\>cd c:\android-sdk-windows
c:\android-sdk-windows>tools
'tools' is not recognized as an internal or external command,
operable program or batch file.
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>adb reboot download
error: device not found
c:\android-sdk-windows\tools>"
I guess it can't be done because the device is not initiated to begin with
jatkins09 said:
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
Click to expand...
Click to collapse
tried that still nothing.. keeps saying waiting for device
drhusamali said:
tried that still nothing.. keeps saying waiting for device
Click to expand...
Click to collapse
Find the tools folder in the SDK you dowloaded and extracted, I found a shortcut to it scroll over the tools folder, hold the shift key and right click on the tools folder then choose open command window here.
When the command window opens type the command ADB shell then hit enter, then type adb reboot download then hit enter with your phone plugged into pc. This always works for me. You can always change the path by moving the folder directly to your c drive but this will work for you for now.
Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
This has saved my azz a few times.....Learn to use adb mode from PC inDEEED!!!!
Adb recovery adb download ....on and on.....
Ok now that we got Root on Arc thanks to our devs (Bin4ry...) it's time to move to the next step...recovery!
All the devs who want to discuss, brainstorm, work on and edit recovery for Arc are all invited here.
I don't consider myself a dev so I will let you begin...
Can you check which
/dev/input/eventX [X is a number]
is the Keys under the display?
On X10 it's
/dev/input/event2
f.e.:
You can try it with:
cat /dev/input/event2
now press the keys, do you see some output? If not just try the next one. Until you find the right one for the keys.
Regards
On mine (unbranded, unlocked, UK version) it's /dev/input/event1
Okay,
Flashtool is already prepared for this case!
So we can try it directly. Download latest!!!!! Flashtool (version 2.9.1) and download the chargemon.zip from my attachment.
Flashtool link:
http://forum.xda-developers.com/showthread.php?t=920746
Unzip the file and copy it into flashtool folder:
Flashtool/custom/xRecvery/
overwrite the original chargemon file!
Now open flashtool and and click "Ask Root Permissions", if that had worked you will see that the "xRecovery" Button on the right side gets activated.
Push it now!
When flashtool says -> Recovery installed.
You can reboot the device -> Now push the back button on the device during the booting process. If all works you will be in Recovery
Regards
Flashed the recovery, but it doesn't appear to be loading (tried rebooting while holding the back button, and 'adb reboot recovery')
adb reboot recovery won't work!
try opening flashtool ->Advanced -> Recovery -> Reboot in recovery.
Does this work?
Regards
Nope, didn't work!
ok, thanks for testing.
Can you check if the files are there correctly ?
use adb shell and type:
cat /system/bin/chargemon
do you get a readable text or some weird signs?
Regards
Strange symbols
As an update - I copied the correct version onto the phone (the script) and it still does the same thing
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Bin4ry said:
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Click to expand...
Click to collapse
File seems to be missing 'sh'. Also, getting permission denied when attempting to copy into /system/bin. (/system/bin permissions are root:shell, 755).
you're missing a file ("sh") and the adb push commands failed - I modified your batch file slightly, but it doesn't work, possibly due to the missing "sh" file
Code:
adb shell su -c "mount -o remount,rw /dev/block/mtdblock0 /system"
adb shell mkdir /system/recovery
adb push files\recoveryLT15.tar.bz2 /sdcard/arcrecovery/recovery/recovery.tar.bz2
adb push files\sh /sdcard/arcrecovery/recovery/sh
adb push files\chargerLT15 /sdcard/arcrecovery/bin/charger
adb push files\model /sdcard/arcrecovery/recovery/model
adb push files\chargemon /sdcard/arcrecovery/bin/chargemon
adb shell su -c "cp -rf sdcard/arcrecovery/* /system"
adb shell su -c "chmod 04755 /system/bin/chargemon"
adb shell su -c "chmod 04755 /system/bin/charger"
adb shell su -c "chmod 04755 /system/recovery/sh"
adb shell su -c "chmod 444 /system/recovery/recovery.tar.bz2"
Ups
Sorry i said before long day today!
Here is one with SH included.
Hope it works for you, if not i have to put it into system.img directly or you have to do all that on your own via shell directly!
Regards
Doesn't appear to be at the moment stuck on the Sony Ericsson screen when I choose reboot into recovery but it boots normally when I adb reboot it.
Powered off, then booted with back button held town, just bootloops
well this is quite good!
It seems the phone tries to start the recovery but for some reason it won't start!
It's designed the way that on next reboot it have to reboot normal, so no need to worry about this behaviour, it should be stick on the logo aswell if you push the key during boot now!
Let me think about this tomorrow, i have to think if the problem is the compiled file or the script! If it's the file we will have to wait for Z, he has the sources on the recovery and i'm just too lazy to reconstruct them for the ARC
But you can check if all files are in right place with right permissions and IF they are really the files ?
Regards
originlabs said:
Powered off, then booted with back button held town, just bootloops
Click to expand...
Click to collapse
But if you DONT press a button it boots okay or not ?
Regards
Bin4ry said:
But if you DONT press a button it boots okay or not ?
Regards
Click to expand...
Click to collapse
Yes, booting with no keys is fine.
Does the recovery mount and filesystems, and if so, does it write a log file?
Just look in the chargemon and extract the tar.bz2 to see how it works.
I think that the init from recovery (the recovery itself) is not working because of incompatible compilation.
So it cannot write anything into logs!
But it's good that the script itself is still working, we can create a working recovery now from this base
I go and get some sleep now! cu
Regards
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Edit: Service centre fixed it. Turns out its a pretty complex issue.
Click to expand...
Click to collapse
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
Hello, thank YOU very much! I got it to reboot properly and working. And I learnt a lot in the meantime.
Words cannot express my gratitude right now.
I have another question though, is it possible for me to wipe partition cache thru adb?
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
Okay, so I tried to do what you suggested, and got stuck at adb root. This is what I got in return:
"Adbd root cannot run as root in production builds"
So what I did was to skip to the second step,
"adb shell"
This is what I got in return:
[email protected]:/ $
I entered the command "su", granted su access on my phone using supersu (got a pop-up) and got this:
[email protected]:/ #
Moving on, I entered "cache /mount" and it repeatedly failed to mount.
I read up a bit of it and it seems like its because my bootloader is not unlocked.
But given the fact that my power button is malfunctioned, I cannot unlock it by normal means. I gave some thought onto PhilZ safe kernel but then the fact that my phone is susceptible to brick if I unlock the bootloader (there will be a data wipe right?) makes me stuck at where I am now.
What are your recommendations?
Additional info on eMMC:
[email protected]:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20
gives back: 19 (susceptible)
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type
gives:
Name: VYL00M
HwRev: 0x0
FwRev: 0x0 (not completely safe)
Manfid: 0x000015
Oemid: 0x0100
Date: 01/2012
Type: MMC
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
you saved me big time!!
I have almost the same problem
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
Did you find a solution for this?
My Samsung j7 is stuck in recovery mode and power button is broken...and my USB debugging is also ON but phone is NOT detecting On PC...not even in DEVICE MANAGER...I checked in ADB deveices command but still nothing...help me....
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
I also have the same problem, my phone is now stuck in recovery, and without power button I am not able to bring it out of recovery mode, did you manage to find a fix for this? My phone is not getting listed in "adb devices"!
Phone:SM J200G
After installing stock rom via odin
I enter into recovery mode and forget to on USB debugging. Also my power button dead.
What to do? Now?
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
please help i have the same problem but my device is not recognized
bryll1022 said:
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
Click to expand...
Click to collapse
please help i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
did you find a solution i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
same did anyone find solution for this?
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
when i plug my phone to pc its not connecting if i use commang adb reboot its say "error: no devices/emulators found"
Ive encounter that problem with j4 + what i did is just let the battery run out after that be ready to press button for download mode and insert charging cable to phone, hope this will help on your problem
x33eraser said:
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Click to expand...
Click to collapse
Sorry i hope i post this right first timer your guide didnt workt but i found a workaround:
usbc to usb adapter i tryed a mouse not working but my cheab truest cxt tastatur ACCEPTED THE ENTER BUTTON
and i came out of this because only repair loking cost 60 bucks .not with me i hope this help others too
i am doing a tiktok video on it(guide) PrestigeWorldWideUS
buy usbc to usb adapter i try your keybords sorry my english