yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] brholt6:
Only flash roms from the Verizon HTC One forum. You'll run into issues with roms not made for the Verizon variant. There are several available for us though. I'm using Viper right now, Ecliptic is a great rom and I can't wait to try unSense tomorrow.
[Verizon HTC One (M7)] athristguy:
thx for the reply...

but im using vzw htc one in india and i dnt want all the restrictions and apps from verizon...

so i want to install international, asia or india version.

plz do tell me if there is a way to flash vzw one.
[Verizon HTC One (M7)] brholt6:
I'm not sure about that...I would assume you'd still have the same issues because the hardware is the same. What restrictions are you talking about? Most of the ROMs we have available are debloated so you won't have the Verizon apps if you don't want them, tethering works, etc.
[Verizon HTC One (M7)] HypostaticOnion:
Check out Viper ROM, or Ecliptic

If I've helped, please hit the thanks button
[Verizon HTC One (M7)] roman_ishchenko:
Its not possible. just a verizon version roms. With root you can delete all verizon stuff.
[Verizon HTC One (M7)] athristguy:
i tried viper rom but there was no network... very shortly im gonna try ecliptic

thx
[Verizon HTC One (M7)] brholt6:
I'm guessing you'll have to toggle the network setting on either Rom to get it to work with whatever network you're using (gsm?). You can change it in Venom Tweaks...Phone Info under the Misc tab.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
I've read a little bit about Knox in the last few months, but wanted to make sure I've got everything right, especially since things have probably changed since the early days of Knox.

Here's my situation: I'm running a TMO Galaxy S3 w/ stock recovery. I was using mrRobinson's T999UVDMD5 and foolishly did the TMO update to T999UVUEMJC.

(I thought I'd be able to retain root, but ended up losing root, getting Knox, and a bootloader that won't let me roll back. :mad:)

Now my phone locks up during boot. If I'm lucky, it'll boot but locks up nearly immediately after boot.

And this is with stock everything. I've had the phone a year and a half, so it's out of warranty.

So what's Sammy's stance on their update breaking phones out of warranty?

Do they cover that? Can I get a TMO store to put DMD5 back on?

I'm thinking of using the root66 EMJC img. I'm pretty confident that it won't brick the phone, since it'll be the same bootloader I'm currently running.

And I'm not too worried if it trips the Flash Counter (flag, really) since I should be able to clear it.

But what about the Knox counter? Will that get tripped? mrRobinson's post leads me to think that it will.

Any other root options I should consider? (Above all else, I'd like to be able to restore back to stock if I need to.)

I kinda like the stock ROM (save for some bloatware) and TouchWiz doesn't bother me.
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
Thanks masondoctorjt! That's one of my questions. (albeit, a lesser one)

If TMO/Sammy's update f'd up my phone will they cover it if it's out of warranty? especially when it was fine before?

(It's also a work phone, so I'd like to be able to return it like I got it, if need be.)

It's that confirmation I'm looking for here.

This Knox thread seems to state that as long as a Knox-enabled bootloader is used, the counter won't trip. But it also says flashing Knox-enabled fw via Odin trips the Knox counter too. (which I don't fully believe) Hence my confusion. A lot of contradictory info.

Add to that the loose usage of 'flash counter' to refer to both the triangle/flash counter/flag and the Knox counter/flag and you can see why my head is spinning!

It was tricky for me to see the Knox Counter info for my phone. Recovery and Bootloader mode didn't pop up the screen.

But when I used adb to enter bootloader, I saw the counter info.
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
So did you root it, and if so, did the trip the knox counter?
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
No, not yet. I was hoping to hear back from someone who's tried this.

I didn't want to be the first guinea pig. :)

I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.
[T-Mobile, Samsung Galaxy SIII] patcal:
I would be like to hear how you did after going to T-mobile. Thanks.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
I honestly don't expect a whole lot from them really. But it's an avenue I have to try.

I'm ultimately going to root this anyway. If TMO can successfully roll me back to T999UVDMD5 completely, I'll just root that and stick till the dust has settled somewhat on Knox.
[T-Mobile, Samsung Galaxy SIII] Perseus:
For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.

It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.

NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
It was ultimately unproductive.

I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.

They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.

He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)

Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.

(all he mentioned was #NUM#)

So I'm back to stock (more or less :)). Not sure when I'll root now.

From what I've read, the custom recovery should trip Knox. Have you tried this yourself?

I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.

(Again, it's a work phone and I'd like to return it as I got it.)
[T-Mobile, Samsung Galaxy SIII] Perseus:
It will trip that previous counter bit. Don't think it will trip the Knox counter.

No I do not have the Knox Counter.
[T-Mobile, Samsung Galaxy SIII] patcal:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.

Pat
[T-Mobile, Samsung Galaxy SIII] Perseus:
Was that the Flash Counter or Knox Counter?
[T-Mobile, Samsung Galaxy SIII] patcal:
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.

Pat
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
Pat,

So just to get this straight, you flashed the stock TMO update, so you were not rooted?

Or did you do a root-injected variant of the stock?

Either way, I'm surprised you tripped the (triangle) flash counter.

But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thanks for letting me know.
[T-Mobile, Samsung Galaxy SIII] patcal:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.

Edit: Don't remember how I got root. Sorry.

Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
[T-Mobile, Samsung Galaxy SIII] Perseus:
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.

So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.

That was my plan anyway. :D I'll probably look into this later this week.
[T-Mobile, Samsung Galaxy SIII] patcal:
Yep. Let us know how it goes.
[T-Mobile, Samsung Galaxy SIII] PhilipJFry:
FYI, the Knox counter gets tripped.:(

I flashed the root66 T999UVUEMJC via Odin. That's it.

Oh, and the flash counter does not get set.
[Droid Ultra Q&A, Help & Troubleshooting] supersailor89:
so I rooted my phone and then had to unroot it because I couldn't use isis, I used RSD lite to put the latest firmware 12.15.15, that I downloaded form Motorola firmwares but the ncfee.access.xml doesn't have the right stuff in there all it say is the instructions and how to write the access. and I cannot find a way to edit the system.img and just edit the file myself. im getting the error isis cannot access the secure element. and does anyone know how to unlock the boot loader, I need a code but the Motorola websites says my phone doesn't qualify. your help is appreciated and this is the site I always got to tho this is the first time im posting :). I have droid ultra.
[Droid Ultra Q&A, Help & Troubleshooting] Yachter99:
You CANNOT unlock the bootloader on Ultra, only on Developer Edition Maxx and X. Reflash stock firmware using RSD Lite, clearly something went wrong the first time around. That or try a factory reset. DON'T try to mess with the stock firmware you are flashing, it sounds like that is what you are trying to do, that will cause problems
[Droid Ultra Q&A, Help & Troubleshooting] supersailor89:
i​

Yachter99. I can't its says I canT downgrade when I try RDS lite to put stock firmware

well turns out it was an isis issue that they had to manually change something , and I got a new sim card its all working now im on 4.4 :)
[Moto X Q&A] poena:
this stopped working a while ago. not sure why. I have it set up to read them but it's not working. is this happening with anyone else?
[Moto X Q&A] melo1819:
Mines not playing music automatically when connected thru aux cable..

Btw are they messages or hangouts? Cause I think hangouts don't work. Mine has never done hangouts. Only text messages.
[Moto X Q&A] poena:
I ended up clearing data/cache for the moto assist app and set it up again and now it works again
[Verizon Samsung Galaxy Note II] subzero2000:
I have a Verizon Samsung Galaxy Note II (SCH-I605), as does my wife. Mine has an unlocked bootloader and is running the "stock" 4.3 ROM minus the official Knox stuff. My wife's is running the stock 4.3 OTA.

I have been using the NFCLockScreenOffEnabler mod for Xposed to provide a tag lost notificiation so that NFC ReTag can use that to put my phone in Car Dock mode. My wife wanted similar functionality, so I rooted her phone with Kingo and verified that it did not trip the Knox counter.

She is not interested in custom ROMs, and frankly I'm not much any more either. Root is more important to me than an unlocked bootloader.

I am having stability issues that include random reboots and force closing of apps for no apparent reason. My wife does not appear to be having these issues, even after I rooted, installed Xposed, NFCScreenLockOffEnabler, RootCloak, and told SuperSU to disable Knox notifications when it prompted to do so.

So my question is simply this: If you were in my shoes, would you be inclined to return to stock and accept the OTA and knowingly lock the bootloader without knowing if it will ever be unlocked in the future, or keep the bootloader unlocked and hope that the devs are able to straighten this out on a device that to the best of my knowledge is close to a year old, if not over it?

I know which way I'm leaning, but I'd love to hear feedback from others, particularly if you're in a similar situation and contemplating it as well.

Thanks!
[Verizon Samsung Galaxy Note II] greekchampion04:
It's a personal decision. Most people on this board are tinkerers and (like myself) will always want to remain unlocked as to have the freedom and ability to do whatever we want to our phones.

If the reliability is the #1 factor to you, then staying stock is probably your best bet. If you don't want Verizon having the final say over what you phone can and can't do, keep the unlocked bootloader.

There are stock-based roms out that are essentially stock, but allow you to keep the unlocked bootloader. For the phone that does not have the OTA yet, I would personally go that route.
[Verizon Samsung Galaxy Note II] trollishtrucker:
I agree, I would keep the unlocked boot loader so that I kept the freedom to do what I wished with the phone
[Verizon Samsung Galaxy Note II] LordRalh3:
Personally I'd install n3bula and win
[Verizon Samsung Galaxy Note II] nightelfdruid:
Am I perma locked?

I've been curious.. I've been running the 4.1.2 stock rooted rom that imnuts put up for quite some time... I acquired the Gear and odined the official 4.3 rom from Sammobile... So I'm running stock 4.3 with root. Since I haven't actually taken any OTA updates, am I "perma" locked having flashed the official firmware?
[Verizon Samsung Galaxy Note II] TonikJDK:
Yes, you are locked.
[Verizon Samsung Galaxy Note II] nightelfdruid:
Dammit.
[Verizon Samsung Galaxy Note II] subzero2000:
Locked Bootloader?

If the official 4.3 ROM from Sammobile replaced the bootloader, then yes. An easy way to tell for certain is to go into Download mode. From a powered off state, hold Volume Down, Home (the physical button at the bottom), and Power buttons all at the same time to go into Download mode, then hit Volume Up when prompted. If on that screen you see mention of Knox Warranty, then yes, your bootloader is locked, unfortunately (if you care about warranty, the desired state of the Knox Warranty flag is 0; any other value indicates that the flag has been tripped). To exit that mode, you can safely do a battery pull if necessary, as just entering that mode doesn't do anything by itself.
[Verizon Samsung Galaxy Note II] subzero2000:
End result

Well, after much soul searching, on Friday evening, I went ahead and did what I was truly trying to avoid, and that was a complete wipe and re-install. I went back to complete stock 4.1.2, re-rooted, and re-installed 4.3 from the "official" ROM from t0ltevzw. I have restored nothing using Titanium Backup, instead setting everything back up manually. I am now up on 4.3 and still have an unlocked bootloader.

So far (knock on wood), it seems to be pretty stable and random re-boot free. Hopefully I didn't just jinx anything by saying that... :fingers-crossed:

Thank you to everyone who read and replied and/or participated in my poll. I should have listed my final course of action as one of the options on the poll, but I really didn't want to do that if I didn't have to, and I didn't think about adding it as an option on the poll until just now anyways... :)
[Verizon Samsung Galaxy Note II] TX_Jax:
How do you confirm an unlocked bootloader?
[Verizon Samsung Galaxy Note II] subzero2000:
Determining whether your bootloader is locked or not

You have to get the phone into Odin mode, as if though you were going to flash something via Odin.

First, take the back off, as you will most likely have to pull the battery to reset the phone at the end of this.

With the phone powered off, hold Volume Down, the Home button (or whatever it's called) at the bottom, and Power at the same time, until the phone turns on, and you see a Warning screen. On that warning screen, press Volume Up to Continue.

The phone will now be in Odin mode, and you'll see an Android with the text Downloading..., Do not turn off target!!

Look at the small text in the upper left corner of the screen.

If you see mention of Knox Warranty, your bootloader is locked, and currently cannot be unlocked.

You may safely pull your battery despite the warning at this point to exit Odin mode (I don't know of any other way to exit Odin mode, unless I'm simply not holding down power long enough to do it). Pulling the battery at this point would only be an issue if you were actually using Odin to flash something and you pulled the battery in the middle of the flash.

Note: Some people may be tempted to try and use adb to achieve this instead of powering down the phone, but this will not work; "adb reboot download" will put the phone in download mode, but you will not see the text in the upper left if you try this method. The only other sane option that I can think of to try would be "adb reboot odin", and this does not have any effect other than rebooting the phone normally.
[Verizon Samsung Galaxy Note II] coffeedave:
Nooo

not the official OTA, there are a number of "stable" ROM options out there that are certainly worth giving a chance before returning to OTA
[Verizon Samsung Galaxy Note II] MunkinDrunky:
Good luck finding the solution that suits you best. We all strive for the best daily diver (plus more). But before going to lock down stability can be had with patience. Relfash the roms clean or Odin back to stock-all before considering the plunge to locked bootloader if you are hesitant.
[Verizon Samsung Galaxy Note II] dmunz:
I tried holding the power button and it shut down after about ten seconds. Didn't need to pull the batery. YMMV.

FWIW

DLM
[7" Kindle Fire HD Q&A, Help & Troubleshooting] buckethead41414:
I have Rooted my Kindle Fie HXD 11.3.1 with root and restore. it said it was successful and everything went fine but when it restarted the last time i didnt have superuser, so i tried to download the .apk and install it and update but it wouldn't. I used root checker to check if it was rooted and it said it was but still no superuser. if anyone could help i would be greatly appreciative. sorry for the grammar i have a D in English class haha. PS i want to install cyanogenmod
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
You can't root your tablet with root and restore. Check the links in my signature.

Edit: There are no custom ROMS for your tablet yet.
[Moto X Q&A] TheCuban:
Okay, got a strange question here. I plan on going from the N5 to the unlocked GSM MotoMaker Moto X version. All I want is root with stock recovery (don't really care for a custom recovery, plus I'd like to still receive OTAs). Can I unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU? Or do I *have* to flash TWRP to achieve root?
[Moto X Q&A] c19932:
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".

or

use one of the methods in the original android development section to achieve root.
[Moto X Q&A] TheCuban:
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root. :)
[Moto X Q&A] flashallthetime:
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto

Sent on my Moto X
[Moto X Q&A] TheCuban:
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
[Moto X Q&A] flashallthetime:
On the moto yes, nexus devices are a different beast

Sent on my Moto X
[Moto X Q&A] xxxdepot:
Hi I am planing my first root and I am honestly a little confused. I am on TMobile with 4.4 KitKat (Moto X).

I understand how to unlock the Bootloader and that I need to install TWRP before I can activate SU.

I am just not sure about the bugs (if any) with TWRP and what version to use.

The reason for my concern is on the TWRP website the Moto X is not listed as a supported device.

Is this video Tutorial still valid - is this how to do it with 4.4 KitKat?

And is this the latest version that works (what are the known bugs)?
[G2 Q&A, Help & Troubleshooting] d3FytH3m1Nd:
Currently the quickview consist of the music player, the clocks and the weather forecast. However, ever since I rooted the phone (d802), I have uninstalled the weather app and now that page of the quickview just gives me an error. Is there any way to remove it or change it?

If not, can someone kindly upload the weather app (there's 2 app i believe) for me? Thanks! The error is seen below. Sorry for the bad quality as I can't take a screenshot with the case cover shut.
[G2 Q&A, Help & Troubleshooting] d3FytH3m1Nd:
bump!
[G2 Q&A, Help & Troubleshooting] dtuma1980:
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.

Symptoms-

Not booting (Hanging at LG screen)

Able to access CWM recovery

Unable to Mount USB

Unable to access Download Mode

#####1#####

Uninstall all previous LG Drivers installed (Add/Remove Programs)

#####2#####

Install PDAnet to get the drivers required installed.

#####3#####

Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.

(ADB Devices should give the result of: ###DEVICEID### Recovery)

#####4#####

Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions

(The file will need to be renamed to aboot.img)

#####5#####

Download: http://www.androidfilehost.com/?fid=23252070760973106

#####6#####

Extract the files we need:

g2_security

loki_patch

loki_flash

recovery.img

#####7#####

Get into a command prompt and run the following:

adb push g2_security /sdcard/

adb root

adb push loki_patch /data/local/tmp

adb push loki_flash /data/local/tmp

adb push recovery.img /data/local/tmp

adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"

adb shell "chmod 644 /data/local/tmp/aboot.img"

adb shell "chmod 755 /data/local/tmp/loki_patch"

adb shell "chmod 755 /data/local/tmp/loki_flash"

adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"

adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"

adb shell "rm /sdcard/g2_security"

adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"

adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"

adb shell sync

adb reboot recovery

Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!

#####8#####

Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)

#####9#####--At this point the following thread finished reverting the phone to stock.

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

My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.

If you found this help, please donate and buy me a beer!

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
[G2 Q&A, Help & Troubleshooting] galeej:
Hi, your last step, a Verizon link for restoring back to stock.. I have international D802.. can I use some other rom(omni rom) instead of your last step...