Develop Bugs

What TWRP and SuperSU versions?

Hi all,
I'm on OpenBeta9 and have /data formatted with f2fs. Couldn't find a clear indication of what TWRP version (and SuperSU) is compatible with this setup.
Could you please assist?
Thanks

Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery

MrSkyFail said:
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
Click to expand...
Click to collapse
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks

andrea.ippo said:
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
Click to expand...
Click to collapse
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069

MrSkyFail said:
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
Click to expand...
Click to collapse
I found out that if you only flash OB9 from TWRP, even though you formatted your /data partition and is f2fs, if you don't flash SU before your first boot, your phone becomes encrypted and you will have TWRP pin issues.
The other issue I found was that if you flash OB9, then try flashing SU (I'm running SR5 right now), it doesn't want to boot. The only way I got it to work is after you flash OB9, Mount /system and delete a couple of google apps (for me, I deleted Calendar and gmail; you can download these after you boot up from playstore), then flash SU, then reboot, and profit.
So order of things for me:
1. Wipe (make sure /data is f2fs)
2. Flash OB9
3. Flash TWRP (modded 1-28)
4. Reboot to recovery (you may have to do a manual power off then volume down + power on)
5. Mount /system and delete calendar and gmail apps
6. Flash SU (SR5; I think there's a newer version but I haven't tried it with the new one).
7. Wipe Dalvik and Cache
8. Reboot System
If everything is done correctly, your phone will reboot twice.
You will have dm-verity and unlocked bootloader warning screens.
First boot takes about 3-5 min.

Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?

Stupifier said:
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Click to expand...
Click to collapse
You may only need to mount /system before you flash SU. I can't find the post at the moment but this was mentioned (delete a few apps) when OB8 first came around.
Only the /data partition has F2FS support on stock OB8 and OB9.

Trouble after CM Update

Hi, I updated this morning my CM 14.1 on my OnePlus3. No my phone isn't booting anymore. Even Recovery does not work. Only fastboot is available, but Bootloader-Version and Baseband-Version don't have any value. I allready tried flashing twrp again. Terminal on Computer says everything went fine, but I still can't boot in recovery...
Can anyone help me please?
Thanks allready.

Flash modified TWRP ( https://forum.xda-developers.com/devdb/project/dl/?id=21835 ) using fastboot.
Now you should be able to get into recovery.
Then when you're in recovery, flash a firmware package that's compatible with cm 14.1 ( https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628 ) . I was going to attach a link but I can't find which one is supposed to be used, so look around for that :L When I flashed CM I had to use something like 3.2.8 but that might've changed. Good luck and hope this helps
---------- Post added at 15:05 ---------- Previous post was at 15:02 ----------
Also if these steps don't work use the unbrick tool from ( https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ ) which has saved my ass few times. You'll probably need method two. Make sure to follow the instructions carefully especially if you don't want to lose data.

Fastboot showing no values for baseband and bootloader is quite normal on Oneplus 3, atleast its the same behavior on mine and some videos on youtube i saw.

cohaolain said:
Flash modified TWRP ( https://forum.xda-developers.com/devdb/project/dl/?id=21835 ) using fastboot.
Now you should be able to get into recovery.
Then when you're in recovery, flash a firmware package that's compatible with cm 14.1 ( https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628 ) . I was going to attach a link but I can't find which one is supposed to be used, so look around for that :L When I flashed CM I had to use something like 3.2.8 but that might've changed. Good luck and hope this helps
Also if these steps don't work use the unbrick tool from ( https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ ) which has saved my ass few times. You'll probably need method two. Make sure to follow the instructions carefully especially if you don't want to lose data.
Click to expand...
Click to collapse
Did it and was going back in Recovery. So I flashed lineageos, because of the end of CM, but everytime I boot, I get in recovery. Do I just need to add the firmware package? Thought it would work with a whole new System ...
---------- Post added at 15:05 ---------- Previous post was at 15:02 ----------
Or do I have to add the system partition in the mount setting in twrp?

GrayGhost93 said:
Did it and was going back in Recovery. So I flashed lineageos, because of the end of CM, but everytime I boot, I get in recovery. Do I just need to add the firmware package? Thought it would work with a whole new System ...
---------- Post added at 15:05 ---------- Previous post was at 15:02 ----------
Or do I have to add the system partition in the mount setting in twrp?
Click to expand...
Click to collapse
The mount setting won't make a difference. I dunno why you're getting into recovery..... It might be the firmware package. Ask around on your ROM's thread on here for which firmware package you should be using.

What to do when you face TWRP Error 7

Every rom threads is being filled with people asking what to do with error 7. Same questions and same answers over and over.
The solution is simple and straightforward as below:
- Make sure you have latest TWRP.
- Make sure you have the right firmware.
All above can be downloaded if you look at 1st page of each rom threads. If not, go to Lineage 15.1 thread and get it from there.
Even with correct TWRP and firmware, you may still get error 7. In that case,
- Unmount (uncheck) System in TWRP.
I guarantee that those three will fix error 7 issues, especially the last part.

how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.

error 7
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720

philourm2.0 said:
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720
Click to expand...
Click to collapse
Update your twrp.
Sent from my LEX727 using xda premium

mchlbenner said:
Update your twrp.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
I have the newest Trwp (3.2.1-0 by codeworkx), installed 20s firmware from linage thread unmounted /system and still get error 7 (e1001). When i try to install a nougat or marshmallow based rom it either says system cant be unmounted (eventhough i did before) or says it was succesful, but i'm not able to boot. When trying to restore a backup i also cannot boot. Just the Leeco splash screen shows till it goes into recovery.

ok but I have twrp 3.2.1.0

give a trwp 3.1 or 3.0 and try los14.1

philourm2.0 said:
give a trwp 3.1 or 3.0 and try los14.1
Click to expand...
Click to collapse
When flashing LOS14.1 in twrp 3.0.2 it gets stuck at somewhere like 90% (Patching system image unconditionally)

Are you guys getting this error?
If you do update your firmware.
Go get it from codeworkx
Sent from my LEX727 using xda premium

Thanks for your help
I installed twrp-3.2.1-0-20180407-codeworkx-zl1 and still this error 7
it's the line
assert (leeco.verify_modem ("2017-01-06 01:40:06") == "1");
which makes me wrong if I delete it in meta-inf ok
in the forum lost15.1 official on xda, they say firmwaire 20s minimun in red
I have never been in official 20s it would not be that?
or find udapte.zip 20s x720
I can try to put back original, put back 3.2.1 trwp and flash for test
thanks
Storm, you're stuck in any case if I understood
try on the site grossoshop leeco the pro 3
there is an automatic tutorial to put in 18s grossoshop
nothing to lose
then you try los 14.1 ok

Fixed it
I actually got this: "E1001: Failed to update system image." followed by Error 7.
So, i don't know how but it just fixed itself. My ADB Drivers suddenly didn't work correctly and after reinstalling clockworkmods Universal ADB Driver it worked out of nowhere. It could also have been a false USB Port scince i also plugged my cable in somewhere else. Now I can flash anything without problems
Hope this helps...

problem solved my turn
for those who have an error 7 with oreo which is a problem identification
you need the firmwaire 20s minimum if you start the custom rom with 18s or 19s
and the solution and in the tutorial aicp 13
so it's not necessarily the trwp that's always the problem
but thanks for the help

I was having the same error 7.
I just reflashed to stock 20s and the problem was fixed

Ferdinantstr said:
how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.
Click to expand...
Click to collapse
Same Here!!

millkyway4 said:
Same Here!![/QUOTE
Is this tread still alive?
Click to expand...
Click to collapse

I read through this post and couldn't get past the error 7 issue. I finally got it solved by updating TWRP to the latest version and then I could flash lineage15 via adb sideload. Thanks for another great, informative, thread from the people of XDA developers.

Stuck on ZUI

So i was on arrow os pie but I wanted to try zui 4.0 so I flashed it but when I tried to switch to aex pie latest build 3rd Nov it didn't boot after the boot logo it showed a blue screen and that's it it kept showing that blue screen and then kept rebooting so I tried to restore my twrp backup of arrow os pie but the results were same no blue screen but it kept rebooting so i flashed zui again and it booted ! Now I'm stuck here
Help please
Thx

Which version of trwp ur using....
Make sure the rom flashed correctly... just flash only rom
And give it a try again....
Before flashing make sure u clean cache, system,data and flash the Zui on twrp version 3.2 r greater version...
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------

LAKSHMI SAINATH said:
Which version of trwp ur using....
Make sure the rom flashed correctly... just flash only rom
And give it a try again....
Before flashing make sure u clean cache, system,data and flash the Zui on twrp version 3.2 r greater version...
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Click to expand...
Click to collapse
Thanks for replying but I figured the problem , the new aex build ships with a new kernel 4.4 which requires a new bootloader so you need to flash a newer zui through qfil and then flash the November build of aex 6.0 to avoid blue screen .
And about the restore problem : my backup was corrupted so it wasn't restoring correctly and hence not booting so I redownloaded the latest arrow os pie build and voila it booted .

samartht said:
Thanks for replying but I figured the problem , the new aex build ships with a new kernel 4.4 which requires a new bootloader so you need to flash a newer zui through qfil and then flash the November build of aex 6.0 to avoid blue screen .
And about the restore problem : my backup was corrupted so it wasn't restoring correctly and hence not booting so I redownloaded the latest arrow os pie build and voila it booted .
Click to expand...
Click to collapse
Suggestion - Abstain from using twrp backups.

Gauravism said:
Suggestion - Abstain from using twrp backups.
Click to expand...
Click to collapse
Especially for our device!

No data for MTK Device

Hi there guys!:fingers-crossed:
I've tried to install a couple of Project Treble roms, however it seems that all of them have the same issue, they don't connect to the mobile connection ( by Vodafone RO, if it's relevant in any way).
I've configured the APN and contacted the carrier and they took a shot at it as well, but to no avail.
I've also noticed that i can send messages however but I'm not receiving any.
The phone is a Umidigi One with MTK6763.
Thanks in advance!

CSI.ISC said:
Hi there guys!:fingers-crossed:
I've tried to install a couple of Project Treble roms, however it seems that all of them have the same issue, they don't connect to the mobile connection ( by Vodafone RO, if it's relevant in any way).
I've configured the APN and contacted the carrier and they took a shot at it as well, but to no avail.
I've also noticed that i can send messages however but I'm not receiving any.
The phone is a Umidigi One with MTK6763.
Thanks in advance!
Click to expand...
Click to collapse
Hey there! I am in the same boat. I have Poptel P60 which also has MT6763. All the symptoms match. Also tried a couple of rooms to no avail including 8.1 and 9.0 ones. Octopus ROM's recent change log mentioned something about Mtk RIL but also cannot get mobile data to work.
I'm noticing that after some time (and maybe some combination of reinserting sim and other things) I see some activity on the mobile connection indicator but still no working data. Double checked and tried different sets of APNs. Nothing
I'm hoping somebody has some suggestions... please let me know if you learn anything and I will, too. Manufacturers GUI is horrid and punishes you for rooting...
Maybe we could submit a bug ticket.

Does data work on any 8.1 treble ROM this phone will be worth it if I can get 9.0 data working but I'll settle for omni ROM or rr remix

No data, unable calls, incorrect network name (KDDI and SoftBank SIM)
Hello.
I'm facing this issue too.
I flashed many GSI ROM to Umidigi One (MT6763), SIM card detected but no data and unable calls.
Network state is always showing "No service - Emergency calls only".
I'm using KDDI SIM 4G VoLTE type.
When I'm using stock ROM, data and VoLTE calling are fully working after apn settings.:good:
I entered *#*#4636#*#* command network testing screen. in stock ROM, current network shown carrier name "KDDI" but I after flashed other ROM, it showing up weird number "44051". is this normally?
I tried friend's SoftBank SIM, it showing up correctly "SoftBank" but still no data and unable calls.
How can I make a mobile connection in other roms??
Sorry my poor English... I using Google Translate and post from Japan.
Thanks.

I am also facing this issue bro i have mt6739 chipset

I have mt6762 (helio p22)
Isee similar problem. Aosp 9.0 flashed and booted without any cell signal.
In order for my device to have working twrp, I needed to pay dm_verity. And I also removed forceencrtpt. I have read a comment that this encrypt change could be the cause of not connecting to cell signal.
I tested this a little. I flashed gsi with encryption still set to force. I was then able to have cell signal. But!!!!!!!!, There was many many apps and system force closeing.
Keyboard
Bluetooth
Settings,
Gallery
Camera
Etc , all repeated crash.

Can anyone tested gsi without encryption ?

facing the same issue here on mt6763 chipset. if i only flash the treble roms (i dont have twrp which mounts system and vendor so i only flash treble roms 9.0 versions via fastboot), after flashing call and mobile data including LTE works fine. I ported twrp for my phone with twrp porter windows app.. anytime i flash it... networks and data doesnt work anymore. i guess it is so because the twrp only boots to DECRYPTION UNSUCCESSFUL page so i cant use the phone with the twrp flashed... i have to restore stock recovery to boot pass the decrytion error page,, which ofcourse also encrypts the phone again. So now, i think the problem is my twrp, does anyone have a better working twrp for 6763 and 4.4.95+ kernel. Why does flashing twrp breaks the network connection??

puflynx said:
facing the same issue here on mt6763 chipset. if i only flash the treble roms (i dont have twrp which mounts system and vendor so i only flash treble roms 9.0 versions via fastboot), after flashing call and mobile data including LTE works fine. I ported twrp for my phone with twrp porter windows app.. anytime i flash it... networks and data doesnt work anymore. i guess it is so because the twrp only boots to DECRYPTION UNSUCCESSFUL page so i cant use the phone with the twrp flashed... i have to restore stock recovery to boot pass the decrytion error page,, which ofcourse also encrypts the phone again. So now, i think the problem is my twrp, does anyone have a better working twrp for 6763 and 4.4.95+ kernel. Why does flashing twrp breaks the network connection??
Click to expand...
Click to collapse
Just reboot to recovery mode when you see dycryption unsuccessful and perform normal factory reset and then reboot

chandan2000 said:
Just reboot to recovery mode when you see dycryption unsuccessful and perform normal factory reset and then reboot
Click to expand...
Click to collapse
it doesnt change anything. decryption unsuccessful still shows. i flashed the ported twrp on my stock an hour ago and realized sim cards dont work anymore. by the way, right after installing twrp i wipe data and install no verity opt encrypt zip but still. My boot and recovery images are all secured in the stock OS. could the secured img be the cause??

puflynx said:
it doesnt change anything. decryption unsuccessful still shows. i flashed the ported twrp on my stock an hour ago and realized sim cards dont work anymore. by the way, right after installing twrp i wipe data and install no verity opt encrypt zip but still. My boot and recovery images are all secured in the stock OS. could the secured img be the cause??
Click to expand...
Click to collapse
Flash this file after that reboot to recovery and format data and reboot if you see dycryption unsuccessful then reboot to recovery on the screen which you are perform normal factory reset

chandan2000 said:
Flash this file after that reboot to recovery and format data and reboot if you see dycryption unsuccessful then reboot to recovery on the screen which you are perform normal factory reset
Click to expand...
Click to collapse
Right but if i successfully get passed the decryption unsuccessful page...sim cards dont work on the phone anymore. does that mean any attempt to decrypt my stock boot/kernel/recovery brings up connectivity issues.?? thinking out loud. and how do i properly get rid of encryption from my stock rom?

puflynx said:
Right but if i successfully get passed the decryption unsuccessful page...sim cards dont work on the phone anymore. does that mean any attempt to decrypt my stock boot/kernel/recovery brings up connectivity issues.?? thinking out loud. and how do i properly get rid of encryption from my stock rom?
Click to expand...
Click to collapse
Flash this file while in recovery mode https://drive.google.com/file/d/1VCgNLByeUQRkX_amZg1u8eypQL3osd3C/view?usp=drivesdk and then format data also select rm-rf instead of formatting option in twrp setting

ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......

puflynx said:
ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......
Click to expand...
Click to collapse
First flash the file after that select rm-rf instead of formatting option in twrp then go to wipe section and format data then reboot after that if you seen decryption unsuccessful then shutdown your phone and reboot to twrp and do a normal factory reset
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
puflynx said:
ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......
Click to expand...
Click to collapse
R u rooted or not ?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
Use carlive image kitchen from pc and unpack twrp then edit fstab file

chandan2000 said:
First flash the file after that select rm-rf instead of formatting option in twrp then go to wipe section and format data then reboot after that if you seen decryption unsuccessful then shutdown your phone and reboot to twrp and do a normal factory reset
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
R u rooted or not ?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
Use carlive image kitchen from pc and unpack twrp then edit fstab file
Click to expand...
Click to collapse
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files

puflynx said:
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files
Click to expand...
Click to collapse
Send me your twrp recovery img file and also stock recovery img file bro i will try to help you
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
puflynx said:
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files
Click to expand...
Click to collapse
If you'r twrp not working properly you cant be able to decrypt your phone
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
You can also edit it yourself just go to ramdisk folder then etc you will find recovery.fstab file edit it according to your stock recovery img recovery.fstab file

chandan2000 said:
Send me your twrp recovery img file and also stock recovery img file bro i will try to help you
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
If you'r twrp not working properly you cant be able to decrypt your phone
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
You can also edit it yourself just go to ramdisk folder then etc you will find recovery.fstab file edit it according to your stock recovery img recovery.fstab file
Click to expand...
Click to collapse
i appreciate your help so very much but i would rather forward you the files, i believe you know best. however, i have also attached a picture fo files in stock rom... because i can also see ramdisk-recovery.img files in there as well
here is a personal link to the files.
https://drive.google.com/drive/folders/1Hdyh3ZtysayWl1qAHFHjgDzzoEJjVdMv?usp=sharing

Get the file bro
https://drive.google.com/file/d/1k2UhVhtFFIkv8eVrP-kI9_GrlQcpCC-S/view?usp=drivesdk

chandan2000 said:
Get the file bro
https://drive.google.com/file/d/1k2UhVhtFFIkv8eVrP-kI9_GrlQcpCC-S/view?usp=drivesdk
Click to expand...
Click to collapse
wow that was fast but i flash twrp,,,whether or not i swipe to allow modification,,, i flash the file (patch_uncryptable.zip), i select rm-rf instead of formatting, go to wipe, select format data, type yes and boom..... failed to mount /data (invalid argument) , unable to format to remove encryption, updating partition details........, failed to mount /data (invalid argument)..... done.
this is what happens bro