Database Users

Root problem I have never had before

Hello!
I flashed a a stock 4 part firmware on my 935F a few weeks before via ODIN. Now I tried to root again to flash a custom rom and for other reasons.
The OEM and USB things needed for root to work are locked in the settings.
I have often rooted my phone, I start ODIN then I choose the TWRP .tar file and after that I directly go to the recovery mode.
First of all while starting the phone with the volume up/power/home button pressed the red text on the top of the screen is missing.
Recovery starts and there is NOTHING in the SD folder. I tried it 5 times now and always the same. The phone tells me that there is no /data folder. There is no folder at all. If I try to restore my handy it doesn't work because the folder(s) is not mounted.
I really don't know what to do. It was never a problem to root the device. I tried to unlock the "AUTO START" option in Odin, too but there is no difference. I tried the TWRP 3.2.0-1 and 3.2.0-2 always the same result.
Has anyone confirmed something like this?
The problem is flashing the stock image again and again takes much time and more serious I don't want to stress my phone to much. Now I am on stock again.
How can flashing a TWRP recovery resulting in deleting anything on the data folder, more precise the complete data folder that there isn't anything to mount or install?
Any help welcome!!
Have a nice day,
lienot

Am I really the only one?
No one ever has faced a problem like me?
Come on, it worked always I am on stock and from today twrp deletes my device or makes it invisible?
Please help!
lienot

Did you flash the dm-verity force encryption disabler?

Yes.
But before I can flash anything the sdcard is completely gone and when I flash files from the external sd card there is nothing real flashable because the internal sd is empty and without /data it doesn't work.
I really do not know. I rooted many times.
Very strange.
If I plug my phone to the computer only the Ext SD Card gets recognized.
Have a nice day,
lienot

TWRP can't see your data partition because it's encrypted and TWRP doesn't support this. You need to format your data partition in TWRP (not wipe), you will lose all your data when you do this.

Thanks, but I know the rooting guides.
The problem is:
Now I am on stock. Not rooted
I flash twrp with odin.
If I let the phone start and put the three finger combination before the twrp starts, but before the twrp is coming the small text on the top ".... is ... enforcing" is missing. Then twrp comes and everything is normal but there is no internal sd, or it is empty.
Exactly the same happens if I click "no reboot" in odin and then go to recovery.
From the very beginning there is no folder. I flashed stock again and again. Always the same happens. I never had such problem before. And I call myself "rooting experienced".
Very strange.
Have a nice day
lienot

Lienot said:
Thanks, but I know the rooting guides.
The problem is:
Now I am on stock. Not rooted
I flash twrp with odin.
If I let the phone start and put the three finger combination before the twrp starts, but before the twrp is coming the small text on the top ".... is ... enforcing" is missing. Then twrp comes and everything is normal but there is no internal sd, or it is empty.
Exactly the same happens if I click "no reboot" in odin and then go to recovery.
From the very beginning there is no folder. I flashed stock again and again. Always the same happens. I never had such problem before. And I call myself "rooting experienced".
Very strange.
Have a nice day
lienot
Click to expand...
Click to collapse
There is no internal SD from TWRP because it's encrypted by default in stock, I explained this in the previous post. TWRP cannot see or mount an encrypted partition. You need to install and boot into TWRP, go to wipe, select Format Data and type the word yes. Reboot recovery and TWRP will then see your internal storage. You can then flash your custom rom. The obvious downside of this is that everything on internal storage will be lost so take what you need off it first.

Thanks.
Sorry I typed a 10 minute answer by phone. It's gone.
Anyway I try I inform
Thanks really much
Bye
lienot
I hate writing with a phone phone

Again
"COULD NOT MOUNT /DATA AND UNABLE TO FIND CRYPTO FOOTER"
"FAILED TO MOUNT /DATA (INVALID ARGUMENT)"
Sh... Nothing works again Stock install again and again and again...
This can not be true!!
Please help me
I went directly into twrp and tried to format only DATA the above text is what has happened...
It's not good... I am getting crazy.
CU
lienot

I AM THE BIGGEST IDIOT ON THIS PLANET!​
I choose DATA but not the data I could choose and type "yes"
Man . I am an idiot - I cannot believe it.
I am just installing and doing anything I have to. If it will work I will tell you. I can't believe the mistake I have done....
Thanks a lot
lienot

I cant believe it! 15 minutes, now I am rooted and back on KING ROM and everything works as good as it should.
Somewhere I have my apps stored on my PC. I will transfer them via Titanium...
Everything can be so easy. But why are there two ways to delete the DATA folder, one with "yes" and one to click.
I just was blind that I did not see it, but it is confusing anyway.
Great, a great way to end this evening.... Now I can watch TV and make my phone as it should be again :good:
Holy s...
I am happy now
CU
lienot

Create Stock Recovery.img from FTF File

Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!

tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.

So my only way is to flash via Flashtool without wipe?

tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.

fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.

realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?

So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?

tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.

XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.

tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)

Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.

realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!

tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.

Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.

realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!

Accidentally wiped system

So I was going to install xXx NoLimits rom and I went to wipe my storage as to not cause and errors or mess ups. I went to select cache and dalvik/art in advanced wipe and accidentally hit system and swiped to format. Now I'm here in twrp with nothing but the root directory.
I have already tried adb sideload to get OOS back on it. It completed but nothing shows up under sdcard or in any of the root folders. I also tried adb push to the sdcard and it spits out and error. I looked back at some old forum posts and they said to install the sdcard fix in twrp but how am I supposed to get in on the phone if sideload or push don't work?
EDIT: I do have backups of OOS but have no way to get them on the phone.

I can get stuff on the phone now with push and sideload but when I sideloaded the OOS zip and tried installing it, TWRP says its corrupt! Its goes up to about 40% in powershell but the bar on TWRP says 100% and it stops the sideload command from completing. after it "finishes" powershell says "Total xfer: 1.00x"

You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.

Eric214 said:
You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.
Click to expand...
Click to collapse
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.

Wiping system is no big deal. Just flash the rom zip file and you'll be good.

PwnedBySumo said:
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.
Click to expand...
Click to collapse
Or if OnePlus added sd card reader into phone...
This is a valid argument for it...

I had your own problem, I solved buying an OTG cable and then I flashed the rom.zip from TWRP.

A2017G V1.2 0B09 - Cannot install ROMs without Gapps

My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.

xectis said:
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
Click to expand...
Click to collapse
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?

Choose an username... said:
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Click to expand...
Click to collapse
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.

xectis said:
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
Click to expand...
Click to collapse
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center

Choose an username... said:
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Click to expand...
Click to collapse
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.

xectis said:
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
Click to expand...
Click to collapse
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547

xectis said:
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Click to expand...
Click to collapse
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev

Choose an username... said:
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Click to expand...
Click to collapse
I see. All clear now. You've been most helpful, thank you again.

[/QUOTE]
xectis said:
I see. All clear now. You've been most helpful, thank you again.
Click to expand...
Click to collapse
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.

Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.[/QUOTE]
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.

Choose an username... said:
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Click to expand...
Click to collapse
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.[/QUOTE]
I did everything you suggested but I still get the 'To start Android use your password'. No wories I'll go back to my old ROM. Thanks anyway.
***Update*** I made a mistake in formatting SYSTEM instead of DATA. Now it works fine installing the ROM's I mentioned. You are a champ!
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).

xectis said:
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways

Choose an username... said:
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Click to expand...
Click to collapse
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.

xectis said:
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
Click to expand...
Click to collapse
Use the zip anyways

Choose an username... said:
Use the zip anyways
Click to expand...
Click to collapse
Ok I'll give it a try.

Damaged File System - Need Fastboot Help

Unlocked Mediapad M3 wifi 713, damaged file system showing 0 storage, managed to get TWRP installed via fastboot, but TWRP is unable to change/repair any partition. I've tried to use "fastboot format:ext4 userdata" but I get the "remote: command not allowed" error.
Is there some way to use fastboot commands? Or some terminal command from TWRP?
thanks, jf

Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up

qlue4e said:
Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up
Click to expand...
Click to collapse
Not sure how things got corrupted, had installed Linage on it, but was not able to download files from any installed program. Reinstalled Linage and it blew up. Erecovery fails to download anything, don't know why. I followed the instructions here https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 to format all partitions, and still TWRP only sees 0 space, can't do anything with it..
In short - can't see how anything could screw it up more!

which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?

qlue4e said:
which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?
Click to expand...
Click to collapse
TWRP is 3.0.3-0 It is failing to mount /data (Invalid argument) nor can it mount any other partition.
Yes, was on stock nougat, then Linage oreo, then reinstalled Linage and got current state.
When I try to install zip from PC, it appears to be successful - but apparently is not.

can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115

qlue4e said:
can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115
Click to expand...
Click to collapse
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf

For gmail you must install the micro version of the gapps not the pico one after that it should work

qlue4e said:
For gmail you must install the micro version of the gapps not the pico one after that it should work
Click to expand...
Click to collapse
It's not working for Aquamail either. Also, can't download from the web, using Brave browser.

friedsonjm said:
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf
Click to expand...
Click to collapse
I'm having the same issue basically storage is off limits to my apps.

The developer of the Linux 15 ROM is aware of the issue, it's on the list to be fixed.