Develop Bugs

Superuser su binary

I've noticed that the su binary installed by superuser doesn't survive a reboot. Anyone else have this problem? Any fixes?
Sent from my SPH-D700 using XDA App

Same here. Have to re update after each reboot
Sent from my SPH-D700 using Tapatalk

same here, had to update the binary too

How do you update the su?

Launch superuser, go to settings and scroll to the bottom.
Sent from my SPH-D700 using XDA App

I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App

dangdang said:
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
How did you update it yourself?

Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App

Code:
#cp /sdx/su /system/bin/jk-su
cp: not found
the last part does not work (i have the same root method)
i have to re-root the phone when i get home today. but i will try to move the updated binary with root explorer instead of the command line.

Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA

dangdang said:
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
Click to expand...
Click to collapse
will try I had the same issues

dangdang said:
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have this exact same problem on my Samsung Moment (have to update SU every reboot).
The directory structure seem a bit different. For example, there's no /system/bin/jk-su (in fact, if I find / -name 'jk-su' I get no results at all).
I am poking around the directory structure trying to figure out where to find the source and destination su files that I'm going to have to overwrite and I can't seem to figure which is which. Does anyone have any idea how to do the functional equivalent of dangdang's post on a Moment?
Thanks!

Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?

k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao

I was about to say. WTF is everyone talking about SU not surviving a reboot /noodlescratcher
davidrules7778 said:
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
Click to expand...
Click to collapse

k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.

lol. i hear ya!
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse

DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
most likely SU is built into your kernel and short of rebuilding or repacking your kernel you cant update it..

I have a samsung galaxy s I9000 running Gingerbread will this work for me..?

[DUMP] SGH-T989 System Dump

SGH-T989 System Dump (Odexed)
Here you guys go, a system dump, thanks to luckyduck69.
luckyduck69 said:
dump: http://dl.dropbox.com/u/21231693/T989odex.zip..
Click to expand...
Click to collapse
I have also mirrored this on my website, here.
I will have it deodexed here later tonight.

Reserved.
as;dflkjas;ldfkja;sldfkj

So, the dump would be useful if one needed to put the phone back to just the way it was out of the box, correct? One could use it with Odin to fix, say... a soft brick?

Ty for this!! this means what exactly? easier to root and set up for odin?????curious

movieaddict said:
Ty for this!! this means what exactly? easier to root and set up for odin?????curious
Click to expand...
Click to collapse
once it deodexed... the real def fun begins as far as modding or cooking up personalized roms.
but we really need to get a modded kernel somehow and get root. that must be our main priority cuz nothing else matters without it. maybe someone has a trick up their sleeve... i hope.

Awesome........ now the ball gets rolling

Ty sir Please remove all the ridiculous t-mobile bloat.

Ty luckyduck!

sence im at school and cant up u all my original build ill root this for u all and upload it back to my sf page

RaverX3X said:
sence im at school and cant up u all my original build ill root this for u all and upload it back to my sf page
Click to expand...
Click to collapse
Nice greatnews and good to see familiar faces from the gs4g thanks raver
Sent from my SGH-T989 using xda premium

Raver always comes thru so glad to see him here!
Sent from my SGH-T989 using XDA App

Ty to all of u guys!! cant wait

Hey fellas i was on sammy's open source site yesterday and nothing was there for the SGH-T989 and today there is an SGH-T989 open source.zip file up on the site just in case this helps in any way with getting things going with rooting this bad mutha!
https://opensource.samsung.com/
Sent from my SGH-T989 using xda premium

Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
IMPORTANT: If the attempt to tar up /system above gives any errors about access denial or permissions, post the name of every file that was a problem.

Would love to but at work atm.
Sent from my SGH-T989 using xda premium

Entropy512 said:
Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
Click to expand...
Click to collapse
"/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *" gives permission denied error

/system itself? That's VERY odd.
zaventh is working this now, talking with him on IRC
Edit: Looks like adb push didn't make busybox executable, as I mentioned in IRC:
Code:
adb shell chmod 755 /data/local/tmp/busybox

Finally the ball gets rolling
Sent from my SGH-T989 using xda premium

Entropy512 said:
Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
IMPORTANT: If the attempt to tar up /system above gives any errors about access denial or permissions, post the name of every file that was a problem.
Click to expand...
Click to collapse
Dump using this method available here: http://www.multiupload.com/MKCNJTUTRW

zaventh said:
Dump using this method available here: http://www.multiupload.com/MKCNJTUTRW
Click to expand...
Click to collapse
Another dump ---- http://www.multiupload.com/424YLKAN90

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.

Reserved

Reserved

This is the same as https://github.com/saurik/mempodroid
saurik ftw.

times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.

Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!

Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus

Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium

This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium

Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.

Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk

efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links

try /data/local/tmp

Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb

Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk

OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.

Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.

convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers

Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.

I cannot unlock my Samsung Galaxy S I9000

Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.

sirgen said:
Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.
Click to expand...
Click to collapse
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin

ruscan.calin said:
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin
Click to expand...
Click to collapse
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?

I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA

sirgen said:
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?
Click to expand...
Click to collapse
It seems you have adb.exe tool already installed but you get error because you do not have enough rights on your phone so get the rights by these lines..
by terminal here I mean cmd.exe from Windows
so enter cmd Start/Run/cmd.exe
then to start adb server enter this
Code:
adb devices
then in cmd enter
"adb shell" press Enter (in fact this is "terminal" - a way to get access on your phone and enter commands)
then "su" press Enter
and so on..
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
lastly enter
Code:
adb pull /efs/nv_data.bin
now you get nv_data.bin on your PC check for this file in the folder where adb.exe is located usually ~\android-sdk\platform-tools\adb.exe
You have the advantage of a well-known phone so there are solutions for everything
by example look here for a tutorial to unlock your phone
If you do not understand something let me know about
This is the case you want to work from scratch the easy way is to search on Market/ Google Play for an app to unlock this phone

Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.

sirgen said:
Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.
Click to expand...
Click to collapse
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?

ruscan.calin said:
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?
Click to expand...
Click to collapse
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?

sirgen said:
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?
Click to expand...
Click to collapse
root is very important if not you can not play with nv_data.bin file...
what link ? and how did you do what steps I can't guess show me some logs screenshots anyway more info !

[QUOTE su
chmod 777 /efs/nv_data.bin
exit
exit
Then from the DOS command prompt:
adb pull /efs/nv_data.bin
Step 5: Select the file on the main Samsung Galaxy S Unlocker & Repair page
Step 6: Enter your desired Unlock and Unfreeze Codes and click the SUBMIT button
Step 7: Download the new file that is generated for you
Step 8: From ADB shell (Type "adb shell" at the DOS command prompt) or a terminal on your phone, enter the following commands to backup your current EFS related files, in case something goes wrong. ![/QUOTE]
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is. I included two pics of tmy adb shell (adb pull /efs/nv_data.bin)
I also copied an efs folder from my phone onto my pc.

sirgen said:
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is.
Click to expand...
Click to collapse
here is it http://www.communityhosting.net/sgsunlock/

ruscan.calin said:
here is it http://www.communityhosting.net/sgsunlock/
Click to expand...
Click to collapse
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.

problem solved
sirgen said:
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.
Click to expand...
Click to collapse
I like your answer this is like 100 thanks for me !
also as Vertron said there are apps in Market to unlock this well-known phone

Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
My sincere apologies to you my friend. I was able to unlocked my SGS after I followed your advice of downgrading to froyo and then I continued with the tutorial I got through Member ruscan.calin. So excess amount of thanks to you both. I will make sure to properly BACKUP my SGS3 before I touch it. I have learnt my lesson. Thanks again.

aarlene said:
Hi,
You can unlock your Samsung Galaxy S I9000 using unlock codes!! Unlocking using codes is easy and also safe!! You can get the codes from your service provider or from reliable online sites!!!Personally, I would suggest prounlocking.com , here they provide accurate codes at reasonable price!!!
Click to expand...
Click to collapse
Thanks for the heads up, but I did it with the help of XDA

Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Thanks

[T-Mobile] Restore Stock Preloaded Data after rooting.

This archive contains the missing apks and stickers that are lost when using the HTC Dev unlock tool.
You can install the apks inside manually, but the png files must be placed into /data/preload/ in order for the gallery app to find them.
Instructions for re-installation. (Busybox must be installed)
Code:
adb push preload.tgz /sdcard/
adb shell
su
cd /data/
tar -xvf /sdcard/preload.tgz
chown root:root /data/preload
chmod 771 /data/preload
chmod 644 /data/preload/*
pm install /data/preload/Flashlight.apk
pm install /data/preload/Calculator.apk
reboot
Download here: http://www.cheatersedge.org/android/m8/preload.tgz

Wow thanks. Did not even realize it was gone.
Sent from my HTC One_M8 using Tapatalk

FYI, wiping /data/ with TWRP erases these preloads as well.
Sent from my HTC One_M8 using Tapatalk

Hey I know this is not specifically related but everytime I remove an app via TB they come back upon reboot (T-Mobile Tv, Lookout, etc etc)
How do I stop them from coming back (delete for good)? Thanks

S-off or try http://forum.xda-developers.com/showthread.php?t=2702575
[Guide] How to have write protection disabled on boot with stock rom
Sent from my HTC One_M8 using Tapatalk

I am uploading a ROM right now that restores these files.

Weird, I'm HTCdev unlocked but I still have the flashlight app but calculator is gone. Weird.

Fenny said:
This archive contains the missing apks and stickers that are lost when using the HTC Dev unlock tool.
You can install the apks inside manually, but the png files must be placed into /data/preload/ in order for the gallery app to find them.
Instructions for re-installation. (Busybox must be installed)
Code:
adb push preload.tgz /sdcard/
adb shell
su
cd /data/
tar -xvf /sdcard/preload.tgz
chown root:root /data/preload
chmod 771 /data/preload
chmod 644 /data/preload/*
pm install /data/preload/Flashlight.apk
pm install /data/preload/Calculator.apk
reboot
Download here: http://www.cheatersedge.org/android/m8/preload.tgz
Click to expand...
Click to collapse
How would I go about executing these commands? I have tried a command prompt with the phone powered into the OS and with it in fastboot but continue to get device not recognized. Could I place the file on my phone and use terminal emulator?

ghettovirtuoso said:
How would I go about executing these commands? I have tried a command prompt with the phone powered into the OS and with it in fastboot but continue to get device not recognized. Could I place the file on my phone and use terminal emulator?
Click to expand...
Click to collapse
Problem fixed! I needed to update my adb tools, was working with outdate ones because they did everything I needed until now.

I tried the commands, but the tar command doesn't seem to work. Do I have to install something to make tar work?
I used Root Explorer to extract the files, then moved them to /data/preload, then changed the permissions using adb. I think I got it correct. How can I tell if the stickers are installed correctly? What uses them? I saw a comment about the gallery but I can't see where that uses them?
Thanks!

fclifton said:
I tried the commands, but the tar command doesn't seem to work. Do I have to install something to make tar work?
I used Root Explorer to extract the files, then moved them to /data/preload, then changed the permissions using adb. I think I got it correct. How can I tell if the stickers are installed correctly? What uses them? I saw a comment about the gallery but I can't see where that uses them?
Thanks!
Click to expand...
Click to collapse
Take a pic and edit it. If you can use the stickers you see in folder and the apps are install then I assume all went well.
Sent from my HTC One_M8 using XDA Free mobile app

ghettovirtuoso said:
Take a pic and edit it. If you can use the stickers you see in folder and the apps are install then I assume all went well.
Click to expand...
Click to collapse
Apparently all went well. I have the apps and the stickers work. :good:
What about tar? Should it have been available?

fclifton said:
Apparently all went well. I have the apps and the stickers work. :good:
What about tar? Should it have been available?
Click to expand...
Click to collapse
I know nothing of a tar. I'm not an expert. I was just able to follow the post. Sorry.
Sent from my HTC One_M8 using XDA Free mobile app

Couldn't install apps from adb
Everything in the op worked up to the point where I tried to install the Flashlight and Calculator apks. I got the following error-
pm install /data/preload/Flashlight.apk
pkg: /data/preload/Flashlight.apk
Failure [INSTALL_FAILED_INVALID_URI]
I was able to use a file manager to find the apks in the /data/preload/ folder and install them through android.
Is this enough to receive any OTAs? Would I need to convert them to system apps?