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..?

[GUIDE] Permanent root on Desire Z 'the clean way', using rage

This thread is copied and modified from the G2 thread by trigeek for the Desire Z:
http://forum.xda-developers.com/showthread.php?t=834228
Apart from the changed hboot and wpthis-Z kernel module for the Desire Z instead of the G2, I have also updated the su-binary and SuperUser.apk to the latest version by ChainsDD
In no way I can be held responsible for any bricks to your phone. You are using this guide at your own risk!! I did test this guide on my own, and also on a friend's Desire Z.
As there was no manual rooting guide for the Desire Z, I posted it myself in order to help others that do not like visionary and like to do it 'the clean way'.
[GUIDE] Temp to permanent root on Desire Z, using rage instead of visionary
=================================================
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]
Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
DESIRE Z ROOT INSTRUCTIONS
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
REQUIREMENTS
=================================================
•Visionary disabled at boot or uninstalled completely
•Android Terminal Emulator app
•ADB
•desirez-combined-root.zip (Attached to this post)
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
VERY IMPORTANT!
Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
TEMP ROOT
=================================================
ON YOUR PC:
Unzip the z-temp-root files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
1.Launch Terminal Emulator
2.
Code:
/data/local/tmp/rage
3.Wait for the message: "Forked #### childs."
4.Menu > Reset Term - Terminal Emulator will exit.
5.Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
6.**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this just yet. Leave the terminal window open.
PERM ROOT
=================================================
ON YOUR PC:
unzip z-perm-root and navigate to that folder. There will be four files. You will need to push two of these to your phone: hboot_7230_0.84.2000_100908.nb0 and wpthis-Z.ko. The other two files are optional for checksum verification.
Code:
$ adb push hboot_7230_0.84.2000_100908.nb0 /data/local
$ adb push wpthis-Z.ko /data/local
Optional but might came in handy:
Code:
$ adb push md5checksum /sdcard/md5checksum
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Optional but recommended:
Code:
# /data/local/tmp/busybox md5sum /data/local/*
You should see:
hboot_7230_0.84.2000_100908.nb0 2ce1bdd5e4c1119ccfcecb938710d742
wpthis-Z.ko c73c5e77c91d306c418983c002b60b93
In case your hboot or wpthis-Z.ko file do not have the same md5hash as shown above, DO NOT CONTINUE. This means your file is corrupt or you are using a different file, for example the one for the G2 instead of Desire Z.
Now, let's turn off security for permanent flashing:
Code:
# insmod /data/local/wpthis-Z.ko
init_module 'wpthis-Z.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You should see some messages indicating that it was written.
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!

Nice guide, thanks

Thank you Mr Q. works like a charm!

first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...

So this only roots your phone? Or does it s-off as well? From what I understand this s-offs as well because you're pushing the hboot as well.
EDIT: Nevermind. I read the thread again and it does indeed s-off as well.

MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
Click to expand...
Click to collapse
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen

ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
having the same issue here

So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)

yelti said:
having the same issue here
Click to expand...
Click to collapse
AnyDone said:
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
Click to expand...
Click to collapse
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.

ssyed said:
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
Ok, so does any one have an explanation why this happened?
1. It wasn't wrong or screwed hboot, otherwise we would be facing a real brick?
Was it the root method? Was it the wpthis-Z.ko?
It might have been the kernel module, but I can't be sure about that with so little knowledge I have. (sure not the module itself but the kick to the emmc?) Just that it seems to be more likely option than a rooting attempt on a cached r-o file system?
I'm not complaining about the guide, it is specific and easy to follow but I would really love to have these semi bricks etc inspected more closely. It is not really helping to encourage ppl to root and try safe-off when we have unexplained bricks and semi-bricks around

MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
Click to expand...
Click to collapse
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
yelti said:
having the same issue here
Click to expand...
Click to collapse
Did you guys run Visionary before trying this "rage" method of rooting ?

steviewevie said:
Did you guys run Visionary before trying this "rage" method of rooting ?
Click to expand...
Click to collapse
I don't know about others, but I didn't on mine. I was rooting it for the first time. Also, I don't know if this has anything to do with it, but I have the Bell version from Canada.

The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
Code:
/data/local/tmp/busybox killall rage
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
sync
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.

Have a quick look, /system/xbin already seems to exist on my phone too.
So is there an error in the script ? e.g. needs to ignore if the directory already exists ? Or am I (we ?) missing something ?

goldenarmZ said:
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Click to expand...
Click to collapse
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?

steviewevie said:
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
Click to expand...
Click to collapse
I did that first.. it threw more errors with the mount commands because I'd already run the script once, so some of the commands were repated. If it's your first run through, commenting it out would be fine.
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.

goldenarmZ said:
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
Click to expand...
Click to collapse
Thanks, I was starting to worry about the bad experiences outlined above, given that this method appeared to be a more reliable one than VISIONary, and a route I was going to go down. But I'm pretty comfortable with shell scripts, so your input makes me feel a whole lot better !

goldenarmZ said:
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
-code-
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Click to expand...
Click to collapse
thanks for this... I will give it a try

Yay, I just perma-rooted my phone using this method, many thanks to those who came up with the method in the first place, plus this handy guide too.
I got the message about /system/xbin already existing, but you can just ignore that message, it runs the rest of the script anyway.

ssyed said:
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
So after doing the guide you simply reeboot your phone into bootloader and select factory reset?
And then will the device be perm root and s-off???

[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"

[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......

Is temp root working?
Sent from my HTC Vision using XDA App

use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29

My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks

My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
Nonentity018 said:
Is temp root working?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse

Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
+1
Like he said, use that, don't waste your time with visionary

sammd301 said:
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Click to expand...
Click to collapse
I'd stay away from visionary if I were you! Its messing up just as many phones as it is rooting them!

part of the problem is that a visionary method is stickied in one of these subforums... that needs to be taken down desperately and replaced with gfree/rage.

Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
I am in the process of using this method....I'll let you all know how it turns out. by the thanks for pointing me to it...

Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
Yes I am in the process of using ADB / RAGE method....I run in problem and I could use someone help please...
TEMP ROOT
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
===========
All the commands are working except
$ adb push rage /data/local/tmp/rage
the reply I get after input the command is
Cannot open 'rage': No such file or directory
I have search the web for help...but I could find help on that issue
SO please if anyone knows what I am doing wrong could you please help....
thanks

unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.

yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it

Cobra281 said:
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Click to expand...
Click to collapse
Yes the "Rage" file is there, all the other command work fine...except the one dealing with the "Rage" file

ratchetrizzo said:
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
Click to expand...
Click to collapse
Thanks so much for your input....when I gfree_temp-root.zip file I can see that the "RAGE" file is present but after 20 to 30 minutes the "RAGE" file disappear from the folder but all the other files remains....Is an alternative gfree_temp-root download link that anyone might know of....thanks again

Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App

ratchetrizzo said:
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...

sammd301 said:
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
Click to expand...
Click to collapse
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.

ratchetrizzo said:
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
Click to expand...
Click to collapse
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system

sammd301 said:
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
Click to expand...
Click to collapse
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.

ratchetrizzo said:
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
Click to expand...
Click to collapse
Yes, I did what you suggested, but now I am getting
"rm failed for -rt, no such file or directory" after inputting ""rm -rf /system/xbin" command...by the way thanks so much for helping me out on this...

[Q] like someone seen this ever eror

Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful

try to use another launcher.
btw i am not sure its the right place to ask...

Please follow the rules, don't post questions in the development section. Ask or report to forum moderator to move this post to the Q&A section.

one more thing I noticed, the product code was reset (000000)

boldman78 said:
try to use another launcher.
btw i am not sure its the right place to ask...
Click to expand...
Click to collapse
friend I've updated I've done everything and this error appearing sige

ediltoyo said:
friend I've updated I've done everything and this error appearing sige
Click to expand...
Click to collapse
0. Download a ROM and put it on external SD or computer.
1.Backup things you need to a computer
2. Flash TWRP recovery (Idk how to do it on CWM)
2.1 take off external SD (if u have one)
3. Go to wipe and format data and wipe everything. Everything..
4. Now you are left with a phone that has nothing at all..
4.1 return SD, restart TWRP
4.2 put the file from the computer to the device.
5. Flash a fresh ROM
6. now you gotta be fine.
Sent from my GT-N7100

ediltoyo said:
Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful
Click to expand...
Click to collapse
It's related to a corrupt efs partition. Reflashing a rom or factory reset would not solve it.
Google for 'factory mode' to get the solution.
Sent from my GT-N7100 using xda premium

ediltoyo said:
Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful
Click to expand...
Click to collapse
Your EFS is corrupted and your phone is now in Factory Mode. Use Terminal Emulator, which can be downloaded from the Google Play Store, and enter the following commands.
Open terminal emulator and type;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
I hope you have a backed up EFS image because you will need it.to replace the corrupted one. Find Dr.Ketan's posts for that.

Thread moved to Q&A, where it should be

How to disable test mode yellow screen in my t889

hello
i have the yellow screen test mode
tried to get rid of it via z3x but not work
Writing data to phone... OK
Rebooting phone... OK
Waiting phone... OK
Bypass MSL... error
Done with Samsung Tool v.17.4
Done with Samsung Tool v.17.4
Any suggestions please?
is there any hidden menu i can enter and disable this ?
Thanks in advance

i found the solution
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
your phone will restart
You now should not see the that message anymore. Its because of an EFS corruption. ( Thanks to yesilcin*com) for exact solution.
Hope it helps!!!

Sobaro said:
hello
i have the yellow screen test mode
tried to get rid of it via z3x but not work
Writing data to phone... OK
Rebooting phone... OK
Waiting phone... OK
Bypass MSL... error
Done with Samsung Tool v.17.4
Done with Samsung Tool v.17.4
Any suggestions please?
is there any hidden menu i can enter and disable this ?
Thanks in advance
Click to expand...
Click to collapse
only dial on the keypad * # 87976633 # reset and ready

Worked ! Thanx

Sobaro said:
Worked ! Thanx
Click to expand...
Click to collapse
That has to be one of the longest times to reply I've seen... Almost 2 years LMAO

kozmo21 said:
That has to be one of the longest times to reply I've seen... Almost 2 years LMAO
Click to expand...
Click to collapse
Hahahaa , Ironically i was searching how to disable the test mode screen for a friends phone and Google leads me to a post i made a couple of years ago , then i saw this reply , i tried it and it really worked for me .