yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Switch Blade:
I have seen various thread regarding the removal of bloatware. Most are directed towards AT&T customers, but some mention us Canadians. Regardless, is there a ROM, or a procedure available to accomplish the following:

1 - root

2 - remove bloatware (in my case Rogers bloatware, and other needless apps)

3 - unroot ***

***The logic in my mind is that an unroot would allow for OTA updates etc..

I love the S4 and most of its features, just don't need half the stuff on here........thanks.
[AT&T HTC One (M7)] Cell Master:
http://xdaforums.com/showthread.php?t=2280995

Sprint received the 1.29 update

Fixed the button and home button issues
[AT&T HTC One (M7)] WA_Bob:
Eh, I'm sure it will be released eventually. (Probably not too long from now) If you're rooted, most of the HTC "stock" ROMs already have this stuff baked in. If not, our time will come! :good:
[AT&T HTC One (M7)] Cell Master:
I hope our update rolls out soon
[AT&T HTC One (M7)] jeeptrash:
Don't count on it, this is ATT we are talking about. They take forever with updates.
[AT&T HTC One (M7)] Cell Master:
AT&T should eat a bag of dicks!
[AT&T HTC One (M7)] CheesyNutz:
I work there and have seen nothing on the books about an ota
[AT&T HTC One (M7)] tyshemi:
And here's some more info that could be good for us in a way

Taimur Asad (@TaimurAsad) tweeted at 4:22 PM on Fri, May 17, 2013:

Android 4.2.2 With Sense 5 For HTC One X Reportedly Being Prepared For Release http://t.co/5laQRurDva via [MENTION=518401]redmond[/MENTION]Pie

(https://twitter.com/TaimurAsad/status/335505701881405440)

Get the official Twitter app at https://twitter.com/download
[AT&T HTC One (M7)] Cell Master:
That is the One X
[AT&T HTC One (M7)] tyshemi:
Duh I know that but means that at least making some headway on HTC devices and hopefully if they are done messing with that we should be soon
[AT&T HTC One (M7)] Cell Master:
It means that an OLDER phone will be running a newer version of android than what we have :/
[AT&T HTC One (M7)] Skizzy034:
I will seriously lmao if the One X gets that update before we do.
[AT&T HTC One (M7)] daddioj:
well I HOPE they atleast release a damn RUU already!
[AT&T HTC One (M7)] Cell Master:
I'll stab a ***** if the One X get that update before us. I'm hoping our update comes tomorrow.
[AT&T HTC One (M7)] Napoleon_PhoneApart:
Feel better, son?
[AT&T HTC One (M7)] Cell Master:
No
[AT&T HTC One (M7)] aka757:
Quick question:

What happens to those of us who have a SIM unlocked One with a custom ROM (CleanROM)? Will we still get the firmware update in some way, for example will be able to just flash it or something? The option in the settings menu "AT&T Software Update isn't there for me anymore.

TapaTolkien
[AT&T HTC One (M7)] gunnyman:
As soon as an update hits someone will release a stock rooted version. No need to worry about ota releases ever again.
[AT&T HTC One (M7)] Cell Master:
True, but those of us that get OTA updates will get the stock AT&T update first :)
[AT&T HTC One (M7)] Tower1972:
its often not long that the OTA is out before its rooted...less then an hour in most cases :P
[AT&T HTC One (M7)] Cell Master:
An hour and the ease of pushing 1 "update" button! ;)
[MDA II, XDA II, 2060 General] georkal:
I was wondering, has anyone confirmed that windows mobile second edition will be availiable for XDA2 in the near future?
[MDA II, XDA II, 2060 General] Rudegar:
some people have claimed to have it for testing but no proof have been represented to us

rest asure that when somebody starts to share it you will see the news on the front page of this site

you can use the search function in this forum to see how many people asked this question before and if you are lucky maybe you'll find posts from people claiming to have it aswell
[MDA II, XDA II, 2060 General] ajong:
SECOND EDITION

Yeah..........

I am boring !!!!!!.

waiting .... wait....wait ......wait....Zzzzz....zzzz....zz
[MDA II, XDA II, 2060 General] powerppc:
I've been waiting patiently, but I have a feeling my hope will be ignored. So I'll just twiddle my thumb even more until I can go back to sleep and dream some more about Second Edition.

I really don't see a point having the SE, unless if you use Pocket Internet Explorer a lot. But it'll be nice to have the option of landscape.
[MDA II, XDA II, 2060 General] georkal:
If you see the photos of the new HTC - Blue Angel here :

http://mobile-review.com/pda/review/htc-blue-angel-en.shtml

you will notice at the today screen that there are some usefull new indications like gprs usage and uptime/battery charge level.

I wonder if the SE update for XDA2 will have them.
[MDA II, XDA II, 2060 General] rahjinoh:
That's just SPB GPRS monitor and UpTime Freeware.
[MDA II, XDA II, 2060 General] georkal:
Thanks for the tip! :D

I'm new in ppc world.I just bought my XDA2 a week ago!

Very pleased though in any aspect (expandability,performance) compared to my previous P900 smartphone :wink:
[MDA II, XDA II, 2060 General] ajong:
Release by Imate

Read this :

http://xdaforums.com/viewtopic.php?t=11431

so, we wait until 2 month later (this year)

:twisted: :twisted:
[MDA II, XDA II, 2060 General] powerppc:
Like I would believe anything from a CSR to tell me it'll be out. Right now it's just vaporware. Besides that, even if i-Mate would have an upgrade, their ROM is different than XDA II.

Thanks for the info anyway, it was a good find.
[MDA II, XDA II, 2060 General] ajong:
from o2 ??????

maybe from 02 : :?: :?: :?:

this link :

http://www.tekguru.co.uk/phpBB2/viewtopic.php?p=24274

this link, i found in `forumponsel` website.

OOT : who is `CSR` ???, what the `meaning `vaporware`

thank's

---------------

special to pak powerppc, kalau online disini lagi

ngomong indonesia aja ya.

sekali-sekali gak papa!!

bhs.inggrisku payah banget!!
[MDA II, XDA II, 2060 General] powerppc:
lol, love your sig. CSR = Customer Service Rep, Vaporware = a software that's mostlikey vapor, like gas, the air.

Vaporware seperti softwarenya pasti nggak keluar.
[MDA II, XDA II, 2060 General] Rudegar:
all roms from all Himalaya devices though
[Galaxy Note II Q&A, Help & Troubleshooting] JOGEXAI:
Hi guys i wanted to ask how to get galaxy nexus home screen/ / theme on galaxy note 2 or tell me any themes so i can switch to it without using a launcher...!!!
[Galaxy Note II Q&A, Help & Troubleshooting] bharatgoyal:
Use a cm or aosp based custom rom .

Sent from my Note II
[Galaxy Note II Q&A, Help & Troubleshooting] KEJA2k:
Yep I would recommend the Apex launcher as the least intrusive and probably the best for changing themes and is the easiest on the battery as well. I had tried using SPB 3D but it is a battery hog so I don't recommend using it. You will find a wide variety of themes that are, very nice. Give it a shot, Apex I think you'll like it better than Nova. You will need the S Pen control app as well to keep full S Pen capabilities and add some improvements, like notification if you forget to redock the pen and walk away.
[HTC One X+] ac3kill:
Has anyone seen there att one x + pick up 3g ? I ask because I have never seen mine say 3g only lte 4g edge g-for gprs but that's it. I don't want to be on 3g for good but it would be nice if my phone would connect to 3g in areas where I only get edge or gprs and a iPhone sitting next to me has 3g why is this ? Any ideas ?

I
[HTC One X+] dmcwhirter72:
Could just be the indicator doesn't change. I have a 3g microcell in my house (long story) which I don't believe is even 4g capable and my HOX+ still says its 4g. Doesn't really bother be either way, I still get better signal strength than I did with my iPhone 4.
[HTC One X+] ac3kill:
Us Haas thinkin 4g and 3g ate the same since 4g is just 3.75 3g w/ enhanced backhaul. So pretty Much any time I see 4g symbol its really a 3g tower just all of them in my area have backhaul so I never see 3g symbol.

Please correct me if im wrong
[HTC One X+] gothicasshole:
The 4g is a 3g back hauled hspa+ system it gives better speed than reg 4 g its marketing I assure you but most likely 4g. Is the back hauled hspa+

remember the HTC inspire 4g and the galaxy s2 both had the 4g hspa+ radios and it was marketed as 4g
[HTC One X+] kylealanr:
Marketing Signal Indicators

I can confirm that in my area with a Nexus 4, the phone will switch between H (3G) and H+ (4G) AT&T HSPA and HSPA+. With the One X+ however, it will only display 4G LTE, 4G, and E. Also, Viper XL+ lets you flash the stock international signal indicators which display LTE, H+, H, and E in my area. The decision to only include the 4G HSPA signal indicator is most likely a marketing decision.
[Sprint LG Optimus G] spackmanbr:
Running Imperium Initiative. Has anybody tried using the new Hangouts app for video chat, and if so, have you been able to send outgoing video? Incoming video is fine, but outgoing just displays my G+ picture and a toast notification "Camera Error."
[Sprint LG Optimus G] polzovotel:
Same problem here on Nexus 4 - seems to be a specific problem with LG branded phones. On my other Galaxy S2 it is working ok. After trying a video chat and a camera error I must reboot the phone to get camera work again,

BTW, if you open Google+ and initiate a video hangouts there - video should work.
[Sprint LG Optimus G] spackmanbr:
Awesome. Thanks. Just wanted to make sure I wasn't the only one.

I noticed the same thing with requiring a reboot to get the camera working again. Thanks for pointing out the G+ workaround.
[Sprint LG Optimus G] aero449:
Worked perfect for me. Running Lifeless 14. No camera error and tested video with multi-person hangout this morning. I've also installed the .xml file from _Epic's camera mod, if that's relevant.
[Sprint LG Optimus G] reddragon72:
I am on stock+root/unlock. I have the camera XML installed and have used it 5 times for vid calls and no problems. Front and back camera's FYI and works great on 4G
[Sprint LG Optimus G] Xiutehcuhtli:
Can 2nd that Lifeless 14 runs this flawlessly, I used it for about 20 minutes last night to give my bro a tour of our new house.
[Sprint LG Optimus G] spackmanbr:
I wonder if there's a problem with Imperium Initiative then. I believe Epic's mods are included. I'll probably jump to an AOSP rom soon anyway.
[Sprint LG Optimus G] mfincken:
I have the same problem on Optimus G e971 running the carbon Rom from Paulicat. I tried using the XML mod from epic but still the camera error in hangouts. I'll probably try a different Rom soon.
[Sprint LG Optimus G] spackmanbr:
Switched to Venum (which is based off of Lifeless, goo.im has been slow so I needed a rom with faster hosting), and no more camera error. I found a forum post with a few people saying that Beats audio was causing the hangouts video issue, so that's why I switched to a rom with no Beats.

Any of you guys with camera errors use Beats or have some other DSP manager installed?
[Sprint LG Optimus G] dbabo:
i have a problem with the video calls under Jedi ROM. I can see ppl they can't. Rom does have BEAT preloaded. How is this related?
[Sprint LG Optimus G] spackmanbr:
I have no idea, and I can't give you a technical explanation. All I know is that while searching around for a solution I encountered a few others who had made the connection that Beats caused problems, and when I switched to a ROM without Beats my Hangouts worked perfectly. I do know that in the past Beats caused various problems for people on the Evo 4g. If you try removing Beats or switch Roms altogether, let me know what happens.
[One (M7) Q&A, Help & Troubleshooting] TylerDurdenK:
Hi guys,

I have jut received notification of an available update to my phone, and I have taken a nandroid backup and attempted to update. This failed and left me in recovery (CWM). I then tried manually updating using the .zip file from the download folder, but this left me stuck too.

How can I apply this update?

Thanks
[One (M7) Q&A, Help & Troubleshooting] ilal2ielli:
Did you remove any of the stock apks? What customizations have you done? Typically the ROM needs to be completely stock before applying an OTA update.
[One (M7) Q&A, Help & Troubleshooting] TylerDurdenK:
I'm pretty sure my rom is stock. Apart from rooting and apply changes to the framework.
[One (M7) Q&A, Help & Troubleshooting] ilal2ielli:
You'll need to be unrooted, stock, and with stock recovery for the OTA to take effect.

If you need stock ROMS and recovery, they are available in the development forums.
[One (M7) Q&A, Help & Troubleshooting] edepot:
Did you root regular HTC One or the China edition HTC One (802w)? I am in the same situation as you if you are using the 802w. Have you tried resetting to factory default, update it, THEN do the unlock/root?
[One (M7) Q&A, Help & Troubleshooting] Emilml:
You should follow Mikes thread here http://xdaforums.com/showthread.php?t=2265618 it explains how to unroot etc. and after that you should be able to update your rom again.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Hi guys!

As some of you must have noticed, latest Samsung GT-I9500 firmwares carry a kernel configuration supposed to prevent SETUID privilege elevation.

Stock unmodified firmware with root is my preferred setup but also a strong dependency for all my development, for me this change is a massive setback if not a dealbreaker.

While poking around I found in about an hour something weird that reveled being a vulnerability, so I created a little thing to make it useful for now.

README:

INSTALL

Source code

On GitHub

License ;)

Kernels downloads, only for demo purposes of the concept, you can flash back original Samsung boot.img once rooted

GT-I9500 Stock + root StupidSU v4 UBUAMDE

GT-I9500 Stock + root StupidSU v4 XXUAMDK

GT-I9500 Stock + root StupidSU v4 XXUAME1

What's next

Owners of Qualcomm Galaxy S 4 devices experiencing the same dificulties with Samsung the anti root strategy might want to try this method, please let me know if you're ready for some experimentations.
[Galaxy S 4 i9500 Original Android Development] muhamet:
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
Going to try this on latest LE1 stock kernel now .....thread is in correct section

edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..

Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Here comes the master :D welcome to SGS4 development forum mate.. (rahulzeven from twitter here :D)
[Galaxy S 4 i9500 Original Android Development] GSeeker:
So the BEST thing's just happened?!:laugh::good:
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.

Download Link

Edit: New file uploaded
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Thanks fo much! Will Titanium Backup work on this kernel?
[Galaxy S 4 i9500 Original Android Development] walda:
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.

... tapat*lked
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
wrong file uploaded. Please download the same in 5 minutes. Uploading is on and the kernel date should be MAY 04

---------- Post added at 12:33 PM ---------- Previous post was at 12:28 PM ----------

it should work as i dont use titanium backup and instead i use gobackup pro and it works fine anyway
[Galaxy S 4 i9500 Original Android Development] jlevy73:
MDK from OP working good, thanks
[Galaxy S 4 i9500 Original Android Development] aslak89:
I'm trying to repack the kernel of korean gs4,

but I am a noob in kernel devs.

I can edit ramdisc, but fist trying in initramfs, zImage.

Is rooting directory means both root.sh and files(folder)?

and paste them on first class route?

hope you give some advices.. thanks
[Galaxy S 4 i9500 Original Android Development] grgsiocl:
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
[Galaxy S 4 i9500 Original Android Development] aslak89:
then, is not necessary to recompile zImage?

ok I m going to try it right now, thank you grgsiocl:)
[Galaxy S 4 i9500 Original Android Development] supercurio:
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.

Great then :)
[Galaxy S 4 i9500 Original Android Development] supercurio:
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.

Which gives you several usage options:

keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed

you can flash back the official kernel and still enjoy root the same.
[Galaxy S 4 i9500 Original Android Development] aslak89:
Thank you for awsering:)

then I repacked my kernel but still not work.

copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.

I guess permission is the thing,

attach my shots

hope you loot at once.
[Galaxy S 4 i9500 Original Android Development] Svid:
He will after he will come back from his vacation.
[Galaxy S 4 i9500 Original Android Development] Chainfire:
I'll look into a fixed CF-Auto-Root for the I9505 as soon as I'm back on Sunday. I imagine that will be tested by Sunday evening, with a I9500 test version available sometime Monday. If all is well :)

This is because you're not installing the backup su binary. The UI app detects this is missing and triggers an update. Bug in StupidSU :P
[Galaxy S 4 i9500 Original Android Development] supercurio:
Alright I'm adding some logging in my scripts so you'll be able to see what's happening − or not ;)
[Galaxy S 4 i9500 Original Android Development] DjeMBeY:
Brilliant news!!!! Thanks a LOT!! :)

Let's make it work!! :) It will be AWESOME if I could use latest STOCK Kernel in my ROM's......

I'll give you a hand :)
[Galaxy S 4 i9500 Original Android Development] hua_wuxin:
I repacked a stock kernel with the Android Kitchen tool from dsixda, same problem occurred, root.sh lost execution permission. After move root.sh to /sbin (and modify the references to it accordingly), it worked. Perhaps Android Kitchen is not handling file permissions in user-added folder properly.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I find that read-me claim about security quite pompous and stupid, in the end you're still relying on the user to flash a custom boot image.

This defeats the whole point of the anti-root mechanism, as soon as you're making users flash something it's game over anyway, whatever method you use, be it recompiled kernel, binary patch, or this method.
[Galaxy S 4 i9500 Original Android Development] Phil3759:
Thank you for this head up

However, this is not really a bug or vulnerability since it still needs flashing a repacked boot.img

Hope Samsung doesn't fix it in a harder way as I see it is enough fare: stock boot.img cannot be rooted, while we still have option to use stock kernel repacked in a custom boot.img

edit: cross post with above answer
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Strange. I flashed this kernel over ME1 firmware, didn't get root.

What did i do wrong?

update: never mind, use OP's MDK and now rooted.
[Galaxy S 4 i9500 Original Android Development] supercurio:
What do you mean by stupid exactly?

Is it humor, related to the name or just offensive.

It seems you didn't understood what Samsung Anti-root strategy is, why I'm against that nor what my effort is about.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Yes, there's a vulnerability exploited here.

Samsung "anti root" kernel feature is supposed to prevent rooting via setuid permissions on stock kernels.

And this is just what my "su helper" does here.

Flashing a modified boot.img is only an easy installation method for this proof of concept. It could be a custom recovery or whatever.

Root stays active even after you flash the original boot.img back, as described.
[Galaxy S 4 i9500 Original Android Development] Phil3759:
I get your point,

Have one question please:

Does repacking recovery.img with such "secured" kernels also affects recovery functions and root access in adb?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It seems you didn't understood what Samsung Anti-root strategy is; it's for unwanted exploits and security.

The simple claim that you broke that security through this exploit is what I call stupid: You did not break it, you just took the back door that has always been opened. In terms of security it's the same as rooting through a recompiled kernel or the binary patched one. If Samsung wanted to prevent this they'd lock the bootloader and disallow custom boot images.

As far as I'm concerned, repacking a stock kernel already makes it a custom kernel. The initramfs is the gateway in terms of permissions, so of course if you alter it, you gain access that wasn't there.
[Galaxy S 4 i9500 Original Android Development] supercurio:
Nope.

Please take a look at the source code, it's extremely short ;)

https://github.com/supercurio/stupid-su/blob/master/stupidsu/files/su#L7
[Galaxy S 4 i9500 Original Android Development] supercurio:
Seriously, please read the code and test by yourself, you're commenting something else that what I share here.

Do you really think I'm calling an exploit an insecure boot image? Come on, this is kinda insulting :silly:

Also, maybe you think that breaking standard Linux setuid feature is a good thing for security, but please don't ignore the fact some original developments rely on it for ease of use and distribution, allowing powerful mods without flashing a custom kernel (as those are very varying in terms of quality control)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
:eek::eek::eek:

That's a whole different issue which simply doesn't matter for what the prevention was meant for; again: unwanted gaining of root. So again, if users wanted to gain root, this mechanism never prevented them in doing so from the very beginning. You're just adding another angle to it (Good work and bravo), but it's neither a vulnerability nor a defeat of the mechanism.

And as a sidenote: The current sources define four different configuration options:

# Add rooting prevention

# CONFIG_SEC_RESTRICT_ROOTING is not set

# CONFIG_SEC_RESTRICT_SETUID is not set

# CONFIG_SEC_RESTRICT_FORK is not set

# CONFIG_SEC_RESTRICT_ROOTING_LOG is not set

The first one is interesting because there's no mention of it other than the configuration files, so we might see a different implementation from Samsung in the future to simply prevent that. Or not.