Database Develop

Root G1 with Latest update

Hey guys I have a stock G1 that was given to me and I can't access the wifi settings thus I cannot sign in. I believe I have the latest update. Anyone know a way around this?

http://forum.xda-developers.com/showthread.php?t=452316

B-man007 said:
http://forum.xda-developers.com/showthread.php?t=452316
Click to expand...
Click to collapse
Does not work with the very latest AOSP update : (

cars1106 said:
Does not work with the very latest AOSP update : (
Click to expand...
Click to collapse
You need to root your phone.....Read the stickys at the top of this section to learn how

It has been rooted before. then I unrooted it gave it to someone to use, it got updated and I don't have a sim with data and now I can't do anything with it. I guess I will have to downgrade via SD stick somehow through the recovery menu and try and run the exploit again.

if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh

B-man007 said:
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
Click to expand...
Click to collapse
Yup, I had the same issue, downgrade to RC29, then follow this:
**Originally Posted by dizzydevil111**
please make sure you have rc29 or lower by typer (enter)reboot(enter)
if the phone reboots then you have rc 29 or lower.
if not, follow this guide to downgrade to rc29
2. Mount your SD card in Windows and reformat it as FAT32. The HTC
bootloader won't be able to see the RC29 (or RC7) image otherwise. Make
sure you back up all your files first!
3. Download the appropriate image (RC29 for USA or RC7 for UK) from
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip or
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC7.zip . This is a DOWNGRADE
to the Android version that contains a root shell bug (this exploit just
seems too easy). I got these files from the forum thread
http://forum.xda-developers.com/showthread.php?t=442480 .
4. Extract the DREAIMG.nbh file from the downloaded zip archive and copy it
to your SD card (again, for me, this had to be formatted as FAT32, not just
regular FAT which is the default). Don't put it in a folder, just stick it
directly on there.
5. Disconnect the SD card the right way (eject, unmount, or otherwise tell
your OS you are unplugging it) to make sure the data gets written. If you
used an SD card reader, put the SD card back in your phone.
6. Make sure your phone has a full battery, then turn it off. Turn it back
on by holding down the CAMERA and POWER buttons. This should get you into
the HTC bootloader (the funky red, green, and blue screen).
7. If everything was done correctly, the bootloader will detect the image.
You'll be taken to a different screen that asks you to press the POWER
button to install the image. Do this, but beware, you will lose all your
saved data on your phone (with the exception of things that are synced with
Google's servers, like contacts, calendar, Gmail, etc.).
8. Wait for the update to complete. The progress bar will fill up, then
all the steps will say OK beside them, and finally, it will ask you to press
the "action key" (I think this means click the trackball). DO NOT do
anything until you see this message. The progress bar needs to DISAPPEAR,
not just fill up.
9. You now have the stock RC29 installed. Take out the battery, put it
back in, and turn on your phone. It should ask you to activate your Google
account again -
once you have this done type on the phone again (enter)setprop persist.service.adb.enable 1(enter)
your pc should now pick this up as an android adb device
point it to the correct drivers found in the file called androidusbwindows
once that installs, extract the adb file anywhere on your pc. (best place is root directory)
open up a dos command prompt and type (cd ..<enter>)
then type (cd ..<enter>)
then type adbshell
should look like this thereafter
$
referring to the dollar sign
then copy the following line into your dos command prompt and press enter
(am start -a android.intent.action.MAIN -n com.android.settings/.Settings)
please make sure that you copy the contents of adbwin.zip in your ROOT FOLDER or else you will be going through hell
voila you should be able to access wifi
pm me if it worked for you

[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)

Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me, you can do so below.
GBP
EUR
USD

So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Buzz. Now, you need to recall what version of Android you were on before you rooted. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for good measure.

I'm sure this will help many people. Should be sticky'd

HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo

Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2

Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin

PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now

42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason

The guide really great....but the shipped rom website don't have RUU for Buzz

coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.

This thread still not stickied?

Piece of art already. Should be stickied for sure.

I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!

[Q] About to root phone with 2.32.651.2

Hello,
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version, or should I downgrade. If I need to downgrade, can anyone tell me which software version I need to downgrade to in order to root, and a thread linking to a guide to downgrade?

forum.xda-developers.com/showthread.php?t=847993
this should do it

I think you can root this version, search around... if it possible you will find a post regarding it.
If you plan to downgrade, I would recommend .5 and then root using regaw's method - you should find all the details on the CDMA hero wiki page.

xlectik67 said:
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version [?]
Click to expand...
Click to collapse
HERE is the link to the post i wrote (in the thread which guided me) to get root in this stock-rom... so, yes, it can be done...
as far as dowgrading, im not sure i would recommend it - but as mentioned earlier, the wiki has a guide which i believe is based on a ...31...5 version you could use...
gl, h.

Root Sprint 2.32.651.2 OTA Permanently (in 10 steps)
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)

ccrosno said:
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
Click to expand...
Click to collapse
Sorry I forgot to mention that there were a couple times that the phone locked up durring the reboot to recovery stage. I do not know why. I beleive that it was due to forgetting to install the recover before rebooting. If this happens, pull the battery, replace the battery and start over.
Thanks

tailsthecat3 said:
forum.xda-developers.com/showthread.php?t=847993
this should do it
Click to expand...
Click to collapse
my WiFi worked fine after rooting the ota update by following the linked method. ^

Go ahead and root using the method mentioned above, if anything goes wrong... you can always RUU and reroot.
BTW, I have downgraded using .5 RUU and rooted my phone, so based on my experience I can say, it works well. I had initially rooted my .7 and was running CM 6.0 stable, had some issues, got my recovery screwed up, so had to go all the way... ;-).

tailsthecat3 said:
my WiFi worked fine after rooting the ota update by following the linked method. ^
Click to expand...
Click to collapse
Ya I tried that one. Couldn't get it to take. Mine is sort of the non-syntax method.

[GUIDE] Complete and Thorough Guide to Rooting the Nexus S [+ No wipe] [GRH78C]

May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.

Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks

Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.

STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps

ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks

Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.

distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop

This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.

I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.

Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.

Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.

AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part

Sent from my Nexus S using XDA App

Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!

No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App

Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.

hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks

Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..

I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse

Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App

[Q] Experiencing various difficulties in rooting u9000, pointers, anyone?

Aloha from the smoggy skies of Beijing.
I have recently purchased a Huawei u9000 from jingdong.com (China's equivalent of eBay), and have encountered a plethora of disappointments in trying to root the phone.
First, the phone (from the About section):
Model: HUAWEI-U9000
Android Version: 2.2.2
Baseband Version: PR232
Kernel Version: Apps_2.6.32.9-perf
Build Number: U9000 V100R001C322B259SP00
Running these methods while using a Windows 7 Ultimate 64 laptop.
Here is what I have attempted:
1) SuperOneClick 2.3.3
Attempted with Auto (as rageagainstthecage was not listed as an option), no success.
2) SuperOneClick 1.7
This was quite annoying. I had read that rageagainstthecage was the silver bullet for most people's problems, but after reading the revision log I noted that it was no longer included in versions 1.8 onward. I have also read that version 1.7 is the recommended version to use with my phone, so I obtained a copy.
Here is where it gets annoying: everytime I unpacked the contents of the zip file into a directory, rageagainstthecage would simply disappear after a few seconds.
I am aware that rageagainstthecage is some sort of trojan, and so I killed both MSE and Comodo processes (those that I were able to, some of the Comodo ones were stubborn).
Every freaking time I extracted rageagainstthecage, it would vanish from the directory 5-10 seconds after extraction. My google-fu could not point me in the right direction, nor could I even find anyone else experiencing the same problem.
SuperOneClick would invariably freeze after the ninja file disappeared.
3) Snakebitezz method
(found at http://forum.xda-developers.com/showthread.php?t=1274972)
Steps followed:
a. Power down phone.
b. Reboot phone holding down power and Vol+ keys simultaneously
c. Plug in phone once download mode has been entered.
d. Access the drive once it is available in Windows
e. Make a copy of all files in the /image directory somewhere on my laptop.
f. Copy over files into /image and overwrite as prompted (recovery.img and META-INF directory) using the files linked in the post.
g. Copy su-2.3.6.3-efgh-signed.zip to the root directory of the drive (also downloaded from the post).
h. Eject, disconnect, remove battery.
i. Replace battery, while holding Vol+ & Vol-, power up the phone until it vibrates, at which point release the power button, but continue to hold in both Vol buttons.
j. Hit the search key, select install from zip, select install from zip again, and...
This is where I hit a wall on this method. The .zip file that I left in the root directory is not listed. I have tried several times with minor variations, and each time the .zip file is not listed, thus not an option, thus I can't progress any further.
Regarding this method, to the best of my knowledge I do *not* have BusyBox installed, though in the post it mentions that it is necessary, though it was not available for download in the post. Furthermore, it seems that I have read that to use BusyBox, the phone needs to be rooted. Regardless, I'm not sure where I can obtain BusyBox, as I am in China, and currently cannot access Google Play/Marketplace (this is one of the reasons I am hoping to root my phone).
4) GingerBreak APK
Using GingerBreak-v1.20.apk, I place the APK file on to my phone, install it, open it, and select the 'Root' option. I have left the phone running this option for 45 minutes with no change in screen, status, and without any reboots. I have read that others have had success while leaving GingerBreak running longer, but my luck has been such that I'm not sure if it would just be a waste of time for me while there are still other options that I have not attempted.
*Note: USB Debugging was on for each of the above methods.
So, here I am, seeking wisdom. Can anyone see from what I have listed any missteps that I have taken?
What other options (that have some nice guides available) are there?
I've read that people running Linux have had better luck, should I get my hands on an Ubuntu distro, and research the routes available through that OS? If possible, I'd like to do this without having to set up a dual boot machine~ I like Linux, but I'm still a Linux n00b and all the games I play are on Windows anyhow.
Your efforts are sincerely appreciated.
TLDR: With a Huawei U9000 have used two versions of SuperOneClick, Snakebitezz method, and GingerBreak APK, all without success. Seeking guidance.

hi
if all u want is to root and add CWM and try new roms then
id suggest u start reading here this link : http://forum.xda-developers.com/showthread.php?t=1288293
details on all of the above is in that read do the needfull and enjoy ur new phone:good::laugh:

Thanks, but I have tried the methods for rooting listing on your post. Very nice compilation, by the way! It looks like it will be super useful once I finally get the phone rooted.
I'd like to add two more methods that I have tried that have been unsuccessful,
1) Unlock Root (program)
2) Z4Root (APK)
When using Snakebitezz method, does it matter how I put su-2.3.6.3-efgh-signed.zip into the root directory? Do I need to be in 'download mode' to place it there? Because when I try to locate it following the guideline, it doesn't show up in the list. All I see are the names of the directories accessible from the root directory. Would it matter if I tried putting the .zip in the root just by turning on USB transfer and dropping it in there (while it's *not* in 'download mode')?

TangBaBa808 said:
Thanks, but I have tried the methods for rooting listing on your post. Very nice compilation, by the way! It looks like it will be super useful once I finally get the phone rooted.
I'd like to add two more methods that I have tried that have been unsuccessful,
1) Unlock Root (program)
2) Z4Root (APK)
When using Snakebitezz method, does it matter how I put su-2.3.6.3-efgh-signed.zip into the root directory? Do I need to be in 'download mode' to place it there? Because when I try to locate it following the guideline, it doesn't show up in the list. All I see are the names of the directories accessible from the root directory. Would it matter if I tried putting the .zip in the root just by turning on USB transfer and dropping it in there (while it's *not* in 'download mode')?
Click to expand...
Click to collapse
hye mate if you confiuse try this
-first insttal this in you computer
http://www.mediafire.com/?cugomknzg3svfhf
- if you dont know how to use this tool,see this guide
http://forum.xda-developers.com/showthread.php?t=1451102
[see the video you tube]
-ater that i suggest you upgread you phone to gingerbread 2.3.xx
this the link the rom by tj-style
http://forum.xda-developers.com/showthread.php?t=1446449
download the rom
and flash this rom use SUT TOOL
GUIDE HOW TO FLASH
SEE HERE
http://forum.xda-developers.com/showthread.php?t=1446449
------------------------------------------------------------------

TangBaBa808 said:
Thanks, but I have tried the methods for rooting listing on your post. Very nice compilation, by the way! It looks like it will be super useful once I finally get the phone rooted.
I'd like to add two more methods that I have tried that have been unsuccessful,
1) Unlock Root (program)
2) Z4Root (APK)
When using Snakebitezz method, does it matter how I put su-2.3.6.3-efgh-signed.zip into the root directory? Do I need to be in 'download mode' to place it there? Because when I try to locate it following the guideline, it doesn't show up in the list. All I see are the names of the directories accessible from the root directory. Would it matter if I tried putting the .zip in the root just by turning on USB transfer and dropping it in there (while it's *not* in 'download mode')?
Click to expand...
Click to collapse
Got root?

elol said:
hye mate if you confiuse try this
-first insttal this in you computer
http://www.mediafire.com/?cugomknzg3svfhf
- if you dont know how to use this tool,see this guide
http://forum.xda-developers.com/showthread.php?t=1451102
[see the video you tube]
-ater that i suggest you upgread you phone to gingerbread 2.3.xx
this the link the rom by tj-style
http://forum.xda-developers.com/showthread.php?t=1446449
download the rom
and flash this rom use SUT TOOL
GUIDE HOW TO FLASH
SEE HERE
http://forum.xda-developers.com/showthread.php?t=1446449
------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks! I will try this right now!
EDIT: BTW, does the phone need to be rooted in order to use SUT? If so, rooting is the problem that I can't get around...

whyzee said:
Got root?
Click to expand...
Click to collapse
Hopefully after I try what elol suggested

TangBaBa808 said:
Hopefully after I try what elol suggested
Click to expand...
Click to collapse
gud,like to see help you

elol said:
gud,like to see help you
Click to expand...
Click to collapse
Just curious, from the page inforall webs com/spicemi410.htm, it says that I should download clockworkmod recovery for Spice Mi410 from MediaFire, but the password listed on the page isn't working... Anyone have a direct link to this file or a working password?

TangBaBa808 said:
Just curious, from the page inforall webs com/spicemi410.htm, it says that I should download clockworkmod recovery for Spice Mi410 from MediaFire, but the password listed on the page isn't working... Anyone have a direct link to this file or a working password?
Click to expand...
Click to collapse
This recovery is for .32 Kernel baseband only
Replace this recovery with your current one.
How to Replace recovery?
Download the attached File on your PC
Switch off your Phone
Press Vol UP and Power Button to go in Download mode
Connect your phone to the PC
Browse to image folder and replace recovery.img, Please backup your old recovery somewhere on PC.

TangBaBa808 said:
Just curious, from the page inforall webs com/spicemi410.htm, it says that I should download clockworkmod recovery for Spice Mi410 from MediaFire, but the password listed on the page isn't working... Anyone have a direct link to this file or a working password?
Click to expand...
Click to collapse
Recovery and stuff is on the roll up thread. God! Only if people started reading the forum would be a better place
Sent from my FIH-FB0 using xda app-developers app

whyzee said:
Recovery and stuff is on the roll up thread. God! Only if people started reading the forum would be a better place
Click to expand...
Click to collapse
I think the roll-up thread should be in General Category and not in Development because whenever people come to start a new thread in General they can see the stickied Roll Up thread, Just my $0.02

Success in rooting!
Perhaps I wasn't using the latest version of CWM? Or maybe it was because I loaded the file onto my SD card by taking it out of the phone and using the USB connector that the SD card came with? I don't know.
I used CWM 5.0.2.7 (touch enabled), and then used the same su-2.3.6.3-efgh-signed.zip file listed in http://forum.xda-developers.com/showthread.php?t=1274972 and I finally got root! Heh heh, now, wait til I'm sober, and I'll start panning the threads for info on how to update the version of Android I'm running... Any good suggestions from people on a u9000?