Honeycomb password/ no recovery - Dell Streak 7

I restarted my streak 7 now its asking for a password I can't get to recovery or the bootloader. I have dj Steve's honeycomb rom installed. Any ideas?

jsc619 said:
I restarted my streak 7 now its asking for a password I can't get to recovery or the bootloader. I have dj Steve's honeycomb rom installed. Any ideas?
Click to expand...
Click to collapse
Did you just install honeystreak, or have you been using it for some times now?

If all else fails reflash from scratch by holding volume+ and volume-... then run steve's updater.
Sent from my MB860 using xda premium

I've been using it for for a while
Sent from my MB860 using XDA App

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

did you figure out the password for dell streak 7

IS there a passowrd

I dont think there is actually, frome research.. it seems like its similar to the encrytion password screen, but I think it is that upon first boot if HHoneycomb doesnt have some credetianls/etc. it is looking for it encrypts the device/boot partition. Vaguely what I remeber reading from a similar issue with the transformer I believe. A guy had similar issue but after 50 or so attempts it reset it self... was also able to get in after a low battery warning through emergency call I think..
really no explanation for it, but no I dont think there is a password, if there was it is likely encrypted anyhow deep somewhere..

I am having the same issue on my Dell Streak 7, after a factory reset it keeps asking for a password but I never had a password on it. I have gone through CWM and erased every single partition re installed, the stock 3.2 upgrade and every time it keeps asking for a password... Any suggestions?

nick2585 said:
I am having the same issue on my Dell Streak 7, after a factory reset it keeps asking for a password but I never had a password on it. I have gone through CWM and erased every single partition re installed, the stock 3.2 upgrade and every time it keeps asking for a password... Any suggestions?
Click to expand...
Click to collapse
Ditto. I'm having the EXACT SAME issue. Idk wtf this is but it shouldn't be a password anywhere on this machine. It's my wife's and she uses it for an e-reader at night. She has a new book and my ass is grass if we don't resolve this. How and why would Steve let a code be infiltrated on our devices? I've never heard of this and I'm not happy about this...not happy at all!!

I found out if you let the battery run down to 15% or less and the low battery message pops up, you can click Battery Use and get into the settings screen. I have tried enabling a password and entering that in but it still does not accept it. I also tried enabling a PIN but that did not work either. It does say my tablet is encrypted but I cannot change it. I am trying to figure out what I can do in there, if anything to fix this.

I'm having the same problem. After I did a factory reset when it restarted now its asking for a password. Has anyone found a fix for this?

The only fix that I have found is to nvflash back to 2.2.2 and then do everything again and flash honeycomb. That seems to work. That's the only solution I've found that works. But if you do a factory reset the problem will once again happen. Even if you do the factory reset from recovery. So make sure to not do a factory reset or you will get this problem again/

Poll to all those with the password issue: did you use CWM 4.0 and either restored a nandroid or fac resetted with CWM 4.0 right before the password issue happened?
I may know why
---------- Post added at 06:27 PM ---------- Previous post was at 05:51 PM ----------
The password screen seems to be the password to decrypt the /data partition.
HC supports encrypting /data to make it more secure.
CWM 4.0 incorrectly formats /data when trying to either: fac reset though CWM or nandroiding.
The rom is assuming that it's merely encrypted and is prompting to decrypt it, it cant tell the differences betweeen a corrupt partition and an encrypted one.
The solution:
If you are on a stock rom: reinstall the stock recovery and fac reset
If you are on Honeystreak R7 or newer: same as on a stock rom
If you are on Honeystreak R2-R6: Upgrade to R7 or a stock rom and fac reset
I will be posting a port of CWM5.0 soon with this bug fixed, it's still in the bugtesting stage.

I have CWM 4.0 and did a factory reset so, yes. Thank you for the info.

I have rooted DS 7 Wifi ver. with stock CWM 4.0.1.4. After factory restore Streak waiting for password.
Where can I find stock recovery? Flash use fastboot flash?

I have the password problem. I get in fastboot and it says Starting Fastboot but when I run adb the cpu doesnt see the device

You cant use adb while in fastboot mode, you can only use fastboot

TheManii said:
You cant use adb while in fastboot mode, you can only use fastboot
Click to expand...
Click to collapse
I just got this device. I'm in fastboot, I put the recovery img in the tools folder. When I run the command for devices, it's not showing. The path is correct

Is the driver installed correctly?

Related

Enter password to use encrypted device storage

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.

Help Encryption unsuccessful error

So to set the story i had came home and rooted jb via linux method. Then presumed to use bootstrap as a recovery. I installed it and it said success. Then i presumed to change the bootloader unknowing if it was locked. So i reboot and i am stuck at Encryption unsuccessful screen and the only option is to power off or reset. What do i do ive tried to reset but it doesnt work also i tried to do a hard reset via stock recovery this also didnt work im unsure where to go about this problem now. Please help Im panicing! From what ive researched i think its soft bricked. Also there appears to be a fix on House of Bionic but it isnt clear. Lastly, I believe the problem resides with bootstrap but im unsure its just a hunch. All options will be tried.
You can use fastboot -w to wipe it and start over but you can't use the Bootstrap recovery any longer with 4.1.2 as it causes the corruption you are seeing.

problem with factory reset

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

TWRP asking for password

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 .

Password doesn't always work.

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.

Categories

Resources