{
"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"
}
This is ONLY for the DROID 4 XT894. Do NOT use this on anything else!
DROID 4 Utility XT894Jellybean
Use a Download Manager such as "Orbit Download Manager" for best downloading results.
Mirrors:
Dev-Host
Batakang
Filesize: 497 MB (521,766,988 bytes)
MD5: B8E86DDCC3C59571E7AB086BE13BD89D
- Windows Instructions
Extract .zip to its own folder on the Desktop.
Install the required drivers. The folder with the drivers is called "Drivers [WINDOWS ONLY]" and is included in the Utility folder.
Double click the ".bat" file. This will be called "WindowsUtility.bat" the image is just for reference.
- Mac & Linux Instructions
Extract the .zip to any folder you like, the /Downloads/ or /Desktop/ folder should work just fine.
Open a Terminal window. (On Mac: Applications > Utilities > Terminal)
Learn your 'sudo' password. This is almost always your Admin password on a Mac computer. On Linux you should already know what this is, its yours account password if your account is an admin as well.
Type the following code into the Terminal Windows, places where it says ***DRAG HERE*** are telling you to simply drag the folder there. For example: cd ***DRAG FOLDER HERE*** then press 'Enter' after each line.
Code:
cd ***DRAG UNZIPPED UTILITY FOLDER HERE***
chmod +x ./LinuxMacUtility.sh
bash ./LinuxMacUtility.sh
You will be asked for your sudo password at least once in the Utility process, so make sure you followed the instructions to learn it.
Functions of the DROID 4 Utility XT894 Jellybean:
Code:
1 Flash Official Jellybean Firmware (Wipe Data)
2 Flash Official Jellybean Firmware (No Data Wipe)
3 Razr Blade: Motorola Droid Razr 4.1 Root Exploit by djrbliss
4 Install Safestrap 3 App by Hashcode.
Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official Jellybean firmware to your device and will wipe data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official Jellybean firmware to your device and will NOT wipe data.
Number 3 Explained -- This is Dan Rosenberg's DROID RAZR 4.1 Jellybean exploit called 'RAZR Blade'. This option requires your phone to be booted normally, with USB Debugging enabled. (This is working on the DROID 4 as well.)
Number 4 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install Hashcode's App for Safestrap 3.11.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters.
Thanks to Hashcode for Safestrap and Djrbliss for RAZR_Blade!
Yes! You are a champion, mattlgroff!
Sent from my DROID4 using xda app-developers app
Root failing.
Hello,
First and foremost I'd like to thank you for this utility. 4.1 flashed without a hitch! Unfortunately, I am unable to get the root to work. I've attached the text from where it started to error.
The root is failing here, after phase 2. Any ideas?:
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
3559 KB/s (543080 bytes in 0.149s)
3597 KB/s (1867568 bytes in 0.507s)
3144 KB/s (476557 bytes in 0.148s)
2308 KB/s (63838 bytes in 0.027s)
[*] Cleaning up...
/system/bin/sh: su: not found
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting...
[*] Exploit complete!
Thanks in advance for your assistance.
Thanks a lot, i could unbrick my phone thank to this tool.
korngames said:
Hello,
First and foremost I'd like to thank you for this utility. 4.1 flashed without a hitch! Unfortunately, I am unable to get the root to work. I've attached the text from where it started to error.
The root is failing here, after phase 2. Any ideas?:
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
3559 KB/s (543080 bytes in 0.149s)
3597 KB/s (1867568 bytes in 0.507s)
3144 KB/s (476557 bytes in 0.148s)
2308 KB/s (63838 bytes in 0.027s)
[*] Cleaning up...
/system/bin/sh: su: not found
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting...
[*] Exploit complete!
Thanks in advance for your assistance.
Click to expand...
Click to collapse
Try wiping and trying again. I was just told by a user on DroidRzr that it worked on the D4 OTA.
Sent from my Galaxy Nexus using Tapatalk 2
When I try this on my Droid 4 with the latest OTA JB update from Verizon, the terminal gets stuck at "waiting for device". This has happened previously when I tried to use the ICS Utility when my phone still had ICS. I've tried on several Windows PC's and none have seemed to recognized my device even with the latest Motorola drivers installed (when I went to install the drivers included in the JB Utility, I was alerted I already had newer versions). I have USB debugging enabled on my device. Am I missing something or doing something wrong?
Do you set your USB option from mass storage to MTP?
Sent from my DROID4 using xda app-developers app
I'm getting findstr.exe is not a valid win32 application... Running windows XP
i noticed the root method used with this utility uses a different superuser
when i used this and tried to use either the verizon tether or wifi tether for root users it wouldn't work because of the su used. But when i downloaded and used a different razor root script that installed supersu everything works great
just a fyi
i used this for rooting
http://vulnfactory.org/public/razr_blade.zip
also using this there is no need to put your device in mtp mode
dbreezy187 said:
Do you set your USB option from mass storage to MTP?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
My USB connection is and has been set to MTP. Is that what it should be set as, or is it supposed to be set to one of the other two options?
Does this work root on the verizon droid 4? tryin to help my friend get his tether back.
When I used it on ICS that was my issue.... as far as I know yes MTP... are you using the same USB cable each time... have you checked device manager to unsure your phone is connected properly... ... ... yes this will root...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
When I used it on ICS that was my issue.... as far as I know yes MTP... are you using the same USB cable each time... have you checked device manager to unsure your phone is connected properly... ... ... yes this will root...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
How do I check "device manager"? I'm reading some stuff that leads me to believe Motorola is quite strict about the use of their cables. Some say you may need an actual Motorola branded cable to get the device to connect. Where can I get an official Motorola micro USB cord?
Thanks for the root suggestion. Worked great and Verizon tether started up with no problems.
ovelayer said:
i noticed the root method used with this utility uses a different superuser
when i used this and tried to use either the verizon tether or wifi tether for root users it wouldn't work because of the su used. But when i downloaded and used a different razor root script that installed supersu everything works great
just a fyi
i used this for rooting
http://vulnfactory.org/public/razr_blade.zip
also using this there is no need to put your device in mtp mode
Click to expand...
Click to collapse
chewy74 said:
Thanks for the root suggestion. Worked great and Verizon tether started up with no problems.
Click to expand...
Click to collapse
no problem glad it helped
i've updated to the ota and have tried to root using this method on both camera and mtp, then wiped and tried again. still no root. phase one fails. used two different usb's, uninstalled and reinstalled drivers twice. whats goin on?
you reinstalled drivers, but did you check device manager to see the pc seeing phone correct (as a adb device)
Sent from my Clear using xda premium
how do i actually open device manager. i see no application after i install it
windows device manager
start>control panel>hardware & sound> device manager
if driver is not correct, may look like
if correct should look like
I have root back! Thank you!
Related
Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!
There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.
From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux
This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...
MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!
-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)
DOWNLOADS
WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8
MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A
LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0
Here's how:
Windows:
Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)
Mac/Linux:
Simply extract the zip then
Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use
Code:
sudo passwd
to reset the root password
Next run:
Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:
Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:
Code:
bash Droid4linux
OR
Code:
bash Droid4mac
I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.
Have fun and I hope you enjoy! [/SIZE]
CLICK HERE TO DONATE
SCREENSHOTS
{
"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"
}
CLICK HERE TO DONATE
I can not get this to unroot.
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.
Please make a selection or hit ENTER to return:
Click to expand...
Click to collapse
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.
appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!
prodigyweb said:
My setup is: http://i.imgur.com/Surbz.png
should it be within the adb package from android itself?
Click to expand...
Click to collapse
Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
highlandsun said:
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
Click to expand...
Click to collapse
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
reigndropz said:
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
Click to expand...
Click to collapse
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
highlandsun said:
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
Click to expand...
Click to collapse
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
reigndropz said:
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
Click to expand...
Click to collapse
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
highlandsun said:
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Click to expand...
Click to collapse
Hey thanks for pointing that out! I didnt notice because they were already executable on my computer. I added
Code:
chmod +x ./files -R
to the script on startup so no one should have to manually do it anymore, sorry about that
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Make sure you have done all of the steps below
Prework
1. Plug in phone to computer.
2. Turn on USB Debugging. Menu -> Settings -> Application -> Development -> USB Debugging
3. Confirm latest Moto driver is installed. Go to Device Manager on Windows while the D4 is plugged into it and confirm you see ADB Interface listed with Mot Composite ADB Interface listed in the group. If you see that, skip #4 & #5. There are other ways to go about this, but this is the simplest and surefire way to confirm the driver is there and compatible.
4. Go get Moto driver and install it: USB and PC Charging Drivers - Motorola Mobility, Inc. USA It is an exe file that must be run and your computer has to restart when completed.
5. Go back into your Device Manager after reboot with the phone plugged in and confirm ADB Interface is there and no error exists.
Done.
I can't get this to root, it appeared to have rooted once since Superuser was installed but TBU said not root access. Now I get message " error more than one device and emulator" when I try to root again or unroot. any idea?
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Hammerfest said:
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Click to expand...
Click to collapse
The phone itself is great. Good build quality, fantastic keyboard, fast, etc. I have not heard any news on fastboot files yet. I assume it's just a matter of time but who really knows for sure. Unlock updates? As in unlock the bootloader? I don't ever expect to see that happen, personally.
Despite that, development seems to be coming along nicely with very usable AOSP CM9, AOKP, and Gummy ROMs. The relative ease with which Razr ROMs can be ported to the D4 (due to almost identical internal components) should help on that front as well as Razr development is seems very strong.
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
mancowmilitia said:
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
Click to expand...
Click to collapse
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
kwyrt said:
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
Click to expand...
Click to collapse
I installed the upgrade with no issues. I was able to re-root without complication as well. The only message I received was that the Superuser.apk installation "failed" because it was already there. Others have noted that unrooting doesn't delete the file. But, its presence did not stop my upgrade.
This time I installed Voodoo and will go that route for the next OTA.
Is there a mirror link for the Windows Utility? The download keeps timing out on me.
heres a link for an older copy
http://goo.im/apps/mattlgroff/Droid4Utility0.3.zip
Unfortunatelly nobody seems to get root, i will try to find out why it worked for me...
I got root acces (and so did a friend of mine) but for some weird reason nobody else seems to get it with the steps i posted. I will explain step by step what i did and had on my pc while gaining root acces:
- I am working on a fresh Windows 7 64 bit pc
- I have never had any lg software installed on it (just formated my hard drives and re installed Windows)
- I have a stock non-branded Dutch LG p-880
- I connected my phone, put it in USB-Debugging mode
- Found out not all of the drivers where installed correctly
- Went to the LG website, downloaded and installed the LGMobile support tool
- In the support tool i went to instal drivers (at the right top), whent to the LGP-880 and double clicked for installing the drivers
- I had the phone connectivity switched on at LG PC Software
- Then i ran the root.bat file and nothing happend
- Changed the phone's connectivity to Charging only and ran the boot.bat file again and that did the trick.
First off all I have to mention i didn't do any development at all and credits go to kennethpenn for his ''One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux) root'' and to one of my close friends for telling me about the tool.
I just wanted to find out how to get root and thought, why not? So i started the script and it gave me root acces, installed SU and a Busybox.
This is how to do it:
- Download and install the LG Optimus 4x HD drivers from the LGMobile Support Tool (you can download it from LG's website or download it here) Start the program, at the top right corner press install drivers and look for the LG P880 then double klick
- Download kennethpenn's root tool here and extract it to a folder you want
- Plug your device in your computer and turn USB Debugging on: Settings, developer options, USB Debugging. Make sure your connection option is set to charge only.
- Now double click root.bat
- Your device will restart a couple of times and congratulations: You've got root
I did all of this without installing/using lg pc suite
As always, i am not responsible (neither is kennethpenn) for bricking your device.
You can find the original thread here
{
"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"
}
I tried 3 times, all failed
I'm on V10b
What FW are on?
The original thread says it's for HTC One X.
edit: I tried serveral times, doesn't work for me.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
and so on...
ragiut1 said:
I tried 3 times, all failed
I'm on V10b
What FW are on?
Click to expand...
Click to collapse
V10b. Are you sure you installed the drivers correctly? I installed them with the LGMobile Support tool (you can download it at LG's website orhere)
Start the program, at the top right corner press install drivers and look for the LG P880 then double klick. Reconnect your phone and try again
pintness said:
The original thread says it's for HTC One X.
Click to expand...
Click to collapse
Correct, but it also works on the Optimus 4x HD
Serious? Need to try but can't until tomoz, anyone else tried with success?
Sent from my LG-P880 using xda premium
When i found 5 minutes, i try it!
Sent from my LG-P880 using xda app-developers app
Wont work for me. Tried several times.
"/data/local/" is locked on my Device.
Only "/data/local/tmp/" is useable.
Let me know if it worked for you guys
i tried many times.... don't work .....
didn't work for me either, i changed a lot, i even cannot push to /data/local - only to /data/local/tmp,
so i changed the pathes and such in the script, didnt' work
fire3d said:
didn't work for me either, i changed a lot, i even cannot push to /data/local - only to /data/local/tmp,
so i changed the pathes and such in the script, didnt' work
Click to expand...
Click to collapse
Very strange, im on v10b Dutch stock version. Did everything on the first post and it worked within 5 minutes. All you guys installed the driver via the LGMobile software tool?
You can also try with uninstalling lg pc sync and then selecting your phones connectivity to lg software ?
I used Windows 7 64
Sent from my HTC One X using xda premium
Not working for me
I'm on V10c
I followed step by step guide and should not be ... gives me permission denied
dexter90 said:
I followed step by step guide and should not be ... gives me permission denied
Click to expand...
Click to collapse
In a couple of minutes i will completely discribe step by step wat i had installed, used and pc. Maybe that will help somebody?
Sent from my HTC One X using xda premium
Sry ... but this wont work.
The "data/local/" folder is locked.
Only "data/local/tmp" is open.
Possible that it worked for you... but not for most users ... no chance.
Nope not working, maybe you have a developer device
Sent from my LG-P880 using xda premium
to me it does not work
JJnJ said:
V10b. Are you sure you installed the drivers correctly? I installed them with the LGMobile Support tool (you can download it at LG's website orhere)
Start the program, at the top right corner press install drivers and look for the LG P880 then double klick. Reconnect your phone and try again
Click to expand...
Click to collapse
I have done all these steps, i try many time, but no work ( win 7 32bit, V10B doic)
Permission denied for me too. It's impossible that all of us cannot root the device!
{
"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"
}
The other thread was removed for various reasons (the thread was not by myself but another Senior Member). But here goes again, here are some ground guidelines I'd like to mention so no one ruins their devices.
Do NOT flash anything in AP Fastboot to try to root. On our locked bootloader devices, it just means having to re-flash FXZ files (which we don't have, or root to make our own copies), and a bunch of other messes. This includes custom recovery images (recovery.img), kernels (boot.img), system (system.img), or whatever crazy schemes that were made up before. The help was a good gesture, but I want to make sure no one can be bricked in the process.
Do NOT try Odin... that's for Samsung devices.
On the stock firmware that comes with the Atrix HD on launch, the kernel is patched from all exploits involving ~/data/local/ that we know of so far... This covers almost all known ICS root exploits out there, including RazrsEdge by Dan Rosenberg.
Here is my thread so far from droidrzr.com that I am now bringing over here for a better, saner, discussion with more invidivuals (obviously not many Atrix HD owners on a Droid Razr website).
No known root access yet for the Atrix HD as of 7/30/2012.
10-16-2012 Not anymore!
Keep this in mind! DroidRZR.com, XDA-Developers.com, and myself at not responsible for anything you do to your phone or anything that happens as a result of you messing with your phone or listening to posts or users on this forum. Always be careful when you flash
WARNING: Since there is no FXZ files yet there is no going back to the original firmware if you flash this, chance of being off the OTA path, etc.
When trying these should all be true:
Phone is plugged into a Windows computer (XP and higher) and booted normally (where you can open apps, email, text, etc.)
^^^Using a standard USB cable, preferably the one that came with your device. NOT a factory-style modified cable.
Phone's USB mode (in the pulldown notification menu) is set to MTP and/or Camera mode, but NOT USB Mass Storage.
Settings > Developer Options > USB Debugging enabled.
Latest Motorola USB Drivers are installed. 64 bit for 64 bit system, 32 bit for 32 bit system. ---To check go to Start, right-click on Computer, and hit properties. Next to GB of RAM it will say. System Version--
64: http://developer.motorola.com/tools/usb_drivers/handset_usb_driver_64/ 32: http://developer.motorola.com/tools/usb_drivers/handset_usb_driver/
Click to expand...
Click to collapse
Good luck! The second post will be reserved for saying what has/has not worked from what has been learned in this thread.
UPDATE 10-16-2012
Coming very soon. Get your bounties ready.
Tested Root Tools:
Motofail2Go by Djrbliss: (http://forum.xda-developers.com/showthread.php?t=1940594) SUCCESS.
Root_with_Restore_by_Bin4ry : http://forum.xda-developers.com/showthread.php?t=1886460 Failed
XT912 Eternity Project Easy Root (using debugfs) ---- Failed.
Dan Rosenberg's Razrsedge Root ---- Failed.
Mempodroid Root (saurik idea) ---- Failed.
XT928 Root v4 from http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4.zip ---- Failed.
XT928 Root v4 Test 2 from http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4_Test2.zip ---- Failed.
XT928 Root v4 Test 3 from http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4_Test3.zip ---- Failed.
XT___ RazrRoot404.zip from http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/RazrRoot404.zip ---- Failed.
Moto Razr ---ChineseRootKeyTool (for XT910,XT912,XT928,XT917) from http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/Moto Razr 一键工具包.zip ---- Failed.
mattlgroff said:
Reserved.
Click to expand...
Click to collapse
Nice initiative mattlgroff. I'll be following this!
Thanks
+1
Just got an Atrix HD.
Moving over from an Inspire 4G with ICS and Jellytime mods.
Also looking forward to development of a ROOT solution for the AHD.
Got a root tool from the http://bbs.gfan.com forums for the XT928, they were having issues with other root exploits and needed a new one. From the looks of the code I modified into english and into one folder from Iopda's root tool, this is just going to be another bust. Worth a shot anyway, no risk to ones phones.
Same settings as normal, USB Debugging Enabled + MTP Mode for USB.
I will be testing 'round the clock when I receive my Atrix HD in the mail in a few days (August 3rd or 4th).
Link: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4.zip
mattlgroff said:
Got a root tool from the http://bbs.gfan.com forums for the XT928, they were having issues with other root exploits and needed a new one. From the looks of the code I modified into english and into one folder from Iopda's root tool, this is just going to be another bust. Worth a shot anyway, no risk to ones phones.
Same settings as normal, USB Debugging Enabled + MTP Mode for USB.
I will be testing 'round the clock when I receive my Atrix HD in the mail in a few days (August 3rd or 4th).
Link: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4.zip
Click to expand...
Click to collapse
I'll give it a shot as soon as I get home, in about 5 minutes...
Glad to see some BIG GUNS in these threads! Thanks Matt!
EDIT: Yup... it's a bust... Here are my results:
***************************************************************************
* *
* XT928 ╥╗╝ⁿROOT░ⁿ v4 by iopda 2012.6 *
* *
***************************************************************************
*
*
* Connect the phone and powered normally with stand USB cable.
* Make sure Setting-Developer Options-USB Debugging is enabled.
* Also make sure MTP mode is selected, NOT Mass Storage or Camera.
*
*
Press any key to continue . . .
Press any key to continue . . .
--- cleaning
--- pushing files
3804 KB/s (2005736 bytes in 0.514s)
1399 KB/s (22364 bytes in 0.015s)
2873 KB/s (1468889 bytes in 0.499s)
--- correcting busybox permissions
--- remounting /system
/system/bin/sh: su: not found
--- copying busybox to /system/xbin/
/system/bin/sh: su: not found
--- correcting busybox ownership
/system/bin/sh: su: not found
--- correcting busybox permissions
/system/bin/sh: su: not found
--- installing busybox
/system/bin/sh: su: not found
--- correcting su ownership
/system/bin/sh: su: not found
--- correcting su permissions
/system/bin/sh: su: not found
--- copying SU binary
/system/bin/sh: su: not found
--- correcting su symlinks
/system/bin/sh: su: not found
/system/bin/sh: su: not found
--- pushing Superuser app
/system/bin/sh: su: not found
/system/bin/sh: su: not found
******************************************************************************
╣º╧▓─·úí XT928 ╥╗╝ⁿROOT░ⁿ░▓╫░═Ω│╔
By iopda
******************************************************************************
ALL DONE!!!
Press any key to continue . . .
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
I want to point out something off about the build.prop....
Code:
com.motorola.debug.fddebug=true
When you run a google on this particular line you find absolutely 0 results...meaning this has not really been in build.props or anything before now. Maybe this is a clue that can lead us to something important.
EDIT: Also, I am requesting someone copy their ~/init.rc and paste the text contents on here or in a pastebin.org dump. Thanks.
IP IHI II IL said:
I'll give it a shot as soon as I get home, in about 5 minutes...
Glad to see some BIG GUNS in these threads! Thanks Matt!
EDIT: Yup... it's a bust... Here are my results:
3804 KB/s (2005736 bytes in 0.514s)
1399 KB/s (22364 bytes in 0.015s)
2873 KB/s (1468889 bytes in 0.499s)
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
Click to expand...
Click to collapse
This would mean the pushed to /data/local/tmp/ worked?
HTML:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
mattlgroff said:
This would mean the pushed to /data/local/tmp/ worked?
HTML:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
Click to expand...
Click to collapse
Will try as soon as my daughter gives me my laptop back (been hijacked for Bubble Guppies...)
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
mattlgroff said:
I want to point out something off about the build.prop....
Code:
com.motorola.debug.fddebug=true
When you run a google on this particular line you find absolutely 0 results...meaning this has not really been in build.props or anything before now. Maybe this is a clue that can lead us to something important.
EDIT: Also, I am requesting someone copy their ~/init.rc and paste the text contents on here or in a pastebin.org dump. Thanks.
Click to expand...
Click to collapse
I am trying to copy the file, but it tells me permission denied. I tried to change the permissions of the file to 777 but it just defaults back to rwxr-x--- (750). How can I copy it for you? I am using a program called Android Commander to explore the root files. Sorry if my question is ignorant/dumb. I am new to the development side of Android, but I am trying to catch on and be of help.
busarov said:
I am trying to copy the file, but it tells me permission denied. Do I need to change the permissions of the file in order to copy it? Sorry if my question is ignorant/dumb. I am new to the development side of Android, but I am trying to catch on and be of help.
Click to expand...
Click to collapse
Try to see if you can open it in the text reader and manually type it over
Sent from my MB860 using Tapatalk 2
mattlgroff said:
This would mean the pushed to /data/local/tmp/ worked?
HTML:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
Click to expand...
Click to collapse
I'm trying, but every time I enter a command, I get the adb command list... (been a while since I've used it.)
What am I doing wrong?
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
mattlgroff said:
This would mean the pushed to /data/local/tmp/ worked?
HTML:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
Click to expand...
Click to collapse
Yes, files are there. But seems there's something wrong with busybox.
This is the patch it's using
/system/bin/sh
It'll never find su in there.
Maybe razr busybox file?
Cheers
mattlgroff said:
Try to see if you can open it in the text reader and manually type it over
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Keeps failing to open. Windows doesnt recognize the file. Linux has no MTP support that I've been able to find, so I can't open the root folder there. And trying to open it in the text reader from the phone directly fails as well and it won't let me copy it to the sd card, I imagine because of it's permissions which will not change.. What else can I try?
busarov said:
Keeps failing to open. Windows doesnt recognize the file. Linux has no MTP support that I've been able to find, so I can't open the root folder there. And trying to open it in the text reader from the phone directly fails as well and it won't let me copy it to the sd card, I imagine because of it's permissions which will not change.. What else can I try?
Click to expand...
Click to collapse
My only other thought would be to "adb pull init.rc C:\Pull" like you would a system pull, even then not really sure.
IP IHI II IL said:
I'm trying, but every time I enter a command, I get the adb command list... (been a while since I've used it.)
What am I doing wrong?
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
Click to expand...
Click to collapse
When you do a command do not just do "adb" do the whole line as shown in code.
Code:
adb install App.apk
Not:
Code:
adb
install
App.apk
mattlgroff said:
My only other thought would be to "adb pull init.rc C:\Pull" like you would a system pull, even then not really sure.
Click to expand...
Click to collapse
No go. See screenshot.
mattlgroff said:
When you do a command do not just do "adb" do the whole line as shown in code.
Code:
adb install App.apk
Not:
Code:
adb
install
App.apk
Click to expand...
Click to collapse
I typed your requested commands as you did, I might need a refresher, but I'm not THAT out of practice... Lol
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
Test 2 of the XT928 root, using a Razr busybox as suggested by Pedro: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4_Test2.zip
Test 3 of the XT928 root, using a Razr busybox, AND a new mounting command, as suggested by Pedro: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/xt928rootV4_Test3.zip
I typed Matt's requested commands as he did, I might need a refresher, but I'm not THAT out of practice... Lol
Click to expand...
Click to collapse
No disrespect meant lol that's just what happens when you only type in "adb"
No go. See screenshot.
Click to expand...
Click to collapse
Shame...
mattlgroff said:
Test 2 of the XT928 root, using a the Razr busybox as suggested by Pedro:
No disrespect meant lol that's just what happens when you only type in "adb"
Shame...
EDIT: If the mounting is screwed up, use the other
Click to expand...
Click to collapse
Permission of file needs to be changed to be able to move it, but it won't let me do it without SU.
So, the debug file from earlier.. do you think that could be monitoring the system and changes we are trying to make and it's keeping them from happening? It seems if we can edit that file, we would just have to change true to false and it would disable it.. Maybe I'm on the wrong path though.
Also, tried test 2. Same result.
***************************************************************************
* *
* XT928 ╥╗╝ⁿROOT░ⁿ v4 by iopda 2012.6 *
* *
***************************************************************************
*
*
* Connect the phone and powered normally with stand USB cable.
* Make sure Setting-Developer Options-USB Debugging is enabled.
* Also make sure MTP mode is selected, NOT Mass Storage or Camera.
*
*
Press any key to continue . . .
Press any key to continue . . .
--- cleaning
--- pushing files
2679 KB/s (2005736 bytes in 0.731s)
2183 KB/s (22364 bytes in 0.010s)
2656 KB/s (1468889 bytes in 0.540s)
--- correcting busybox permissions
--- remounting /system
/system/bin/sh: su: not found
--- copying busybox to /system/xbin/
/system/bin/sh: su: not found
--- correcting busybox ownership
/system/bin/sh: su: not found
--- correcting busybox permissions
/system/bin/sh: su: not found
--- installing busybox
/system/bin/sh: su: not found
--- correcting su ownership
/system/bin/sh: su: not found
--- correcting su permissions
/system/bin/sh: su: not found
--- copying SU binary
/system/bin/sh: su: not found
--- correcting su symlinks
/system/bin/sh: su: not found
/system/bin/sh: su: not found
--- pushing Superuser app
/system/bin/sh: su: not found
/system/bin/sh: su: not found
******************************************************************************
╣º╧▓─·úí XT928 ╥╗╝ⁿROOT░ⁿ░▓╫░═Ω│╔
By iopda
******************************************************************************
ALL DONE!!!
Press any key to continue . . .
↓ A new root method! ↓
There is now a new root method, that does not require downgrade!
http://forum.xda-developers.com/showthread.php?t=2180688
↑ Read this thread first! ↑
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Step 0
Backup all your settings, and data from internal storage (!), cause factory reset (wipe) will be required.
You can try using LG's backup tool or Titanium Backup or anything else.
Also I'd strongly recommend removing SIM card and SD card from the phone.
Step 1
Make sure USB debugging is enabled (Settings -> Dev Options -> Debugging)
Connect your phone to your PC.
Execute file step0.bat and ensure that you grant su priv to ADB shell (2000).
Now execute file step1.bat - it:
- creates folder /data/rootkit
- copies busybox from /system/bin to /data/rootkit
- copies su from /system/xbin to /data/rootkit
- copies Superuser.apk from /system/app to /data/rootkit
- ensures owner and group of 0 for those files
- chmods files to required attributes (06755 for su, 0644 for apk, 0777 for busybox)
Result should be something like this: Note: In v2 i modified step1, so it tries to copy busybusybox from bin and xbin - one of them will fail, thats normal.
{
"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"
}
Step 2
Upgrade your firmware to v20a. For example: http://forum.xda-developers.com/showthread.php?t=2069723
DO NOT DO FACTORY RESET! OR YOU WILL DELETE /data/rootkit FOLDER! DO STEP 3 FIRST!
Step 3
After successful upgrade shut down your phone.
Now, with USB connected (!!), hold volume up and power, and keep holding it at least until you hear windows "new device" sound.
You must see something like this:
Now execute file step3.bat - it:
- remounts system as writeable
- copies su to /system/xbin/
- copies superuser to /system/app/
- sets permissions on those files
Step 4
Now you can hold power button to reboot or just run step4.bat to reboot instantly.
Make sure that root is working, before doing factory reset!
Now you are STRONGLY recommended to do factory reset - or many things will mess up, such as lock screen settings or storage.
AGAIN warning, that factory reset WILL wipe internal storage, look at step 0
If you did all things correct, root will be kept (because it is on ro system partition now)
Step 5
Enjoy.
Note
If you are already at v20a and you want root, you can:
1) Wait for official release, with really unlocked BL - then it will be possible to install CWM -> get root
2) Wait until I make some interaction with B&R daemon in recovery
3) Wait for someone to find easier method
4) If you dont want to wait, you can go back to v10x (warning: all data will be wiped!), root phone, and do the procedure.
Any comments, notes, criticism or anything else very welcome!
Edit: In version 2 it tries to copy busybox from /system/bin and /system/xbin, thanks to AlderCass for pointing out
Nice work friend :good:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
@non4 said:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Utterly fantastic work, and I'm sure this discovery will be the first huge step in truly unlocking this device. Congratulations!
Sent from my LG-P880 using xda app-developers app
skydev said:
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
Click to expand...
Click to collapse
Isn't adb a pain to install? At least it was back in the day when I rooted my desire z with froyo thanks for the good work I will try get this to work on my own
Sent from my LG-P880 using Tapatalk 2
Dexter_nlb said:
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Click to expand...
Click to collapse
Well, when now root is easily obtainable, you can do it
I think you are more experienced in all those things, i am low-levelly playing with phones only for 3-4 days so far.
I just dont want to trash stuff to the extent that reflash would be required.
Anyway i worked on the method almost 10 hours instead of sleeping at night, so now i think i going to go take some "Deep sleep" /10:46/
Anyway, i am noting again: if anyone also has disassembly skills, then you really should try to disassemble and analyze brd (backup and recovery daemon) - it runs at recovery with root rights, listens for commands on udp port, and probably can be used for "perfect root" (root without reflashing, and maybe even any LG device)
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Dexter_nlb said:
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Click to expand...
Click to collapse
Well, adb will be required anyway, and i want to keep freedom of choosing the su binary and Superuser.apk file.
The only requirement: su must grant root if called from recovery (when Superuser.apk is not accessible)
Also, why mess with terminal? You can easily misspell command, and they are long and important (because executed as root)
But idea with tar is good, maybe it will be required to do it this way, from B&R way.
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
postacik said:
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
Click to expand...
Click to collapse
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Click to expand...
Click to collapse
Already mentioned in first post.
lukas77 said:
Already mentioned in first post.
Click to expand...
Click to collapse
I stated that I changed the line to work "on my system".
So everybody trying this will pay attention to that...
sry for this newbie ques,
but how to install adb drivers in our device..
jitesh22 said:
sry for this newbie ques,
but how to install adb drivers in our device..
Click to expand...
Click to collapse
There are many posts on these forums on how to do this - search for them, as this thread does not deal with that.
Everything works perfect, and now i have root on my JB .
Works like a charm! Thanks so much skydev! :laugh:
I upgraded to v20a with these instructions and now I have a rooted v20a.
Thank you very much skydev.
A picture for proof: http://g1303.hizliresim.com/17/7/ktz5m.png
I think we will be able to root when new versions arrive as long as we keep the /data/rootkit folder.
Edit: I upgraded to v20a with my LG PC Suite Version Hacker ( http://forum.xda-developers.com/showthread.php?t=2134192 ) and did no factory reset after the upgrade. Everything seems to work fine upto now.
quick and dirrrrrty
thats how i like it^^
well done
AW: [TUTORIAL] Keeping root after upgrade from v10x to v20x
Worked fine. There we're no problems. Did the kdz flashing via virtual machine with windows and the rooting part on mac os x since your scripts can be easily adapted. Also i dont have to care about adb or fastboot drivers.
Gesendet von meinem LG-P880 mit Tapatalk 2
Anyone know if it is possible to root a Motorola Droid 4 running Android 4.1.2? I have seen several videos and directions online for using razr_blade but they don't seem to work and I think its because my system version is XT894.
I downloaded the latest Motorola drivers and made sure USB debugging was set to on. Yet, when running the exploit, it doesn't seem to see the device. Any ideas?
Sent from my DROID4 using xda app-developers app
cities7 said:
Anyone know if it is possible to root a Motorola Droid 4 running Android 4.1.2? I have seen several videos and directions online for using razr_blade but they don't seem to work and I think its because my system version is XT894.
I downloaded the latest Motorola drivers and made sure USB debugging was set to on. Yet, when running the exploit, it doesn't seem to see the device. Any ideas?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Different cable? My xt894 rooted just fine with RAZR blade. :-/
Sent from my DROID4 using xda app-developers app
All you need to do is make sure you are running the JB OTA update and have the latest motorola drivers. Install motocast, moto drivers from their website, whatever you can find. Assuming the drivers are okay after that, download Razr Blade, unzip the file, run the file called "run" and follow the onscreen instructions.
check your device manager, if there is yellow triangle in front of xt894
you need to update drivers
Sent from my Clear using xda premium
Thank you both for your responces. As soon as I get somewhere with internet access I'm going to try again.
Sent from my DROID4 using xda app-developers app
i also was looking for a 4.1.2 root and found the razr_blade method
and ya it worked ;=)
used this files:
https://docs.google.com/file/d/0B_nizg6yUZ0NRjVTZlQ0d1hXVVU/edit?pli=1
any tuto?
Hey everyone!
any link with razr_blade method tutorial?
I'm also at 4.1.2 using a xt894
huhu1312 said:
i also was looking for a 4.1.2 root and found the razr_blade method
and ya it worked ;=)
Click to expand...
Click to collapse
here is a video, he is rooting a razr, but same root program
http://youtu.be/XDV_72mPt4k
Try using Linux, the mod works better in Linux and use the Droid 4 JB utility,that you can find in the D4 Development forums and that should work great for you. It rooted my D4 just fine.
Sent from my DROID4 using xda premium
Help me unf*ck myself please
Using the LinuxMacUtility...
I removed the log redirects to null and found this:
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
rm failed for /data/logger/last_apanic_console, Permission denied
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
I loaded the 4.1.2 firmware per the utlity, wiped. I tried to root, no luck. Logs show the above. Is the exploit closed?
--#
try
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
or run http://vulnfactory.org/public/razr_blade.zip
in windows
Error trying to root
I'm following the instructions step by step and I have tried everything to root my Droid 4 running 4.1.2, I get stuck at phase 3 and this comes up
>failed on `/data/logger’ – Permission Denied
>mkdir failed for /data/logger, File exists
>Unable to chmod /data/logger: Operation not permitted
>link failed File exists
any help would be greatly appreciated. I already tried to clear cache and data on smart tasks, Tried to connect as media device and camera with no luck, please help.
miselonez said:
I'm following the instructions step by step and I have tried everything to root my Droid 4 running 4.1.2, I get stuck at phase 3 and this comes up
>failed on `/data/logger’ – Permission Denied
>mkdir failed for /data/logger, File exists
>Unable to chmod /data/logger: Operation not permitted
>link failed File exists
any help would be greatly appreciated. I already tried to clear cache and data on smart tasks, Tried to connect as media device and camera with no luck, please help.
Click to expand...
Click to collapse
try this
DarkMatterM4 said:
I GOT ROOT! I'm going to structure this post in such a way so that it will be easily searchable by those who are having the same problem.
The issue that I was having was that the RAZR Blade exploit was giving me the following errors when trying to root:
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File Exists
Unable to chmod /data/logger: Operation not permitted
link failed File exisits
Device: Droid 4
Network: Verizon
System: XT894
Android version: 4.1.2
What I did to solve the problem:
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
-Ran the exploit again. Went through with no errors. Upon reboot I had root access.
After I had root access, I went back to the USB computer connection and changed back to Mass Storage mode.
Thanks for all of the help you guys gave me. I really appreciate it!
Click to expand...
Click to collapse
sd_shadow said:
try this
Click to expand...
Click to collapse
Tried, still a no go, still getting the same error msgs at phase 3, I just don't get what i'm doing wrong here...sigh
did you check windows device manager?
see Driver Errors
Yes, it seems that drivers are all there, it comes up as ADB Interface, MOT composite ADB Interface.
xp, win 7, 8?
Win 7 Pro 32 bit, yes, I am admin and only user.
try a different usb port, if desktop, use rear rather than front
Tried that as well.