HowTo: Root your Motorola Droid X2 - UPDATED [14DEC2011] - Motorola Droid X2

Moon Shadow's Droid X2 Tutorials - HowTo: Root your Motorola Droid X2
Please keep in mind that this tutorial is specifically for the Motorola Droid X2 running any version of Gingerbread 2.3.4 and below. This procedure MIGHT work for other phones, however, I would not recommend taking the risk of bricking, or even soft bricking, your phone.
Standard disclaimer: I, nor XDA Forums, are responsible for what you do to your phone. Just because these tutorials work for me, does not mean that they will work for you.
I make no claims to be the original owner of this process. I am just consolidating the process into an easy to follow (hopefully) guide that will help everyone from noobs to experienced users.
This tutorial has been adapted from the post: [16/Nov][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v3.0](zergRush Exploit by DooMLoRD.
Unrooting is covered at the end of this post.
This method uses Windows! (I know, I'm a Linux guy, but...) If you have a Mac or a Linux box, use Pete's One Click Root for Linux and OSX - Droid 3. I have not tried it as my Linux system crashed several months ago and I do not have the funds to purchase new hardware or fix it. I can try to assist as I am a mixed environment System Administrator, however, I make absolutely no claims of being a guru. I have heard (not substantiated) that people are having success using Virtual Box. I highly recommend Virtual Box as it seems to be the only free virtualizing environment that supports accessing hardware directly, as long as Linux sees the hardware, Virtual Box and use it (for the most part).
I am making some assumptions in this tutorial:
1. You understand and are comfortable with installing software on a Windows computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. You understand and are comfortable with downloading programs.
3. You understand and are comfortable with extracting compressed files (*.zip, *.rar *.7z, etc.) (I recommend 7zip to extract all compress files.)
4. You are willing to read this entire tutorial and ask questions if something is unclear to you, BEFORE you start this process. (Better to be safe than sorry.)
Now, on to the good stuff…
Hints:
Text in green are applications to launch or buttons to push within an application.
Text in red are warnings.
Orange is reserved for text that must be typed or copied. – Specific commands are also listed in code boxes.
This process is for Gingerbread (2.3.x) ONLY! For the Froyo gingerbreak, see booked's thread: [REF] Roms, Root, SBF, RSD, Bootstrap, Mods.
I have performed this method for rooting my Droid X2 from both Windows XP (SP3) and Windows 7 Professional x64. After a system boot file (SBF) restore of 2.3.4. Tutorial on SBF is here: Moon Shadow's Droid X2 Tutorials - How to perform an SBF of your Motorola Droid X2.
1. First download the correct Motorola driver for your Windows system:
a. Windows universal 32-bit Motorola drivers version 5.2.0
b. Windows universal 64-bit Motorola drivers version 5.2.0
2. Next download DooMLoRD's ROOT-zergRush: DooMLoRD_v4_ROOT-zergRush-busybox-su.zip (Older version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip).
3. Install the correct driver and reboot.
4. Once the computer comes back up, extract DooMLoRD_v4_ROOT-zergRush-busybox-su.zip.
5. Make sure USB Debugging is enabled on your device. This can be accessed by hitting the Menu key and navigating to: Settings -> Applications -> Development and making sure there is a check mark in the box next to USB Debugging.
6. Plug the USB cable into your phone and computer.
7. Make sure your phone is in “Charge Only” mode:
a. Drag the Pull Down Menu down
b. Tap “USB Connection”
c. Select “Charge Only” mode
d. Click OK
8. From the new folder you created, launch runme.bat.
9. A command prompt window will open, make sure the phone is plugged into computer via the USB cable and press any key.
10. zergRUSH will reboot your phone once it is done. Watch for errors. If there are none, you will be rooted. If there are errors, try re-running zergRUSH again.
11. Once your phone is rooted, open the market and upgrade Superuser and Busybox. Busybox can be upgraded via the app from Stephen (Stericson) or JRummy16. Please, if you use these tools, purchase the Pro versions. This helps support our developers! Thanks!
People have asked about un-rooting their DX2. Here is what I posted in another topic:
I do not know about unrooting using Pete's tool. I haven't tried it. (But ashclepdia says it works just fine.)
There are two options that I know of to unroot your Droid X2. They are:
1. If you already have root privileges (and root/su works), using a root enabled explorer (I use File Expert) mount the /system folder in read/write (rw) mode and delete the following 3 files:
a. /system/xbin/busybox
b. /system/xbin/su
c. /system/app/Superuser.apk
OR
In the adb shell, type the following:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/xbin/busybox
rm /system/xbin/su
rm /system/app/Superuser.apk
reboot
(The reboot command will reboot your phone. If you are not done working with your phone or in the adb shell, just type exit, or keep working with ADB.)
2. The easiest, don't screw up your phone, put it back to "as stock as the day you got it", way is to do a data wipe and SBF. Performing a SBF restore is not difficult at all. See my tutorial: Moon Shadow's Droid X2 Tutorials - How to perform an SBF of your Motorola Droid X2.
Click to expand...
Click to collapse
Old rooting method (depricated but left in for information):
This tutorial has been adapted from the post: [Gingerbread Root] Pete's Motorola Root Tools by infazzdar who reposted from the original post from Pete Souza at http://www.psouza4.com/Bionic/.
This method uses Windows! (I know, I'm a Linux guy, but...) If you have a Mac or a Linux box, Pete posted this:One Click Root for Linux and OSX - Droid 3. I have not tried it as my Linux system crashed several months ago and I do not have the funds to purchase new hardware. I can try to assist as I am a mixed environment System Administrator, however, I make absolutely no claims of being a guru. I have heard (not substantiated) that people are having success using Virtual Box. I highly recommend Virtual Box as it seems to be the only free virtualizing environment that supports accessing hardware directly, as long as Linux sees the hardware, Virtual Box and use it (for the most part).
I am making some assumptions in this tutorial:
1. You understand and are comfortable with installing software on a Windows computer.
2. You understand and are comfortable with downloading programs.
3. You understand and are comfortable with extracting compressed files (*.zip, *.rar *.7z, etc.) (I recommend 7zip to extract all compress files.)
4. You are willing to read this entire tutorial and ask questions if something is unclear to you, BEFORE you start this process. (Better to be safe than sorry.)
Now, on to the good stuff…
Hints:
Text in green are applications to launch or buttons to push within an application.
Text in red are warnings.
Orange is reserved for text that must be typed or copied. – Specific commands are also listed in code boxes.
This process is for Gingerbread 2.3.3 and 2.3.4 ONLY! For the Froyo gingerbreak, see booked's thread: [REF] Roms, Root, SBF, RSD, Bootstrap, Mods.
I have performed this method for rooting my Droid X2 from both Windows XP (SP3) and Windows 7 Professional x64. Both on the initial 2.3.3 Gingerbread load when I received my phone, on the 2.3.4 Gingerbread over the air (OTA) update, and after a system boot file (SBF) restore. Tutorial on SBF is here: Moon Shadow's Droid X2 Tutorials - How to perform an SBF of your Motorola Droid X2.
1. First download the correct Motorola driver for your Windows system:
a. Windows universal 32-bit Motorola drivers version 5.2.0
b. Windows universal 64-bit Motorola drivers version 5.2.0
2. Next download Pete’s Motorola Root Tools: PetesMotorolaRootTools_v1.07.zip
The program still say's "This is version 1.06 of this tool, by Peter Souza IV. Exploit by Dan Rosenberg." What was updated was the version of su and busybox.
3. Install the correct driver and reboot.
4. Once the computer comes back up, extract PetesMotorolaRootTools_v1.07.zip.
5. Make sure USB Debugging is enabled on your device. This can be accessed by hitting the Menu key and navigating to: Settings -> Applications -> Development and making sure there is a check mark in the box next to USB Debugging.
6. Plug the USB cable into your phone and computer.
7. Make sure your phone is in “Charge Only” mode:
a. Drag the Pull Down Menu down
b. Tap “USB Connection”
c. Select “Charge Only” mode
d. Click OK
8. From the new folder you created, launch Pete's Motorola Root Tools.exe.
9. Click the Root My Phone button.
10. Pete’s Motorola Root Tools will reboot your phone a total of three times. At the end of the last reboot, Pete’s Motorola Root Tools SHOULD tell you that your phone has been rooted successfully. If it does not, follow the steps in the next section. (I had to do this after one SBF.)
11. Once Pete's Motorola Root Tools tells you your phone is rooted successfully, open the market and upgrade Superuser and Busybox. Busybox can be upgraded via the app from Stephen (Stericson) or JRummy16. Please, if you use these tools, purchase the Pro versions. This helps support our developers! Thanks!
Manual root:
If the preceding steps did not root your phone, follow these manual steps (it's kind of ugly, but it works). This process will install the Android Debug Bridge (ADB) and the Android Standard Development Kit (SDK). For a specific and customized HowTo on ADB Visit the [HOW-TO] ADB for Dummies(How-To Learner's Guide) post on XDA by VanillaTbone and download either the ADB for Dummies Guide or ADB for Dummies AIO(All In One) App by AndroidSamurai. (I think both VanillaTbone and AndroidSamurai are two different people, but I’m not sure. If anyone can clarify that would be great. Thanks!) Please keep in mind that these manual steps are specifically for the Motorola Droid X2. They might work on other phones, however, I take no responsibility for you bricking or soft bricking your phone by trying this.
1. Download and install the latest Java Development Kit (JDK) from Oracle. (As of this writing, 22OCT2011, Java SE Development Kit 7u1 is the most current version. PM me if there is a newer version so I can update this.)
2. Download and install and configure the latest Android SDK from Google. Once installing the Android SDK, launch SDK Manager and download and install the "SDK Platform-tools". (As of this writing, installer_r14-windows.exe is the most current version. PM me if there is a newer version so I can update this.)
3. For Windows XP and Windos 7 32-bit (i686), add the following to your path statement: C:\Program Files\Android\android-sdk\platform-tools. For Windows 7 64-bit (x86_64), add the following to your path statement: C:\Program Files (x86)\Android\android-sdk\platform-tools. The path statement is located by right clicking My Computer in Windows XP or Computer in Windows 7 and selecting Properties -> Advanced -> Environment Variables and locate PATH under System Variables. Double click the line and add a semicolon to the end, if there is not one there and copy and paste the above line to the end.
4. Reboot your computer.
5. Download DROID 3 easy root script v7.zip.
6. If the following folder does not exsist, create it: C:\TEMP
7. Then create a folder in C:\TEMP called MANUAL_ROOT
8. Extract the Droid 3 easy root script v7.zip into the C:\TEMP\MANUAL_ROOT folder.
9. Once you have rebooted your computer, open a command prompt. Yeah, you know, one of those DOS things… ADB is an Android tool, and Android is a fork of Linux. Get used to it. A bunch of typing is in your future, plus it’s good for you.
10. Type the following command:
Code:
adb shell
11. You should receive an ADB prompt ending with either a # or a $.
12. If the line ends with a $, then run Pete’s Motorola Root Tools.exe.
13. Click the Run Temp. ADB Root Procedure button.
14. The program reboots your phone three times, I think… Hey, I’m an old guy and my memory is failing me. Okay, maybe not that old, but that is my excuse!
15. Once the process is complete, enter the following command:
Code:
adb shell
16. You should now have and adb shell ending with a #. If not, reboot your computer and Droid X2 and start again at step 13.
17. Type the following command: (This remounts the /system directory on the Droid X2 as read/write, because the partition is mounted read only.)
Code:
mount -o remount,rw /dev/block/system /system
18. Type exit until you are back to the DOS C:\> prompt, then type the following: (The first changes directory to the C:\TEMP\MANUAL_ROOT directory, the push commands push the required files for su, busybox and the Superuser.apk app to the Droid X2, the shell commands set the read/write/execute (rwx) permissions on su and busybox and changes the owner and group on the /data folder to system, the reboot command reboots your phone.)
Code:
CD \temp\manual_root
adb push busybox /system/xbin/busybox
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
adb shell chown system.system /data
adb shell reboot
19. It may take quite a while (5-10 minutes) for your phone to come back up to the home launcher. Sit, relax, or better yet, walk away from your computer.
20. Once the phone has booted, open the market and upgrade Superuser and Busybox. Busybox can be upgraded via the app from Stephen (Stericson) or JRummy16. Please, if you use these tools, purchase the Pro versions. This helps support our developers! Thanks!
21. This concludes the tutorial for rooting your Motorola Droid X2.
Again, if you have any questions, or comments, either post them here, or PM me! Thanks all!
Ciao!

Very nice!
Sent from my DROID X2 using xda premium

Great write up, hope this helps the new guys!

THANK YOU!! FINALLY someone got this together.
Now maybe I can stop defending noobs hahahaba.
This is great. Very nice job. I even enjoyed just reading it even though I am already rooted and all that jazz. This is very accurate and very well written. Thanks for ur time. Great job.

question...how easy is it to unroot? like if i need to get my x2 warrantied for any reason. will i have to go through the whole SBF process?
Thanks

neiche said:
question...how easy is it to unroot? like if i need to get my x2 warrantied for any reason. will i have to go through the whole SBF process?
Thanks
Click to expand...
Click to collapse
As long as u made a nandroid right after rooting BEFORE doing any mods all u need to do is restore nandroid and use the one click root method again. But use it for unroot.
Personally tho I would just sbf and data wipe as that should get rid of ANY trace of root. And sbf isn't hard. It would take maybe 15 minutes longer than uprooting but u have the security of knowing it is back completely stock afterwards.
Have u done an sbf ever? U will be surprised at how simple it can be once u do it a couple times

neiche said:
question...how easy is it to unroot? like if i need to get my x2 warrantied for any reason. will i have to go through the whole SBF process?
Thanks
Click to expand...
Click to collapse
Sbf would be ur best bet. Just to make sure u remove everything (
Sent from my DROID X2 using xda premium

Sbf is the "save all" so far for x2. And it's really only like 5 simple steps once u have rsdlite and moto drivers installed

ashclepdia said:
Sbf is the "save all" so far for x2. And it's really only like 5 simple steps once u have rsdlite and moto drivers installed
Click to expand...
Click to collapse
I do not know about unrooting using Pete's tool. I haven't tried it. There are two options that I know of to unroot your Droid X2. They are:
1. Using a root enabled explorer, I use File Expert, mount the /system folder in read/write (rw) mode by typing this:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
and delete the following 3 files:
a. /system/xbin/busybox
b. /system/xbin/su
c. /system/app/Superuser.apk
2. The easiest, don't screw up your phone, put it back to "as stock as the day you got it", way is to do a data wipe and SBF. Performing a SBF restore is not difficult at all. See my tutorial: Moon Shadow's Droid X2 Tutorials - How to perform an SBF of your Motorola Droid X2.
Also, to everyone, I really appreciate the kind words. My intent it to help as much as possible, without being the complete techno-weenie that I am.

Moon Shadow - NM said:
I do not know about unrooting using Pete's tool. I haven't tried it. There are two options available to unroot. They are:
1. Using a root enabled explorer, I use File Expert, mount the /system folder in read/write (rw) mode and delete the floowing 3 files:
a. /system/xbin/busybox
b. /system/xbin/su
c. /system/app/Superuser.apk
2. The easiest, don't screw up your phone, put it back to "as stock as the day you got it", is to do a data wipe and SBF. Performing and SBF restore is not difficult at all and I will be publishing an SBF tutorial here, probably tomorrow.
Click to expand...
Click to collapse
Yup. That works also.
But I am also positive that the one click method has an option for unroot as I have seen AND uses the option
Edit:: by the way I want to say thanks again for writing this tutorial and in advance for the sbf tutorial.
this one is very complete and up to date and I look forward to reading ur sbf post.

This should be stickied, would save a lot of member headaches trying to find it to point newbs!

AtLemacks said:
This should be stickied, would save a lot of member headaches trying to find it to point newbs!
Click to expand...
Click to collapse
Thanks! Let the mod know... Infact, who is the mod for this forum?

Just an FYI for Windows 7 on the manual rooting method. The default directory the Android SDK installs to is Program Files (86x). In your direction it just says Program Files which would be correct for XP I believe. I had trouble running the Command Prompts because it wouldn't recognize any of the commands until I figured out it was because i put the wrong directory for the PATH for the commands.

Meticode said:
Just an FYI for Windows 7 on the manual rooting method. The default directory the Android SDK installs to is Program Files (86x). In your direction it just says Program Files which would be correct for XP I believe. I had trouble running the Command Prompts because it wouldn't recognize any of the commands until I figured out it was because i put the wrong directory for the PATH for the commands.
Click to expand...
Click to collapse
Ahhhh! Thanks! I did forget that! Thanks for the catch! Tutorial has been updated!
Sent from my rooted, deodexed, personalized, stock rom, Motorola Droid X2. What's with the locked bootloader Moto????

Moon Shadow - NM said:
Thanks! Let the mod know... Infact, who is the mod for this forum?
Click to expand...
Click to collapse

arrrghhh said:
Click to expand...
Click to collapse
Thanks arrrghhh!
Moonshadow also has a tutorial for bootstrap and sbf that would make GREAT stickies if u wouldn't mind

ashclepdia said:
Thanks arrrghhh!
Moonshadow also has a tutorial for bootstrap and sbf that would make GREAT stickies if u wouldn't mind
Click to expand...
Click to collapse
Heh, ok. Went a little crazy with the sticky threads. Moon Shadow, might want to clean up the thread titles - just a thought. You pretty much own the sticky section now .

arrrghhh said:
Heh, ok. Went a little crazy with the sticky threads. Moon Shadow, might want to clean up the thread titles - just a thought. You pretty much own the sticky section now .
Click to expand...
Click to collapse
Ummmm, really? I own it? Hmmmmm...
Anyhow, I'll remove the self credit in the thread titles and make them specific.

Moon Shadow - NM said:
Ummmm, really? I own it? Hmmmmm....
Click to expand...
Click to collapse
Eh I was just teasing. You do have a lot of threads up thar tho .

Can somebody please help me? Running stock 2.3.4 and Windows 7 32-bit
The one click tool does not work for me. I followed the steps exactly but I get this:
"ERROR: adb could not be granted root access via local.prop method"
I tried doing it again and the same thing happened.
Then I followed the SBF tutorial, thinking that would help. I SBF'd and did a factory reset and tried the program again and it still did not work.
Then I tried doing the manual method and followed steps 1 through 4 (step 5 is missing?? or just numbered incorrectly?) and 6 through 11. When I type adb shell in the command prompt, I get " 'adb' is not recognized as an internal or external command, operable program or batch file." preventing me from moving forward with the rest of the steps. I have rebooted both my phone and my computer many times and reinstalled the drivers and everything.
If someone could please explain what I am doing wrong and help me root my phone, I would very much appreciate it. I've been trying for the past three hours now and am getting frustrated.
Thank you.

Related

[UTIL] New Root Method as of 8/13! -> UPDATED 12/30 for NOOBS! <-

Hello everyone!
You may or may not know me, however I have secretly been working behind the scenes with ChiefzReloaded to learn how Android works. Together we have been trying to develop new ways to root the Slide, primarily because we both landed in a sticky situation that left us both without root and without a way to revert to root.
After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
To get started, please see the bottom of this post for the link and download it. You will want to download it to your computer and not your phone's SD card. Also, you will need the tools from the Android SDK. I would suggest extracting the file from my zip at the bottom of this page into the Android SDK's tools directory.
Extract the zip
Make sure your phone is in USB debugging mode AND you are in "Charge Only" mode.
Connect your phone to your computer.
Make sure you're in the same directory as where exploid is extracted before continuing to the next step.
Issue the following command: adb push exploid /sqlite_stmt_journals. Note: It MUST be in that directory - NO exceptions.
Run: adb shell
Run: cd /sqlite_stmt_journals
Run: chmod 0755 exploid
Run: ./exploid
Toggle your phone's Wifi (on or off, however you wish to do that).
Now (again) run: ./exploid (if prompted for a password enter: secretlol)
The next line should now begin with a pound (#) - if not, then something isn't setup right. Make sure to follow the directions verbatim. If you suspect you did follow them correctly, please reply to this post letting me know.
You should now be root! At this point you can do many things, but if you're looking to flash a custom ROM, continue to these instructions:
[NEW 10/18/2010:]
Steps 1-12 are intended to get you the ability to flash mtd0.img (which previously required using the SimpleRoot method) by gaining root inside of Android. By following the instructions in the rest of this section, it will allow you to flash a ROM or S-OFF your device:
The files you need are at: http://forum.xda-developers.com/showthread.php?t=703076- download both files linked in there (ESPRIMG.zip and SlideEng-package.zip)
Extract the contents of SlideEng-package.zip to a place of your choosing on your computer.
Place the entire (unextracted) ESPRIMG.zip on your SDcard.
Now push the files 'flash_image' and 'mtd0.img' that you just extracted from SlideEng-package.zip to /data/local using 'adb push'. (Noob? Instead of using 'adb push', install Droid Explorer and, using that utility, copy the 'flash_image' and 'mtd0.img' files to /data/local on your Slide)
Now I'm going to assume your phone is at root prompt (#) using steps 1-12. So now do (without typing the '#' symbols in front of both lines - they're just there to remind you that you need to be at a '#' prompt):
Code:
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Before you reboot make sure that the ESPRIMG.zip is on your SDcard!
Now turn off the phone.
Then press Volume-Down + Power.
The phone will power on and after about 5 minutes of verifying ESPRIMG.zip it will ask you if you want to flash it.
Press Volume-Up for 'YES' and wait until it finishes (ABSOLUTELY DO NOT POWER DOWN WHILE IT'S STILL FLASHING!!!).
Now when you go into recovery it should allow you to 'Apply update.zip from sdcard' (booting into Clockwork). If you don't have the Clockwork update.zip, here it is: http://www.4shared.com/file/OTRU7T3y/update_2.html (rename to update.zip after downloading since it's currently update_2.zip, then place it on your sdcard).
[/NEW 10/18/2010]
[NEW 12/30/2010]
Optional: Now that you're rooted you might want to disable all flash memory protections so you can permanently flash Clockworkmod (recovery - no more using an update.zip!) as well as other random things. Check here for details: http://forum.xda-developers.com/showthread.php?t=798168
[/NEW 12/30/2010]
CREDIT GOES TO:
[*] ChiefzReloaded! (For helping me learn the intricacies of Android and patiently answering all of my questions)
[*] 743C (For developing the original exploit)
Source code: (Yes, it's hackish. I was just trying to figure out why the system kept rebooting and haven't cleaned up the code since) download
DOWNLOAD:
http://www.4shared.com/file/CZsxSq-f/exploid.html
DONATE:
(Anything helps!)
(Some people may wonder why this is special compared to the One Click Root application. What's important is that One Click Root doesn't work on Slides running production/retail software, likely the same problem I had to fix to get exploid to work in my version.)
Thats whats up!!
If you be trollin then YOU BES TRAWLLIN
But if not then good job nb!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
Sure, I was getting around to that - and I understand your concern. I'll post it in a second.
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Sent from my T-Mobile myTouch 3G Slide using XDA App
r0man said:
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Click to expand...
Click to collapse
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
nbetcher said:
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Click to expand...
Click to collapse
Ill take a look at it when I get home.
ilostchild said:
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
Click to expand...
Click to collapse
I actually had to do a lot of work on it. It doesn't quite work the same as the original exploid simply because the original exploid crashes the entire system and reboots. This causes the rootshell to never be committed to NAND and thus you get no where. I had to keep playing with things until I found a different method that works. It took several hours of me being upset with it, but watched the latest Burn Notice, came back to it, and BAM I had a stroke of genius.
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Armyjon88 said:
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Click to expand...
Click to collapse
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Sweet
Sent from my T-Mobile myTouch 3G Slide using XDA App
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
statuzz said:
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
Click to expand...
Click to collapse
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
nbetcher said:
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Click to expand...
Click to collapse
Let me know if you want to work together on some kind of one-click root app for the Slide. If the commands work through the terminal on the phone itself rather than via adb, I could probably make this into an app already, but since you're working on a more non-developer-friendly version, I'll just wait until that's out
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
I'm delaying the release of my non-developer program for another couple hours.
As far as what you said above, all you need to do after gaining the # prompt is (in a separate window):
adb push flash_image /data/local
adb push mtd0.img /data/local
(switch back to your # adb shell, then type
cd /data/local
chmod 04755 flash_image
./flash_image misc mtd0.img
Then reboot and apply the ESPRIMG.zip. All of these files are found on the same post that I referenced in my OP. These instructions are all in that same page.
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
Im also stuck since im not sure if you can update to eng from the ota..But first i want to personally thank the OP & CR for providing this.
This would be great for a One Click method
this would be nice to work into a one click root!
And This did work for me!
Does this root method gets /system moumted when android running?In short do we finaly get metamorph and root explorer working?

[Q] sbf_flash on mac

below is a short preface and introduction before the main point of this thread. you can skip the preface if you want.
PREFACE/INTRODUCTION
i am relatively new here. i owned a nexus one a year ago and sold it for an iPhone 4. left the iOS world and jumped over to the "fastest phone in the world" (GS2 doesn't count yet). had my device for 3 days and i love it. jailbreaking iOS was very easy for me and i am *somewhat* comfortable rooting and unlocking bootloaders on android. Nexus One was very easy from what I can remember. fastboot oem unlock i believe it was? CWM, flashing *.zips, etc. So I would like to think I am not a complete n00b, but when it comes to motorolas, i have no experience. i currently own a macbook pro as my main computer, however, i do have limited access to a notebook running vista. now to get to my point of this thread.
***************************************
MAIN POINT OF THREAD: sbf_flash tool
SBF_FLASH (Mac and Linux) executable for flashing *.sbf files to motorola android phones in lieu of RSDlite. **ATRIX is said to be supported
link: http: //blog.opticaldelusion.org/2011_04_01_archive.html (wouldn't let me post real link, sorry)
*note: originally the developer wrote separate scripts for linux and mac as mac uses mach-o executables while linux uses ELF, however, the updated version works on both linux and mac platforms.
i searched the forums and only found 4 posts related to the tool sbf_flash and none of them were related to the motorola atrix. therefore i felt compelled to write this post and see if anyone has used this tool. if you read my preface it stated that I have a mac and only limited access to a windows computer therefore . my main question is. has anyone used this tool to flash *.sbf files to their atrix? if so, were there any issues whatsoever?
**if no one has used this tool before, I will hold my breathe and take the plunge. I will gladly be the guinea pig for all you mac/linux users out there (mainly mac users as if I am not mistaken, linux users have someway of flashing *.sbf files?)
thank you for reading this post. if I do not receive any input in terms of user's experiences with this tool by July 12th 9:00PM (EST), I will attempt to use it and see what happens. very anxious to get the bootloader on my device unlocked and flash CWM and flash 2.3.4. but i will wait.
**EDIT: i am aware of the fact that I can use bootcamp, VMware, Parallels or essentially any Virtual Box to run Windows on my mac and use RSDlite, however, I feel that if a simple executable such as sbf_flash worked, if would save a ****load of time/frustration/hassles.
I have used it
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
ionstorm3 said:
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
Click to expand...
Click to collapse
I run windows 7 on ny mac so... yea
Sent from my MB860 using XDA Premium App
thanks for all the input (from both of you). im assuming if i cd into the directory where the sbf_flash file resides I don't need to include the path every time? i have some knowledge of C and limited C++ or object oriented programming knowledge as well. i would love to use your script that automates the entire procedure if you don't mind giving it to me. once again thanks for the advice.
correct me if i am wrong, but chmod -x essentially gives the file permission to execute? trying to remember all the different unix commands. sudo, cd, and ls are only ones i use on a consistent basis
I have realized that it is not necessary to chmod +x the script file. All you have to do is include a ./ in front of it. For example ./sbf_flash filename.sbf. Btw saw your guide on how to sbf flash under *nix, so not sure if this information is still useful to you.
oh and yes cd, sudo and ls are the commands to use on a constant basis.
hey guys, kinda new to linux and the atrix. running 10.04 im not sure if i have the sbf_flash.sh. i have a file that shows as a shell script, i hope thats right. anyway. i have followed the direction above and cant seem to get it to run. this is what i have.
sudo chmod +x /home/serooted/Desktop/sbf_flash.sh
I in return get.No such file or directory. any ideas that would get me rolling? really want to get rid of the "unlocked" from my moto splash screen
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
ionstorm3 said:
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
Click to expand...
Click to collapse
Yes the sbf_flash does show up in the output. so my question would be, how now do i get it to flash the file?
is there any way that someone can post a step-by-step guide to unlocking the bootloader for the mb860 running 4.5.91 on a mac as i don't have access to a pc and am un able to find a clear method to doing so. sorry I'm new to this :/

Droid X2 OTA Gingerbread Root Guide

Droid X2 Gingerbread Root Guide
"One Click" method now available, see MikeJ92YJ's post here: http://forum.xda-developers.com/showthread.php?t=1234973
Click to expand...
Click to collapse
Thanks to drjbliss for finding the Motorola vulnerability that lead to this. Original work here: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
Follow this guide exactly, and you can root OTA Gingerbread on your Droid X2 That means no more SBF'ing Froyo just so you can root. I have put all the commands into a few simple scripts. Instead of doing everything manually, you can just follow this simple guide. This post assumes you have ADB installed and know how to use it, and that you have the Motorola USB drivers installed.
--
Step 1:
METHOD A: Download the attached zip file with the root files, and extract the files somewhere memorable. Plug your phone into AC charger or computer. FOLLOW STEP 2.
Click to expand...
Click to collapse
OR
METHOD B: Download the attached zip file with the root files, plug your phone into your computer, and put the phone in USB Mass Storage mode. Then extract the files to the internal storage device a.k.a. MOT. If you choose this method then you can SKIP STEP 2 AND GO TO STEP 3.
Click to expand...
Click to collapse
Download: http://www.multiupload.com/B7HPPKOT86
Mirror: http://www.mediafire.com/?t31bnhaiwyulf81
--
Step 2 (if you chose METHOD A):
Open Windows command terminal.
Type these commands:
extracted-location = place where you extracted files to, if you are in the same location as the files, then you can omit extracted-location/.
Code:
adb push extracted-location/motoroot-step1.sh /sdcard/
adb push extracted-location/motoroot-step2.sh /sdcard/
adb push extracted-location/motoroot-step3.sh /sdcard/
adb push extracted-location/su /sdcard/
adb push extracted-location/Superuser.apk /sdcard/
--
Step 3:
Type these commands:
Code:
adb shell
sh /sdcard/motoroot-step1.sh
Hard reboot your phone.
--
Step 4:
Type these commands:
Code:
adb shell
sh /sdcard/motoroot-step2.sh
Hard reboot your phone.
--
Step 5:
Type these commands:
Code:
adb shell
sh /sdcard/motoroot-step3.sh
Your phone will reboot itself.
--
Step 6:
Type these commands:
Code:
adb shell
su
Accept the Superuser prompt on your phone and allow access. Now any time you want to adb shell, you can type su afterwards and obtain root.
--
Congratulations, you are now rooted.
worked great...thank you
Trying it now.
Edit: Script works great, rooted and everything, superuser works.
Worked for me as well !! Thanks +1 . Now if only I could get into my recovery
I tried using P3's new one-click root. It complete successfully, but Titanium is claiming it does not have root access. P3's one-click appears to be doing the same thing listed here. Anyone else?
triplec76 said:
I tried using P3's new one-click root. It complete successfully, but Titanium is claiming it does not have root access. P3's one-click appears to be doing the same thing listed here. Anyone else?
Click to expand...
Click to collapse
I just downloaded Titanium and ran it . It tells me that everything is ok .
Is that using P3's one-click or the method here?
Ditto. Worked great. THANKS!
Jason
triplec76 said:
Is that using P3's one-click or the method here?
Click to expand...
Click to collapse
The method here .
The step by step method here worked while one-click would not no matter what I tried.
I used the oneclick, no problems at all. Glad i didnt have to go SBF'ing back and forth.
Requested addition to roll up sticky, thanks for posting
Sent from my DROID X2 using XDA App
Can someone point me in a good direction to learn ADB. I am reading over and over that the one click method doesn't work for the X2. I have a X2 running pre-rooted GB right now from the old "sbf back then root" method, but it is getting replaced on Tue. Would love to just root it when it arrives rather than sbf and stuff.
unless there is a method to get the one click to work of course....then by all means educate me on that
nerdslogic said:
Can someone point me in a good direction to learn ADB. I am reading over and over that the one click method doesn't work for the X2. I have a X2 running pre-rooted GB right now from the old "sbf back then root" method, but it is getting replaced on Tue. Would love to just root it when it arrives rather than sbf and stuff.
unless there is a method to get the one click to work of course....then by all means educate me on that
Click to expand...
Click to collapse
Sure, no problem. Here are some guides found with a quick XDA Google search, I hope they help you (or anyone else) out with ADB. Keep in mind that while this will help you learn how to use ADB and get ADB working, some of the information may be outdated or may not apply.
ADB Easy Tutorial
[GUIDE] ADB Workshop and Guide for everyone
[TUTORIAL/HOW TO] Basics of ADB
Here is a link to Google's official ADB Android page. This has all the commands you need, a good reference.
Hard reset = battery pull?
Also please make a note to put on root of SD Card.
SBF'd GB. Rooted with one click. Worked perfect. Couldn't be easier.
Sent from my DROID X2 using XDA App
atrohde said:
SBF'd GB. Rooted with one click. Worked perfect. Couldn't be easier.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Me too. Got my 3rd x2 today & it came with gb on it. One-click did the trick.
Sent from my DROID X2 using xda premium
No go
I've been working on this six hours straight, so my mind is pretty tired.
Here's where I am stuck at, and I should know the answer but am burned out:
Ah nevermind......nothing that a couple of cold beers couldn't help! I had it in mass storage mode. Used to HTC, stock Android USB modes....
It worked as advertised. Thank you very much!
sweet no problems
Does this work for 2.3.5 418 from OTA? In other words, I have 2.3.5 418 from OTA updates. Will this method work for that version?

[Q] Re-Rooting Photon after OTA update to 2.3.5

I was enjoying the beauty of having a rooted device, but now that I have received an update from Motorola (which I thought was ICS) I have lost root access.
I have a Photon 4g running 2.3.5, and I did my root using a OCR when I was on 2.3.4. I have tried that OCR again among others and torpedo photon and no luck. Every app I try says that it was denied superuser access (which is still installed). The only exception to this is Play Movies, which says that "This app currently does not support root access, and your device is rooted" I do not know where else to turn. I just want to be part of the cool kids again. Please someone help me.
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Shad0wguy said:
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
I used Motorola DROID 3 one click. Worked great.
Sent from my MB855 using XDA
Thank you, I will try the Droid 3 OCR, and if that does not work, see if I can get Torpedo to work, and if that does not work I will send it in to Motorola.
Use torpedo thru terminal emulator on your phone as I did
Sent from my Motorola Electrify using XDA
What worked for me was to use the command prompt on windows 7 instead of terminal emulator. For some reason, TE could not see the photon-torpedo file in the phone after i had transferred it there. Command prompt did.
Sent from my MB855 using xda premium
Also remember to reboot after!
I got the OTA update to 2.3.5 yesterday, and photon-torpedo is NOT working for me. After running photon-torpedo.sh, I get the error message, but my prompt doesn't change to # or root. Trying to run install-su.sh doesn't work since I'm not root and gives me permissions errors. Has anybody gotten photon-torpedo to work after yesterday's OTA update?
UPDATE:
I figured out the issue and a fix:
http://forum.xda-developers.com/showpost.php?p=28669160&postcount=363
JohnH4 said:
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
Click to expand...
Click to collapse
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
can someone please help me with my post above?
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
here's an easy way to do Photon Torpedo: http://www.groovypost.com/howto/motorola-photon-4-g-how-to-root-your-phone/
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
You don't need to create /data/tmp in your phone's internal storage. That folder already exists inside the system partitions. Use ADB to push it in. Follow the instructions in the Photon Torpedo thread.
Sent from my MB855 using xda app-developers app
I didn't have my phone Rooted before the update to Android 2.3.5 but after trying several different methods I found one that worked with ADB and torpedo program/files with a step by step that actually says to have 2.3.5 I followed the instructions and it worked for me, only problem I had was I unzipped the photon-torpedo.tar file by mistake... it doesn't have to be unzipped into the folder just place the whole file in the folder.
Hears a link to the walk through from gamerguy13
instructables.com/id/How-to-get-root-access-on-your-Motorola-PhotonEle/?ALLSTEPS
Good luck everyone else trying to root or re-root.
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
I would think twice before taking that ota update. Currently, under 2.34, your bootloader should be unlockable. The main effect of the 2.35 update is to lock the bootloader.
Sent from my MB855 using xda premium
Worked for me
JohnH4 said:
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Click to expand...
Click to collapse
John was right, just ignore the errors. This method by edgan worked for me.
---------- Post added at 07:28 PM ---------- Previous post was at 07:16 PM ----------
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
I agree with bitbang, I've had enough of this bullsh*t from Motorola. It's time for me to shop around. Unfortunately for me, I have a little more than a year on my contract! I've heard that Sprint had some kind of buy back or release program where they let you trade in your phone for something new (for a "small" fee, of course). It just might be worth it to get away from Moto. This smartphone technology changes way too fast for 2 year contracts anyway.
It's a shame. When I can get this phone to work properly, it is awesome, I'm sure bitbang even agrees with that but it is definately time to move on. The Samsung Galaxy 3 looks pretty cool!
amlodipine said:
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
Click to expand...
Click to collapse
When the update fails and you see the Android guy with the "!", press and hold both volume up and down. This will show you on the screen why it failed. Common causes for failure are mods to the build.prop file or removal of core apps.

Fire HD 6 - 5.3.1.1 - How to root correctly?

Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help ?
cuki3r3k83bln said:
Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help
Click to expand...
Click to collapse
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Killa8 said:
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Click to expand...
Click to collapse
@Killa8, as I mentioned HERE in more detail, the procedure for downgrading to 4.5.3 doesn't appear to be explained in the linked tutorial. Any help would be greatly appreciated! I'm trying to root and install CM on my daughter's tablets as they find Android to be far more intuitive than FireOS. Many thanks!!!
Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1
RadRacer said:
Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1
Click to expand...
Click to collapse
Thank you for this! I was having the same issue as the OP and this solved it.:good:
geoyou said:
Thank you for this! I was having the same issue as the OP and this solved it.:good:
Click to expand...
Click to collapse
Can you tell me how you installed TWRP? the 2nd post of the page is confusing to me.
NVM i found a video tutorial
I've seen too many threads mentioning 5.3.1 and implying that 5.3.1.1 is the same.
Even if that is the case, all the tutorials I have read left me scratching my head at various points. So here is a walkthrough of what I just went through to root my Kindle fire HD 6
It's now running 5.3.1.0 and will stay there for the time being (unless I can get solid answers on 5.3.1.1).
I started with this tutorial thread but I found it easy to make mistakes and I ended up bricking my device (fortunately the unbrick iso is very good and the tutorial video is excellent).
So here is my procedure. Doing this on Windows is probably less involved thanks to the bat file in one of the steps.
Start by getting the stuff you will need together.
You will need ROMs from here.
Specifically, the 4.5.3 and 5.3.1.0 ROMs.
The 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
Note: The version number on that second file makes no sense to me, and I made a mistake trying to flash the wrong one in TWRP. Here is the correct name for reference. You might change the file names to reflect the version number.
Go ahead and change the extension of the 5.3.1.0 bin file to zip instead. TWRP will need it this way.
Download the stock recovery image. There is a link at the bottom of the second post in the tutorial thread I linked above. Or you can just click here.
Grab the WindowsAutoTWRP_v03.zip from the tutorial thread (or click here).
It has the Windows ADB executable and drivers in it so it will save you some hassle on a Windows machine.
For Macs, I found a video from RootJunkie.com that linked to tools at http://rootjunkysdl.com/files/?dir=Adb%20Fastboot%20Files. I was able to do everything from my Mac with these.
As a side note, the video I found these on was https://www.youtube.com/watch?v=iv0VcNM8IAw, but it's not important to watch.
It will help to gather zips and APK files you will need right now as well.
Get a copy of ES file explorer, Kingroot (I used the APK, but if you have a windows system, it might be easier to use the Windows version instead), and an android launcher of some sort.
For additional images, you will need the following:
From the tutorial thread: make_space_v02.zip
Supersu.zip linked at https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Xposed which if you follow the link from the tutorial through the forum thread should lead you here: http://dl-xda.xposed.info/framework/sdk22/arm/. I grabbed xposed-v87-sdk22-arm.zip
flash Pico (Uni) GAPPS for 5.1 which again, if you follow all the links, will take you here: https://basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/gapps/tk_gapps-modular-pico%28uni%29-5.1.1-20150920-signed.zip.
Make sure you have all the files gathered in one place, it's really helpful.
If you are using a Mac, you will also need Android File Transfer at https://www.android.com/filetransfer/.
Something optional that might help is a USB OTG cable or one of those USB drives that support USB OTG with its own micro USB connector. It's not necessary but it might help if you need to get files to your tablet in TWRP.
At this point, I'm going to go into Mac instruction mode. If you know that the Windows command prompt is sort of like the terminal application on OS X, that you don't use ./ path specifies on windows, etc, you should be able to come up with some
Once you have everything in place, shut down your Kindle Fire 6.
On your computer, open a terminal window and get to where you unzipped your ADB tools.
The simple way is to type cd followed by a space then drag the folder with your tools from finder to the terminal widow so you get something like cd /users/me/abd
The actual path will be dependent on your system.
This terminal window should remain open for the entire process. It will make life easier.
Hold volume up and turn the Kindle Fire on. You should enter recovery.
Back at your computer type ./adb devices
Your kindle should show up there. When it does, go back to your tablet and select "apply update from ADB".
Then, from the terminal, enter ./adb sideload 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
If you just type ./adb sideload then drag the file into the terminal window, it will fill the name and path out for you.
Note that this all seems kind of like the video I linked above but we are downgrading to 4.3.5 instead as the tutorial thread says we should.
Once that's done, you end up back at the recovery screen. I went ahead and did a wipe data/factory reset. I don't know if this is necessary though.
When you get into 4.5.3, you need to shut down wifi if you are not prompted through new device setup.
If you are prompted, just skip it.
You may need to enable debugging. Go to setting, device options, find the serial number field and tap it 7 times.
Open the now revealed developer console and toggle "enable ADB" so it's on.
Install the APKs you downloaded earlier.
Use ./adb install <name of ES file explorer apk>
If you're on Windows, you can go ahead and run the Windows root util.
If you are on a Mac, install the Kingroot APK using the ./adb install command.
If you go the APK route, Kingroot requires a wifi connection. This will expose you to Amazon's OTA updates. You will need to watch your Kindle carefully at this point.
The download with probably download but as long as you don't let it sleep, it should not reboot and install.
Kingroot may take a couple of tries to get root.
As soon as it does, turn off wifi!
After that, open ES file explorer, give it root permissions, then navigate to the root folder, then to cache. Look for a bin file there. If there is nothing, you didn't get the OTA update pushed to you. If you did, delete it. See post 5 in this thread: https://forum.xda-developers.com/kindle-fire-hdx/help/deleting-downloaded-update-t3100573
To prevent any OTA relapses until we can go further, use ES file explorer to rename /system/etc/security/otacerts.zip. I replaces the first o and last p with _ characters.
It should be safe to turn on wifi at this point.
If you deleted a bin file in /cache, you aren't out of the woods yet. The Kindle could still reboot on you and it will give you the red ! but I found booting into recovery then just rebooting the Kindle caused it to work itself out after a couple tries.
We should be good to go for TWRP at this point.
In the terminal type ./adb shell
When the shell opens type su
Grant the shell permissions on the Kindle
Type exit twice.
On a Mac, we cannot run the bat file included in the WindowsAutoTWRP_v03.zip file.
But here are the commands to enter manually:
./adb devices
./adb install gscript-android.apk
./adb shell "mkdir /sdcard/gscript"
./adb push gscript /sdcard/gscript/
./adb shell "cp /sdcard/gscript/flash_453_stay.sh /data/local/tmp/"
./adb shell "ls /data/local/tmp/"
./adb shell "su -c 'chmod 777 /data/local/tmp/flash_453_stay.sh'"
./adb shell "su -c 'sh /data/local/tmp/flash_453_stay.sh'"
Once complete open ES file explorer again
DELETE sdcard/gscripts/s5.4.1_113_stock_recovery_uboot.zip!!!!!!!
It's too easy to mistakenly flash this in TWRP and it WILL brick your kindle.
We will now copy those zip files we downloaded earlier onto the Kindle.
I used the Android file transfer unity to put them in the scripts folder but copying them to Downloads on the Kindle might be easier.
If you are a command line type of person, you can also use the adb push command.
You want to copy over the following:
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
5.5.2_1534_stock_recovery_uboot.zip
UPDATE-SuperSU-v2.46.zip (or whatever the current version you downloaded is)
make_space_v02.zip
xposed-v87-sdk22-arm.zip (or whatever the version you downloaded is. The version could have changed after I wrote this.)
tk_gapps-modular-pico(uni)-5.1.1-20150920-signed.zip (again, based on what version was available when you downloaded it)
It might be a good time to sideload that extra launcher you downloaded earlier. I didn't need it, but you might.
Again the command is ./adb install <apk file name>
In the terminal, type ./adb reboot recovery.
You *should* end up in TWRP.
These next steps are important to do in one go. Don't exit TWRP until you have installed all the zip files you copied over.
The order in the tutorial thread is the 5.3.1.0 system image, the recovery image, the make_space zip, the Supersu zip, the xposed zip, and the tk_gapps-modular-pico(uni)... zip.
Do all this from the Install menu in TWRP. I did not try to queue up all the zip files at once, I don't know if that would work.
If you forgot to copy a file, TWRP should allow you to copy files via a USB cable to your tablet.
If you do this on a Mac and Android file transfer craps out on you as it did with me, that is where the USB OTG cable comes in handy. But lets hope you copied everything or that the USB connection doesn't crap out on you.
Select the wipe menu, then advanced wipe. Check the cache and dalvik cache. Once done use the back arrow and swath the "swipe to factory reset" slider.
If you are brave, you can just reset and wait through the fire logo.
If you are trying to follow along with the tutorial I linked, reboot while holding volume up to see what recovery you land in. If it's not TWRP, proceed.
When you finally get to Android, you can use ES file explorer as one way to check for root privileges. I'm sure there are others.
I'm no expert, but if you run not problems with the Kindle Fire HD 6 (4th gen) and you started with 5.3.1.1, I can tell you some of the pitfalls I ran into and how I got out of them.
Excellent guide, thanks elementcarbon12!
I'm a total new comer to rooting and getting my hands dirty with android (although I am a long time linux user), and i made it work, and now have a fire hd 6 that I can sort the way I want it!
I did encounter a few problems though, first, I did not do a factory reset /data wipe after the downgrade and ended up in a boot loop. This was easily sorted by using the "adb reboot recovery" command, doing the data wipe/reset and then holding down power for 20 sec.
Everything was smooth sailing again until the reboot out of TWRP after installing the ZIP files. I did the wimps reboot to recovery to make sure I didn't get TWRP, which I didn't, so rebooted to get into android, however I entered a boot loop again. This time a simple hold the power for 20 sec and then turn on worked and the system started it's 'optimization'.
Upon completion, i still had root, although ES and my chosen launcher had gone, so had to reinstall them. No problems there though.
So thank you very much for collection all of the information and links from other pages into this one easy to follow post!
hi guys i have a question I'm on cm11 on fire hd 6 i also have a android backup of 4.5.3 my question is I'm note sure what boot loader i have at one point it did have 5xxx on it but not sure what version can i just side load 5.4.0 and be okay since the stock rom was put back to 4.5.3 thats how i installed cm11 or does it need boot loader from a 5xxx rom

Categories

Resources