Database Develop

Backing up stock rom before flashing another

Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though

jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
Search for Huawei ERecovery you may find something useful..

jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.

xzyk said:
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
Click to expand...
Click to collapse
Thanks for the reply, I suspected that's how it worked, just flash back the original system image.
I think I'm gonna hang fire for the time being until I know I have the correct firmware to go back if needed, hopefully the camera will be sorted by then too.

I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?

evolucja said:
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
Click to expand...
Click to collapse
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.

xzyk said:
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
Click to expand...
Click to collapse
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?

jusumgeezer said:
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
Click to expand...
Click to collapse
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.

xzyk said:
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
Click to expand...
Click to collapse
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go

jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.

jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
xzyk said:
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
Click to expand...
Click to collapse
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin

VigneshS007 said:
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
Click to expand...
Click to collapse
Great, that's good news. Please report back with a link so we can all share. Thanks.

Thanks for the replies everyone.
Great news about TWRP too, I look forward to trying it out.

Update 535 C00 has been pushed officially

If your HiCare region is not set to China, set it to China, then search for an update either in HiCare or Settings -> Update. You will then be eligible for the push.
Haven't tried other Asian regions, but it wasn't pushing to my device with Europe set in HiCare.
Speed, battery life and network performance seem to be significantly improved.

Thank you,
works very well your tip.

Hey Friends,
I used FirmwareFinder to download the 3 OTA-MF (not FullOTA-MF) files.
Is it possible to install the update with TWRP and HuRUpdater without loosing any data and without the need to reinstall all installed apps?

slimdns said:
Hey Friends,
I used FirmwareFinder to download the 3 OTA-MF (not FullOTA-MF) files.
Is it possible to install the update with TWRP and HuRUpdater without loosing any data and without the need to reinstall all installed apps?
Click to expand...
Click to collapse
Make a Data Backup in Twrp,install Full Ota Update with Hur Updater.Restore Data Backup with Twrp.
I think the Phone not Boot with not Full Update

slimdns said:
Hey Friends,
I used FirmwareFinder to download the 3 OTA-MF (not FullOTA-MF) files.
Is it possible to install the update with TWRP and HuRUpdater without loosing any data and without the need to reinstall all installed apps?
Click to expand...
Click to collapse
I'd also like to know this.
Also, if the bootloader locks again when doing/flashing an update, can the same old unlock code be used or do I have to request a new code?
Thx

Today I received the update 8.0.0.555.
After all these Years there are still Updates

letschky said:
Today I received the update 8.0.0.555.
After all these Years there are still Updates
Click to expand...
Click to collapse
Hi Letschky! How are you?
I'm still using the Honor Note 8 and love the size.
I was on B538 happily but something happened. I had to relock and unlock the bootloader (To write a new recovery. Seems after a few years it relocks while still showing "unlocked" in fastboot. So weird.) and I didn't know it would factory reset the thing. Then I couldn't unlock the bootloader because Find My Phone got turned on somehow, and the thing was bootlooping. So frustrating.
Anyway. There doesn't seem to be a way to get back to B538 anymore. Hisuite Proxy doesn't work for me. Have you tried it? With official Hisuite you can go to B359 and B528 then B539. I couldn't root B539 so had to settle for B528.
Now I'm contemplating updating all the way to B555 or whatever the newest is, and try to extract the boot.img and patch it with magisk. The only problem is, how the hell do I get a hold of boot.img? It seems TWRP for Oreo broke after B53X somewhere. They must have switched to a different partition configuration.
Now I'm on B528 and battery life isn't great but I did get root and xposed to work.
I can't figure out where official Hisuite is downloading the firmware update. Do you know? It's not in /data/media/0/HwOUC/ which some people report.
Cheers! /Mike

letschky said:
Today I received the update 8.0.0.555.
After all these Years there are still Updates
Click to expand...
Click to collapse
Short version: Are you running 555 rooted? May I ask how?
Thank you so much.

Patched Boot.img via Magisk
I added the Patched Boot img.
Unpack with Winzip and flash via Fastboot
fastboot flash ramdisk magisk_patched-25205_hnSnL.img
For me works root without any Problem.

letschky said:
Patched Boot.img via Magisk
I added the Patched Boot img.
Unpack with Winzip and flash via Fastboot
fastboot flash ramdisk magisk_patched-25205_hnSnL.img
For me works root without any Problem.
Click to expand...
Click to collapse
You sir are a life saver! Is this on 555?
I would like to share something I found with you, if I get it to work on 555. On B538 I used a custom stock rom wanmei, and in it there's a config app called Mobile. There are TONS of features but for me only ONE feature that's been really freaking useful to me. It's to disable the temp sensor. It enables full speed charging. Stock charging often slows down to 1200mA but with this it blasts 2700mA until 80% (I use BatteryChargeLimit anyway to stop at 80-85%). I've been charging like this for years and no battery degradation. That's why I want to stay on B528 or B538 where this app works. I want to try it on B555 too.
Also. I have found that the default CPU governor isn't "interactive" on the slower cores. Only on the faster ones. Setting this to "interactive" gives a nice battery and speed boost compared to performance/conservative/ondemand. This app Mobile can set the governnor too. Mobile requests root access upon first launch. I hope it works on 555 too, after I extract it from the system/app on my B528. I remember after B538 it became a PAID app. You had to pay the developer like 20 usd to activate it. Sneaky. Anyway, I have the free one I can share with you.

Here they are if you're interested.
These are all the custom folders I could find in system/app. The app itself is only the Hwsystemmobile folder but I don't know if it has dependencies in the other ones.
Been using this for years. Took me a long time to translate. The setting I love is at the bottom of the screenshot. ”核心温控“ turn that on. From the main menu you first need to enter the sub page ”其他功能“ (other functions).
In ”其他功能“ you can also set the cpu governor etc.

Yes for 555.
Have you a Link or can upload the wanmei rom?

letschky said:
Yes for 555.
Have you a Link or can upload the wanmei rom?
Click to expand...
Click to collapse
Huawei - Google Drive
drive.google.com
It actually works to flash this over a stock B528 even though it's meant for B538. The system remains B528 but Mobile works normally without bugs. I've used it for a week now as a daily driver.
It's possible to revert to B528 using official Hisuite. Gotta go to B359 first.
Let me know if you manage to get anything to work. I used to get 8h screen on time on B538. I miss that. With B528 I seem to get like 5h. Terrible.
How's 555?

Other features Mobile has are things like enabling VoLTE, enabling RAM compression, gaming modes, hiding status/nav bars, disabling automatic updates, etc.

I do seem to have more free RAM on B528. I never saw 2.4GB free on B538 but on B528 I did. I'd still take the better battery if I had to choose one.

ok thank you, (Downloading)which Twrp to use to install this Rom?The is Multilanguage?

555 is not bad,i use it since the Update..4,5 Hours SOT in almost three days of use

Ok i flash directly via DLOAD Method from 555 to 528.The next Update is 539 and not 538.You say it works on 528?Works this rom on 539?

letschky said:
Ok i flash directly via DLOAD Method from 555 to 528.The next Update is 539 and not 538.You say it works on 528?Works this rom on 539?
Click to expand...
Click to collapse
Hi! I live in China so sorry for the late reply.
You flash that wanmei firmware in fastboot. There's a bat file (to run the bat you need to set windows language settings "Non-unicode" programs default language = Chinese simplified). Yeah it works on B528. I don't know how but it works. I'm using it since a few days.
In B539 if you try to flash it fails when flashing system.img. I suspect the names of the partitions changed around B539. Boot.img is flashed to "ramdisk" now, not boot. This is also why twrp doesn't work right I think.
Are you using a working twrp in 555? I tried flashing one oreo twrp.img dated July 2018 (the newest I could find) and it can't get write access. The log is just full of errors.

4.5h SOT on 555 oh nooo. I'll still try it and see what I get. If this is really the case i'll pay a chinese shop to get me back to B538. They said they can.
How about available RAM? After a reboot, can you see more than 2.0GB free in Recent Apps?

This is RROS dev here need something important.

Hi guys, i am looking to release an update for the faumous and powerful RoadRunner OS 8.10. My problem is the latest firmware blocks all sorts of samsung ui customization options applying any mods just bootloop the Tab. So, my request is anyone on the firmware code XAR check for updates amd tell their firmware's last 4 alphanumeric value ( I need DRJ1 ). Also send me a screesnhot from about device before sending me what i am going to ask for.
If u are on XAR and the security patch says 1st august 2018 and DRJ1 in build number then do the following:
Install TWRP if not already .
backup system and boot and in options enable compression.
after backup is done copy it to the computer or use rar for android to compress it as a zip and upload it on Google drive with link sharing on and then send me the link for the uploaded file
If u have any confusion in the backup process or identification process let me know will be happy to help.

Androbots said:
Hi guys, i am looking to release an update for the faumous and powerful RoadRunner OS 8.10. My problem is the latest firmware blocks all sorts of samsung ui customization options applying any mods just bootloop the Tab. So, my request is anyone on the firmware code XAR check for updates amd tell their firmware's last 4 alphanumeric value ( I need DRJ1 ). Also send me a screesnhot from about device before sending me what i am going to ask for.
If u are on XAR and the security patch says 1st august 2018 and DRJ1 in build number then do the following:
Install TWRP if not already .
backup system and boot and in options enable compression.
after backup is done copy it to the computer or use rar for android to compress it as a zip and upload it on Google drive with link sharing on and then send me the link for the uploaded file
If u have any confusion in the backup process or identification process let me know will be happy to help.
Click to expand...
Click to collapse
I just got a 710. Its stock. Is this what you need?

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

Good source for firmwares?

I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2

All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).

There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml

I'd recommend around sammobile and samfw. These are the two sources I use the most

hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?

Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?

WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for

Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((

My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).

Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?

You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata

DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).

WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse

WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday

Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell

schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.