yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] hp79:
Going bestbuy in your current state won't work. They are only able to do a update or emergency recovery to NC2, so you will still be stuck with non-working SuperSU still under /system/app even after reflashing. Unfortunately they don't have full factory reset image for 4.4.2 NC2 yet as of 5/17/2014.

What I did to remove that is to flash leaked Kitkat MLG with NC2 bootloader (look for the thread posted by Carl) using Odin, and this will wipe everything out. Then go to Bestbuy Samsung and update to NC2. This is the only way to remove SuperSU or any junk left behind.

As a precaution I did factory reset after I got mine updated to NC2 and after installing some stuff my PlayStore dissappeared so I had to do a factory reset another time. Now I think everything is pure stock.

And you don't have to make up any excuses about why you want it reflashed. Just tell them you had it rooted and now because att MFs locked down everything so bad you couldn't even get rid of it without flashing with leaked Kitkat. Samsung guys are there to help you.

I'm never going to buy another At&t crap again.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] xfaega:
I'm going to have to disagree with you since I was in the same boat as the OP. I went to Best Buy Samsung and they did the update from Samsung site and it wiped out all traces of root files and supersu. They first had to download the update from Samsung site and then they connected my note 3 on nc2 with superus still there. Once they finished I checked my disabled apps and superus was no longer listed. I did a complete factory restore to verify it worked and superus was nowhere to be found. Not sure what is different from AT&T update and Samsung but Samsung version completely wipes out root.
[One (M7) Q&A, Help & Troubleshooting] ronanzz:
I'm using TWRP for a factory reset , but I hit the wrong press the Format Data , and now can not do anything with it . Help me I'm going to do next . In order to give the computer back to normal. My machine is detailed

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000.

(bootloader) version-baseband: 4A.21.3263.04.

(bootloader) version-cpld: None.

(bootloader) version-microp: None.

(bootloader) version-main: 3.63.61.1.

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

(bootloader) serialno: FA395WXXXXX

(bootloader) imei: 35XXXXXXXXXXXX

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064.

(bootloader) modelid: PN0710000

(bootloader) cidnum: ORANG001

(bootloader) battery-status: good.

(bootloader) battery-voltage: 3800mV.

(bootloader) partition-layout: Generic.

(bootloader) security: on

(bootloader) build-mode: SHIP.

(bootloader) boot-mode: FASTBOOT.

(bootloader) commitno-bootloader: dirty-b0a25cb2.

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

ADB sideload is Failed :crying::crying::crying:

but can use adb fastboot

help me please
[One (M7) Q&A, Help & Troubleshooting] svenell:
I am kinda trying to figure out the same issue, I will post a reply in here if I get it working. I think from what I have read you might need to relock your device and flash an appropriate RUU in fastboot usb using the apropriate adb commands. I am a newbie though and still learning the android architecture so I would wait for someone more qualified to respond. If I get my device back to a stable ROM I will update you on the steps I took!
[One (M7) Q&A, Help & Troubleshooting] BenPope:
adb push?
[One (M7) Q&A, Help & Troubleshooting] nateboi81:
Yep like he said. In recovery adb push ROM.zip /sdcard/
[One (M7) Q&A, Help & Troubleshooting] ronanzz:
thank for help

I can relock it again, but I have no ruu for cid: ORANG001 trying to hard.:crying::crying:
[One (M7) Q&A, Help & Troubleshooting] ronanzz:
thank for help

Can you recommend a rom for my device that you can use nandroid or not.

I'm finding it difficult

Thank you
[One (M7) Q&A, Help & Troubleshooting] ronanzz:
tell me please
[One (M7) Q&A, Help & Troubleshooting] fenstre:
"adb sideload", while convenient, is less reliable than the old-fashioned method of pushing to /sdcard and using TWRP to install it. For this to work:

- TWRP must be installed (2.6.3.3 or newer).

- If not installed, make sure the bootloader is unlocked and install it with "fastboot flash recovery name-of-recovery.img", then clear cache just to be safe.

- Boot to TWRP through the bootloader using volume/power buttons (look for instructions online)

- Use "adb devices" to make sure ADB is working and detecting the phone

- Use "adb push rom.zip /sdcard/"

- If the push fails, make sure you are typing the correct path/filename to the ROM zip you want to install.

- If the push fails with an error about can't write or "no such file or directory", your data partition may be corrupted or not mounted (or maybe even out of space). You can solve this within TWRP. The most drastic (and most effective) solution is to format userdata, but you'll lose everything on the phone. There are other ways to solve this, but it's a case-by-case thing.

- If you try something to fix the "push" and want to try again, make sure /data and /sdcard are mounted (in the TWRP mounts section).

- After "push", you should check the md5sum of the file to make sure it hasn't been corrupted (check to see that it agrees with the md5sum on the download page). If there is no md5sum on the download page, ask in a forum.

- The command to check the md5sum for ALL zip files on /sdcard (because this is accident-proof) is:

adb shell "md5sum /sdcard/*.zip"

- Then you can "install" the normal way, using TWRP, without sideload.

Depending on which step fails, there are different things to try to fix the problem. If something fails, please provide ALL details of what you did, and all details about the error (write down the exact error message). If the error is in your TWRP usage, get the "recovery.log" file, which you can copy to the computer with

adb pull /tmp/recovery.log

---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------

Oh, and I forgot to mention, the ROM that most people seem to use (also the one that looks the most like the stock ROM) is Android Revolution HD. Note that there's a bug in the installer: if you don't have the newest firmware, you should choose "Wipe Data" when the Aroma Installer asks whether you want to wipe data. For some reason this is not the same as a factory reset in the TWRP menus.
[One (M7) Q&A, Help & Troubleshooting] Brycery91:
I'm having a similar issue but my internal sd won't mount when I start it, It says unable to moung /system, /cache and so forth. I'm running out of things to try.

---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------

I'm having a similar issue but my internal sd won't mount when I start it, It says unable to moung /system, /cache and so forth. I'm running out of things to try.
[One (M7) Q&A, Help & Troubleshooting] nateboi81:
You can use fastboot to wipe all those partitions. Fastboot erase system.....cache...etc. then format those ones in twrp
[LG G Flex] oaklanda123106:
I flashed [ROM]D95920h D-FUSE Stock rooted KK onto my lg-d950at. If anyone has a cwm or twrp backup of the stock at&t firmware ill greatly appreciate it so i can restore it back to the right rom. I have no signal and it says my service is disabled that is why i wish to revert back everything else seems to be working fine.
[LG G Flex] D-FUSE:
Ok man I'm gonna help u out

---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------

1st thing u need to do is downgrade to jb the d959 jellybean. Then root again and get freedom flex and install recovery. I just so happen to have a att jb tot I'm made a flashable rom for u

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

Another thing is it probably won't be uploaded til the morning
[LG G Flex] oaklanda123106:
Ok thank you so much ill do the downgrade now.
[LG G Flex] D-FUSE:
The flash tool is gonna think u r a D959 so use D959 well I'm hoping that is what did when I tried to port a att rom I had to use att tot file. That is why I have it to make u a rom

D95910c.kdz
[LG G Flex] D-FUSE:
Uploading now. 100% stock as so you'll have to root and do recovery again
[LG G Flex] joecash:
any chance you could post a link to that .zip, I think that this would help a lot of us dimwits that didn't listen to your original precautions and flashed our AT&T phones
[LG G Flex] lorawithano:
Any word on a link to that zip? I could use it too.
[LG G Flex] Alixbot:
Can you help a bro out? I need a restore file for the same t-mobile g flex you might have. Please see my issue on my thread.

http://xdaforums.com/general/xda-assist/please-help-lg-d959-twrp-format-error-t3091339
[JASJAR, XDA Exec, MDA Pro General] tonespeed1999:
has any one in the uk tried a sim card from the "THREE" network in an exec.

just curious to see if it works.
[JASJAR, XDA Exec, MDA Pro General] GaZ:
haven't tried it in an O2 branded one, but 3 have just released the Universal on their network apparently
[JASJAR, XDA Exec, MDA Pro General] adamelphick:
When i first got my Exec i was still with 3 (now i have left thank goodness!). I used my Exec with my 3 USIM with no problems at all mainly because i got it from an O2 shop and it was unlocked.

I hope this helps.

Adam
[One (M7) Q&A, Help & Troubleshooting] svenell:
After doing some research I decided I wanted to upgrade my stock odexed HTC Sense Rom (android 4.3) to the Android Revolution HD with Sense 5.5 (android 4.4 kitkat) which I found here:

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

Android Revolution HD 53.0.

The device had been previously unlocked however I still have S-ON. I updated my recovery from an older version of CWMR to the most recent version of TWRP via installing the TWRP zip within CWMR. After reboot TWRP was working fine and the current android 4.3 rom was functioning normally. I proceeded to place the new rom on my internal SD storage and began installing the rom via TWRP. I made a backup prior to this and backed up all of my personal information to the cloud. The installation seemed to go smoothly and I checked the additional utilities that I desired. When prompted between super user and superSU I chose super user (this was recommended) and everything seemed fine. After installation of the ARHD 53.0 rom I went to reboot and TWRP gave me a warning that I had no OS installed, I thought this might have been a fluke that just needed a reboot, then it prompted me to install supersu because I lacked it, which I thought was already installed during the ARHD 53.0 setup.

After some trouble shooting on my own I ended up clearing my backup and data to try and start fresh (probably rookie mistake). Right now I have the ability to get into bootloader, fastboot, and TWRP. I was able to adb push the ARHD 53.0 rom to my device but I get an error when trying to install the rom within TWRP. I am thinking I might need to do a RUU within fastboot in order to get my device to a stable state with an OS before I try to go on, but I am not totally sure what move to make next. I know that I probably need to relock my device and I am comfortable doing that within adb/fastboot but I am not sure where to go after that.

Here is my current getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4T.20.3218.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

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

(bootloader) serialno: ~~~~~~~~~

(bootloader) imei: ~~~~~~~~~~

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4248mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-2da61e5e88

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.044s
[One (M7) Q&A, Help & Troubleshooting] svenell:
Update... Since I have S-ON I am under the impression that flashing RUU via fastboot USB is NOT an option, however I have access to TWRP. I believe in clearing my data I got rid of the partition on my phone, so while I am able to adb push the ARHD 53.0 rom to my phone I cannot get it to install. After some reading I thought an adb sideload of the rom would be appropriate as it allots the RAM as a functioning partition. I am able to adb sideload the rom till around 55-60%, at which point my phone reports:

Starting ADB sideload feature...

(progress starts in cmd terminal)

~55% comes around

phone reports:

Installing ' /tmp/sideload.zip...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

E: Zip file is corrupt!

updating partition details...

E:Unable to mount '/data'/

E:Unable to mount internal storage.

MD5 Check on the Rom zip: http://imgur.com/N2OtHfC

Is my TWRP corrupt, or do I need a specific zip associated with adb sideload? I think if I can sideload a stable ROM I will be in the clear :)
[Verizon HTC One (M7)] rgps:
I have a bluetooth speaker in my kitchen connected to a power switch. My Wife and I each have a HTC One phone. I have configured a NFC tag to connect to the speaker so we can scan when we want to connect since the speaker only allows one connection.

This works great except for one issue. When we power off the speaker and then power it back on it connect to the last device automatically. I am not sure if that is the speaker or the phone reacting to the speaker's bluetooth connection. In either case the other person can now not make a connection since the previous phone is already connected.

Is it possible to prevent the phone from automatically connecting to the speaker when it is powered on ?
[Verizon HTC One (M7)] zeropally:
Yeah turn Bluetooth off for the time being on the phone you're not using
[Verizon HTC One (M7)] rgps:
I forgot to mention that I don't want to do that because I want the phone to auto connect to my headphones, car, etc. I just want to prevent the speaker from connecting.
[Verizon HTC One (M7)] zeropally:
The Bluetooth I'd is saved in any device you use. And most devices auto try the last id. So you're most likely stuck with it as its not the phone sending the connect signal its the device. Just toggle it for a sec let the other one connect then toggle it back
[Verizon HTC One (M7)] rgps:
Thanks, but I don't understand your suggestion. The other phone may not be near by. It may be in another room or even downstairs and yet it connects first if it was the last phone connected. I don't think I can toggle anything on the speaker so I would have to chase down the phone and either disconnect or disable bluetooth on that phone and then connect with the other. That is the exact issue I am trying to prevent.

I would think the phone has to be reacting to the speakers request to connect so perhaps there is an app that will deny such a request and only allow the connection to be established from the other direction (ie allow from phone to speaker but not allow speaker connection to phone) This would seem programmaticly possible, I just haven't found an app that does it yet.
[Galaxy S 4 Q&A, Help & Troubleshooting] dlsygaco:
Hi. My friend has this s4 with jb 4.3 in which she updated recently. And even before that in 4.2 we cant turn the wifi on or even tethering. We tried pulling batt out or wiping cache. Its still not working. Its not rooted and it came out of smart carrier here in the philippines.. Any ideas?

And how can i update to 4.4? It says canf update coz ifs modified o.o but updated to 4.3 via ota..
[Galaxy S 4 Q&A, Help & Troubleshooting] Chalao:
Wha's the result of punching *#1234# into the dialler?
[Galaxy S 4 Mini General] Aronuser:
Reserved
[Galaxy S 4 Mini General] tinko975:
my device turns knox to 0x1 in the beginning when i flash newer stock firmware with odin..

in Croatia (Europe) Warranty is void if your knox is 0x1.
[Galaxy S 4 Mini General] Aronuser:
Good to know, I'll add this to the OP :good: Thank you for contributing
[Galaxy S 4 Mini General] Aronuser:
Information updated, thanks to [MENTION=4378556]Gloris[/MENTION]
[Galaxy S 4 Mini General] Bullet92:
Can confirm that. Reflashed it via Odin yesterday and KNOX is still 0x0.
[Galaxy S 4 Mini General] afme89:
Many rooting methods will set the Knox flag 0x1 too.
[Galaxy S 4 Mini General] Aronuser:
Thank you both, I added the infos and credits to you.
[Galaxy S 4 Mini General] leripe:
I think there could also be a list of firmwares which have knox.

Example mine doesn't have one, l9195XXUAMF5.

Edit: Added link to this to few of my threads, also linked this to my signature, thanks!
[Galaxy S 4 Mini General] Aronuser:
First off, thank you for adding the link to your signature, i really appreciate it.

About the firmware list, well the idea is good but I don't have time for doing that. If you like to provide it I'd add it to the thread if you like (second post).
[Galaxy S 4 Mini General] rpgdev:
You can add that your phone will be functionally the same, I bought a 9195 (after owning the 9190) that had knox and went ahead and flashed something else (knowing that it could trip it, guarantee doesn't cover me anyways) and while it is tripped I can still flash anything, use all of my apps, etc. I had an s3 before and knox was tripped and I still could do everything I used to do.

The only really annoying thing about tripping knox is that on the first boot screen it will always show this little message announcing the "set warranty bit" which can be 'kernel' (if you're just normally booting the phone) or 'recovery' if you're booting into recovery. It shows up everytime you turn on your phone. It looks like this:
[Galaxy S 4 Mini General] Aronuser:
Thank you I'll add the info to the OP and give you credits :good:
[Galaxy S 4 Mini General] Aronuser:
I've a question about that, I heard the knox app's will stop working. is this true or false?
[Galaxy S 4 Mini General] rpgdev:
I know that sometimes on stock some persistent warning messages show up on the notification bar and to get rid of them you have to freeze some 'knox apps' or remove them from the system apps. I have yet to meet a useful 'knox app' but if there is let me know and next time I'm on stock I could try it out and report back.
[Galaxy S 4 Mini General] Flatric:
On my phone Knox was tripped after rooting my phone and everytime I wanted to give an application root rights knox said there's something wrong and I should uninstall the app and reboot my phone.
[Galaxy S 4 Mini General] Razvan:
From arco's root thread.

Powered by CM11 - M6 snapshot
[Galaxy S 4 Mini General] Aronuser:
Thanks for providing the info, I'll add it to the OP and give you credits :good:
[Galaxy S 4 Mini General] Aronuser:
Thank you, I'll add the info to the OP and give you credits. :good:

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

To all further informations which can be added I'll add them too and give credits, but skip writing it down here
[Galaxy S 4 Mini General] issue5854:
KNOX tripped

Hi, I like that there is someone taking care for this device.

I have a GT-I9192 (A Duos version of S4 Mini) and rooted it so the KNOX is 0x1

Also a friend of mine has one too, and I updated his phone to the latest stock rom (not rooted or anything other, just update) with Odin, and his warranty bit shows 0x1 :rolleyes:

but a couple of days ago, his phone had a hardware damage (I think so) there is a problem with the screen so the phone shuts down after 3 or 4 minutes, and then doesn't restart. Went to Samsung Costumer Care and they say that the phone has been rooted, so it's out of the warranty.

also about the knox and eFuse thing, as I could understand in some other topics ( like this one: http://xdaforums.com/showthread.php?t=2486346 ) the eFuse thing comes in use in Snapdragon N9000 and above chips, and this device has a Snapdragon 400 :eek:

however, it would be very good if we could make a Knox reset...
[Galaxy S 4 Mini General] rpgdev:
A knox reset isn't possible right now and probably won't be in a while (or ever). Tripping knox voids your warranty, in many people's cases (like mine) this isn't a problem because they aren't covered by it but if you are then you should probably think it twice before messing with something that could trip knox. There's no way around it sadly. I hope your friend can at least repair the device with a third party.
[Galaxy S 4 Mini General] fburgos:
Was you're friend previous rom a knox one?

About efuse, afaik all snapdragon chis have them, and it's not exclusively on snapdragon an old motorola model which is not snapdragon had efuse to lock bootloader, then efuses are there and they could be used by vendor in any way,

certainly they're not in samsungs exynos
[Galaxy S 4 Mini General] issue5854:
Yep, I think so, just as mine is

Sent from my GT I9192 (rooted stock ROM)
[Galaxy S 4 Mini General] fburgos:
That's bad, then it's true flashing different boitloader version will trip Knox, even a newer.

I guess the only way to update is the official way
[Galaxy S 4 Mini General] rpgdev:
If you don't have knox don't EVER UPDATE. It's difficult to have a device and not trip knox, at least not if you want to have all the good stuff. Samsung it's really screwing their customers with this stuff.
[Galaxy S 4 Mini General] issue5854:
It's so bad for them, there are many other companies providing Android phones, so there are other choices too.

But I think there will be some guy out there who will find a workout for this...

Waiting for it... :what:

Sent from my GT I9192 (rooted stock ROM)
[Galaxy S 4 Mini General] fburgos:
hope that guy is there, but i think is hanging out with the guy bring custom rom to the i9192
[Galaxy S 4 Mini General] rrgrrg:
There will be a custom rom for the i9192 ;)
[Galaxy S 4 Mini General] fburgos:
Ohhh ^_^

I'm so excited hope i can try it soon
[Galaxy S 4 Mini General] rrgrrg:
its wip but its 95% done :D :cool:
[Galaxy S 4 Mini General] Razvan:
NOT FOR OUR PHONE! Is just for INFO.

Some hopes for resetting Knox, currently only for Exynos CPU. :cool:

NOT FOR OUR PHONE! Is just for INFO!

[MENTION=5752531]Aronuser[/MENTION]

You can add this info in OP, if you want of course. :D
[Galaxy S 4 Mini General] say010:
I need flash the rom But i Can back to old once again without problems or not.
[Galaxy S 4 Mini General] leripe:
You are always able to get back to stock, but if you have knox it will void your warranty.
[Galaxy S 4 Mini General] gladson1976:
I am not sure about tripping KNOX with a custom recovery.

I have a 9192 with BML1 (has KNOX). I have rooted it with Kingo (doesn't trip KNOX) and have flashed Philz Touch recovery using Odin. I am still on the stock ROM with stock kernel.

My KNOX warranty is still 0x0.

Am confused now :confused: :confused:
[Galaxy S 4 Mini General] Aronuser:
I guess you deserve an award, at me a custom recovery tripped it. I'll add the info to the OP.
[Galaxy S 4 Mini General] :
I don't know what's the 'big thing' about KNOX.

So what? Knox is 0x1 on your phone... will there be a difference? The most important thing in my opinion is getting the status back to Official from Custom/etc. , which I did (and I'm sure everyone knows how).

- You voided your warranty? So? Just buy the phone a €5 cover (like I did) and it's almost unbreakable... If you drop it from 3m high, the phone will not feel it with a silicone cover. Just be careful with water, cause it can cost you €50 to remove water from a phone, and you will still have errors.

- Be careful while flashing files you're not sure about to your phone. Always ask.

That's what I think about KNOX and warranty.
[Galaxy S 4 Mini General] say010:
Please help me I am unable back to stock rom... The word Samsung and nothing happens phone is KSA-I9192XXUBNB and flashed withe odin heeeeeeelp:eek:
[Galaxy S 4 Mini General] Aronuser:
Do a factory reset in recovery if that doesn't help

Do a full wipe in the twrp recovery and flash stock rom again
[Galaxy S 4 Mini General] say010:
Thank you I flash stock rom again and again and again :eek::eek::eek: and the latter worked :eek::eek: thanks ....