Related
have any of you guys tried the unlockr.coms method of perm rooting?? I used it for my g2 and it worked but idk if it will work like a charm with the mt4g..also do we have to use visionary r14 or a different version because the link it gives us is visionary r14
Same as it was originally done though G2 then MT4G was developed. You can use it with ease nothing to worry about.
STHNS said:
UPDATE: Here I found you Youtube videos how to do step by step.
TempROOT> http://www.youtube.com/watch?v=gylaXOCNzqU
PermROOT> http://www.youtube.com/watch?v=Sy_aqKoeev4
Use the howto from Theunlockr video posted above it maybe easier for you to follow.
Click to expand...
Click to collapse
Worked great for me, and easy as pie
Im sorry for any stupid/ noob questions, but in your honest opinion aside from having root access and being able to remove pre installed apps, what are the other benefits from going thru the root process?
You can overclock (make phone faster) also set cpu profiles to make phone cpu to run at lowest mhz to save battery. install customs romsthat have better customization and also have the newest android software before anyone else. .
Sent from my HTC Glacier using XDA App
kingvaj23 said:
install customs romsthat have better customization and also have the newest android software before anyone else. .
Click to expand...
Click to collapse
Just remember that this'll disable any OTA updates that'll come out for your phone...
But who needs ota updates we already have gingerbread if your rooted
Sent from my icey cold glacier 4g freezing every phone in its path
+1
Sent from my HTC Glacier using XDA App
jriv said:
But who needs ota updates we already have gingerbread if your rooted
Sent from my icey cold glacier 4g freezing every phone in its path
Click to expand...
Click to collapse
LOL thats why I was laughing as it being on XDA lol and who would want to use OTA stock base in first place?
after I purchased my phone, I immediately hit the internet and looked up some info on the MT4G and saw the Unlockr method for rooting and following the guide made it very easy. 2 thumbs up for me, and yes visionary 14 works
Sounds good I'm gonna use that method once my replacement gets here wednesday
Sent from my HTC Glacier using XDA App
Best...simpliest...and easy
Temp and permarooted w the steps given....1 try and it was golden and flashing was easy
Highly recommended!
Sent from my HTC Glacier using XDA App
i just got the mt4g and i wanna root it but i dont wanna lose swype like i did when i root my mt3gslide. is there a way i can get swype on 4g after i root it?
@RoyalTaco:
Several of the roms have swype. Including "iced glacier" and "evil's desire hd" (which I'm using now as I type. Love swype)
Sent from my HTC Glacier using XDA App
RoyalTaco said:
i just got the mt4g and i wanna root it but i dont wanna lose swype like i did when i root my mt3gslide. is there a way i can get swype on 4g after i root it?
Click to expand...
Click to collapse
Rooting a MT4G will not remove any applications. Swype is pre-installed, and will stay that way. The only way to "lose" Swype is to flash a ROM that does not include it. In that case, you can go to the Swype website and download it directly by signing up for the beta.
oh ok thx guys. Using this method i after i reboot the phone i keep getting S-On. what could i be doing wrong?
unlockr
I get this far
1. On your phone, go to Settings > Applications > Development > and make sure USB Debugging is ON (it MUST be ON) and make sure Fastboot is checked OFF (if it exists in your settings, otherwise don’t worry about it).
2.Download Visionary from here
3. Plug in your phone via USB cable and mount the sd card so we can transfer files to it.
4.Copy the Visionary .apk file to the root of your phone’s memory card (NOT in any folder just on the sd card itself).
5. Then simply open any file manager app on your phone (like Linda File Manager for free from the Market for example) find the visionary apk file in the file manager and click it and follow the prompts to install it.
Click to expand...
Click to collapse
When I open the file manager app (i tried Linda and OI File Manager) the file isn't there.
I know I did everything, I tried several times, but nothing. Any advice?
Jonathan
lanternslight456 said:
... the file isn't there.
I know I did everything...
Click to expand...
Click to collapse
If the file isn't there, I can imagine only three possibilities. Choose one. These are the only reasonable possibilities, but as we're not psychic, you'll have to figure out which it might be of these three.
You did not transfer the file to the SD card at all.
You transferred it to the wrong directory on the SD card .
You're looking for it in the wrong directory.
Could it be something else? Sure. Perhaps you renamed the file. Perhaps you switched SD cards.... but if you're using the same SD card, and you did not rename the file, then one of those three are the likely candidate.
Here's the info I know from what I've done in regards to these options (I'm going to try again tonight though)
1. You did not transfer the file to the SD card at all.
My computer can see the file on the lettered drive, (the USB port it's plugged into) there is no other address info in the address bar other than the lettered drive
2. You transferred it to the wrong directory on the SD card .
Again, same as above
3. You're looking for it in the wrong directory.
In the file explorer on the phone the address in the directory is just /
again I'm going to try tonight but maybe this info can clear it up. I'm learning a lot about these things and how they work so thanks for all the help!
Jonathan
unLockr
II. Flash the S-OFF Hboot Image and Gain Perm Root
1. Download the rooting files:
* T-Mobile MyTouch 4G / HTC Glacier S-OFF/Rooting Files
2. Extract the files somewhere to your computer.
3. Plug your phone in via USB cable and mount the SD card so we can transfer files to it.
4. Copy the entire root folder from inside the extracted folder from step 2 to the root of your sd card on your phone (NOT in any folders, just on the SD card itself).
5. Unplug the phone.
6. Go to the Market on your phone and download/install Android Terminal Emulator (free).
4. Open the Terminal Emulator app and type the following with hitting enter at the end of each line (to get the touch screen keyboard to come up hit the menu button then toggle soft keyboard):
su
cd /sdcard/root
sh root.sh
5. Now, wait for it to finish.
6. After that is done, reboot the phone. When it boots back up, turn it off and back on holding down Volume Down and Power until the HBoot screen comes up. Confirm it says S-OFF at the top. If so, you have S-OFF.
i do steps 1-5 but when i get to step 6 and reboot my phone while holding volume down i have S-ON and not off! any ideas what i can be doing wrong. btw i did the temp root b4 trying this.
I'll say this from the start, I'm a total newbie when it comes to smartphone rooting, modding and developing.
So today I decided to go ahead with my Bell mobility HTC Desire Z and get it rooted.
I read through the forums ans all the threads related to desire z and vision phones.
Knowing that I had a version of 1.84 I knew that a downgrade was the only way for me. Got a goldcard created, downgraded to 1.34 got all the nifty tools and finally rooted the phone permanently and loaded Cyanogen mod7.
All this to say that the Xda community put up some damn fine guides.
Sent from my HTC Desire Z using XDA Premium App
Right on dude grats, total new device on cm7.
Im also on a bell dz but on the rogers network. Loved the look on the bell reps face when i told her i was gonna use it on rogers and she laughed at me, 2 hours later i went back to make her eat her words...it was priceless.
Sent from my HTC Vision using XDA Premium App
Welcome to the community and great on you to root and load up a custom rom. I also have the Bell DZ but on the Telus network running Virtuous G-Lite. Few people would do what you did (patience and reading before acting) so props to you!
Have fun with the device
Thx guys!
Definitely noticed that it's running faster with Android 2.3.3 also. I'm quite happy with the modification.
Had to test it on mine first before I started playing with my friends DZ... he's been hounding me to do it for a few weeks.
I had free time on my hands and I honestly have to mention that I did screw up once on the initial rooting, took a second pass at it and figured out what I did wrong.
It's been running fine since 3pm EST yesterday. Had to load all my apps again which was a pain at first but it's slick now.
fluxgfx said:
I'll say this from the start, I'm a total newbie when it comes to smartphone rooting, modding and developing.
So today I decided to go ahead with my Bell mobility HTC Desire Z and get it rooted.
I read through the forums ans all the threads related to desire z and vision phones.
Knowing that I had a version of 1.84 I knew that a downgrade was the only way for me. Got a goldcard created, downgraded to 1.34 got all the nifty tools and finally rooted the phone permanently and loaded Cyanogen mod7.
All this to say that the Xda community put up some damn fine guides.
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
Hi im sort of a newb to this and im in the same situation as you. can you help me with rooting my bell htc desire z? i used a guide to create a goldcard. but when i got to the step that needed the misc.img, it said u need super user. but i didnt have root or temp root and visionary dosent work to temp root. how can i pass the step of finding the misc.img and changing it?
All right which part are you stuck at. I need the link to the guide your following... After I created my goldcard there's a process using hxd hexeditor to make some changes to your IMG file that you'll need to save to the SDcard top header so that when you try to use PC10IMG.zip will validate correctly and allow you to downgrade.
This is the processed I fallowed to get my Goldcard.
http://forum.xda-developers.com/showthread.php?t=832503
Part 1 GoldCard
1) Format the microSD card to FAT32 format (in card reader).
2) Put the microSD card in your device and boot it.
3) Open Up an ADB shell this doesnt need to be ran as root.
4) Enter 'adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid' and press enter. You should get a very long number copy it.
5) Visit this page, paste in your number and reverse it.
6) Visit this page, enter your reversed number and create your goldcard image, which will be e-mailed to you.
7) Open the HxD hex editor. If you are using Windows Vista or Windows 7, you must run the application as administrator.
8) Go to the 'Extra' menu and select 'Open Disk'. Under physical disk, select Removable Disk (your microSD card), uncheck 'Open as Readonly' and click OK. Note that you should select physical disk NOT the logical disk. This is important!
9) Go to the 'Extra' menu again and select 'Open Disk Image'. Open the goldcard image that you received by email.
10) You should now have two tabs - one is your removable disk, the other is your goldcard image. Press OK when prompted for 'Sector Size' (selecting 512 (Hard disks/Floppy disks)) and click OK.
11) Click on the goldcard image tab. Go to the 'Edit' menu, choose 'Select All' then select the 'Edit' menu again and select 'Copy'.
12) Click on the 'Removable Disk' tab. Highlight offset (line) 00000000 to offset (line) 00000170 (including the 00000170 line), then click on the 'Edit' menu and select 'Paste Write'.
13) Click on the 'File' menu and select 'Save', accepting the warning.
This will allow you to be able to use PC10IMG.zip to be able to downgrade to 1.34. From that point on fallow this guide:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Point #7.
Hopefully this helps you.
-/ I'm located in Ottawa so if your in my city I could help you out. Cheers mate.
well were somewhat near by. im in toronto, ontario lol. ok i got past that step but the step im stuck on is when i go into the boot loader after i created a new misc.img, it says no image or wrong image?
Morning mate.
You actually need the PC10IMG. Zip on your sdcard root that's the recovery OS
Sent from my HTC Vision using XDA Premium App
i do have it on my sd card rooot. but i downloaded as the zip file from a friend because i couldent find the zip file from the ruu
also since were in the same timezone, do you think you could stayonline for a few minutes to help me?
I'm not home. But if you followed the goldcard process once in recovery it should detect the img file and verify it before asking to complete recovery.
Sent from my HTC Vision using XDA Premium App
I followed the guide exactlly, and everything was good until part 4 where i had to go into bootloader. i copied the pc10img file to the root and when i do the hboot, it says checking for imp then it says no img or wrong img.
All right then you haven't done the goldcard process correctly. Did you use the hxd hexditor to open the misc.img file and copy the top part as indicated to the sdcard header on the hexditor tool?
Sent from my HTC Vision using XDA Premium App
i think i did it right but il try again and get back to you thanks
ok one quick question. i have the wwe ruu. once i run that, where do i find the .zip file on my computer?
Having any more luck?
Sent from my HTC Vision using XDA Premium App
no, i think i can solve the problem if i can just find the original .zip file from the 1.34.405.5 ruu. everytime i run it i cant find the .zip file. i have been using another one right now. where do i find the .zip file?
Hey,
I wouldn't know since I didn't get the ruu pack. I just downloaded the PC10IMG. Zip file.
Sent from my HTC Vision using XDA Premium App
If you are running 2.3.3 on your HTC EVO 4G, this method will gain you access to system and root files. This is not exactly root, but I am trying to figure out if it would be possible to manually replace hboot using my method. I was able to root my evo, but same method I am trying doesn't seem to work on my wife's phone.
STEPS:
01. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work.
03. Download "SD Tools" from the Android Market.
04. Copy the SD card CID code after installing "SD Tools".
05. Reverse the SD card CID code. ie "123456789" should be written as "987654321"
06. Go to here to generate your goldcard.
07. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
08. Click Continue and you will receive the goldcard.img in .zip format in your email.
09. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
10. Download HxD Hex Editor from here
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program.
17. Reboot your phone with this SD Card (now GoldCard) inside
You should now be able to use a file explorer like ASTRO to browse around in system, lib, sbin, framework, xbin, etc.
So what are you able to do with the your temp root? How long does it last (till reboot or one shot)
Correct me if I'm wrong, but I'm pretty sure you can browse threw the folders you listed without going threw any of the steps you listed.
roids87 said:
Correct me if I'm wrong, but I'm pretty sure you can browse threw the folders you listed without going threw any of the steps you listed.
Click to expand...
Click to collapse
I was thinking that as well but wasn't sure.
roids87 said:
Correct me if I'm wrong, but I'm pretty sure you can browse threw the folders you listed without going threw any of the steps you listed.
Click to expand...
Click to collapse
u r correct
so i did this and i got to a bootloader error via RUU . one small step closer
leo72793 said:
so i did this and i got to a bootloader error via RUU . one small step closer
Click to expand...
Click to collapse
I think ur talkin about the error u get when u try to downgrade i.e. 2.3 to 2.2.
Anyway, OP did u see this post?
http://forum.xda-developers.com/showthread.php?t=883548
Maybe the info can b used to edit 2.16 to look like 2.10 if ur method allows for hboot writes
leo72793 said:
so i did this and i got to a bootloader error via RUU . one small step closer
Click to expand...
Click to collapse
That's about where I got an RUU error message. You are right, it was one step closer. But now I am getting a signature error. Before, I could not even get past reboot to bootloader.
{ParanoiA} said:
I think ur talkin about the error u get when u try to downgrade i.e. 2.3 to 2.2.
Anyway, OP did u see this post?
http://forum.xda-developers.com/showthread.php?t=883548
Maybe the info can b used to edit 2.16 to look like 2.10 if ur method allows for hboot writes
Click to expand...
Click to collapse
yea maybe it can be used to make the 2.10.0001 bootloader fake as the new one
{ParanoiA} said:
I think ur talkin about the error u get when u try to downgrade i.e. 2.3 to 2.2.
Anyway, OP did u see this post?
http://forum.xda-developers.com/showthread.php?t=883548
Maybe the info can b used to edit 2.16 to look like 2.10 if ur method allows for hboot writes
Click to expand...
Click to collapse
I did see that, but that method requires S-off. Our S is on at this time... BUMMER.
Should probably remove TEMPROOT from the topic, since indeed, there is no temproot.
Ehh, I see the WIP tag.. whoops. I guess, good luck, but I think this has been tried.
cheers.
well since youve got the goldcard made, could you by any chance put a pc36img.zip of the 3.70.651.1 froyo build with all the stuff it needs and downgrade that way? kinda like what the inspire hack kit does
frickinjerms said:
well since youve got the goldcard made, could you by any chance put a pc36img.zip of the 3.70.651.1 froyo build with all the stuff it needs and downgrade that way? kinda like what the inspire hack kit does
Click to expand...
Click to collapse
Here is a link to the 3.70 zip file:
http://goo-inside.me/supersonic/ruu...15.00.11.19_NV_1.90_release_161482_signed.zip
Don't forget to rename it PC36IMG.zip and place on the root of the card.
So OP, you were able to go from never rooted with 2.3.3 (4.24 S-ON) to being rooted using the exact instructions you posted?
OP is just trolling us again. He did the exact same **** a few weeks back
http://forum.xda-developers.com/showthread.php?t=1169387
Nick N said:
Here is a link to the 3.70 zip file:
http://goo-inside.me/supersonic/ruu...15.00.11.19_NV_1.90_release_161482_signed.zip
Don't forget to rename it PC36IMG.zip and place on the root of the card.
Click to expand...
Click to collapse
well now we just need someone willing to take the plunge
frickinjerms said:
well now we just need someone willing to take the plunge
Click to expand...
Click to collapse
I tried this using steps from the "Downgrade" section located here:
http://androidforums.com/desire-hd-...b-build-downgrade-1-32-405-6-easy-follow.html
..but I got the failed older version message when using the 3.70 PC36IMG.zip
Wow, this guy is 2 for 2 on trolling.
People, no need to be so gullible. If any kind of usable root is achieved all you need to do is install a terminal app on your phone and type "su" at the prompt to test. Also need USB debugging enabled in phone settings...
Sent from my PC36100 using XDA Premium App
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
Hi guys
I just updated my HTC Wildfire from HBOOT version 08… to 1.01.0001 and I ran into many problems on the way. I’m just writing this guide to help out any other people that are in the same situation as me and don’t want to be searching Google for half a day finding solutions to every tiny problem. Please note this worked for me but I cannot guarantee it will work for you so follow this tutorial at your own risk!
Step 1: Find the RUU that has HBOOT 1.01.0001
I used RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe which you can find here.
And more specifically the download link is here (Credits to 3xeno for the RUU list and uploads).
Step 2: Extract the rom.zip from the RUU
There are many ways of extracting rom.zip the method I used is:
1. Run the RUU installer.
2. Go to your windows temporary folder.
3. Search for rom.zip
Another method that will definitely work and you can be sure you have the correct zip file is given here.
Step 3: Create a goldcard (easy way)
I found that flashing the above RUU was impossible without a goldcard and after lots of searching I found a link for downloading the GoldCardTool - a software that automates most of what you have to do and saves you lots of time.
Note: You need to format your SD card so backup anything important and then go to
Settings -> Storage -> Unmount SD Card
Then hit Erase SD card.
Now you are ready to create a Goldcard.
You can download the software here and follow the instructions in the readme file, they are very straight forward.
Step 4: Prepare the ROM for flashing
Rename rom.zip to PC49IMG.zip and place it on your SD card (in the root folder of your SD card ie. No folder within the SD card).
Now reboot your phone into the bootloader. Mine always starts with FASTBOOT in focus and I have to press the power button over BOOTLOADER to get it to scan the SD card for PC49IMG.zip. Once it finds the zip file it will open and parse the file and then ask you if you’d like to update. Press volume up to confirm then DON’T TOUCH ANYTHING.
Once the update is complete reboot the bootloader and make sure the HBOOT is 1.01.0001. Once that is confirmed you can boot into Android.
Step 5: Use AlphaRevx to get S-OFF and Clockwork recovery
Before you use AlphaRevx you will need to make sure you have the correct drivers.
Download the HTC Fastboot drivers which you can get here.
Also download Superuser which you will use later from here and copy this onto your SD card when you find the time!
(Credits for the links go to the guys at unrevoked for their wiki)
Now it’s time to get the Revolutionary software.
Go to http://revolutionary.io/ and download Revolutionary.
Now plug in your phone and make sure USB debugging is on, if it is not then go to Settings -> Applications -> Development and Enable USB debugging.
Now extract and run the Revolutionary software. It should open a command prompt and it will walk you through the installation, the serial number that you give in the website is given in the command prompt (it is not the same as the serial number on the back of your battery!). If you find an error right from the start it probably means you don’t have ADB drivers – Google sdk can help you out with that one. At the end of the installation it gives you the option to download and install Clockwork recovery mod – say yes (Y) to this option!
Step 6: Rooting your phone
Now that Revolutionary is complete you can reboot your phone into Clockwork Recovery. Select install application from zip file. Choose to select the zip file and then find the Superuser zip file that you download earlier (Superuser-3.0.7-efgh-signed.zip) and install it. If you forgot to put it on DON’T reboot your phone just go to the main menu of Clockwork Recovery. Go to mounts/partitions (I can’t remember the exact name) and at the bottom it says “mount SD card”. Select that and copy the file over to the SD card and then flash it using the directions given above.
Step 7: Flashing a custom ROM (or Fix for if your phone stops on boot screen)
You can either stop at Step 6 or continue to this step and flash a custom ROM.
To do this boot into Clockwork Recovery and do the following:
1. Wipe data
2. Clear cache
3. Clear Dalvik cache in advanced menu
I found that after I flashed a ROM without doing the above 3 steps it got stuck on the boot screen so please do the above 3 steps!
Now flash the ROM by choosing to install from a zip file. Reboot and you’re done!
I updated to Cyanogen mod 2.3.7 and I just want to throw in that Radio_13.55.55.24H_3.35.20.10.zip worked for me !
I really hope this tutorial helped. I just did it with my phone and it’s working well so I wanted to share what I did. Credits go out to everyone that put up tutorials on how to solve problems and all the download links and especially to the guys that wrote Revolutionary – it is an amazing software keep up the good work !
Cheers guys
Kerren
A very thorough guide and many people will benefit from this.
This is nearly exactly the same routine I followed from a guide which I can't remember where from now lol and very grateful help from 3xeno (yoda) but I don't think I did anything with alpharevx though and also I just flashed my cm7 nandroid after revolutionary to gain my superuser and I'm sure the serial part WAS my serial on phone but can't remember exactly.
Anyway my point is that after reading through your post it brought back the memory of the satisfaction of successfully s-offing my phone. great work.
"sent from me2u"
Cool!
Haha thanks man glad I could bring back memories
When it comes to the serial number I'm not completely sure, I had generated a code from the serial on the back of my battery and that didn't work. I then read the serial from command prompt and it seemed a lot shorter (also I got a code that worked ).
Maybe I made a mistake originally but all I know is that you don't have to rip your battery out to get the serial number - they give it to you anyway .
Thanks very much for the reply!
Ah yes that sounds familiar now.
"sent from me2u"