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

Root Need some adb help

S

spezticle

Guest
I've been following the rooting guide.
I've downloaded and unzipped the GingerBreak, su, and Superuser.apk files and the android sdk. and i've pushed GingerBreak and su to /data/local/ without problem.


my problem comes into the part where i run
Code: 
/data/local/GingerBreak
essentially, a little, but nothing happens.
Code: 
16:21:55 benjamin@blend27:~/root/abX_FILES$ adb devices
List of devices attached 

16:22:01 benjamin@blend27:~/root/abX_FILES$ adb devices
List of devices attached 
1000064fac22    device

16:23:04 benjamin@blend27:~/root/abX_FILES$ adb push GingerBreak /data/local
157 KB/s (16830 bytes in 0.104s)
16:23:31 benjamin@blend27:~/root/abX_FILES$ adb push su /data/local/
248 KB/s (26336 bytes in 0.103s)
16:23:40 benjamin@blend27:~/root/abX_FILES$ adb shell
$ /data/local/GingerBreak

[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi

[**] donate to 7-4-3-C@web.de if you like
[**] Exploit may take a while!

[+] Detected Froyo!
[+] Found system: 0xafd1452d strcmp: 0xafd1d7ed
[+] Found PT_DYNAMIC of size 264 (33 entries)
[+] Found GOT: 0x000162e8
[+] Using device /devices/platform/s3c-sdhci.2/mmc_host/mmc2

[*] vold: 2386 GOT start: 0x000162e8 GOT end: 0x00016328
I let it sit at that screen at 2am last night, woke up this morning around 10am, and nothing had changed. i've rebooted my phone and tried again a few times...
Any insight as to what could be wrong?
 
Before I was in linux, now i've tried in windows.
different errors:
Code: 
c:\android-sdk\platform-tools>adb push GingerBreak /data/local
200 KB/s (16830 bytes in 0.082s)

c:\android-sdk\platform-tools>adb push su /data/local
243 KB/s (26336 bytes in 0.105s)

c:\android-sdk\platform-tools>adb shell
$ /data/local/GingerBreak
/data/local/GingerBreak
/data/local/GingerBreak: permission denied
$
 
Root checker from the market displays the following information:
Code: 
Root Access is not properly configured or was not granted.

Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!

System Environment PATH: /sbin /system/sbin /system/bin /system/xbin

The adb binary is set to default shell user access as a standard non-root user

Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory

Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory

Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory

Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory

SU binary not found or not operating properly

Results provided on your SCH-I510 device by Root Checker version 3.7
from joeykrim in the Android Market - http://goo.gl/GgWae

This is confusing to me because I was instructed to push su to /data/local and not /system/bin or xbin or something else...

also busybox check displayed:
Code: 
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin

BusyBox binary location:
Installed BusyBox Version:
BusyBox is not sharing its version information

BusyBox supports the following applets:
BusyBox is not sharing its supported applets


Results provided on your SCH-I510 device by Root Checker version 3.7
from joeykrim in the Android Market - http://goo.gl/GgWae

and when I try to use the superuser app, I can't update:
SC20111009-182507.png
 
That method isn't valid anymore.

Typing from phone... Let me see if I can get you a useful link. :)
 
Since i'm new to this, i was thinking learn to root first, play with a new rom afterwards.
 
Kelmar said:
Sounds good, you should do fine. :)
Click to expand...

well, the recovery.md5 didn't give me root or any other noticeable difference... so i said screw it and downloaded a de-bloated rom from Droid Charge Gingerbread (2.3.4) (EP1W) Leaked - Official Build

If i understand correctly, the ep1w is (relatively speaking) old and outdated?
I don't quite understand the hierarchy of the roms yet, i'll look into it more. I read a lot of stuff about how "rom x" couldn't be installed unless you did "rom y" first or something like that.

I sort of get that concept.. it reminds me of back in the day when i was on ModMyMobile Forums flashing my motorola RIZR z3 with the moster packs lol.

Anyway, thanks again :)

=====
edit
====
So i just realized that modymoto.com is now modmymobile.com and it's pretty much extinct from what it used to be, that's sad, in a weird way. i'll have to use google's wayback machine and check it out for nostalgia :-D
 
Kelmar said:
Correct, ep1w was a few leaks ago.
Click to expand...

ep1w is the only one i've been able to get to work :-\
everything else is for clockwork recovery and from what i've read that method doesn't work... unless Clockworks "Rom Manager" application and clockwork recovery are two different applications...
 
Kelmar said:
When flashing through CWM, be sure your system is mounted (under advanced).
Click to expand...

Ah, I see. It's saying that I need to be premium user to do that.
How many applications do I actually have to pay for for this to work?
Just this one?
 
Kelmar said:
You don't need to buy any for it to work!

Are you trying from recovery or from an app?
Click to expand...

that's where im confused.
i thought that the clockwork recovery IS the application "Rom Manager"
 
Ah... Ok... You don't need ROM manager at all. It doesn't work right with the charge anyways.

Make sure that the .zip file is on your SD card.

Power off the phone (completely). Press and HOLD volume up, home and power button. When Samsung logo pops up, let go of power button. It should boot you into recovery.
 
Kelmar said:
Ah... Ok... You don't need ROM manager at all. It doesn't work right with the charge anyways.

Make sure that the .zip file is on your SD card.

Power off the phone (completely). Press and HOLD volume up, home and power button. When Samsung logo pops up, let go of power button. It should boot you into recovery.
Click to expand...

ah, okay, i tried that as well, but it always reports the error "signature verification failed" and i get nowhere...

I think i messed something up somewhere so i'm reflashing back to where I started from with odin and starting over
 
While I know it's preference, would you be willing to try this one?

You'll be able to install it via Odin (put in battery prior to pressing start)
 
Kelmar said:
While I know it's preference, would you be willing to try this one?

You'll be able to install it via Odin (put in battery prior to pressing start)
Click to expand...

Yeah, i'm up for anything at this point. I want to try as many as I can really.
Thanks :)
 
Well, I figure this way you can get the latest GB leak and stay rooted, etc. :)

I haven't run the latest leak yet FWIW.
 
You must log in or register to reply here.
Back
Top Bottom