You need to be in stock emui 8 with unlocked bootloader.
If you are in elemental rom come back to stock emui 8 then flash this rom.
If you are in another gsi you can proceed directly (flash below recovery then do factory reset then flash gsi los rom via fastboot then again reboot to stock recovery do factory reset)
If you are in stock emui 8 do not wipe anything just flash it via fastboot and do factory reset.
first flash this recovery
https://mega.nz/#!cbJFAIQD!qvp1KnZ0qxlg6nHDFmpM5qyZ9QUVIDe5PoZE0BQf8fs
Fastboot command: fastboot flash recovery_ramdisk name of recovery.img
Then download
https://openkirin.net/download/
Fastboot command: fastboot flash system name of image.img
Los or RR rom and flash via fastboot (no need to wipe anything) then reboot to recovery do factory reset. You will have oreo 8.1 with gapps ,full signal bars,face unlock and stock camera.
If you are experiencing no sound its not gsi problem you didn't flashed stock completely so first flash this twrp recovery (only if you are in oreo not for emui5)
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Then flash stock emui 8 via huru
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If huru only flased update.zip and gave you error no update_full_hw.zip and no update_data_full_public.zip not found in sd card then you need to rename them and flash again without wiping anything.
If stock emui 8 taking more than 5 minutes to boot then flash stock recovery mentioned above and do factory reset then it will boot with in 5 minutes.
If you don't have network or imei then you need to root. Then use any root explorer then go to cust/cn/all/localprop and change the line ro_config full network support=ture to false then reboot your network and imei will come back. You can do this in stock or in gsi.
RR ROM has great battery life with tons of customizations.
For emui8 flashing instructions,root and sound mod follow these instructions
https://forum.xda-developers.com/ho...si-honor-6x-8-1-0-t3809004/page5#post76981105
For telegram support of openkirin join this group
https://t.me/joinchat/HUf8EBJUJZQD281E59MdDw
Hell yess, thanks to open kirin team and you for mentioning it, the rom is excellent in use all bugs (the ones i faced in other gsi) fixed in this one and the availability of stock camera is just a cherry on top ?
Im newbie not familiar with this term
what is "gsi"?
need help
How to install emui 8 on bln-l21c432
jlan007 said:
Im newbie not familiar with this term
what is "gsi"?
need help
Click to expand...
Click to collapse
Generic system image. Read about project treble.
jlan007 said:
Im newbie not familiar with this term
what is "gsi"?
need help
Click to expand...
Click to collapse
Gsi means generic system image. In oreo custom roms will be available in system image formate we don't need twrp to flash custom roms just flash it via fastboot and factory reset.
Gsi roms will give you latest android os updates same as pixel devices getting so we don't need to wait for hauwei to release updates. If android p releases these gsi roms will give u update same as google devices getting. Oreo is game changer for every device.
If u want to flash gsi rom follow the emui8 upgrade method
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
Then follow instructions on openkirin support section.
--ahmed said:
How to install emui 8 on bln-l21c432
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
Follow that guide you will be on oreo in 10mins or less
If we rebrand to Chinese then update to Oreo and flash gsi..can we rebrand to our original variant or is there need to?
Which gsi redirection rom , carbon rom or los 15 ???
johnscrub said:
If we rebrand to Chinese then update to Oreo and flash gsi..can we rebrand to our original variant or is there need to?
Click to expand...
Click to collapse
Yes we can rebrand to original variant using hwota8
Khan ubaid said:
Which gsi redirection rom , carbon rom or los 15 ???
Click to expand...
Click to collapse
Go for Los 15 which is more stable and updated one.
Resurrection remix has huawei stock camera inbuilt....
Why flash stock recovery ? For those who are on Twrp ?
Great post. Hope you share some more experiences.
Trying to use the Google Play store it's telling me that my device isn't certified and I can't do anything..
NVM: For anyone else wondering I installed Magisk then the Magiskhide module and changed fingerprint.
Khan ubaid said:
Resurrection remix has huawei stock camera inbuilt....
Click to expand...
Click to collapse
Los is also had hauwei stock camera but rr in initial buid and los got 4 updates.
Nollie8969 said:
Why flash stock recovery ? For those who are on Twrp ?
Great post. Hope you share some more experiences.
Click to expand...
Click to collapse
Because you can't perform factory reset from twrp it can't do it correctly finally you will ended up in bootloop. You can flashctwrp right after doing factory reset but openkirin doesn't support twrp.
whateven12 said:
Trying to use the Google Play store it's telling me that my device isn't certified and I can't do anything..
NVM: For anyone else wondering I installed Magisk then the Magiskhide module and changed fingerprint.
Click to expand...
Click to collapse
So before flashing magdisk did playstore worked for you? Or did you flashed magdisk when flashing os? For me playstore works perfectly.
Ramesh006 said:
So before flashing magdisk did playstore worked for you? Or did you flashed magdisk when flashing os? For me playstore works perfectly.
Click to expand...
Click to collapse
Play store or any Google app wouldn't work for me before I install Magisk and the Module to change the fingerprint to a certified device.
No solution, but in the meantime you can use Aptoide as store: http://en.aptoide.com
whateven12 said:
Play store or any Google app wouldn't work for me before I install Magisk and the Module to change the fingerprint to a certified device.
Click to expand...
Click to collapse
Did you flashed los or rr? Try reflash.
Related
WARNINGS:
This ROM is in the canary test and NOT STABLE.
You flash this rom on your own respondibility.
Someone have got stuck in a bootloop.
The default language is Chinese.
Flashing this ROM will convert your ZUK Z1 from COS 12.1 to ZUI, and the bootloader will be replaced and locked.
If you want to go back to COS, you can search for help in this forum.
NOW you can install the gapps, and they can run well.Download the newest version (ZUI 1.5.201).
What works:
ALL.
Because ZUI recovery's device code name is K9, TWRP recovery's device code name is ham, if you flash it by TWRP recovery, you must modify the script.
How to flash:
1. convert to ZUI:
How to flash ZUK Z1 ZUI version 0.9.084_ST_150729
2. Download this rom.
3. Rename the rom file to update.zip, and put it into /sdcard .
4. Boot into ZUI recovery and full wipe.
5. Flash this rom and reboot.
NOTICES:
I tested this rom, and it works well. I flash it by TWRP recovery (I modified the script).
For first boot, you may wait for 10+ minutes.
Download:
ZUI 1.6.225 official ota url
ZUI 1.6.225 Baidu Colud Disk(This is a Chinese website.)
hfutxqd said:
WARNINGS:
This ROM is in the canary test and NOT STABLE.
You flash this rom on your own respondibility.
The default language is Chinese.
Flashing this ROM will convert your ZUK Z1 from COS 12.1 to ZUI, and the bootloader will be replaced and locked.
If you want to go back to COS, you can search for help in this forum.
What works:
ALL.
Download:
click here to donwload
http://pan.baidu.com/s/1bgw8Vk
Click to expand...
Click to collapse
The link is not opening....it's just keep loading...
Ramshu97 said:
The link is not opening....it's just keep loading...
Click to expand...
Click to collapse
You need to click the circled button....
bartito said:
You need to click the circled button....
Click to expand...
Click to collapse
Thanks man I downloaded the ROM file...
Here, I mirrored it on AndroidFileHost. This should make things easier to reach.
Hi,
Tried flashing the ROM with latest Breadcrust TWRP version. I had an error saying that the ROM was made for the "K9" model, and that mine is Z1. I modified the script in the rom file and finally flashed it, but I get stuck in a bootloop. Any ideas?
Thanks.
woonaval said:
Hi,
Tried flashing the ROM with latest Breadcrust TWRP version. I had an error saying that the ROM was made for the "K9" model, and that mine is Z1. I modified the script in the rom file and finally flashed it, but I get stuck in a bootloop. Any ideas?
Thanks.
Click to expand...
Click to collapse
K9 is the ZUI's official device code of ZUK Z1.Try to convert to ZUI firstly,and rename the rom file to update.zip. Boot into the ZUI's recovery, wipe and flash.
Could someone do a comparision in camera quality between COS12.1 and ZUI 6.0 ?
so with this ZUI Android 6.0 version, can be root or not..?
Problem solved after trial and error.. :highfive:
but now I have issues using playstore about google play service... so can't use play store.. :crying:
kaizer hanz said:
so with this ZUI Android 6.0 version, can be root or not..?
Problem solved after trial and error.. :highfive:
but now I have issues using playstore about google play service... so can't use play store.. :crying:
Click to expand...
Click to collapse
Flash TWRP recovery firstly, then you can flash the gapps.
hfutxqd said:
Flash TWRP recovery firstly, then you can flash the gapps.
Click to expand...
Click to collapse
can you give me the gapps..? I have TWRP installed, Rooted but don't have a Working Gapps.. I mean.. I have tried all gapps.. but no one work for me..
kaizer hanz said:
can you give me the gapps..? I have TWRP installed, Rooted but don't have a Working Gapps.. I mean.. I have tried all gapps.. but no one work for me..
Click to expand...
Click to collapse
http://opengapps.org/
choose ARM, 6.0, and the size you need
woonaval said:
http://opengapps.org/
choose ARM, 6.0, and the size you need
Click to expand...
Click to collapse
using the smallest.. nano version.. until now almost 30 minutes stuck at ZUK boot logo (maybe bootloop) :crying:
maybe going back to ZUI 1.2.0.40
So is there anyone who boot correctly and is able to give us a report?
We clearly need a more detailed step by step for those of us having an international Zuk device. If I can try it (maybe tomorrow), I will post this detailed info.
I have unlocked the bootloader and installed TWRP as well but while i'm trying to install GAPPS got error code:25, Now it's Bootloop i'm going back to the old version.
kaizer hanz said:
can you give me the gapps..? I have TWRP installed, Rooted but don't have a Working Gapps.. I mean.. I have tried all gapps.. but no one work for me..
Click to expand...
Click to collapse
You can find the gapps here.
opengapps.org
Before flash the gapps, you must wipe the data.
thrpod said:
Could someone do a comparision in camera quality between COS12.1 and ZUI 6.0 ?
Click to expand...
Click to collapse
+1 for this.
hfutxqd said:
You can find the gapps here.
opengapps.org
Before flash the gapps, you must wipe the data.
Click to expand...
Click to collapse
it is work for you..? couse I have bootloop.. maybe I need wipe data before flash gapps..
can you give your screenshot playstore working in Marshmallow version of ZUI..
EDIT :
after wipe data, wipe dalvik cache, wipe cache with no Luck... stuck at ZUK logo (Bootloop):silly:
going back to ZUI 1.2.040.. until someone give tutorial step-by-step cleary... :highfive:
I'm unable to downgrade after this update.. Cyanogen recovery give signatures verification error in the middle of installation...
I want to flash an RR into my Mi 4C. So I unlocked my bootloader by registering in Mi.com.
Firstly I flashed in a TWRP Rec
Code:
fastboot flash recovery ..../twrp.img
fastboot boot twrp.img
And successfully boot into rec.
Then I tried to install the ROM. After flashing it stuck on the Mi Logo every time.
Tried sideload and "install" by the TWRP but didn't work.
You can simply check your bootloader status by
fastboot oem device-info
Click to expand...
Click to collapse
Also select correct TWRP version for Mi4c, based on android version
Suxter said:
You can simply check your bootloader status by
Also select correct TWRP version for Mi4c, based on android version
Click to expand...
Click to collapse
TWRP selection is related to Android version? Could you please explain a little? When I was flashing my Nexus 6P I've never considered about Android version
Darkouting said:
TWRP selection is related to Android version? Could you please explain a little? When I was flashing my Nexus 6P I've never considered about Android version
Click to expand...
Click to collapse
After you flashed Nougat based Xiaomi rom, you can't boot on the older version of TWRP.
There is a new TWRP for nougat rom.
If you already flashed Nougat based Xiaomi rom, use the new version. You can find it in here https://xiaomi.eu/community/threads/7-2-16-17.38651/
Suxter said:
After you flashed Nougat based Xiaomi rom, you can't boot on the older version of TWRP.
There is a new TWRP for nougat rom.
If you already flashed Nougat based Xiaomi rom, use the new version. You can find it in here
Click to expand...
Click to collapse
Nothing ever changed
I used this TWRP before.I flashed it in, boot the recovery, flashed in my ROM, checked clear Dalvik cache, pressed Reboot System.
The screen goes dark and never turned on. Press the power button only to realize it Reboot into bootloader.
Every time I reboot it reboot in Bootloader.
Plus I do a FULL wipe every time I flash in and did not work ?
UPDATE!! I flashed in a ROM in XIAOMI.EU and succeed.But why ???
Still failed in flashing in other ROMs
Darkouting said:
Nothing ever changed
I used this TWRP before.I flashed it in, boot the recovery, flashed in my ROM, checked clear Dalvik cache, pressed Reboot System.
The screen goes dark and never turned on. Press the power button only to realize it Reboot into bootloader.
Every time I reboot it reboot in Bootloader.
Plus I do a FULL wipe every time I flash in and did not work
Click to expand...
Click to collapse
sorry to here that then. which MIUI version you flashed? official & unofficial ?
Suxter said:
sorry to here that then. which MIUI version you flashed? official & unofficial ?
Click to expand...
Click to collapse
xiaomi.eu provides a modded MIUI. Maybe it's unofficial.
I got a weekly-update version and flashed it in and succeed.
It is MIUI 8
Darkouting said:
xiaomi.eu provides a modded MIUI. Maybe it's unofficial.
I got a weekly-update version and flashed it in and succeed.
It is MIUI 8
Click to expand...
Click to collapse
try this.
flash this http://bigota.d.miui.com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz with MiFlash
then connect to fastboot & fastboot oem unlock
now flash TWRP for 5.1 rom https://www.androidfilehost.com/?fid=24421527759888487
boot into TWRP & install any other rom.
for nougat based xiaomi.eu rom, read their introductions carefully https://xiaomi.eu/community/threads/7-2-16-17.38651/ Don't flash TWRP for nougat rom if you still in 5.1 ( TWRP for nougat https://www.androidfilehost.com/?fid=457095661767135741 )
Suxter said:
try this.
flash this http://bigota.d.miui.com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz with MiFlash
then connect to fastboot & fastboot oem unlock
now flash TWRP for 5.1 rom https://www.androidfilehost.com/?fid=24421527759888487
boot into TWRP & install any other rom.
for nougat based xiaomi.eu rom, read their introductions carefully https://xiaomi.eu/community/threads/7-2-16-17.38651/ Don't flash TWRP for nougat rom if you still in 5.1 ( TWRP for nougat https://www.androidfilehost.com/?fid=457095661767135741 )
Click to expand...
Click to collapse
It worked! So that seems to be a bug that only exists in my 4c on MIUI based on Android 7.0 ?
THANKS A LLLLOT！
Darkouting said:
It worked! So that seems to be a bug that only exists in my 4c on MIUI based on Android 7.0
THANKS A LLLLOT！
Click to expand...
Click to collapse
Most probably you mess up with old TWRP & Nougat 7.0 rom
You are welcome :good:
Thanks dude! It helps me a lot! I thought we need to install Nougat recovery before flashing Nougat rom!
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year
Hi,
i´m update my honor via HuRupader_0.4 to last oreo (562) -FirmwareFinder. This step wipe my TWRP and flash stock recorvery (I had to do factory reset and whipe the cache to boot). I used it this instructionshttps://forum.xda-developers.com/honor-8/development/twrp-honor-8-emui-8-t3886862 and finaly not work. i flash twrp for honor 8 (original error 0MB inter storige) but i was stuck to error 9. How should I proceed? Multitool flash twrp and su ends with a jam on the start logo.
I have not slept for two nights, please help me solved this problem
delete
PremiumBlaze said:
Maybe you could try flashing a openkirin rom using fastboot? Like omni oreo (don't flash omni pie from emui but only from omni oreo)
Click to expand...
Click to collapse
No.. He can flash Omni pie from emui if he wants. Tons of our users have done so without issue.
PremiumBlaze said:
Maybe you could try flashing a openkirin rom using fastboot? Like omni oreo (don't flash omni pie from emui but only from omni oreo)
Click to expand...
Click to collapse
Openkirin rom is the same as the original firmware? Emui 8 and oreo? Twrp and su works correctly?
delete
I have the OTA file downloaded and I know how to use adb, but I can’t find exact directions on how to do this. Thanks for any help.
tuffluck said:
I have the OTA file downloaded and I know how to use adb, but I can’t find exact directions on how to do this. Thanks for any help.
Click to expand...
Click to collapse
What rom are you on now? Do you have a recovery installed?
Hi ,what
differenceceat vendor by creat ventor 2 in j710f
Pixel Experience based on Android 11 and no I did not do a recovery.
tuffluck said:
Pixel Experience based on Android 11 and no I did not do a recovery.
Click to expand...
Click to collapse
This works for me
Fastboot boot into TWRP,, ( TWRP nebrassy edition)
install trwp via advance settings
reboot into recovery
send a copy of your ota oos over to your phone ,
flash oss ,
reboot into oss recovery
Format data in oss stock recovery
Reboot
just find a way to relock your bootloader, it will revert you to stock completely.