Trustzone error - OnePlus 3T Questions & Answers

Hi guys !
On my OP3T i was on OOS 4.0.3 with kernel r12. I flashed OOS with TWRP 3.1.0-1. Before that, i flashed a lot of ROM for fun and see the differences etc ...
Today i wanted to test some new ROM because i was on OOS since a long time and wanted to change. Si I downloaded Citrus and Nuclearom and tried to flash with TWRP 3.1.0-1 and i have error 7. Same with Nuclearom before the message error 7, i saw this :
Comparing TZ version TZ.BF.4.0.1-85373 to BZ.BF.4.0.1-83199
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-85373") == "1"
First time I saw this message so i searched in Google and apparently I don't have the last firmware of OP3T so i find a URL on Google : https://drive.google.com/file/d/0Bzko1towAti5NzU5b3lDaEZfZ3M/view
I flashed the firmware but still can't install custom ROM except OOS 4.0.3.
So i don't understand why i can't install custom ROM but OOS works, i have the last firmware, TWRP 3.1.0-1, bootloader updated etc ...
I searched a lot on Google :
https://www.reddit.com/r/LineageOS/comments/5vksqe/update_bootloader_on_oneplus_3t/
http://www.lineageosdownloads.com/fix-error-7-lineage-os/
https://forum.xda-developers.com/oneplus-3t/help/twrp-error-7-t3552273 (more interesting)
But i followed all steps of all links, didn't find a issue.
Sorry if my english is bad and hope someone have a idea.
Best regards,

Which rom are you trying to install
Some roms like sultan cm13 has not been updated with the required firmware trustzone and it uses the old firmware trustzone

Balashe said:
Hi guys !
On my OP3T i was on OOS 4.0.3 with kernel r12. I flashed OOS with TWRP 3.1.0-1. Before that, i flashed a lot of ROM for fun and see the differences etc ...
Today i wanted to test some new ROM because i was on OOS since a long time and wanted to change. Si I downloaded Citrus and Nuclearom and tried to flash with TWRP 3.1.0-1 and i have error 7. Same with Nuclearom before the message error 7, i saw this :
Comparing TZ version TZ.BF.4.0.1-85373 to BZ.BF.4.0.1-83199
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-85373") == "1"
First time I saw this message so i searched in Google and apparently I don't have the last firmware of OP3T so i find a URL on Google : https://drive.google.com/file/d/0Bzko1towAti5NzU5b3lDaEZfZ3M/view
I flashed the firmware but still can't install custom ROM except OOS 4.0.3.
So i don't understand why i can't install custom ROM but OOS works, i have the last firmware, TWRP 3.1.0-1, bootloader updated etc ...
I searched a lot on Google :
https://www.reddit.com/r/LineageOS/comments/5vksqe/update_bootloader_on_oneplus_3t/
http://www.lineageosdownloads.com/fix-error-7-lineage-os/
https://forum.xda-developers.com/oneplus-3t/help/twrp-error-7-t3552273 (more interesting)
But i followed all steps of all links, didn't find a issue.
Sorry if my english is bad and hope someone have a idea.
Best regards,
Click to expand...
Click to collapse
You can solve the problem deleting one string in update script file into the rom, many roms now give that problem, simply follow the info in this thread:
https://forum.xda-developers.com/showpost.php?p=71436515&postcount=4273

kunal1540 said:
Which rom are you trying to install
Some roms like sultan cm13 has not been updated with the required firmware trustzone and it uses the old firmware trustzone
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...-kernel-nuclearom-radioactive-kernel-t3544836
https://forum.xda-developers.com/oneplus-3t/development/rom-kernel-citrus-caf-t3534978
Ok VampireHeart i will try tomorrow, thanks

VampireHeart said:
You can solve the problem deleting one string in update script file into the rom, many roms now give that problem, simply follow the info in this thread:
https://forum.xda-developers.com/showpost.php?p=71436515&postcount=4273
Click to expand...
Click to collapse
Only do this if you are flashing a custom rom! OOS actually requires this line since it makes sure that you do not brick your phone by downgrading the firmware.
OOS flashable zips contain new firmware and then OnePlus inserted this line to protect ppl.
(Actually I might be wrong and you are indeed able to downgrade and 1+ is just kidding you, however I would not want to try)

Si tried to delete the string for Citrus and that works, i will try later with others ROM, thanks guys !

Related

Huawei P9 - Android 6 to 7 Firmware

Hi all,
Ive been a fair while out of flashing ROMs since Note 4 Edge / HTC M7 and have today unlocked bootloader and rooted my P9.
It is currently Australian Vodafone release EVA-L09CC346B160 (Android 6) but I want Nougat.
There is no local carrier updates available but I understand that there is Android 7 available in Australia on 'international' branded handsets.
How can I identify what this firmware is for international Nougat? Can some one assist me. Or can someone advise what would be a suitable equivalent firmware that I can use in place of.
I am unsure how this device goes in flashing ROMs of higher or lower android versions on the current firmware and dont really want to brick it.
Thanks for any tips / suggestions
Umm, just found a thread mentioning L09C636B361 - will check this out, but is there any more recent? And still how does fl;ashing other premade ROMs on 7 go on top of the current Android 6 firmware go?.. Ta
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
using this guide you can update to the latest nougat release
Thank yuo Xtcislove
I have completed the steps suggested and now have Nougat. Though it is a newer version being .383 which was updated via OTA to .378 and then zip to .383.
Thank you for the help
I'm trying to flash firmware on my P9, now I have EVA-L09C40B181, but it stuck on 5% and HiSuite shows Recovery failed! I tried custom firmware, same problem. What can I do ?
Dfani511 - just follow the instructions in the thread provided by Xtcislove, it works but took me a long time.
I found the steps concerning the update to be added in dload was a little not clear, in the update zip that's downloaded, you need to open it until you get the dload folder, extract that and copy to the SD card.
Throughout my updating, o never ended up on the firmware you have
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
This is what I did to root my Huawei P9 on Nougat L09C432B383:
Use the SuperSU-v.27.9-201612051815EMUI5.0.zip file flash via custom recovery and it should root your device no problem.
twerg said:
This N seems to be working fine, nicer looking.
I do have 1 issue, no matter what I do I can not get root to work. I'm on .383, can this one be rooted or not currently? If it can, how do I root .383? I have TWRP 3.1.0.3 as current recovery..
Or, is that ok to flash on my current P9 L09C432B383 ? from this thread - https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Click to expand...
Click to collapse
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
xtcislove said:
Use this
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much
twerg said:
Hey xtcislove - is there a preferred version? 1, 2 or 3 do you recommend? Thanks mate
--------------
EDIT - Nevermind, Xtcislove, your the best man, appreciate your help with your guides etc. I went with option 1 and the handset is now rooted on Nougat. Thanks so much
Click to expand...
Click to collapse
3 is the version i preffer, you cant freeze apps with v1 but most things should work fine.
btw you can flash v3 over v1.
Ive flashed v3 over 1 and all appears good, root working fine. Thanks again.
Though I have noticed on both v1 and v3 that SuperSU binary needs to be updated, ob both v1 and v3. The phone fails to update both, states unsuccessful and to reboot, which also does not update the binary.
Only other thing I have done is to get BusyBox.
What can be done about the failing binary update? Will it be fine to leave as is, just getting rid of the prompt when it appears, or does it really need to have the update done sometime?

Questions regarding xiaoumi.eu ROM

I made the update from stable global to beta global last week, because I needed to unlock bootloader. Now my plan was to wait for the first stable release of Lineage, but I didn't know about Xiaoumi.eu rom and that headphone volume was so bad on this stock (beta) rom...
Now my questions are:
Which partitions have to be wiped before flashing the ".eu" rom?
(Already googled this one on my own, see "EDIT")Are the weekly versions like Beta versions? If yes then would this one be the latest stable rom:
xiaomi.eu_multi_MIMAX2_V8.5.15.0.NDDCNED_v8-7.1.zip
Other than that there shouldn't be any other Things to worry about, right?
Thanks in advance!
EDIT: So I googled a bit about the meaning of weekly and I guess it will work well enough for me, downloading this one right now:
xiaomi.eu_multi_MIMAX2_7.10.12_v9-7.1.zip
I couldn't find much about my other questions though..
EDIT 2: I just went the "factory reset" way and wiped data, cache and dalvik and it worked.
No further questions from me.
Were you able to install Xposed on this ROM?
haven't tried yet, I don't have the time eight now to fix it if it starts acting weird or bootloops...
maybe I have some time in the weekend, I really need xposed fir pbmc...
dnbdel said:
Were you able to install Xposed on this ROM?
Click to expand...
Click to collapse
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Tazmaniiac said:
I finally managed to flash xposed-v88.2-sdk25-arm64-test4.zip from the official MIUI 9 Github thread.
I'm on latest weekly MIUI 9 xiaomi.eu rom (7.10.19), which is Android 7.1 with Magisk 14.0. Flashed via iscle's TWRP.
Download for test4 (Android 7.1), Android 7.0 would be this one
Got the downloadlink from here: http://en.miui.com/forum.php?mod=viewthread&tid=946636&highlight=xposed
I suggest you to read the description in the MI Forum thread. I haven't tested any modules yet, I only know that the framework is active for me and that it disabled SafetyNet.
Click to expand...
Click to collapse
Tazmaniiac said:
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Click to expand...
Click to collapse
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?
dnbdel said:
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?
Click to expand...
Click to collapse
Nope, that's more or less how I did it. But before I flashed this version of Xposed I installed the Xposed Installer. Maybe that's necessary, but I think not.
Can you try out flashing the no-verity-opt-encrypt.zip? I did it for something else earlier and also after every attempt of flashing Xposed.
If I understand it right some Xiaomi phones bootloop after you write to /system, then you have to flash that file to fix it. Xposed writes to /system, so that could be a solution.
Before you flash that research it a little bit more, because I don't know much about this topic and don't want to give you false advice.
EDIT:Did you flash the xposed version from my downloadlink? It is different from the regular 88.2 SDK25, it's a testversion made by the xposed creator specifically for MIUI 9 devices.

[SOLVED]/Help/ Update Lineage 13.0 to Lineage 15.1 GN7000

Hello guys,
I don't know if here is the good place to post. My bad and SORRY for my english, I'm french and I'm learning by myself specially in watching tv series with subtitles :fingers-crossed:
I'm currently on version Lineage 13.0-20170204-UNOFFICIAL-n7000 (6.0.1) and I would like to install OREO 8.1.0 (Lineage 15.1).
I don't want to mess up everything so I ask for help as I know I can rely on tips here.
Should I install Lineage 14 first and then move to 15? There is explanation on Updating If you are running an earlier NightOwl cm15.1 alpha version: but nothing if we are on other version. Is the cm version important here? It must be another cm15 or it works no matter version we installed? So I'm confused and after spending 1 month to recover a BLOD Nexus 5X without recovery and locked fastboot... I know I must check twice before doing anything.
So if someone can enlighten me. Thank you
Edit :
I followed Updating If you are running an earlier NightOwl cm15.1 alpha version.
When I try to flash the ROM, it end up with :
- detected filesystem ext4 for /dev/block/mmcblk0p9
- Patching system image unconditionally...
- E1001 : Failed to update system image.
- Updater process ended up with ERROR : 7
- Error installing zip file '/sdcard0/Nightowl-lineage15.1-beta2-n7000.zip
Help please. Thank you
yessade said:
Hello guys,
I don't know if here is the good place to post. My bad and SORRY for my english, I'm french and I'm learning by myself specially in watching tv series with subtitles :fingers-crossed:
I'm currently on version Lineage 13.0-20170204-UNOFFICIAL-n7000 (6.0.1) and I would like to install OREO 8.1.0 (Lineage 15.1).
I don't want to mess up everything so I ask for help as I know I can rely on tips here.
Should I install Lineage 14 first and then move to 15? There is explanation on Updating If you are running an earlier NightOwl cm15.1 alpha version: but nothing if we are on other version. Is the cm version important here? It must be another cm15 or it works no matter version we installed? So I'm confused and after spending 1 month to recover a BLOD Nexus 5X without recovery and locked fastboot... I know I must check twice before doing anything.
So if someone can enlighten me. Thank you
Click to expand...
Click to collapse
SOLVED
yessade said:
Edit :
I followed Updating If you are running an earlier NightOwl cm15.1 alpha version.
When I try to flash the ROM, it end up with :
- detected filesystem ext4 for /dev/block/mmcblk0p9
- Patching system image unconditionally...
- E1001 : Failed to update system image.
- Updater process ended up with ERROR : 7
- Error installing zip file '/sdcard0/Nightowl-lineage15.1-beta2-n7000.zip
Help please. Thank you
Click to expand...
Click to collapse
I went to WIPE-ADVANCED and format Kalvin, Cache, System and Data.
- Flash lanchon REPIT
- Flash the rom without error.
After successfully flashed the ROM, Wipe Kalvin cache and flash gApps.
After "5-7"minutes of rebooting, the phone was updated to CM15 and running smoothly.
If my post can help someone else.
Admin, this thread can be tag SOLVED.

Data security and phone encryption. Miui custom rom

My new MI8 SE is not my daily use, so I got time to check all available MIUI custom rom (eu,Globe,MiRum,Miuipro,Ros,MS and Masik 1.8.)
At this point no problem, they install very well and they answer my needs.
BUT:
AS EVERYBODY should know that it is very easy to delete the central Password and finger print by the mean of our sophisticated tool (I mean TWRP).
In order to be safe '(without turning back to stock rom) I tried to encrypt the phone WITHOUT success...
Process failed every time with different results (full reset, logo loop for hours, partial encrypt for data only). But was always the point that minimum security can't be reached!
Question:
-Can you well sleep If you mind that you are having all your precious data available in the wind as soon your phone is lost or stolen or even worst let in some bad friends hands...? It takes 1 mn to delete the file without any computer.
I see a partial solution by installing afterward a stock recovery that does allow to trick the system file.
(If somebody has it, I am available to test this option, but don't tell me to flash a stock rom as solution!!)
Your comments/solutions are welcome.
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
NexusRunner said:
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
Click to expand...
Click to collapse
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
lolo9393 said:
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
Click to expand...
Click to collapse
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
me_death said:
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
Click to expand...
Click to collapse
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
lolo9393 said:
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
Click to expand...
Click to collapse
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
me_death said:
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
Click to expand...
Click to collapse
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
Thank you so much for all the help.
lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
9. What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.14
lolo9393 said:
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
Click to expand...
Click to collapse
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
me_death said:
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
Click to expand...
Click to collapse
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
lolo9393 said:
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
Click to expand...
Click to collapse
Finally i got it working following your instructions on the MIUI EU forum. Thanks a bunch. :victory: :highfive:
To others for reference. Following are the procedures that i followed to boot up Miui Eu :silly:
- Flash official 8.12.13 (Dev Fastboot Rom) through MiFlash.
- Flash TWRP 1102
- Clean Data
- Push/ Copy and Flash 8.12.20( EU Rom), it booted up finally without redirecting to Fastboot.
- Update 8.12.20 to latest available from system updater.
- Now there won't be any recovery or we aren't able to enter into available recovery even though the system boots.
- Flash TWRP 1227.

Looking to flash OK Pie on P9 Any help would be appreciated.

Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
SideSkroll said:
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
Click to expand...
Click to collapse
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
zgfg said:
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
Click to expand...
Click to collapse
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
SideSkroll said:
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
Click to expand...
Click to collapse
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
zgfg said:
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
Click to expand...
Click to collapse
Thank you. Thats exactly what I was looking for. I really appreciateyour help.
Btw, no one should have the "hide extensions for known file types" checkbox marked...
Edit: Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
SideSkroll said:
....Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
Click to expand...
Click to collapse
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
SideSkroll said:
Thats exactly what I was looking for...
Click to expand...
Click to collapse
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
zgfg said:
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
Click to expand...
Click to collapse
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
SideSkroll said:
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
Click to expand...
Click to collapse
This small OTA bringing Patch02 over b540 installs even over TWRP (but that was not the case for OTA from eg b535 to b540)
Cannot discuss/compare battery for Omni Pie, since not using Omni
Problem with Camera app does not show on stock Oreo. Even if the app was somehow ported from Huawei, there are maybe problems with integration to Omni.
Various Huawei/Mate models come with different cameras, but there is only one OK Omni ROM (with one Camera app) given to work on all Huawei/Mate models
Btw, somebody else also complained about issues with Camera (and GPS) and decided to go back to stock Oreo.
Similarly, issues you described about black notifications or so must be related to the custom ROM, theme or so.
As a general rule:
- for installing OK ROM, you flash System partition, and nothing else
- you also wipe Data partitiom (containing all your installed apps, incl Magisk Manager, also containing your user settings)
It does not affect any other partition.
Therefore, changes given by NW patch persist - without, you will have (also in that OK ROMs) problems with SIM card(s) and connecting to the network
Also, Magisk, which was flashed to Ramdisk, persists. You must only install Magisk Manager again, because it is user apo, installed to Data partition that was wiped
You must check on the OK side how they advice installing the updates of OK ROMs
(It is questionable if they will get updates any more, since OK team switched to development of ROMs which install over the stock Pie, whereas on P9 you have no stock Pie - only Oreo, and most likely, we will never see stock Pie for P9.
Just check when OK team released last ROM for stock Oreo, and compare with their releases of OK ROMs for stock Pie:
https://openkirin.net/download/
Hence IMO, for updating the OK ROM (if/when it comes), you will again just need to flash its System and to wipe Data (and then to reinstall user apps like Magisk Manager).
Hopefully, you can backup and restore some apps and settings by Titanium.
Whether you don't need to wipe Data for such update - check from the OK support.
On the Open Kirin site you will find Support pages (Faq, HowTo) and also a link to the live Telegram channel

Categories

Resources