Related
I'm Fairly savvy with computes and technology this has me at hump
what i have
Usb coard
Sd Card
G1 Phone
Windows 7
Q.A) how do i know what model stock version i have on my G1? ( I AM stuck at the google activation screen, so i can't go in and check
B. I downloaded everything i need to, Drivers and on my device manager i see ADB device and it shows HTC Dream
C. My SD Card is not showing up or is grayed out almost as if the g1 is not even reconginzing it.
I really can't do anything as far as rooting without a sd card, so how do i make my phone reconginze it?
U have to activate it I think to be able to mount your sdcard to the computer or to get the info for your phone so start there. Then I beloved holding volume down and power will get u the info. When u plug your phone in u have to pull down from top of phone and click mount to get SD on computer
Sent from my Chromatic Magic using XDA App
damn, i live 4 hours from the nearest T-mobile store
U don't have a sim card with them I take it? Or a friend who does. Lol
Sent from my Chromatic Magic using XDA App
freshkid87 said:
damn, i live 4 hours from the nearest T-mobile store
Click to expand...
Click to collapse
Call them or go on the web and order an activation kit, they'll mail it to you.
alright man im help you out get passed that jus follow these instructions
But what you can do is check your hboot and what bored you have!
power down and hold camera buttong and press power
keep it held down till you see 3 tri colors, and make sure your hboot is not 1.33.005 or something along those lines
if its at 0.005.00 something then you can use the Dreaimg and go down and then use these instructions to get passed it then do the telnet root, and from there follow root instructions
if you have white screen with 3 skateboarding androids and hboot 1.33.2005 then you have (death SPL) but im sure your still on stock hboot and all but you can check what bored you have and grab the right Dreaimg for your phone
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro...devicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
Click to expand...
Click to collapse
Is there a better tutorial for making a gold card, I have read it over a dozen times and i still don't get it, I don't know what to do with the command prompt, so I am stuck at that and I want to know it all for sure before I go and brick my phone?
Does anyone know how to do this, or explain it clearer than the original tutorial?
Sure. use this tool and you can't really go wrong:
[PC Application] GoldCardTool, Windows Tool for helping make GoldCards @ MoDaCo
And I don't understand the whole command line part
Unzip the file you downloaded to a directory, then open a command prompt / terminal window at that directory.
Turn off your HTC Legend, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
In the terminal window, enter either 'step1-windows.bat', './step1-mac.sh' or './step1-linux.sh' as appropriate.
When this step has completed, REMOVE THE GOLDCARD and either format it and replace, or replace with a different (non goldcard) microSD.
Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
Help?
If you don't know what that means, maybe you shouldn't be doing it?
Reluctantly this is what it means in terms of the commands on your PC.
So unzip to your Desktop and call the folder Goldcard, open it and make sure the files are located directly in that folder and not another subfolder above that.
Open command line / Terminal and type this...
on a Windows machine:
cd %userprofile%\Desktop\Goldcard
on a Linux machine it's:
cd ~/Desktop/Goldcard
That gets you into the unzipped folder it talks about, where you enter step1-windows.bat and step2-windows.bat or the Linux version of the commands when required.
If you muck it up, you knew the risks when taking this on
Maybe this is a stupid question, but: how do we REMOVE THE GOLDCARD
It isn't mentionned anywhere tu turn off the device, and removing a micro sd involves to turn it off since it removes the battery too
I never did remove it personally.
Is it possible to use the goldcard in more than one phone?? so i created it with my legend, can I use it to update a legend of someone else??
Thanx in advance!!
nemphis said:
Is it possible to use the goldcard in more than one phone?? so i created it with my legend, can I use it to update a legend of someone else??
Thanx in advance!!
Click to expand...
Click to collapse
YES! I've just rooted my friend's legend with my goldcard.
pe3ksve3k2 said:
YES! I've just rooted my friend's legend with my goldcard.
Click to expand...
Click to collapse
I found the reason why I think on this forum,
http://forum.xda-developers.com/showthread.php?t=753374
There are two kinds of CID. There is the CID on your phone, which determines which brand of phone you have - this is irrelevant here. Then there is the CID on your sdcard, this is the card's serial number, and this is what you use to create a goldcard.
So therefor you can use your goldcard with an other telephone, but you can not copy the image of your goldcard to an other sd card.
Common Telnetd problem - unable to root
What's up xda!! This is my first post ever!
..please be kind.
I am experiencing a n00b issue w/ rooting my G1. So far I have been able to get up to where I am on RC29 and <enter>reboot<enter> successfully reboots my phone! This is great up until I'm told to hit the enter key twice, type "telnetd" and press enter. after the phone starts up.
FOOD FOR THOUGHT:
I believe I have ADB drivers installed properly installed
I am able to run Droid Explorer and it connects and recognizes my unit
I also have the following files on my SD CARD prepared
recovery-RA-dream-v1.5.2
update.zip
I have also read that ONE solution is to look for someone with an current T-Mobile Monthly Account and ask to borrow their sim card so I can install the Telnetd and enable WiFi past the Google Login(I have asked a fellow and I was told an aggressive NO, apparently people are afriad of anything related to hacking and their SIM CARDS)
I have the G1 Original SPL currently
Also when booting into recovery Alt+L gives me the Log that shows ""
I hope to have made an appropriate first post granted I've been searching for answers and help and am still experiencing issues. I look forward to participating in this forum in the future looks like you guys have been having fun for a while!
Any suggestions are definitely welcome.
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
RE: Maybe try to update your phone to Android 1.6
raven_raven said:
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
Click to expand...
Click to collapse
Hey raven, thanks for the reply!
By doing this update are you suggesting that I use the G1 Original SPL to flash the Offical Dream RC29 ROM (OTA_ROM RC) listed on that page, IF so what should follow that? Would I be allowed to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC) and the Official RC33 Update - from RC30 to RC33 (OTA_ROM RC) with the same update.zip that came from the G1 Original SPL also?!
I'm lost with your suggestion, b/c if it requires me to enable WiFi to get the OTA update I would still be unable get pass the Google login. Would I not be stuck back to where I am now? As of right now, I am at the Android Welcome Screen with the G1 Original SPL and RC29 that were not listed on that page AND so far unable to get root b/c of unavailability of TelnetD and WiFi. I will proudly follow those instructions?? Sounds like following the flash of Offical Dream RC29 ROM (OTA_ROM RC), that I would need to somehow use a method to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC)...I think?!
Excitement!!!!!
EXCITEMENT!!!!!
I used:::::
1- Plug your G1 & Install Drivers.
2- Without Sim Card in Your G1, <enter>setprop persist.service.adb.enable 1<enter> Even though u dont see what u typing, but u are actually executing a Command on your G1 to Enable USB Debugging in Settings.
3- Once u Execute that Command USB Drivers will be Installed again, but this time will be recognised as ADB Interface.
4- Click Start>Run>cmd> to Command Prompt
5- Type c:\adb devices (If your Device is Connected u will see it)
6- Restart your G1 but now With Sim, to see the Activation Screen then Plug USB Cable & Type c:\adb devices (to make sure u are connected)
7- Type c:\adb shell (U will see a $ sign) Just Copy & Paste this into Command Prompt (am start -a android.intent.action.MAIN -n com.android.settings/.Settings) The Settings Screen will Appear, now Switch on Wi-Fi & Connect to the Internet.
8- Now u can either Login with your Existing or Create New Account with Google.
Click to expand...
Click to collapse
here is where I was lost, I'm sure many are running into the same issue. The adb.exe that is located on my PC is what the command prompt should be finding, however there are other folder possibilities in where the application is ran to even use the adb functions. For instance, my adb.exe was installed in "c:\android-sdk-windows\tools" instead of strictly on the "c:\" I was not aware that I would be controlling the phone unit through my command prompt as well!! silly me, something so easy can become one of the biggest problems. ONE MONTH LATER!!!! THANKS XDA!
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
Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?