Develop Bugs

[How-To][tutorial] Bootloader Unlock, Custom Recovery Razr M

So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw

sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.

As long as we do this first, future OTAs can't relock our bootloaders, can they?

Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.

BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...

sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.

trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl

dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium

new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?

CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...

Does this wipe our phone
Sent from my XT907 using xda app-developers app

Nope

ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?

Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app

I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2

mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).

Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks

Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD

Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.

sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.

APK root exploit

I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit

Do you have a link to their research or are their findings private?
Regards,

Mr_Bartek said:
Do you have a link to their research or are their findings private?
Regards,
Click to expand...
Click to collapse
saurik - his analysis of the "second master key vuln"
giantpune for his symlnink attack vuln in property space:
Code:
/system/bin/mv /data/property /data/backupprop
/system/bin/mkdir /data/property
/system/bin/ln -s /sys/kernel/uevent_helper /data/property/.temp
/system/bin/setprop persist.sys.fail /data/pwn.sh

jcase said:
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.

coolrevi said:
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
Click to expand...
Click to collapse
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from

jcase said:
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
Click to expand...
Click to collapse
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!

ricky310711 said:
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
Click to expand...
Click to collapse
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely

pulser_g2 said:
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
Click to expand...
Click to collapse
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...

ricky310711 said:
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
Click to expand...
Click to collapse
It depends on if OEMs backported it, depends on which build OEMs used and depends on the bug. Four or five different zip parser bugs with similar results. This one I used was patched in 4.3, but other exist.

Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.

trickraca said:
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
Click to expand...
Click to collapse
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two

jcase said:
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
Click to expand...
Click to collapse
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..

giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
It should not come rooted, if it comes rooted then no way did it pass CTS. I'm guessing unlocking the bootloader and flashing a recovery? I don't know, I dont have one

giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk

noobish doubts..
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Please i ne ed a walthrough..
1) download twrp
2) put it in root of the telephone robot
3) flash it in recovery?
4) reboot recovery wipe cache and dalvik flash omnirom..
Please correct me..
Thank you

giuliano rigon said:
1) download twrp Yes
2) put it in root of the telephone Yes
Make sure to copy Omnirom to your phone at some point
3) flash it in recovery? No - Flash TWRP in Fastboot if you haven't flashed the recovery already. Use the official Teamwin site for guidance
4) reboot recovery wipe cache and dalvik flash omnirom.. Wipe Cache, Dalvik, System, and Data
Click to expand...
Click to collapse
Updates in Red
This is off-topic for this thread though. Questions/Info for flashing Omnirom should be addressed in the Omnirom thread.

Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks

nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.

not rooted.. confirm i can flash
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
I nave tried my damnedest to root .. Fastboot flashing supersu flashing from recovery Direct install from google play complete unroots and reflash letting recovery do it .. No way..
So now i need a last confirmation.. Can i flash omnirom after wipes even if i am unrooted.. And has anyone rooted omnirom or does it come unrooted.. Thanks for the info .. Another idea.. Flashing color OS footing and then flashing omni.. Or is this a late night bad Dream..
---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------
Harfainx said:
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
Click to expand...
Click to collapse
Sorry now i got it.. It was in the forums.. Just unchecking the respect cyanogen settings in the super su menu got me roooted and happy.. Sorry for your time.. I flashed super su zip from recovery rebooted and unchecked .. Now i am set..

I were rooted myN1 in yesterday, its really good . thankss
Sent from my N1 using XDA Premium 4 mobile app

[Q] Reboot fix not working for Xperia M dual C2004 build 15.2.A.2.5

I want to swap internal-external sdcard or mount folder app so that I can play big games with large data. For this, I rooted my phone with Impactor, and tried remount reboot fix by NUT and reboot fix by Anto Kus. But till now the phone reboots on using folder mount. Also my phone reboots while using a dual partitioned sdcard to use it with Link2sd. I have tested root checker which shows phone is rooted. I am using Titanium Backup without any problems. Should I go for bootloader unlock?
My phone xperia m dual c2004, 4.2.2, build 15.2.A.2.5.
Thanks

Sri007 said:
I want to swap internal-external sdcard or mount folder app so that I can play big games with large data. For this, I rooted my phone with Impactor, and tried remount reboot fix by NUT and reboot fix by Anto Kus. But till now the phone reboots on using folder mount. Also my phone reboots while using a dual partitioned sdcard to use it with Link2sd. I have tested root checker which shows phone is rooted. I am using Titanium Backup without any problems. Should I go for bootloader unlock?
My phone xperia m dual c2004, 4.2.2, build 15.2.A.2.5.
Thanks
Click to expand...
Click to collapse
Follow this guide step by step and dont forget to install busybox read carefully this guide
to play games i suggest you to install folder mount its better than swapping gl to sd n all
http://forum.xda-developers.com/showthread.php?t=2523597

Anmol0022 said:
Follow this guide step by step and dont forget to install busybox read carefully this guide
to play games i suggest you to install folder mount its better than swapping gl to sd n all
http://forum.xda-developers.com/showthread.php?t=2523597
Click to expand...
Click to collapse
I had already installed busybox and followed the procedure shown in the thread. The busybox is supported but inspite of root access, I can't change permissions in system files as a result the reboot fix is not working. Somewhere I read unlocking bootloader will help. Is it?

yes u must unlock bootloader for use full root access like change permission etc

mahithlal said:
yes u must unlock bootloader for use full root access like change permission etc
Click to expand...
Click to collapse
No, you don't need to unlock your bootloader to get full root access. Try this updated version of the reboot fix and then you're fully rooted...
Unlocking your bootloader will give you full root access without using root tools, exploits, etc., but many proprietary Sony apps will not work anymore because your DRM keys will be wiped when you unlock the bootloader...

mahithlal said:
yes u must unlock bootloader for use full root access like change permission etc
Click to expand...
Click to collapse
I have already backed up bootloader using TA backup and got bootloader key from Sony website. But can I claim warranty, if I restore locked bootloader? Or warranty is void, not reversible.

Unlocking your bootloader will give you full root access without using root tools, exploits, etc., but many proprietary Sony apps will not work anymore because your DRM keys will be wiped when you unlock the bootloader...[/QUOTE]
Ya, I know about the cons of unlocking bootloader. Thats why I am still waiting for other ways. I have also tried the fix by NUT from the forum which u gave link but still not fully rooted as it is unable to write in system folder. But other root operations like removing bloatware is done without any problems. Thats strange. Busybox is installed by NUT which supports part of the fix but the other scripts did not work in system.
By the your xm dual c2004 was updated to build 15.2.A.2.5 or is it from out of box like mine?

What script is basically not working

Anmol0022 said:
What script is basically not working
Click to expand...
Click to collapse
The scripts in the fix tool like killswitch.sh, etc. which needs to run to avoid reboot while mounting.

Sri007 said:
The scripts in the fix tool like killswitch.sh, etc. which needs to run to avoid reboot while mounting.
Click to expand...
Click to collapse
Well have not tried that but after rooting using that guide was able to use folder mount

Anmol0022 said:
Well have not tried that but after rooting using that guide was able to use folder mount
Click to expand...
Click to collapse
Is your phone same model and build like mine? I think it is due to the build version.

Sri007 said:
Is your phone same model and build like mine? I think it is due to the build version.
Click to expand...
Click to collapse
yes its same build 15.2.A.2.5
Stock Rom
If not working then you may update it via sony update service and reset phone
then follow guide again to root
According to guide use the same busybox as mentioned open and install it
or try from beggining again
Here are steps
use injector
install super su from google play
open and use super su
and install it binaries
install busy box x as mentioned
then open it and install allow root access if asked
then use reboot fix by NUT
follow cmd guide
and allow adb when ask permission
then phone will reboot
Then its written wait to check fix
And then its done press continue
done
use folder mount have fun
then

My C2004 also have full root access with locked bootloader, just updated to 15.2.A.2.5 through Sony Update Service, used Cydia Impactor, installed SuperSU from Play Store and then ran the script I linked to you. After all I have full root access, can remount system without problems and my bootloader still locked...

Anmol0022 said:
yes its same build 15.2.A.2.5
Stock Rom
If not working then you may update it via sony update service and reset phone
then follow guide again to root
According to guide use the same busybox as mentioned open and install it
or try from beggining again
Here are steps
use injector
install super su from google play
open and use super su
and install it binaries
install busy box x as mentioned
then open it and install allow root access if asked
then use reboot fix by NUT
follow cmd guide
and allow adb when ask permission
then phone will reboot
Then its written wait to check fix
And then its done press continue
done
use folder mount have fun
then
Click to expand...
Click to collapse
I have again followed the procedure as you mentioned. Everything worked except the fix. While waiting to check the fix, the phone reboots again. I am attaching the snapshots of the terminal window from which you may know the problem.

Its seems that is problem of busy box Bcoz it should show something like this

Anmol0022 said:
Its seems that is problem of busy box Bcoz it should show something like this
Click to expand...
Click to collapse
Ya, I know I have seen in a tutorial video on youtube. So, what's the solution you think? Which version of Busybox are you using?

Sri007 said:
Ya, I know I have seen in a tutorial video on youtube. So, what's the solution you think?
Click to expand...
Click to collapse
Well after installing busy box you have to open the app then in app you have to click install something like that have you done it

Anmol0022 said:
Well after installing busy box you have to open the app then in app you have to click install something like that have you done it
Click to expand...
Click to collapse
Ya, I have installed in normal mode busybox version 1.21.0, but on using the fix, it was replaced with busybox version 1.20.2-jb which support nohup or something. Which version of Busybox have you installed?

Sri007 said:
Ya, I have installed in normal mode busybox version 1.21.0, but on using the fix, it was replaced with busybox version 1.20.2-jb which support nohup or something. Which version of Busybox have you installed?
Click to expand...
Click to collapse
The same as mentioned from google play
Busy Box X by Robert
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
Download it again
from above link install it open it install then try fix again

Anmol0022 said:
The same as mentioned from google play
Busy Box X by Robert
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
Download it again
from above link install it open it install then try fix again
Click to expand...
Click to collapse
I tried to download it but the play store says it is not available in your country. Can you send me the apk?

Spend all night trying to root.

I have a LG optimus g pro at&t unlocked and updated to 4.4.2. Spend all night trying to root. i get the following error
"adbd cannot run as root in production builds error: device not found " Tried on 2 different pc's, same result. Any ideas? Thanks guys.
got it to root somehow, how can i get clockworkMod Recovery now?

You can root with:
POOT: This app is a one click root app. No computer needed
Framaroot: Framaroot is a oneclick root app . No computer needed
This is the most popular one!
Z4Root: Z4Root is an oneclick root app . No computer needed
Towelroot: Towelroot is an oneclick root app. No computer needed
Baidu: No information
Vroot: No information
Gingerbreak: This app can root almost all gingerbread devices
Downloads:
Poot - Download the app >>here<<
Framaroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Z4ROOT - Download the app inside this XDA Thread - >> CLICK HERE <<
Towelroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Baidu ROOT - Download the app >> HERE <<
vROOT - Download the app >> HERE <<
Gingerbreak - Download the app inside this XDA Thread - >> CLICK HERE <<
Flash a SU ZIP - Download the ZIP >> HERE << and flash it on your unlocked bootloader phone !
Hit thanks if you liked this post or this post has helped you out !

wowmk1 said:
I have a LG optimus g pro at&t unlocked and updated to 4.4.2. Spend all night trying to root. i get the following error
"adbd cannot run as root in production builds error: device not found " Tried on 2 different pc's, same result. Any ideas? Thanks guys.
got it to root somehow, how can i get clockworkMod Recovery now?
Click to expand...
Click to collapse
Start your device by pressing volume+ and power and hold it until the screen gets black. Release both buttons and press volume-
It works for me every time.

I too received the same message when I tried to root. Something had to do with att locking boot.img. Use a program called rootmaster to root my phone.
Sent from my LG-E980 using XDA Premium 4 mobile app

wowmk1 said:
I have a LG optimus g pro at&t unlocked and updated to 4.4.2. Spend all night trying to root. i get the following error
"adbd cannot run as root in production builds error: device not found " Tried on 2 different pc's, same result. Any ideas? Thanks guys.
got it to root somehow, how can i get clockworkMod Recovery now?
Click to expand...
Click to collapse
I realize that this post is nearly one month old, but I rooted using Towelroot(only works if you haven't updated to the latest firmware from AT&T) mentioned above, and then used the method that chappatti found [here](http://forum.xda-developers.com/showpost.php?p=52945705&postcount=1) to install the custom CWM.
Of course, if you want TWRP, you can always use FreeGee in the play store to install that easily.

wowmk1 said:
I have a LG optimus g pro at&t unlocked and updated to 4.4.2. Spend all night trying to root. i get the following error
"adbd cannot run as root in production builds error: device not found " Tried on 2 different pc's, same result. Any ideas? Thanks guys.
got it to root somehow, how can i get clockworkMod Recovery now?
Click to expand...
Click to collapse
Tambuyeye said:
Let me first thank the forum for helping me root my E98020g and for the files. Ok so all the info is here on the forum but not really in one place. i cant remember where exactly to find them so im a just put the instructions and files up for you and everyone else. hope this helps.
1. Use roottool.kitkat to root the device (unzip>>run the "startroot.bat" file thats in the folder>>and follow the instructions.)
2. After device is rooted and reboot place SuperSU, GPRO_Recovery and FreeGee apks on the device
3. Install SuperSU, GPRO_Recovery and FreeGee apks
4. Run the now installed app GPRO_Recovery and select "Flash Kitkat Recovery for G Pro". WHEN ITS DONE DONT REBOOT .
5. Now run the already installed app FreeGee and install CWM-6.0.4.7 or TWRP, when its done u can reboot to recovery to check.:good:
Click to expand...
Click to collapse
Here try this and see what happens. the 6th post down on this link has the files for the job http://forum.xda-developers.com/showthread.php?t=2558697&page=90

HTC One M8: Root/Bootloader Unlocking failed? "No SU binary"

Root/Bootloader unlocking failed? "No SU binary"
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back) and tried to root and unlock the bootloader but failed so I just stored it away .
I followed these videos. Can't paste links...new xda account:
youtube:
HTC One M8 : How to Unlock Bootloader & Root - Easiest Method
HTC One M8 : How to Root & Install TWRP Recovery - Easiest Method
I believe the first video, unlocking the bootloader, was successful(says "Software status: Modified""**Unlocked**" in bootloader mode).
In the second I believe TWRP was installed successfully (It opens up via Recovery) but the SuperSU app was not successful . I don't remember exactly what happened (it was months ago) but when I hit the SuperSU app I think it failed to update as seen in the second video at 2;29. As of today, when I try to open SuperSU, I'm presented with a message that says: "There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root" hit ok and SuperSU closes.
I found various fixes and such but I'm not sure which is the safest.
Sorry I'm new to android and I just don't want to ruin my device.
SOLVED
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Delete this thread I guess.

If you used the toolkit as shown in the Youtube video, that was your main problem.
The toolkit uses obsolete (and by obsolete, I mean over a year) versions of both:
SuperSU (current version is 2.46)
TWRP (current version is 2.8.7)
Using outdated versions of either/both of these with a stock Lollipop M8 will cause some major issues. Before doing any mods, its best to read and research to make sure you are using the most up-to-date procedures and files. Youtube should not be your only modding resource. Also, keep in mind that the "easiest" way, is not necessarily the "best" way.
huura said:
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Click to expand...
Click to collapse
Making a TWRP backup before flashing anything would have minimized any risk.
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
huura said:
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back)
Click to expand...
Click to collapse
M8x is the Taiwanese, higher CPU clocked variant.

That makes sense. Thanks for all the info. woo slightly higher clock speed variant!
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?

huura said:
T woo slightly higher clock speed variant!
Click to expand...
Click to collapse
On a side note. Only thing to be aware of, the M8x can't have other versions' radios flashed to it, even with s-off; as confirmed by a few users here (including one very knowledgeable one).
By extension, this probably also means that you can't "convert" to another version by running that version's RUU.
Probably not a major issue, as all other common mods (TWRP, root, flashing custom ROMs) should work fine on the M8x. Just something to keep in mind.
huura said:
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Click to expand...
Click to collapse
My advice would be to learn how to use fastboot to install TWRP, and skip the pointless middle man apps. Doing it by fastboot is easy, and much more reliable.
huura said:
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
Click to expand...
Click to collapse
No benefits that I know of. 2.46 roots the phone (on Lollipop) just fine, no need to have any "benefits" beyond that.
Marshmallow is a different story.

Ah ok. I'll keep note of that quirk, thanks.
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?

huura said:
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
Click to expand...
Click to collapse
Its a good trick to know (as well as other fastboot commands) as it allows you to flash recovery without a working OS (not an unheard of situation, if you mess with flashing ROMs and other things enough times).
The process is pretty simple, as you most likely already have fastboot setup on your computer if you unlocked the bootloader. So flashing a recovery is simply a matter of:
1) Download the desired recovery .img to your fastboot folder (where fastboot.exe is located)
2) Connect your phone to the computer, and boot into bootloader-fastboot mode
3) Open a command prompt on the computer
4) Issue the proper fastboot command
5) Drink beer
huura said:
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
Click to expand...
Click to collapse
I haven't messed with Xposed for a while, but I think you just need to:
1) Make a nandroid of your current working setup
2) Install the Xposed apk
3) Open the Xposed app and install the desired frameworks

Figured it out, was straight forward