Develop Bugs

M8 Eye (MELS_TUHL) problem recovery, software corrupted

Hi Guys,
I need urgent help with this. My friend's phone suddenly won't turn on and shows "Encryption unsuccessful". Tried factory reset but shows error triangle, tried wipe cache and all but to no avail. As I have uploaded you can see below. Never rooted. I hope you guys will help because I'm at my wits end here since the phone have no custom rom if I rooted it. So no point. Please help me ASAP!
View attachment 3636256
View attachment 3636257

how well are you with adb? coz i need to know where to start from

MuminMohamed said:
how well are you with adb? coz i need to know where to start from
Click to expand...
Click to collapse
I'm good with it, simple coding would be great if you have a solution for this

download twrp from https://drive.google.com/file/d/0B3wzFG_FuEb3UzVKWHJSekZuQTQ/view?usp=sharing
install it via fastboot [fastboot flash recovery twrp-m8eye-2.8.0.3 (1).img] use the command inside the bracket, download this backup from http://1drv.ms/1WkbudN now for the back to work well i suggest that you create a backup of your cache on your sd card so that you can have the correct directories to copy the backup to, usually its TWRP/BACKUPS/YOUR SERIAL NUMBER/BACKUP FILES, if you wish to root flash supersu zip from chainfire,

MuminMohamed said:
download twrp from https://drive.google.com/file/d/0B3wzFG_FuEb3UzVKWHJSekZuQTQ/view?usp=sharing
install it via fastboot [fastboot flash recovery twrp-m8eye-2.8.0.3 (1).img] use the command inside the bracket, download this backup from http://1drv.ms/1WkbudN now for the back to work well i suggest that you create a backup of your cache on your sd card so that you can have the correct directories to copy the backup to, usually its TWRP/BACKUPS/YOUR SERIAL NUMBER/BACKUP FILES, if you wish to root flash supersu zip from chainfire,
Click to expand...
Click to collapse
Stop doing this when you don't read and you don't know what option that you offered. This is for India version .. won't work for him and not for his problem

ckpv5 said:
Stop doing this when you don't read and you don't know what option that you offered. This is for India version .. won't work for him and not for his problem
Click to expand...
Click to collapse
Is there any solution? Trying to find solution for this problem

HollowLeon said:
Is there any solution? Trying to find solution for this problem
Click to expand...
Click to collapse
If it still under warranty then send it in ... this usually means the data partition is corrupted.
If it is unlocked, formatting data partition in TWRP recovery will fix it but this is non-rooted stock device, so the best option is HTC service centre.

Best way to create and re-flash userdata image on latest N (ryu-nrd91n)

First of all, thanks so much to everyone for all the hard work creating and updating utilities for the Pixel C.
I have a rooted (but otherwise stock) Pixel C running the November update of Android 7/N (ryu-nrd91n) and am trying to:
1. Create an image of the userdata partition
2. Read/modify files
3. Re-flash the modified partition back to the Pixel C
So far I've been able to create a 24.8 GB image file using 'dd' but the file is unreadable, probably due to encryption.
I don't see any Developer Settings option to remove encryption or otherwise unencrypt the data partition.
What is the best approach?

jason_hanley said:
First of all, thanks so much to everyone for all the hard work creating and updating utilities for the Pixel C.
I have a rooted (but otherwise stock) Pixel C running the November update of Android 7/N (ryu-nrd91n) and am trying to:
1. Create an image of the userdata partition
2. Read/modify files
3. Re-flash the modified partition back to the Pixel C
So far I've been able to create a 24.8 GB image file using 'dd' but the file is unreadable, probably due to encryption.
I don't see any Developer Settings option to remove encryption or otherwise unencrypt the data partition.
What is the best approach?
Click to expand...
Click to collapse
Do you want to get rid of your encrypted data partition ?
- Format data (inside TWRP - and do not boot into system in between)
- Flash stock boot.img
- Install SuperSU.zip / or flash antother boot.img - with "encryptable" flag.
If you flash stock boot.img and boot into system your are encrypted again - automatically.
yes, "dd" will dump the complete partition including encryption ..
you may can "tar" the complete file system while decrypted .. similar to TWRP backup function.
Why do you want to "backup - modify - restore" at all ?
Why you don´t modify your files directly on data using root-explorer ?
Cheers

followmsi said:
Do you want to get rid of your encrypted data partition ?
- Format data (inside TWRP - and do not boot into system in between)
- Flash stock boot.img
- Install SuperSU.zip / or flash antother boot.img - with "encryptable" flag.
If you flash stock boot.img and boot into system your are encrypted again - automatically.
...
Why do you want to "backup - modify - restore" at all ?
Why you don´t modify your files directly on data using root-explorer ?
Click to expand...
Click to collapse
Thanks so much for the follow-up. The main goal is actually simply to be able to create images, and re-flash them reliably on a different Pixel C (replicating the exact system state). The modification step is simply to verify that it's working.
I was able to unencrypt /data using the method above -- Thanks, that's extremely helpful!
However, I'm still unable to mount/read the file produced by "dd if=/dev/block/mmcblk0p7"
Is there a better way you can recommend to make an image of the userdata partition?

How do you mount the unencrypted dd dump of data ?
mount -o loop dumped.data.img /mnt/data
As well you can untar all twrp backup files into one new data.img file.
Or tar the complete /data partition ... etc.
It's an ext4 partition ..
Of course, you can use the twrp backup files directly to restore on another pixel c device.
There is no modification needed at all.
Good luck!
Sent from my Nexus 10 using Tapatalk

That whole boot.img step.. is that why I always get stuck in a weird misplaced bootloop whenever I modify anything in TWRP? I just flash original boot.img in fastboot?

gnome9er said:
That whole boot.img step.. is that why I always get stuck in a weird misplaced bootloop whenever I modify anything in TWRP? I just flash original boot.img in fastboot?
Click to expand...
Click to collapse
The boot.img step to decrypt data ?
It's a one time task.
Once decrypted you always need to root after new boot.img flash.
If you don't root or don't use encryptable flag boot.img you will get encrypted.
Not really related to bootloops.
What are you changing when you are using TWRP ?

If I use backup then restore it loops. If I flash twrp it just boots to recovery. Now that i think about it i never did root this thing properly. Well i did with a toolkit but that doesnt count. I went beta then hated it lost root on restore then when i tried to do it again i kept running into bootloops. It says in the forums here that its common ans to just fastboot reboot but that dont work. I cant wait for the new nexus 7

gnome9er said:
If I use backup then restore it loops. If I flash twrp it just boots to recovery. Now that i think about it i never did root this thing properly. Well i did with a toolkit but that doesnt count. I went beta then hated it lost root on restore then when i tried to do it again i kept running into bootloops. It says in the forums here that its common ans to just fastboot reboot but that dont work. I cant wait for the new nexus 7
Click to expand...
Click to collapse
Depends what are you restoring
Do you backup / restore other partitions except the data partition ?
Pls don't
In general .. pls backup data partition only !
All other .img files should be taken freshly from image.
In systemless rooting world the su.img is placed on data.
You may have an older version inside your backup.
If you restore boot.img from backup, supersu ramdisk modifications will fail.
Flash what ever system.img, vendor.img and install twrp as recovery.
If you flash a boot.img, it should have stock ramdisk, to be able to let supersu.zip do the work for proper rooting.
At the same time the su.img on data will be refreshed too.
To summarize .. if you change something always install a fresh copy of your boot.img and run SuperSu.zip inside TWRP afterwards!
Hope this helps ..

followmsi said:
Depends what are you restoring
Do you backup / restore other partitions except the data partition ?
Pls don't
In general .. pls backup data partition only !
Click to expand...
Click to collapse
In this case, we're only looking to backup and restore the data partition.
Once we have the raw image created by dd, what would you say is the most reliable way to convert it to something that can be flashed by fastboot?
I've tried several different utilities to convert it to a "sparse image" but flashing it just erases data and doesn't copy anything from the image.

jason_hanley said:
In this case, we're only looking to backup and restore the data partition.
Once we have the raw image created by dd, what would you say is the most reliable way to convert it to something that can be flashed by fastboot?
I've tried several different utilities to convert it to a "sparse image" but flashing it just erases data and doesn't copy anything from the image.
Click to expand...
Click to collapse
Did you test img2simg as well ?
I use simg2img to convert the sparse to raw image, the other way around.
Or something like this below .. "s" defines sparse image.
make_ext4fs -s -l xxxxxxxx -a data data.img
Sorry, can't help you better now ..

followmsi said:
Did you test img2simg as well ?
Click to expand...
Click to collapse
Yes, unfortunately we've tried everything.
First we created the file data.dd using
Code:
dd if=/dev/block/mmcblk0p7
, which can be read as an ext4 image.
Then we tried using SparseConverter, ext2simg and img2simg to convert the raw image to a sparse image.
They all produce files of different lengths, and none of those files seem to flash successfully
They go through the flash process and report being successful, but the data isn't there.
Is there any way to debug this and figure out what's going wrong?

followmsi said:
Do you backup / restore other partitions except the data partition ?
Pls don't
In general .. pls backup data partition only !
Click to expand...
Click to collapse
Why should other partitions not be backed up? Is it not possible to flash the /data partition if you flash other partitions at the same time?

jason_hanley said:
Yes, unfortunately we've tried everything.
First we created the file data.dd using
Code:
dd if=/dev/block/mmcblk0p7
, which can be read as an ext4 image.
Then we tried using SparseConverter, ext2simg and img2simg to convert the raw image to a sparse image.
They all produce files of different lengths, and none of those files seem to flash successfully
They go through the flash process and report being successful, but the data isn't there.
Is there any way to debug this and figure out what's going wrong?
Click to expand...
Click to collapse
If you don´t get an error message from fastboot the sparse image seems to be valid.
How do you verify data partition after flashing ?
Are you able to mount and check ?
Also from recovery .. e.g. before you boot into system ?
For example on Nexus 7 flo there is still a userdata.img inside factory rom (6.0.1), but not for Pixel C anymore.
Maybe some permissions are required (file_contexts) - like on Nexus 7 flo too.
Sorry, no idea whats going wrong for you ..
---------- Post added at 12:49 PM ---------- Previous post was at 12:35 PM ----------
jogrimst said:
Why should other partitions not be backed up? Is it not possible to flash the /data partition if you flash other partitions at the same time?
Click to expand...
Click to collapse
You can backup all partitions you want .. but you should know the possible impact if you restore them.
And Yes - you can flash all partitions at the same time .. but normally you don´t flash data partition via fastboot - not on Pixel C.
In times of systemless rooting and monthly security releases there is no need for system.img backup anymore.
Unless you have special modifications inside your system.img.
If you were rooted before I recommend to use fresh boot.img and reinstall supersu.zip after change.
Just to prevent issues ...

followmsi said:
And Yes - you can flash all partitions at the same time .. but normally you don´t flash data partition via fastboot - not on Pixel C.
Click to expand...
Click to collapse
Why is userdata.img normally not flashed via fastboot on Pixel C?

jogrimst said:
Why is userdata.img normally not flashed via fastboot on Pixel C?
Click to expand...
Click to collapse
Because it will wipe your device.

cam30era said:
Because it will wipe your device.
Click to expand...
Click to collapse
Ok. Do you recommend creating a flashable ZIP file instead?

jogrimst said:
Ok. Do you recommend creating a flashable ZIP file instead?
Click to expand...
Click to collapse
Yep, pls use flashable zip for your purpose.

How to factory reset OP 3 with PC?

Hello,
it seems to be that sth went wrong today. I wanted to factory reset my OP3 but right now nothing is working.
The initial set up was the following:
Unlocked bootloader with TWRP installed. Oxygen OS + several custom ROMs installed
What I did:
I deleted the data from system partition since I thought that they Oxygen OS system data will be deleted.
Problem:
Right now I get a encryption hint without the possibiity to factory reset my OP3 since I don´t get access to the data partition in order to upload a Oxygen OS .zip on my OP 3 from my PC.
What can I do in oder to factory reset my OP3 with the help of my PC? I want to install the OnePlus 3 OxygenOS Open Beta 28.

Search mega unbrick guide method 2 and then flash the last OnePlus recovery and then flash OB28

I managed to flash the most current Oxygen OS on my OP3 by doing a factory reset within TWRP and flashing the Oxygen OS .zip and Magisk 4.5.
BUT after rebooting, the file system seems to be encrypted again in TWRP (even allowing explicitly file modifications!). This means that I am not able to flash another .zip.
How can I manage that the file system remains decrypted also in TWRP?

I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?

king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.

king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
Well, there is a way to decrypt the device, but you'll lose everything. Reboot do fastboot and connect to pc, then type from CMD "fastboot erase userdata" or "fastboot format userdata"

Puddi_Puddin said:
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.
Click to expand...
Click to collapse
Please send me a link to the thread. I can't find it.

king0r said:
Please send me a link to the thread. I can't find it.
Click to expand...
Click to collapse
http://lmgtfy.com/?iie=1&q=Bluspark+oneplus+3t
If you pay attention, it also explains how searching in the internet works. It's littery the first result if you google "Oneplus 3 Bluspark".

I was already using
twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img !!!
BUT nevertheless I don't have access to any file (e.g. .zip) even using the newest version of the Bluspark TWRP. Every directory is listed with 0 Bytes.
When accessing TWRP an Error message comes up but I can allow file modifications. But this doesn't help to get access to any file.

Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.

madsponge26 said:
Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.
Click to expand...
Click to collapse
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?

king0r said:
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?
Click to expand...
Click to collapse
Well, if you can't access your data with TWRP then you are ****ed any way.

I can only not access the data in Recovery! In OOS no peoblems at all!!
I don't understand why in Recovery nö data access is possible.

[SOLVED] TWRP doesn’t let browse /sdcard files

I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me

Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps

Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?

So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.

Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads

tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?

Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .

AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.

Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:

Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.

AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM

[Guide] How to Remove Device Encryption to Flash Custom ROMs

The Issue
The device does not allow to use the newly flashed Custom ROM as it is Encrypted thereby asking for Password every time the phone boots up and wiping Data Partition with a Custom Recovery also does not work.
The Solution
Step 1 - Type anything as Password when the device asks for it after booting up. Be Quick as the device will shut down if you don't type anything within a few seconds.
Step 2 - Check whether it says Decryption was successful but the data is corrupted and also instructs to do a factory reset by tapping the Reset button. If Yes then go to the next step as the subsequent steps will resolve the issue. If No then this guide can not help you.
Step 3 - Do not touch that Reset button and reboot the device to Recovery by long pressing the Power button and then pressing Power and Volume Down simultaneously and choosing to go to Recovery from the Fastboot/Bootloader Menu.
Step 4 - Now connect the phone to your PC and transfer everything from your internal storage (if you didn't do it before flashing the Custom ROM) using MTP as the next steps will wipe the internal storage. Eject your SD Card from the device.
Step 5 - Download the Platform Tools from the link : [url]https://drive.google.com/open?id=1LEcF5iAjRdno2_aPKv9DYdOYtviC5xB7[/URL] and after extracting the folder place it in the C drive.
Step 6 - Install Motorola Device Manager from the link : [url]https://drive.google.com/open?id=12k2joSx5G08oourGlYLdtLEdTuOC9CVb[/URL] on your PC.
Step 7 - Download the Stock Recovery from the link : [url]https://drive.google.com/file/d/1_gogMT_GgSvg6FKpe2q4Z51gh22ftUdt/view[/URL] and place it in the platform-tools folder.
Step 8 - Assuming that your phone is still connected to the PC go to the Fastboot/Bootloader menu on the device by using Reboot to Bootloader option from the Recovery.
Step 9 - Go to the platform-tools folder on the C drive of your PC and open a Command Prompt window there by holding Shift key while Right clicking on the mouse and choosing the option. Enter the command fastboot devices to ensure that your phone is connected to the PC.
Step 10 - Enter the command fastboot flash recovery recovery.img to flash the Stock Recovery on the phone.
Step 11 - Reboot the device and enter anything as Password when the device asks for it. Now tap the Reset button to do Factory Reset. The phone will reboot to Stock Recovery and ask you to perform Factory Reset. Choose Yes to proceed and it will take a few seconds to do so. Voila!!! Your phone is successfully Decrypted and now you can boot into the Custom ROM you flashed.
Step 12 - As the phone is already Decrypted there is no need to keep the Stock Recovery. You can flash the Custom Recovery of your choice by going to the proper website and following the instructions to flash it on your device.
N.B : It took me a couple of hours to figure out the solution to this issue when I faced it and I wrote this guide so that it will help people who face the same issue in future. A Thanks! is much appreciated .

I work with "format data" in twrp

kuzo said:
I work with "format data" in twrp
Click to expand...
Click to collapse
That didn't work in my case.
Otherwise it's the easiest way to do so.

I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally

kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
I did it at least four or five times and was unsuccessful.
The phone was only booting up normally with Stock ROM but always asked for Password if any custom ROM was flashed.
Then only I came up with the idea I posted here and was successful to remove the encryption.

data on the phone will not be deleted?

whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Step 7: ". . . the next steps will wipe the internal storage. Eject your SD Card from the device."
You should expect that data will be deleted.

whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Yes!
Step 10 will wipe the Internal Storage and the SD Card too if it is still in the device.
It's a safe practice to eject the SD Card before doing any operations.

Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.

io_gh0st said:
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
Click to expand...
Click to collapse
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted. Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted.
Click to expand...
Click to collapse
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
Wolfcity said:
Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.

io_gh0st said:
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
Click to expand...
Click to collapse
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Edit: Check screenshots in the next post
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Click to expand...
Click to collapse
Sorry, wrong screenshots.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?

io_gh0st said:
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
Click to expand...
Click to collapse
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?

io_gh0st said:
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
Click to expand...
Click to collapse
Exactly. Here's the latest one:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Sent from my Moto G5 Plus using XDA Labs

Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks

itcanbdone said:
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
Click to expand...
Click to collapse
@Zackptg5 seems to have changed his side a bit, here's the actual link:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Do I need to select "Format Data" under "Wipe" to decrypt it? On TWRP, I see Wipe -> Format Data. If yes, do I need to remove SD card that has my system backup and custom ROM? Thanks.
---------- Post added at 03:14 AM ---------- Previous post was at 03:02 AM ----------
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
Are you referring to the "Format Data" tab under "Wipe" (that is, Wipe -> Format Data next to Advanced Wipe)? If yes, do I need to take out a SD card where I have a backup and custom ROM? Thanks.