Related
I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.
This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.
I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.
NOTE: For those of you that are looking to root thier Inc and already have the latest 2.2+ OTA released in November, these steps will not work. Changes have been made to the ROM so until a new root application has been developed by the unrEVOked team, I am afraid you are left with a stock phone. Sorry. If new updates come out, I will try to post them here.
NOTE: I have uploaded the 2.1 and 2.2 RUUs to Rapidshare and updated the links.
First, let me say that I did not come up with this nor did I create any of the tools. I am passing all this on in a single thread to let people know how update thier Droid Incredible to the OTA 2.2 and have root access if they have it in any of the following conditions:
1. Stock 2.1 without root or unrEVOked Forever
2. Stock 2.1 with root and no unrEVOked Forever
3. Stock 2.1 with root and unrEVOked Forever
4. Stock 2.2 without root and with unrEVOked Forever
5. Stock 2.2 without root and no unrEVOked Forever
6. Custom ROM with root and S-OFF
7. Getting free WiFi Tethering on 2.2
8. Removing unwanted preloaded applications.
NOTE: This may work with custom ROMs, but I have not verified it.
NOTE: SOME PEOPLE, INCLUDING ME HAVE HAD THE PROBLEM OF BEING STUCK IN HBOOT AFTER LOADING A ROM IMAGE. IF THIS HAPPENS TO YOU AFTER LOADING THE 2.1 OR 2.2 ROM, DO NOT PANIC, JUST REAPPLY THE ROM AND ALL WILL BE FINE. FOR SOME REASON THE ROM DOES NOT LOAD CORRECTLY ON THE FIRST TRY BUT DOES ON THE SECOND.
I am passing this on because I loaded the OTA 2.2 without unrEVOked forever loaded on my phone. What a mess. I tried everything (I thought) to try and downgrade it back to stock 2.1 but with no luck. If you do not know, unrEVOked3 cannot currently root a 2.2 updated Droid Incredable and if you have not used unrEVOked forever, you can not get clockworkmod recovery to reload on the phone. I tried the 2.1 RUU to downgrade, but never could get it to connect to the phone. I then tried to use the 2.1 PB31IMG.zip to load and the HBoot loader would just tell me that it was an older image and not load it. I thought I was hosed until the unrEVOked team breaks the code on the 2.2 HBoot loader until I got pointed in the right direction (sort of).
TNS201 pointed me to the following thread: http://forum.xda-developers.com/showthread.php?t=768295
I gave this a try and still could not downgrade my phone. I searched around and after much trial and error, I was able to put together the correct steps to downgrade my phone and then applied unrEVOked3, unrEVOked forever, the OTA 2.2 update, and then reroot the phone. Anyway, here is what I have come up with:
** NOTE: THIS WILL TOTALY WIPE YOUR PHONE CLEAN!!! BACKUP ANYTHING YOU WANT BACK ON THE PHONE!!! **
Condition 1
1. Go to the following link and follow the instructions: http://forum.xda-developers.com/showthread.php?t=709220 Only do the steps for getting ADB loaded on your computer!
This will get ADB loaded on your computer which you will need when doing customizations to the phone. It will also walk you through rooting your phone and doing a lot of other things. Good thread for us noobs.
2. Download unrEVOked Forever from here: http://unrevoked.com/rootwiki/doku.php/public/forever
3. Copy the file to the root of your sdcard.
4. Reboot your phone into clockworkmod recovery and load the unrEVOked Forever zip file. This will turn S to off and allow unsigned images to be loaded.
When you reboot your phone, you will have a fully rooted and S-OFF stock 2.1 Droid Incredible.
NOTE: If you are having troubles downloading the OTA 2.2 RUU, use this link to download the ROM. Just delete the "_2.2" from the file name and go straight to step 12. http://rapidshare.com/files/418523008/PB31IMG_2.2.zip
To load 2.2, do the following:
5. Download the OTA 2.2 RUU from here: http://rapidshare.com/files/418527589/RUU_Incredible_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_1433.exe
6. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
7. Run the RUU and update your phone to 2.2. If the RUU updates your phone, go on to step 15. If the RUU will not connect to your phone Go to step 8.
8. Start the RUU.
9. Go to your computers temp directory and locate the folder that contains the file rom.zip.
10. Once you locate this file, copy it to any folder (or your desktop).
11. Rename rom.zip to PB31IMG.zip
12. Copy PB31IMG.zip to the root of your phones sdcard.
13. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip. This will take a while, so be patient.
14. Follow the instructions to have HBoot install PB31IMG.zip.
Whether you used the RUU or HBoot and PB31IMG.zip, at this point, you should have 2.2 loaded on your phone, but you will no longer have root. You will have S-OFF.
To regain root access, do the following:
15. Download clockworkmod recovery from here: http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
16. Download the payload update from here: http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
17. Download superuser from here: http://dl.dropbox.com/u/6408470/su-releases/su-2.3.4-ef-signed.zip
18. Copy all three files to the root of the phones sdcard.
19. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip.
20. Follow the instructions to have HBoot install PB31IMG.zip. Since the phone is still S-OFF, this will reload clockworkmod recovery on the phone.
21. Boot the phone into recovery and load the two zip files downloaded in steps 16 and 17. This will root the phone and reload superuser.
If all went well, when the phone reboots, it should now be loaded with 2.2 and have full root and S-OFF. Enjoy.
Condition 2
1. Do steps 2 through 21 under Condition 1.
Condition 3
1. Do steps 5 through 21 under Condition 1.
Condition 4
** NOTE: THIS ONE DOES NOT WIPE YOUR PHONE!! **
1. Do steps 15 through 21 under Condition 1.
Condition 5
This is a tuffer one and requires the phone to be downgraded to 2.1 before upgrading it back to 2.2. Anyway, here are the steps:
NOTE: YOU MUST USE THE 2.1 RUU I HAVE LINKED AND THE MTD0.IMG FILE I HAVE ATTACHED OR THIS MAY NOT WORK!!!
NOTE: If you are having troubles downloading the 2.1 RUU, use this link to download the ROM. Just delete the "_2.1" from the file name and go straight to step 5 after completing step 1 and 2 (skip step 3 and 4). http://rapidshare.com/files/418141003/PB31IMG_2.1.zip.html
1. Do steps 1 and 2 under Condition 1.
2. Download the attached zip file. It contains the files I had a hard time finding.
3. Download the 2.1 RUU file from here: http://rapidshare.com/files/418525132/RUU_Incredible_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_.exe
4. Follow steps 8 through 11 under condition 1 to get a good copy of the 2.1 ROM.
5. Copy the 2.1 ROM to the c:\android-sdk-windows\tools folder.
6. Unzip the files downloaded in step 2 to the c:\android-sdk-windows\tools folder.
7. Copy the unrevoked-forever.zip to the c:\android-sdk-windows\tools folder.
Note: At this point, you should have the following files copied to your c:\android-sdk-windows\tools folder:
PB31IMG.zip (this is the 2.1 ROM)
unrevoked-forever.zip (will set S-OFF)
rageagainstthecage-arm5.bin (this is a root exploit - gives you temperary root)
mtd0.img (need to research this one)
flash_image (this flashes images)
7. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
8. Open a command promt window and change to the c:\android-sdk-windows\tools folder.
9. Enter adb push unrevoked-forever.zip /sdcard/ and then press enter.
10. Enter adb push flash_image /data/local/ and then press enter.
11. Enter adb push rageagainstthecage-arm5.bin /data/local/tmp/ and then press enter.
12. Enter adb push mtd0.img /sdcard/ and then press enter.
13. Enter adb push PB31IMG.zip /sdcard/ and then press enter.
14. Enter adb shell and then press enter.
15. Enter cd /data/local/tmp/ and then press enter.
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
17. Enter cd /data/local/ and then press enter.
18. Enter chmod 777 /data/local/flash_image and then press enter.
19. Enter cd /data/local/tmp/ and then press enter.
20. Enter ./rageagainstthecage-arm5.bin and then press enter. You will now see some text on your cmd prompt screen explaining the exploit. Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
21. Enter adb shell and then press enter. You will see you now have a # instead of a $ prompt.
22. Enter cd /data/local and then press enter.
23. Enter ./flash_image misc /sdcard/mtd0.img and then press enter. This will flash your misc partition with Toast's mtd-eng.img and should return you to a # prompt.
24. Enter reboot bootloader and press enter.
25. HBoot will load. Select bootloader and HBoot will then load PB31IMG.zip.
26. Follow the instructions to have HBoot install PB31IMG.zip.
Once it is finished, select restart. You now are on the stock 2.1 build of Android. Now you can follow steps 3 through 21 under condition 1 and get your phone loaded back with 2.2 and have root and S-OFF.
Condition 6
1. Do steps 5 through 21 under Condition 1.
Condition 7
The following steps will allow you to use the 3G Mobile Hotspot that comes with the OTA 2.2 update and not have Verizon charge you for using it:
1. On your phone, bring up the dialer and dial ##778. This will load EPST.
2. Select EDIT.
3. Enter 000000 for the password.
4. Select SECURITY.
5. Select the username that has [email protected].
6. Edit the username to read [email protected] (delete "dun.").
7. Click the back button to return to the list.
8. Select M.IP DEFAULT PROFILE.
9. Repeat steps 5 and 6.
10. Click on MENU and select COMMIT.
At this point, your phone will reboot and you will be able to use the 3G Mobile Hotspot application to get free WiFi tethering. Enjoy.
Condition 8
I have so far found three options for removing the preloaded apps. They all require the phone to be rooted. Here they are:
1. The first way is to get Titanium Backup. You will also need to donate (as little as $3.99) to get full functionality of Titanium Backup, but it is well worth it. If you do not want to physically remove the application, you can use the FREEZE function and the application will be removed from the app list, but physically will still be on the phone. If you really want to get it off, you can uninstall and then deleted from the phone. All of this through a user interface that is pretty easy to use. By the way, it also does backups of apps and data.
2. Another option is to get Root Explorer. You have to pay for this one. It will let you mount the system folders on the phone as read/write and allow you to move and/or delete apps from the apps folder on the phone. This is a good app and worth having even if you do not use it to remove apps.
3. The final way is to use ADB and the command prompt to remove or move any application you do not want. This is tried and true, but combersome. You do not have to buy it, but there is no GUI to help you out.
My thanks to all the folks here on XDA that made it possible for us to release the possibilities of the Droid Incredable. As I stated above, I did not create the apps or the steps, I just put them together for others to use. I wish I could thank all the individuals that made this possible, but I did not get thier IDs, so in lew of an individual thank you, I am posting this group THANK YOU. Keep up the good work!
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Scblacksunshine said:
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Click to expand...
Click to collapse
No, in the case of having 2.2 already loaded and S-OFF, you are correct, the phone will not get wiped. The steps will root the phone and load superuser back on.
confirmation
Can anyone confirm option 4 working??
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
Those are steps I used to get root back on my phone after I update to 2.2. As I stated, I messed up the first time and did not load unrEVOked forever and could not root the phone, so I had to downgrade to 2.1 first and then go through the rooting process. That time I made sure to load unrEVOKED forever. After that, all went well.
Sent from my HTC Incredible.
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
also Im running Ubuntu 10.04 if that makes a difference
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
PimpShit420 said:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
Click to expand...
Click to collapse
I tried this and it did not work for me. It looked as if it did. It gave me the proper prompt, but on reboot, no root access. I had to use chmod 777 instead of chmod 0755.
PimpShit420 said:
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
Click to expand...
Click to collapse
I made a mistake, the line should have had 777 after chmod, not 0755. I have updated the instructions. If other individuals that use 0755 instead of 777 get the above to work, let me know. I do not know what the difference is. All I know is 0755 did not work for me. I had to use 777. I think I will do some research on chmod.
Hope other individuals find this helpful.
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
PimpShit420 said:
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
Click to expand...
Click to collapse
This is the problem I had. Try 777 instead of 0755 after each of the chmod commands. That is what worked for me.
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
chmod 0755 vs chmod 777
PimpShit420 said:
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
Click to expand...
Click to collapse
Well, I looked the chmod 777 and chmod 0755 commands up. Both commands change the read/write state for a file. 0755 changes the permissions for a specific group and user. 777 changes the permissions for everyone. You can find an explanation here: http://ss64.com/bash/chmod.html
0755 did not work for me, but 777 did. I am going to keep the instructions as they are unless I get feedback that 0755 is working for other people. If I do, I will add them as an alternative.
PimpShit420 said:
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
Click to expand...
Click to collapse
Are you using 777 for each chmod command?
Also, I was reading through the steps and found an error with step 16. It said the following:
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
It should have said this:
16. Enter chmod 777 /data/local/rageagainstthecage-arm5.bin and then press enter.
I have updated the steps on post 1.
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
BNG303 said:
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
Click to expand...
Click to collapse
Your welcome. I am glad it helped.
bagery77 said:
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Click to expand...
Click to collapse
Glad this helped. I wanted to give everyone a one stop shop for updating and root for 2.2. Also hoped everyone would not have to go though all that I did.
I've rooted then unrooted with super one click but still had superuser icon so I just dropped into trash. All was good then so I decided to uninstall/delete everything associated with root including going into astro and deleting (hope this isn't the downfall) clockwork folder holding backup... Now 1st time shutting down after doing all this last night then booting up this morning I'm still getting the clockworkmod recovery green screen to reboot system now. Only thing I can see left is in phone settings>applications>mng apps>all tab> is Terminal Emulator. So of course my ? is how the hell do I get rid of this?? Someone recommended reroot then delete logwrapper.bin to logwrapper. I really don't want to SBF flash so any other recommendations would be greatly appreciated.
Running OTA 2.2
i would sbf just to be safe man if you try deleting stuff and accidently delete something wrong it wouldnt be good and then you would have to sbf anyways so i say just sbf and start from a clean slate. besides that i got nothing!
Try the following:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Root Phone
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
GSBJackson said:
Try the following:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Root Phone
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
Click to expand...
Click to collapse
Does this work??
TheSwig said:
Does this work??
Click to expand...
Click to collapse
Yes, this will work.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
What can i use to do this? I dled terminal emulator but i cant get it root access for some reason, also tried sshdroid but i dont know how to connect to it from my mac....any help?
Nope, im not getting anything...i granted terminal emulator super user permissions and i tried it through sshdroid, but when i type mount -o .... all i get is the mount usage script...
I don't think he meant for you to use terminal emulator on your phone. Try using command prompt on a PC or terminal on a Mac.
Sent from my DROIDX using XDA App
dwray said:
I don't think he meant for you to use terminal emulator on your phone. Try using command prompt on a PC or terminal on a Mac.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yes, use a command prompt or terminal on Mac
GSBJackson said:
Try the following:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Root Phone
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
Click to expand...
Click to collapse
Welp...I tried this...guess what...stuck in a boot loop. Any suggestions?
I have the r2d2 droid 2. I suppose I'll have to SBF it...I'm looking for the file now (if it's even available.)
osufans said:
Welp...I tried this...guess what...stuck in a boot loop. Any suggestions?
I have the r2d2 droid 2. I suppose I'll have to SBF it...I'm looking for the file now (if it's even available.)
Click to expand...
Click to collapse
Yes there should be one you can find on mydroidworld I believe
Sent from my DROIDX using XDA App
SBF is the way to go
I'm usually over at android forums but I recently got Fission and realized I should venture over to here. I installed Fission and I tried the google youtube app and hate it. I was wondering if anyone could guide me on installing the stock app. And because im new, I'm not sure if this is the section to post this thread.
apavolka said:
I'm usually over at android forums but I recently got Fission and realized I should venture over to here. I installed Fission and I tried the google youtube app and hate it. I was wondering if anyone could guide me on installing the stock app. And because im new, I'm not sure if this is the section to post this thread.
Click to expand...
Click to collapse
attached is an older version of youtube, but still stock.
To have used the following method with re-installing the stock facebook apk, but I recommend that you take a nandroid backup before attempting anything
Save the .apk to your sdk\tools folder.
Open up 2 command prompt windows.
In the first do the following (with the phone connected via Charge Only mode for usb connection):
1) type: adb shell (press enter)
2) type: su (press enter)
3) type: mount -o rw,remount /dev/block/mtdblock4 /system
Switch to the second command prompt window
Change directory to your sdk\tools folder where you should have saved the .apk file
1) type: adb push Facebook.apk /system/app/Facebook.apk (press enter)
Switch back to the first command prompt
4) type: cd /system/app (press enter)
5) type: chmod 644 Facebook.apk
6) type: exit (press enter. you made need to do this 2x to get back to the regular command prompt.
when back at the regular command prompt
7) type: adb remount (press enter. This will remount the system partition as read-only)
8) type: adb reboot (press enter. This will reboot your phone. When it reboots, the youtube app should be reinstalled as a system application.
NOTE: i take no responsibility for any damage this may cause. I have not tested this method on a custom ROM, only on my own device when I have removed applications from the default 2.3.15 OTA.
I decided to put together a nice, straightforward tutorial on how to root and unlock your device. I have recently joined the Android scene myself, and the XDA forums have been invaluable to my learning process. I did hit a few brick walls in the process (and nearly bricked my phone as well) before I finally achieved a 100% working, rooted, unlocked ROM installation. So, I just wanted to put together a short, easy to follow guide on rooting and unlocking, which will (hopefully) avoid you extra time / headache.
Note: It is quite possible (though not certain) that you may lose your current data after the unlock process, so make sure to make a backup before you proceed.
Pre-Requisites:
- Atrix 4G (AT&T)
- Any firmware up to 4.5.91 (which is currently the latest official - as of 8/4/11)
- A Windows PC
- Current Motorola drivers for your device installed on your PC
Required Files:
Android Root and Unlock (2011-08-04).zip
This archive contains Fastboot, ADB, Tenfar's ClockWorkMod, Pudding (v2), and RSD Lite 5.3.1 (which is all you'll need). I put it together into one package to save you a bit of time, but all the credit goes to the original devs / creators.
Step 1 - Unlock the Bootloader
Extract the provided archive into a folder on your PC. Let's assume this is "C:\Atrix\".
Install RSD Lite 5.3.1 program on your Windows machine.
Make sure the latest Motorola USB drivers for your Atrix are installed on your PC.
Run the RSD Lite program on your PC.
Power down your Atrix and connect to your PC via USB.
Power on your Atrix, and immediately hold the Volume Down button until you see a menu pop up. This will be a text menu which will appear at the top of your screen, and the first option you'll see will be "Fastboot". Cycle the menu by pressing the Volume Down button until you get to the "RSD" menu option. Press the Volume Up button to launch the RSD support on your Atrix.
You should now see the phone appear in the RSD Lite program interface on your PC (in the bottom menu). Click on it. You should see some data about your Atrix appear in the Device Properties pane.
Hit the "..." button in the RSD Lite program to bring up the file menu and select the "4547-fix-try2.sbf" (included in the archive above). This is Pudding. It will unlock your Atrix in just a moment.
Hit the "Start" button. RSD Lite will flash your phone. This process will be fairly quick, and your Atrix will reboot once or twice. After your Atrix boots back into Android, power down your phone and close the RSD Lite program on your PC (ignore the warning... the process is complete... if it wasn't complete, you would not be able to boot up into Android).
Power down your Atrix once again. Leave it connected to your PC via USB. Power it on again and hold the Volume Down key to get to the boot menu (as before). This time, select the "Fastboot" option by pressing the Volume Up button.
Open up the Command Prompt on your PC (Run 'cmd', or browse for it in your 'Accessories' application menu) and go to C:\Atrix\ (or the directory where you extracted the provided archive).
Type in the following command:
fastboot oem unlock
You will see a message pop up with a warning about unlocking your device. Assuming you are here, you don't care about this, so just make note of the device id that the message provides.
Type in the command again, this time with the device id:
fastboot oem unlock ### ,
where ### is the device id you noted above.
Type:
fastboot reboot
That's it! Your device now has an unlocked bootloader.
Step 2 - Flash the ClockWorkMod
ClockWorkMod ("CWM") will allow you to make backups of your current system, as well as install mods and ROMs.
Reboot your Atrix.
Hold the Volume Down button as the device powers up to get to the boot menu. (You should be familiar with this by now.)
Select the "Fastboot" option from the menu by pushing the Volume Up button.
Type the following command from the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or the directory where you extracted the provided archive):
fastboot flash recovery recovery-en-goapk-0630-1029.img
Type into the command prompt:
fastboot reboot
You're done. You will now be able to launch CWM from the boot menu by selecting the "Android Recovery" option. Again, the boot menu cycles with the Volume Down key, and you make a selection with the Volume Up key. If you selected the wrong option, just pull your battery and try again.
Step 3 - Root Your Device
Rooting will give you the "Superuser" program in Android and allow you to provide superuser permissions to apps.
Reboot your device. As it powers on, hold the Volume Down button to get into the boot menu. Select the "Fastboot" menu option using the Volume Up key.
Type the following commands into the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or where you extracted the provided archive):
fastboot flash preinstall preinstall.img
fastboot reboot
Wait until your device boots fully into Android.
On the command prompt on your PC, type in the following commands, sequentially (executing each one-by-one, i.e., hitting the enter key after each):
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Done! You should now see the "Superuser" program as one of your Android's apps.
You are now unlocked, rooted and have CWM installed! You are ready to mod / ROM your Atrix.
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
antoniolcrd said:
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
Click to expand...
Click to collapse
Keep typing commands. It'll look like an error but keep going.
Sent from my MB860 using XDA App
Maybe out of luck...
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
This is one of the most n00b friendly guides I ever read. I can picture each step in my head as I read the instructions.
EDIT: This can go either way. I find it easier just to flash a ROM that's pre-rooted after unlocking the BL and installing CWM when it comes to step 3.
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
antoniolcrd said:
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
Click to expand...
Click to collapse
No way.
Nickel3ack said:
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
Click to expand...
Click to collapse
I´ve tried this command also. Pls check:
C:\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount/system -o remount,rw
/bin/mount/system -o remount,rw
bash: /bin/mount/system: Not a directory
[email protected]:/# cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: cannot create '/system/bin/su': Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Holy Crap I Think I'm Bricked
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Don't Panic
sonnyjame5902 said:
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Click to expand...
Click to collapse
No... don't worry. It's not a brick. Worst case you can restore the stock ROM.
1st Thing to try:
Basically, just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Before it can go to RSD, press the Volume Down key to get to Fastboot. Press Volume Up to get into Fastboot. Continue with steps 11-15. If this unlocks the bootrom, your error should disappear and you'll have your fully functional Android back.
2nd thing to try:
Just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Let the phone go into RSD. Go back to the RSD Lite program on your PC and repeat the Unlock process. Hopefully this time it will work.
3rd thing to try:
If not.... go to the Firmwares Superthread here on XDA and download the ROM appropriate for your carrier. Flash it onto your device via RSD (same method for flashing as above, except select the SBF you downloaded from the thread). This will get your device back into operation at least (you will lose all your data tho, so I'd try the other 2 methods first).
Friggin Cheers Mate! Got it all set up with option 2, and now I'm rooted and SU! And they said it couldn't be done after the Gingerbread OTA update! Bollocks!
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Dell2 said:
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Click to expand...
Click to collapse
The method for CWM described here is to flash the CWM directly to your recovery partition. All it needs is for the device to have an unlocked bootloader. You don't need to be rooted for this. Rooting only affects the way your Android OS permissions apps. You'll definitely need to be rooted to install CWM via ROM Manager or Titanium Backup. This is not that method.
can i just root with step 3 or do i have to unlock first?
Just out of curiosity I see in the OP that this should not affect data - what evidence is there of this being the case with 4.5.91 OTA?
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Nickel3ack said:
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Click to expand...
Click to collapse
This is just the first time I've read about being able to work on 4.5.91 without wiping the user data, so I was curious how this method differed from the others that were out there (mrramirezusa and the original pudding). Thanks for the info.
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
im getting error when i click start button it gives error of failed flashing
jeffhwitz said:
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
Click to expand...
Click to collapse
For RSD, none.
EDIT
Now having done this I can say it doesn't make any difference because this is all done outside of the Android Operating System.
Well, I did it and I did irritatingly lose everything in my /data. Luckily I've got everything backed up. Came from the 4.5.91 OTA and other than rooted was totally stock. Did give me a failed to boot 0x1000, pulled batt, restarted and did fastboot, did the unlock successfully (i.e. didn't flash any additional files so per the posts no reason I should have lost everything but I still did).
So, it does seem like more often than not doing this from the real actual unmodified OTA will cause a loss of user data as has been stated even though sometimes it doesn't seem to.