Related
This is a guide from a noob who spent a few hours today on my wifes phone trying to get it into Download mode after using Master Clear.....Worked fine before Master Clear but I wanted all the root apps IE Titanium) gone which the stock ROM update did not do. Being a total noob at Android and the Captivate being my first foray I though I would try to provide noob instructions to cover most bases. Most of the instructions here are scattered and not easy to find or are incomplete and make assumptions. This is specifically for those who cannot get into recovery or download mode.
Recovery/ Download modes are SEPARATE modes for for different uses.
I used recovery mode to "root' the phone AFTER putting the "update" file into the root directory using USB mass storage mode.
I use Download mode to install ROMS such as Stock and the 2.2 update.
My biggest issue was having a device that Would not GO INTO RECOVERY/DOWNLOAD MODE using any combination of button presses which it did before I Master cleared the phone. . Very frustrating. So I decided to bite the bullet and use the SDK mode. This first part will guide one on how to use the Android SDK and Command Prompt.
The assumption is all the drivers have been loaded for the Samsung Captivate.
First you need to have JAVA installed in your PC ( I did not)
The next you need to download the SDK package readily available
http://developer.android.com/sdk/index.html
This is what I did:
1. Created a folder called SDK on my C drive root directory.
2. Copied the android-sdk_r07-windows.zip SDK file to that directory
3. Extracted the ZIP into a newly created folder in that Directory
4. Deleted the Downloaded Zip package.
5. Moved all files from the new folder created by the extraction to the root SDK directory and deleted the now empty folder they came from. (This makes the path to the tools folder simple (as you will need to type that path out exactly in command Prompt)
My Path looked like this C:\SDK\Tools . Doesn't matter how you get there but tools folder must be in the path and the path must be exact
Next I started my Captivate normally and put my Captivate in USB debugging mode. Plugged in the USB.
I then opened the ODIN file I wanted to use whether original stock ROM or the new Froyo ROM
1. Opened command prompt on PC
2. Type CD\ to start at C root directory
3. from there I typed in CD \sdk\tools\
4. The next step involves the typing the command to open the screen you want the Phone to use...Recovery or download
4. Type in adb reboot recovery for the recovery screen (This gets you into the "three button screen" with no USB attached many cannot get into.
5. OR type in adb Reboot download to get the yellow download screen...
From there ODIN should indicate a com port..You hit start and the new ROM will be installed. There should be NO hangups on the indicated steps within ODIN. it happens pretty quickly.....YOu will see a filler bar at the top of ODIN and a blue line filler across the phone as the ROM is loaded.
I used Froyo..and discovered with Froyo I did not need to use the SDK method to get into recovery mode.....Froyo fixed that.
I have two Odin files. One for Jf6 Stock and the new 2.2.
I updated the JH7 FW using mini Kies in debugging mode. That was the only way I could load that FW which did not work OTA.
Bottomline is this is not a Hardware phone replacement issue if one cannot get into download mode. It is all about the FW in the phone. IF you can use the SDK you may likely not have to use it again.
OK ALL YOU EXPERTS Please correct or certify the steps.
Just trying to hep those who cannot read a 110 page thread that goes in many different directions.
Very nice instructions...
This type of detail is refreshing to see. Nice to see that assumptions aren't made. This type of detail can eliminate a lot of questions/posts.
I would just add - make sure you grab the right SDK - 1.5 ADB will not work with 2.1.
Thank You !
Followed your instructions but..
I tried to use sdk tools to reboot into download mode this is the specific comand I use:
adb reboot download
If I type this in the phone acts like i typed
adb reboot
The fact is that I searched help in the comand line and there is no reboot download only reboot recovery or reboot bootloader.
I cant get my kyocera torque into download mode and that is the problem I have also tried to boot with keys pressed nothing works. I want to get the phone to download mode so that I can install cwm recovery through odin
Maybe there is a esier way ?
U can make or buy a download mode jig. Quick search in the Captivate forums will show ya a thread of how to make one. Plus a lot of videos r on youtube as well.
Sent from my Nexus 5 using Tapatalk
AlphaRev X Beta is now available for Wildfire/Buzz users stuck on 2.2.1 with HBOOT 1.01.0001 and above. This will make your Wildfire/Buzz s-off and give you the ability to get root. Follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1130881
If you have downgraded to a 2.1 rom and want to get back to official 2.2 rom to use Alpharev X Beta or have HBOOT 1.01.0002 and want official 2.2 with HBOOT 1.01.0001 to use Alpharev X Beta follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1132028
Thanks to all who made this method possible and to those who developed the tools used etc.... This is not my work just trying to simplify it.
I accept no responsability if you brake your phone
Will NOT downgrade the HBOOT but useful if you need to go back to stock 2.1 rom.
Right Here we go:-
Downloads you will need:
Android SDK:- http://developer.android.com/sdk/index.html Google search for a guide to setting this up and read the guide carefully so you know how to use adb.
HTC Sync:- http://www.htc.com/uk/SupportDownload.aspx?p_id=316&cat=3&dl_id=1073 Basically for the drivers to use adb as these are included with htc sync you no longer have to install drivers from sdk to use adb.
HEX Editor:- http://mh-nexus.de/en/downloads.php?product=HxD I suggest you find a guide on making a GOLD CARD as you will need a GOLD CARD any way, this will get you ready and use to using the hex editor later in this guide.
Super One Click:- http://forum.xda-developers.com/showpost.php?p=10452428&postcount=43 Download un zip it and save to pc.
Flash_Image:- http://www.android-hilfe.de/attachm...-how-rebrand-o2-desire-fertig-flash_image.zip un zip and save somewhere on your pc you will remember.
A 2.1 rom RUU to downgrade to:- http://shipped-roms.com/index.php?category=android&model=Buzz Choose the one that best suits you WWE=Unbranded or chose one for your provider/carrier, download and save to ur pc.
Now your have set up the Android SDK you know what ADB is and how to use it (hopefully), you have created a GOLD CARD, you have installed HTC Sync, you have downloaded the 2.1 RUU.exe you want to downgrade to, you have downloaded Super One Click 1.5.5 and un zipped it and save it to ur pc and you have dowloaded the Flash_Image and un zipped it and place on ur pc.
Ready Here We Go:
Step1 - Open Super One Click and press SHELL ROOT it will run its commands and will give you temp root. You will see rooted at the bottom when its done. Try again if it says FAILED it may take a couple of attempts. ( Make sure you have adb working ) and (make sure usb debugging is ticked on your phone and unknown sources tho im not sure if unknown sources needs to be ticked, mine was and that when you plug your phone it the pc via the usb cable you select charge only on the phone)
step2 - open a cmd (command Prompt) on your pc and type adb shell (if you installed the android sdk and read about how to get to adb shell you will have no problem) (for me i type cd C:/android-sdk-windows/platform-tools and hit enter, the type adb shell. (if you see a $ try shell root in super one click again, if you see # your good to go).
step3 - copy the mtd0 file to sdcard.
(in cmd type) cat /dev/mtd/mtd0 > /sdcard/misc.img
step4 - move the misc.img to your pc and use the hex editor to edit it. (run HxD as administrator click extras, open disk image and select your misc.img you just got from your sd card).
step5 - go to 11th row down, you will find current version number at
the end of that row.
step6 - Change it to 1.25.405.1 if you want to use "Ruu_Buzz_HTC_WWE_1.25.405.1", the press file and save. (change the numbers to match the 2.1 RUU you are going to downgrade to (common sense) ok)
step7 - copy the flash_image (the one you downloaded at the start of this guide) and misc.img back to your sdcard.
step8 - (in cmd type) cat /sdcard/flash_image > /data/flash_image
step9 - (in cmd input) chmod 755 /data/flash_image
step10 - (in cmd input) /data/flash_image misc /sdcard/misc.img
Now you can flash offical android 2.1 RUU rom you downloaded earlier (don't forget to make gold card).
Now your on Android 2.1 but your HBOOT is still version 1.01.0001, so Unrevoked still wont work. So still no full root as yet.
Once again not my work just trying to keep everything simple and in one place, ALL THANKS TO ORIGINAL DEVS AND GUIDE CREATERS. BUY THEM A BEER.
Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory
Birthe88 said:
Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory
Click to expand...
Click to collapse
Yip lol. Ive been asked so many times on how to do this because i posted on a thread that i done it, so i thought i would try and give a step by step brake down of how to do it lol. i wrote it all out the other night went to submit the thread and it wiped cos i got signed out while typing it up (gutted lol) so here it is, hope its clear enough for every one.
Tried it but keeps saying waiting for device and then loops
elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
Just updated link to super one click download that i used should work now also have usb debugging and unknown sources tick on your phone as i did whilst using super one click.
elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
my phone got this loop, too
i even tried in fastbat and recoevry mode...
edit:
just try another usb port, not at an hub
Can someone confirm this and create a video tutorail of this?
thanks in advance.
MarkPower said:
Can someone confirm this and create a video tutorail of this?
thanks in advance.
Click to expand...
Click to collapse
Confirmed - make sure to have proper drivers, adb working, put phone in charge only usb mode + usb debugging
This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root
INET.exe said:
This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root
Click to expand...
Click to collapse
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...
Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App
brilldoctor said:
Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
It gives you temp root so you can downgrade to a lower rom but I couldnt get it to work with titanium or get su permission in terminal app on the phone! have not really tested past the downgrading stage yet will update if I get any more info.
dj_destruction said:
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...
Click to expand...
Click to collapse
2.2 is more stable and use less of ram and the radio reception is better for most providers.
superoneklick cant give the access for root apps its shell root not file system root
I read somwhere a technique that involved fooling a RUU installer to apply an older rom by replacing some file(s) with older one(s).
I too am stuck with 2.2 and hope to see an easy way to set my phone free
Sent from my weak Wildfire, can't wait to trade in for HD2.
try this>>>>>
open the ruu setup and do not click on and let it open, look in the temp directory of your windows user, according to the extracted files of the setups and replace try something there maybe it will work, I have not tried it yet because most processed rom . zip files stop at the signature and the md5 check.
As if I wan to downgrade my wildfire in order to root . does it downgrade work ? Because u said tat "Will not downgrade the HBOOT" . Newbie here.. dont flame me~ thx..
wait for an other way to root. Downgrading the rom to 2.1 dont give a possible way to root because it will still have the new hboot. The unrevoked team say weeks a go that they are working on it but i guess still without succes. Just wait a read the forums.
I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer
dj_destruction said:
I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer
Click to expand...
Click to collapse
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.
beastaki23 said:
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.
Click to expand...
Click to collapse
Nice try. And if you test with the img.zip from the older official RRU?
Sent from my HTC Wildfire using XDA App
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
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?
So iam running bo 2.0.1 with cwm 5.5.0.4. Tried to update to cwm 6 touch by replacing cwm image in pretty much all the aio's.. it'll either say it pushed and still reboot into old cwm or I'll get permission denied on /data/local/temp/sh and mmcblk14 even after giving them all read write and execute permission. Can someone help me get this on my revo? Maybe a guide to do it with adb? It would be much appreciated..... sorry if this is posted in wrong section... I wasn't sure where it would be seen by the dev 's who can help
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
slimzim said:
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
Click to expand...
Click to collapse
The same exact way I've done it. Numerous times with no success. It said it pushed but reboot back into 5.5.0.4
Anyone else have this problem? How can I achieve this with adb or file explorer... the method posted just isn't pushing the image...
To do it from within the phone... (Insert the usual disclaimers here about messing your phone up here. It's all you from here on out)
You can open up the .bat batch file of one of the rooting tools that have CWM install scripting.
Copy the commands they perform in preparation for the procedure. Remove adb shell and push from the commands as you will be doing this from inside the phone, not via adb. I think you might have to remove some open/close quotation marks too, unnecessary from the terminal prompt.
Rename the new CWM file to match the command prompt change the command to match the new CWM filename.
Move that file to the expected location (/local/tmp if I recall correctly).
Use app Terminal Emulator to create a terminal windows and type su and Press enter. That will get superuser access.
Then, issue the commands you took note of from the batch file.
Reboot to Recovery to test if successful.
I used this basic process to get CWM on after rooting stock ZV9 a few weeks ago. Combing through a couple different batch scripts, I wanted to make sure I wasn't going to bork my phone. The adb remount command doesn't seem to work after rooting for some reason. That seems to be the cause of adb failure to update CWM.
If you get into trouble, I can't help you much there as I'm not that advanced. Good luck.
Anyone else with tips please chime in and help the chap :beer:
Sent from my VS910 4G using Tapatalk 2
Ill try it out. Thanks for the advice
Didnt work.. iam hoping that resetting back to stock and using that image from the start will work
Weird. I was expecting to hear good news since that's how I got CWM onto my phone. Good job trying!
Sent from my Transformer Prime TF201 using Tapatalk 2