Database Info

Rooting the Eris

Has anyone been able to root thier Erie yet? If so how did you do it? Or can anyone point me in the right direction to get started. Thanks for the help.

I think it'll be at least a few weeks. Someone needs to get the recovery image and mod it as they did with the Hero. I think.

so is anyone working on this? if you give me instuctions i will dump my phone and post it, if that will help? i would really just like to be able to tether over wifi when needed without having to pay out the ear for it.

Is it that different from the Sprint's Hero? Try the current method...

herzzreh said:
Is it that different from the Sprint's Hero? Try the current method...
Click to expand...
Click to collapse
I'm concerned that the image from the Hero will cause problems since it's different carrier etc

The method used to root isn't carrier dependent. You probably won't want to load MoDaCo's current ROM as it is Sprint specific, but assuming the kernel build is the same you may be able to gain root with the asroot2 script.
To clarify, 'rooting' is not the same as loading a custom ROM. One begets the other, but loading a custom ROM isn't a requirement, just a door that gets opened when you gain root access to your phone.
Assuming everything else is the same on the phone, the Amon_Ra recovery bootloader should work as well.

If asroot2 works then we can flash a new recovery image, you can dump your ROM, and I can do a MCR version.
P

would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?

binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
If you use the recovery image for the hero and it doesn't work, it's not usually a big deal.
Just pull out the battery to restart your phone normally. Since the recovery image is separate from the rom, replacing the first does not affect the latter.

binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
Follow the rooting instructions to the letter, all the way through. Just don't flash a new rom if successful.

You can use the recovery image posted for the Hero.

ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory

The eris and droid can't use that exploit unfortunately, you'll have to wait until there's another way in

binny1007 said:
ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory
Click to expand...
Click to collapse
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.

well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.

thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.
Click to expand...
Click to collapse
That's what I thought. Hopefully since the hardware is so similar it wont take long.

Unfortunately hardware is barely a glimmer in this equation - the expliots used to gain root are software, usually kernel bugs.
Something will turn up soon.hopefully.

binny1007 said:
well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.
Click to expand...
Click to collapse
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!
Have you attempted the flashrec method?
Drop the Recovery Image from here onto your sd card
http://forum.xda-developers.com/showthread.php?t=581521
Download the apk from here and install it on your phone:
http://zenthought.org/content/project/flashrec (download it from your phone's webbrowser and open the file...if that doesn't work, download astro file explorer from the market and try again).
Once you open flashrec, click on the "backup" link and then type in the path to your recovery image (most likely: /sdcard/recovery-RA-heroc-v1.2.3.img)
Then flash and try to reboot into recovery mode (power off, then either home+power, volume down+power, or camera+power...depends on who you ask, one of those should get you into the recovery image where you'll see an option for nandroid, that's how you'll know it was a success).
If you reboot and it doesn't work or it freezes, pop out the battery and boot normally...shouldn't hurt anything (though if you want to be more safe, I'd wait until we got the RUU for whatever carrier you're on (Verizon/Telus/etc)). Currently the Sprint RUU is the "get out of jail" card that's saved a bunch of people.
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!

thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
Click to expand...
Click to collapse
Cellular South
thecodemonk said:
Have you attempted the flashrec method?
Click to expand...
Click to collapse
It doesn't use the same exploit as asroot2?

markachee said:
Cellular South
It doesn't use the same exploit as asroot2?
Click to expand...
Click to collapse
Sorry, Cell South, Bell south...(can you tell I'm not from around there? )
I have no idea if it does...but I figured it can't hurt to try eh? Because if it works, wouldn't that be awesome?

Samsung sidekick 4G

Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App

Wreximus said:
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
i wish i knew how to do this, but if i can't figure it out, i'm sure others will soon.

Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.

abliss said:
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
Click to expand...
Click to collapse
Oh really? Cool. So far all I've used is one-click root for the Samsung Epic.... is this similar? I'll check it out, thanks!

Has anyone tried using SuperOneClick yet?? I will probably try in a bit and post back with my results..

Ok... well I didn't try SuperOneClick, but I did root it via the rageagainstthecage exploit...

Want to help me do the exploit on my SK4G to root it man ?
Give me instructions ?!

I got it working on mine too. The basic steps were
1) enable debug USB mode on your phone
2) install Samsung drivers for the phone - right now Samsung's site seems to not have a choice for the Sidekick 4G's model (SGH-T839), but I grabbed the drivers for the Vibrant (at www .samsung.com/us/support/downloads/SGH-T959ZKDTMB) and they worked.
3) get adb shell working on your PC (Google it)
4) download the rageagainstthecage-arm5.bin and Superuser packages from the links in this page: wiki.cyanogenmod.com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide (be sure to unzip the files into the directory where your adb.exe program is unless you've put it in your path)
5) reboot your phone and plug it in
6) adb push rageagainstthecage-arm5.bin /data/local/tmp
7) adb shell
8) cd /data/local/tmp
9) chmod 755 rageagainstthecage-arm5.bin
10) ./rageagainstthecage-arm5.bin
11) wait until you get booted back out to your DOS command prompt
12) adb kill-server
13) adb start-server
14) adb shell
15) you should now be at a # prompt. The first few times I tried, I wasn't - I was at $. Doing this from a fresh boot seemed to be the trick. Reboot your phone and try again if you're getting a $.
16) mount -o remount,rw /dev/block/stl9 /system
17) exit
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/stl9 /system
22) exit
23) reboot the phone then run an app that requests root, such as Root Explorer, to verify
(p.s. sorry for having to mangle the URL's above, XDA won't let me include links since I haven't posted 8 times yet)

josby said:
16) mount -o remount,rw /dev/block/st19 /system
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/st19 /system
Click to expand...
Click to collapse
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Also, after step 20, I had to run the following commands for the superuser application to grant root privledges to applications..
adb shell echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
adb shell echo "root::0:" > /etc/group

Awesome to see it being rooted so fast.
I'm really interesting in getting this phone but I'm not in the US. Does anyone know if the phone will work outside US?

brenix said:
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Click to expand...
Click to collapse
Dang, good catch, thanks. That's what I get for not copying and pasting from my terminal window...stupid, since I was just chastising two people at work for making the same mistake yesterday. I've edited the original post to prevent problems for people who might start before reading the entire thread.
Interesting about having to create a passwd and group file...I've only run a few root apps so far, but they've worked without me doing this. I wonder if it's app-specific.
Now to start removing some of the damn bloatware this thing comes with!

19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools

i'm so glad this thing got rooted. i used to be a scene kid with a kick. i dont have this phone, i doubt i'm going to get this phone considering the sensation is droppin soon.... but for nostalgia purposes, i'm glad it got rooted. now you can really hack it!!!
not like the old ones!!

Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?

fawkReviewz said:
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
Click to expand...
Click to collapse
Double-check your step 18...that's the step that copies the su file from your computer onto the phone. I forget the exact output format, but it shows you a Kb/second number of how fast the file transfer went when it finishes successfully.

droctii said:
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
Click to expand...
Click to collapse
I'm not brave enough to try putting the ClockworkMod for one of the Samsung devices on the list onto mine, for fear of bricking it. Don't know enough about that works as far as hardware differences go.
I have removed the APK's listed below from /system/app with no apparent ill-effects. Not that YOU should remove them necessarily - just that they're things I don't have a need for:
AccountAndSync.apk
AmazonMp3.apk
AppPack.apk
DriveSmart.apk
DriveSmartHelper.apk
install_flash_player.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Memo.apk
MiniDiary.apk
MobileBackup.apk
MyFiles.apk
PhoneSetupWizard.apk
Twitter-2.0.1-121.apk
vvm-signed.apk
Though there must be something I don't fully understand, because even after a reboot, Amazon MP3 and AppPack are still on my phone, and they still work.
FYI, don't remove Settings.apk - I got stuck in a loop where the launcher kept crashing then reloading itself (thank goodness I was able to put it back in place with adb).

Can anyone tell me if Setcpu works for them?

Ace42 said:
Can anyone tell me if Setcpu works for them?
Click to expand...
Click to collapse
Appears to work fine.. no crashes although the Max Hz is 1000. U can still raise the Min Hz.
Sent from my Nexus S using XDA App

Can someone post a full:
ls of / and /dev/block and /efs
Thanks

Will this phone get a proper sub-forum on xda?

[Q] Restoring stock recovery

Anyone know how I can restore to stock recovery? I rooted and flashed CWM recovery, but I need to restore to stock because I am having so many problems with random reboots that I see lots of people are also having problems with. I have downloaded the dump. If someone could tell what I need to do on would be extremely grateful.

Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk

Ace42 said:
Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.

see my next post for the 1 click

ehall2k7 said:
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.
Click to expand...
Click to collapse
Me too, which is why I regret it now....I want a phone hat I less buggy, this thing crashes all the time which sucks. Also the phone won't get much faster since it doesn't have enough space for the galaxy s lagfix, which applies to this since it has rfs and not ext4 like it needs..
@person above, if we brick it then they would replace it, right? You would just need to do some "acting" in the store and play dumb with the rep, if you know what a mean.
Sent from my SGH-T839 using Tapatalk

I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know
updated to Here

http://forum.xda-developers.com/showthread.php?t=803682
that is the link to SuperOneClick its a Root app that you can also use to unroot the device.. i Haven't Received my other SK4G yet to test but it should work its universal and works on multiple phones.
hopefully those that have root can use this method to unroot

blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.

ehall2k7 said:
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.
Click to expand...
Click to collapse
Just to give a heads up a bricked device will stay at the splash screen or may not even turn on, so it will be hard for them to know.I wish this phone was better, since I wanted I ever since I heard it was being remade by sammy.
Sent from my SGH-T839 using Tapatalk

blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I tried it and still no luck. Here is what I am seeing:
one click uninstaller based off of noobnl's
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
84 KB/s (0 bytes in 5392.000s)
2 KB/s (0 bytes in 88.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2650, 2650}
[*] Searching for adb ...
[+] Found adb as PID 2390
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
remove joeykrim root method
mount: Operation not permitted
rm failed for /system/bin/joeykrim-root.sh, Read-only file system
rm failed for /system/bin/jk-su, Read-only file system
rm failed for /etc/passwd, Read-only file system
rm failed for /etc/group, Read-only file system
rm failed for /system/bin/su, Read-only file system
rm failed for /system/xbin/su, Read-only file system
rm failed for /system/app/Superuser.apk, Read-only file system
failed to copy 'playlogo' to '/system/bin/playlogo': Read-only file system
Unable to chmod /system/bin/playlogo: Read-only file system
rm failed for /etc/resolv.conf, Read-only file system
rm failed for /system/bin/remount, Read-only file system
rm failed for /system/bin/busybox, Read-only file system
copy recovery and flasher
384 KB/s (0 bytes in 313888.000s)
495 KB/s (0 bytes in 7864320.015s)
flashing recovery
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/bml8.bin
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
Do you think it would be possible to flash the bml8.bin with ODIN? I haven't tried to go into download mode but it should be possible seeing how its almost identical to the vibrant and it's made by samsung.

I wonder if this has a bootloader like htc devices where you can flash system images which have the stock recovery, or if the system dump has it, then we can do.. flash recovery /sdcard/xxx.img from term or adb or fastboot, which ever one.
Sent from my SGH-T839 using Tapatalk

you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
mount -o remount,rw /dev/block/stl9 /system
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied

blu9987 said:
you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
remount rw
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied
Click to expand...
Click to collapse
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.

Ace42 said:
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.
Click to expand...
Click to collapse
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*

blu9987 said:
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*
Click to expand...
Click to collapse
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there

Ace42 said:
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there
Click to expand...
Click to collapse
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it

blu9987 said:
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it
Click to expand...
Click to collapse
Thr thing is..I'm exchanging mines today so I will try what you said and then do a factory erase afterwards. If it leaves some files there's not much I can do, can you fix he uninstaller to add the other files today, ill really appreciate it.
Sent from my SGH-T839 using Tapatalk

Disregard this post i'll make something and put it up after portfolio is done in a few hours

I have attached a one click uninstaller for root, revised and will work. Just extract and run the run.bat
It should remove all root and reflash stock over clockworkmod!
If this works let me know and i'll post it in its own thread

Shameless triple post:
Anyone end up testing this? It would be highly beneficial if somebody could remove CWM and root, restore to stock, and follow some instructions to pull the necessary images to make an odin tar. I would do this myself but I don't have a sidekick. Or maybe once we get a working CWM make a pre-rooted odin flash

[i9003][Mod] Root XXKPM without CWM

Hi everyone,
this method helps you to achieve root in XXKPM without CWM (which will be available shortly). You will need the attached files and Linux with installed Android SDK. Credits go to ChainsDD for the Superuser binary and APK and to Skin1980 for his normalboot.img repack script. This method is more time consuming than flashing CWM and more risky. Beware!
Flash XXKPE followed by XXKPM via Odin.
Flash the modified normalboot.img as PDA via Odin and do a full wipe. This enables the adb shell to run as root on the device, allows debugging and mock locations.
Now start up Linux and hook up your device to your PC. Do not forget to activate USB debugging in the settings. Follow these directions very carefully, otherwise you might have to reflash or even loose your IMEI!
Run Terminal. In Terminal, gain root access and start adb:
Code:
su
adb start-server
To be sure adb is running and recognized your device, issue
Code:
adb devices
Now the delicate part: Mount /system read-write:
Code:
adb shell
su
At this point, the "$" at the beginning of each line should change to "#". Otherwise, you're not root and can not continue.
Code:
mount -o remount,rw -t yaffs2 /dev/block/stl9 /system
exit
And now push the Superuser files to the device (I am assuming they are lying in your home directory. Otherwise, adjust the path. For example, "su" could be in "/home/user/i9003/su"):
Code:
adb push su /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
And finally set the correct permissions and remount /system read-only:
Code:
adb shell
chmod 6755 /system/bin/su
sync
mount -o remount,ro -t yaffs2 /dev/block/stl9 /system
exit
Reboot.
After this, you will typically install busybox from the market. But this is up to you. Have fun!

Thanks for the info..r we really need this?coz I've no linux on my desk
Sent from my GT-I9003 using xda premium

AmirolAhmad said:
Thanks for the info..r we really need this?coz I've no linux on my desk
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
it can be done by using command prompt in windows with adb setuped in ur pc..

Anyone tried this method?

confirmed this method works

@g5abiera: I sure hope so
You mention an error in the OP. Can you specify?

Works!
Rooted and Deodexed...

i really don't know what went wrong the first try, i was getting an error telling me there isnt enough space in the partition where the su binary goes. then again, i simply reflashed kpm, and viola, it works.

[Recovery Unofficial Clockword Mod] for SPH-D600 (Conquer 4g)

A working recovery for Samsung Conquer 4g!!!
Needs Root!
V. 5.0.2.7
1.Download the files below
2.Move flash_image (in the zip folder) and CWMR.img to your sd card
3.On your phone download root explorer
4.Move flash_image to /data/local using root explorer
5.Download a terminal Emulator on your phone
6.Open the terminal and put in:
Code:
$ su
# /data/local/flash_image recovery /sdcard/CWMR.img
7.Than to make sure it doesn't revert to stock recovery put in:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock9 /system
to make sure its in rw mode put:
Code:
# mount | grep system
than:
Code:
# chmod 444 /system/etc/install-recovery.sh
(dont worry if you get an error not found some phones dont have this)
Credit goes to utankos over at rootwiki for creating the recovery.

Need some clarification
Perfect timing. I am just now starting to learn how to root my conquer 4g. I am having some issue locating this folder "/data/local/"
/data/local/flash_image recovery /sdcard/CWMR.img
I have installed the Root Browser - free version on my phone, but still not able to find the directory. Am I supposed to create the "local" folder within the /data folder?
Thanks.

yanxizao said:
Perfect timing. I am just now starting to learn how to root my conquer 4g. I am having some issue locating this folder "/data/local/"
/data/local/flash_image recovery /sdcard/CWMR.img
I have installed the Root Browser - free version on my phone, but still not able to find the directory. Am I supposed to create the "local" folder within the /data folder?
Thanks.
Click to expand...
Click to collapse
I have never ran into a problem like this but do so in the /data folder on your phone and sorry this has taken so long I haven't been on XDA for a while. Tell me if it works.

/data/local dir in root browser
Hi, in order to properly see the /data/local folder which is a hidden folder you need to access it as root. If you installed root browser before the phone wa rooted it already checked for root access and was denied. From then on it will run without root permissions. you need to gran it root access before you can access hidden folders the easiest way would be to erase the data of root browser in options|applications.
hope this helps.

Thanks for this, works great!

jhorton014 said:
Thanks for this, works great!
Click to expand...
Click to collapse
Actually I'm having difficulties getting the CWM recovery to be permanent. When I reboot it reverts back to stock recovery. I followed all of the instructions on the tutorial that you provided.

nvm