• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [EXPLOIT] Root DX GB without 2-part or AIO TBH files....One-click method now included!!!

AdjBrightness works, and so does Light Flow, to turn the lights off. Unfortunately, Light Flow and BattMonX don't seem to play well together, or at least act tetchy at times.

LOL, yeah, you'd have to turn off the LED Notifications setting in BattMonX to allow Light Flow to have control of the LEDs, and just use BattMonX for the notification status bar icon.

Too many cooks in the kitchen, so-to-speak, when you have two apps that both want to use these FIFO resources (i.e., the LED). The non-root mode of my app should work okay with Light Flow, but you wouldn't necessarily know which app has turned on the LED for what function.

Cheers!
 
I had this same issue, I had Z4 in froyo, and with the 604 ota I was unable to get root in this method.

However I was able to use the abd shell and remove the old SuperUser.apk and the su and busybox from their locations.

Then re-run the one click and gain root.

Open the abd shell - Click start, run, and type cmd - this will open a command prompt.
Navigate to the location of your one click root (ie C:\Users\User\Desktop\MotorolaOneClickRoot_psouza4) and type: abd shell
If you have root in the abd shell you will see # prompt

Type:
rm /system/apk/SuperUser.apk
rm /system/bin/su
rm /system/bin/busybox

Note: If you still see superuser in your menu after this use the lower case version instead: rm /system/apk/Superuser.apk

Then re-try the one click root and see if you then have root access.

This process worked for me, I hope that you can get it to work for you as well.

I'm stuck. I tried everything I could find. I ended up with what I thought was success using petes xp version. I had to unplug remove battery and manual power up when each reboot froze. after the 3rd in process it said you should now have root. I try to open titanuim but says no root. i dont know how to use the abd shell above. please help. i was on the two part flash with root for ginger before. I see the files in the download but when i click on them in windows the abd just flashes the black command screen and disappears. Thanks ... Cruzrock
 
Worked flawlessly for me....I was on .596, so i sbfed to 4.602 and ran the 1 click root,was done with both in under 20 minutes.....flawless install...
 
flashed the .602 sbf. Worked fine.

The 1 click root did not. I couldn't get it to recognize my phone to begin with. I gave up

Re sbf'd to 340, went to .602 aio and am back. Frustrating.
 
Steven, did you have it in Charge Only mode when connected? I had that problem when I first tried and then changed the connection setting to Charge Only and it picked my phone up right away.

Now that we have a .602 SBF this root method will take SBFing back to .340 out of the steps!
 
Steven, did you have it in Charge Only mode when connected? I had that problem when I first tried and then changed the connection setting to Charge Only and it picked my phone up right away.

Now that we have a .602 SBF this root method will take SBFing back to .340 out of the steps!

Somehow, I KNEW someone was gonna ask that question. Yeah, I had it in "charge only" mode. I don't know why it wouldn't recognize my phone. Did the rooting app folder have to be in C:\? I had it on my desktop. I'll bet that was it.
 
I was running the .596 rooted version from the long way that was posted previously. All I had to do was SBF back to froyo and do a clean install. I just restored the phone and it is perfecto. Thanks for this, my phone has been trying to update over the past few days haha.

EDIT: I restored and it went back to .596, going back over it again
used D2 bootstrap, noob fail.


**Well everything seemed fine until I restored under bootstrap, I will try again tomorrow night, too tired for this haha.
 
So, I don't need to sbf back? Im running liberty, and don't want it anymore... with this new root method, how do I get rid of it?
 
Time to fess up. I had trouble rooting 602. Wanna know why? I FORGOT TO SELECT DEBUGGING! DOH! Just in case anyone has trouble? Don't forget this step. I guess it's been a long time since I've rooted. With P3's AI0's, they enabled me and made me forget how to do it! ;) (It's always someone else's fault, right?) :p
 
Time to fess up. I had trouble rooting 602. Wanna know why? I FORGOT TO SELECT DEBUGGING! DOH! Just in case anyone has trouble? Don't forget this step. I guess it's been a long time since I've rooted. With P3's AI0's, they enabled me and made me forget how to do it! ;) (It's always someone else's fault, right?) :p

And to go along with this statement. I could not boot into recovery because i did not UNCHECK debugging prior to trying to reboot.
 
Hey steve..which roms are availabe for users who have oem 602 rooted? The rom/theme list seems to be divided into sections pending which version you have rooted(?)
 
Time to fess up. I had trouble rooting 602. Wanna know why? I FORGOT TO SELECT DEBUGGING! DOH! Just in case anyone has trouble? Don't forget this step. I guess it's been a long time since I've rooted. With P3's AI0's, they enabled me and made me forget how to do it! ;) (It's always someone else's fault, right?) :p

I was wondering if you were going to let the cat out of the bag or not :p
 
Hey steve..which roms are availabe for users who have oem 602 rooted? The rom/theme list seems to be divided into sections pending which version you have rooted(?)

As I understand it, cm7 has a 2nd init rom for gb now, only. I'm on it. It's smooooooooooooooooooth.
 
I had this same issue, I had Z4 in froyo, and with the 604 ota I was unable to get root in this method.

However I was able to use the abd shell and remove the old SuperUser.apk and the su and busybox from their locations.

Then re-run the one click and gain root.

Open the abd shell - Click start, run, and type cmd - this will open a command prompt.
Navigate to the location of your one click root (ie C:\Users\User\Desktop\MotorolaOneClickRoot_psouza4) and type: abd shell
If you have root in the abd shell you will see # prompt

Type:
rm /system/apk/SuperUser.apk
rm /system/bin/su
rm /system/bin/busybox

Note: If you still see superuser in your menu after this use the lower case version instead: rm /system/apk/Superuser.apk

Then re-try the one click root and see if you then have root access.

This process worked for me, I hope that you can get it to work for you as well.

rm /system/app/SuperUser.apk
rm /system/app/Superuser.apk

No apk directory for me DX
 
Now someone should make an apk that will implement this without a computer and I'd be set lol

LOL, I tried making an app for this...the issue is that the exploit requires using a shell started-up via adb to make it work.

I had an idea to emulate and adb client that works wirelessly, but I'm pretty sure you can only enable this when you are rooted (i.e., a catch-22 situation).

I haven't given up on the idea, but its looking like you'll only be able to do this on the PC for now.

Cheers!
 
Back
Top Bottom