• 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!!!

It looks like it has root, but a lot of root functions dont seem to work. Titanium, wireless tether, bootstrap.

So apparently after researching it seems I can't really get root because I had an old superuser on my phone from .596 root.
Now the problem is I cannot delete it(old superuser) or flash a new one because I am not rooted.
Any ideas or am I gonna have to sbf?
 
Upvote 0
It worked perfectly! I didn't realize how much I missed having root. Thanks to all who found / posted / helped with this exploit!

I'm with you. I had root on Froyo with Z4, but got rid of it when we got GB. I didn't bother with the "long way" to root on GB. But when I saw this, I figured WTH. Worked without a hitch and now I can dig deeper into my phone. It would be great if Scary Alien can get a 1-click going for others!!
 
  • Like
Reactions: scary alien
Upvote 0
I'm with you. I had root on Froyo with Z4, but got rid of it when we got GB. I didn't bother with the "long way" to root on GB. But when I saw this, I figured WTH. Worked without a hitch and now I can dig deeper into my phone. It would be great if Scary Alien can get a 1-click going for others!!

Thanks...I'm trying :).

I got the app to where I thought I could actually test it on someone's phone last evening. I had my son come over after he got off work with his Droid 2 Global so I could test it out, but I forgot that he's still on Froyo, so I had him start searching for a GB leak for his phone while I did some final prep on the app.

That's when I realized that there's that one little step of getting the su program installed via the adb shell that is the hang-up. I've got a couple of ideas I'm working on and researching, but I understand why no one else has come out with an on-phone solution to this.

Anyway, I'll have my son's fresh, unrooted GB phone to play with later this afternoon, so hopefully a work-around / solution to my hang up can be found.

Cheers!
 
  • Like
Reactions: jaydubbs
Upvote 0
Will I have to reinstall all my apps if I root? Also, what precautions should I do before rooting (like backing things up)? Sorry for the newb questions

Vinnie,

Well, just gaining root access / privileges doesn't really change too much on your phone other than adding a few files (specifically, the su program that lives in /system/bin/su or /system/xbin/su that actually gives you the root privileges, a busybox utility (basically a toolkit of useful commands), and the Superuser.apk application which helps manage which apps are allowed to gain root access).

Its what you do after you root than matters. You certainly want to be knowledgeable and aware of the impact of using your new root powers (such as running root-only apps, installing a custom recovery so you can flash new custom ROMs, etc.) so that you don't take any action that could adversely affect your phone's operation. You always want to be able to undo or recover from something scary that you might have done to your phone and being knowledgeable and aware is invaluable in enabling you to do this.

Read the root stickies, do some Google and forum searches, and ask questions--that's how we all learn :).

Cheers!
 
Upvote 0
Okay, I think the dream of building an on-phone GB for the DX rooting app using djrbliss' adb exploit is over (for me at least, for the time being).

It turns out that you do indeed have to use adb to implement all aspects of djrbliss' exploit.

The shell created by the "adb shell" does get special access permissions vs. a shell launched on the phone (i.e., Android Terminal Emulator) or via an app (/system/bin/sh).

I got my son to install a GB leak on his D2G and when we ran my app on it, even the first line of the first step of the exploit would not execute due to a permission denied error when attempting to access files inside /data/local (i.e., the core of the exploit) whereas an adb shell has no such problem. I would have still been stymied by the post-exploit steps that I'm sure require using adb (although I started researching and building an on-phone adb client (which would have been pretty cool) to overcome this hurdle.

At the very least, I've learned a lot of new stuff over the last several nights and that's got my "app"itite ;) whetted to do some new app development.

Sorry guys, I gave it my best shot.

Cheers!
 
Upvote 0
Should be waaaay less that that...the exploit is dead-simple.

The exploit itself involves adb, but should not actually require adb to implement.

If this isn't published by someone by Sunday, I'll write the .apk myself ;).

edit: don't think this is possible at this time; djrbliss' exploit does indeed require using adb to implement the exploit since the shell created via adb get's special permissions that other shells do not (see this post http://androidforums.com/droid-x-all-things-root/403069-exploit-root-dx-gb-without-2-part-aio-tbh-files-one-click-method-now-included-2.html#post3132259 for more details).

(lol, I thought I was editing my original post...oh well, here's a bonus post)
 
  • Like
Reactions: P1DroidX
Upvote 0
So apparently after researching it seems I can't really get root because I had an old superuser on my phone from .596 root.
Now the problem is I cannot delete it(old superuser) or flash a new one because I am not rooted.
Any ideas or am I gonna have to sbf?

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.
 
  • Like
Reactions: eldealero
Upvote 0
Went through everything and it went 99% without issue. Had to unplug the DX in between booting to prevent it from going into the stock bootloader but other than that...............worked well.

I am a BIG fan of Bouchigo's BWC theme. Asked him how to go about things and i am now running 602 Gingerbread theme with Bo's BWC............can not ask for much more..................

I do have an issue................can not find Shootme screen grabber or Drop Cap screen grabber anywhere......................does anyone have the apk's to these that i can get?

Thanks much:)

CAP2011083013051.png
 
Upvote 0
Should be waaaay less that that...the exploit is dead-simple.
The exploit itself involves adb, but should not actually require adb to implement.
If this isn't published by someone by Sunday, I'll write the .apk myself .

edit: don't think this is possible at this time; djrbliss' exploit does indeed require using adb to implement the exploit since the shell created via adb get's special permissions that other shells do not (see this post http://androidforums.com/droid-x-al...-click-method-now-included-2.html#post3132259 for more details).

(lol, I thought I was editing my original post...oh well, here's a bonus post)

Thanks for trying anyways, hope that something will inspire you and you'll figure it out though!
 
  • Like
Reactions: scary alien
Upvote 0
Thanks for trying anyways, hope that something will inspire you and you'll figure it out though!

LOL, thank you, too!

I haven't stopped thinking about ways around it...I just haven't figured-out one that will work ;) (yet).

I had one idea that sent me on a path towards researching a lot of stuff I need to understand more deeply. There's so much to grok, but I enjoy the journey regardless of the outcome :).

Cheers!
 
Upvote 0
Worked like a charm and super easy. Huge thanks.

The only reason I rooted to be honest, was to apply a hard button LED hack so I could turn off the insanely bright lights when I have it docked. Still can't believe there isn't a fix for this yet.

What's the hack or app?

I might be able to make a quick option in my BattMonX app for you to turn these off...I haven't researched this, but my app can use root to tweak the LED brightness files...I'm sure the backlights are similarly and easily available.

Let me know.

Cheers!
 
Upvote 0
What's the hack or app?

I might be able to make a quick option in my BattMonX app for you to turn these off...I haven't researched this, but my app can use root to tweak the LED brightness files...I'm sure the backlights are similarly and easily available.

Let me know.

Cheers!

It's just an app called adjbrightness in the market. Works good now that I'm rooted.

I apologize, I should have said app and not hack in my post above.
 
Upvote 0
It's just an app called adjbrightness in the market. Works good now that I'm rooted.

I apologize, I should have said app and not hack in my post above.

LOL, Derek :) no need to apologize...I don't think the term hack is always meant (or taken) in a negative context.

Oh, yeah, I've heard about AdjBrightness before...looks simple and effective.

Cheers!
 
Upvote 0
LOL, Derek :) no need to apologize...I don't think the term hack is always meant (or taken) in a negative context.

Oh, yeah, I've heard about AdjBrightness before...looks simple and effective.

Cheers!


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.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones