I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
hachamacha said:
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
Click to expand...
Click to collapse
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
cameljockey1 said:
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
Click to expand...
Click to collapse
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
hachamacha said:
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
Click to expand...
Click to collapse
Are you sure you had 3.5.3 the first time you did it?
c_86 said:
Are you sure you had 3.5.3 the first time you did it?
Click to expand...
Click to collapse
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
hachamacha said:
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
Click to expand...
Click to collapse
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
ghettopops said:
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
Click to expand...
Click to collapse
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
hachamacha said:
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
Click to expand...
Click to collapse
Yes page 9 or 10 OP gives me a link
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
This seems to happen when you've got the fingerprint method enabled with PIN or password for that matter.
My experience:
I update from Oxygen 4.1.6 to 4.1.7 with TWRP and something went wrong because the phone stuck in bootload for more then half hour.
I've reboot and it appeared 'Encryption Unsuccessful' and it locked my phone. I tried to go to TWRP and it required the password that was 'default_password' but after it not allowed me to mount data and it seemed that there weren't any data in my phone.
I couldn't wipe, format or install other rom because I received error like 'unable to mount X'.
I've solved downloading the Oxygen Recovery and with a USB OTG, flashing it on my phone (with 'mount image' in TWRP).
I rebooted in Oxygen Recovery and it also asked me the password. I've just pushed 'Forgot password' and it formatted my phone.
The phone rebooted without problems (and without any data :\)
Hope to be useful for someone else in my same situation
You can get back in, without loosing any Data.
Go to TWRP
Choose Advanced
Select Terminal
Type this commands:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
reboot
Use Android again
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
astralbee said:
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
Click to expand...
Click to collapse
Same problem on one of my 3Ts, the other is working with the Oreo based TWRP.
Oreo based Red Wolf Recovery is working: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/recovery-red-wolf-recovery-project-t3805416
These things are weird:
1. Why does one 3T work, but not the other 3T ?
2. Why does (Oreo based) Red Wolf Recovery work?
3. Why is OOS Beta 29 able to decrypt Data perfectly?
I assume it's a decryption related bug in Oreo based TWRP.
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
What exactly is it you're trying to do? What TWRP are you using? What ROM?
You sound surprised that you can't see your Storage when you haven't entered a Password to Decrypt? That is, after all, what it's supposed to do. What security have you set up on your phone? Did you have Boot time security?
With so little useful information to go on it's hard to help. I'd recommend trying Red Wolf Recovery in any case. It's magic at solving many issues.
Sorry lol what happen was I was updating to latest stable oos, and had standard encryption set up. I wipes caches, and flashed latest rom, then magisk and again twrp (which I should not have) and then my phone had a quick reset. From there it was locked with twrp, neither my pin or default_pw worked so I just formated my phone, after copying data and important things to PC. Everything is good now just had to waste my own time.
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
raeee1 said:
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
Click to expand...
Click to collapse
Not so. I removed the password and TWRP still asks for a password.
hachamacha said:
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
Click to expand...
Click to collapse
This did not work for me.
Related
I've encrypted my phone but I forgot to decrypt before flashing ROM. I flashed custom LSC in this forum and after boot it ask my encryption password. I type the correct password but it said it's failed.
I try to use PCodin with downloading mode to back to stock GB. When the phone boot it won't ask anything, I can use it normally, but when I flash JB again the encryption page is still keep asking for the password. When I boot into CWM (I use PhilZ kernel) it said failed to move "exfat /dev/block/mmcblk1p1 sdcard", I cannot even wipe my internal memoery.
I've tried to find an answer in this forum but I only found an answer for GNex. It about booting into fastboot mode but GNote cannot do this.
please help!!!
--------------------------------------------------------------------------------------------------------------------------------------------------
Edit Fixed!!
I've flashed my SGN to stock GB with ODIN (with PIT file and check Re-Partition). When I updated it to JB again it still asked for the password, but this times it has password failed count. When it reached 10 it's reset and my problem was fixed, the next boot didn't ask a password anymore.
(Note !! - the messsage in CWM "exfat /dev/block/mmcblk1p1 sdcard" it because I forgot I've removed my SDCard. CWM will said that when it's not found SDCard)
Bump. In the same boat. Praying we're not up shoot creak. I have the same phone I used to encrypt (till Friday when this phone gets exchanged for new one. Radio is dead and tech at sprint flashed it).
Card encrypted, irreplaceable files trapped inside
Card is still in the Same device that originally encrypted the card
Know the password
Flashed device before decryption possible
Scouring the web for way to retrieve files
It should also be interesting to note that zi can see "all" files on the card. I just can't open them. I see the movies, pictures, documents. They are all there. Their just scrambled up so I can't open them. Please help
EncryptedMemories said:
Bump. In the same boat. Praying we're not up shoot creak. I have the same phone I used to encrypt (till Friday when this phone gets exchanged for new one. Radio is dead and tech at sprint flashed it).
Card encrypted, irreplaceable files trapped inside
Card is still in the Same device that originally encrypted the card
Know the password
Flashed device before decryption possible
Scouring the web for way to retrieve files
It should also be interesting to note that zi can see "all" files on the card. I just can't open them. I see the movies, pictures, documents. They are all there. Their just scrambled up so I can't open them. Please help
Click to expand...
Click to collapse
My problem is I've encrypted my device and did factory reset wihout decrypted it.
But I think your problem is you've encrypted SDCard because you still can use your phone normally.
I think the solution is you need to restore the backup of the ROM you've used encryption (the backup, not the ROM).
Because only the ROM (backup file) that encrypted it can do a decryption.
There have been several similar cases.
The encryption file resides in the /EFS metadata.
If you search the N7000 threads there is a user that solved the problem
by changing the efs metadata. ask him for details.
Af
takato11000045 said:
My problem is I've encrypted my device and did factory reset wihout decrypted it.
But I think your problem is you've encrypted SDCard because you still can use your phone normally.
I think the solution is you need to restore the backup of the ROM you've used encryption (the backup, not the ROM).
Because only the ROM (backup file) that encrypted it can do a decryption.
Click to expand...
Click to collapse
What backup.
I don't even have a note. I have a GSII. I found this thread which was close to what I was going through.
Hi i am using samaung Galaxy Note GT-N7000, with stock rom. I encrypted my phone. It was working fine.
Now i have started decrypting it. I know the password and applied it. My phone also took it successfully and started the decryption process.
Its been nearly 2 hours since its decrypting. I didnt tocuh it. Just getting curious now, how much more time would it take to decrypt?
Battery was full and phone is plugged in wall charger for the past 2 + hours, so battery isn't any issue. I am just seeing samsung logo. Can anyone help me what should i do? How much time i should wait? Any feedback would be appreciated. Please help.
I have a problem.
When installling TW Roms (latest ones) I get "Enter password to use encrypted device storage" - and no matter what passwords I try - it doesn't go further.
When I clean install other roms, it works.
Any Idea?
Search function doesn't work on this site, maybe there are some others with similar problems, hopefully it is curable!
Hae you ever used encryption or exchange or vpn?
Sent from my GT-N7000 using xda premium
lio02 said:
I have a problem.
When installling TW Roms (latest ones) I get "Enter password to use encrypted device storage" - and no matter what passwords I try - it doesn't go further.
When I clean install other roms, it works.
Any Idea?
Search function doesn't work on this site, maybe there are some others with similar problems, hopefully it is curable!
Click to expand...
Click to collapse
Have you encrypted your phone in the past or perhaps its secondhand?
Try formatting your sdcard + flashing a different kernel using odin and try again..
After trying everything in a similar scenario, I input the wrong password about 15 times on a TW-based ROM - then everything was deleted and it was fine
giatros said:
After trying everything in a similar scenario, I input the wrong password about 15 times on a TW-based ROM - then everything was deleted and it was fine
Click to expand...
Click to collapse
I tried didn't work. Although mine is stock rom. ANy update on this OP
xaragen said:
I tried didn't work. Although mine is stock rom. ANy update on this OP
Click to expand...
Click to collapse
What happened when you did that?
giatros said:
What happened when you did that?
Click to expand...
Click to collapse
Nothing kept on saying try again.
I went into recovery (stock recovery) and did factory reset and wipe cache. Still the same screen.
xaragen said:
Nothing kept on saying try again.
I went into recovery (stock recovery) and did factory reset and wipe cache. Still the same screen.
Click to expand...
Click to collapse
Did you persist enough times? After some point there is a timer that you can't try for a couple of minutes and then a countdown...
giatros said:
Did you persist enough times? After some point there is a timer that you can't try for a couple of minutes and then a countdown...
Click to expand...
Click to collapse
after reboot I am still trying. Will update if it gives me anything other then try again.
I do not remember setting up any encryption. Though I did at some point used exchange but deleted that account after a while. So when I updated nothing was on it no passwords.
---------- Post added at 04:23 PM ---------- Previous post was at 03:54 PM ----------
Yeah no luck. I lost count as to how many time I tried again. It remained the same.
I can only suggest installing the xperia-sized ROM by AminX..... this is the one that let me reset.
Sent from my GT-N7000 using xda app-developers app
SOLVED.
Ok guys just a quick update. I haven't had time and forgot about this thread but here's what I did and I am posting here so that somebody in same situation could benefit. I created a note to self in past and found it.
"In case I ever get that annoying Encryption message.
Do the following:
1) For this method to work you must have access to SDcard or internal memory.
2) If you dont have access, make sure you have Superuser file on any type of Memory (internal or external).
(On the sidenote I will always keep that in internal as well as external card from now on.)
3) Fire up Odin - Install Clockwork Recovery in PDA - Do Not Check reset time.
4) START....
5) Install zip from sdcard... superuser
a) it will fail first time with error code 0.
b) do it again (dont worry about that).
6) Fire up odin again.
7) Rename the MD5 i717 file to TAR. (see NOTE)
8) PDA that ****.
9) START and wait....
10) PASS you're done. Thank PAST ME...!!!! "
NOTE : Now I think this will work for other devices than just I717. You must get a stock rom TAR for your device. Dont get the latest but the one before latest.
After booting is complete and the device no longer asks for passcode. Go into security settings of the device. Then Setup a password lock for your device. Make sure its password lock and is at-least 8 characters. NOTE DOWN THAT PASSWORD
REBOOT.
Device will ask for password to unclock, Enter it and then go to security settings again and disable password unlock it or simply set it to slide.
Make sure you have NOT enabled any device Administrators in security settings. Most commonly people with exchange accounts on phone have that.
After this you can flash the any ROM you intend to flash (On stock rom it will still appear.) and if that encryption screen comes up use the password you setup previously.
Again I cant guarantee this will work for individual devices but yeah It worked for me and my friends device (both i717). Its now a goto method to get rid of it.
xaragen said:
Ok guys just a quick update. I haven't had time and forgot about this thread but here's what I did and I am posting here so that somebody in same situation could benefit. I created a note to self in past and found it.
"In case I ever get that annoying Encryption message.
Do the following:
1) For this method to work you must have access to SDcard or internal memory.
2) If you dont have access, make sure you have Superuser file on any type of Memory (internal or external).
(On the sidenote I will always keep that in internal as well as external card from now on.)
3) Fire up Odin - Install Clockwork Recovery in PDA - Do Not Check reset time.
4) START....
5) Install zip from sdcard... superuser
a) it will fail first time with error code 0.
b) do it again (dont worry about that).
6) Fire up odin again.
7) Rename the MD5 i717 file to TAR. (see NOTE)
8) PDA that ****.
9) START and wait....
10) PASS you're done. Thank PAST ME...!!!! "
NOTE : Now I think this will work for other devices than just I717. You must get a stock rom TAR for your device. Dont get the latest but the one before latest.
After booting is complete and the device no longer asks for passcode. Go into security settings of the device. Then Setup a password lock for your device. Make sure its password lock and is at-least 8 characters. NOTE DOWN THAT PASSWORD
REBOOT.
Device will ask for password to unclock, Enter it and then go to security settings again and disable password unlock it or simply set it to slide.
Make sure you have NOT enabled any device Administrators in security settings. Most commonly people with exchange accounts on phone have that.
After this you can flash the any ROM you intend to flash (On stock rom it will still appear.) and if that encryption screen comes up use the password you setup previously.
Again I cant guarantee this will work for individual devices but yeah It worked for me and my friends device (both i717). Its now a goto method to get rid of it.
Click to expand...
Click to collapse
After trying this method for a few hours it turns out that I had to downgrade, only after that there was an override on the encryption password requirement. Just in case you don't mind reinstalling evrything.
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...
kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.
ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.
Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .
Hello. Sorry if this issue already exists and I'm being negligent, but I have an interesting issue with TWRP. Whenever I try to boot to recovery, the screen stays at the teamwin splashscreen for a short time as it should, but then the device reboots normally and never allows me into the recovery. I've tried reflashing numerous older versions of TWRP via "fastboot flash recovery..." but the reboot still occurs. Just before this started happening I tried doing an "adb push..'" and that resulted in a permission denied. So I remounted using "mount -o rw,remount,rw /system" and the push succeeded. I'm pretty sure that this is at fault because I was able to get into recovery one time after playing with the writable and read only forms of the aforementioned command and wiping the cache via fastboot. Any ideas?
try deleting it first, via fastboot, then reflash it.
simms22 said:
try deleting it first, via fastboot, then reflash it.
Click to expand...
Click to collapse
I ran "fastboot erase recovery", reflashed TWRP, and the reboot still occured at the splashscreen.
It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simple app to use. :good:
Maverick-DBZ- said:
It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simply app to use. :good:
Click to expand...
Click to collapse
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Yeah, enter your password.
Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
If you're still having problems, then just turn off pattern lock or use a regular numbered password. On the off chance what I said doesn't solve your problems, you can try one last thing.
Backup anything important on your phone before doing any of these steps below. Make sure lockscreen password is off. You can turn it back on once you've confirmed this worked.
1) Flash a modded stock boot image via Flashify, this will disable forced encryption.
2) Boot into bootloader and use fastboot format userdata
The command will wipe your phone to factory setting, so make sure you backed up! Flash a custom kernel after if you want.
Maverick-DBZ- said:
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
Click to expand...
Click to collapse
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?
danarama said:
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?
Click to expand...
Click to collapse
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789
Maverick-DBZ- said:
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789
Click to expand...
Click to collapse
Further, if he hasn't set a lock, there should be a default TWRP one somewhere in the thread.
My 4-digit password works just fine during normal use. But after upgrading to oxygenOS 5.0.1 (OTA) , I decided I wanted to revert back to nougat. So I load my backup in twrp and reboot, and it asks for my password rather than fingerprint to unlock screen because of reboot. And that's when my password is not recognized.
This is the only password Ive ever used for my phone so its definitely the right one. I can also see notifications and accept calls, it just won't unlock the screen. I also tried the default code for my simcard but even removing it doesnt make a difference.
Next, I restore my backup for 5.0.1. that I made prior to restoring nougat, and the same thing happens, password doesn't work. I had to do a factory reset to get my phone working again.
Still determined to get good old android 7 back, I install the original recovery as to upgrade from the oneplus website. And upon booting to recovery my password is once again not recognized.
I'm now back on twrp and have no problems with my passcode. But I think this is strange so maybe someone here has an idea about what's going on.
If you're restoring a backup, you have to remove gatekeeper.pattern (or password).key and locksettings.db, once removed it will work
I moved those files from data/system to data and it worked. Thank you very much!
I noticed this also removes the lock if you set it from another computer using the 'my devices' section of your google account. But it does not remove the lock notification, to do that you simply have to set a new password from your phone.
And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.
ast00 said:
And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.
Click to expand...
Click to collapse
AFAIK stock recovery allows only sideloading via adb
przemcio510 said:
AFAIK stock recovery allows only sideloading via adb
Click to expand...
Click to collapse
Not sure about Oneplus, but we have a Prestigio tablet here and I managed to delete an entire partition from the stock recovery. Wipe data didn't help a bootloop so I actually wiped it for good.
I hope other manufacturers aren't that foolish, but I'm not sure they know better.