Database Users

Just got RMA, can't disable force encryption

Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?

kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.

murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .

kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/

murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?

found something on a N6 thread that says wipe user data and it should work .

kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?

kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.

murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .

kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.

martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.

CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?

I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app

So this just happened...

So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?

Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.

Kochoa940 said:
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Click to expand...
Click to collapse
Did you try to flash the OTA image or full factory image? I think there is a known problem with the latest build of Pure nexus where some people can't boot past the Google logo. If that's your issue there are workarounds. You should check the Pure nexus thread.

Try a full wipe(without internal) and restore your nandroid without the data partition and let me know how it went.

If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.

Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
Eric214 said:
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Click to expand...
Click to collapse
Ok I am gonna try and revert to 3.0.0 and restore the EFS and then the backup. Would that be the correct resolution?

Ok so I fixed it!!!!! Btw thank you guys for all your responses!!!
Even though my version of TWRP was 3.0.2-2 this still worked for me following these commands. I randomly found this page and said what the hell I have nothing to lose so I did it and it freakin' worked! anyways here's the link in case anyone else has this issue of not booting past google splash screen
http://www.droidorigin.com/warning-nexus-6p-users-twrp-3-0-2-1/
Again thanks to those who responded and tried to help!

No OS to boot

Help help help!!! I am having a strange issue since last night. Wanted to install the MIUI ROM and since I was earlier on nougat I thought I will do a clean install so installed the stock Marshmallow ROM freshly And installed the TWRP through ODIN and as usual after installing the TWRP, also flashed no decrypt thing and also did Format. Now it says there is no OS to boot. Flashed this ROM but still no luck. So basically when I do Format it's wiping out the OS as well and after that no matter what I flash its not booting up. Tried the whole process some 5 times with no luck. What on the earth could be possibly doing wrong? How is it wiping out the OS too when I do the Format? This is the first time it has happened to me. Any help is really appreciated!!!

Use Odin to flash stock rom and then start from scratch.

Did that 4 times now and the same damn thing is happening. Tried different versions of TWRP too but with no luck. This is so frutrating
finnmacool said:
Use Odin to flash stock rom and then start from scratch.
Click to expand...
Click to collapse

TWRP has nothing to do with Odin. Does Odin 'pass' when you flash stock? What files are you flashing with Odin?

The phone boots up when i flash the Stock ROM through Odin, but when i install the TWRP and then do the Format option, Its wiping the OS too. Very strange. And later it doesnt boot up irrespective of what ROM i flash. Tried it so manytimes and same thing is happening.
finnmacool said:
TWRP has nothing to do with Odin. Does Odin 'pass' when you flash stock? What files are you flashing with Odin?
Click to expand...
Click to collapse

Why are you wiping anything after twrp install?
---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------
If you are going to wipe anything, only dalvik and cache.

After installing the TWRP, the internal storage shows as 0mb until i format it completely. Hence have to Format.
finnmacool said:
Why are you wiping anything after twrp install?
---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------
If you are going to wipe anything, only dalvik and cache.
Click to expand...
Click to collapse

so, odin stock, reboot...it loads, right? Odin TWRP and reboot. Shouldn't be any wiping required that way
http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/

Well i dont know how you did it, but it clearly says in the tutorial that after installing the TWRP the phone needs to be formatted. And if i dont, then the TWRP wouldnt recognize my internal storage. Hence i have to format it completely. The strange thing is, i have done it in the past and it would never wipe the OS but for some reason its doung now.
finnmacool said:
so, odin stock, reboot...it loads, right? Odin TWRP and reboot. Shouldn't be any wiping required that way
Click to expand...
Click to collapse

Nowhere in that tutorial did it even mention the word 'format'

Well the problem at the moment is, if i dont wipe it completely after installing TWRP, the internal storage shows as 0 mb. Doesnt this happen to all? And the internal storage shows up only after i do a complete wipe. What could be possibly wrong? And is full wipe supposed to wipe the OS as well?
finnmacool said:
Nowhere in that tutorial did it even mention the word 'format'
Click to expand...
Click to collapse

Why don't you just install twrp and reboot to see what happens.

Let me give that a try. I am sure it reboots normally. But for installing a custom ROM i need to wipe it completely and thats when the OS is getting wiped too.
finnmacool said:
Why don't you just install twrp and reboot to see what happens.
Click to expand...
Click to collapse

Thats a totally different issue. To install a new rom, put it on your sd card, fully wipe device then install new rom. After you make a twrp backup of course.

Well thats when i am facing this issue. After installing the twrp i tried installing a custom ROM and it says cant mount storage. And when i wipe it completely and flash a ROM,it doesnt boot up. Have been flashing for years now, this had never happened. What i am not able to understand is, hows it wiping the OS too. Bluddy frutrating.
finnmacool said:
Thats a totally different issue. To install a new rom, put it on your sd card, fully wipe device then install new rom. After you make a twrp backup of course.
Click to expand...
Click to collapse

Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button. That should solve your problems.

Well now i have installed the twrp and it did boot normally, but again in TWRP the internal storage is showing as 0mb. And FORMAT DATA is what i have been doing each time and its formatting the OS too.
finnmacool said:
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button. That should solve your problems.
Click to expand...
Click to collapse

Read through this and see if you find a solution: https://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331

Thanks for the link, had seen it before. Dint help much either. Just flashed the Stock rom and i think i will stick to this s***
finnmacool said:
Read through this and see if you find a solution: https://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
Click to expand...
Click to collapse

TWRP restore still not working?

It has been months since op5 come out, and the problem is that when restoring data partition from backups will lead to bootloop on OOS.
Has there been any fix on that?(official or non-official)
p.s. I have searched before, none of the recovery works for stock OOS, due to forced file encryption on OOS.

timescaming said:
It has been months since op5 come out, and the problem is that when restoring data partition from backups will lead to bootloop on OOS.
Has there been any fix on that?(official or non-official)
p.s. I have searched before, none of the recovery works for stock OOS, due to forced file encryption on OOS.
Click to expand...
Click to collapse
Not just problems with OOS, custom ROM's give bootloop too

When you do a backup, you have to also backup the system image partition. That will make your backup around 8-10gb in size but then you can restore your data partition and not get a bootloop. I am on TWRP 3.1.1-1 cheeseburger TWRP. Make sure you're at least on that or the k2 version which I'm updating to soon.

Eric214 said:
When you do a backup, you have to also backup the system image partition. That will make your backup around 8-10gb in size but then you can restore your data partition and not get a bootloop. I am on TWRP 3.1.1-1 cheeseburger TWRP. Make sure you're at least on that or the k2 version which I'm updating to soon.
Click to expand...
Click to collapse
So you can confirm it works?
Does this apply to OxygenOS too or just custom ROMs?

Jonathanve said:
Not just problems with OOS, custom ROM's give bootloop too
Click to expand...
Click to collapse
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.

sjamie said:
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.
Click to expand...
Click to collapse
I've personally try to backup and restore stock oos with the k3 version, ended up with a boot loop. Never tried k2 though, to scared to try again.

timescaming said:
I've personally try to backup and restore stock oos with the k3 version, ended up with a boot loop. Never tried k2 though, to scared to try again.
Click to expand...
Click to collapse
Understood. LoL

Pwnycorn said:
So you can confirm it works?
Does this apply to OxygenOS too or just custom ROMs?
Click to expand...
Click to collapse
Yes, it's works. But k2 apparently doesn't need the system image for data restore so your backups will be smaller and faster obviously.
Also, I'm on stock oos with stock kernel 4.5.10
---------- Post added at 11:19 AM ---------- Previous post was at 11:09 AM ----------
sjamie said:
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.
Click to expand...
Click to collapse
I can't seem to find the k2 file anywhere. Do you mind posting a kind to it so I can download?

Here you go: https://www.androidfilehost.com/?fid=889764386195921506

lekiaM said:
Here you go: https://www.androidfilehost.com/?fid=889764386195921506
Click to expand...
Click to collapse
Awesome, thanks!

Eric214 said:
Also, I'm on stock oos with stock kernel 4.5.10
Click to expand...
Click to collapse
So it means k2 can perform restore on stock oos, gonna try again when I get home.
Did you decrypt your device, or remove screen lock on the device before backup? Or anything I should do before backup? Thanks.

timescaming said:
So it means k2 can perform restore on stock oos, gonna try again when I get home.
Did you decrypt your device, or remove screen lock on the device before backup? Or anything I should do before backup? Thanks.
Click to expand...
Click to collapse
I ALWAYS remove screen locks and fingerprints before a backup. I also never decrypt my phone's, not worth it in my opinion.

Im curious if anyone has tried this to flash in TWRP to remove password and pin.
https://drive.google.com/file/d/0B3gcDbDvV4MkSmNCcDdTcHpyanc/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs

Eric214 said:
I ALWAYS remove screen locks and fingerprints before a backup. I also never decrypt my phone's, not worth it in my opinion.
Click to expand...
Click to collapse
Thanks, I'll try later today.

[HELP] extracttarfork() process ended with error=255 - when i restore data via TWRP

Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version

I got the same problem... I did't find the solution. Can someone help ?

k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.

Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.

Try OrangeFox-R10.0_8-Stable-davinci recovery.

flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20

Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?

flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has

I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.