FORUMS

Which Lockscreen Security Type Do You Use?

From pattern locks to the controversial face unlock, there are a number of different ways you … more

Xposed 3.0 Alpha 3 Released

A new alpha for the Xposed framework is out and brings several bug fixes. You’ll only need to flash … more

XDA Recap: This Week In Android (Apr 18 – 25)

Here in the digital XDA newsroom, we spend our days pouring over an average of … more

Sunday Debate: Custom ROMs vs. Modular Tweaks

Join us in a fun Sunday Debate on Mods and ROMs. Come with your opinions and feel free to … more
Post Reply Subscribe to Thread Email Thread

[Root/Write Protection Bypass] Droid Ultra/Maxx/Mini

15th September 2013, 12:00 AM |#1  
jcase's Avatar
OP Forum Moderator / Senior Recognized Developer - Taco Vendor
Flag Sequim WA
Thanks Meter: 10,376
 
Donate to Me
More
Warning:
I will not be responsible for damage to your device(s) by using this exploit. Antivirus software and Play services will likely detect this as potentially malicious. It is an exploit, deal with it or don't use it. Do not mirror these applications without my permission!


PwnMyMoto is a replacement for my previously released MotoRoot. PwnMyMoto exploits three vulnerabilities, to gain root access, then to gain write to system. This is a traditional root, and doesn't use any 'hackery' to maintain su access unlike MotoRoot.

First we use bug 9695860 (aka second masterkey) to gain system user, then it uses a symlink attack to gain root access. After gaining root we exploit a flaw in the bootloader, allowing us to bypass the write protection applied to system. In the process we remove stock recovery, so OTAs will not be a worry.

Install PwnMyMoto by running:
Quote:

adb install -r PwnMyMoto-<version and model go here>.apk

Then run PwnMyMoto, depending on the current root status of your phone it will reboot 2 or 3 times, after the last reboot it will uninstall it self and su will be installed on the actual system partition. Please install SuperSu from the market after this step is done.

We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.

After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.

The exploit will uninstall itself after successful exploitation.

To see if write protection is applied, you can run:
Quote:

adb shell getprop ro.boot.write_protect

If it returns '1' then write protection is applied to /system, if it returns '0' then no write protection has been applied.

In the future we will have a replacement recovery, but at this time it is still in development. Enjoy.

Change Log:

1.4.3 allows detection of failed su installation (0 size su) and reinstallation)

1.4.1 adds reliability, and fixes issues for users when improper permissions are applied to su (Preventing updates).

1.2 - Bug fix for devices which had recieved OTAs.

If you used 1.1 and have a problem with recovery coming back, run the following command:
Quote:

adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"

1.1 - initial release
Attached Files
File Type: apk PwnMyMoto-1.4.3-Droid.apk - [Click for QR Code] (309.2 KB, 53502 views)
Last edited by jcase; 18th September 2013 at 03:36 PM.
The Following 44 Users Say Thank You to jcase For This Useful Post: [ View ]
 
 
15th September 2013, 12:09 AM |#2  
Member
Flag Lexington Park
Thanks Meter: 19
 
More
Thanks!
15th September 2013, 12:15 AM |#3  
Recognized Contributor
Flag Florida
Thanks Meter: 2,981
 
Donate to Me
More
Figure I should add that this does not allow usage of custom kernels at this time because everything is still signature checked.
The Following User Says Thank You to Indirect For This Useful Post: [ View ]
15th September 2013, 12:33 AM |#4  
Senior Member
New York, NY
Thanks Meter: 104
 
More
Is there an unroot process?
15th September 2013, 12:52 AM |#5  
Senior Member
Thanks Meter: 342
 
More
Quote:
Originally Posted by alee

Is there an unroot process?

I'd assume you could boot into the recovery mode and just delete superuser, su, and busybox, but someone more knowledgeable should confirm.

Sent from my Nexus 7
15th September 2013, 01:29 AM |#6  
Member
Thanks Meter: 20
 
More
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out
The Following 2 Users Say Thank You to Dr. Carpenter For This Useful Post: [ View ]
15th September 2013, 01:36 AM |#7  
mbh87's Avatar
Senior Member
Flag Idaho
Thanks Meter: 1,539
 
Donate to Me
More
Quote:
Originally Posted by Dr. Carpenter

Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out

It probably didn't work for you then. I was having the same problem earlier and again now.
15th September 2013, 01:38 AM |#8  
Member
Thanks Meter: 20
 
More
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.

Sent from my XT1080 using Tapatalk 4
The Following 2 Users Say Thank You to Dr. Carpenter For This Useful Post: [ View ]
15th September 2013, 01:39 AM |#9  
mbh87's Avatar
Senior Member
Flag Idaho
Thanks Meter: 1,539
 
Donate to Me
More
Quote:
Originally Posted by Dr. Carpenter

I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.

Sent from my XT1080 using Tapatalk 4

It shouldn't boot to recovery since it is being replaced.
15th September 2013, 01:43 AM |#10  
Member
Thanks Meter: 20
 
More
Sorry, meant when booting to "recovery". It went to the no command screen for a minute then rebooted to Android.

Sent from my XT1080 using Tapatalk 4
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes