yashsingh1/xdaforums huggingface dataset:
[HTC One X] treebill:
Beats is for headset only.

Sound like you need to clean the speak out, I would suggest opening it and cleaning from inside out but you can do it from the outside if you rather.

A tooth brush as the best way to go about it
[HTC One X] monkoid:
Well I thought about the speaker, but it's unlikely. I'll try anyway, just to get that out the way, but it was still going fine before the last update...

By the way, I just tried cm-10.1.3-endeavoru - I didn't have sound at all (neither did I have wifi or bluetooth... nevermind though, that's not my current problem)

I'm back to Revolution HD now... made sure pureXaudio was installed again - still no change.

Before switching ROMs I used ROM-Cleaner and wiped all data, cache, dalvik cache...
[HTC One X] treebill:
Did you wipe cache in fastboot?

Fastboot erase cache
[HTC One X] monkoid:
I wiped with CWM recovery every time... do you think wiping through fastboot would change anything regarding sound ?

Now I'm looking into flashing it with an earlier stock rom nandroid backup (from a thread found here in the forum) - but the one I tried earlier didn't take. I downloaded another (even slightly older) version which I still need to try out.

I also apologize regarding the earlier "AudioX" suggestion : there is indeed an AudioX mod available, one of which every one seems to be happy - unfortunately, it doesn't seem to have any effect on mine :(

I'm starting to wonder if installing those mods really has any effect. I'm using CWM - which I'm told is OK for all those mods (installations do succeed), but I also noticed most people are using TFWP(?) - so I'll start looking into switching from CWM to TFWP if the earlier stock roms don't help.
[HTC One X] samyaditya:
did you figure it out?

I'm having the same problem. AudioX or any other mod doesn't seem to work. Did you sort it out?
[Sony Xperia S, Acro S, Ion] ronin1728:
Guys I need some help.

I am trying to deodex my friend's Acro S using this tool here: http://xdaforums.com/showthread.php?t=2176241

I can make the sytem dump but can't deodex it. I followed the instruction on how to get the bootclasspath and I am sure of the bootclasspath I am inputing but gives me an error saying "The system cannot find the specified path." After pasting the bootclasspath and pressing enter, the tool just returns to the start asking what I want to do. Anyway can someone post their bootclasspath here for verification.

Did anyone here tried using this tool?

My friend's Acro S in on stock .96 rom, rooted, and unlocked bootloader.

Any help will be greatly appreciated.
[Sony Xperia S, Acro S, Ion] abcdjdj:
The bootclasspath files generally are the files in /system/framework. So you need the files present in /system/framework.

Or you can use my tool over here - http://xdaforums.com/showthread.php?t=2213235

I am sure that it will work for Acro S.
[Sony Xperia S, Acro S, Ion] ronin1728:
Oh thank goodness you are here. Yes I saw your tool too. And I have some questions about what to do (^^)d

1st: The apks that need deodexing are inside the /system/app, everything inside???

2nd: What about the jar files, where are they located? I am unsure where I can find these.

3rd: After I successfully deodex the apk & jar files, do I need to manually zipaligned them?

4th: And can I just copy/paste the deodexed files in /system?

Thank you in advance. (^-^)v
[Sony Xperia S, Acro S, Ion] abcdjdj:
1. Yes, the apks in /system/app need to be deodexed, but some of them are already deodexed. Simply pull all the apks from your phone and place them in the "apks" folder of my tool. The already deodexed apks will be automatically deleted:)

2. Jar files are located in /system/framework. You can use the pull from framework option in my tool. It will pull all the framework files.

3. Yes, you will have to manually zipalign all the apks. Sorry:(

4. It is better if you make a flashable zip, or try this - first keep the deodexed apks in /sdcard/done_app and the deodexed framework files in /sdcard/done_frame. I would still recommend you to make a flashable zip as it is the safest.

adb shell

su

stop

mount -o rw,remount /system/ /system/

cp /sdcard/done_app/* /system/app/

rm /system/app/*.odex

cp /sdcard/done_frame/* /system/framework/

rm /system/framework/*.odex

mount -o ro,remount /system/ /system/

reboot

Regards,

abcdjdj
[Android Q&A, Help & Troubleshooting] ter_101:
Hi all,

I am a noob to android and this forum.

I have a kogan 10" with stock rom on it and I noticed a few people asking for kogan stock roms.

Can I be of any help by posting my stock rom for the dev's to use etc?

I don't know how to do it yet so please could I have a bit of help?

Also I would like to customise my tablet too!

Cheers,

Terry.
[Android Q&A, Help & Troubleshooting] ter_101:
PS

P.S. can I update my android from 2.2.3?
[Android Q&A, Help & Troubleshooting] ter_101:
Now rooted perfectly

Hi,

I have successfully managed to root my device but can't get clockwork mod to work.

If it helps anyone I used Cydia Impactor to root my device, it took 30 seconds the downloaded SuperSU and installed it and device successfully rooted.

Please can someone help me with a rom that would work for me.

Cheers,

Terry.
[Android Q&A, Help & Troubleshooting] Shadowstriken:
Me too

I couldn't get clockwork to work on mine either, did you try this http://xdaforums.com/showthread.php?t=1119778

Worse for me is that my brother went and installed cm9 on it without making any back up = No touchscreen and no method of going back. So if that offer still stands of the stock ROM I will take you up on it.

*Just found cwm works using this http://xdaforums.com/showthread.php?p=36251400
[Samsung Galaxy S II Plus] shad0wboss:
I bought this phone recently and i have realized that it shuts down randomly when i try to use 3g a bit...Does anyone else have the same problem?
[Samsung Galaxy S II Plus] Brian_SGW_CM9:
Same question: do you have power saving turned on?
[Samsung Galaxy S II Plus] shad0wboss:
Can that be causing the random shut down?
[Samsung Galaxy S II Plus] Nekator:
He had that issue caused by power a saving so he ask always if it is on.
[Samsung Galaxy S II Plus] Brian_SGW_CM9:
yes to both
[Samsung Galaxy S II Plus] shad0wboss:
still the same...it just reboots when 3g is used.
[Samsung Galaxy S II Plus] Brian_SGW_CM9:
Flash another firmware, mate, that's the only thing you can do
[Samsung Galaxy S II Plus] shad0wboss:
Actually it's my sister's phone and she doesn't want to void the warranty. Do you think, sending it to the company would help in anyway? I know that the problem seems to be in the firmware..
[Samsung Galaxy S II Plus] Brian_SGW_CM9:
Flashing back to stock Rom actually brings you back your warranty =="
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Seeing as the thread in the development section is being flooded with questions when its meant to be a development research thread and important info is getting lost amongst all the questions, I thought Id create a Q&A thread for all Knox bootloader 0x1 related questions so that we can try and keep the development thread just for research and testing.

Please feel free to ask any question here and i'll do my best to answer it but hopefully some of the other members who know a bit more will also join in and help answer some of the questions people have.

What we know so far (I think!)

1. Upgrading to newer Samsung firmware will upgrade the bootloader to knox bootloader. this will give an additional 2 lines in download mode about knox status.

2. If the Knox warranty void line says 0x1 then you cannot use knox softwareas your device has been flagged as insecure. By this i mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use knox to keep security your device will not allow this. You are still able to use future samsung firmware releases with the knox flag 0x1. hope this makes sense. sorry for any confusion this has caused!

3. If the knox warranty line says 0x0 knox will work.

4. with the new knox bootloader root will work, however rooting with CFautorootwill trip the knox flag. thanks [MENTION=4398524]DjeMBeY[/MENTION] for correcting this point :) you can use the root method (Root de la Vega) described here for rooting a device with knox bootloader.

5. If you try to downgrade to earlier firmware / bootloader it will set the knox flag to 0x1 i.e. void.

6. once the knox flag gets set to 0x1 there is no way to set it back (that anyone has found yet anyway!)

7. some newer 4.2.2 software that's supplied with the knox bootloader has been repacked by devs to not use the new bootloader and it all works fine you can still keep up to date.

8. I've seen people trying the test build of 4.3 touchwiz without the new knox bootloader sound and wifi does not work. This is no longer the case, see point 12.

9. There seems to be a big question mark as to weather Samsung will allow hardware repairs under warranty with the knox 0x1 flag

10. only seems to affect GT-i9505 at the moment!

11. Software affected thanks to [MENTION=4398524]DjeMBeY[/MENTION]

12. it is now possible to install custom 4.3 TW roms which have been modified to work without the new knox bootloader, do make sure that they are free from knox bootloader before flashing. Do note also that if you already have knox bootloader flashing anything even these 4.3 custom roms will still trip your 0x1 flag

What knox bootloader looks like in download mode . In this picture Knox warranty is in tact as the flag is 0x0:

I hope this answers some questions, anyone feel free to correct me and i'll try to keep this OP updated with info as people supply it / discover it.
[Galaxy S 4 Q&A, Help & Troubleshooting] kantjer:
Nice initiative mate.
[Galaxy S 4 Q&A, Help & Troubleshooting] lolo9393:
good idea,

This thread Must be splitted because of several models that can be concerned in different aspect. ( I9505 or 9500 and others)

this would avoid misunderstanding or wrong rules to be spread over.

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] r.spanish:
Its quite obvious that Samsung are not only trying to control the software we use on our device but also how we obtain it.

I dont see many posts about binary counter recently, because now theres a bigger wall that has been put up.

So you cant even check to see if there has been custom software on your device, because doing so would require root which will trigger the knox crap, permanently.

Its that permanently which i have a problem with, and one i believe Samsung will use to reject a warranty claim in future based on that.

They want OTA and Kies naturally. I mean going back to an older official release bootloader via odin break knox? What the hell Samsung.

The saying you cant have your cake and eat it too applies here. I do read some people of the opinion that its my device and i can do anything i want with it, and Samsung you must now fix it when it breaks.

Anything, really? No, and this is the problem, because running custom software gives you the ability to do this. Not because you did, but because you could have and they probably dont have the resources to prove it with every single warranty claim.

So where does that leave the rest of us? In the same boat because they now have a way to prove you did something naughty, theyre not quite sure what it is except knox warranty void 0x1 (maybe).
[Galaxy S 4 Q&A, Help & Troubleshooting] ace_of_spades021:
hi...

I have mh8 btu firmware and Then I root it with CF-Auto root and my knox warranty is 0x1...

my question is: Can I install new official frimware that released from sammobile or samsung-update????
[Galaxy S 4 Q&A, Help & Troubleshooting] iamflamez:
I just got my new s4 20 mins ago, I've switched it on and it has 4.2.2 MH8 can i use a repacked 4.2.2?

If I cant get root the phone is useless to me as i need to run it in my car with the pioneer appradio arliberator software.
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

The new "Official" firmware is not yet available.

Please let us know if you can update.

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

BTW, if anyone is interested what the KNOX thing is all about,check THIS

:eek:
[Galaxy S 4 Q&A, Help & Troubleshooting] paras:
Does Knox make a person's phone non rootable

Sent from my GT-I9500
[Galaxy S 4 Q&A, Help & Troubleshooting] ace_of_spades021:
thx for reply...

but if I can't upgrade my phone I perefer to sell it as soon as possible!!!!

how can I know that? :crying:
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Pretty much yes it will mess with root so it only partly works and voids the warranty at the same time!
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
Yes I'm afraid there is no way to know at the moment. Only info we have is that people have been able to install the leaked 4.3 build with 0x1 flag already present but it's not finished build so who knows what Samsung will do to it
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
I loose track of letters and builds. If you turn it off and turn it on holding vol up and go into download mode does the small text at the top mention Knox?
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Great idea mate - Subscribed:good:
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
What's the FIRST ROM that contained the dreaded Knox bootloader?

I used: I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.tar to flash via Odin, before I knew anything about Knox, and I do not have a Knox flag in Download mode. I have not gone beyond this ROM, as I normally use CyanogenMod.

I have never been able to get a direct answer on this. I am pretty sure (if memory serves) that I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.tar contains Knox software in the ROM, but the Knox flag does not show up in the Download mode screen. Mine looks like this:

ODIN MODE

PRODUCT NAME: GT-I9505

CURRENT BINARY: CUSTOM

SYSTEM STATUS: CUSTOM

CSB-CONFIG-LSB: 0X30

WRITE PROTECTION: Enable

Does it have a Knox bootloader or does it not? :confused:
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Not entirely sure but if it had the Knox bootloader I believe it would say Knox/Knox warrenty somewhere in the list and would be at 0x0 or 0x1:confused::confused: My CSB-CONFIG-LSB is also 0x30 and I am pretty sure I do not have Knox.......
[Galaxy S 4 Q&A, Help & Troubleshooting] kapiszon53:
PhoeniX ROM - question

Hi, i am on MGA now and i want to install PhoeniX ROM.

This is knox free so after install can i back for example to MGA ?

Sorry for my bad english and thx ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
If your current ROM IS knox free and the ROM you are going to is Knox free then yes you should be able to go back without any issues!
[Galaxy S 4 Q&A, Help & Troubleshooting] Ritchiejoe:
It looks like the insurance I took out will come in handy when I accidentally drop my s4 in the bath.......
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

Knox looks like this:

You do not have it

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
That's not what anyone is saying. If you spend some time actually reading to find out what Knox actually is and how it fits into Samdung's future plans, you'll understand that:

1. The eFuse cannot be reset. Period.

2. You can remove the Knox software, but...

3. If you have a Knox bootloader and care about your warranty, that party's over, because....

4. Any root/custom recovery/custom kernel will trigger it and void your warranty.

5. Further, it even appears at this point that you won't be able to move forward into later ROMs (4.3+) and retain the old 4.2.2 bootloader, because doing so kills sound and wifi functionality, and that's probably by design.

Samdung development will continue, and they'll still sell millions of locked-down laggy Touchwiz burdened devices, but a lot of buyers (myself included) will move to other more developer friendly options ASAP.
[Galaxy S 4 Q&A, Help & Troubleshooting] chavdar:
The knox flag is really a blow under the belt, if it so happens, that there is a hardware fault not due to modding.

We all know, that with custom kernel it is quite easy to fry you cpu\gpu if you don't know what you are doing or not caring.

Samsung has done what others has already long done, but in a way, that still allows modifications for the cost of guarantee. It is a simple matter of choice. Just wait and see when Google walks this way

Sent from the N7100 Galaxy
[Galaxy S 4 Q&A, Help & Troubleshooting] vikash0513:
So i can instal omega v10 with knox 0x1 i am on 4.2.2
[Galaxy S 4 Q&A, Help & Troubleshooting] kingzain900:
Yes you can.
[Galaxy S 4 Q&A, Help & Troubleshooting] UltraPower31:
So, please give an example, I haven't heard from anyone who tried it.

BTW it has nothing to do with being dumb. The first people who flashed the new bootloader just didn't know it and if they haven't warned us you'd be one of those "dumb" people, too, so stop insulting other people!
[Galaxy S 4 Q&A, Help & Troubleshooting] mankvl:
Maybe Samsung will understand that this is a stupid idea and unlock the bootloader, Knox could be good if it would be not so deep integrated into the phone, now it's more pain in the ass than usefull. If Samsung go this way where you are stuck with stock phone if you want to keep your warranty I'm never going to buy anything from them. Why just we can't buy a phone with root :D
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
I can't help what you've heard. There are multiple reports of such failures. If you use the Search feature, you may find them.

Why would I fabricate such information? Fame? Money? Power?

In no way is it an insult to say that it's sorta' dumb to flash a leaked Samsung ROM, particularly given the track record of the company when it comes to bootloaders, etc. It's just a dumb thing to do, and everyone knows there are real risks involved with such things, and those who did it are paying the price for it, and for that matter, if you recall, I also said that I was dumb enough to buy the S4, which will be my last Samdung purchase.

I would not have been one of them, because I don't flash leaks, and I very rarely use Stock Firmware for the simple fact that I don't trust Samdung.

I'm not saying that it was dumb for anyone to update to Stock firmware that included the Knox bootloader, because there's no way anyone could have known what it would do, so don't misrepresent my comments, or take them personally.

That's not what this is all about.

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

If you read the above carefully, you'll see a thread titled "solved!" with reference to Knox, but it's false and miseading in every way. Nobody has ever been able to downgrade the bootloader and reset Knox eFuse.

Period.

Don't believe the experience of others if you don't want to. Give it a try and report back. I'd love to be wrong about this, as I'm sure all the others would, but I don't think that's the case.

---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------

Samdung will never relent on this issue. They do not care and they never will. It's a false hope to even dream that they will ever get rid of Knox for anyone.

They've already made their decisions and spent the resources to develop Knox, and they aren't going to scrap the whole thing just because a bunch of phone zealots like us raise a stink about it, even on the biggest device forum in the world.

It just does not matter. The only thing any of us can do is learn from our (repeated) mistake of trusting Samdung and never buy any of their crap again.

That's my plan. Petitions, letters, calls, etc. will all be ignored. We've been down this road before, and it's an absolute dismal dead end.
[Galaxy S 4 Q&A, Help & Troubleshooting] mankvl:
It's a little bit stupid, when I bought s4 I knew that bootloader is not locked on my S4 version, and now they just release update with no info about it, maybe we could claim to get our $ back because of this?
[Galaxy S 4 Q&A, Help & Troubleshooting] Hawke84:
u could try but it will likely need to go to court to try and get your money back and it will only be the retailer you got it from that you hurt, not samsung
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
No OTA??

Hi All,

I have done a quick search and not found anything related; apologies if it's been covered/mentioned:o

Can anyone confirm that OTA is no longer possible after tripping the KNOX flag? I only ask as I am currently using the leaked 4.3 and have tripped the KNOX flag....(this is not a problem to me as I will not and do not plan on using KNOX locker/container etc). I have previously rooted and just recently re-flashed 4.3 via ODIN and not re-rooted. I now get a message when I try to check for updates (aware that none will be available:p) that my device has been modified and updates are not available:confused: This has only become apparent on 4.3......previous returns to stock (prior the KNOX boot loader) I have been able to get OTA updates.

Anyone else? OR could someone enlighten me a little?
[Galaxy S 4 Q&A, Help & Troubleshooting] mankvl:
You should be able to go back to latest official 4.2.2 firmware and have the OTA updates again I think. Anyway u will be able to flash newest firmware via Odin
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
That's correct. You just won't be able to use the Knox container.
[Galaxy S 4 Q&A, Help & Troubleshooting] chickentuna:
I haven't flashed any knox enabled bootloader but I seriously think that claiming warranty when your KNOX Warranty flag is 0x1 will vary depending on the country.

Like say for example in my country the latest update was MG5 and as of this writing there are no updates available yet. Now the question is what if I update my device to a KNOX enabled firmware and trigger the KNOX flag? Would they even know what the KNOX WARRANTY VOID 0x1 means? I know those Samsung tech guys are not that stupid but I could probably play stupid myself (like I did with my first visit to the Samsung service center when I've hard bricked my device lol) and say that my system status and binary all says "official" you'll never know, maybe they'll consider it.

Anyway I have no plans on flashing any unofficial leaks with knox enabled bootloaders just yet. Just posting my thoughts regarding this. I'm still waiting for the official 4.3 update.and for the kernel source to be released. Im hoping that the devs can do something with it and disable the KNOX warranty void trigger at the kernel level.
[Galaxy S 4 Q&A, Help & Troubleshooting] donalgodon:
The reality is that the Knox issue isn't something as simple as a kernel flag. It's also in the bootloader itself, and that's very complex to deal with. Much more so than a kernel. It's a lot lower level. I agree also that it's quite likely, as you say, some service centers might not know about the Knox flag initially, but it won't take long for Samdung to update them via service bulletin and end close that loophole. They aren't stupid, and even if some of the service centers are a bit out of the loop, it won't last.
[Galaxy S 4 Q&A, Help & Troubleshooting] tariqso:
If I flashed the pre rooted rom my knox will be increased to 0×1?
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
Have you read here? [MENTION=4398524]DjeMBeY[/MENTION] - http://xdaforums.com/showthread.php?t=2250824

But most likely yes!
[Galaxy S 4 Q&A, Help & Troubleshooting] tariqso:
I don't have time to read all but he tells only about the binary

Binary number I think we can rest it but don't know about the knox

I need my warrant and I want to root it so if there is any way to root and keep knox 0×0 it will be better

Thank u
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
EXAMPLE

Model: GT-I9505 (4.3)

PDA: JSS15J.XXUEMI8

PHONE: XXUEMI8

CSC: OXAEMI8 (8 codes)

Kernel: 3.4.0-1715731 (20.09)

Bootloader FREE!!

FULL WIPE ROM!! BACK UP YOUR DATA!!

Leaked/TEST FW

Device Status - CUSTOM

KNOX WARRANTY VOID 0x1

It is explained quite clearly regarding KNOX:confused:

Don't be lazy:silly:
[Galaxy S 4 Q&A, Help & Troubleshooting] tariqso:
What about to make it 0×0 there is no way??
[Galaxy S 4 Q&A, Help & Troubleshooting] CarlM34:
You really have not read much have you.....??? Once you have triggered KNOX as VOID 0x1 It is (at the moment and for the forseable future) irriversable!!!!!!!!