I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.
Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492
Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??
What!
can you get in the recovery?
Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.
Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!
Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?
Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window
Related
Hi guys.
Sorry for this noobish post, but i cannot remember for the life of me on how to install things by using 'adb' - i know there is an option on the phone, but where bouce is it? I used it when rooting, but i just cant find it.
I'm trying to install a new boot image, but when i go into cmd i type "adb remount" and the reply is "device not found"... AndroidSDK is in my C directory.
Another EDIT; I just rebooted my device into the recoverymode, and i didn't see ndroid back up thing, does that mean my phone hasn't actually been rooted... - But my phone is deffently debranded.
Thanks if anyone can help my noobish style.
Slim.
When in recovery mode you must have the driver installed. If you enter 'adb devices' it should give you the serial number of your device, if the driver is installed correctly.
To enter the recovery menu you must run the recovery-windows.bat from modaco if using windows or a similiar file (recovery-linux.sh, recovery-mac.sh) according to your operating system. The file should be run when in recovery-mode or else it returns a whole bunch of errors.
Awesome, thanks mate. Just what i needed! Could i have advice what driver i need to be able to acsess the adb?
I just use the driver supplied in the newest version of ADB.
You can get it here. usb_driver.rar
Or else just install HTC Sync from htc.com. It also has the driver files needed.
Remember to have USB Debuging enabled from the Programs/Development menu.
I have been helping out with rooting HTC Aria's over in IRC in the #liberatedAria channel for a while now. A lot of people have problems with drivers on Windows. The easiest solution for them to do this has been to download an Ubuntu LiveCD and use it to root their phone, however many people know nothing about Linux at all and feel daunted by this.
I have created a customized Ubuntu LiveCD that has a script that downloads the Unrevoked Teams reflash, untars it, and runs it as root to root HTC's phones that are supported by the tool (HTC Evo, Hero, Aria, Desire, and Incredible). It also has the Android SDK included and added to the path so it is accessible from a terminal. Everything can be done without a single change to the computer you are doing it on.
Download the iso image here:
MD5: 9a34c343e8f610e66674af9384334bf6
ubuntu-10.04-desktop-i386-HTCROOT.iso Primary
ubuntu-10.04-desktop-i386-HTCROOT.iso FileFactory.com
Burn the iso to a cd (This can be done with any cd burning software, imgburn found here is free)
[Optional]
If you do not have a CD drive, you can create a bootable flash drive by using the tool found here:Pendrive Linux
Put the CD into your computer cd/dvd drive and reboot your computer.
You must make your computer boot from CD, there are many different ways to do this depending on what computer you have, most recent computers have this enabled by default. Here is a guide that may help if you can't get this to work:Enable Boot from CD
Once it boots from the cd it will show a small picture of a keyboard and a person, do not press anything here and it will come to a window that will allow you to select your language.
Select your language and click "Try Ubuntu 10.04 LTS". This will boot up to a standard Ubuntu livecd desktop.
On your phone click menu, settings, applications, development, usb debugging
On the computer click "Places" on the top menubar and click "Home Folder". This will open a file explorer window, in that window is a script called "reflash.sh".
Double click reflash.sh. A window will pop up asking you what to do with this file, click "Run in Terminal". This will go get from the internet the current version of Unrevoked recovery installer from unrevoked.com/recovery, unzip/tar it, and run it as root.
Once it is complete you will be looking at the unrevoked3 screen and you should follow the prompts on screen.
You will then follow the prompts on the screen to plug in your phone, from the notification pane in android select charge only.
unrevoked3 will reboot your phone twice and leave you in ClockworkMod Recovery. On the computer at the bottom of the window it will say "Done".
Close the window, if you do not need to do anything further you can shut down the machine and be back in windows with nothing changed on your windows system.
Congratulations, your phone is now rooted and has ClockworkMod recovery installed.
There are other guides to setup of sideloading for the aria as well as how to load roms. You can do these using this live cd as well, this is a full ubuntu 10.04 livecd with only games and open office removed, and the unrevoked3 installer and the android sdk installed, it is already in the path and you can use adb commands from the terminal without having to switch directories(however it can be found in /opt/android-sdk-linux_86).
I would like to thank The Unrevoked team for making such a nice tool, and website that made this possible. I would like to that the guys in IRC on Freenode.net channels #liberatedAria and #koush for everything I've learned recently as well as all the great work they have done. Thanks also to Attn1 for making some nice roms for the HTC Aria and gave me the idea to create this. Thanks to Downer3d for the torrent mirror. Thanks to Neolobster for the new faster mirror.
Allowing Non-Market Apps using this cd on the stock ARIA rom:
Click Applications in the upper left corner.
Go to Accessories, click Terminal. This will put in you a terminal in the default users home folder. Because ADB(and android sdk) are in the path you do not need to change any directories. Start the phone in CLockworkmod with data mounted from the partitions menu and plug the phone into the computer.
Code:
sudo su
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
What this does:
Switch user to root.
ADB pulls the file that contains the setting to allow non market apps down to the machine from the phone.
The next line runs a sql update of the field install_non_market_apps in table 'secure' and sets the value to 1 (on).
ADB then pushes the file back to the phone in its original location.
You then use ADB to reboot the phone to enable it.
Thats awesome!! If I didnt already go through all the trouble of doing it on my Windows box I would definitely try your live CD. I already have 10.04 installed on my laptop and I never really thought of trying it on there. I wonder if it would have been easier....oh well. Thanks again. Im sure there are plenty of people out there that will find this very useful.
Much easier. And yes, this IS awesome. Great job, Shad0wf0x. This kicks ass.
This is a fantastic idea, I had a ton of trouble rooting my Aria on Win7 x64 and downloading and using Ubuntu 10.04 eventually proved to be much easier. If your iso works as advertised I can see this possibly being the most pain-free solution for annoyed Windows rooters.
Sent from my HTC Liberty using XDA App
This works wonderfully for rooting and sideloading apps (the only issue there was figuring out I needed the root account and permissions). As painless as a dentist trip.
If I was to install Ubuntu from that LiveCD, would it still have the Android SDK on it or would I need to reinstall it? I like not having to cd to it.
the android sdk is installed on the livecd and in the path, you'll have it every time you boot up, the part the script downloads will be gone on a second boot(unrevoked.com's recovery installer)
Great job!
Do u think that u could add some other HTC devices, in the future?
Awesome, thanks!
matteios said:
Great job!
Do u think that u could add some other HTC devices, in the future?
Click to expand...
Click to collapse
The devices supported are the devices supported by the unrevoked3 tool, I am not part of their team, just trying to help out some windows users who have driver problems.
Virtual image?
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
jmdearras said:
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
Click to expand...
Click to collapse
not sure if this is what you're looking for, but it'll help.
http://forum.xda-developers.com/showthread.php?t=701816
Problem with reflash.sh tool
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
jbwfg said:
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
Click to expand...
Click to collapse
it says in your signature you have 2.2 updated OTA, that must mean you have an evo, and those aren't supported by the unrevoked tool when running 2.2.
awesome shortcut for rooting phones, however I followed the steps and it is saying that the hero is not supported at this time? Did i do something wrong, I'm running 2.27.651.5
I've burned the the iso file to a cd but I'm not able to get the boot-up to work correctly..or to come up at all, when re-booting windows.
@lcw
When you boot, you will need to hit your bios and select your CD drive as a boot device. Then enjoy the ride - easy as falling off a bike.
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
pinkpanther2000 said:
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
Click to expand...
Click to collapse
You're not supposed to burn the ISO file onto a disc as a file. You're supposed to burn the contents of the ISO to a disc.
Sent from my HTC Liberty using XDA App
I attempted to boot from the CD, I get the person/keyboard screen then i get the Ubuntu screen, then my computer goes black, any solutions?
This is the BEST way to root your Aria. Big props to everyone that helped create it. You guys are the best.
We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Spiaatie said:
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
Click to expand...
Click to collapse
I know, I know mate .....I'll do it later...
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
I have done this on a Windows 7 64-bit PC. If you have a Linux, run *.sh instead of *.bat
Required:
1. A formatted micro SD card.
2. Fully charged phone.
3. A windows PC.
4. Android SDK.
5. Backup tools to backup existing data on your Android phone.
Create GoldCard:
A GoldCard turns your device into a generic device, thereby allowing modifications like installing another firmware possible. There are different methods to create a GoldCard but I found this the easiest:
1. A formatted SD card is necessary for this. A GoldCard is nothing but a formatted SD card with modified CID. Insert the SD card in the phone and format the card (Settings -> SD Card & Phone Storage -> Unmount SD Card -> Format SD Card).
2. Download “Klutsch’s GoldCard creation tool” from here. Run this tool as administrator. (this tool is windows only)
3. Enable USB Debugging mode in your phone (Settings -> Applications -> Development -> USB Debugging) and connect the phone to your windows PC.
4. Click on “Get CID” Tab and copy the CID that is generated. In case you get any error, select MMC0.
5. Open the link “http://psas.revskills.de/?q=goldcard“, enter your email id and the CID. You will then get the GoldCard image to the mentioned email id.
6. Download the GoldCard image to PC, from the GoldCard creation tool, click on ‘load GoldCard.img’, select the image that you just downloaded and click on “Patch MMC”.
7. Voila, you now have your GoldCard. Please do not use this card for any other purpose till the rooting process is over and it’s time to downgrade the OS.
Remove the GoldCard and use the primary card till the GoldCard is needed. (not necessary)
Downgrade the OS:
Download the following packages before starting this process:
• Android SDK (copy the SDK to C:\ add C:\androidSDK\Tools to your windows path)
• hack4legendv5.zip
• RUU 1.31 for Legend
Connect your phone to the PC ‘charge only’ mode. copy the contents of hack4legendv5.zip to androidSDK/tools directory and then run the script crackin.bat The phone will reboot couple of times and there will be lot of errors shown in the terminal. In the end look for the line showing permissions for the file /dev/mtd/mtd0. It should look like this:
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
Click to expand...
Click to collapse
This means that your phone is ready for OS downgrade.
Now, connect your phone to the PC in ‘charge-only’ mode and execute the file RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe and just follow the instructions and the phone will reboot to 1.31 version of firmware. And it’s time for Legend to get rooted. There will be a few errors but don’t get disheartened.
Root the Legend:
Time to use the GoldCard. Insert the GoldCard and connect the phone to the PC in ‘charge only’ mode.
1. Download the file r4-legend-root.zip from here. Unzip the file to a directory and cd to the directory.
2. Switch off your Legend, switch it back on in ‘fast boot’ mode (keep the back button pressed while switching the phone ON). When you see that the phone has booted into fast boot screen.
3. Connect the phone to the PC and run step1-windows.bat
4. After that is over, select RECOVERY option. Fastboot screen –> Boot loader -> recovery. You need to use phone’s volume rocker to move up/down the menu and power button to select the option. The phone screen should now show a phone with red caution sign.
5. From the terminal window, run step2-windows.bat. Once this step is completed, the phone will be back in recovery mode. From the options, select ‘wipe data’ and then select the option to update the ROM, select the file ‘rootedupdate.zip’ from SD card. The rooting process will now start and after few minutes, the phone will boot with rooted firmware.
Moderators and other experienced Members, I know my editing isn't perfect here 'cause I'm in a hurry but this is the guide I followed and I was rooted within 15 minutes. Feel free to edit (Mods) and suggest (Members). Umm... does this belong to the Development section?
Fantastic guide. Really great. I had half a mind to do one myself, no need now. This should help a lot of people. It might also be worth going through the other threads, and pulling out an FAQ with links to relevant posts. I'll help with that if you like.
Get this in the stickies!
ishan_rulz said:
Required:
3. A windows PC.
Click to expand...
Click to collapse
Hmm, Windows? Haven't seen that for several years (thankfully) except on our house, but I can still manage to root...
Sent from my HTC Legend using XDA App
@TheGrammarFreak
Okay, if you have additional points, just write it down... I'll add it next time I edit it.
@BlaY0
I have only tested this on a Windows PC, but I'm sure it'll work on Linux too. Added it as a note before the guide. Thanks.
where do i dl "rootedupdate.zip" or when u do step 1 and step 2 it will be on card or what?
MeBeSad said:
where do i dl "rootedupdate.zip" or when u do step 1 and step 2 it will be on card or what?
Click to expand...
Click to collapse
The scripts push it on there. That's why the download is so big...
Bump. Well... can someone have this moved to the development part.
Any way to root via OS X?
I'm getting this error when trying to get the CID in the gold card tool, what am I doing wrong?
------------------------
* daemon not running. starting it now *
* daemon started successfully *
------------------------
Could not locate CID in output
Im also getting the same error as tecchtalknews and have no idea what is causing it. ps im using a sand disk 2gb sd card that came with the phone, and yes usb debugging is on.
ahh never mind, i just had to sync it with htc sync before i used gold card tools
Does it work for 2.2 devices XD
Sent from my HTC Legend using XDA Premium App
im stuck on .
copy SDK and android SKD to C ... are you suggesting installing the complete SKD and then copying the folder to C instead of C/program files / Android SDK .?
and when double clicking crackin.bat . the terminal shows up for about 4 seconds then disappears and nothing happens on my phone ..
help first time rooter ..
Cheers
ok so my problem is that i click "crackin.bat" my phone reboots several times, but them the cmd closes before i can see if it's "crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0" or not.. however i think it should be because i've already gotten the other, wrong "cr---w--" (or something) and i think i might be doing it right this time, but after that when i go with the "RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe" it gives me error "(-5001 : 0x80070002)" and nothing happens .. please help cuz i've whiped all the data to my phone although i had a lot of stuff and i'm really looking forward to this :/ newb rooter, sry :?
am also having the same problem
help
Hi all,
i've recently bought a Nexus S which is a non-US/UK (GT-i9020) version having a SC-LCD screen (GT-i9023).
Which is not, sadly, the only difference...
MOD EDIT: This tutorial also applies to AT&T/Rogers/Telus variants of the Nexus S with SAMOLED screen (i9020A)
This tutorial is based on AllGamer's [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020 only).
Part 1 - Drivers
1 - Download Android SDK
2 - Unzip & launch "SDK Manager.exe"
3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."
4 - Select "Google USB Driver package" & click "Install Selected"
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20as described here [SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized
7 - Turn Off your SNS
8 - Make sure the SNS is connected to the PC via the USB cable
9 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
It reads LOCK STATE - LOCKED
Open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
10 - Do a right click and select Update Driver Software
11 - Select Brose my computer for driver software
12 - Point it to your Android SDK installation "extras\google\usb_driver" dir
13 - Make sure to CLICK "Let me pick from a list of device drivers on my computer"
14 - Then from the list 3 choices select Android Bootloader Interface
15 - If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Part 2 - Unlock
1 - Open a command prompt go to run & type "CMD" & hit enter
2 - Switch to the directory where you unzipped the Android SDK & go to "tools"
3 - Type "fastboot oem unlock" & hit enter
Then you will get thisfastboot oem unlock
...Selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
4 - Use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done... OKAY [435.433s]
finished. total time: 435.433sNow back on this screen you should read
LOCK STATE - UNLOCKED
Part 3 - Recovery
1 - Download the ClockworkMod recovery image (for i9020A models, use this i9023 recovery image too!) 3024v3-i9023.img from [MOD][RECOVERY]Clockwork 3.0.2.4 New wipe & confirm menus!! i9023 & i9020 versions
2 - Save it to the Android SDK "tools" dir
3 - Open a command prompt go to run & type "CMD" & hit enter
4 - Switch to the directory where you unzipped the Android SDK & go to "tools"
5 - Then type "fastboot flash recovery 3024v3-i9023.img" & hit enter
You should get something like this, if not your image is corrupted, download it again
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
2 - Download su-2.3.6.1-ef-signed.zip from [APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
3 - Save it to the Android SDK "platform-tools" dir
4 - Open a command prompt go to run & type "CMD" & hit enter
5 - Switch to the directory where you unzipped the Android SDK & go to "platform-tools"
6 - Type "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" & hit enter
7 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
8 - Select "Recovery
9 - Then it should boot into this screen, if not then repeat the steps to download the image
10 - Select "Install ZIP from sdcard" (power button to apply)
11 - Select "Choose ZIP from sdcard" (power button to apply)
12 - Select su-2.3.6.1-ef-signed.zip (power button to apply)
13 - Select "Yes - su-2.3.6.1-ef-signed.zip"
Should says
Install from sdcard complete15 - select go back
16 - select reboot
You're now free to install the ROM you want.
Have fun, take care !
Credits goes to AllGamer & afilopou
I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.
Brilliant. Thanks!
this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic
DoomFragger said:
I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Click to expand...
Click to collapse
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
DoomFragger said:
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.
Click to expand...
Click to collapse
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !
AllGamer said:
this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic
Click to expand...
Click to collapse
By the way AllGamer, i apologize for the non-agreed use of your tutorial, i was all in the thing at that time, just thinking about to end up with my cyanogen rom.
It works now, thanks to you. MIUI this evening
hi
i also have the 9023 and tried your guide. but im am stuck at #14 because it dont find the android bootloader interface entry, there are just three adb interface driver in this list. i also cleared the driver registry with usbdeview before.
adb driver is installed and i tried to unlock the bootloader but fastboot dont recognice the phone.
and i tried it on 2 different pcs, one with win xp and one with win7, same problem on both systems
ugrubni
When I unlock my bootloader, I've downloaded the "Google USB Driver package" and the "Galaxy Tab by Samsung Electronics".
I haven't edited any .inf file. Those were the instructions I followed from this article.
ok, finally i have bootloader interface installed with edited .inf installed on win7.
i tried to unlock with fastboot but it just does nothing. my nexus says
usb control init
usb control init end
standard_set_configuration
anyone an idea?
ugrubni
Before I root my Nexus S, i got some questions to ask.
Can I "unroot" my nexus s to stock if I do this?
What kind of roms are there available other than CM7 mod?
Hi all,
Followed advice above, had to reinstall SDK as did not have an adpfile. SDK all fine now, but am stuck on fastboot not recognising the phone - stays on waiting for device, did a search on xda but brought up other phones and nothing that could helped me...
updated: adb devices works fine, it sees the phone with adb, but just not with fastboot?
another update:
tried usbdeview to uninstall drivers
re-installed them again, no such luck.. annoyingly adb sees the nexus but fastboot does not..
would appreciate any more ideas?
i finally got it work
fastboot also dont recognized my phone
what i did is:
go to android-sdk/platform-tools folder and copy adbwinapi.dll and adbwinusbapi.dll to /tools folder where fastboot also is located and it worked.
cheerz, ugrubni
kursk said:
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !
Click to expand...
Click to collapse
That's right.The script which removes Cwm recovery after reboot does not exist in i9023(slcd)
Sent from my Desire HD using Tapatalk
hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers
Colombus said:
hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers
Click to expand...
Click to collapse
Did you try to install eclipse and start sdk from eclipse?
http://www.eclipse.org/downloads/ (download this one Eclipse IDE for Java Developers)
and then read this one
http://developer.android.com/sdk/eclipse-adt.html#installing
Had as well problems, but now i am using eclipse in order to start sdk
thx now it's working, all good, with it, and able to setting up
cheers
thanks ugrubni,
worked like a charm...
now have zeroxs on my nexus sorted!
Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?
Fmbl said:
Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?
Click to expand...
Click to collapse
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help
afilopou said:
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help
Click to expand...
Click to collapse
Thnx for your reply,
I followd everything you said, but fastboot is still not recognized, the above error message still aplies!
I do however dont get step 2 of part 2, maybe noobish but how do i get to that directory in CMD?
hmmm what to try next?