[TOOLS] R3L3AS3DRoot and 43V3R root for the BIONIC v2.1

[spooner2007]

It wont root my phone.

Run root app as admin, keeps saying its not a valid command when i try to run option 2. So i run option 1, it wiped/formatted it, then tried to root same issue as option 2. If i dont run it as admin, it says starting daemon server thing, and just gets stuck there. Ill post pic up soon. Anyone else run into this?

-Mithu

What os are you running?

Sent from my DROID BIONIC using DroidForums

 

[mithu]

What os are you running?

Sent from my DROID BIONIC using DroidForums

Win7 x64.

Phone shows up, wheni run adb devices in cmd.

 

[spooner2007]

ive used it a couple of times... im going to re run through it because i had a few problems fingering it out also... make sure that the tool is in a folder on your desktop also... lastly your phone has to be, not recovery the other one... power off... hold the volume down... and the hit the power button... flash mode (fastboot) is how you use this...

 

[mithu]

ive used it a couple of times... im going to re run through it because i had a few problems fingering it out also... make sure that the tool is in a folder on your desktop also... lastly your phone has to be, not recovery the other one... power off... hold the volume down... and the hit the power button... flash mode (fastboot) is how you use this...

Yeah the folder is on desktop, and i know about fastboot. I was saying that i went all through that, it did the first part (wiping), but when it came down to rooting, it either got stuck or said not a valid command.

 

[captainflowers91]

Error Message

I'm trying to use this on Ubuntu 10.10. I keep getting an error message. What program should I open it with in Ubuntu? (the default for it is Wine for some reason)

 

[TheJester34]

Like a charm. Thanks for the work!

 

[chedder72]

I received and installed the 5.5.893 OTA upgrade today. I was on Purity with 5.7.893 but restored my phone back to stock, rooted. After I installed the OTA I lost root. Is there any way known right now to get my phone rooted once again? I tried using this tool and followed the instructions to a T and I receive the errors below. Thanks in advance for your help!
View attachment 43396View attachment 43397

 

[Cinoib]

took the update 5.5.893

I downloaded the r3l3as3droot. I looked at it. I want to regain root. I was rooted (SuperOneClick) or maybe Pete's. Anyway, I lost root when I installed the update (yes, I know, if forgot to use Permaroot). If I use this root will I retain the update or do I have to step back to 5.5.886? It looks like from the options that I'll return to the former.

Plus if there are further updates from Moto and Verizon, will I have to do this until finally I get to Ice Cream Sandwich?

 

[Valkor_Raptus]

Also took update 5.5.893 and lost root

I also updated to from 5.5.886 to 5.5.893 (while rooted from Pete's OneRootClick) and lost root. I, too, did not have "forever root" or "PermaRoot" and have been trying for the last 12 hours to regain root while remaining on 5.5.893. Argh!!! I have tried Pete's root tools v1.02, v1.05, v1.07, and R3L3As3Droot (option #2), but get the same error as rooting unsuccessful.

Is my only option to revert back to 5.5.886 stock, wipe all cache & data, then re-root? Please help.....I'm so frustrated. I attempted trying the whole adb shell tweek method for adding those lines: rm /data/local/root/local.prop &
rm /data/root/local.prop, but I don't know enough to get cmd to recognize device from cd androidsdk\platform-tools & adb devices. Mainly, I want to know is the solution to revert back to 5.5.886 stock, wipe cache/data, then re-root?

Thanks for any help!

 

[chedder72]

I also updated to from 5.5.886 to 5.5.893 (while rooted from Pete's OneRootClick) and lost root. I, too, did not have "forever root" or "PermaRoot" and have been trying for the last 12 hours to regain root while remaining on 5.5.893. Argh!!! I have tried Pete's root tools v1.02, v1.05, v1.07, and R3L3As3Droot (option #2), but get the same error as rooting unsuccessful.

Is my only option to revert back to 5.5.886 stock, wipe all cache & data, then re-root? Please help.....I'm so frustrated. I attempted trying the whole adb shell tweek method for adding those lines: rm /data/local/root/local.prop &
rm /data/root/local.prop, but I don't know enough to get cmd to recognize device from cd androidsdk\platform-tools & adb devices. Mainly, I want to know is the solution to revert back to 5.5.886 stock, wipe cache/data, then re-root?

Thanks for any help!

Theres a one click that works after u do the ota without forever. Its by P3Droid. It's over in bionic tech support under the thread named .593 lost root or something like that. I was in ur position too and im all better now.
Check my recent posts.

Sent from my DROID BIONIC using DroidForums

 

[icoblue]

Questions Regarding 43V3R Root

Ok, so I have read every post on all 25 pages of this thread, and I am not new to the root world. I only have two questions before I use this tool;

1. What is the likelihood of Moto/VZW "patching" the 43V3R Root method at any point in the future?

2. Is there any method by which a user can reverse the changes made by the 43V3R Root method for, say, warranty replacement of a device?

I apologize if either of these is covered elsewhere, but I did not find these answers in the places I considered most likely.

 

[thunderjcm]

Ok, so I have read every post on all 25 pages of this thread, and I am not new to the root world. I only have two questions before I use this tool;

1. What is the likelihood of Moto/VZW "patching" the 43V3R Root method at any point in the future?

2. Is there any method by which a user can reverse the changes made by the 43V3R Root method for, say, warranty replacement of a device?

I apologize if either of these is covered elsewhere, but I did not find these answers in the places I considered most likely.

Not likely to be patched as of the latest release from moto. And the method has a remove root feature so yes this is the best way to root your phone.

Sent from my ROOTED BIONIC 5.7.893

 

[Valkor_Raptus]

Theres a one click that works after u do the ota without forever. Its by P3Droid. It's over in bionic tech support under the thread named .593 lost root or something like that. I was in ur position too and im all better now.
Check my recent posts.

Sent from my DROID BIONIC using DroidForums

Wow chedder72 - you saved me! Your referral to the "5.5.893 root lost" thread and downloading the "root exploit" link from tp76 did the trick in only 10 minutes! Didn't even have to revert back to stock 5.5.883. Wish I would have reached out sooner (could have saved an entire day and wife would not have felt so ignored as my focus has been on fixing this issue)!

I'm all great now and I hope this advise will also help the next poor soul. Thanks Again!

 

[icoblue]

Not likely to be patched as of the latest release from moto. And the method has a remove root feature so yes this is the best way to root your phone.

So I am now 43V3R Root-ed. I do not, however, see an option in the R3L3AS3DRoot program to remove the 43V3R Root. I would assume you were referring to a full system recovery using the stock 5.5.886 which would remove both the base root files and the modified mount_ext3.sh file, to a factory condition, correct? Wouldn't that make it, then, a semi-permanent root? What's to stop Moto from integrating that fix into the next OTA? I don't want to sound ungrateful, I appreciate all the hard work from people much more dedicated than myself. I would just like to know where I stand and my options for the future.

BTW, I went to verify the 43V3R Root, and within the mount_ext3.sh file, the desirable lines (at the end) read as follows:

chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk

*These lines will [chmod] change the file permissions of your [/bin/su , /xbin/su , /app/Superuser.apk] files to [4755] full read/write capability*

 

[thunderjcm]

So I am now 43V3R Root-ed. I do not, however, see an option in the R3L3AS3DRoot program to remove the 43V3R Root. I would assume you were referring to a full system recovery using the stock 5.5.886 which would remove both the base root files and the modified mount_ext3.sh file, to a factory condition, correct? Wouldn't that make it, then, a semi-permanent root? What's to stop Moto from integrating that fix into the next OTA? I don't want to sound ungrateful, I appreciate all the hard work from people much more dedicated than myself. I would just like to know where I stand and my options for the future.

BTW, I went to verify the 43V3R Root, and within the mount_ext3.sh file, the desirable lines (at the end) read as follows:

chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk

*These lines will [chmod] change the file permissions of your [/bin/su , /xbin/su , /app/Superuser.apk] files to [4755] full read/write capability*

Moto did patch this exploit in the patch. 893 and then unblocked it in. 894 as with any root/mod of your phone you do it at your own risk, and that would include future dev or the lack of. Most of the time when it has been patched, a new way is found. Just depends on who is still dev on this model. I would caution you or anyone else to only use the official OTA updates as you can end up in the boat I am in, and be stuck at the last leaked version with no way to get the official patched update.

Sent from my ROOTED BIONIC 5.7.893