Related
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
update: cant root it, cant install official update through rsdlite, cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
wyklocnik said:
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
Click to expand...
Click to collapse
uncheck restore data Hard Reset - DROID 4 by MOTOROLA - Verizon Wireless Support
update: cant root it, cant install official update through rsdlite,
Click to expand...
Click to collapse
updates.zips are not installed with rsdlite, XML/firmware is install with rsd lite, but adroid version can not be downgraded
cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
Click to expand...
Click to collapse
what official site? use files from my page How to Use RSD Lite to flash a .XML Stock Rom (firmware)
thanks for taking interest
tried factory reset with options You mentioned unchecked, same thing as before.
i did use xml with rsdlite and zip through built in recovery.
tried to find this page i downloaded files but theres too much in yesterdays history, trying those from Your link now.
also tried to update rom ota, but of course theres an error. oh my droid runs 4.0.4, i havent mentioned it before.
also, found in the net schematics for factory cable, was thinking if its worth a shot this way:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable-4.html
Factory cable only allows you to power device with low battery/no battery
Sent from my Amazon OtterX using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------
Update zips only update specific system versions, you have to use correct one, and must be complete stock.
Sent from my Amazon OtterX using Tapatalk
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
phone needs to be in AP Fastboot mode when flashing with rsd lite.
verify md5 checksum for xml file before flashing.
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
wyklocnik said:
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
Click to expand...
Click to collapse
Factory/Fastboot cable only uses the alt power (4) pin to power device, there are several pre-made ones
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
Click to expand...
Click to collapse
try reformatting internal sd card, before wiping
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
wyklocnik said:
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
Click to expand...
Click to collapse
there are no official moto download sites, all moto firmware is pulled by people with special access, and reuploaded
try reformatting internal sd card, before wiping
Click to expand...
Click to collapse
is it any different than checking "erase internal storage" when reseting phone?
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
wyklocnik said:
is it any different than checking "erase internal storage" when reseting phone?
Click to expand...
Click to collapse
formatting is different than wiping data, in menu>settings>storage>unmount>format
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
Click to expand...
Click to collapse
did system version change?
same story after formating internal memory.
no changes whatsoever. same homescreen, same widgets/apps present. same system version.
and of course new error every 5 seconds. guess the phone is messed up good.
talk about luck. its second droid 4 i bought. first i bought over a month ago on auction site, it was new. i paid, guy never sent it.
now this one. its like a curse
formatting internal won't wipe, user data, but will wipe backup data.
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
wyklocnik said:
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
Click to expand...
Click to collapse
it happens sometimes
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
Click to expand...
Click to collapse
select wipe data, then select reboot
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
wyklocnik said:
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
Click to expand...
Click to collapse
which fastboot version? 0A.74 , 0A.77?
which xml file?
0A.74
cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml
looks like you have a failure to write data, don't think there is a fix.
could try my Unbrick Moto device with moto-fastboot.exe
but unlikely that it will work
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 .
For some reason my Galaxy S5 mini (SM-G800) Android 4.4.2 is locked and asking for the alternate password instead of my fingerprint. I already restarted it, took of the battery, but it always goes to the same locked screen on boot.
I also tried the Android Device Manager on my google account. I tried the Lock option, changing the password, but since the phone was already locked, it is not working. By the way, the phone WiFi is on.
I searched a lot and found no solution besides resetting my phone and loosing everything or voiding the warranty flashing some recovery room. The are a lot of photos and stuff that I don't want to loose! So the reset is still not an option.
It seams so stupid that I own the google account registered on the phone, I own the fingerprint to login and I know everything is inside the phone, but I cant login! Any simple email account have a forget password option! Why the fingerprint login does not come back!?? Stupid programmers!!
Some sites says that after about 20 incorrect passwords tries it would give me an option to logging using my google account, but I already tried a lot of password and the only thing that happens is a wait 30 seconds countdown ! Where is that google account recovery options? Is it missing on Android 4.4.2?
Is there any way I can backup my data without voiding warranty?
Bro there are no 4.0.4 version for this device. It coming up with 4.4.2 and 5.1.1 versions
viddamusic said:
Bro there are no 4.0.4 version for this device. It coming up with 4.4.2 and 5.1.1 versions
Click to expand...
Click to collapse
Sorry, Ive fixed the question...
I really thought I would get some help here. This forum have so many advanced Android users, but not a single answer. That is sad... :crying:
Boy jst do as i say n u will get ur stuff as well as the media also
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
Do as I say just open the recovery mode by pressing volume + menu plus power button when you will get there just see there is an option to backup ur stuff jst do the backup in sd card n thn reset ur phone so that it is unlocked once everything is set then again go to the recovery mode and then search for option they are available as restore data option select the option and your data will be in your phone again and u will b happy thn
abhishek2805 said:
Boy jst do as i say n u will get ur stuff as well as the media also
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
Do as I say just open the recovery mode by pressing volume + menu plus power button when you will get there just see there is an option to backup ur stuff jst do the backup in sd card n thn reset ur phone so that it is unlocked once everything is set then again go to the recovery mode and then search for option they are available as restore data option select the option and your data will be in your phone again and u will b happy thn
Click to expand...
Click to collapse
Thank you for the help, but all I can see is:
Android system recovery <3e> ....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Where is the backup option? :crying:
Is your phone rooted if yes do this reset your phone than download diskdigger app from play store n u will b able to restore your data again
No, it is not rooted. :/
Hey guys and gals,
just wanted to bump the OP. Same story here... In short: Only asks for alternate password, not for a print. Non-rooted phone...
I thought about the following (going on my S3 knowledge here... If S5mini is different please correct me):
I could flash twrp via Odin, boot directly into recovery and then (after backup) delete password.key under /data/system/
That would remove a pin/password lock for sure. But does someone know if that would also clear the alternate password to the fingerprint? Or is that stored elsewhere?
I'm pretty sure factory reset and restoring the backup would do jack because the fingerprint data and the alternate password must be stored in there.
Any ideas/knowledge are/is welcome except some mumbo jumbo restore app...
Alright people, who dares wins... I just tried to resolve this issue and it WORKED! :highfive:
Only downside: This will trip KNOX and void your warranty! But most people don't care, and so do I.
So for all who have this or a similar problem, here's what I did:
1) I took this TWRP version, flashed it via ODIN and removed the "auto reboot" option (this is to prevent the UNrooted system to overwrite the recovery again on boot)
2) The phone I had could not be booted to recovery directly from download mode (as can be done with my S3...), so I removed the battery, reinserted it and booted to TWRP via 3-button-combo
3) I renamed the following files via "TWRP->Advanced->File Manager" to make the system "unaware" of them (choose whatever renaming scheme you like):
/data/system/personalfingerprintpassword.key
/data/system/fingerprintpassword.key
4) I then rebooted to system normally and was greeted with the standard "swipe lockscreen". Done!
On a side note: I then went on to change the lockscreen method to PIN. In the settings it still said "fingerprint" as the current locking method. And when I tried to change that to PIN it asked for the fingerprint. So I swiped the finger - which was recognised - and I could ONLY THEN change the actual setting. So the actual fingerprint data must be stored somewhere else...
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.
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.