yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] mnorris298:
Hi Everyone! I have a HTC One M7 with Verizon and am looking to unlock bootloader, S-OFF, as well as root mainly. I have tried Sunshine which tells me I have to root first. I have also tried, Kingroot, Moonshiner and most of all of the other programs.Upon looking up this I found I need to unlock my bootloader. To do this I need to S-OFF. I didn't catch HTCDEV in time to unlock the bootloader since Verizon blocked it so I would appreciate anyone who could help me root, unlock the bootloader and S-OFF. Thanks! I forgot to add, I am running HBOOT 1.6.1.
[Verizon HTC One (M7)] bdizzle1686:
If you're on lollipop, pretty much only things I can think of that have worked are Kingroot (You have to try it MULTIPLE MULTIPLE TIMES) , N if that doesn't work on the latest version, try older versions (I remember old versions working for a few ppl, I believe it was like version 4.5 or 4.50.-something). The way kingroot works, u have to run it like sometimes 10-20-30 times of it saying failed, and eventually it works. I successfully did it on 2 of my friends m7's... (Not my own, I Sunshined back on 4.4.2)

Then, when/if u get kingroot to work, run sunshine...
[Verizon HTC One (M7)] mnorris298:
Alright I'll keep trying kingroot
[Verizon HTC One (M7)] mnorris298:
Any other ideas? Kingroot just keeps rebooting my phone. If not rebooting it fails regardless. Ran at least 40 times
[Verizon HTC One (M7)] bdizzle1686:
Only other way for a vZw m7 is to find somebody who has a Java card, and make arrangements to ship / drive your phone to them, and they'll b able to S-off, bootloader unlock, & root it within 5 mins. Java cards from what I understand r VERY expensive, but over in the vzw M9 thread, there's a whole thread that's just/only for the topic of arranging to get your phone unlocked with a Java card owner, as Sunshine still to this day has never worked for the VZW variant of the M9. I know there are some VERY reputable and well known devs over there who would be willing to hook u up and have been doing it for others on xda for over a year now, (for quite cheap I understand) -although I highly recommend tossing em a donation at least for their troubles.... Maybe [MENTION=3472611]dottat[/MENTION] can point u in the right direction
[Verizon HTC One (M7)] firejuggler86:
Danngg.. I wonder if this is a result of Google's continuous security updates? When I ran Kingroot to temp root before running Sunshine, it rooted on like... the first or second try... this was also after I'd foolishly tried every single root exploit that were designed in the days of Android 1.x and Gingerbread, which might have weakened some security if it didn't break it completely.. The binaries are called psneuter and gingerbreak, if you wanna give it a shot. There's also Rumrush, Firewater, Towelroot... probably others that I can't think of. None of them are likely to give you root, but if you use all of them and then use Kingroot, maybe Kingroot will work. I would personally do that sooner than running Kingroot and having my phone reboot 300 times...

So, I guess all you can do is keep trying.
[Verizon HTC One (M7)] azizorochi:
I have verizon htc one m7 and i want to root it i have tried

Kingoroot

Kinguser

Firewater

Rumrunner

Rootgenius

Etc

Android kitkat 4.4.3 htc6500lvw plz help
[Verizon HTC One (M7)] mrcblake:
I can not help you with the s-off and unlocking bootloader but Ican tell you how to root your phone.

Install WeakSauce2.apk, and superuser in that order and you are done.
[Verizon HTC One (M7)] sandraf:
solve it?

Did you find a way to do s-off? because I can't do it, It rooted but I can do the s-off :confused:
[Verizon HTC One (M7)] mozhno:
I did it as follows. I used KingRoot and obtained its form of root. Then I ran Sunshine, which requires that you first are rooted. Sunshine reboots mid-process, losing root. So I ran KingRoot again, obtaining root. Then I ran Sunshine and it took up where it had rebooted, and got s-off. Then I found a script to eliminate the KingRoot temporary root. It did not exactly fit my file system, so I by hand made all of the changes indicated in the script (some of the changes in the script were not really important, some referred to files I did not have, etc., but I was able to change the important ones.) When I rebooted, I got the SuperSu pop-up to update, which I did, and ended up with a Verizon M7 with unlocked bootloader, s-off, and rooted.
[Verizon HTC One (M7)] Maonela:
What script did you find? Do you mind sharing it? So that I try your method... because I too have the same htc6500lvw and have tried all of the above methods using KingRoot and sunshine. :good: thanks I'm advance
[Verizon HTC One (M7)] mozhno:
Here are two sites I had left in my bookmarks:

http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/

https://androidmtk.com/replace-kinguser-with-supersu

You could probably find more.

The only way this worked for me was to read the script and figure out what the critical replacements are. You should note that the critical steps involve files that have the immutable bit set, and the scripts show a two step process of first changing the immutable bit, and then deleting the file. I did these by hand, since some of the files that needed replacing were not in the sub-folders indicated in the scripts.
[Verizon HTC One (M7)] starboi4eva:
HI, fellow m7vzw user here. Let me share my experience. Around mid 2015 last year HTC released an update for lollipop that patched kingroot to be used to root its device. But all hope is not lost as you can doengrade back to the version of lollipop that is vulnerable to Kingroot exploit. I discussed this method last year around October with some other htc one m7 vzw owners. One of them pointed out that as a failsafe in case something went wrong with htc's firmware, it can be downgraded back ONE version to avoid that faulty firmware. For example if they release a version in January, February and March (March firmware being faulty as example). You can downgtade back to the previous firmware using fastboot and the required firmware files. We never tried to downgtafe again from Febraury to January because when we were already rooted and s-off after one downgrade ???.All files on links for the files are located on the Verzion HTC one forum..... i'll try to find the post containing proof for you.

---------- Post added at 07:56 PM ---------- Previous post was at 07:49 PM ----------

Sorry for the long post btw. Here's the link to the thread that taught me how to downgrade. http://xdaforums.com/verizon-htc-on...-3-s-users-t2919442/post64629850#post64629850 Today im happily S-off and running santod's GPE 5.1.1 cfw. Good luck! !:)
[XDA Assist] ssaull:
Hello,

This is a continuation of post http://xdaforums.com/general/xda-assist/xperia-c4-5306-wont-upgrade-t3301096?nocache=1 To recap, about two weeks ago I got a OTA update message, left the phone updating which resulted in a complete unresponsive device, that is a black screen, a red light when charging. The only thing that is allowing me is to go into flashmode, which I've been using to try to repair.

The last thing I've tried was to use Flashtool (v. 0.9.18.6) which gave the the following error.

02/046/2016 17:46:26 - INFO - Selected Bundle for Sony Xperia C4 (E5306). FW release : 27.1.A.1.106. Customization : US-Generic-0
02/046/2016 17:46:26 - INFO - Preparing files for flashing
02/047/2016 17:47:07 - INFO - Please connect your device into flashmode.
02/053/2016 17:53:27 - INFO - Device connected in flash mode
02/053/2016 17:53:27 - INFO - Opening device for R/W
02/053/2016 17:53:27 - INFO - Device ready for R/W.
02/053/2016 17:53:27 - INFO - Reading device information
02/054/2016 17:54:36 - INFO - Unable to read from phone after having opened it.
02/054/2016 17:54:36 - INFO - trying to continue anyway
02/054/2016 17:54:36 - INFO - Start Flashing
02/054/2016 17:54:36 - INFO - Processing loader.sin
02/054/2016 17:54:36 - INFO - Checking header
02/054/2016 17:54:36 - ERROR - Processing of loader.sin finished with errors.
02/054/2016 17:54:36 - INFO - Ending flash session
02/054/2016 17:54:36 - ERROR - S1 Header checksum Error
02/054/2016 17:54:36 - ERROR - Error flashing. Aborted

This happened with 7.1.A.0.106 R3A and 27.2.A.105 R5A firmwares.

As I mentioned in the other thread, with flashtool v. 0.9.19.10 the only error I received was about a missing flashboot-delivery otherwise the flashing process continued.

Another thing that I've noticed is that when I plug the phone without going into flashmode, windows (8.1 or 10) doesn't recognize it. I keep hearing the sound of a device plugged and unplugged. This makes me think that it may be the cause why I get an error when using Sony PCC. Oh, also I get no message when using adb as suggested in http://xdaforums.com/xperia-c5-ultra/development/bootloader-unlocked-custom-recovery-t3285521

I've read elsewhere about a way to repair a bricked phone by finding a test point but I found no tutorials for my phone.

Any ideas will be welcomed
[XDA Assist] Art Vanderlay:
Hi and welcome to XDA.

There's no dedicated forum for your device here in XDA. I found a discussion thread about the flashtool here http://xdaforums.com/xperia-c5-ultra/development/androxydes-flashtool-features-xperia-c4-t3292650 You can try asking there or in General discussion Questions and Answers

Good luck :)
[Nexus 6P Q&A, Help & Troubleshooting] indiecognition:
I have a Nexus 6P, and need to transfer everything on it (settings, apps, data, etc.) to a new replacement device (also a 6P). Both devices are rooted and have TWRP installed.

I have a TWRP nandroid backup from the original device, and I'm having issues restoring it onto the replacement. When I restore the cache, data, and system backup options, everything seems to work perfectly except for the screen lock and fingerprint security settings. (In addition to the nandroid backup, I also copied the Internal Storage partition of the old device to the new one.)

When I restore the backup and boot up the new device, it has all my settings except for the fingerprints I had saved in Nexus Imprint. I have tried to set up the fingerprints again, and get a "fingerprint not enrolled" error that prevents me from registering my fingerprints again.

I've experimented a little, and have made two backups on the original device -- one with my original screen lock and fingerprint settings, and a second with the finger prints deleted and no screen lock. I've also tried deleting the *.key files locksettings.db from /data/system with no luck. I can access the new device and set up the screen lock again, but can't figure out how to register my fingerprints to use the sensor again.

Please help me get this figured out. I still have the original device on hand, if there's anything I need to change or I need to make a new backup with different settings. (I also have Titanium Backup pro, or could try Helium if that would do it.) Ideally I'd like to find a way to transfer everything without having to set everything up manually on the new device -- user apps, settings, and data (as well as system settings like homescreen setup, widgets, etc.).

Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] Gizmoe:
Use titanium backup for apps. And then just restore from last android backup during setup. You can choose to restore your 6P settings and which apps you use. It remembers where you put everything on MM. Even your folders and where they where. Then when it's done restore app data with TB.
[Nexus 6P Q&A, Help & Troubleshooting] indiecognition:
Thanks, the built-in Android backup/copy from nearby device worked a lot better and more thoroughly than I'd assumed. Between Helium, TiB, and nandroid backups on hand just in case I need to get more restored for an app or two (which I can extract in Titanium Backup), I think I'm set.

I did realize that the fingerprint and/or screen lock information is saved somewhere in the data partition in TWRP backups. It'd be great if someone can find them and come up with a way to remove them before restoring. Since I was transferring between two of the same devices, using TWRP to restore a nandroid backup should've worked except for the lock features. I wouldn't have restored system (and especially not EFS and Vendor) onto the new device. But data is mostly stuff for user-setup, so it'd be good to be able to have the option to remove or replace the few device-specific contents so it can be used to restore after RMAs, etc. At least for Nexus devices, that'd be a nice way to do a one-shot backup and restore.
[Nexus 6P Q&A, Help & Troubleshooting] Gizmoe:
If you were looking for just that its in

data/system/locksettings.db

If you erase that with twrp file manager after a restore you can log in and change your lock settings. There are more lock setting files in the same directory you can delete but the locksetting.db is what keeps you locked out even with the right pin/pattern/password. I have heard it doesn't play nice across devices though. So the route you took should be better IMO.
[Nexus 6P Q&A, Help & Troubleshooting] StephenMSmith:
That only works when restoring a backup to same device. There is a hardware key for the fingerprint reader somewhere else in Data partition tied to device. So, like OP found, when restoring a nandriod to a new device the fingerprint reader won't register fingerprints or work at all bc the hardware is different.
[Nexus 6P Q&A, Help & Troubleshooting] indiecognition:
I found that, and it works fine to access the device and setup the lockscreen. But the Nexus Imprint settings are separate from locksetting.db (and the *.key files in the same folder). I just wish there was a way to easily or automatically remove all of the security or lock settings from a TWRP backup and keep the other app and user settings and data. Maybe an option in TWRP or TiB for restoring a backup archive onto a new device that filters out anything that's unique to each device. Or prior to restoring the data parition, TWRP could merge any device-specific files/folders from the new device into an additional file to be kept with the original backup. Something like that.

Some things like call/SMS history, widgets, and a few app settings didn't transfer perfectly using the combo of google's Android backup and Titanium Backup that I went with. And a selective restore from TWRP files might not be hard to develop.
[Nexus 6P Q&A, Help & Troubleshooting] Gizmoe:
I covered that. It's in the last part of what I wrote. But you were more elaborate.

---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------

Yeah security is good, but it's making the days of transferring data and modifying partitions much harder.
[Nexus 6P Q&A, Help & Troubleshooting] dave2metz:
I had these problems too. How exactly do I disable those security settings? In the my file manager, I can't seem to find what I need. Can someone please explain how I go about disabling these settings so I can make a nandroid? Thanks so much.
[Nexus 6P Q&A, Help & Troubleshooting] myshen:
Not sure if this is the full list but works for me.

To clear fingerprint/Nexus Imprint data, delete/move to backup:

/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db

For each user (e.g. 0), delete/move to backup:

/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
[Nexus 6P Q&A, Help & Troubleshooting] stalls:
This works!!! Thank you!!!!
[Nexus 6P Q&A, Help & Troubleshooting] smartpr1v4t3:
u are awesome ;)

thanks
[Nexus 6P Q&A, Help & Troubleshooting] indiecognition:
Just got an N6P RMA. Deactivated screen lock and fingerprints on the old device, then made a full nandroid backup in TWRP. Restored boot, system, data, and cache partitions onto the new device.

Initially the new phone couldn't register fingerprints after the restore. Deleted the folders that myshen suggested. Had to reboot, but was able to add my fingerprints with no problem after that. :good: Worked like a charm.

Thanks for the great tip!
[Nexus 6P Q&A, Help & Troubleshooting] cognitivedissonance:
I can't believe this isn't pinned. This is a major, major issue for anyone RMAing their phone or anything like that. Thank you so much for this solution, it was not easy to find!!!
[Nexus 6P Q&A, Help & Troubleshooting] tech_head:
It is pinned.

https://xdaforums.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
[Nexus 6P Q&A, Help & Troubleshooting] ncsuwolfs:
after multiple attempts of using TB to restore phone, i did a twrp backup, and this worked. thank you
[Nexus 6P Q&A, Help & Troubleshooting] androidfreak11:
you got any idea where "fpc" went with android 9 on the pixel 3? i'm having the the same problem .. could only find "settings_fingerprint.xml" and deleted this, but problem persits .. thx in advance!
[Nexus 6P Q&A, Help & Troubleshooting] devsk:
Amazing how we all run into issues which have been looked at by many people and solutions proposed over a period of time....:)

Anyhow, I faced the same issue. The trick as outlined above didn't seem to work at first.I did a 'find /data -name fpdata'. It turned its now living in a different folder: /data/vendor_de/0/fpdata. A quick 'mv /data/vendor_de/0/fpdata /data/vendor_de/0/fpdata.org' from root shell, followed by reboot fixed the issue.

There seems to be no 'fpc' folder anywhere in 9.
[Nexus 6P Q&A, Help & Troubleshooting] Gizmoe:
All I ever did is erase locksettings.db in /data/system and all was fine. Haven't used the 6p in a bit though.
[Nexus 6P Q&A, Help & Troubleshooting] devsk:
I faced this issue on Pixel 3, where I restored from a /data backup from my earlier Pixel 3.
[Galaxy S 5 Android Development (Snapdragon)] rbgCODE:
Yes, I was about to start working on a new Root method I am hoping works now only on the latest version of android the S5 runs on which is 5.1.1? but also any version before that. I have already generated a PoC and had it work on a few of my other phones but I am going to compile the application and try to make it automated so that anyone can use it, say click and root for the community.

Anyone feel like helping out? I actually think this may work for almost all phones and tablets as the exploit I am working on is generated from the android OS running the sensord daemon with root privs.

I look forward to your thoughts.

-Thanks

rBg :confused:
[Galaxy S 5 Android Development (Snapdragon)] The_Anomalist:
Any luck on your rooting app?
[Galaxy S 5 Android Development (Snapdragon)] ninestarkoko:
that would be amazing for many people! For example, sony Z5 line users just need an exploit to gain temporary root priviledges.

I could test your exploit on a sony xperia Z5 compact locked bootloader. I don't know if sensord daemon runs with root privs.

I can tell you two things, though:

- sony's kernel has a /system partition protection, so you cannot write/modify it. SELinux is enforced

-The good thing for the Z5 users is that we just need temporary root privs to backup a special partition (TA partition) that contains the unique DRM device key that is needed for warranty service (sony refuses to repair phones with device key erased) . This key gets erased as soon as we unlock the bootloader, which is necessary for permanent root and custom kernels.

If there's a possibility to gain just temporary root priviledges, please tell me and i can test it :)
[Galaxy S 5 Android Development (Snapdragon)] ninestarkoko:
seems that xperia Z5 uses sensors.qcom instead of sensord, unfortunately.
[Huawei Mate S] ChronoWerX:
Hi, I bricked my L09 while updating to Marshmellow ... can't install the 145 and can't install 303 too. Has someone an TWRP Backup for me from 145?
[Huawei Mate S] bgx:
That doesnt help. After restore backup from b145 with twrp the fingerprint is dead and no rotation and lightsensor.

Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
[G4 Q&A, Help & Troubleshooting] Lerchisti:
Hi there! My girlfriend has an lg g4, and has a problem with the back buttons. When she start to dialing any number the buttons start to vibrate a little bit with an annoying sound but when someone accept her call it stops or when she ends the dialing, only just when dialing. Her phone just came back from the service after a screen issue about a month ago. Anyone has the same problem? If yes, how to solve it?

Thanks for the answers! (Sorry for thd bad english)
[Nexus 6 Q&A, Help & Troubleshooting] Locoman_:
Q: why was it permissible to bully atl4ntis off XDA? Did the lesser devs have that much pull?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
huh?

i dont think that something like that is permissable. ive been "bullied" by devs before, and ignored it or fought it off, and xda does not like that sort of stuff at all, from experience. and is very against it! especially if its in public view.
[Nexus 6 Q&A, Help & Troubleshooting] hormosapiens:
I moved to stock after atlantis left. It is tough now. But I think is was about an argument concerning policy xda have for open vs closed source. maybe I am wrong but it is a lost in terms of community.
[Nexus 6 Q&A, Help & Troubleshooting] mikeprius:
In b4 the lock.
[Nexus 6 Q&A, Help & Troubleshooting] Locoman_:
He wasn't open sourced which is his right by xda policy even. Other devs made accusations they couldn't back up and harassed and attacked. Google+ has the details and it was terribly ugly before the sanitation "fixed things". That will happen soon enough here too. I never cause trouble here but felt the need to say something. Cataclysm was the best thing to come to Android ever, in my honest opinion.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
The fact is that the development of the unique 'cata-mod' has come to an end caused by a formality. The moderators concerned should be ashamed.
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
He was not bullied in any way. IT was brought to our attention that the rom should not have been in OD, so we looked at it and it was moved. The so called bullied dev decided to throw a temper tantrum and quite. It was his choice.

Now as stated he had the right to close his source completely, But when questions come up about Original work to be placed in OD the Dev is required to provide the code to prove it is Orignal development. As it was closed sourced and he refused then there was no way to prove it.

So before people start to judge. You might want to sit back and understand you know very little of the whole story.

Normally we dont bother responding to threads like this but to be honest I am sick of hearing about this. Had any of you followed the rules you would see that all the threads about this are closed. Yet here we are.

Thread closed.
[Galaxy S 5 Q&A, Help & Troubleshooting] Axle0:
Hi,

I recently rooted my S5 successfully and then got rid of touchwiz and installed Cyanogenmod 13. But then I realized that the root was gone from my phone. So I rooted again and now Cyanogenmod won't boot. (Stuck on Cyanogenmod booting animation.)

I have an S5 g900I (Oceania edition).

I'm guessing the mod went away because I wiped the system through recovery before installing CM but why can't I root again? If anyones had the problem previously which is the best version to go with? I might try CM12.1 now just to be sure. But any ideas?

Thank you :)
[Galaxy S 5 Q&A, Help & Troubleshooting] jlbuck6212:
Flash the latest update supersu.zip and root your phone. I think now you can use supersu2.46.zip on aosp 6.0.1. I've done it and works for me. If not then use the latest systemless root by chainfire. The one that works for me is 2.62. Try 2.46 first. Thanks [MENTION=631273]Chainfire[/MENTION] for all of your hard work and making it easy to root our phones. Good luck
[Galaxy S 5 Q&A, Help & Troubleshooting] tangcla:
CM13 has root built into the ROM.

Go to settings -- > about device, tap on "Build number" enough times until the Developer options appear, and enable root from within the developer menu.