Related
The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.
sorry, got it!
blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?
Don't forget fastboot boot for testing images. My most used command
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.
dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.
Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.
pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.
recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.
seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it
I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.
A couple of days ago I flashed Eclipse v2.0, wanting to change my phone up a bit I had been on shift3r for a few weeks. Anyways, just now I was trying to copy some modules into my /system/lib/modules to overclock my device and was having issues copying within my phone. So I tried to use an adb shell to do so, but I keep getting the output of the device being offline, this is what I'm getting:
-NV57H:~$ adb devices
List of devices attached
0A3BAF200C014015 offline
And I have done a search, where some people were having trouble using certain cords, mainly with Samsung devices, and switched cords with success. This does not apply in this situation as I have used adb many times with the cord I'm using, and also I did try to switch cords anyways. Also the only other thing I saw was a situation involving driver installation and re-installation creating problems. As I am on Lubuntu, and not Windows, this does not apply to the situation because I have neither installed or re-installed drivers. My adb is setup properly because I have been using this computer for a couple weeks now and it was working previously. Any ideas on anything that could have happened? or maybe I should switch ROMs?
additionally: on my file manager, in the address bar for my device when it is plugged up, it is seeming odd to me, this is now what the address is showing for my device's sdcard:
gphoto2://[usb:002,007]/
I think I might have messed something up on my Bionic. If you read the first post I was saying how I tried adb on the same computer I've been using, AFTER flashing Liberty. Well I've gotten rid of Liberty and went back to SHIFT3R to try to fix the problem, and my problem is still looming. I have tried on Lubuntu and Windows, and my girlfriend's Incredible 2 works on both of the OS's with the same cables I'm using as well. I remember the other day when I was flashing Liberty, I had to mount my USB while in recovery to move the file onto my SDCARD because it had vanished once I tried looking for it to flash it. I remember when I tried to eject my phone from my computer (lubuntu), it said that it was busy and could not unmount the phone, after the file transfer screen went away as well. And then I waited a few minutes and tried again, it said the same thing, but I unplugged the cable anyways and unmounted USB in recovery. The file flashed fine so I know it was not still transferring the zip file. If anyone knows what I may have done or what I may be able to do to fix this let me know. I just wanted to update the thread with my most recent trials and errors in fixing it. Thanks to anyone who can guide me. I have never had issues with adb before.
O man i really hope someone can help us with this issue.
I have the same problem..
I am trying to use the path saver, and it keeps telling me device offline.
RSD lite won't even recognize it.
HELP!!!
Me too
I had the same problem... I wanted to upgrade the radio on my Bionic to the .901 load... I could not get adb to see my device.
Using Windows 7 64 bit (Ultimate).
RSD Lite would not recognize device either.
Decided "Screw it", I'll just go back to my nandroid backup... which didn't work either.... soooo... here I am.... stuck.
Off to google I went... I don't know which of these fixed it, but it is working now... here is what I did.
Found a thread that stated "run your commands from the 'C:\platform-tools' directory... so I took all of the files from the "Bionic Path Saver 1" and copied and pasted them into this directory.
Secondly, instead of just double clicking the upgrade batch file (runmebbb.bat) like I was before, I opened a DOS command shell -IN ADMINISTRATOR MODE- and ran the batch file from there.
It immediately kicked off and I was off and running.
For those of you that don't know what I am talking about, I was upgrading... using instructions from this thread:
http://forum.xda-developers.com/showthread.php?t=1433783
I hope this helps... it bugged the crap out of me... but the feeling of relief certainly makes up for it.
Well the thing is it doesn't work on windows or Linux with my bionic. I've tried various Android devices that I own and all of them work on both of my operating systems except for my bionic
Sent from my DROID BIONIC using Tapatalk
Same issu
I just installed Eclipse 2.2 on my Bionic and now i am getting the same issue. Has anyone found an answer or a fix for this? Also, does the .902 patch have anything to do with it? Any help is greatly appreciated.
Once i had this problem the only way i fixed this was by using RSDLite to flash a FXZ. Changing ROMs didnt work, nothing worked but that. It wont affect RSD reading the phone in AP Fastboot mode. Just make sure you install moto drivers and have the newest version of RSD Lite. That worked for me, now I have my adb back
Sent from my Transformer TF101 using xda premium
Are you using Safestrap recovery? If so I think that may be the issue.
Try downloading "ADB Over Wifi" from the market.
Then "adb connect iport"
The widget should show you ip/port when you activate it.
Bionic 2.2 Eclipse adb device offline
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
s.wyckoff1 said:
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
Click to expand...
Click to collapse
First of all, it automatically adds 5555 into your address so instead use
Adb connect 10.0.2.2 or whatever your ip is. And as far as not showing your device with a USB cord, try various other cables. I have over ten cables and maybe two work with my bionic. I urge you to use as many as possible before my next recommendation. This problem screwed with me for a couple months and finally i booted into fastboot mode and FXZd my phone. I booted my phone up after that and adb worked perfect. I don't know what causes this.
Sent from my DROID BIONIC using xda premium
Eventually I discovered why adb wasn't working. Apparently there was no adb daemon running. I came across this in a different thread awhile back. Once I copied it to my phone's /sbin/ directory (there was a link to the file in this post http://forum.xda-developers.com/showthread.php?t=974824) and ran adbd from a terminal I could use logcat. However it was removed everytime the phone cycles power so only a temporary fix. I was considering trying another rom instead of eclipse 2.2. It was also buggy in that when I tried to do an adb install it broke terminated the daemon.
If you're using linux I always do "sudo adb start-server"
Sent from my DROID BIONIC using Tapatalk 2
***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.
You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk
If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.
link not working
anyone have updated link that works to download this?
yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra
I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk
nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .
I am going to update the post and host the files. There is also some extra stuff i will put up for download.
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse
using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?
BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk
What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5
This worked great.
Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.
Hi,
My GF broke the screen on her Galaxy S i9000 today. Completely black with She would like to get a copy of what's in the internal memory. Initially I thought I'd install CWM and copy it out using ADB. However, ADB does not work. It will intermittently be able to see the device with adb devices, but adb shell fails, and so does adb backup. After trying three different USB cables (two of which I know to bee good) and two different cf-root recoveries (CF-Root-XW_NEE_JVH-v3.2 and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS) I have concluded this is most likely because the USB port on the phone was damaged on the trip to the ground, and is unable to keep a connection. Heimdall kernel flashing succeeded two of three times though, so it is strange. However, it was impossible to connect to the phon with both Kies and as Mass Storage device while it was still booted into Android, so it is most likely the USB port that's the problem.
Anyway, I can see one possible solutions that is likely to succeed:
Is it possibly to, by way of init scipts or similar, to make CWM copy everything from the internal SDcard to the external one, as well as everything on the /data partition?
Have someone already made such/ sa similar script a script, or could anyone possibly be willing to write one?
Note: I can't flash CWM.zips on the phone, I can only flash imagefiles via heimdall (which is like Odin). Is it a all possible? I guess I COULD flash another CWM, come to think of it, by putting it on the sdcard and follwing keyprrss instructions.
Thanks for any help or suggestions in advance, they will be appreciated.
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
bullpen7979 said:
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
Click to expand...
Click to collapse
you can push adb when the phone is connected as a camera. To connect it via ptp, you just scroll down your notifications bar and click on the usb notification, you can switch to ptp there. But like i said, adb works when connected as a camera device, so you are doing something incorrectly with adb. Possibly the commands you are running. The OS for your computer might be causing the problem (but that would mean oyu have the wrong stuff downloaded to adb with the computer set up you are using). You don't have the correct drivers. You are using a faulty data cable. you are using a usb 3.0 port that isn't compatible. it is an endless list. Also, you can copy stuff to your device in camera mode as well.
also would like to note that whether you phone is rooted or not has nothing to do with your ability to use adb or push files to your phone.
finally, this is a question which should go under q&a not the general discussion subforum.
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
so whats the problem. you have adb working. What do you mean you can't copy things to the phone. What error do you get when you try to push a file to the sdcard on the phone? You see your phone in the list of devices so you can put files on it that way too. Really confused at your dilemma.
you trying to root? you trying to push files to the phone? IDK, but you clearly should be able to push them if you have adb running. Perhaps you aren't running the right commands to push files to your phone.
Don't you have to have USB debugging on?
Sent from my XT1060 using Tapatalk
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Click to expand...
Click to collapse
Unless you have another android device connected to your computer, your X has USB Debugging mode turned on, and Windows & ADB properly sees your phone.
As jayboyyyy posted, in this state you can use ADB to push files from the PC to phone, or pull files from the phone onto the PC, assuming you are using the right commands. But if all you are looking to do is copy files back and forth, this is overkill as you can do it with windows. ADB is usually only need for hacking and flashing your phone.
As I said in the other thread... Please include what you were doing and what the results are. You haven't given us a complete enough of a picture to understand 1. what you are trying to do. 2. Any/all steps you have taken. 3. EXACT error message you are receiving.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader. But your second paragraph starts saying you can't get the thing rooted to save you life.. So which is it? Are you rooted or trying to root? If you are trying to root, what process are you trying to follow? What step in that process are you stuck at? What did you type and what did you get back?
I know you are probably frustrated, but its just as frustrating on this side when you don't give a complete picture that allows us to help you. Look, rooting and hacking isn't easy. It can even result in turning your phone into a paper weight. So these details are important so we don't screw things up and add to the headaches and frustrations.
bullpen7979 said:
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
I'm not sure what you are doing, or trying to do, as you said in the first post that you unlocked the boot loader and rooted.
The Moto X wont show as a drive letter in "My Computer." Even if USB Debugging is on, it should show up as a "Media" device, or Player type device with an icon in a separate section from your hard drives, DVD drive, mapped network drives, or even USB memory sticks/flash drives. It does this because the X supports/uses MTP/PTP, and NOT USB MASS STORAGE MODE.
MTP/PTP wont show a drive letter in My Computer. This is by design. You don't have to "stop" or "eject" the phone from windows when you are done. This mode also allows the phone to access the "storage" or emulated "SD" partition at the same time a connected Computer can.
USB Mass Storage mode will give you a drive letter in My Computer, IF the phone supported it. However the X doesn't, at least not out of the box, and I'm unaware of any app or hack to enable this. In USB Mass Storage mode, the PHONE looses access its storage partition or emulated internal SD card while the PC is connected. You'd need to "stop" or "eject" the device when you want to disconnect form the PC in order to prevent data corruption of the "emulated SD"
So again, its important for us to know exactly what you are trying to do.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader.
Im sorry I was unclear. Bootloader is unlocked, but I am not rooted. What I said was that I had another thread about getting it rooted.
I'm sorry for the mis-speak. And I'm sorry I'm being such a pain, but others in the thread I'm referencing are clearly having the same issue I am. I just need to know what to do to obtain root access if my bootloader is already unlocked. To be clear, I do NOT have root access.
This is my procedure.
Start with this link:
http://forum.xda-developers.com/showthread.php?t=2509676
Download Cydia Impactor. Check.
Download RockMyMoto.zip attachement. Unzip two files to directory x. Check.
Download PuTTYtel file "puttytel.exe" Check.
Step one. I have my ip address. At bottom of wireless config on phone, it is 10.59.1.6. So far so good.
I run adb shell getprop dhcp.wlan0.ipaddress just to be sure. same ip addy. Good.
I start command window. push the two files to the phone. all is well.
Step two i open the puttytel window and proceed to run the exploit
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
and I can't run the damn thing because i get PuTTytel Fatal Error
Network Error: connection timed out.
exactly like this dude: http://dl.xda-developers.com/attach...f04a/5290120c/2/3/8/1/6/0/9/1384014224630.jpg
The end. I read the rest of the thread, and post #22 is the first of about five other posts that mentions the same time out problem, a solution for which is NEVER ADDRESSED, except indirectly as a possibility that the the two devices are not on the same network. My wireless card is on dhcp and the phone is the IP address above.
that's where it stops. I can't run the exploit because i can't type the command fast enough. Several people mention this problem, but I read all SIX pages of the thread and this defect is experienced my many and adressed by nobody.
This is driving me stark raving Bat S#!+ crazy.
And yes I have USB debugging on.
If your boot loader is already unlocked, there is another process.
https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Is the process and while I think that twrp version should work, you might need the older version. Had to take my mom to the hospital so not in a good position to find older if newer doesn't work.
EDIT: this thread -> http://forum.xda-developers.com/showthread.php?t=2536200 has some discussion too