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

Flashing ONLY the newest baseband on custom rom

I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.

McFlypants said:
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
Click to expand...
Click to collapse
I'm running the original bootloader and baseband from 6.0.1 without any issue, so I would suggest leaving it.

I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.

McFlypants said:
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
Click to expand...
Click to collapse
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you

Good one, flashallthetime
Back in, uh, I think Atrix time or even HTC Desire it was normal to flash/change radio baseband. It supposed to improve radio, prolong battery life... In reality, most of the time didn't do anything, sometimes broke something...
So in theory, you can do that. Should be fine but I wouldn't recommend.
If you have to, to get VoLTE, I would make a backup of the current rom, follow guide to flash back to stock and then restore backup. But be extremely careful, so many users over here bricked their devices. As far as I can see, downgrading and the accepting OTA.
Sent from my LG-V940n using Tapatalk

flashallthetime said:
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Click to expand...
Click to collapse
Good idea, please return it to me afterwards if it's working! :good:

Motorola specific flash questions

Hi, bear with me, new at Motorola.
1. What are the slots A and B that we have inside TWRP? How to flash a ROM "inside" of both slots (as it is written in some sites)?
2. Can we upgrade an unlocked bootloader? I mean, phone starts at 7.1.1, we unlock, how to get the 8 (oreo) bootloader?
3. When we move to Android P, can we upgrade an unlocked bootloader to the next Android version?
4. Does rooting affect the OTAs? If so, what should we do to get them?
Thanks.

Technical said:
Hi, bear with me, new at Motorola.
1. What are the slots A and B that we have inside TWRP? How to flash a ROM "inside" of both slots (as it is written in some sites)?
2. Can we upgrade an unlocked bootloader? I mean, phone starts at 7.1.1, we unlock, how to get the 8 (oreo) bootloader?
3. When we move to Android P, can we upgrade an unlocked bootloader to the next Android version?
4. Does rooting affect the OTAs? If so, what should we do to get them?
Thanks.
Click to expand...
Click to collapse
1. Slots are only for seemless updates. Don't worry about anything else. Just flash once and reboot.
2. What? Just flash all to stock and you can update to Oreo. You need to OTA.
3. Same as above: through OTA.
4. Yes. Any modifications to any petition besides /data will cause OTA failures. Just use a "back to stock" method to get OTAs to work.

Technical said:
Hi, bear with me, new at Motorola.
1. What are the slots A and B that we have inside TWRP? How to flash a ROM "inside" of both slots (as it is written in some sites)?
2. Can we upgrade an unlocked bootloader? I mean, phone starts at 7.1.1, we unlock, how to get the 8 (oreo) bootloader?
3. When we move to Android P, can we upgrade an unlocked bootloader to the next Android version?
4. Does rooting affect the OTAs? If so, what should we do to get them?
Thanks.
Click to expand...
Click to collapse
1. The phone has dual slots for seamless updates, when you apply an update it goes to the other slot and is optimized and checked. Then it is booted, in theory one slot should always be a build behind, but that wasn't well thought out and has caused problems (good job moto). If you're thinking dual boot two roms, probably won't work as the data is shared by both slots and **** will ensure if two different roms try to play in the same sandbox. A lot of the zips around here flash to both slots to avoid that problem. In short, it shouldn't be tampered with unless you have a reason and know what you're doing.
2. An unlocked bootloader is unlocked until it is relocked (not advised) or unless moto ****'s itself and relocks itself. It has happened before. To upgrade to oero, as long as you are bone stock you can update OTA. If not, you can check this thread and download the appropriate files and do it manually.
3. In theory yes. If moto releases an update for us or if our devs build it.
4. If you root or flash a custom recovery, anything that modified the original checksums then OTAs will fail. If you want OTA then you need to be bone stock and you should check this thread.
---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------
Uzephi said:
1. Slots are only for seemless updates. Don't worry about anything else. Just flash once and reboot.
2. What? Just flash all to stock and you can update to Oreo. You need to OTA.
3. Same as above: through OTA.
4. Yes. Any modifications to any petition besides /data will cause OTA failures. Just use a "back to stock" method to get OTAs to work.
Click to expand...
Click to collapse
lol you're always a step ahead.

Many thanks for the responses.
But I'm really afraid of bricking my phone. I've done this before with 2 Motorolas...
User had a Moto Z2 and just after entering it (Android 7.1.1), go flashing DU (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce) followed by TWRP.zip according to the guide. Phone bricked and the user can't even go to flashboot mode.
How can we solve it? I mean, Asus has FlashTool to recover a dead messed phone (even partitioning it, even if you cannot boot or get into recovery, or flashboot). Samsung has ODIN. Can RSELite do the job? As far I could read, you need, at least, get into flashboot mode. If something messes, you're locked out. Is it right?
Anyway, as far I could read about, both slots must be at the same Android version, otherwise, phone does not boot.
How to "flash to both slots" one after another?

Has anyone been able to get fastboot access on the G710VM with Android 9.0?

So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?

Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303

In the same guide post if you look on page 6 you will find how people have updated to pie retaining fastboot.
It can also be used to use a pie vm rooted stock rom also.

MaitiuD2 said:
Out of appreciation for all the work that everyone in this community does (I read lots but don't post often) I would say, you need to search and skim through at least an hour worth of posts to find that answer, but I'll link it here to say thanks. Short answer- PIE loses Fastboot commands. You can flash to Oreo, and then you should be able to use fastboot commands. I still haven't found a posted method for installing TWRP. I just acquired an 'unlocked' Sprint model with the ULM firmware and would love to explore rom options.
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Click to expand...
Click to collapse
Thank you very much for responding.
And that really sucks about fastboot and Pie, now I have to wonder how LameMonster82 did it in his guide . Someone else there tried installing that TWRP from Oreo, and got his phone bricked for it.

Halogen_03 said:
So, I picked up a used G710VM 64GB Storage/4GB RAM, I specifically wanted this model because I'm on Verizon and wanted to ensure that my phone would work with their wack-as-all-hell network. Upon booting it up on the stock firmware for the first time, and intentionally not putting in my SIM, nor getting it online, I saw it using up 16 GBs of storage right out of the gate, and about 2.8 or so GBs of RAM. I thought this unacceptable, and so began my journey of putting custom ROM on it.
I was looking at putting either Lineage OS or AOSP, but both guides require getting TWRP on there first, and that has been my hang-up.
I followed this guide on getting the bootloader unlocked, and got that done.
Now my problem is fastboot mode, with the bootloader unlocked, and on the G710ULM11g firmware, I can get into it just fine. But on the G710EM20b, G710EM20d, and G710ULM20d firmwares I follow the steps to get into fastboot mode, get a warning about the bootloader being unlocked, and then it just does a proper boot up into the OS, every. single. time. And I've gone back and forth between my 8.0 and 9.0 versions of Android a few times, and confirmed it's only the 9.0 ones that are giving me this issue, the 8.0 one lets me in without fail.
Did I unlock the bootloader wrong? Or am I just using the wrong firmware? Has anyone else had luck with a G710VM version of the phone? Or did I hose myself by not buying a ULM or EM version?
Click to expand...
Click to collapse
Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot.

"Weird, I'm using G710EM20d firmware on my G710ULM and it boots to fastboot."
-----------------------------------------------------------------------------------------
I have the ULM model as well but the G710EM20d Model doesnt boot to fastboot. Could you tell me the KDZ file you used?
Example, "G710EM10b_00_0521.kdz"
I'd really appreciate the help

u should cross flash the ulm firmware by lg up and then boot ur device in to the download mode after erase laf partition

Warranty problem: Flashing to stock Nougat from a custom Pie rom

Hi folks,
I searched the forum and did not find a suitable thread that answered my question.
My Moto G5 has a charging problem and I want to give it back for a repair - it still has warranty.
I have read that flashing a custom rom does not necessarily invalidate the warranty, but to ensure that Motorola will repair the phone I would like to flash a stock (nougat) rom.
Is it possible without the risk of losing IMEI or other stuff?
Or do you recommend to send it back to Motorola with the custom rom installed?
Thank you VERY MUCH in advance!!!
Kind regards
Wolf

They will be able to see you have unlocked the bootloader regardless of whether you re-lock it
Just download the latest stock firmware and flash it via fastboot
If your base firmware is already oreo you can skip flashing gpt and bootloader to avoid risking hard brick
Don't downgrade your base firmware eg if it's oreo don't flash nougat (base firmware is stock firmware not custom rom)
I would flash it back to stock rom so at least they can't blame custom rom

Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...

moped2000 said:
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
Click to expand...
Click to collapse
Yes flash android 8 - note if it was never updated to android 8 you will also have to flash gpt and bootloader as well the rest of the firmware
You will need to flash the firmware via fastboot
Flashing via twrp is just like flashing a custom rom with no modifications & you will still have twrp installed and not stock recovery & still have a modified system partition etc

Thanks! Android 8 was definitely installed, only possibly not as stock firmware, but only as custom rom.
But I guess it's okay if I just flash all the files to make sure?

Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.

moped2000 said:
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
Click to expand...
Click to collapse
Depends what country you are in
In America or Europe you can argue and would most likely win in court that if your issue is totally unrelated to the unlocking of the bootloader they must repair it
Eg if the camera doesn't work because of a faulty component they must fix it
However if the camera stop working because you unlocked the bootloader & did some modifications causing it to no longer work then you're not covered
This would be the same for boot issues - If your phone no longer boots and you have unlocked the bootloader they can claim you have done a modification that now stops it booting
The general rule is if you unlock the bootloader than software/firmware booting issues are not covered but hardware faults unrelated to a bootloader unlock are
Again it varies depending on your country but the above is true for USA & the majority of Europe (EU)