[Q] Rooting Rogers HTC Dream - G1 General

I am moving from an iphone to a HTC Dream and I am pretty stumped on how to root my phone. It is post 911 patch. But I have a couple of questions that are probably noobish but just need clarification.
Using this guide:
Cyanogen Wiki Post 911 HTC Dream patch guide
Do I need ADK or ADB as I seem to be mixing them up and not sure.
Should the fastboot we download from there replace another fastboot already in the SDK tools folder?
I seem to be getting Batch Command not recognized when I do command prompt with it.
Any help will be greatly appreciated by this Rooting noob.

You will first need to install the USB Drivers:
http://developer.android.com/sdk/win-usb.html
Then make a folder and download ADB and Fastboot and extract them into that folder:
http://www.filedropper.com/adb1026
http://developer.htc.com/adp.html#s2 (just download fastboot.exe)
You should now be good to go and can just follow the the rest of that guide.
Remember that your phone is not designed to run 2.1 or 2.2 and while it will work it may be slow. See my post here: http://forum.xda-developers.com/showpost.php?p=8731550&postcount=3

Related

my easy root based off the easy root script

ive created a walkthru for rooting the htc thunderbolt, based off the easy root script.
the adb folder is already setup, sdk is there, and the downgrade and upgrade. where should i host the file that this forum will allow me to post?
BTW if your running 64bit windows 7 i have included the ADB drivers, but not 32bit. i think they are installed with 32bit windows, but im not certain.
let me know if anyone is interested.
DOWNLOAD > Link 1
if anyone has any trouble please just post here, ill be on all day.
these steps will only work with the DL i have linked. if anyone wants to PM me a mirror it'd be greatly appreciated
steps:
THIS ONLY WORKS WITH A Thunderbolt running 605.6 or 605.9 Firmware
1. copy the root folder to the C: drive.
2. first, install the android SDK in the ZIP file. reboot if needed. plug in your phone, ADB most likely will not install. once or if it fails, search for the driver manually in the ADB+driverX64 folder though device manager.
3. now run the oneclickroot.bat file. dont worry about the prerequisites, they are all setup in the root folder i had you copy to the C drive.
4. after you reboot, plug your phone in. make sure adb drivers are istalled and working.
5. run the oneclickroot.bat file again, and follow all the directions. if you follow the steps slowly and correctly, all will work fine.
************************************************** *******************
REMEMBER! when it tells you to rename some lare file to PG05IMG, that is the PG05IMG_downgrade file. just copy to the root of your SD card, and rename it to PG05IMG after it finishes copying.
also if things freeze up make sure u have USB debugging enabled. DO NOT UNPLUG THE PHONE. just disable and re-enable if it hangs up when it says "this process may take w while".
************************************************** *******************
Ive also added the kernal to OC the phone to 1.5Ghz, you can do that with rom manager, or though clockwork recovery if your familiar with it. if u do it just copy the zip to the root of your SD card on the phone
Might want to throw a disclaimer in there just to cover your ass. Just saying.
Sent from my ADR6400L using XDA App
Am i missing the link???
Am I missing the credit? Thread Locked

Rooting/Downgrading HTC Desire Z confusion

Hey guys, complete n00b here
I'm trying to root my htc desire z, and in the process I realised I have to downgrade.
adb, sdk... etc. etc. I'm very in the dark about a lot of this... I've trawled through page after page after page (mostly on this site) and I get lost for a lot of it. I'm only learning very basic stuff about cmd prompt now.
Can anyone help me through this? Maybe fire some questions at me to get the ball rolling? Any help at all is much appreciated.
Oh, and if this is posted in the wrong forum, please direct me otherwise
Cheers guys.
Further info
I'm running Android 2.3.3
I've been following this:
http://forum.xda-developers.com/showthread.php?t=905261
Although I've been using a different downgrade folder (replace "psneuter" with "fre3vo")
All the files are in a folder called "Downgrade", directly on my C drive...
I go into cmd prompt and type the following...
---------------------------------------------------------------------------------------------------
cd\Downgrade
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo
and then it gets stuck at
fre3vo by #teamwin
Please wait....
---------------------------------------------------------------------------------------------------
It used to continue on from that, and I'd type adb shell and get a # instead of a $, but I had the wrong .zip file on my SD card so the reboot thing didn't work properly.
Now that I'm certain I have the right .zip file on it, I'm stuck at this command prompt problem.... I'm very, very confused...
Ok, I've gotten past all those problems. But it just won't downgrade to older firmware for some reason. I get to the bootload, and it waits for a second, then comes up with a quick list (that I can't make out in time) but I'm fairly sure it's coming up with the .zip files and saying they're not images? Then it just reverts back to the bootloader screen.
Am I completely wasting my time based on the fact that it's 2.3.3?
Can you see the file extensions on your PC? A common mistake is to name the file zip.zip instead of just .zip at the end.
Here is a good downgrade guide for gingerbread.
Like ArmedandDangerous said, make sure your computer is not set to 'hide file extensions' (quick google search will tell you how to check/change).
If hboot still refuses to flash the PC10IMG.zip, come to #G2ROOT on freenode irc for help.
-Nipqer
Hey guys thanks for the replies! (likin the profile pic Nipqer )
Yeah I can see the file extensions and I'm fairly sure that I have the .zip file named perfectly. I'm not on my PC right now, but I'll have a "root" ( ) around when I am. I'm fairly certain I already gave that downgrade guide a bash though, but I'll try it once more. I'll post updates when I have them, thanks guys!
little more extensive on the rooting procedure if maybe your interested
http://techticians.com/index.php/mobile-tech/14-mobile-phones/27-rooting-the-t-mobile-g2
Is it possible to downgrade from 2.3.3 though? I've read in a lot of places that it can't be done?
Thanks for all your responses guys! I understand how irritating n00bs can be
No worries--we've all been newbs once
It IS in fact possible to downgrade then upgrade from stock 2.3.3 (I've actually done it; I've messed about with custom firmware back when I had a Samsung Omnia, but this was pretty much my "rooting deflowering" as far as Android phones went).
Here's how I did mine (this assumes you are running Windows and not MacOS X or Linux). I'm assuming you've backed up your apps first
a) Install Android SDK Tools (http://developer.android.com/sdk/index.html). I pretty much did the full install.
b) Install HTC Sync (I got it from http://www.htc.com/de/SupportViewNews.aspx?dl_id=1073&news_id=918 which is all in German but will still get you set up).
c) You will need to set paths correctly--in my case I had to click "Start", "Control Panel", "System", "Advanced", then click the button labeled "Environment Variables", then add in the "PATH" where the apps for ADB and (more important for our purposes) the platform-tools directory for ADB lives.
(There's actually a pretty good, in-depth guide at http://forum.xda-developers.com/showthread.php?t=879701 on how to do this, but I'm just posting the Cliff's Notes version here )
d) Set USB Debugging on with the phone. Connect phone to computer using stock cable, click "Start", "Run", then "cmd" to open a command window. Type "adb shell cat /dev/msm_rotator" in that command window, hit return--if it gives some error about invalid length, your phone is visible to ADB and you SHOULD in theory be ready to downgrade.
e) Download and unzip the files attached in the article on downgrading (http://forum.xda-developers.com/showthread.php?t=1178912) to the directory where "platform-tools" lives (usually something like C:\Program Files\Android\android-sdk-windows\platform-tools unless you installed it in a nonstandard location) and then in the command window type "cd C:\Program Files\Android\android-sdk-windows\platform-tools" (without quotes, and change that last bit to the actual directory if you installed it in a nonstandard location).
f) From there, follow the downgrade guide--if it hiccups, go on IRC to #G2Root and ask for help. (I didn't have any hiccups with this guide.) All the commands will be typed in that command window I mentioned. (Oh yes, you'll be getting intimately familiar with a command line and command window with this.)
g) Confirm (once the phone boots up after you re-flashed the ROM) that it is running 2.2.
h) Follow the guide on how to root a stock Froyo phone (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision)--you won't have to worry about psneuter or any of that, because you've already done that (with fre3vo rather than psneuter).
i) Once you've confirmed it's rooted (according to that guide), then (assuming you're upgrading to 2.3.4 rooted or CM7 or whatnot) install the latest radio for the T-Mobile G2 (yes, you want to do this before ever messing with putting on a new ROM, otherwise you are going to find that stuff will go sideways). Get the latest T-Mobile G2 radio (http://www.mediafire.com/?vumdi3gges6ia4o), rename it to PC10IMG.zip, and follow this guide (http://forum.xda-developers.com/showthread.php?t=970809&highlight=install+radio).
j) Install the particular rooted ROM you want to use. (I ended up just using a rooted version of stock in this thread: http://forum.xda-developers.com/showthread.php?t=1202498).
And--barring a hiccup with the phone--voila, root.
This is pretty much what worked for me--can't guarantee it'll work for others. (Probably the scariest part to me was the radio update, but even this actually was relatively painless.)
I could KISS you guys!!!!
I ended up just going with the guide that Tbbo514 linked, and after a few hiccups, it works like a charm. I'm now rooted, gonna go search for a ROM so exciting.
Once again, you guys are legends! Thanks so much!
philbagg said:
I could KISS you guys!!!!
I ended up just going with the guide that Tbbo514 linked, and after a few hiccups, it works like a charm. I'm now rooted, gonna go search for a ROM so exciting.
Once again, you guys are legends! Thanks so much!
Click to expand...
Click to collapse
no problem at all dude i wrote the article because i wanted people to have exact details it makes it easier when you dont have to research anything
Tbbo514 said:
little more extensive on the rooting procedure if maybe your interested
Click to expand...
Click to collapse
Thank you so much! Took me a while since I just rooted my phone for the very first time, time to install a ROM! <3
corrupted23 said:
Thank you so much! Took me a while since I just rooted my phone for the very first time, time to install a ROM! <3
Click to expand...
Click to collapse
no problem just trying to make things a little easier
I have downgraded no probs, just having problems getting S-OFF with stock froyo 2.2 with temp root.
slufoot69 said:
I have downgraded no probs, just having problems getting S-OFF with stock froyo 2.2 with temp root.
Click to expand...
Click to collapse
which methods have you attempted to turn S-off
Well I finally figured out the S-OFF issue now im stuck on the last step to perm root my 2.3.4 GingerBread. Here is where Im stuck now.
http://forum.xda-developers.com/showthread.php?t=1228515
thanks...
Sean...
slufoot69 said:
Well I finally figured out the S-OFF issue now im stuck on the last step to perm root my 2.3.4 GingerBread. Here is where Im stuck now.
http://forum.xda-developers.com/showthread.php?t=1228515
thanks...
Sean...
Click to expand...
Click to collapse
should have just posted it here lol..this may sound stupid to say lol but are you hitting the power button or the optical pad button..if you hit power i noticed sometimes it would show the gear with the hat on..try selecting with the optical button instead

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.
Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium
Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium
Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.
okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?
@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.
Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium

do i need adb if im using ubuntu?

I'm thinking of rooting this kindle fire but all the directions are for Windows. I rooted my EVO on ubuntu without adb. Where can I find directions for rooting with Linux?
please please please check the forums. also it would be helpful if we knew what software version you were running.
adbirdie said:
please please please check the forums. also it would be helpful if we knew what software version you were running.
Click to expand...
Click to collapse
Thanks 6.2.1
Getting ADB working is your best bet. Even if you can get it rooted without adb, it will save you a lot of headache later if something doesn't work.
Getting adb to work on Ubuntu with the Kindle Fire should just require downloading the sdk, running the SDK manager to install platform-tools, adding platform-tools to your path, editing ~/.android/adb_usb.ini to include 0x1949, and likely adding udev rules for it (you can find instructions on udev rules on quite a few forums, or read the README in /etc/udev/rules.d which might help).
Rootzwiki has instructions for rooting (not using KFU) and for installing TWRP afterwards too. Just follow the steps in jcase's thread for root and the TWRP post is stickied. I'd link, but I forgot my old account and don't have enough posts on this one to link yet.

[Q] cant downgrade mytouch 4g

im a noob and i installed adb and in adb the serial number of the mytouch is there or watever it is. n i just dont understand the part of put the frevo file inside the frevo zip file inside the platform tools n the misc version inside the misc zip file in platform tools.wat do i do with the rest misc files that were in the zip file its too downgrade n i dont thats only part dont understand to downgrade plz reply fast i alredy want to downgrade n already saw all the other forums of it
Did you install android sdk or just adb by itself?
Sent from my HTC Glacier using xda premium
You know that ZIP files contain other files?
You know you can extract those files?
You know that there are different folders on disk?
You know that folders are in a tree-like structure?
You know where platform-tools folder sits under SDK folder?
You know how to move ZIP files where you need?
You know how to extract ZIP files in place?
Answer all these, and you'll know what to do.
If you don't know the answer to one or two specific questions - ask away.
If you don't know some of the answers and can't or don't want to look for them - please refrain from rooting. Rooting isn't just for fun, it gives you some powers over your phone that you need to know how to use - otherwise your phone will have a great potential to end up screwed.
Whoa alexriio!
You can find a lot of people here to help you but you will need to do 2 things first :
1- Please write complete sentence. It's so hard to read you; a lot of people will skip you post.
2- Read these tutorial :
ADB from cyanogenmod
http://wiki.cyanogenmod.com/wiki/ADB
Newcomers please read me, a helpful little guide by neidlinger
http://forum.xda-developers.com/showthread.php?t=1281085
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo by Setherio
http://forum.xda-developers.com/showthread.php?t=1178912
My usual advice is :
1- Print all part of the tuto (tuto, downgrade to froyo, CM install...)
2- Read it carefully and come back here to ask questions
3- Prepare all file in distinctive folder (check all file with md5sum!)
4- Grab a coffee (or tea, or beer )
5- Attack!
Regards.
I installed everything n know how to root n flash. And I installed adb n sdk too. And I extraded the frevoo n misc zip file. n then it said put the files into the sdk platform tools so I did but on the misc file there's alot of files inside the zip. so which one do I put in the platform tools
Sent from my LG-E739 using xda premium
This is what I have in platform-tools :
$:>ls /opt/android-sdk/platform-tools
aapt*
adb*
aidl*
busybox
dexdump*
dx*
fastboot*
fixsu.sh
fre3vo
gfree*
hboot-eng.img
lib/
llvm-rs-cc*
misc_version*
NOTICE.txt*
PD15IMG.zip
psneuter*
recovery-clockwork-5.0.2.0-glacier.img
renderscript/
root_psn
source.properties*
su
SuperUser.apk
update-cm-7.1.0-glacier-signed.zip
Click to expand...
Click to collapse
The rest of the file in misc_version.zip are the source.
Thanks you that's wat I wanted
Sent from my LG-E739 using xda premium
Need help downgrading mytouch
Greetings. I've got a mytouch 4g. I have followed the instructions in http://forum.xda-developers.com/showthread.php?t=1178912. Excellent article. Every step works great. I have tried both the manual downgrade section and the fastboot downgrade section. Both methods appear successful. No error messages, etc... When the phone reboots it boots to a fresh 2.3.4. Im sure im skipping something simple. Any ideas greatly appreciated!

Categories

Resources