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.
I have rooted my phone once before like a year ago, and it worked like a charm - but when the official 1.6 came out it apparently unrooted me (I assume thats what happened?) All I know is now when I try to run root required apps it tells me I'm not rooted.
So I figured to just start over from the beginning. I downgraded to RC29 no problem, but when I get to the telnet step it shows a pattern of question marks in diamonds, with boxes separating them. Like this:
<?><?>[]<?><?>[]<?><?> <?><?>[]<?><?> #
I run the commands anyway, (with the Recovery Image and HardSPL on the root of my SD card) - with each command returning two hash marks # #. But the commands don't seem to do anything, because even when I finish ROM Manager tells me I'm not rooted.
Back in Telnet, I can 'ls' to see my directories, including a root folder - but I'm not sure that means anything.
Not sure where to go from here - any help would be greatly appreciated...
-TQ
........................................
The following Observation was made :
Wrong Section. Belongs in Q/A
K so when u go in adb and type adb shell do you see # or $
Please let us know.
Apologies for posting in the wrong forum. And thanks for moving it.
I can't connect to my phone via ADB - I just get 'device not found' even though I have the USB drivers downloaded. If I do 'adb devices' it shows a blank list.
I've looked into how to resolve this, but with no luck. The phone shows up in device manager under the 'Disk Drives' category as "HTC Android Phone USB Device" when everywhere I read says it should show up under the ADB interface section as "HTC Dream Composite ADB Interface".
I've tried USBDeview to reinstall it properly - no dice. And I tried manually updating the driver with ones I downloaded, but windows says I already have the best driver installed.
I don't know what to do now...
Common Telnetd problem - unable to root
What's up xda!! This is my first post ever!
..please be kind.
I am experiencing a n00b issue w/ rooting my G1. So far I have been able to get up to where I am on RC29 and <enter>reboot<enter> successfully reboots my phone! This is great up until I'm told to hit the enter key twice, type "telnetd" and press enter. after the phone starts up.
FOOD FOR THOUGHT:
I believe I have ADB drivers installed properly installed
I am able to run Droid Explorer and it connects and recognizes my unit
I also have the following files on my SD CARD prepared
recovery-RA-dream-v1.5.2
update.zip
I have also read that ONE solution is to look for someone with an current T-Mobile Monthly Account and ask to borrow their sim card so I can install the Telnetd and enable WiFi past the Google Login(I have asked a fellow and I was told an aggressive NO, apparently people are afriad of anything related to hacking and their SIM CARDS)
I have the G1 Original SPL currently
Also when booting into recovery Alt+L gives me the Log that shows ""
I hope to have made an appropriate first post granted I've been searching for answers and help and am still experiencing issues. I look forward to participating in this forum in the future looks like you guys have been having fun for a while!
Any suggestions are definitely welcome.
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
RE: Maybe try to update your phone to Android 1.6
raven_raven said:
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
Click to expand...
Click to collapse
Hey raven, thanks for the reply!
By doing this update are you suggesting that I use the G1 Original SPL to flash the Offical Dream RC29 ROM (OTA_ROM RC) listed on that page, IF so what should follow that? Would I be allowed to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC) and the Official RC33 Update - from RC30 to RC33 (OTA_ROM RC) with the same update.zip that came from the G1 Original SPL also?!
I'm lost with your suggestion, b/c if it requires me to enable WiFi to get the OTA update I would still be unable get pass the Google login. Would I not be stuck back to where I am now? As of right now, I am at the Android Welcome Screen with the G1 Original SPL and RC29 that were not listed on that page AND so far unable to get root b/c of unavailability of TelnetD and WiFi. I will proudly follow those instructions?? Sounds like following the flash of Offical Dream RC29 ROM (OTA_ROM RC), that I would need to somehow use a method to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC)...I think?!
Excitement!!!!!
EXCITEMENT!!!!!
I used:::::
1- Plug your G1 & Install Drivers.
2- Without Sim Card in Your G1, <enter>setprop persist.service.adb.enable 1<enter> Even though u dont see what u typing, but u are actually executing a Command on your G1 to Enable USB Debugging in Settings.
3- Once u Execute that Command USB Drivers will be Installed again, but this time will be recognised as ADB Interface.
4- Click Start>Run>cmd> to Command Prompt
5- Type c:\adb devices (If your Device is Connected u will see it)
6- Restart your G1 but now With Sim, to see the Activation Screen then Plug USB Cable & Type c:\adb devices (to make sure u are connected)
7- Type c:\adb shell (U will see a $ sign) Just Copy & Paste this into Command Prompt (am start -a android.intent.action.MAIN -n com.android.settings/.Settings) The Settings Screen will Appear, now Switch on Wi-Fi & Connect to the Internet.
8- Now u can either Login with your Existing or Create New Account with Google.
Click to expand...
Click to collapse
here is where I was lost, I'm sure many are running into the same issue. The adb.exe that is located on my PC is what the command prompt should be finding, however there are other folder possibilities in where the application is ran to even use the adb functions. For instance, my adb.exe was installed in "c:\android-sdk-windows\tools" instead of strictly on the "c:\" I was not aware that I would be controlling the phone unit through my command prompt as well!! silly me, something so easy can become one of the biggest problems. ONE MONTH LATER!!!! THANKS XDA!
Hi Everyone!
I was trying to change the sales code using remount command by rotohammer but at terminal emulator and ADB I get remount: not found.
ROM: Overcome 1.4.2 with 2.1.2 kernel
Terminal Emulator
ROOTED.
Regards.
Dear DarkPal ,
if u only want to actually change your product code, u can use SGS csc selector
after that when it reboot u , it will see yellow words show
"installing multicsc-XXX" XXX is the product code.
For the overcome rom, there have 7 product code for u to choose, but I don't exactly know which is for your country.
To verify , u can connect it to KIES and it will show your product code.
For the ADB issue, which kind of flashing process u use? hemediall or odlin?
I sometimes can't have ==> adb devices as I have 2 I9000 and 1 TAB, always flash TAB and I9000 for my friends. So the usb driver sometime can't work. as too many device have being connected. If this happened, I will try step by step in the following until the driver work again.
re-install device driver by KIES
adb kill-server and than reboot the computer
control pannel=>system manager=>device manager=>uninstall samsung usb driver and than connect the phone and window will reinstall the driver.
regedit user-local-key =>samsung=>kies=>deviceDB=>clear all things and then reboot
usually these steps will let me redetect the device
But in some older rom of I9000 , it never be connected as the rom fault in USB connection app. But this will not the case for overcome rom itself as I tried it before and have no issue,it work fine..
hope this help
p.s. if u just want to hack KIES, use spoofFW, it have some preset product code for the western country, after hack you can update through KIES to the newest official firmware of your own country.
p.s. use this command in adb shell or terminal emulator on your tab to get in to csc selection section:
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
ADB does detect the device my friend and gives it a number. The issue is that some commands in adb are not working. Remount command being one of them.
I flash through ODIN.
Thanks for SGS selector
bump.
I still get the remount: not found which is rendering ADB not usable for me. Any help would be appreciated.
I asked the same question a few weeks ago, using same odlin.
I was hoping rotohammer would chime in and state the issue.
Went to Android SDK and downloaded all they said to get, and still no remount.
Hey guys, it took me 3 whole days to find the right way to downgrade.
Note: This is to be done at your own risk; I am not responsible for any damage or harm caused by this process.
Note: Information in this guide is taken from the works of following Authors:
1. wag3slav3: (http://forum.xda-developers.com/showthread.php?t=725430)
2. Paul (http://android.modaco.com/content/ht...rom-froyo-ota/)
3. TheDeadCpu: (http://forum.xda-developers.com/showthread.php?t=746454)
Please Follow the Instructions Carefully; to ensure success!
Items Required:
1. HTC Legend
2. 1 MicroSD Card (Gold Card)
3. 1 Micro USB Cable
4. Full Charge Recommended
5. Windows OS (I used W7)
Other Stuff:
1. Android SDK
2. hack4legend-v5.zip
3. RUU 1.31 for Legend
Common Errors Faced in the Process:
1. c---rw---- INSTEAD OF crwxrwxrwx
2. ADB Server timed out
3. Various RUU Errors
4. Visionary Not Working/Opening
Troubleshoot:
When you attempt to root you may face ADB timed out errors, it can be very annoying – there are various reasons for this, for me it was HTC Sync that was conflicting with ADB, shutting it down allowed me to boot into the custom recovery (step2 in the root process).
If you run into various other RUU errors (such as: unable to load boot loader, which was fixed by following step 3 correctly.) while trying to downgrade, most likely you didn’t do it correctly. Try doing it again and it should work.
Visionary Not Working/Opening (Solution: Download from phone browser: http://content.modaco.net/dropzone/c...ryplus.r13.apk)
Recommended to Back up Data:
1. Contacts:
You can save you’re contacts from you’re legend by clicking contacts, menu, import/export and export to SD Card.
2. SMS:
Get the SMS Backup and Restore App form Market, Install and Save it on to the SD Card.
3. Backup Complete SD Card:
Copy all the contents of the SD Card and save it onto the PC.
We start now;
Step 1:
Install Android SDK
Extract hack4legend-v5.zip to C Drive
Step 2:
Have adb in your path, or move the files contained in hack4legend-v5.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
crackin.sh
or in Windows
Code:
crackin.bat
Your phone will reboot 5 times.
You WILL see several error messages.
it looks like this c---rw----
c---rw---- 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
You’re done with this.
Step 3:
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
Step 4:
RUN RUU to downgrade to 2.1 – it should be possible to do so now.
Hence, you will be downgraded to 2.1 and you can use the normal way to root your legend.
All I can say is that the CM7 Mod is so fast on the Legend, no lag whatsoever, it's beyond! (will post a video 4 you guys)
End.
Forgive me if i seem rude.Hasn't this been covered in many other threads before?
I searched the site but never found this same method, is a combination of 2 or more guides at one place, also touching on some of the common errors faced when downgrading.
after this command '/data/local/flash_image misc /data/local/misc1-2.img'
it says "flash_image not found"....
So? Find it and put it there via adb.
but this is what i try...
i have both files in c:/hack4/ and in c:/android-sdk-windows/tools/
i wright in command " /c/hack4/flash_image misc /c/hack4/misc1-2.img"
and i have the message "flash_image not found"
am i doing something wrong?
i have also tried "/c/android-sdk-windows/tools/flash_image misc /c/android-sdk-windows/tools/misc1-2.img" the same problem...
What hboot do you have? Look at the guide for YOUR hboot ive had different Hboots across 2 devices and needed to use the right guide for the right hboot
bonesy said:
What hboot do you have? Look at the guide for YOUR hboot ive had different Hboots across 2 devices and needed to use the right guide for the right hboot
Click to expand...
Click to collapse
i have 1.01
alfagama said:
i have 1.01
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10217134&postcount=1
bonesy said:
http://forum.xda-developers.com/showpost.php?p=10217134&postcount=1
Click to expand...
Click to collapse
i have tried this to... the same problem
Are you sure you executed these codes from Guide 2 ?
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
Click to expand...
Click to collapse
These is supposed to upload the images required on your phone and be exventually be executed on your phone to replace the image
ps: im no expert but i just flashed mine recently and i had to read the guides several times to understand the logic behind each guide to avoid mistakes some had with their phones...
alfagama said:
i have tried this to... the same problem
Click to expand...
Click to collapse
Then you cant be followign the guide right.Have you done temproot?
yes i tried with visionairy13 and 14 both time i had su= #
a noob question...'/data/local/flash_image misc /data/local/misc1-2.img' =" /c/hack4/flash_image misc /c/hack4/misc1-2.img" where i have the 2 files...
Blay0 answered correctly...i didnt
alfagama said:
a noob question...'/data/local/flash_image misc /data/local/misc1-2.img' =" /c/hack4/flash_image misc /c/hack4/misc1-2.img" where i have the 2 files...
Click to expand...
Click to collapse
Nooooooooo dammit! You have just pushed both those files to your phone!!!!!!!!! Go to your phone shell via adb, execute su to gain root privileges and then execute flash_image on your phone not on your PC!!!!! It doesn't really matter where on the phone do you have both as long as they are both in /data dir and don't prepend anything!!!
i am very confused now , can yoy help me step by step?
i run on my phone visionairy and then i click on temproot.
then i run on my pc cmd and i give the comand "adb shell" and then i type su and it says #...
after that should i give the next command on the pc again or on my phone, and with what should i replace the /data/local/ ...?
Pay attention dude!
Open two command prompts. Name them ONE and TWO. You gonna use ONE for copying files from your PC to your phone using adb push. You gonna use TWO for connecting from your PC to your phone using adb shell and execute all commands meant to be executed on your phone there. Now use ONE to copy (adb push) a program called flash_image to your phone's directory /data/local. After you do that use TWO to connect to your phone (adb shell), execute su to gain root privileges (you get # prompt) now in the same commnd prompt (that's TWO) change permissions of program flash_image you have just copied to your phone in ONE. Then also on TWO execute flash_image program with parameters from above.
If you don't understand what I'm saying you better sell that phone and instead use phone booth. In fact sell all your hi-tech stuff including your PC. It would be much safer for you and even for us.
Sent from my HTC Legend
alfagama said:
/c/hack4/flash_image misc
Click to expand...
Click to collapse
Faaaairly sure you're gonna want to write C: and not c/ dude, regardless of what other stuff you're doing wrong.
BlaY0 said:
Pay attention dude!
Open two command prompts. Name them ONE and TWO. You gonna use ONE for copying files from your PC to your phone using adb push. You gonna use TWO for connecting from your PC to your phone using adb shell and execute all commands meant to be executed on your phone there. Now use ONE to copy (adb push) a program called flash_image to your phone's directory /data/local. After you do that use TWO to connect to your phone (adb shell), execute su to gain root privileges (you get # prompt) now in the same commnd prompt (that's TWO) change permissions of program flash_image you have just copied to your phone in ONE. Then also on TWO execute flash_image program with parameters from above.
If you don't understand what I'm saying you better sell that phone and instead use phone booth. In fact sell all your hi-tech stuff including your PC. It would be much safer for you and even for us.
Sent from my HTC Legend
Click to expand...
Click to collapse
my friend i pretty sure that you know much than i do...
but for your information i am 48 and i am the last 20 years involved with computers and mobile phones.... over that 20 years i have learned at least to follow instructions (if they are clear), so once again thanks for your help.
my problem was that after unistalling sync 3.0 and installing sync 2.033 i have not uninstalled the drivers so i had problem.
after fixing that everything went smooth.
So after 20 years in computers, you actually found out that the problem was on your side and not in the instructions. Too bad. My mom is also been using computers for more than 20 years. She knows what is monitor and that she can move cursor around with the mouse.
BTW what has version of sync to do with your confusion? You are trying to say that "flash_image not found" error had something to do with sync version? Ohh, give me a break...
And as far as clear instructions are concerned... I guess they are pretty clear if 99 ppl find them OK and one (that's you) doesn't.
Don't want to be rude but maybe 20 years was too much and it is time to start something completely different.