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

Root First attempt at rooting

I did some testing and am beginning to think that the key signing for the Superuser.apk is being rejected. Android requires that all apk's be signed otherwise the app will never show up in the list of applications. I checked and Superuser.apk is signed and valid however it is possible that the key is on a reject list. If this is the case then I'm unsure how to remove it from the list of invalid keys. If we could get the maker to re-sign with a different key as a test it would help. I've dropped him an email and will see if he replies.

In the meantime, I got rid of the annoying startup sound. I removed /etc/PowerOn.snd and /etc/PowerOn.wav after remounting the /system drive.
 
LightningTH said:
I did some testing and am beginning to think that the key signing for the Superuser.apk is being rejected. Android requires that all apk's be signed otherwise the app will never show up in the list of applications. I checked and Superuser.apk is signed and valid however it is possible that the key is on a reject list. If this is the case then I'm unsure how to remove it from the list of invalid keys. If we could get the maker to re-sign with a different key as a test it would help. I've dropped him an email and will see if he replies.

In the meantime, I got rid of the annoying startup sound. I removed /etc/PowerOn.snd and /etc/PowerOn.wav after remounting the /system drive.
Click to expand...

Thanks for the heads up on the startup sound. I'll definitely get to it. You can imagine how many times I had to turn the device off and on this last night :)
As for the driver signing, that's the whole deal. As the dude explains in this video: http://www.youtube.com/watch?v=Q7xV0yE9ZcA
unlike the stock version, clockworkmod kernel allows you to install custom updates that are unsigned. there is a toggle in the main menu to turn signing verification on or off. I feel like we may be very close to achieving our goal here, I just need to get to the right directory or need to push the update.zip file onto the phone's memory, if I figure out which part of it I'm seeing on the above picture. Any ideas? Also, what is the command for adb to copy files onto the device once we tempo-root?
 
You can do adb push <local> <remote>. If <remote> is a directory then make sure the / is at the end of it.

Oddly enough, the app I'm playing with is signed and should load from what I can tell but it won't show up. His video talks about how the new recovery does not allow unsigned zips, different than what i'm dealing with.
 
LightningTH said:
You can do adb push <local> <remote>. If <remote> is a directory then make sure the / is at the end of it.

Oddly enough, the app I'm playing with is signed and should load from what I can tell but it won't show up. His video talks about how the new recovery does not allow unsigned zips, different than what i'm dealing with.
Click to expand...

OK. I'll try that tonight. Any idea which directory listing I'm getting if you look at the picture that I attached?
 
is there a "advanced ULK features" in the clockwork menu?? if so you should be able to rrot from there

where you able to boot after the clockwork mod?
 
That is the directory listing of /data, only accessible if root however /data is a seperate device from /system and under normal mount is rw.
 
Lol wow tons of stuff has happened since I was sleeping :D. So yeah thunder I tried the blank password, and for some reason it tells me the password isn't correct.

As for clockwork I have it on this Huawei ascend i'm fixing with Icarus installed. I remember I got the EXACT same error msg when trying to apply an update in stock recovery mode for the indulge. So very odd your still getting the same stock error.
 
Silvist, do cat /etc/passwd. Make sure the root line is exactly what you see below. When the echo is done you have to put in the \ before the $ to avoid it from being interpretted.

root:$1$uTLqFpvI$7sqdAsiz7ID7/itfGxzZd.:0:0:root:/:/system/bin/sh
shell:x:2000:2000:shell:/:/system/bin/sh

An alternative is to download the below file then do the following after getting root thru the soup or root executable and remounting /system as rw (mount -o rw,remount ... line)

adb push passwd.txt /etc/passwd

<edit>
Looking back at the old post, it appears my previous re-edit didn't work. The original line would result in the password being "root".
 

Attachments

LightningTH said:
That is the directory listing of /data, only accessible if root however /data is a seperate device from /system and under normal mount is rw.
Click to expand...
OK, so is there any way to push the update.zip in there or is there any way to get to the real external sd card from clockworkmod? yes, I am able to boot and reboot after I installed clockworkmod recovery.
 
i have a tester...what do you want me to do?? im still trying to get clockwork mod on there and i cant seem to do it without odin...when i flash the cwm with odin the phone gets stuck in a boot loop...talk to me fellas, lets whoop this sob
 
rjsweesy said:
i have a tester...what do you want me to do?? im still trying to get clockwork mod on there and i cant seem to do it without odin...when i flash the cwm with odin the phone gets stuck in a boot loop...talk to me fellas, lets whoop this sob
Click to expand...

you haven't bricked your phone, man, have you?????
 
I'm not sure what to say exactly. I'm good at testing and tinkering but am not good at relaying to others of things to do. I know I myself would attempt a kernel build for testing but unless someone can tell me how to image backup my phone and restore under worst case, I'm a bit helpless.
 
nickrussel said:
you haven't bricked your phone, man, have you?????
Click to expand...

I ordered some fru units so I have some to play with...I bricked one flashing some of the other kernels so ill send that back but now I have a fresh one again plus my personal one....ill order two more tomorrow just in case

Give me play by play on cwm please
 
rjsweesy said:
I ordered some fru units so I have some to play with...I bricked one flashing some of the other kernels so ill send that back but now I have a fresh one again plus my personal one....ill order two more tomorrow just in case

Give me play by play on cwm please
Click to expand...

rjsweesy: don't I wish I had a few to play around with. OK, so your first step is to download drivers. since samsung haven't release drivers for the indulge, we're using those from samsung galaxy s. you can get those here: [Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - xda-developers
then complete Mike's instructions in this post: http://androidforums.com/samsung-galaxy-indulge/282280-success-bloatware-removed.html#post2313284
it's up to you whether to go for the last step and remove bloatware. most of us are much happier without it. or you can modify Mike's the script to your liking.
Note: some of us (myself included) have been having difficulties getting the computer to properly detect the phone. The easiest way I've found is to turn the phone off. take the battery out for 30 seconds, then put it back in, turn the phone back on and connect to usb within the first few seconds of the phone's bootup process. if you're in windows, go to start -> run -> type "devmgmt.msc" (no quotes), hit OK and watch the device manager populate the list of devices. As soon as the phone is detected, a new category towards the top of the list should appear (android based ***). When that happens, proceed with Mike's instructions. Running the first of his two files is mandatory in order to achieve level 1 root (so far only temporarily, unfortunately). then when the script is done running, do not disconnect or power off your phone but close the command prompt and run GalaxyS_One-Click_Root_All_Models. You can download it here GalaxyS_One-Click_Root_All_Models.rar - 4shared.com - online file sharing and storage - download

or if this link doesn't work, googling for the above filename will bring a lot more choices.

Run it with your phone still connected and follow the on-screen instructions. Is this last one fails, download and run the following:
http://firon.net/xda/one.click.root.exploitv2.5.5.zip discussed in this thread:
One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector! - xda-developers

Lastly, if all of that fails, try flashing it with Odin v 1.7 found and discussed with this thread: [PROGRAM] Odin 1.7 with pit files. - xda-developers

I'm not sure we should use any of the ROMs from that thread, though, as those are for the GSM Galaxy S i9000. Although, we could try...

Here is the video on how to flash a clockworkmod with Odin: http://www.youtube.com/watch?v=Q7xV0yE9ZcA

The only question to this day is what kernel should we use to flash our indulge with?.. i.e. from which phone... which is the closest relative to our indulge?..

Let us know how you're progressing.
 
congrats, rjsweesy! Since I've tried practically everything there was, I wasn't sure exactly which package worked. Now we know it's the one.click.root.exploit v2.5.5 from this Epic 4G thread on xda-developers, that worked. If you succeed in pushing su there, please share the routine.

Also, a question for all: if we have cwm now, how can we get the darn update.zip to any location that is visible from cwm recovery? According to LightningTH, my yesterday's screenshot shows the contents of /data, which is only visible under root. I'll try and see if I can mount /data using Mike's script and then push update.zip up there. Any advice on adb shell syntax, as well as on how to push su will be much appreciated, as I'm not that well versed in shell syntax! Looks like if we manage to run update.zip from cwm, chances of finally having this mo-fo rooted are quite high.
 
I thought to install a custom rom we just install an update.zip from the sd card root with the img we want to use. I never seen a custom rom installed through the root directory in custom recovery @_@.

Thunder when I did the check it showed up like this:

$ cat /etc/passwd
cat /etc/passwd
root:$1$1VkSwbgI$EH2K7lUVuZjCRqpDXkgkh1:0:0:roo t:/:/system/bin/sh
shell:x:2000:2000:shell/:/system/bin/sh


Which seems different than your new post. Course it didn't edit your post, so I did whatever you had there before. So i guess I can try to redo it.

Nick, where you at with all this lol. I see you got the custom recovery, did you get your phone working?
 
You must log in or register to reply here.
Back
Top Bottom