Develop Bugs

Blackscreen Recovery Visual Now!!

Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Days are gone with BLACK SCREEN RECOVERY
Here how it works!!
You need some files.
1.Download Adb Files form here
2.Download This [email protected] Tool,Thanks To RiboComments
3.Extract Adb "c:\ " on your pc Creating Folder Adb.
4.Copy [email protected] From your Downloaded folder to desktop.
5.Double click on [email protected] ,and locate the adb.exe form c:\ when asked.
6.Connect you phone using "Charge only mode" with usb debug on.
7.Follow The UI of [email protected] and when will you get your phone screen appearing.
8.Now restart your phone in Recovery mode.
And enjoy The Pleasure Of CWM.
REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.
Sometime if not working in CWM .
Do the following Troubleshoot .
1. Disconnect your phone.
2. Close [email protected] And
3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .
4. Now connect Your phone With CWM recovery screen and START [email protected]
5.Click on Restart ADB . (More than once if needed)
This Tool Is Not Mine.
Original Thanks Goes to creator of this Tool RiboComments For his Great Work.

Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc

BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
And rajanand is the only one that provides a solution.
I'll try the solution of rajanand and I will post the results
Greetings.
Sorry for my bad English.

rajanand said:
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Click to expand...
Click to collapse
Works great ! Thanks again.

Works great ! You're the BOSS.:good::good:
Thanks a lot.

Aww yeah! Great job sir!

BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
little knowledge it always dangerous to health, so tk care of ur health.
Thanks aunto for commenting on my useful post.

Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc

Do not download! Maybe a VIRUS!
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.

matt5eo said:
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
Click to expand...
Click to collapse
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so
To avoid interruption between ADB and Your phone.
i personally recommend it, rest is on your side.

BigChillin said:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Click to expand...
Click to collapse
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.
Please Stop Arguing..further ,i am not here to entertain such comments.

rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help

Anto2 said:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
Click to expand...
Click to collapse
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.

ngoralph said:
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Click to expand...
Click to collapse
Thanks for your support.

marchelius said:
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
Click to expand...
Click to collapse
Thanks dear for support , hope you all be with me always .

rajanand said:
Thanks dear for support , hope you all be with me always
Click to expand...
Click to collapse
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!

marchelius said:
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
Click to expand...
Click to collapse
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.

I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2

rajanand said:
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
Click to expand...
Click to collapse
Not working, same sh*it

insink71 said:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)
its just a recommendation from my side. That's it
Its fully safe from my end and free from any type of virus.
as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.
i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.
Why occurred?
1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)
2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)
3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)
4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)
4.CWM is fully working without any error.(Blindly)
5.only the four keys are lighting up,
6.This tool is The only option in that case to flash any custom ROMS.

[Q] viper x reboots when receiving calls

all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?

Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue

Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )

A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...

webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January

Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...

What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.

Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!

Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue

Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW

Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing

webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH

webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!

[Unbrick Service] Bricked Phone? Need Help? Look Here.

Introducing the ...
Matt Unbrick Service!
If you have a problem with your HTC One (M8), and just don't know what to do, don't despair! I can help.
With over 3 years experience with Android phones, we exist solely to help you enjoy your phone, and prevent you from experiencing the inconvenient HTC return process, which can take several weeks.
Services I offer:
Rooting
Unrooting
Unlocking Bootloaders
S-off
Updating Firmwares
Flashing RUUs
Fixing unbootable phones!
Service is free, however donations are welcome and appreciated
How it works!
To request a repair, simply post here on the thread.
I will then get back to you as soon as possible and we can then arrange a TeamViewer session or I can write up a guide for your situation, for you to follow independently.
People I have helped:
Eswog
Crazhy
nolinuxnoparty
mattoffshore
dayze0
bteljuice
Amrut223
bamidrol
ringrover
ElunChen
slicetherice
darktyroll
IT4ALii3EN
malavan
ProxiStyx
natzakaria
sly101s
smaug8821
dlnas
sardor
SoftHd
dh2311
royoshukrun
mathrania
adichandra
sfjeep
Thanks for reading, and I hope to be able to help ​

i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!

Question Please Help
I was installing some roms on my vzw varient of the HTC One M8 can the install failed and so i recovered to nandroid backup and finally get data back but only have 3G any way or thing that you know that might help?

Iconic Bullet said:
I was installing some roms on my vzw varient of the HTC One M8 can the install failed and so i recovered to nandroid backup and finally get data back but only have 3G any way or thing that you know that might help?
Click to expand...
Click to collapse
Try a simple sim pull if you haven't already. Often times if you are stuck on 3g, a sim pull will enable LTE when you reboot the phone. on Verizon.

I tried that i am still having a problem can i try at revert to stock and fix it if so can you please help me...

delete

Thread cleaned.
When posting always try to provide as much information as you can.
Ghost

So I have the att varient and I tried to flash the Venom rom 1.2 version from stock rooted S-On and after flashing I am now stuck at the splash screen and cannot access the bootloader, any suggestions?
EDIT: I have figured out the problem and solved it please disregard this post.
Sent from my LG-E980 using XDA Premium 4 mobile app

Hey Matt, I wonder if you can help me out. I flashed the GPE rom, it was working fine until i decided to edit the build prop. I changed the density value from 480 to 320. It worked but it was too tiny. Then i would readjust the value to 400 but upon restart the value wouldnt change. So i tried changing it back to 480 and saved it and directly went to reboot, not my phone refuses to load up. When i hold power and volume up the HTC logo screen comes up and then it turns back off, I cannot get into bootloader by pressing volume down and power. I am stumped. If you can assist me, id be sure to tip you some BTC your way.
Thank you in advance
---------- Post added at 09:49 AM ---------- Previous post was at 09:13 AM ----------
yas1987 said:
Hey Matt, I wonder if you can help me out. I flashed the GPE rom, it was working fine until i decided to edit the build prop. I changed the density value from 480 to 320. It worked but it was too tiny. Then i would readjust the value to 400 but upon restart the value wouldnt change. So i tried changing it back to 480 and saved it and directly went to reboot, not my phone refuses to load up. When i hold power and volume up the HTC logo screen comes up and then it turns back off, I cannot get into bootloader by pressing volume down and power. I am stumped. If you can assist me, id be sure to tip you some BTC your way.
Thank you in advance
Click to expand...
Click to collapse
Never mind Matt, It eventually Loaded, Sigh what a relief. Il be sure to keep you in mind!

Hi @Matt !Got an m8 with that whelp message on firewater, u said above u can s off?

Prompt 24 hour service.....haven't seen Matt here since the 15th. Hmmm :sly:

th3lawmak3r76 said:
So I have the att varient and I tried to flash the Venom rom 1.2 version from stock rooted S-On and after flashing I am now stuck at the splash screen and cannot access the bootloader, any suggestions?
EDIT: I have figured out the problem and solved it please disregard this post.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have an issue similar to this.
Phone gets to the HTC powered by android screen and then dies. I cannot access bootloader using vol down and power. It won't respond.
S-Off, unlocked boot loader.
Phone also periodically turns on by itself, then procedes to shut down after it gets to the HTC Powered by android splash screen.
EDIT:
Managed to get into recovery using the advice in this post:
Tikerz said:
When you plug it into the computer does the computer make a ding sound that it's connected? If so, then press power and volume up until the disconnect ding sound which indicates it's rebooting and then immediately press volume down and see if you can get into fastboot. The timing is tricky so I've found using audio cues from computer can help if the phone is messed up.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Leaving this here in case anyone else has the same issue. Mods delete if you see fit.

Prompt 24 hour service? but how?

SimplyNando said:
i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!
Click to expand...
Click to collapse
copy your custom ROM into a flashdisk. then use USB OTG, search on youtube about the tutorial.

Mr Hofs said:
Prompt 24 hour service.....haven't seen Matt here since the 15th. Hmmm :sly:
Click to expand...
Click to collapse
It usually is, I've just got back from holiday and ran up a large phone bill so been trying to sort that out.
People should private message me so that I get the notification email as I thought I was subscribed to this thread yet when I checked just now, there's loads that I hadn't seen.
Sorry!

Matt said:
It usually is, I've just got back from holiday and ran up a large phone bill so been trying to sort that out.
People should private message me so that I get the notification email as I thought I was subscribed to this thread yet when I checked just now, there's loads that I hadn't seen.
Sorry!
Click to expand...
Click to collapse
That's no problem and could happen to all of us. But some pointers from my point of view :
When i look at your O.P you give the tendency to look like a non profit company/organization which indeed offers a free service, that's all fine but please give the users the hint when it will be "offline" when you are on holiday or at least "offline" without a reason to stop the reactions users like me posted before. It looks like a 24 hour service promise which is not there.
I have been a helpful member on the hox section of xda the last 2 years and never had the need of such a thread/service. I think it won't make that major difference because users will always make new threads with their problems anyway.
This is not ment in a bad way, just my personal opinion !
Cheers.

SimplyNando said:
i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!
Click to expand...
Click to collapse
kinda ran into the same problem. problem is i dont have an usb otg cable. i tried installing viper rom from but it would fail towards the end. would really like to have my phone back up and running.

exocetdj said:
Hi @Matt !Got an m8 with that whelp message on firewater, u said above u can s off?
Click to expand...
Click to collapse
He can help with this? Matt, you can help with this? hahah

Hi @Matt, i read that you can help with s-off?
I'm using a european WWE m8 (CID htc__e11) and i can't seem to get it working, you would be my personal hero if you could help me out with this one.
Greetings,
Incapable

incapable said:
Hi @Matt, i read that you can help with s-off?
I'm using a european WWE m8 (CID htc__e11) and i can't seem to get it working, you would be my personal hero if you could help me out with this one.
Greetings,
Incapable
Click to expand...
Click to collapse
If firewater isn't working for your device, then this service nor any other can help you gain S-Off, like it's been started in many threads already. You'll have to wait until firewater suports your phone.

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

Lock Screen Pin reset overnight

Hi Everyone,
I am mildly freaked out because I'm overseas and somehow between the time I went to bed and woke up my pin stopped working and I am really stumped. The phone is encrypted at boot and I can get through that lock but when I reach the lock screen my pin just doesn't work anymore. I have rooted my T-Mobile HTC 10 without issue and have TWRP installed.
My fear is that I am going to have to do a hard reset and that scares the crap out of me.
Any ideas on what I might be doing wrong or can try? Yes, the pin is absolutely correct.

Try the following:
Boot into TWRP and open the TWRP file manager.
Go to /data/system and delete all locksettings.* files.
Reboot to your system.
Your pin should be removed and you can set a new one.
Sent from my HTC 10 using XDA Labs

Worked Great!
Thank you thank you thank you!!! Worked as expected.
Maik268 said:
Try the following:
Boot into TWRP and open the TWRP file manager.
Go to /data/system and delete all locksettings.* files.
Reboot to your system.
Your pin should be removed and you can set a new one.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse

Maik268 said:
Try the following:
Boot into TWRP and open the TWRP file manager.
Go to /data/system and delete all locksettings.* files.
Reboot to your system.
Your pin should be removed and you can set a new one.
Click to expand...
Click to collapse
Good job you just unlocked the phone he just stole or maybe trying to creep on the significant others texts photos.
This is a joke

afuller42 said:
Good job you just unlocked the phone he just stole or maybe trying to creep on the significant others texts photos.
This is a joke
Click to expand...
Click to collapse
Well, you also find this information in the TWRP thread - FAQ section
Sent from my HTC 10 using XDA Labs