Develop Bugs

[Tool][HTC 10][S-On]Firmware Updater

Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!

This works with unsigned firmware?
Good job, though irrelevant to me

xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...

krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.

xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups

Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .

It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.

Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.

Why it doesn't work with unlocked bootloader?

CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...

krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com

xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...

krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.

xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years

Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?

Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.

Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...

krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.

-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?

krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520

Safe STOCK Oreo by Fastboot FULL flash!

Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!

Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!

Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!

SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!

So this will work for european users who did not break their persist?

Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know

Battery performance is for fully happy and satisfied OVERWHELMING

will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man

can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update

LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?

carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat

will it work for indian version XT1686

LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?

carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome

LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...

I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks

I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough

No risk no Win buddies

Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1

JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie

LG G8 (LM-G820QM) Unlocked

I have LG G8 Alexa variant. Model LM-G820QM.
I think ts on latest firmware "qm21e". Right now I live in India so the VoLTE is not working. I tried to cross-flash it to Open firmware but LGUP gave error "Cant change the device(AMZ_US > OPEN_US)".
I have three questions.
Can I cross flash Korean firmware ?
And if so, will i get VoLTE working ?
And my G8 has 2 cams while the Korean varient has 3 cams. Will my cams work with Korean firmware ?
Thank you.

Do you by any chance still have the OPEN_US Firmware?
I've been looking everywhere for it but I can't find it.

Download LG Firmware for LG G8 ThinQ LMG820QM Android 10 Q kdz stock BPT Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-roms.com
--------
| Firmware Update Android 10 Q kdz stock AMZ Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-firmware.net
I think any of this 2 are OPEN. If not then reply me back I will deep search on google. I happend to found it somewhere but can't remember where exactly.

Thanks for your reply
Unfortunately, neither one worked.
I tried the first one, however the flash tool didn't work because (OPEN_US_>NAO_US)
The second one would not download at all. I don't think it would have worked anyway since my phone is not the Alexa version. It's factory unlocked, purchased from Best Buy.

Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.

awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
I see, but I just want VoLTE to work. I don't mind using stock rom or custom rom too. So keeping that in mind what do you suggest? And also, Do you think that your solution " I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root! " could work for me too ? If so do let me know how did you figured that NAO_US was actually OPEN_US. Maybe I can find out one for AMZ_US.
On the box Model : G820QM
SKU : G820QM8 (QM8 stands for AMZ)
Thank you.

I'm really not sure how VoLTE works internally, so I couldn't tell you if using another firmware would actually work for you - but the way I found out one of the firmwares was actually OPEN_US was by extracting it using the KMZ extractor tool someone made. This is how I was able to reflash the partition on my phone that I screwed up on in the first place and created a brick with. Like I said, you could manually reflash all those partitions one-by-one in QFIL, but i don't recommend it as it may not even work and could potentially brick your device. It's really up to you in this case, if you'd like to try though:
Download the firmware you want to try, search for KZM extractor on Google, download QFIL and all of it's prerequisites, and finally the firehose.
Use the KZM extractor and place the firmware inside of it.
Once it is done extracting all the files, put your phone into download mode and open QFIL
NOTE: DO NOT FLASH THE PARTITIONS WITH 'OP' IN THEM! Your phone won't boot for sure!
From QFIL use the firehose file and manually, one by one, sort through the output files of the KZM extractor and find the partitions that match their name and flash them with the file.
Zero guarantees this will work, and you may end up with a brick for a phone at the end of the day, but if you're that desperate it just might work.

Hi there.
I am still looking for solutions for VoLTE to work. I googled a lot and came on this post " https://piunikaweb.com/2021/06/07/unlocked-lg-g8-thinq-now-supports-att-volte-after-april-update/ "
Mine is Amazon version "QM8". Yet I did received april update via OTA. But still no VoLTE. I can OEM unlock from devs. Can I flash AT&T "QM7" on Amazon "QM8" ?
What do you think of this please let me know.
Thank you

VoLTE seems to depend on files in the OP partition, so crossflashing other partitions but not OP will not get VoLTE to work. LGUP will not allow crossflashing.
See my experience to get working VoLTE and Wifi Calling: https://forum.xda-developers.com/t/lg-g8-volte-fix.4113291/post-85455109
You will need to be bootloader unlocked and rooted.

awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
Pls how to extract kdz,mine get error bad header

Question Steps to root

I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!

I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303

It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)

leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.

ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)

leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

i need fastboot driver for win 64

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?

Question Cannot update to C.47

Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.

Which phone version do you have?

luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120

skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.

luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?

Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.

luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.

skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/

luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.

skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.

luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing

I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....

If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.

luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....

TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.

luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!

To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!

TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!

luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,

I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.