Related
Hi everyone,
I picked up a Droid X a few days ago and I have been looking into modifying it ever since. So far I have successfully Rooted, De-Odex'd, and installed custom themes. Being new to the android platform, it has taken some time to learn and there is still more to know. I have started to piece together a guide and I am looking for some input from the community to correct/add/remove tips/tricks/tools/etc as needed.
Please take the time to review and let me know what you thoughts are. Let me know what you encountered when trying to do a specific task. For us n00b's out there, let me know what you were unsure of and how you resolved the issue. My goal is to make one source for the Droid X that gets rid of most confusion.
Look forward to your input.
Thanks!
Update 10/26/2010: Guide Complete, still open for suggestions, just PM me.
Updated attached guide and also posted to wiki.
RLM703 said:
Hi everyone,
I picked up a Droid X a few days ago and I have been looking into modifying it ever since. So far I have successfully Rooted, De-Odex'd, and installed custom themes. Being new to the android platform, it has taken some time to learn and there is still more to know. I have started to piece together a guide and I am looking for some input from the community to correct/add/remove tips/tricks/tools/etc as needed.
Please take the time to review and let me know what you thoughts are. Let me know what you encountered when trying to do a specific task. For us n00b's out there, let me know what you were unsure of and how you resolved the issue. My goal is to make one source for the Droid X that gets rid of most confusion.
Look forward to your input.
Thanks!
Click to expand...
Click to collapse
Looks like you put a lot of time/effort into this.
How about integrating that info into the wiki?
http://forum.xda-developers.com/wiki/index.php?title=File:Motorola_Droid_X.png
Nice work! +1 on zaphod's sug. ping me if you need any help!
Will do, I have some more work I'd like to do on it though. Thanks for the tips and support
Dude...seriously...THANK you. Step-by-step directions are great when you only have a vaguely general idea of what you're supposed to be doing (that's what happens when you still haven't tried to learn though, so it's kinda my fault...).
Hey- this is awesome. Keep up the good work. Don't forget- now that we can overclock - those will be useful instructions since they are pretty confusing for noobs right now.
nice work!
Thanks for taking the time to write this up for all of us trying to hack our Droid X's.
nice guide, i didnt realize the recovery mod was so easy until i read this. nice to have a backup now.
Does anyone have anytips on getting this root to work. Ive installed the drivers and followed the instructions on the guide but for some reason when i hit the root button it gets hung up halfway through it. Then it can find my DroidX. help plzz
Thanks in advance
hadog32 said:
Does anyone have anytips on getting this root to work. Ive installed the drivers and followed the instructions on the guide but for some reason when i hit the root button it gets hung up halfway through it. Then it can find my DroidX. help plzz
Thanks in advance
Click to expand...
Click to collapse
Guide is a bit out dated. A much easier root method is z4root. apk and support page below:
http://forum.xda-developers.com/showthread.php?t=833953
1. Download .apk, copy to SD card.
2. Enable "Unknown sources" (Settings => Applications => check "Unknown sources"
3. Use file manager to navigate to file on SD card, install. I recommend rebooting before install and again after install, prior to running root command from within z4root. <= may help the process run smoother.
4. Open z4root, tap Permanent Root, let it run, once complete your device should restart and you would then be rooted.
Next step, installing ROM's. Many great ROM's out there, I highly recommend Liberty.
Hi, I am looking to root my MT4G.. but I always see "root at your own risk" etc... Well, I am ready to root at my own risk, however I don't really know enough to want to attempt thsi yet.. so I am looking for a general thread explaining what this stuff is and how it is explained..(definitions for commonly used terms and acronyms..) someone please point me somewhere.... Thank you.
I have been looking for a thread that answers these questions I have and I haven't found one in about a week, so I posted this...however I literally just found one, that I think answers most of my questions @ http://forum.xda-developers.com/showthread.php?t=859446&highlight=guide sooo any MOD please close or delete my thread, and I am sorry for wasting your time.
I used grankin01's instructions...
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
I have rooted 3 MT4G's using the following guide by grankin01...
http://forum.xda-developers.com/showthread.php?t=834225
It really can't be any easier. I started out on a G1 and rooting was not this easy back then. To paraphrase grankin01's instructions (please read his instructions carefully and do this at your own risk)...
1. Download and install VISIONary
2. Extract that root.rar file to your sdcard. This is where a lot of people got messed up. There's a 'root' folder within a 'root' folder 'cause the person who originally .RAR'd these files, RAR'd a 'root' folder. Basically, when all is said and done, you should have a folder named 'root' on your SD Card. Within the 'root' folder, will be 3 files - hboot_dhd.nb0, Root.sh & wpx.ko.
3. Run VISIONary and click Temproot now - you now have temporary root access
4. Download and run Terminal Emulator and execute the commands outlined in grankin01's post. You will be prompted to restart. Once your phone boots back up, run VISIONary again only this time, click Attempt permoot now. Your screen will go black and eventually, the phone will reboot.
On two occassions, when I was doing this on replacement MT4G's I received, I forgot to enable USB Debugging. I found that VISIONary would just spin its wheels at the Temproot portion. After rebooting the phone and trying again, VISIONary actually prompted with an error to let me know USB Debugging had to be enabled. Totally my fault, but the app just spins its wheels at first, so you don't really know what's up until you reboot and try again.
To recap:
- VISIONary temproot
- Commands outlined in grankin01's post
- VISIONary permroot
It really is quite easy to do! If anything, there are plenty of redundant posts that explain how to get root access. I hope my info above doesn't add to the mire.
shlongwoodian said:
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
Click to expand...
Click to collapse
I think that is why I posted this... Because I have been searching but I don't know what exactly to search for, or what step to do such thinigs in...I appreciate the help. I am currently following the s=off perma root guide, however I am struggling at getting my ADB drivers installed correctly....sooo I have some tinkering to do but I am looking forward to rooting my phone, and I don't even know what that is gonna open up..CANT WAIT!!!
EDIT: I checked out your link, and I am using a guide written by him, i believe, but it is the one that is a little more complex, and causes a deeper perma root...
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
grankin01 said:
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
Click to expand...
Click to collapse
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Jaskwith said:
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, I had to install it for adb to work on my windows installation and it has saved several other people heartache too.
Ughhhh.. just found out I work at job #2 tonight...how FREAKING lame...like I wasted ALL my freetime not being able to figure it out last night and now that I think I know what to do... I have NO time...BLAH!!
Okay, so my ADB **** is still not working... I don't know why.. I am following the guide over at theunlockr.com and it still won't work.. I installed the SDK from google... I didnt DL the archives however... and then I installed the drivers off my SD card onto my computer, and when I open the Command prompt and type cd\ cd AndroidSDK\tools\ it says the directory does not exist... it says on the unlocr guide to try installing PDAneT and that might help, and so i did that as well, still says directory does not exist...ARGH this is frustrating!
Do you need perma root to boot into recovery?
I would just follow the visionary method so you won't even have to bother with adb. Just use root explorer to copy and past the files into the right directory. Did it on the bus, took me 5 minutes. No need to get true/deep root especially for someone just starting off. I promise, for all you'll be doing (and a hell of a lot more) you'll NEVER know the difference. Just gives you more options to screw up your phone. Start with perm root (set up the easy way), flash a rom or two, mess around with some cool apps for root users, figure out adb, and then work your way up to messing with the deeper system stuff (if you still feel need).
Just my 2ยข
Sent from my HTC Glacier using XDA App
It sounds like you are looking in the wrong directory. Open your file browser and do a search for adb and pay attention to what folder it is in. My installation had like two subdirectories before I could even get to the tools directory on my windows drive.
That is if you still want to try adb. It is a valueable thing to learn. Espescially if your going to be doing these kinds of things to your devices. It can take a brick and turn it back into a phone if you know how to use it.
Thank you kind sirs you are very helpful to a pour nub such as myself...well it seems like I dont havr any freaking time ever so I think I might take c_licious's advice for now and read up on adb some more...i did see that in the thread its easy to convert from the perma root to the deep perma root so think that's what ill do. Thank you grankin for the tip on finding adb drivers that will definitely come in handy when I get to that. Yayyyyy!!!!
Sent from my HTC Glacier using XDA App
So I've poured over the potentially relevant threads and I haven't found anything about how to go about rooting the Tab on a Mac. I've rooted a Xoom on a Mac before, which was no problem using adb, but does adb recognize the Tab as a device (given the lack of Mac file reading compatibility otherwise) or is there another trick I'll need to know? Obviously at some point I'd need the new Kies for Mac, but is this all I'll need in order for adb to work? The only guides I've seen pertain to rooting through a PC, which is no help to me unfortunately. I don't have my Tab yet, but I was hoping to get a feel for what lies ahead once it arrives.
Please do not Post Questions in the Development forum thanks
lufc said:
Please do not Post Questions in the Development forum thanks
Click to expand...
Click to collapse
IT WAS A DEVELOPMENT (ROOTING) QUESTION, not a general question, so now its in a less appropriate place, but whatever
Anybody?
Regardless if it was a rooting question. Development forums are for development releases like kernels, roms, mod instructions. Questions are asked in the General forum.
As for your question:
In order to get a reliable root you must install CWM. In order to flash CWM you must use nvflash which is a windows command line tool. So there is currently no way to do this from a mac. TBH there may never be a way to do this from mac. I would suggest getting a copy of windows and use bootcamp as I have.
X10D3 said:
Regardless if it was a rooting question. Development forums are for development releases like kernels, roms, mod instructions. Questions are asked in the General forum.
As for your question:
In order to get a reliable root you must install CWM. In order to flash CWM you must use nvflash which is a windows command line tool. So there is currently no way to do this from a mac. TBH there may never be a way to do this from mac. I would suggest getting a copy of windows and use bootcamp as I have.
Click to expand...
Click to collapse
Well at this point I do have Parallels, so I'm guessing I should be able to use that as my means of installing CWM, as per the instructions found in the thread in the development section, yes?
Correct. But! I've tried this stuff before from parallels with limited to no success. You need to boot from windows(bootcamp). So that windows has full control of your hardware. I've never been able to get paralleled windows to see things right for this kind of stuff.
http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
That is the guide that you want to follow. Once your are done flashing CWM you can then just drop the busybox and root zips on your SD card like you normally would with your mac and flash with CWM.
X10D3 said:
Correct. But! I've tried this stuff before from parallels with limited to no success. You need to boot from windows(bootcamp). So that windows has full control of your hardware. I've never been able to get paralleled windows to see things right for this kind of stuff.
http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
That is the guide that you want to follow. Once your are done flashing CWM you can then just drop the busybox and root zips on your SD card like you normally would with your mac and flash with CWM.
Click to expand...
Click to collapse
Yeah but in order to do this wouldn't I have to have a copy of a Windows CD (which I have no access to)? And obviously I'm not about to drop $$$ on a damn Winblows CD just to be able to root. This seriously sucks.
Now I do have access to my work PC, which runs XP. Might you have a rough estimate on how long the steps in that guide would take, should I decide to try doing it here at the office?? I could of course get the files, drivers, etc all set up in advance, so take that part out of the equation. Just wondering on how long in terms of installing CWM; once I have that I can root at home later that night.
...and actually, once I get CWM installed on the 10.1 I should really have no need to connect to it for adb (or at least very very rarely) in the future, correct? I mean it seems like the main hump to get over for a Mac owner is to just get a custom recovery on the 10.1, and after that everything else is just all about flashing (from recovery that is). Would that be a fair statement??
It seriously took me like 10-15 min to run through the steps from none root to CMW, Busybox, and root. I did it at my desk at work eating lunch on my bootcamp Win7 x64.
Well, it seems that the new update (as mentioned in a previous thread), breaks the current root.
I was looking to see if anyone can provide a step by step tutorial on how to successfully install CM7 onto their Kindle Fire. I have tried in the past (few days ago really, but "past" sounds so cool to say), and it failed. Are there any tutorials, other than the original, that are easy to understand and help install CM7?
I'd greatly appreciate your help!
Background: Not a total newb on computers, but not a total vet using cmd and/or Android devices... I currently have 3-4 Apple devices with iOS and jailbroken. I am fairly comfortable with messing with my devices.
I'm a newbie to rooting and CM7 but I managed fine by following the main threads in the developers forum and the videos on kindlefirewire.com
Use the .zips and files contained in the main thread and make sure you follow those commands (I think they are the same, but just to be safe)
When you root, make sure you install BusyBox when SuperOneClick asks to - you will need it later. I didn't have the 'cp' command without it. So you might need to root again before installing CM7 just to make sure.
In the CM7 thread, follow the steps to install the google apps - it was a lot more effort to get the Market back on the KF without doing so (I had to push dropbox and ES Explorer to the device first).
Edit: I should note that I did all this with 6.2 before the 6.2.1 update came out. If you've got the new update in your KF I would wait until a workable root solution is found.
Here follow this guide
http://liliputing.com/2011/12/amazon-releases-kindle-fire-6-2-1-software-breaks-root.html
Thanks a lot for both of your helps!
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8