Develop Bugs

[Q] Lost with a Galaxy W

Forgive me posting what has probably been asked hundreds of times but over the last 2 weeks I have read so much information that I have got myself completely lost and I need help. (hard to admit that but there it is)
I have a Galaxy W that came with Android Gingerbread
A While ago I decided to upgrade that to KitKat using instructions I found online. this involved firstly installing Cyanogen Mod on my phone and then copying the ROM? to my SD card, rebooting and installing.
This worked perfectly and I was running KitKat, the only issue being that the camera didn't work because the phone couldn't see the SD card... there seemed to be no fix for this so I decided to try and change the software to Jelly Bean.
This is where I came unstuck. I copied Jelly Bean to the SD card, and tried to follow the same procedure as I did with KitKat, no good, just kept getting error 7 messages.
Eventually I restored the handset back to Gingerbread, copied the Jelly Bean Rom over to the phone itself and then ran the upgrade again... still the error 7 message.
I now appear to be stuck on Gingerbread, with no way of modernising the handset..
Can anyone help, please don't give me links to read, the chances are I've read all of them and they just confuse me, I need someone kind enough to walk me through all this.
Thanks

derekmines said:
Forgive me posting what has probably been asked hundreds of times but over the last 2 weeks I have read so much information that I have got myself completely lost and I need help. (hard to admit that but there it is)
I have a Galaxy W that came with Android Gingerbread
A While ago I decided to upgrade that to KitKat using instructions I found online. this involved firstly installing Cyanogen Mod on my phone and then copying the ROM? to my SD card, rebooting and installing.
This worked perfectly and I was running KitKat, the only issue being that the camera didn't work because the phone couldn't see the SD card... there seemed to be no fix for this so I decided to try and change the software to Jelly Bean.
This is where I came unstuck. I copied Jelly Bean to the SD card, and tried to follow the same procedure as I did with KitKat, no good, just kept getting error 7 messages.
Eventually I restored the handset back to Gingerbread, copied the Jelly Bean Rom over to the phone itself and then ran the upgrade again... still the error 7 message.
I now appear to be stuck on Gingerbread, with no way of modernising the handset..
Can anyone help, please don't give me links to read, the chances are I've read all of them and they just confuse me, I need someone kind enough to walk me through all this.
Thanks
Click to expand...
Click to collapse
What kitkat ROM did you flash? Silly question, did you root your phone first?

dec0der said:
What kitkat ROM did you flash? Silly question, did you root your phone first?
Click to expand...
Click to collapse
Ok, so you're already losing me a little... if it helps, I used the following files:
CyanFox-2.0.2-20140101-UNOFFICIAL-ancora.zip
CyanFox-Gapps-2014-03-02.zip
I also installed Clockwork Mod (I think that's the rooting part?) but I can't remember which version and I don't know how to tell!

derekmines said:
Ok, so you're already losing me a little... if it helps, I used the following files:
CyanFox-2.0.2-20140101-UNOFFICIAL-ancora.zip
CyanFox-Gapps-2014-03-02.zip
I also installed Clockwork Mod (I think that's the rooting part?) but I can't remember which version and I don't know how to tell!
Click to expand...
Click to collapse
I'll assume you already have the latest CWM installed.
1- Install the stock CM11 and GAPPs by arco68 from here:
http://forum.xda-developers.com/showthread.php?t=2588495
2- After flashing CM11 and before rebooting, select the wipe data/factory reset option
** you might also want to format you SD card too to remove remnants of older ROMs.
This guarantees a clean install with minimal issues.

derekmines said:
Ok, so you're already losing me a little... if it helps, I used the following files:
CyanFox-2.0.2-20140101-UNOFFICIAL-ancora.zip
CyanFox-Gapps-2014-03-02.zip
I also installed Clockwork Mod (I think that's the rooting part?) but I can't remember which version and I don't know how to tell!
Click to expand...
Click to collapse
Okay, I'll make it more specific.
To check your CWM recovery version (same as booting manually), read HERE
If you want to install kitkat ROM, you need to have at least CWM version 6.0.4.5 and up installed on your phone (not really sure about the version but 6.0.4.5 will work ). But if you get status 7 error, flash this via CWM. CWM 6.0.5.0 flash-able.zip
If you want to use the latest CyanogenMod 11.0 (20140721), download the following and put them in your external sd-card:
cm-11-20140721-UNOFFICIAL-ancora.zip credits to @arco68
7-24_GApps_Minimal_4.4.4_signed.zip credits to @BaNkS
Then enter CWM and do the following strictly/ carefully: credits to @arsradu
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard0 (be careful NOT to format /sdcard1 (external_sd) by mistake)
install cm-11-20140721-UNOFFICIAL-ancora.zip (from the external sd)
install 7-24_GApps_Minimal_4.4.4_signed.zip (from the external sd)
reboot your phone
Done

dec0der said:
Okay, I'll make it more specific.
To check your CWM recovery version (same as booting manually), read HERE
If you want to install kitkat ROM, you need to have at least CWM version 6.0.4.5 and up installed on your phone (not really sure about the version but 6.0.4.5 will work ). But if you get status 7 error, flash this via CWM. CWM 6.0.5.0 flash-able.zip
If you want to use the latest CyanogenMod 11.0 (20140721), download the following and put them in your external sd-card:
cm-11-20140721-UNOFFICIAL-ancora.zip credits to @arco68
7-24_GApps_Minimal_4.4.4_signed.zip credits to @BaNkS
Then enter CWM and do the following strictly/ carefully: credits to @arsradu
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard0 (be careful NOT to format /sdcard1 (external_sd) by mistake)
install cm-11-20140721-UNOFFICIAL-ancora.zip (from the external sd)
install 7-24_GApps_Minimal_4.4.4_signed.zip (from the external sd)
reboot your phone
Done
Click to expand...
Click to collapse
OK, so I tried to follow step one of the first link in your post but the phone won't go into recovery mode, I press and hold the correct button combination but the screen just says RAMDUMP MODE - Cause: Force Upload
If I try and reboot normally I get the Samsung splash screen then nothing... help?!!

Scratch that Mr dec0der Sir... I'd like to buy you a virtual pint.
Your instructions have got me back up and running from what I thought was a bricked phone.... not only that but I have a new version of Android to play with.
Thanks so much.

[RECOVERY] [MULTILANGUAGE] TWRP for Huawei Mate 8 **UPDATE 5/22/16**

Here is TWRP for the Mate 8. You must have an unlocked bootloader to flash this. After you flash this then you can root by flashing SuperSU after booting into TWRP. When installing a ROM for the first time you must go into TWRP and go to Wipe, then Format Data and do a format or else your internal storage will not be recognized.
-------------EMUI 4.1-------------
TWRP 3.0.2 Black & Blue:
https://drive.google.com/file/d/0B5I_q70mNuR4bGhWZDkyVXZVbnc/view?usp=sharing
-------------EMUI 4.0-------------
TWRP 3.0.2 Black & Blue:
https://drive.google.com/file/d/0B5I_q70mNuR4aWphQ2w3QXBUcU0/view?usp=sharing
TWRP 2.8.7.0:
https://drive.google.com/file/d/0B5I_q70mNuR4U3NCSWpCdEUtMjg/view?usp=sharing
Changelogs:
4-05-16: Updated to TWRP 3.0.2 Multi Language and changed some colors. Now TWRP will tell you if your internal storage is encrypted.
4-06-16: Added dark TWRP. Bug: when installing a rom the progress bar doesn't show anything. Don't worry, it still works.
4-09-16: Progress bar partially working in the Black & Blue version
5-06-16: TWRP for EMUI 4.1. Multilanguage. You can now mount through TWRP and copy files from your computer to the phone. Default language set to English. Blue themed.
5-22-16: Added themed TWRP Black & Blue to the OP. Based off of the latest twrp.
**On first screen tap the right most button, second from the bottom (Settings) then tap on the globe icon at the top right and choose your language. Then it will stay in that language**
** When formatting data in TWRP after updating to B321 it will take about ten minutes. Let it finish**​

thx for posting this, much appreciated
one of the bugs ive found with the mate 8 version is that the screen brightness cant really be adjusted. at some point it goes pretty dark and then just stay that way. a bit annoying but u can still work properly with it btw, the twrp themes from xda work like a charm
Sent from my Huawei Mate 8 using Tapatalk

jbmc83 said:
thx for posting this, much appreciated
one of the bugs ive found with the mate 8 version is that the screen brightness cant really be adjusted. at some point it goes pretty dark and then just stay that way. a bit annoying but u can still work properly with it btw, the twrp themes from xda work like a charm
Sent from my Huawei Mate 8 using Tapatalk
Click to expand...
Click to collapse
On my Mate 8 in TWRP I cannot mount or backup data no matter what I try. Do you have the same issue? I think we need a better build of TWRP. I'm in the process of making a stock debloated ROM but the TWRP problems are driving me crazy. EDIT: Going to Wipe, Advanced Wipe and Format Data fixed the issue. Now I can install from the internal memory and my data partition is working in TWRP.

oh i thought that had smth to do with the data partition being encrypted. i had the same issue but once ive installed the decrypted boot.img i could properly access the data partition in twrp....weird huh?
Sent from my Huawei Mate 8 using Tapatalk

jbmc83 said:
oh i thought that had smth to do with the data partition being encrypted. i had the same issue but once ive installed the decrypted boot.img i could properly access the data partition in twrp....weird huh?
Sent from my Huawei Mate 8 using Tapatalk
Click to expand...
Click to collapse
Me too, but doing that seems to fix the problem any time TWRP doesn't see my Internal Storage. The brightness bug is an issue although not a major one. It seems that after you let the screen time out then turn it back on the brightness is a lot higher.

ha nice one, didnt notice that since i usually switch off the screen timeout option yeah, all in all its definitely in working condition! no major bugs one cant work out currently. and im sure itll get better in time
Sent from my Huawei Mate 8 using Tapatalk

Thx for TWRP but can someone explain me how to unlock the bootloader on my mate 8?

use the tool dc unlocker in order to read out the bootloader code for your specific device. ull need to pay 4€ to use that function, everything else is explained in detail on the website and in the tool itself for huawei phones.
Sent from my Huawei Mate 8 using Tapatalk

@ajsmsg78 This recovery have a lot of problem in fstab partition just because chinese team used omni 5.1 sources. In my tool there is a new recovery with omni 6.0 and multilanguage

acer73 said:
@ajsmsg78 This recovery have a lot of problem in fstab partition just because chinese team used omni 5.1 sources. In my tool there is a new recovery with omni 6.0 and multilanguage
Click to expand...
Click to collapse
OK, thanks, I'll check it out

ajsmsg78 said:
OK, thanks, I'll check it out
Click to expand...
Click to collapse
No problem. I hope that you can port also in this recovery your good stuff :good:

acer73 said:
No problem. I hope that you can port also in this recovery your good stuff :good:
Click to expand...
Click to collapse
I was gonna ask you.... Thanks.... I'll do that tonight.

Hi guys
I flashed this twrp with fastboot. But it doesn't work, it can't mount anything and the phone now stuck at the Huawei logo. What can i do to solve this issue?
N910C ~ eRobot 11.1 ~ GoogyMax 2.0

dlorean said:
Hi guys
I flashed this twrp with fastboot. But it doesn't work, it can't mount anything and the phone now stuck at the Huawei logo. What can i do to solve this issue?
N910C ~ eRobot 11.1 ~ GoogyMax 2.0
Click to expand...
Click to collapse
Format data in TWRP...

Ok, i will try it when I'm back at home. But will it work, when the twrp can't mount anything? I tried to wipe dalvik and cache, fix permission nothing worked. Mounting didn't work too. Get only red text that isn't possible. It's my first Huawei device, have it since Saturday and now this problem
N910C ~ eRobot 11.1 ~ GoogyMax 2.0

i had the same problem initially. u have to flash a decrypted boot image first, then mounting is possible and the bootloop is resolved
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

Where can i find the decrypted boot image, so many questions starting from scratch with Huawei, is other than samsung.
Edit: ok, read in another thread where to get the decrypted boot image.
N910C ~ eRobot 11.1 ~ GoogyMax 2.0

I'm working on a custom ROM for the Mate 8 with the Google Apps installed, decrypted boot and rooted. I'm just trying to fix a few bugs. If I can fix them a Simply Google release will be near.

dlorean said:
Ok, i will try it when I'm back at home. But will it work, when the twrp can't mount anything? I tried to wipe dalvik and cache, fix permission nothing worked. Mounting didn't work too. Get only red text that isn't possible. It's my first Huawei device, have it since Saturday and now this problem
N910C ~ eRobot 11.1 ~ GoogyMax 2.0
Click to expand...
Click to collapse
Back up your internal storage to your computer and try this. In TWRP go to wipe, then Advanced Wipe and Format Data. Type in Yes. Tell me if after you do that if TWRP sees the Internal Storage properly. No matter what I did TWRP would not see my internal storage until I did that.

ajsmsg78 said:
I'm working on a custom ROM for the Mate 8 with the Google Apps installed, decrypted boot and rooted. I'm just trying to fix a few bugs. If I can fix them a Simply Google release will be near.
Click to expand...
Click to collapse
nice! which rom is this gonna be based on? any stock or aosp compiled? looking forward to that thx for your contribution, much appreciated!
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

[Need urgent help] Multiple issues on my Oneplus 3

I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.

I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.

For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!

Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check

I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.

mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm

Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.

I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.

Oppo Find 7a lineage OS Android 7.1.2 unified storage

Hi all!
Some one know if Lineage OS Android 7.1.2 for Find 7a support LVM or unified storage? If not, how can get it?
Many thanks!

From what i know lvm us not supported. It may support chinese unified partition. But i never tried. If u r looking for stable daily driver with unified, use omni. It is awesome.
Sent from my Redmi Note 3 using Tapatalk

Omni support Android 7.1.2? Do you have the link?
Thanks

Look in xda itself. Thread is under find7. But rom supports both find7 and fnd7a.
Yes latest android version of rom is 7.1.2. I have installed it on my find7a. Running great since quite some time now.
Sent from my Redmi Note 3 using Tapatalk

If I install omnirom 7.2.1,do I Need to install lvm patch? Can you tell me the exact procedure?

Use the unify storage option in coloros. Then install omni. This way lvm patch is not needed. To unify use coloros 2.1.x preferably.
What rom do u have now?
Sent from my Redmi Note 3 using Tapatalk

I have lineage. Could you tell me the procedure step by step?

1. Copy coloros rom to ur internal stirage or sd card.
2. Get into fastboot mode
3. Flash coloros kitkat recovery. You should find the link in oppo forums under download section for find7.
4. Reboot into recovery and Flash coloros
5. Boot into coloros and unify storage. Hope u can find ur way around coloros to do this.
6. Then flash latest twrp recovery
7. Finally flash omni.
I am assuming ur device is not modified to use chinese storage format or any other format. If yes, then additional steps or different procedure may be needed.
Sent from my Redmi Note 3 using Tapatalk

Thanks! The most difficult point is no. 5..how to install unified storage? That's not so clear for me..
And then, after flash omnirom, unified storage will keep the same?

Once you boot into coloros you have the option. You gave to under settings and further down. Play with coloros settings and you will find it. It will show what ur current storage format is and what can be done.
There is no install needed once u r in coloros. If u choose to unify it will ask u to confirm, then it will boot into recovery an run the necessary scripts to unify and reboot back.
Sent from my Redmi Note 3 using Tapatalk

DroidSK said:
Once you boot into coloros you have the option. You gave to under settings and further down. Play with coloros settings and you will find it. It will show what ur current storage format is and what can be done.
There is no install needed once u r in coloros. If u choose to unify it will ask u to confirm, then it will boot into recovery an run the necessary scripts to unify and reboot back.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
ok done it! now I have unified internal storage (14,68 GB)
I have tried to add new mp3 ringtones but I'm not able. Seem it cannot recognize it! COuld you help me please? Thanks!

kirkal01 said:
ok done it! now I have unified internal storage (14,68 GB)
I have tried to add new mp3 ringtones but I'm not able. Seem it cannot recognize it! COuld you help me please? Thanks!
Click to expand...
Click to collapse
Are u on omni now? Or still in coloros? Coloros may not support mp3 ringtones.
Add a ogg file and see if is recognized. Mp3 on Omni definitely works.
Sent from my Redmi Note 3 using Tapatalk

kirkal01 said:
Some one know if Lineage OS Android 7.1.2 for Find 7a support LVM or unified storage? If not, how can get it?
Click to expand...
Click to collapse
LVM is not supported. I tried the latest nightly with chinese unified partition layout. It will install and boot up, but many apps (e.g. gallery, file manager, camera etc.) have problems because there is no "internal SD card" any more.
Not sure if the coldbird unified layout works though, anybody tried?

I'm using the LineageOS with Chinese unification and no issues at all. Just after each LineageOS update you need to apply patch. There was a guide on OPPO forums, which are unfortunately down, but I hope it can be found somewhere else. For start use the thread with LineageOS here on XDA.

Got it working. :good:
Official LineageOS 14.1 with unified partition layout, running smooth and without problems so far after 3 days of usage. Now this finally is the device Oppo should have shipped right from the beginning.
In case anybody is struggeling to collect the information how to do it (like me): The guide in this post is still valid and contains everything you need. In a nutshell, you have to perform the following steps:
- Download and run the tool linked in the post above. This will wipe your phone completely and install a beta of ColorOS with unified partition layout.
- Put your phone into fastboot mode and install the modded TWRP recovery with unified storage support.
- Boot into TWRP recovery, wipe data, system and cache and install LineageOS 14.1. Add OpenGapps and root addon if you like.
- Install "CM13.0 Unified parttion Patch". It still works with LineageOS. After every update of LineageOS, you will have to install this patch again.
- Boot LineageOS and check if you can access your internal storage mounted on /storage/emulated/0. If not, wipe useradata in TWRP (worked for me).
Thanks to everyone who made this possible. :highfive:

I can't unified storage, my oppo model is x9076, ant doesn't work with the tutorial
Nexonian said:
Got it working. :good:
Official LineageOS 14.1 with unified partition layout, running smooth and without problems so far after 3 days of usage. Now this finally is the device Oppo should have shipped right from the beginning.
In case anybody is struggeling to collect the information how to do it (like me): The guide in this post is still valid and contains everything you need. In a nutshell, you have to perform the following steps:
- Download and run the tool linked in the post above. This will wipe your phone completely and install a beta of ColorOS with unified partition layout.
- Put your phone into fastboot mode and install the modded TWRP recovery with unified storage support.
- Boot into TWRP recovery, wipe data, system and cache and install LineageOS 14.1. Add OpenGapps and root addon if you like.
- Install "CM13.0 Unified parttion Patch". It still works with LineageOS. After every update of LineageOS, you will have to install this patch again.
- Boot LineageOS and check if you can access your internal storage mounted on /storage/emulated/0. If not, wipe useradata in TWRP (worked for me).
Thanks to everyone who made this possible. :highfive:
Click to expand...
Click to collapse
My Oppo find is X9076 version
in the tutorial only have a option for download (x9077) I try with this, but i can't do
I do the rest of steps and I unified the storage, but... in the system looks 26.5 gb used for 29gb, 26.5gbo only used in system
Help me please

Hazelito said:
My Oppo find is X9076 version
in the tutorial only have a option for download (x9077) I try with this, but i can't do
I do the rest of steps and I unified the storage, but... in the system looks 26.5 gb used for 29gb, 26.5gbo only used in system
Help me please
Click to expand...
Click to collapse
Same issue... Have you found a way ?

Thank you!!
Nexonian said:
Got it working. :good:
Official LineageOS 14.1 with unified partition layout, running smooth and without problems so far after 3 days of usage. Now this finally is the device Oppo should have shipped right from the beginning.
In case anybody is struggeling to collect the information how to do it (like me): The guide in this post is still valid and contains everything you need. In a nutshell, you have to perform the following steps:
- Download and run the tool linked in the post above. This will wipe your phone completely and install a beta of ColorOS with unified partition layout.
- Put your phone into fastboot mode and install the modded TWRP recovery with unified storage support.
- Boot into TWRP recovery, wipe data, system and cache and install LineageOS 14.1. Add OpenGapps and root addon if you like.
- Install "CM13.0 Unified parttion Patch". It still works with LineageOS. After every update of LineageOS, you will have to install this patch again.
- Boot LineageOS and check if you can access your internal storage mounted on /storage/emulated/0. If not, wipe useradata in TWRP (worked for me).
Thanks to everyone who made this possible. :highfive:
Click to expand...
Click to collapse
Thank you so much!! I will try this, after 2 long weeks searching on the internet to resolve the internal storage issue!

Find791 said:
Thank you so much!! I will try this, after 2 long weeks searching on the internet to resolve the internal storage issue!
Click to expand...
Click to collapse
Holy sh*t it worked for me too xD

my though
Hazelito said:
My Oppo find is X9076 version
in the tutorial only have a option for download (x9077) I try with this, but i can't do
I do the rest of steps and I unified the storage, but... in the system looks 26.5 gb used for 29gb, 26.5gbo only used in system
Help me please
Click to expand...
Click to collapse
By the way i think the difference between X9076 and X9077 is only about software, the internal hardware is identical. But, i agree with you better be safe not to install X9077 ROM on X9076.
I think the first key in step by step guide by
Nexonian said:
...
Click to expand...
Click to collapse
is you must first installed ColorOS with Unified Storage support. And it is also possible for X9076.
My friend's X9076 already manually update to latest ColorOS and enable it's built-in unified storage feature. I don't remember what ColorOS version he has, but if i look in the following thread, it is ColorOS 2.1.5i. Link: https://forum.xda-developers.com/find-7/general/oppo-7-x9006-x9007-x9076-x9077-stock-t3671678
So, try to update to latest ColorOS manually. Better update it through Oppo stock recovery and wipe everything beforehand to be clean.
The remaining problem for me is do the X9076 need to be converted to Unified Storage before flashing LOS or no? Based on a post by DemonDroid_97 the answer is yes. Link: https://forum.xda-developers.com/showpost.php?p=71752026&postcount=2. and then simply do:
(Have a Unified Storage through ColorOS 2.1.5.i)
Flash latest TWRP (no need TWRPmod?)
nandroid backup (optional)
Wipe everything
Flash the LOS ROM. done!
I think it is safe to try it. If it failed, then do:
Flash TWRPmod by Wuxianlin https://cloud.mail.ru/public/LJQE/VaPJxmPt8
Wipe everything
Flash LOS
Flash the "CM13.0 Unified parttion Patch"
The last step is as written by
Nexonian said:
Boot LineageOS and check if you can access your internal storage mounted on /storage/emulated/0. If not, wipe useradata in TWRP (worked for me).
Click to expand...
Click to collapse
Hope this comment not bricking the device, my friend will kill me:silly:
all credit to @Nexonian with regards.

Recovery

What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?

altojd said:
What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
Click to expand...
Click to collapse
Yes

Where did you find it ?

Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?

altojd said:
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
Click to expand...
Click to collapse
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works

a g bell said:
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
Click to expand...
Click to collapse
i found this recovery in msm extended telegram chat.
the installation did not format my data since i have all my apps working and i can see the entire internal storage when i connect the phone to pc.

I have this recovery on my device for a later time in case I decide to move away from OOS so I can't speak to experience...BUT:
My understanding is due to decryption/recovery on this device the chinese recovery will work BUT the limitations are that if you are on OOS currently you cannot decrypt storage, HENCE you will not see anything in TWRP (again that is my understanding). After backing up the device and wiping the data partition at minimum (most custom roms seem to require us to fastboot wipe our partitions from instructions ive read)... then we can use this version of recovery for custom roms.
I think the major difference between this one and the official version here is of course the unofficial nature of this twrp but also the chinese twrp will let you flash (not boot) the recovery image without issue so we can still USE OOS OR flash custom roms without things going...wrong?...I plan to wait until the A11 OOS upgrade before I make a decision. After learning about how 1P botched the recovery keys + partition issues with the A10 launch I think its just better to see how development goes AFTER the new year maybe

Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.

a g bell said:
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
Click to expand...
Click to collapse
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.

Lossyx said:
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Click to expand...
Click to collapse
Ok l stand corrected just wondering why mauronofrio hasn't released an update or updated his thread. So OnePlus have to implement changes to keystore with Android 11 so they might fix it ?