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

Root First attempt at rooting

Silvist

Android Enthusiast
Dec 23, 2010
370
113
San Francisco, CA
Heyo everyone,

Despite the lack of massive bloatware on this 4g phone, i still hate metro wifi, and of course my extras. There's like 8-9 apps i hate that come on any metro phone (they waste space, and esp the wifi it kills the battery, amongst other hidden apps). Since this is using 4g, the battery life is meh, so i'm really interested in maximizin it. So i'm determined to try to root this. Z4root does not work, and I tried a couple other ways to no avail. Right now i'm trying it through usb to see if i can downgrade it. I'll let ya know if i was successful.
 
  • Like
Reactions: ickster
Really really wierd. So i was able to use both super one click, and adb to verify i'm rooted. But for some reason I can't get super user. Shows busybox is installed as well. Adb device shows my serial. Kinda wierd, its like i'm in a half rooted state. Another thing I notice with super one click is it shows two options at the top right corner. Guess its back to the drawing boards.
 
  • Like
Reactions: ickster
Upvote 0
MEh this sucks. I don't want to mess with imaging because that's more heavier potential to brick your phone. Yeah, unless some how some of the other galaxy phones get a custom rom port to the Indulge, or they make a custom recovery, we can't do shit. I'm gonna keep my tabs daily on if anyone figured out how to do it, on every board i can find. The only other thing i'm thinking is we will need LAZY ASS SAMSUNG to put up some ****ing drivers for our phone so we can at least have proper drivers. Not to mention a full manual.
 
  • Like
Reactions: miariver
Upvote 0
ALright, this cracks me up. So this is what I got when I used super one click:


SuperOneClick v1.6.5.0
Killing ADB Server...

OK

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...
23 KB/s (5392 bytes in 0.223s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...
ROOTED

Pushing busybox...
523 KB/s (1062992 bytes in 1.981s)

OK

chmod busybox...

OK

Getting mount path...
/dev/block/stl10
OK

Reading OS Version properties...
Version: 2.2.1
OK

Remounting system with read-write access...

OK

Pushing su-v2...
1644 KB/s (26264 bytes in 0.015s)

OK

chmod su...

OK

Creating /system/xbin...
mkdir failed for /system/xbin, File exists


OK

Copying busybox (/system/xbin/)...

OK

chmod busybox (/system/xbin/)...

OK

Installing busybox (/system/xbin/)...

OK

Pushing Superuser.apk...
1713 KB/s (196521 bytes in 0.112s)

OK

Remounting system with read-only access...

OK


the only thing that fails is for it to make /system/xbin, and whatever mkdir is. I even SEE SU in the darn /xbin folder, so wtf lol. Somehow this is encoded. I realize the NAND is locked, but look here:

With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can’t copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don’t need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.

This apparently doesn't work either. Only option is here:

Level 1: Shell Root (with ratc rooting the adb shell but no /system write access)
Level 2: Temporary Root (/system/bin/su installed but lost on reboot)
Level 3: Full Root (/system/bin/su installed and sticks)
Some devices have a NAND lock. SuperOneClick will only give a Shell root until you remove this lock.
The following phones can use unrevoked to remove this lock:
Sprint EVO 4G (HTC Supersonic)
Droid Incredible (HTC Incredible)
HTC Desire GSM
HTC Desire CDMA (HTC BravoC)
HTC Aria
Droid Eris (HTC DesireC)
HTC Wildfire (HTC Buzz)
 
Upvote 0
Upvote 0
Upvote 0
Upvote 0
Okay gonna try this when I get home, I'm not sure if this guy is bsing. Its here:

[APP]SuperOneClick v1.6.5 (Root, Unroot, Enable Non-Market App, Get UNLOCK code) - Page 260 - xda-developers

"This worked great for my MetroPCS Samsung Galaxy R910, android v 2.2.1, running the program from windows xp, (with the USB debug turn off and on stuff)."
Thank you

note:
same phone, same program, would not work from Windows 7 64 bit"

This is what he said.

Yes i was wrong when i posted that, in my defense, SuperOneClick said it was successful.
 
Upvote 0
Yes i was wrong when i posted that, in my defense, SuperOneClick said it was successful.

Heyo Mr. Parker! No worries man, I wasn't saying you were wrong at all. In fact I was blown away by the fact you pulled it off lol. Yeah the super one click check is bs. Its just they have this phone encrypted up the ass so hard, that the CIA probably sweats bullets. I'm scanning the web for any info relating rooting this baby. Now the biggest problem I STILL think, stems from the fact we have no driver. I even tried the SPH M910, which is the intercept drivers, which the phone even recognized. Still no luck getting super one click to work. We need a hacker basically, one helluva a good xda hacker. Problem is not much demand yet for this phone being rooted. I'm sure when like 50 people scream about it, maybe someone will finally be so kind as to do it.
 
Upvote 0
Holy crap I was able to boot into system recovery! I used these drivers:

[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - Page 11 - xda-developers

Obviously removed whatever was currently installed. Then i used this:

[PROGRAM] Updated:One Click Root/UnRoot (Mac and PC) - xda-developers

That's for the samsung captivate. Anyways it didn't root my phone, but it DID boot me into the blue android custom recovery screen FTW. That's one helluva a step, now we just need some kind of update that will root the phone.
 
Upvote 0
Holy crap I was able to boot into system recovery! I used these drivers:

[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - Page 11 - xda-developers

Obviously removed whatever was currently installed. Then i used this:

[PROGRAM] Updated:One Click Root/UnRoot (Mac and PC) - xda-developers

That's for the samsung captivate. Anyways it didn't root my phone, but it DID boot me into the blue android custom recovery screen FTW. That's one helluva a step, now we just need some kind of update that will root the phone.


I also just noticed that samsung has posted there source code for the Indulge up on Samsung Open Source Release Center

we are getting closer I can taste it.
 
  • Like
Reactions: ickster
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