Database Users

Please help, possible bricked phone???

Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?

I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.

RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.

RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.

Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.

RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.

Stuck on Sony logo after TWRP has been run.

Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.

Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.

kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.

Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.

kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.

Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?

HELP! SM -G901F, TWRP can't find storage partition to mount

Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:

Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?

BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping

Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.

BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!

Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again

BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again

Any newer or best TWRP for X727?

It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
[Solved]
If this happens to your device and you happen to use the chinese screen flicker fest TWRP, just go on and flash the latest official TWRP for our device. And you're going to be able to see your internal storage again.
you can either flash it ADB or from your recovery, but I flashed mine through TWRP

drckml said:
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
Click to expand...
Click to collapse
Stop reading out of date articles, and use the latest Twrp here: https://twrp.me/leeco/leecolepro3.html
The Chinese bootloader issue is no longer an issue
* So to be clear about you issue you cannot boot to recovery.
* You do see you phone when you connect it to the computer...Right?
* BTW, I also have an X727
Your issue is most likely due to corruption and encryption
Backup whatever data you can and then use the All in One ( "AIT " ) tool to remove encryption ( NOTE: this is going to erase your data.
Next Using AIT install Twrp and magisk 17.1 or the easier way to resolve this may be to temporarily go back to stock.
Option 1
Try flashing the latest Twrp and magisk 17.1, using either ADB or AIT
After flashing boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, check boxes to keep Twrp installed
8. Boot to system go through setup.
Option 2
You could flash my Recovery which includes Twrp and Root. ( Instructions at Link Below)
Afterwards you will be able to update the Twrp, and Root, then Flash whatever you want.
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
https://forum.xda-developers.com/showpost.php?p=75021582
Option 3
Use All in One tool to restore my recovery, Flash a Stock Rom , or simply Flash TWRP/ROOT and then your Rom> Gapps> Magisk once again > Reboot to Recovery ( Check Boxes, for Twrp manager installation) Reboot to recovery > do not choose to make you drive read only! Clear Cache ( Not Dalvik) Reboot to system > Finished.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your storage
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Of course use ADB or AIT once the phone is restored but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. This way you can quickly make changes on the fly. I recommend buying at least 32GB usb 3.0 drive. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
Again , if you do not use an OTG drive. Just use ADB or AIT for flashing your files, the steps are same as with any other phone.
Finally, look past any typos, I don't have time to proofread after spending so much time on a single post.

Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.

drckml said:
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
Click to expand...
Click to collapse
That's great!
In the future
If you have an encryption issue again, and you have latest tarp and magisk.
Just format storage and reboot to recovery, then wipe and issue will be resolved.

After first boot /data mount is gone in TWRP

I've got a SM-G950F, and succesfully flashed TWRP on it.
Wiped /data, after that i flashed dm-verity and force encryption disabler, everything was ok until the first boot into the system.
It booted up, and immediately after that i turned off the phone and booted into TWRP, and for some reason it couldnt mount /data again.
The tutorial i have followed:
Thanks for the tutorial to: jesec
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
Before the 1st boot i even rooted the device, that remained after the first boot, but no /data mount.
After the 5th try, i gave up.
What could be the problem, or is this normal on this phone?

Are you using latest twrp version 3.2.3.2

I'm using 3.2.1.0

kristof889 said:
I'm using 3.2.1.0
Click to expand...
Click to collapse
Use latest twrp 3.2.3.2 should have data mount and quota issues fixed.
You can flash the .Img file through twrp or flash the .img.tar file with Odin.
After flashing reboot straight into twrp and repeat part 2 of the guide you quoted.
I would be interested to know also if in download mode if you have a line in there saying rmm state?
Twrp for s8 exynos
https://dl.twrp.me/dreamlte/

Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.

kristof889 said:
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
Click to expand...
Click to collapse
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.

I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
Click to expand...
Click to collapse
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.

kristof889 said:
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
Click to expand...
Click to collapse
When do the errors occur ie: during backup,restore,flashing something.
When first starting twrp did you swipe to allow modifications or did you leave it as read only.

You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.

kristof889 said:
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
Click to expand...
Click to collapse
Still sounds like you device is still encrypted.
Doing a factory reset with twrp should work to restore your phone or at worst you can re-flash your firmware.
If you can in twrp FORMAT data again and flash the no verity zip use version 6 zip file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I would be curious to know in twrp in the mount menu what options are ticked as well.

After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB

kristof889 said:
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
Click to expand...
Click to collapse
What Android version are you on?
When you flashed twrp it should have asked you whether or not to ' swipe to allow modifications ' did you swipe to allow or not.
In the mount menu of twrp I have ticked/checked data,cache,SD card the option at the bottom to allow read only I have ticked - this does not stop me from doing backups but does stop me from restoring (data mount error ) so you can leave it unticked.
I would.like to know your steps for twrp installation (not the one you quoted in first post) as I screwed up when I first tried.

I attached the software information bellow.
I have not swiped to allow for system modifications

First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system

kristof889 said:
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
Click to expand...
Click to collapse
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.

spawnlives said:
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
Click to expand...
Click to collapse
Thank you for your advice. I will try it in the following days and will post the result.

I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.

CoreyOS said:
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
Click to expand...
Click to collapse
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?

kristof889 said:
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
Click to expand...
Click to collapse
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.

CoreyOS said:
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
Click to expand...
Click to collapse
So on that rom i can use s health and all knox based apps like normal?
If yes, i will try it, it looks very nice