yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] supercurio:
Root is a special file with specific permissions installed in /system/xbin directory, this is not dependent on the kernel itself.

In case of Stupid SU, I install a tiny "helper" or "loader" that workaround today's Samsung blocking, also in /system/xbin (which means in system partition)

Flashing back the original kernel doesn't affect su installation nor its behavior.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Here you go, untested! as I don't own this device.

http://dl.project-voodoo.org/kernels/GT-I9505-I9505XXUAME2-stock+root-StupidSU-v3-kernel.tar

Yes stupidsu folder won't be there anymore but it's only the auto-root installer.
[Galaxy S 4 i9500 Original Android Development] Chenglu:
[MENTION=2617206]supercurio[/MENTION]

I make a auto unpackbootimg & mkbootimg update sctipt,use [MENTION=617884]Koush[/MENTION] anykernel script,test on my i9500:

#!/sbin/busybox sh

$b rm /tmp/mkboot.log
exec >>/tmp/mkboot.log
exec 2>&1

#unpack boot.img
/tmp/dump_image /dev/block/mmcblk0p9 /tmp/boot.img
/tmp/unpackbootimg -i /tmp/boot.img -o /tmp

#unpack boot.img-ramdisk.gz
mkdir -p /tmp/ramdisk
cd /tmp/ramdisk
gzip -d -c /tmp/boot.img-ramdisk.gz | cpio -i -d -m

#add service
rm -rf stupidsu
cp -r /tmp/stupidsu stupidsu
chmod 0775 stupidsu/root.sh
if ! grep -q 'service rooting' init.rc; then
sed '/service bootanim/ i\# Stupid SU\
service rooting /stupidsu/root.sh\
class main\
user root\
group root\
oneshot\
' init.rc > new_init.rc
cat init.rc > init.rc.bak
cat new_init.rc > init.rc
rm new_init.rc
chmod 0750 init.rc
echo "Service rooting added."
fi

#create new boot.img-ramdisk.gz
find . | cpio -H newc -o | gzip > /tmp/boot.img-ramdisk.gz

#make newboot.img
cd /tmp
/tmp/mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --cmdline "$(cat boot.img-cmdline)" --base $(cat boot.img-base) -o newboot.img
[Galaxy S 4 i9500 Original Android Development] supercurio:
Cool stuff, thanks!

However I see no usage for it.

The reason is that you have a custom recovery running, you can root the device already.

Patching the boot image will be an unwanted extra step.
[Galaxy S 4 i9500 Original Android Development] Chenglu:
Yes, you're right.
[Galaxy S 4 i9500 Original Android Development] romeo26222:
Ok so flashing the stoke firmware will remoce your code from /xbin, right?
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
[MENTION=3084245]Chenglu[/MENTION] is the script to be exceuted from the recovery with the unmodified / un-patched stock kernel installed, so that it will patch the boot.img with supercurio method to obtain root?
[Galaxy S 4 i9500 Original Android Development] Chenglu:
Yes, you can obtain root privileges, but it is not necessary to modify the boot.img.:D
[Galaxy S 4 i9500 Original Android Development] Phil3759:
To be more clear, you do not have to wait for someone to modify it for you. You just root any new released kernel your self

The script will repack it and modify it for you, then it will flash it

Just crazy right :good:

edit: You should release it in a dedicated thread, crediting supercurio. It will help many people to root while keeping Samsung kernel
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
Thanks for the explanation mate. I always prefer to have a stock kernel rather than custom kernels. Supercurio made my day and chengulu helped everyone by automating the root process. Chengulu should make a dedicated thread as you advised.
[Galaxy S 4 i9500 Original Android Development] rovo89:
I tested it myself. I have an S2, so I just installed it myself by unpacking /files and setting permissions manually. su-koush didn't work for me (CM10.1 nightly), so I linked su-real to the backup of my original su.

Now I noticed two issues:

1. If the app wasn't granted root permissions before, the confirmation dialog pops up for a very short moment, but with no chance to accept it.

2. Otherwise, the helper generally works, but it splits my arguments to su incorrectly.

Let me explain the second point. I call su like this (one line = one argument):

su
-c
/data.../install.sh 12345 2>&1

This is how I pass the UID of the installer to the script. But with your redirection, it ends up like this:

su
-c
/data/../install.sh
12345
2>&1

This is an important difference, because 12345 is no longer part of the argument for the -c option (and therefore not passed to the script), but interpreted as the target user (LOGIN):

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

This little change fixes my use-case, but might break others:

/system/xbin/mksh -c "/system/xbin/su-real [B][COLOR="Red"]'[/COLOR][/B]$*[B][COLOR="Red"]'[/COLOR][/B]"
[Galaxy S 4 i9500 Original Android Development] Phil3759:
Or the nightmare to pass one variable as multi arguments without splitting it into many variables. Face same issues when building automated scripts to handle --cmdline arguments that need to be quoted inside command line

This will be a big limitation for some programs requesting su rights while using this method
[Galaxy S 4 i9500 Original Android Development] DjeMBeY:
Hmmm.... something is wrong as it won't boot at all..... getting stuck on SAMSUNG LOGO.... :(
[Galaxy S 4 i9500 Original Android Development] supercurio:
Flashing the stock firmware will remove the code from xbin, considering stock firmware is system + boot + recovery + [...]

However once you're rooted you can flash the original kernel back. Not the whole firmware but only boot.img.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Stupid SU "su helper" doesn't rely on a custom kernel, I mean.. that's the whole point ;)

That's why if you have root somehow (like in a custom recovery) you don't need to modify the kernel in any way, only install su binaries just like Sutpid SU script does
[Galaxy S 4 i9500 Original Android Development] supercurio:
Yes but if you already have root.. lol :D

Edit: Oh maybe you meant not on the device itself but on a workstation. Yes, sure.

Tho it shouldn't be too useful to invest on that, a better solution is an updated su binary that does this little trick by itself without the need of any helper.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Haha good catch =) and thanks for analyzing that by yourself that's very nice :good:

I believe you're right that's exactly it, an oversight of args processing in my code.

I'll test a few more cases and release soon a v4.

The reason why I didn't notice is that I use interactive shells instead of pre-written scripts in my su apps.

Code itself being dynamically generated, there's no need to pass any arguments.
[Galaxy S 4 i9500 Original Android Development] Phil3759:
:D
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
for me xposed framework works fine with rooted ME1 kernel without any issues. Infact i dont have any problem with root accessing apps including es file explorer and everything works fine as it is suppose to
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Did you use OP's ME1 kernel as well? thanks
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
I have done one on my own and posted the link for download few post back. I dont find any screenrecorder app rom the market which supports our s4 or else i would have posted the video here.
[Galaxy S 4 i9500 Original Android Development] GSeeker:
thanks! But i've tried that one earlier and found the camera didn't work. strange
[Galaxy S 4 i9500 Original Android Development] jlevy73:
The one in the OP doesn't work, the one posted a few pages back does (at least it did for me).
[Galaxy S 4 i9500 Original Android Development] supercurio:
Yes, this Taiwanese firmware doesn't seem to work properly with the camera. Sometimes works, sometimes crashes the device.

I would say, probably not related to Stupid SU.
[Galaxy S 4 i9500 Original Android Development] marbulas:
Thx a lot supercurio! Now I got su and using lots of apps need su permission and also init.d scripts :D
[Galaxy S 4 i9500 Original Android Development] aslak89:
+1,

hey marbulas I fixed again root kernel as using supercurio's stupidsu v4.

it brings no permission error in unexpected apps.

I would not update the post on matcl yet cuz it's too often.:o
[Galaxy S 4 i9500 Original Android Development] marbulas:
Thx mate :D

If you're willing to release your new work for 3 carriers in Korea, just post them on the thread like before.

Then, I'll change the link of the post included on the main post.

I'm staring my thread with instantly e-mail notification so you can upload your work you want :D
[Galaxy S 4 i9500 Original Android Development] aslak89:
great buddy:good:

so I'm willing to upload them tomorrow. good night:D
[Galaxy S 4 i9500 Original Android Development] supercurio:
Hi guys!

I updated to v4 the demo kernels, removed I9500-ZSUAME1 because this firmware quality seems questionable (camera instability).

I also commit rovo89 fix taking care of crediting the real author in git ;) and thanks for that.

ES File explorer still gets root permissions but fails to complete its root test − I don't know why as it's not too chatty in logcat.
[Galaxy S 4 i9500 Original Android Development] Paparasee:
Can I use the method above, but replace "Adam's Kernel with the Kernel in the first post (GT-I9500 Stock + root StupidSU v4 XXUAMDK - since this is the one on my phone now)?

Thanks :)
[Galaxy S 4 i9500 Original Android Development] HS™:
I cant confirm about the kernal in the post as i havnt tried that one i would rather suggest used the adam 1.2 and will work the best its as good as stock
[Galaxy S 4 i9500 Original Android Development] supercurio:
Suggestion, when you don't know nor tried.. don't answer lol
[Galaxy S 4 i9500 Original Android Development] supercurio:
Answer is yes, except you don't need to enabled USB debugging (has no effect in download mode)
[Galaxy S 4 i9500 Original Android Development] romeo26222:
If you just find why the ES file explorer is not gaining root and fix it, this will be the best kernel out there :D
[Galaxy S 4 i9500 Original Android Development] Odia:
What is a custom recovery if it's not a custom kernel?

So you need root to get root?
[Galaxy S 4 i9500 Original Android Development] supercurio:
Chainfire's SuperSU su binary is now capable of gaining root by itself without helper.

I'm also assisting him to make an autoroot for I9500, which will make Stupid SU definitely obsolete, as intended.
[Galaxy S 4 i9500 Original Android Development] Curron:
Any one having experiece this?? After I installed root I can't uppdate or install new programs, an error message saying that It is to little storagespace. I have 6.4 Gb in free storagespace!! ??

Wath to do??

Skickat från min GT-I9505 via Tapatalk 2

Skickat från min GT-I9505 via Tapatalk 2
[Galaxy S 4 i9500 Original Android Development] supercurio:
AutoRoot for GT-I9500 is now available from Chainfire so Stupid SU is now definitely obsolete!

Just keeping this thread for reference but this project is now dead.
[Galaxy S 4 i9500 Original Android Development] eric-filth:
Sad because is a good way to keep your rom rooted with "kernel stock" for who likes.

CF Auto is perfect too but always you will need one computer to do that.
[Galaxy S 4 i9500 Original Android Development] mathieulh:
Sorry to be bumping up some old thread here, but how is modifying initramfs any different from using a custom kernel ? Don't you need root to do that in the first place ? That would certainly defeat the purpose of your script.

---------- Post added at 11:03 AM ---------- Previous post was at 10:56 AM ----------

From what I could see, it does rely on one in order to gain root access and modify initramfs, that script of yours wouldn't work without it (or another root exploit), a recovery IS a kernel, therefore a custom recovery is obviously a custom kernel.

I don't want to point at the obvious here but, considering that the SETUID privilege elevation check has been implemented to prevent root exploits from working on the device, since your script isn't a root exploit per se and relies on root access to work, wouldn't using it be some kind of a moot point ?

---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------

Thanks, I didn't l know about FX Explorer, that tool is very user friendly however so I just bought it.
[Galaxy S 4 i9500 Original Android Development] supercurio:
CF Auto Root is better on every aspects, I'm happy that sharing my discovery allowed Chainfire to update its su binary very quickly.
[Galaxy S 4 i9500 Original Android Development] supercurio:
You don't understand, the purpose of my work here was to share an exploit with other developers.

Please learn about what is a kernel, what is an initramfs, and how you manipulate an initramfs content without modifying the kernel binary first.

Because no, you don't need to be root to modify an initramfs. You do that on a computer, using firmware packages files containing everything you need.

Samsung publishes firmware updates very often and doesn't share their kernel .config, while provides updated kernel source code at a much lower frequency schedule.

Ideally we would have the .config and updated source code for every firmware published, but it's not the case.

My project succeeded in its purpose, allowing rooted new Samsung kernels on the Galaxy S4, when some were saying it would "impossible".

Qualifying my work as moot is not welcome, especially if you start by ignoring its achievement allowing today a large amount of people to use stock+root on their I9500, I9505 T-Mobile Galaxy S4 and probably more, and also as you don't understand the basic underlying concepts used here.

Take a look at the number of downloads CF-auto-root for I9500...

I found a vulnerability in Samsung's code, which is now used transparently to provide root access in su binary in a transparent way, that's was the plan and I honestly have no idea why some people come here to debate the definition of "custom" kernel or recovery
[Galaxy S 4 i9500 Original Android Development] supercurio:
Closing the thread now.

[MOD EDIT: totally uncalled for response.]

− until Samsung fixes this vulnerability.. ^^
[Galaxy S II Q&A, Help & Troubleshooting] ehsan372:
hi

i want

1-use my galaxy s2 as sound card and speaker for my pc

2-show my phone screen in my pc

please help me
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Try Airdroid or Splashtop.

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] ehsan372:
Thank.explanation please.i want connect via usb cable.
[Galaxy S II Q&A, Help & Troubleshooting] ehsan372:


This program (splashtop) for remote pc.i dont have remote pc.i want display my phone screen in the pc
[Galaxy S II Q&A, Help & Troubleshooting] WilhelmPrice:
TeamViewer allowed my tablet to play the sounds the computer is supposedly playing AND display the entire desktop complete however I think that has some delay but I was relatively far from our router back then, give it a try
[General Questions and Answers] igorsantos07:
Hey guys,

I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.

The phone is unlocked and rooted, running the stock Android 4.2.1.

I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.

I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.

I'm right now trying to copy /data into my computer. Is it of any use?

Is there anything else that I can backup before sending the phone out?

Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc

Thanks in advance!
[General Questions and Answers] Chromium:
since the phone itself still works, and the unresponsive screen is the only issue, you might be able to make a nandroid backup (complete backup of everything on phone-apps, settings, etc.)

I assume you probably have a touch based recovery on your phone like twrp or cwm touch. This is obviously an issue.

To counter this you could try using fastboot to flash clockworkmod non touch recovery. This allows you to use the volume rockers and power button to navigate.

To flash the recovery install all the correct drivers, and download the non touch cwm and place it your fastboot directory. Then boot the phone into the bootloader, and use this command:

fastboot flash recovery "name of recovery file.img"

Then from there you can boot into recovery, go to backup and restore, and finally make a nandroid backup. From there you could copy the backup using adb onto your computer. (the backups are stored in sdcard/clockworkmod/backups)
[General Questions and Answers] igorsantos07:
Thanks! I'll try that.

I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).

And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?

Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?

On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
[General Questions and Answers] Chromium:
Yep once you get the phone fixed/replaced, you may need to reflash cwm and copy the backup back onto the phone (if they wiped it)

Then just use the restore option in cwm.

If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
[General Questions and Answers] igorsantos07:
Boo =(

Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?

I should just take care on not backing up system stuff, right?
[General Questions and Answers] Chromium:
Yep thats probably your best bet. Although I would avoid backing up/restoring system stuff with TB as it causes lots of bugs.

Just use TB to backup apps+app data, and you can restore them after installing PA. There shouldnt be any problems
[MDA II, XDA II, 2060 General] asci:
Here it is my experience...

Hi,

I have received in 10 days my Brando Ultra Clear protection for Qtek 2020. Before buying this new one, I was using your basic screen protector and I was very satisfied, suggesting it to a lot of Qtek2020 users. But testing this new one I was really disappointed, because I was expecting some improvements, and I dare to say I have found only worsenings.

Here it is what I have found worse:

1- the electrostatic side, useful to the adhesion of the film to the display. Moreover washing it, its effectiveness is reduced remarkably.

2- An humidity effect on the display due, probably, to the hair bags, practically impossible to eliminate... I will try to see with the time if they disappear by themselves... I hope not to loose the film meanwhile because of the not good adhesion of the film. Note that I am using it from the right side... because from the other one it does not have no adhesion to the display at all.

3- The surface is the much most delicate one.

4- By eliminating that light opacified effect that had the surface of the previous films, very useful because it improved remarkably the sliding of the pen over the display and the backlighting or solar light vision of the display, attenuating the glares, the comfort visualization and generally the surface usage are gotten worse.

I hope this testing would be useful to improve your great product.

Best Regards

I am going to resume my old one...
[MDA II, XDA II, 2060 General] asci:
I have just replaced the old one...now it's ok...just wasted about 10 euro :roll:
[Galaxy Tab 2 Q&A, Help & Troubleshooting] gtuck1002:
is there a version of recovery clockwork or Twrp that has support for OTG for galaxy tab 2 7.0....
[Galaxy Tab 2 Q&A, Help & Troubleshooting] busarida123:
Bump
[Galaxy Tab 2 Q&A, Help & Troubleshooting] openmatrix:
Thinks no,(correct me if I am wrong):D
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Please don't create duplicate posts.

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Oh sh!t, thought xda app was drunk again.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Me too!! Since this happens almost always, I always check the time of posting. :D

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] ehsan372:
Sry.my taptalk has problem.i dont create 2post
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Its ok mate. Stuff like that happens! Just report this post and have it closed. :)

"To err is human, to forgive is divine"

Sent from my SGS II
[Xperia Play Q&A, Help & Troubleshooting] Pablete197:
Hi everyone.

I have just installed and ics rom 4.0.4 and i was wondering if there is any method to install google now because i find pretty awesome how it answer your question and thet kind of stuff.

Thanks
[Xperia Play Q&A, Help & Troubleshooting] i_like_chicken:
This is a nice app that installs google now on ICS

http://xdaforums.com/showthread.php?t=1916926

You might also want to try utter! Voice Commands BETA! on Google Play

The interface is not as pretty but in my opinion it has a lot of pontential and has extra features for root users

http://xdaforums.com/showthread.php?t=1508195

Hit thanks if i helped :good:
[Android Q&A, Help & Troubleshooting] unknown243:
Hey to all. This is my first post here, even though I have been using the wonderful advice of XDAers for quite some time now. My questions is this. I am looking to flash a custom kernel to my phone, but have not been able to figure out if I would require a specific kernel for my phone (techinally a T999V, but flashed with TMO rom, so a T999) or can I use any kernel from any Glaxy S3 variant? I know with ROMs you must ensure the correct one is used or you end up with a paper weight. Would the same be true for kernels as well? If I did happen to have a bad flash, would ODIN/NANdroid save my bacon?

Mmmmm...Bacon...

Thanks in advance guys and gals! Looking forward to being a contributing memer to this site, and helping out wherever I can!
[Android Q&A, Help & Troubleshooting] shimp208:
Just like when flashing ROMs it is even more important to make sure the kernel your flashing is specifically meant for your device. That being said I would recommend taking a look at this guide that's lists available Touchwiz and AOSP kernels for the T999 Galaxy S3 http://xdaforums.com/showpost.php?p=36426656&postcount=2. Only flash kernels for your version of the Galaxy S3 and never flash an international version Galaxy S3 kernel on a US/Canada version Galaxy S3. It is sometimes possible to recover from a bad flash through a NANDROID backup, oftentimes a ODIN restore will be needed.Let me know if you still have questions :).
[Android Q&A, Help & Troubleshooting] unknown243:
Awesome, thanks! So in other words, I need to ensure my kernel is specifically for the T999 or T999V model of GS3, I cannot use one for ATT or VZW or anything, dtrictly TMO T999 or T999V...

Thanks!!!

Part 2 - I dont quite understand the difference between TW and AOSP, as during my learning days AOSP and AOKP were explained to me in a false way...Thanks!