yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M8)] schmeggy929:
yeah there is a setting in the Default.xml and level is at 4. I change it to 2 and make a flashable zip for ya.
[Sprint HTC One (M8)] captain008:
Dudebyour the man thanks.
[Sprint HTC One (M8)] schmeggy929:
Here try this.
[Android Q&A, Help & Troubleshooting] cleverior.ipul:
Hello XDA lovers :D

i just built custom kernel for my device. but i have this problems. on stock kernel, i can see list of folder in file explorer on ADT but when i use custom kernel i cant see anything. FIle explorer is blank. could anyone please help me ? thanks in advance.
[Android Q&A, Help & Troubleshooting] cleverior.ipul:
up up

no body here ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] pavana:
Dear I9000 friends,

i've noticed that some of the slim, fast ROMs allow me to use swype/slide function on Android keyboard (or Google keyboard), so I do not need to install rather big Swype which I bought. Most of the ROMs like SlimKat or CynaAOSP allow swype function in English or German, but not in Croatian language. However, this is one of my most important functions and I am lost among of all ROMs in this forum. (BIG THANKS AND CONGRATS TO ALL DEVELOPERS FOR PUTTING A LOT OF EFFORT IN THIS WORK).

Other than this thing with swype/slide function for Croatian languange, I only want to have Maps and Whatsapp function as fast as possible and have the ROM as fast as possible that would work with these premises (couldn't care less if this is 4.4, 4.3, 4.2 or 4.1).

Could any of you good souls suggest me a FAST ROM which would allow me to use swype function in croatian languange and be fast on my Whatsapp.

After trying so many different ROMs from different developers, I am LOST in TIME and SPACE and would greatly appreciate if you could point me towards a ROM with Swype/slide function integrated and be as fast as possible. As the father of the family, I have the slowest Samsung of all ( :) ), but I guess it is typical for a family man. Unfortunately, I do not have so much money to invest into a new Samsung 5.

Which ROM with Swype/slide function would you recommend me? All other functions are more or less not important since I communicate mostly thorugh Whatsapp with my family and friends.

THANX for ALL/ANY of your suggestions/recommendations/critique etc.

Best regards,

Pavana
[Galaxy S I9000 Q&A, Help & Troubleshooting] Nhuts:
Hi there,

i'm testing many roms for my i9000 but 1st thing i do is installing the Touchpal X Keyboard from Google Play, try it out. I got the recomendation here from the Forum. It says it works for your language, too. I only tested in german and english, works perfect for me.
[G2 Q&A, Help & Troubleshooting] pockiee:
[Q]Tried to flash cm10.2, can't get past LG logo with "secure boot unsuccessful"help!

I'm panicking right now because I just got this phone yesterday. I'm not sure if this is soft bricked or hard bricked? I'm a complete noob, all I want is for my phone to be fixed.

I flashed twrp through flashify, then downloaded cm 10.2 and gapp then let it do it's job, but now, my phone doesn't even work. The LG logo comes on, then directly goes to a screen that says "secure booting unsuccessful cause: " then turns off.

Am I totally screwed?
[G2 Q&A, Help & Troubleshooting] tdevaughn:
Install your backup, then make sure you installed the correct version of cm
[G2 Q&A, Help & Troubleshooting] pockiee:
Can you please explain to me how to install the backup? Once again, I'm a total noob :(
[Galaxy S 4 Q&A, Help & Troubleshooting] MarkMRL:
1. Why the ?%$& is the album art getting displayed in full screen in the lock screen? It looks like absolute ****. Can't seem to find a way to disable this disgusting feature.

2. Why isn't my preference of keeping the lights under the buttons constantly enabled? After a while they just don't turn on anymore.

3. Any way to get something resembling realistic colors on this god awful screen? Jesus christ the screen on my Xperia S was way better than this. The various screen modes don't seem to make any difference.

4. Any way to disable the shutter sound on camera? I mean what were they thinking, making it impossible to disable?

5. Can I get the Sony WALKMAN app and widgets on this phone and if yes, how?

6. What the hell is KNOX?

7. How do I get rid of S Voice once and for all? The stupid gimmick keeps popping up and talking and I don't know what the hell it wants from me.

There's more, but I'm done for today.

8. Suggestion on how to deal with buyer's remorse?

Thank you.
[Galaxy S 4 Q&A, Help & Troubleshooting] raksan:
It seems to me that what you don't like about S4 is the software. Sure, it packs lots of crap wares. I too can't stand those so I have to rooted and customized those.

1. Album art is kitkat feature, it exist also in AOSP and no option to disable it.

2. Mine stay on if I chose "Always on"

3. You're used to LCD screen, granted LG G2, HTC One... screen are better, not sure about Xperia S. What I love about Amoled is true black, viewing angle, battery consumption... however color reproduction is slightly off, but far better that Amoled it replaced.

4. Mine; go to camera pp > Settings > 3rd tab > Shutter sound > off.

5. Not sure, it might just like installing app... you gotta search in this forum.

6. KNOX is some enterprise feature... not sure anyone use it. But flashing fw could lead to KNOX warranty void and make your phone lose warranty.

7. You can disable S Voice app.

8. I'm not sure.

Hope some one will give you clearer info on this.
[Galaxy S 4 Q&A, Help & Troubleshooting] MarkMRL:
Thanks for trying to help me. I'm sorry if I sound mad in my post but I expected a lot more and was pretty disappointed. And yeah, my main issue is the software, it looks bad and it's not as usable and refined as the Sony UI I was used to.

That being said

1. It's too bad you can't disable fullscreen album art, it looks so bad.

2. Mine also stay on for a while, then all of a sudden they're off and there's no way to turn them back on again unless I fiddle with the settings. What could be the problem?

3. Yeah, screen is just a matter of getting used to. I'm more used to a realistic color palette with lighter whites. This looks a bit off to me, and whites are slightly tinted but it seems there's no way to fix it (on Xperia there was a "white balance app", Samsung doesn't seem to have an equivalent).

4. Why is it not there on mine? I searched everywhere for it, it's nowhere to be found. Maybe it's because I have the stock Italian firmware? Which firmware are you using? On Xperia there were various variants of the same firmware, I flashed a "WORLD" one which had no third party bloat, is there a similar one for Samsung?

By the way, I rooted the phone by flashing some file from Odin, but I'm having issues: for example, I tried to apply the hosts patch with adaway, and it doesn't seem to work properly, also, I can't seem to get Android Commander to detect the phone no matter what, and I tried to install CWM using ROM Manager from Play Store, and that also doesn't work (I still have the stock Samsung recovery that's completely useless), even though ROM Manager says I installed CWM.

And one last question, how do you know if a new firmware is available? Since I rooted and tripped that Knox BS, it now says I'm not original anymore and I'm not going to receive any more updates. Is there a website I can check for firmware updates? My phone is an unbranded i9505.

Thanks in advance.
[AT&T, Rogers HTC One X, Telstra One XL] FlubbedJohn:
I have used the WeakSuace apk to successfully root the HTC ONE XL on Stock 4.2.2! I hope this will help every one on the 4.2.2 update.

Credits:

vuln - jcase

exploit - jcase & beaups

icon - mattlgroff

Dr_Drache - lots of testing

http://xdaforums.com/showthread.php?t=2699091 <-------- Click for instructions, download, and credit etc.

NOTE:

-It might say root failed or something, just run the app again and install SuperSU from playstore

-This root is temporary, every time you reboot, the device will automatically reroot

-Tested on ATT variant

-Not sure if recovery or installing roms will work

-Not responsible for anything that happens to your device

ENJOY!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
This is in the right section.

Sent from my Evita

---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------

If this is indeed confirmed to be working by some others, you might want to change the title to "at&t One X 5.18 Root Method". All other variants of the Evita are able to be rooted via traditional means, and have been the whole time, only the at&t variant hadn't been able to.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Agree. General is the correct forum section. Development is for posting your own work. Linking to somebody else's thread is not Development.
[AT&T, Rogers HTC One X, Telstra One XL] scotty1223:
Have you tried firewater after achieving root with weaksauce? It's working for the vzw one with 4.4.2
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
I have tried with no success on evita stock 4.2.2.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What about using the hex edit method to change your CID after using Weaksauce?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
Already tried. Fastboot oem readcid ---- cws_001.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
So basically Weaksauce is useless for this cause.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
What about this method http://xdaforums.com/showthread.php?t=1732980? Is it safe? Don't want to brick my device..
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Did you read the first pre-requisite?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
Sure. But in downloaded zip spoofpartitions/mmcblk0p4MOD has cid 11111111 and in mmcblk0p5MOD (offset 00000010) 11111111. Steps are similar to this http://xdaforums.com/showthread.php?t=1671396 where "8. Change CWS__001 to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well". Am i wrong? Or there is another hex editing method?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
My point was that you need root and SuperCID already. That method is to unlock your bootloader, and is really only for a specific firmware version. What is your end goal? What are you trying to do?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
I'm trying to unlock bootloader. I thought once i get supercid i can unlock it through htcdev.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yes that's true, but how is the method you linked to going to help you?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttol3g:
I dont know. Thought these "spoofpartitions" do the trick. So mmcblk0p5,6,13,26 not needed?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The problem is you're not paying attention to the details, the first pre-requisite is that you already have root and SuperCID, plus that exploit is specifically for a very early firmware. You need root to do that, and you can't get root until you've unlocked your bootloader, see where I'm going here? My suggestion is to try Weaksauce, and then see if hex editing your CID will work with the Weaksauce temp root. I believe this is your only option at the moment.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Raistlen0:
Ok. Hope someone can make this info helpful. Weaksause does work on evita ATT. I don't know what use having root to the xbin folder does for us. Please fill me in.

I did get Firewater to run by copying it to the folder /data/local/tmp. Using adb you can chmod 755 those folders and copy not push Firewater there and then run it. I get through 12 bottles then it fails. Perhaps if we knew what other folders needed more rights for firewater we could change them too.

Anyone know what firewater does?

I also tried the manual hex edit. Can't get my edited file to save to the needed location and can't change that locations rights with adb.

More ideas to try?
[AT&T, Rogers HTC One X, Telstra One XL] scotty1223:
Did you meet all of firewaters prerequisites:? Including ADB reboot and having a working data connection?

Was fire water running in a root shell?
[AT&T, Rogers HTC One X, Telstra One XL] Raistlen0:
Ok not all prereqs because it wanted you to push with adb but that did not work and yes a reboot but you have to chmod the folder before running firewater. WeakSauce is only temp root so after reboot the 755 rights to /data /data/local and /data/local/tmp have to be re-given. So you can not run firewater right away. Now the copy of firewater does stay in that location after a reboot so you don't have to recopy it.

Data connection was a yes. It wasn't the best connection but it had one at the time.

Firewater has a prereq of being rooted and unlocked boot loader so maybe that's the problem too.

All I want is to get my CID changed so I can get my bootloader unlocked.

I am hoping letting everyone know that there are other folders that permissions can be changed on (not just xbin) with using weaksuace; will maybe help someone figure away to get a full root so the CID file can be edited.
[AT&T, Rogers HTC One X, Telstra One XL] joantwift:
thanks, I will try that.
[AT&T, Rogers HTC One X, Telstra One XL] AyohGe:
Great stock rom. Pretty fast too.
[AT&T, Rogers HTC One X, Telstra One XL] jcase:
I wrote WeakSauce, and another root for this phone early on (dont recall the name) also helped with FacePalm.

WeakSauce was actually developed on this model because I had it here. What is the issue with getting root and s-off? Someone ping me with details and I will whip up something to get s-off going on it.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Weaksauce works, verified by [MENTION=4523921]zounduser[/MENTION]. Once a user has root via Weaksauce they should be able to hex edit their CID to SuperCID, which will then enable them to unlock the bootloader etc etc. Just waiting on confirmation from zound on whether hex editing the CID is working for him.
[AT&T, Rogers HTC One X, Telstra One XL] jcase:
I'm aware it works, I used evita when developing it. Does Forrester not work for s-off?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I don't think anybody has actually attempted the s-off component yet, from memory. If they have they haven't reported any findings.
[AT&T, Rogers HTC One X, Telstra One XL] gigel_georgel:
On my stock/unmodified 4.2.2 ATT HTC One X I successfully gained temporary root with Weaksauce. The first time I ran it said "Root failure" then I got a message saying "Tampered detected.. rebooting". Phone rebooted and I ran Weaksauce again. It said "Root failure" but then when I ran a second time it said "Already rooted" and I was able to install SuperSu.

After that I tried Firewater (8.0.4.11 - the latest that I could find) and it didn't work for me.

First, I'm a bit confused about the instructions; the first thing it says to do is adb reboot, even in the instructions specific for Weaksauce, although they know full well Weaksauce needs to be run after every reboot in order to be root again.

Anyway, I did a reboot, then ran Weaksauce (again the same ritual - first "Rooting failed, then Already rooted"), then continued with

adb shell

su (this worked with supersu as expected)

chmod 755 /data/local/tmp/firewater

/data/local/tmp/firewater

The first time I ran this, it went through 3 "bottles" or so, and then displayed something to the effect of "this funk has some skunk" and "force (FORCE!!!!) reboot your phone and try again." The phone was indeed frozen so I had to do a hard power down (holding the power button for almost 10 seconds).

When it came back I tried firewater again (weaksauce first), and this time it stopped at

preparing, one moment

The first bottle is open

chugging..........

nasty, need a chaser

Tried several times and each time it stops at different (early) stages, without any hint of what exactly it was that failed.

I rebooted the device in fastboot and the S is still ON, although it now says "Tampered" - I'm not sure if that comes from firewater or Weaksauce (most likely the latter since I got that message on the android screen the first time I ran Weaksauce).

I would also like to add that whoever refuses to publish the source code but requires an Internet connection on the phone while their software is running under root, is at least suspect in my opinion. I ran it only because I don't store anything of value on my phone (no "mobile" banking or anything, and reset to factory before trying out all this so that erased even the email accounts).

If anybody has any suggestion about how else I could try to S-OFF, please let me know.

I think I'll try hex editing the CID next.

Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] gigel_georgel:
My attempts to write to /dev/block/mmcblk0p4 and /dev/block/mmcblk0p5 seem to be silently ignored.

I did:

adb shell

su

dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4

dd if=/dev/block/mmcblk0p5 of=/sdcard/mmcblk0p5

then went in with a hex editor and changed /sdcard/mmcblk0p4 and /sdcard/mmcblk0p5 to replace with supercid 11111111.

Then

dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4

dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5

Then, in order to verify:

dd if=/dev/block/mmcblk0p4 of=/sdcard/cid_backup/mmcblk0p4

dd if=/dev/block/mmcblk0p5 of=/sdcard/cid_backup/mmcblk0p5

Then went in with the hex editor and looked at /sdcard/cid_backup/mmcblk0p4 and /sdcard/cid_backup/mmcblk0p5

and they still have the old cid in there.

All this under root and I didn't even restart the phone in between. I tried this a dozen times. Everytime the command seems successful (e.g. I get success messages such as: 2+0 records in

2+0 records out

1024 bytes transferred in 0.007 secs (146285 bytes/sec)

Any clue?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'd be very careful about accusing the authors of Firewater of being suspicious if I were you. If it wasn't for those guys and jcase we wouldn't be able to root any HTC phones, period. Those guys have done more for modifying HTC devices than anyone. They haven't released any source code because the exploit belongs to them, it is not open source and nor should it be.

Now, just as a side note you didn't need to run Weaksauce before every attempt of Firewater.

Sent from my Evita

---------- Post added at 05:24 AM ---------- Previous post was at 05:17 AM ----------

My only other idea would be to install Goo Manager from the Play Store and then try to install a custom recovery. If you can install a custom recovery via this method then you might be able to install a fully rooted ROM. This is a bit risky though because you have no way of backing up your stock recovery. There's also no guarantee you'll be able to install a ROM. If you make a backup of your current system though you should be able to restore it if a ROM install doesn't work. If you decide you want to try, just grab it from the Play Store, open it, grant root access, and then select "install OpenRecoveryScript" from the three dot menu (shown in screenshot).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] jcase:
I personally won't run binaries that I believe are suspicious. Running binaries you find suspicious outside a VM is foolish. Even in a VM it could be, they might be able to escape the virtual machine.

These suspicious binaries, since they gain root and turn off signature verification, could be planting bootloader level root kits. Factory resetting wouldn't remove these root kits. My suggestion is wiping the entirety of your emmc, and rewriting it with a jtag device from a known clean copy.

When I need to exploit something, if I can't find an open source exploit that works I sit down and write my own. I suggest you do that. Finding vulnerabilities and writing exploits is a very fun activity, it works best after one bottle of wine. Even if open source, it is quite easy to hide malicious activity in the source code, especially if the person reviewing it is unaccustomed to such behavior. More so, most people would run the precompiled version anyways, source code may not match.

Another option would be to reverse engineer WeakSauce and Firewater and reimplement the exploits. WeakSauce should be fairly easy, I didn't put much effort into obfuscating it, just enough to deter the inexperienced developer from reversing it. Firewater will probably take a fair bit of experience, and a good bit of time to understand it.

You are unable to write your CID because the partition is write protected.

Enough fun, lets get to the reasoning

Now, why are these closed source and obfuscated?

Because the scum that repacks them into tool kits and then goes "donate to me here" or the super scum like http://www.gsmcocktail.com/ that steals our work, packages it into a commercial dongle and sells it for $80 a pop. I will detail how WeakSauce works at some near point in the future, I probably won't release source like I normally do with exploits, because of people complaining about not having source.

Why does WeakSauce and Firewater require internet permission

WeakSauce requires the internet permission as part of the exploit, on new devices it is impossible to exploit the vulnerability without it.

Firewater requires internet for security and management, beaups uses this to deter/prevent the reselling of binaries or offering "rooting services" using the binary. He can also prevent bad copies or leaked test builds from running. Lets say he releases a build that has a bug that can brick the occasional phone, well he can deauthorize that version and prevent more people from bricking. Safety first yo!

The theft of exploits has sadly become a common occurrence, and it really sucks to put time and passion into developing it to see someone completely unassociated with the project take your work, and hustle money from people using. I am talking about those that pack these exploits into one click root tools, tool boxes, "flash" box and dongles. Those people just suck.
[AT&T, Rogers HTC One X, Telstra One XL] jcase:
Yes, those blocks are write protected. You need to find a way to remove such write protection.
[AT&T, Rogers HTC One X, Telstra One XL] gigel_georgel:
timmaaa - so what I"m getting is that you might be be able to write into the recovery partition without actually having the bootloader unlocked, just root would be sufficient? Is the code that verifies the htc digital signature and system partition write permission located in the recovery, so once that's replaced you're free to flash a ROM?

How about turning S-OFF, that would still be not achievable even with a custom ROM (while the bootloader stays locked), so flashing a jellybean RUU back wouldn't work?

Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] jcase:
I'm not timmaaa (you may want to quote/reply so people get notification) but...

If not unlocked or s-off you won't be able to write recovery. Even if you managed to write it, you wouldn't be able to boot the recovery due to the signature verification.

pbl (i think) verifies sbl1, sbl1 verifies sbl2, sbl2 verifies sbl3, sbl3 verifies hboot, hboot verifies kernel and recovery (i could be wrong here, but the last one is right for sure and it is all that matters for you).
[AT&T, Rogers HTC One X, Telstra One XL] Madcat8686:
Jcase, whatever your motivation and desire to develop and modify Android, I'd like to offer you a solid thank you. It's folks like you that make a phone or tablet that's pretty good into so much more and beyond what it was designed for. And I suppose freedom from what carriers think we should settle for goes in there too. I couldn't imagine what the OS would look like today without the innovation, creativity, and pushing the limits that individuals like you do.