Related
Hey Guys
So one of the biggest questions I have seen in the last couple weeks since the Rogers captivate was released is how to root. I figured I would write a nice tutorial for everyone to make it easier!
Method 1: SuperOneClick
This is the easiest way, however most people have not been able to achieve root using this. Try this first if no luck move to method 2. Instructions on how to root using SuperOneClick can be found here
Method 2: Manual Root using ADB and Terminal
This one takes more time and not as easy to do as you have to do everything manually. But haven't heard of any problems with it yet
Step 1: Install <PDANet> Drivers. Just download the file and install. Select Samsung drivers. No need to actually install PDAnet on the Captivate you just need the drivers from the install. Follow the instructions with the installer to properly install the drivers.
Step 2: Download <Andriod SDK>.
- Extract the Android SDK .Zip file to C:\AndroidSDK (this should name the new folder created AndroidSDK in the C directory.
- Go to your start menu and search cmd or click run and type in cmd to open command prompt
- Type the following into command prompt, hitting enter at the end of each line
cd C:\AndroidSKD\Tools
adb devices
- You should see a serial number pop up. This is the serial number of your phone. This means ADB is set up
Step 3: Download <RageagainsttheCage Rooting Files>
- Extract them to the c:\AndroidSDK\tools\ folder. HAS TO BE IN THIS FOLDER FOR THE FOLLOWING COMMANDS TO WORK
Step 4: Unplug phone if it is plugged in. Then, on the phone, go to Settings > Applications > Development and make sure USB Debugging is Checked ON.
Step 5: Plug phone back in to computer. Make sure SD are not mounted
Step 6: Reopen Command prompt if not open. In the command prompt enter the following, pressing enter at the end of each line
cd c:\androidsdk\tools\
adb devices
adb push Superuser.apk /sdcard/
adb push su /sdcard/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
Step 7: On the phone, go to Marketplace and download Terminal Emulator
Step 8: Leaving the phone plugged in, open the Terminal Emulator on the phone. Type the following, pressing enter at the end of each line
cd /data/local/tmp
./rageagainstthecage-arm5.bin
Step 9: WAIT. It will take a full minutes for the rage root to install. When finished you will see "Forked Childs". DO NOT DO ANYTHING TILL YOU SEE THIS. Terminal will allow you to type as it goes back to $ while it is installing BUUT DO NOT DO ANYTHING JUST WAIT(Cannot stress this enough)
Step 10: once "Forked Childs" appears, exit the Terminal App, and then reopen it. Instead of $ you should now see #. If not redo Step 7. Otherwise continue.
Step 11: Type the following hitting enter at the end
cat /proc/mounts
This should bring up a list (Easiest to view in landscape mode. Look for the following
/dev/block/XXXXXXXXXX /system YYYY ro 0 0 (the XXXXXXXXX part should be different depending on which device you have. The YYYY part will either be; ext2, ext3 or yaffs2 or something similar. )
My YYYY was rtf , not sure if it will be the same for everyone (though i assume it is)
Step 12: Now in the terminal window, using the info from above, enter the following, hitting enter at the end of each line (Be sure to enter spaces where needed as below)
mount -o rw,remount -t YYYY /dev/block/XXXXXXXXXX /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t YYYY /dev/block/XXXXXXXXXX /system
exit
Step 13: Close terminal window if still open. Check your app drawer and, assuming everything was completed properly, you should see Superuser. If not redo Step 12, again watching for spaces and using the correct info from Step 11.
ACKNOWLEDGEMENTS
I, in no way shape or form, came up with the above method or tools. This method was modified from and composed from the method decribed over at Theunlockr.com for ease of use and to root the Captivate specifically. I big thanks go out to those guys!
ORINGAL LINK CAN BE FOUND HERE
WARNING
I am not responsible for any damage doone to the phone or its file system as a result of this tutorial. It is for educational purposes only. You have been warned!
THANK YOU!
No other method was working for me (not SuperOneClick, not these ADB instructions). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
PhrProfess said:
THANK YOU!
No other method was working for me (not SuperOneClick, not ). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread[/url] (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
Click to expand...
Click to collapse
Yup same problem here. I was able to root it manually a few days ago, but have as of yet been unable to lag fix it.
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
deacfire said:
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
Click to expand...
Click to collapse
Correct. I've tested out quite a few apps from the market, though.
When I mount my device, I notice that there are some files on my internal SDCard:
-su
-Superuser.apk
-nv_data.bin
-busybox (why is this there, I uninstalled that)
-update.zip
...and some folders:
-layar
-twc-cache
-Android -» data -» com.cooliris.media
-Android -» data -» com.google.android.apps.maps
-svox
...These all have subdirectories.
Not knowing what a default internal SD directory ought to look like, I wonder: Could any of these be causing a conflict? I read that some said not to have any apps installed on the SDCard while trying to mess around (with ROMs, I think), so I tried removing what I could, and then rebooting (and some folders respawned), and reapplying the fix—no dice. I've since replaced all of the folders and the files.
Stock rom here as well.
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
deacfire said:
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
Click to expand...
Click to collapse
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
mrprefect said:
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
Click to expand...
Click to collapse
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
deacfire said:
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
Click to expand...
Click to collapse
Happen to have a link right to the forum? so many threads to search through...
I'm new to the whole android thing though I've been working with linux for years but its a bit of a learning curve coming from a blackberry.
also what are you using to flash your device?
I'm having the same problem. Let me know if you somehow fix it.
Sent from my SAMSUNG-SGH-I896 using XDA App
I was finally able to get my last night.
Turns out my first root attempt was a failure. I had to unroot via an update.zip method as i did not have the permissions to remove the files from terminal.
Once unrooted i then did the update.zip method for the I897, and modified the script to look for I896 instead. It worked flawlessley. I am now getting the pop-up asking for root permissions. I had never seen it work previously.
I was then able to install OCLF without any problems. (and it popped up asking for root)
I am now rooted and lag fixed. Previous quadrant score was at 860's and i pulled a 2285 last night after the OCLF.
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuse app wont go away after unrooting and factory reset
inningsdefeat500 said:
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuser app wont go away after unrooting and factory reset
Click to expand...
Click to collapse
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download THIS FILE and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
EDIT!!!
Some mirrors for the files
For the UN-Root files go HERE
For the ROOT files go HERE
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
dandroid123 said:
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Take a look here. It answered alot of my questions.
http://www.androidcentral.com/rooting-it-me-some-qa
Also, if you only follow the second half of my post above you should be able to root it as well.
Thanks deacfire! The one click wouldn't work for me but the second method did.
I am having a really annoying problem though. The superuser.apk that you included just gave me a black screen. So I updated it to this one: http://forum.xda-developers.com/showthread.php?t=682828&highlight=no+apps+in+list
Which is newer. But now it just says "no apps in list". Tried installing it from the zip, tried from the market no different.
I do have apps that require superuser: ROM Manager, Root Explorer, Adfree. They all work, also have titanium backup but its is telling me it needs root access.
How can I fix this, it is a major issue.
EDIT:Thanks impulser91!! That work and was SUPER easy! Should probably get posted in the original post.
when i copy update.zip into the /sdcard and then try hitting reinstall packages, it results in an error and aborts. any suggestions?
Nevermind....it worked MUAHAHAHAHAHAH LET THE FUN BEGIN!
Sweet, 2 users. Not bad for under 10 posts
I'm glad its working for others. I had one heck of a time finding the right combination of files and process's for the I896. I am an IT professional and it took me a few days of fumbling around all the I896 and I897 posts.
Anyways, glad to hear it worked, and i hope other people find it useful as well. I will keep the originals, so if the links go down someone just PM me and i will load them somewhere else.
impulser91 said:
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
Click to expand...
Click to collapse
I could just about kiss you.... but I won't
Thanks for the update files they worked like a charm. I had a similar issue where the device didn't seem to be properly rooted, though it didn't give me any issues with most things when applying the lagfix it would die.
applied both your unroot and then root and it worked flawlessly the first time, lagfix then ran with no issues and my quadrant scores are 2250 now.
Not sure what you did exactly, I've tried rooting from update.zip from oneclick and neither worked I ended up rooting with the ADB and though it seemed to work it apparently did not.
Thanks again
This is my easy-rooter for the Thunderbolt. I do not personally have a thunderbolt but I have tested it and fixed as many problems as I could. As far as I'm aware this will only work with firmware versions lower than version 1.12.605.9.
If adb does not see your device try installing the htc sync drivers. If that doesn't wok install PDA.net. If it still does not register please post here. If you have a 64-bit version of windows replace the files in the rar with these
THIS IS A WINDOWS-ONLY PROGRAM. You must have windows or a windows VM to use this.
As always there is a small chance of bricking your phone.
DISCLAIMER: AndIRC is not affiliated with this program and by using it you agree that neither AndIRc nor myself is responsible for any damages caused by this program.
This provides all necessary files and gives you in-program instructions.
Please read this before using this.
Known bugs:
Sometimes you need to redo step 3. If the phone does not reboot on its own simply press the step 3 button again.
Issues:
The files take a long time to push. It could be anywhere from 3-10 minutes.
Once you have completed step one do not redo it for any reason! If it flashes only continue from step 2!
Credits:
Team AndIRC - for developing the root method found here
XDA - for giving me the chance to make programs like this
me - for making it
Donations:
Please donate to charity first and myself only if you want to. Please make donations in AndIRC's name as well as your own. You can donate here, to the Japan Relief Fund, or any other worthy charity.
since I just saw jcase's thing about my donation link (apparently I'm blind) here it is for those of you who wish to donate to me.
Downloads:
http://www.megaupload.com/?d=28H4U0QS
mirrors:
Instructions:
For those of you who can't follow or understand the directions in the program here is a pdf with instructions.
For anyone having problems getting steps 1 and 2 to work the first time through here's something to try.
lado44 said:
Hey man, I'm new so can't post in dev forum.
Your method worked for me - one thing I found. It was hanging at step 1 like some folks have reported, pushing the files (could see .ZIP on SD card), but would fail to reboot. This happened several times with Fast Boot enable under Settings>Applications. When I unchecked Fast Boot and re-ran Step 1 it worked first try. Couldn't tell you why or if just coincidence, but might help others.
Cheers.
Click to expand...
Click to collapse
For those of you who are interested in how this method works, here's the explanation. I will be focusing on what the program does,not user interaction so much except where necessary.
Push busybox, psneuter,and misc.img to /data/local/
Push PG05IMG_downgrade.zip to /sdcard and rename to PG05IMG.zip
chmod psneuter and busybox
execute psneuter
check the md5 hash of misc.img
flash misc.img to /dev/block/mmcblk0p17 if the hash is c88dd947eb3b36eec90503a3525ae0de
reboot into the bootloader
press power to enter bootloader and flash PG05IMG.zip (done by user)
once back in android:
remove PG05IMG.zip
push busybox, psneuter, and wpthis to /data/local
chmod all 3 files
run psneuter
run wpthis
push the engineering hboot(hbooteng.nb0) to /data/local/
check the md5 of the hboot file (it should be 6991368ee2deaf182048a3ed9d3c0fcb)
if it is flash hbooteng.nb0 to /dev/block/mmcblk0p18
push the PG05IMG.zip file to /sdcard
reboot into the bootloader
again press power and flash PG05IMG.zip (done by user)
push su, busybox, and psneuter to /data/local
chmod psneuter and busybox
run psneuter
mount /system as read/write (rw)
copy su to /system/xbin/su
chown and chmod su
install superuser and RomManager
Click to expand...
Click to collapse
I do recommend learning ADB as it is quite helpful but I realize that for some people that is a daunting task at first glance. I remember being a n00b and this will allow you to fully utilize your phone while still learning at your own pace on the side.
I am attaching just the updated exe.
Great idea showing what happens. Cool that you put something together for TBOLT owners, I just hope people will try and figure out what is going on when they use this.
After seeing a lot of issues people having with setting up adb I guess I should share this link... ADB For Dummies by AndroidSamurai
Even has an app to set everything up in the right spot.
This is a great thread on altering the android_winusb.inf for compatibility with Thunderbolt (adb driver).
<open>Can of Worms</open>
Thanks for the hard work.
One of the conditions for release was that I explain what happend. Hope this helps people out.
Nicely done. thanks for your hard work and knowledge. Now to get adb up and running finally.
You're welcome, and if the program functions properly you shouldn't need to setup adb beforehand as it comes with the necessary files for interaction. If it doesn't work properly try the debugging steps I posted in the OP and if that doesn't work setting up adb as a system command (adding the tools folder to PATH) should fix things.
^Thank you kind sir. I plan on giving this a spin tonight.
Ooking o walk a friend through this.later on tonight. And he camt boot into to the bootloader so im anxious to hear any feedback about this. If u guys dont mind please post anything you feel needs to be known about this, or just post that it rocks ass
Sent from my ADR6400L using XDA App
Hey guys, I didn't think about it when I created the thread but I want to have a bit of a poll here. If it works post here letting us know, and I'm fairly certain if there's a problem I'll hear about it so I don't think I need to say anything about posting them
Don't let dbzfanatic marginalize himself, don't forget some donations for him. (kinda hard to find his link in his post).
I hope it won't brick any phones. You're up on AP now - http://www.androidpolice.com/2011/0...en-tried-and-true-meets-new-and-blazing-fast/
I saw that. In my test group I had no reports of bricks, just random quirks which I have sense fixed (except those listed in the OP).
need to find an excuse to get off work early now...
Is firmware version the same as software number ? . My software number is 1.12.605.6 .
Yes it's the same, you should be fine to use this.
Looks awesome, but I'll still wait until all of the kinks have been worked out.
Since this uses the same method as manual root, it SHOULD continue to work until gingerbread.
awesome, cant wait to get outta work!
Does this wipe the phone like the manual adb does?
Yes, it's exactly the same method, just automated to make things easier.
BTW what do you mean "ADB needs to be setup as a system command"?
My ADB works properly and I can see the device so I assume that's the one I'd need to download and not the one that says "ADB need not be previously setup"?
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
UPDATED XOOM FLASHING GUIDE 02/02/12
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk
My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)
XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob
Thread moved to General.
This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general
This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down
Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse
kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.
Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"
first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
At which point do I back up data already on Xoom? Will there be any data loss?
Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.
gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
This may look complicated, but is super easy. If you don't feel comfortable using this method, you can use this automated tool (yes, it works on 4.5.141). It won't be as satisfying, or even feel good. You won't learn anything, but you will be rooted. Download tool here (link in OP is broken).
Pre-work:
1) Read the xda Atrix Beginners Guide (then read it again)! (Link)
2) Download and install 7zip. (Link)
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. (Link)
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
You can simply copy each command and paste in to the command prompt.
If you encounter any errors after entering a command, just ignore and keep going (assuming you entered the command properly).
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down until you see "fastboot".
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
17) Open a terminal emulator, then type "su" and hit enter. You should see "#" if you are rooted. Or, download Root Checker from the Play Store.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Note: If you experience problems with updating superuser after rooting, try going in to Manage Applications and clear Superuser data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Downloads:
My Atrix AFH Folder
*****
Thanksssss
Just want to show my appreciation. Your guide followed step by step worked flawlessly on my atrix. Ive been trying to root this darn thing for about a week and a half with no luck. found your guide and worked perfect first time around. Thanks..
David
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
upndwn4par said:
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
Remember to click THANKS if this guide helped you!
Pre-work:
1) Read the xda Atrix Noob Guide (then read it again)! Link
2) Download and install 7zip. Link
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. Link.
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down.
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Click to expand...
Click to collapse
RE super user pkg.
aksma said:
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
Click to expand...
Click to collapse
Well for me what happen is down at the bottom he has two links for two of the files you need to zip. in one of those, there is a superuser file. When doing the cmd commands at the end you will end up installing the superuser. The best thing to do which really helped me was to download the command prompt text file, that way you can mimic exactly what you see. Hope this helps.
-David
Thanks David, I just started doing the same. Lets see how it goes.
good luck
aksma said:
Thanks David, I just started doing the same. Lets see how it goes.
Click to expand...
Click to collapse
no problem. Believe me i was in the same position. I must of tried rooting mine like 15 times to no avail ,then i found this thread and it worked.
Worked like a Champ!! Thanks David... Was quick and easy.. ..
excellent
aksma said:
Worked like a Champ!! Thanks David... Was quick and easy.. ..
Click to expand...
Click to collapse
Good deal. So glad i found this thread haha.
Glad I could help!
good one.
Thanks a lot
was so expected that this guide
Going to give it a try
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Thanks!
Rooted phone
dmacdog said:
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Click to expand...
Click to collapse
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
thanks
that was cool!
very usefull!! thank you!
very useful
Sent from my MB860 using xda premium
condor7272 said:
that was cool!
Click to expand...
Click to collapse
Yes it is. Awesome feeling to look in your app drawer and see this:
THANKS!!
upndwn4par said:
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
Click to expand...
Click to collapse
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
1iJakk said:
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
Click to expand...
Click to collapse
Don't unlock your bootloader if you think you will want official Moto ICS update (major hard brick risk).