Hello guys, I want to ask you for help. I was trying new RessurectionRemix ROM (Oreo) so I have created recovery file in TWRP (3.0.4.1) and stored it in my PC. Now after trying new RR I wanted to go back to my old RR Rom so I have restored my system from recovery. Everything went fine but after typing my SIM card Pin code, I had set that pattern lock which always show up when you reboot device and here is the problem. I am 100% sure what the patter was but it is not working, so I tried to restore everything once more but it didnt help. I have tried some tutorials which I have found here on XDA and on YT but it didnt work. Even when I tried to lock my phone with google device manager I hadnt option to lock it but only to leave message and my phone number. I do not know what to do now so I would be gratefull for any help. I might have here many mistakes but I have done what I could with my English skill. Thank you.
Edit: Someone sent me this and it fixed my problem. Thank you very much. Problem solved.
"https://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/"
Related
So yesterday I was using the Font Installer app on my HTC One M8 (AT&T) and I was trying to delete a font I downloaded. But on accident, I deleted the Clockopia font and Robotto font (two system necessary fonts). So I thought it would be fine, but it wouldn't let me do anything on my phone so I reboooted it. It now will only start in recovery (TWRP) and bootloader. If I try to boot the system, it says I have no OS, and I get stuck on the boot screen. I have wiped the data, and tried everything I could think of. I can't find a way to fix this problem and the phone is not going to work unless I get something done. I am going to the store to buy a MicroSD card for the phone, in case that is a way to help. Please, any help would be appreciated! I am generally new to the rooting world, so this was a dumb mistake, but please help if you can. I have found threads similar to this but none helped because this phone is different so certain ways to fix this won't work. Again, please help if you can!
What ROM are you using? You can try dirty flashing that ROM again. If you're in ATT stock, just download the ruu and run that. It's going to wipe everything on your internal storage, so copy the things you want to a microsd card before you do
The problem is that I already wiped everything, but it says I have no OS anymore. Like I said, I am no pro with this stuff so I basically just have a phone sitting in recovery. I am currently trying to use ADB to load a file to the device but its a whole ROM (hoping that will help put the fonts back where they were) so I can flash it when it's on the phone. When I slide to start the adb sideload, it disconnects and won't pop up in the Device Monitor, but as soon as I stop the sideload I can see all of the files in my computer. So I'm not sure what I can do with this. Thank you for the reply, but I was on Android Revolution HD before I accidentally deleted the font. Now I'm trying to download it again!
Ligammari said:
The problem is that I already wiped everything, but it says I have no OS anymore. Like I said, I am no pro with this stuff so I basically just have a phone sitting in recovery. I am currently trying to use ADB to load a file to the device but its a whole ROM (hoping that will help put the fonts back where they were) so I can flash it when it's on the phone. When I slide to start the adb sideload, it disconnects and won't pop up in the Device Monitor, but as soon as I stop the sideload I can see all of the files in my computer. So I'm not sure what I can do with this. Thank you for the reply, but I was on Android Revolution HD before I accidentally deleted the font. Now I'm trying to download it again!
Click to expand...
Click to collapse
Put the ROM onto your extSD, and flash it in recovery. Your phone will work again.
Hey guys thanks again for the help, I fixed it all with the flashing of a ROM again and I'm now posting this with my phone! You guys helped really quick, I appreciate it!
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.
Hi..
I updated to Android N, and everything went fine, but I found it a little buggy and (my mistake) didn't realize xposed was not working yet, and there are some privacy modules I really would like.... So, I decided to downgrade back to MM.
As I am s-off, I booted into a rom.zip RUU (1.96.617.20). During the subsequent initial setup, I picked a screen pattern (to be used on restarts only)..for whatever reason, I decided to pick something different besides the rather easy pattern I had used since the M8... I will call this pattern B. Also during setup I copied over my internal storage files which I had backed up my laptop.
I then flashed the correct TWRP and then installed the correct SuperSU.zip. When I rebooted from here, Pattern B worked fine as I expected it to. I then thought I it would save time by restoring a nandroid (also 1.96.617.20) which had a lot of tweaks and other things. That nandroid backup however I know used my old screen pattern, which I will call Pattern A. That restore finished without error.
After reboot I got the restart screen asking for the pattern... I wasn't sure which one would work, so I first tried Pattern A which would have been used in the nandroid restore I just finished.... no luck. So I thought ok, I will try the pattern I used when I set up MM, Pattern B. But that didn't work...
This makes no sense... I have never used a screen unlock pattern other than Pattern A, and then today, I tried Pattern B which I know I remembered correctly because I used it once before I restored the nandroid.
When I search on how to solve this problem, I see "do a reset"... but wouldn't a reset be the same as restoring a nandroid backup? And since I just restored a nandroid and the pattern doesn't work, I am stumped.
Anyone have any clue how I can fix this???
Thanks in advance!
syntropic said:
Anyone have any clue how I can fix this???
Thanks in advance!
Click to expand...
Click to collapse
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!
syntropic said:
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!
Click to expand...
Click to collapse
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead
mirok said:
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead
Click to expand...
Click to collapse
I just googled "site:sea-developers.com pattern security not working HTC 10"
This wasn't strictly a TWRP issue... You could use TWRP or ADB to access the system partition IF the files which stored this security code were stored there (of this I wasn't entirely sure).
I didn't know for certain if these files were located in the same place or even under the same name as the Nexus, so I used TWRP's file manager to look around (starting in the above location) aa maybe I'd find them.
Sent from my HTC 10 using XDA Labs
Hey, i'm assuming that @Flippy498 is going to reply, because he is the god of these forums, but after helping me figure out how to flash roms the right way, I have been enjoying ViperOneM9 6.1.0 alot, but for some reason the stock navbar was broken after the flash, oh well, Viper comes with one that I particularly like, problem solved. I have no idea why I did this, but I installed an apk of paphonb's custom navbar, to demonstrate to a friend that android is quite obviously superior, in terms of customization, and I showed him, then went on with my day, I saw this cool feature (I don't remember what it was but i'm getting to that) in the paphonb Custom Navigation Bar app, so I turned it on just to see how it works... And everything hit the fan.... My phone popped up the dreaded "system.ui has stopped" and sent me back to the lock screen. But now when ever I swipe up to put in my pattern to unlock I can see the dots momentarily, then the phone black screens. When I press the power button again it brings me to the lock screen again.....
Then I opened an ADB shell, and using my knowledge acquired from you I ran the command "adb uninstall xyz.paphonb.systemuituner"
It suceeded
I then wiped the Cache, and Dalvik cache through TWRP, but the issue persisted.
I still get the black screen/crash when swiping up to unlock, which means that I must be able to fix the issue using ADB right? I don't really know what to do now, so so help would be much appreciated!!!
First of all, did you try dirty flashing your current rom (installing it without wiping any data)? If that doesn't fix the issue then you need to think about the following:
Are there any data you don't want to lose on that phone? If yes, try to boot to twrp, connect it with your PC and to copy everything that you need from the internal storage to your PC. If the PC doesn't recognize the phone directly you should try the mount menu in TWRP.
If there is no data you don't want to lose or if you already copied all you need you simply clean flash the rom (installing it with deleting all data on your phone).
Please be aware that there's a small chance that your issue isn't caused by the app that you used but by the infamous dead nand issue. If twrp starts throwing out a lot of mounting errors during any of the steps and if you face an error while trying to boot to download or recovery mode at the same time then the evidence is clear that the nand died.
Sent from my HTC One M9 using XDA Labs
Does anyone have the stock firmware for the XT1789-02 I flashed a rom from TWRP, didnt really care for it and attempted to restore a nandroid backup, now when the system boots it asks for a pin, which i enter but says that it is incorrect. The PIN works in TWRP to decrypt, but for some reason is not working at the lockscreen. Any help here would be much appreciated. Thanks
After a little more reading and a little less panicking (i just got the phone today) I found flashall and that has saved my behind.
Apologies, I posted while i was still freaking out.