Related
Hi,
I installed Galaxian Soup 1.5.1 beta a week ago and all has been running fine. This morning the tab was blank like it had run out battery so I put it on charge and found it wasn't dead. Tried to reboot and it's just stuck at the "Samsung Galaxy Tab 8.9" screen. I was using it fine last night and haven't changed anything!
I've tried ODIN to restore Stock Recovery which said it passed and worked, but still the same problem. It has removed CWM though. When I try to do anything in Stock Recovery it complains about not being able to mount the /data directory.
Is there anything else I can try, do I need to use ODIN to flash a ROM again? If so, can you tell me which file to use as there are hundreds in the Galaxian Soup zip.
Thanks!
Flash stock rom with Odin. Unfortunately you also need to wipe data in stock recovery for this to work, so you will loose everything.
Thanks for the reply. Unfortunately this hasn't worked, it passes in Odin but then on the tablet it says E:failed to mount /data, and "your storage not prepared yet, please use UI for format and reboot actions.
Trying to factory reset fails.
Any other ideas?
OK, a bit more detail. I use ODIN to flash the stock rom found here - http://forum.xda-developers.com/showthread.php?t=1483168
It passes and goes into recovery but complains in red letters about not being able to mount /data, can't access /system/csc/XEU/system in yellow and can't mount /cache or a few other subdirectories.
I select wipe data which appears to work although it complains about make_extf4fs failing on /dev/block/mmcblk0p8. It then complains about not being able to mount /cache and other subdirectories again.
I then select reboot, it complains again about not being able to mount /data and /cache and switches off, not reboot. If I turn it on again I'm straight back to recovery.
Got to be something I'm missing here!
Any input appreciated.
It seems your partition tables are messed up, but i have no idea how this could happen if you didn't flash anything that could cause this, maybe a hardware problem?
There is a way to repartition the tables, you need a PIT file for this. I have not done this myself, so unfortunately i don't know much about it. Try to search for a PIT file, but make sure it's for your tab model, otherwise you can mess it up completely.
Many thanks - that fixed it! For future reference and for anyone searching this thread I found the pit file here - http://forum.xda-developers.com/showthread.php?t=1406137&page=9 and flashed it with ODIN together with the standard firmware I mentioned in the earlier post.
It's not all good news though. The tablet now keeps freezing. Even in recovery while I was trying a factory reset for the freezing. This leads me to believe it may be a hardware problem that caused the original brick and ongoing freezing issues. What do you think? Does it save a dump anywhere when it crashes?
Glad to see it worked. Maybe try to flash the stock rom again, now without the pit file. Also try factory reset in stock recovery. If you are still having problems, then im afraid its a hardware problem.
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Mbuxton said:
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Click to expand...
Click to collapse
I have been flashing different roms, kernels and recoveries on my tab for more then 200 times probably. And i have been using Galaxian-Soup AOSP ICS rom with molteys kernel for almost two months. Never had any problems (that i didnt create myself). Never used overclock, but havent heard of anyone who has had problems with it either.
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.
In short: Canceled Factory Reset, Now my SD card is not being detected properly and I am unable to format/mount it in recovery
Hey Everyone,
I've recently created quite a frustrating problem on my HTC Vivid that I'm unable to figure out. While attempting to go into CWM Recovery to check what version I have I accidentally selected Factory Reset from the bootloader. I quickly pulled the battery, as my back cover was off, within a second or two of this selection, and to my knowledge the phone was still on the bootloader screen and hadn't begun the process. After rebooting into my ROM and I attempted to install TWRP Recovery via Goo Manager in preparation for flashing a new ROM. After the download timer expired my Goo Manager crashed. Any attempt to install via Goo Manager since then is giving me this error, or it just hangs at the download web page. I suspect that this is because of the botched Factory Reset I mentioned earlier, and I'm worried I've somehow messed up the internal SD. My internal sd card is not detected by the camera app nor correctly seen in my file manager, in settings it is reported at the correct size, but apparently all my media has been deleted. I'm unable to format/mount ext sd or emmc in Recovery. My questions are: Has my sd card been corrupted, and If so, why did all my apps and user data remain? Secondly, how can I remedy this situation? I should mention that my phones data port is basically unusable, so I am unable to connect my device to a PC and use adb/fastboot.
My recovery is CWM 5.5.0.4 and my ROM is CM-10.2 | AOSP 4.3.1 Jellybean [KANG] [Oct-31] My phone is unlocked and S-OFF
Update: I tried to Factory Reset, thinking maybe what got me into this mess would get me out, but that option just takes me into recovery. This leaves me even more puzzled. I followed that up with a factory reset/davlik cache wipe from recovery but that hasn't done anything either. My conclusion thus far is that I need to somehow reformat my internal storage, is that possible without connecting my phone to a pc?
Thank you for any responses, and taking the time to read this.
I inadvertently hit the factory reset once from the boot loader and it did the reset in just a few seconds. It hosed my internal memory and unfortunately had to run the ruu to fix it. I know that is not what you want to hear if you can't connect it to a computer.
Sent from my Nexus 10 using Tapatalk
Seriously?
I have answered this question literally 100 times...
Please use the search feature...
Or at least scroll down and read thread titles...
And if your port is borked... Replace it
Sent from my Vivid 4G using Tapatalk
I did a forum search, I was unable to find a satisfactory answer so I started my own thread. (All were referring to using some method of connecting the phone to a PC)
If anyone is wondering, I solved my problem by simply doing a reset/data wipe via recovery and reflashing my ROM. During setup it prompted me to format my internal storage and now my phone is behaving as normal.
Mods feel free to lock and delete this thread.
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Corrupted /efs partition on GT-N7000 causing bootloop
PaoloUrsini said:
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Click to expand...
Click to collapse
Any help?
The only things I found on internet are two tools that assert to rebuild your EFS nv_data.bin file (RIFF box and Zx3 box), but I don't want to spend money because the /EFS get corrupted by itself, without any attempt to flash or modding or whatever else.
I think that reflashing kernel will not solve my problem, because (I think) the information are hardware related, and not software related. If needed, I am able to manually change the file reflecting the IMEI and S/N on my cell box, but I need a generic file and some references about positions...
Please guys help me... even if you have only bad news
Thanks in advance
Paolo
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
nokiamodeln91 said:
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
Click to expand...
Click to collapse
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
PaoloUrsini said:
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
Click to expand...
Click to collapse
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
ndmuni said:
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
Click to expand...
Click to collapse
Thank you ndmuni,
I don't understand very well what you did; consider that my phone is in bootloop, so I am not able to read an eventyually SMS, but I can accesso to file system with Aroma tool in PhilZ recoverty tool. Have I to create a special folder under root in my N7000? With what name?
Thank you in advance
Paolo
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.