yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cupfulloflol:
There is no best. Each one has it's fans. Just make sure the kernel fits the ROM you are planning on running, and that it covers your needs and wants.

Not trying to sound like a prick, but all of that should be very well documented at this point. By this I mean, don't be lazy and use search. Some of that is probably in the stickies above this post. Kernels, AOSP, odex vs deodex are all covered super well at this point. If you can't find information on it, you are doing it wrong.

Those are probably covered as well, but perhaps not as well as the others. Decompiling and recompiling there are tools out there, probably found in theming sections. I am unsure of what options are the best, apktool was what I used a year or so ago. Generally I don't ever have a need to decompile or recompile things.

smali
[Galaxy S 4 Q&A, Help & Troubleshooting] velein:
Hey guys!

When i boot my phone i get this error:

"firmware upgrade encountered an issue. please select recovery mode in kies and try again"

I can't flash access recovery or Android OS, and i can't flash from Odin (No PIT-partition error)

What to do???

I am almost panicking - my phone didn't work earlier today because of CWM, so i tried to flash TWRP from Odin, and now I am screwed again!!

It this fixable?

Please help me

Thanks in advance
[Galaxy S 4 Q&A, Help & Troubleshooting] Lennyz1988:
First thing you need to do is stop panicing. That will only make things worse. If you start messing with your phone, then prepare yourself that these things happen.

Also, there is little usefull information in your thread. If you want help, I suggest you make more work of you topic. What rom were you on? What did you do with CWM? What version where you on? What version of TWRP?

Can't you just flash CWM again and then flash a custom rom? If not, then try:

1. Do you have knox enabled bootloader?

2. If so, then flash any stock rom with a knox bootloader.

3. If not, then flash a stock rom without a knox bootloader.

4. Root again and flash recovery again.

5. Flash custom rom.
[Galaxy S 4 Q&A, Help & Troubleshooting] Misterjunky:
re: odin flash

Be sure you have or get the official stock odin flash rom for your phone baseband/model

number from SamMobile.com. They only have official stock roms their with exact model

and basebands.

Make sure the battery is at least 50% charged.

Open odin and set it up so it's ready to flash.

Then remove the battery for 10 seconds & replace the battery then then hold/press the vol-down

and the power button at the same time until the phone is in download mode.

Connect the usb cable from computer to phone and then:

Be sure ODIN is ready to start, if it is then start the odin flash.

Have patience, after the flash it can take up to 4-5 minutes for

the phone to go thru the initial boot.

REMEMBER, only flash official and specific odin flash rom which is designed for

your phone's baseband and model number. Double check before flashing to be sure.

Also to avoid problems in the future, once you get your phone working properly

uninstall kies on your phone and in your computer.

Kies is really not required unless you plan to stay STOCK/UN-ROOTED and don't

plan to flash any custom roms, mod's, themes.

Good luck!
[Galaxy S 4 Q&A, Help & Troubleshooting] velein:
Solved it by using this guide:

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

had to change to USB3.0-port before i could flash without getting an error.

Thanks for the help guys. :)
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] Celtic67:
Is it possible to change the partition table on the S5830i? I've done it on other phones to move data away from system and into data, then used a cut down rom with less bloatware. I've had a search, but nothing seemed clear, though there was talk of pit files and Odin.
[G2 Q&A, Help & Troubleshooting] skimilk44:
Hey everyone,

I have the most up to date Google Hangouts (1.2.018) at least it says so by reconciling b/w phone and play store online.

But I can't seem to find the SMS/MMS setting feature? I'm running stock, and i've gone through every option in the settings menu.

Any ideas? I guess I can root, get titanium and delete and reinstall? Or am I just missing something.

EDIT - I'm on TMO
[G2 Q&A, Help & Troubleshooting] craigbailey1986:
You have to get the hangout apk. That comes with android 4.4. Install as regular app and your good to go.
[G2 Q&A, Help & Troubleshooting] Steamer86:
I used it, needs more attachment options. When so, it will be my default if it's still as fast.
[G2 Q&A, Help & Troubleshooting] jellybear456:
Just head here to get the .apk with full SMS/MMS functionality. Working on my D800 Beautifully:victory:
[G2 Q&A, Help & Troubleshooting] skimilk44:
I figured as much. Articles kept saying 2.0+

Looking forward to the Kit Kat update (crossing fingers the rumors are true), but until then the apk will have to do. Thanks everyone!
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
I decided to write this, even though it was already written by SO many people already, to have it in an easily accessible spot

YOU MUST ALSO BE SUPERCID!!

YOU MUST BE S-OFF!!!!!!!

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

So here we go!

2.15 Firmware: http://www.androidfilehost.com/?fid=23060877490004040

2.18 Firmware: https://www.androidfilehost.com/?fid=23329332407572084

Download the firmware zip. Put it in a folder where you have the fastboot sdk tool

Plug your phone in with USB Debugging

Reboot into bootloader:

Open a command window in the folder with fastboot sdk

Once the phone gets to bootloader, go into fastboot

Check if fastboot commands are working:

Now the fun starts:

if it shows FAILED (remote: 90 hboot pre-update! please flush image again immediately)":

If it ends with "INFO..... OK", reboot to the bootloader:

Verify everything was successful by running:

This is what you're supposed to see:

Reboot into Android:

Reboot into Recovery:

Thanks to Turge and everyone else who helped with this firmware and Sense 5

Thanks [MENTION=4812700]24ky[/MENTION] for 2.18 firmware zip

CLICK THANKS IF I HELPED!!!!!!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I might be wrong, but this probably belongs in the General section as it isn't your own development.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] orangekid:
Moved to General.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Yeah sorry guys. Was in a rush to create this between classes and wasn't paying attention to the section.
[AT&T, Rogers HTC One X, Telstra One XL] Madcat8686:
Worked fine

I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
can you do update to firmware 2.15 with S-ON and no SuperCID (it's still Roger001)?

cause I'm getting lost connection and random reboots with Viper XL 4.2.0

I tried Beastmode kernel but WiFi stopped working..
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
believe me I want to!

but I'm not sure how to do it yet.

(chicken-egg situation, lol)

I've read conflicting things, like you have to have SuperCID first before you S-off..

but then I read that you need to S-off first

which one is it?
[AT&T, Rogers HTC One X, Telstra One XL] 954wrecker:
If you can't read and understand the instructions in the S-OFF thread you are not ready

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Get s-off before they patch it in the next update. Besides, you can fully customize your systems with kernels easily

Did I mention no fastboot commands?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
no offence!

I'm not accusing anyone of anything! lol

and I'm obviously not an Android guru..

As you can see from my number of posts, I'm not a regular here!

so I wasn't following the progress of things..

and I'm not familiar with the specific thread you guys mention.

I was mostly using Google,

and trying to find someone with a Rogers version, to see how they did it.

And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.

You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Madcat8686:
You are definitely on the right site but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
Yeah I can see this site is a wealth of information.

A lot of brilliant people here!

thanks a million!

you sir are a true gentleman.

I followed the SuperCID instructions and everything seemed to work perfectly.

Now when I type: fastboot oem readcid in fastboot I get: (bootloader) cid: 11111111

which is great, but I also have an app called CID Getter (with a cupcake icon), and that app is telling me that my CID is [ROGER001].

Before I go any further, I need your help!

what does it mean?

I rebooted in fastboot again and fastboot oem readcid command still gives me 11111111
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
CID Getter doesn't display the correct CID, I'm not sure where it pulls it from but it's incorrect. The 11111111 you get from the fastboot command is your true CID so you can go ahead and proceed with s-off.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Hailfire:
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.

This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.

Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
AOSP-wise, I'm pretty sure CFX is 2.15 compatible
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
4.3 just wasn't a good run for aosp
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
For some ROMs it's been a bit bumpy. I had zero issues on Slimbean though, and CFX is looking the same way. A good portion of the bugs we've seen have been kernel related anyway.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Yeah, CM10.2 was updated to be compatible with hboot 2.15 a while ago. So I agree with timmaaa, that unless you are flashing an old version of CM10.2, hboot 2.15 is not the issue.

If the hboot is not compatible, it will fail to flash. Successful flash, then bootloop is something else.

---------- Post added at 01:30 PM ---------- Previous post was at 01:21 PM ----------

Relax buddy, there is nothing in timmaaa's response that implies you were accusing anyone of anything, or insulting your knowledge. He was simply pointing out your statement was incorrect.

If you are new here, I recommend you bookmark my Index thread and refer to it often: http://xdaforums.com/showthread.php?t=1671237

I think you are misinterpreting the meaning of the phrase "SuperCID for S-off" (or similar phrases). It isn't meaning to say what you assumed, but rather: "Obtain SuperCID which is required for the s-off method".
[AT&T, Rogers HTC One X, Telstra One XL] cessna784:
I followed the instructions and I get

FAILED (remote: 99 unknown fail)

Current Rom Installed: CleanRom 7 p1.zip

Device: ATT HTC One X white

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.14.0002

(bootloader) version-baseband: 0.19as.32.09.11_2

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.20.502.7

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT29CW303478

(bootloader) imei: 359691047295780

(bootloader) product: evita

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ8310000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3847mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: RUU

(bootloader) commitno-bootloader: 1a7fdca3

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You're s-on, s-off is required to flash this.

[MENTION=5357811]pandasa123[/MENTION], you might want to mention the s-off requirement the OP.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Yes, this is absolutely critical, and should be added to the OP.
[AT&T, Rogers HTC One X, Telstra One XL] cessna784:
You guys were totally right after turning s-off and running the command twice as stated I was able to reflash.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
ok just added to OP S-OFF is 100% required

for those of you haven't, I strongly recommend you do so:

http://xdaforums.com/showthread.php?t=2155071
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
ok I'm getting the same:

FAILED (remote: 99 unknown fail)

error message while I'm trying to S-OFF

instead of

“FAILED (remote: 92 supercid! please flush image again immediately)”

I read somewhere that I need to Wipe Cache / Dalvik.. bu that didn't help.

any suggestions?!

joes:android joe$ fastboot flash zip PJ8312000-OneX.zip

sending 'zip' (36064 KB)...

OKAY [ 2.651s]

writing 'zip'...

(bootloader) adopting the signature contained in this image...

(bootloader) zip header checking...

(bootloader) zip info parsing...

FAILED (remote: 99 unknown fail)

finished. total time: 2.902s

joes:android joe$ fastboot flash zip PJ8312000-OneX.zip

sending 'zip' (36064 KB)...

OKAY [ 2.652s]​
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Next time please search before posting. I've answered this question numerous times in the s-off thread, I'm willing to bet the answer is in the last three pages.

[EDIT] It's on the fourth last page, that shouldn't have been too hard to find, it took me less than thirty seconds.

When you get error 99 force a reboot to the bootloader and start again.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
It was mentioned in the instructions, you know?
[AT&T, Rogers HTC One X, Telstra One XL] clockwars:
I haven't got to firmware flashing yet! I was following the instructions in the thread Timaa gave me.

I actually searched xda-developers for "FAILED (remote: 99 unknown fail)" but I couldn't find anything that would help.

I finally decided to boot into Recovery, and from there reboot into Bootloader (as opposed to using adb reboot bootloader)

It worked on first try.

I have no idea why (and what's the difference between this and using the adb reboot bootloader command),

but I hope it helps someone out there.
[AT&T, Rogers HTC One X, Telstra One XL] bremair:
When I do it like the instruction on post 1 I get the following error:

FAILED (remote: 41 model id check fail)

I'm S-OFF (rumrunner-mode)

CID: T-MOB101

HBOOT: 2.14.0000
[AT&T, Rogers HTC One X, Telstra One XL] Menicing:
change your superCID to 11111111

i did this method with good results - http://xdaforums.com/showthread.php?t=2212737
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's a very complicated way to get SuperCID for someone who's already s-off. When s-off you can change your CID as many times as you want with a simple command:

fastboot oem writecid 11111111

Sent from my Evita.

---------- Post added at 05:07 PM ---------- Previous post was at 05:04 PM ----------

You need SuperCID for this to work, you can get SuperCID by issuing just one fastboot command.

fastboot oem writecid 11111111

[MENTION=5357811]pandasa123[/MENTION] You might want to include SuperCID as a requirement in your OP please.

Sent from my Evita.
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
On one of the other threads I read about new 2.17 firmware - does anybody know if it can be flashed using this method ? I dont have windows and cannot run a full RUU
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Is the 2.17 firmware even available? Why do you want it?

Sent from my Evita.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
hboot 2.18 was released with the Orange 5.14.

hboot 2.17 was released with the HTC Hong Kong 5.08.

The Orange 5.14 firmware is the latest. Has newest hboot and radio. Also has the newer tz and sbl2 that also shipped with Telstras 5.08.

I have not heard of anyone flashing this firmware.zip to their phone yet. It can be obtained from the ota zip and should be possible to flash via rebootRUU.

Untested on modded phones, who knows if it will brick your phone or not.

Normally the rule for untested things is, if you have to ask you probably should not be trying to flash it.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I second that. If it hasn't been done yet, don't do it, unless you intend to be the guinea pig.

It should also be noted that the firmware in the OP of this thread is not stock, it was modded by Turge to include all three hboot modules. Flashing the firmware.zip as included in the OTA only had one module, which resulted in hard bricks for those that were on Pre-Jellybean hboot and tried to flash it.

Just one example why not to mess with the newer hboots unless you know what you are doing. And aside from the new radio, there is probably little if any difference, and therefore no reason to mess with them, anyway.
[AT&T, Rogers HTC One X, Telstra One XL] cTech12:
Can anyone give a definitive answer to what changes/improvements exist between 2.14 and 2.15?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The 2.15 firmware package updates your hboot, radio, WiFi modules, and media modules. The main benefit is being able to flash Sense 5 ROMs without suffering signal drops or random reboots.

Sent from my Evita.
[AT&T, Rogers HTC One X, Telstra One XL] cTech12:
But if I'm not using Sense, there is absolutely no benefit?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Not really, no.

Sent from my Evita.
[AT&T, Rogers HTC One X, Telstra One XL] cTech12:
Well then I guess I'll leave it be.

Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] brandontrout:
Just to double check, if I'm running CM11, with s-off and CID 111111, I can install this right? I read that it should help with my radio drops.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Yes, S-off and SuperCID means you can run this. But unless you have specifically read that this helps with CM11, I don't think this will help at all on AOSP ROMs. This helps with Sense 5 ROMs because of the sleep/power save function exclusive to Sense 5 is not compatible with older radios, causing signal drops and random reboots.
[AT&T, Rogers HTC One X, Telstra One XL] HeavyMetalHighVoltage:
Does the firmware package in the op wipe data? I also see no warning to relock bootloader so I'm assuming that isn't needed. My wife's AT&T htc one x is now running on straight talk and has active LTE connection but it signal drops and reboots quite often. I've installed ViperXL 4.2.0 with elementalX kernel as well. The device is also s-off and superCID. Excellent job on this guide by the way! If I wasn't already familiar with firmware flashing (done multiple times on my HTC One) I'd have no problem flashing firmware for the first time. Very well written, Thank you!
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
[MENTION=5004039]HeavyMetalHighVoltage[/MENTION] no wiping. Just keep a backup stored on your computer just in case. And thanks man
[AT&T, Rogers HTC One X, Telstra One XL] HeavyMetalHighVoltage:
Finally got to try flashing the firmware just now but it says writing firmware failed remote: not allowed. The device is s-off and superCID and matching modelid. I double checked android info.file text and all matches. So I'm not sure what I can do to get it flashed. Any help or ideas would be appreciated.

Edit: I had to type fastboot flash zip firmware.zip instead of fastboot flash firmware firmware.zip

All is updated and running smooth.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's why reading directions is important :p

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ejonathanz:
if i update my hboot 2.14 to this 2.15 my device will not have anymore random reboots? Cuz i'm running cleanrom 7.0 in my HOX att and the random reboots are a headaches :/ ..
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yes, updating your firmware should stop the random reboots.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ejonathanz:
sup bro, it's me again, hope u're fine, has a last question for you, if something goes wrong with my device while I'm doing this process I can reverse the process by restoring my last backup?

greetings.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
No. That's only for system. You could just follow the same process for other firmware packages
[AT&T, Rogers HTC One X, Telstra One XL] ejonathanz:
to flash this firmware i've to relock my bootloader? In this case, at what point should I run the "fastboot oem lock" command? in the beginning?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Absolutely not. It doesn't say anything about locking the bootloader anywhere in the instructions. You must follow the instructions precisely.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ejonathanz:
wow man, this worked really good, thank you for all and sorry for the troubles, greetings.
[AT&T, Rogers HTC One X, Telstra One XL] chrisb906:
This is the thread I was talking about.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That thread doesn't say anything about flashing just the hboot, that thread details how to update your firmware, it states that very clearly in both the title and the instructions. Why are you posting this here instead of your hboot thread?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] chrisb906:
Yea. I did follow the instructions precisely
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well then why are you saying you flashed only the hboot?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] chrisb906:
I corrected myself. I said I ran 3.18 ruu then flashed 2.15 hboot.

---------- Post added at 06:34 AM ---------- Previous post was at 06:33 AM ----------

I posted here cuz I couldn't copy and paste the URL. Sorry
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yeah, which is wrong. If you followed these instructions you didn't just flash the hboot, you flashed the firmware. We're off topic for this thread now.

Sent from my Evita