Develop Bugs

[Q] One M8 LRA soft brick issues

Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.

promsos said:
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
Click to expand...
Click to collapse
Did your firmware.zip have a boot*.img in it? You probably need the old version of the boot.img to match the old software. You might want to find on of the old Verizon RUUs and extract the boot.img from there and try flashing that in fastboot. Message me if the Verizon boot doesn't work for you, I might have some other ideas. I'd say be careful, but you're already in trouble.
Edit: You could also do a nandroid backup and try a custom ROM to get it functional in the short term.

I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.

promsos said:
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
Click to expand...
Click to collapse
The boot.img from an older Verizon RUU would probably work, but you might have to try a couple to get the right one. The boot.img is directly tied to the ROM version that is installed, and is often called the kernel and tells the system how to boot the ROM.
Make sure you do a backup of your working Viper before restoring the stock one and trying to flash a boot.img.

I don't understand why you re locked the boot loader and flashed a firmware zip just to revert to stock recovery? All you had to do was pull the stock recovery from the firmware.zip in the OTA then flash it via fast boot. Then go ahead and flash the OTA.
You need to now find and flash a compatible boot.img. Just keep trying different ones until it boots.

I'm making a little progress here, thanks for the help. I downloaded a 4.4.3 Verizon kernel, loaded that (after restoring the old nandroid backup) and I'm able to boot, whew... I'm having two issues now, 1) my wireless won't turn on for some reason and 2) I tried installing the 4.4.4 OTA update my carrier released (downloaded via 4G) and it won't apply - I was hoping successfully applying this OTA would fix the wireless issue. Looking at my software version it looks like I'm actually running 4.4.2, could that cause both of these issues? I'm trying to locate a 4.4.2 kernel to load but figured I'd toss out the question in the meantime.
Ashyx - I wish I had a better answer to why I temporarily relocked the boot loader and flashed firmware.zip other than desperation (trying to get that darn OTA). It was a while ago I flashed the firmware.zip file but I thought that when I initially extracted the recovery from the zip file and flashed it I could no longer boot into a recovery, maybe I'm making that up though - I can hardly remember last week lol. I'm an IT guy, so I'm not completely clueless, but I'm far from proficient with mobile technologies, as I'm sure you gathered already.
Anyways, I'd appreciate any insight, in the mean time I'm going to keep hunting for a 4.4.2 kernel to try on this thing. Thanks again to all.

http://forum.xda-developers.com/showthread.php?t=2723159
Try the zips from here, they should have a boot.img for 4.4.2.
Sent from my One M8 using XDA Free mobile app

Ok, I think I'm back up and running. I was able to find a 4.4.2 boot.img that allowed me to once again use my wireless. After getting the wireless working I had to find valid versions of flashlight.apk and calculator.apk to put in data/preload and the OTA finally took....success at last. I really appreciate the help durgis, I'll be grabbing a nandroid of my now working phone right away so I don't run into issues in the future. Again, thank you for the help, very much appreciated.

I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.

rook79 said:
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
Click to expand...
Click to collapse
Hey rook, I do have the same CID, are you on Cellcom out of Wisconsin? I didn't grab a bare bones nandroid, but i can do a backup, uninstall my apps and do one, or rebuild mine from my unbootable one now that I have everything i need. If you want to try a different ROM you could try Viper, it worked decent for me, just a few quirks when i bounced from wireless to 3G for some reason.

I am with Cellcom. My problems started with the recent OTA update. The update wouldn't take, because of the flashlight.apk. I decided it was time to root this phone anyway and try some custom roms. I've done it with my other HTC phones in the past with no problems. Unlocked the bootloader, loaded TWRP and did a backup. Didn't check where the backup was being put and ended up saving it to internal. Put on a new ROM and wiped my backup. Cyanogenmod 11 is the only ROM that I've had success with. Every other rom that I have tried so far will not complete the initial boot. I suspect that I'm missing something stupid, or it has something to do with the OTA update not completing. Are you running Viper, or did you get the Cellcom OTA update to work?

I was running Viper for a while but now have my phone reverted to stock with the 4.4.4 OTA applied. If you want a nandroid of stock Cellcom 4.4.4 I can work on one for you, it may take a couple days to get it but I should be able to get one.

That would be awesome. I've been looking for a stock Rom for a while now. As you know those are nearly impossible to find. Not having a stock nandroid backup or the OTA update zip kind of put me in a SOL position. Thanks for your help.

Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0

That worked awesome. Thanks!!!

Hi Guys, (@rook79 , @promsos)
i have the same model and running into similar problem, i was also not able to flash any other rom than SkyDragon, wanted to be able to flash other roms but no luck, i thought its the firmware that wont let me install so i went for S-Off and flashed one of the firmware from verizon, since there was not much help for this specific model and everyone was referring it as a variant from verizon, i did flash one and my problem started, my phone had no signals after flashing the firmware and was still not able to flash any other ROM, i flashed couple of more firmwares and radios to get my network working but no luck, and i got a new problem that the phone keeps rebooting after a couple of minutes it loads into system.
then somebody helped me with the stock firmware 4.4.4 from here and nandroid from this thread, firmware was still verizon, i managed to restore it but still the same reboot issue and no signals, but i was able to download OTA which wont install, everytime i try to install it, it goes to stock recovery with a progress bar 1% filled and then stuck into boot loop and after n number of attempts it boots into system, where again it reboots after a couple of minutes.
extracted the firmware from OTA and manually flashed it and tried to install OTA but still same, i tried to reboot into stock recovery but every time i do that, it goes to black screen and then keep rebooting, i am not able to get to that red triangle screen.
help less clueless trying to find complete RUU for it (not sure if thats going to help)
my partition table has 2 vzw partitions as well because i flashed dottat's RUU for verizon.
can you guys help me with that?
my phone is m8_wlv CID: LRA_001 MID: 0P6B20000
s-off, and i am on a GSM network (not US).

promsos said:
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
Click to expand...
Click to collapse
I'll appreciate if you share the 4.4.4 OTA, I really need it now.

hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
is this what you are looking for? https://www.dropbox.com/s/2oozc291kwe5l9r/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip?dl=0

hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
Hi
Do you still have that LRA version?? I need some help

[Q] Frustrated Xperia Z1C T-Mobile UK owner.

Hi,
I have the CDA 1280-7858 Sony Xperia Z1 Compact model. I have yet not been able to upgrade my phone to latest lollipop, since T-mobile UK have not released it yet.
My phone is carrier unlocked, but bootloader CANNOT be unlocked, this leaves no possible way for me to add a custom rom , right?
What are my options here? Sit and wait forever or just get a new phone?
As you can see in the attachment, only T-mobile remains on the 14.4.A.0.157 release in the UK carriers.

You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.

templeka said:
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
Click to expand...
Click to collapse
Ok, but this would erase my phone completely right? i would use flashtool to upgrade?
Is t here any reason why its taking so long to get the OTA update? I mean, optimally, i want that one and not really need to bother to reset the phone entirely for this update.

You can always make a backup in recovery (I'm thinking you have a recovery already) just in case you don't like lollipop (I didn't). You lose any app installed and preferences (for sms u can backup those and contacts you can sync with Google account) so you will have to reinstall those. If you want root for your phone you need one of those prerooted ones and those are flashed from recovery usually. Best thing is to read the instructions in those threads.

I don't have recovery mode i think. Since this comes with unlocking bootloader, which i CANNOT on my phone.. (its not possible, not even paid with jinx13).

You don't need unlocked bootloader for recovery. Just go here http://nut.xperia-files.com/ and browse to XZDualRecovery > XZDualRecovery 2.8.15 > Z1C-lockeddualrecovery2.8.15-RELEASE.installer.zip and install that from your PC (with the phone connected to your PC via USB). I think you need to enable USB debugging before doing this and you definitely have to be rooted. You should read around how to install stuff there are some guides and resource threads in General forum.
Edit: Also get the flashable version and store it somewhere safe on your phone. Anytime you flash a new ROM you need to also flash the recovery else you have to connect phone to PC and do the install version and that takes longer.

Thanks templeka, I have been unsuccessful in any attempt to root this phone also.. What would be the best way? it just seems to be locked in all ways possible for me to get this done.
edit: i tried the towelroot selection 3 from file you suggested.. it just stopped after libdvm opened (loljavasucks), and after reboot, i was unable to enter recovery mode. (pressed volume up or down, and there was no light on any diode, at any time)

You need to flash a stock .108 rom, root and install dual recovery.

Towelroot will not work on v157. Follow the guide here http://forum.xda-developers.com/showthread.php?t=2977774
In short you need to flash v108 kernel, root and flash v157 kernel back with Flashtool. Be sure to install the necesary drivers after installing Flashtool (they are in the folder where you installed it).

Sorry for being noob still.. But how do i enter flash mode now? I mean reboot and holding volume down will only enter Safe Mode of the phone. (i think its because i have the wrong kernel?)

Just when i was about to give up.. 14.5.A.0.270 just released on t-mobile.. FINALLY!

HELP!! Potentially bricked my m9

Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!

anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?

Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.

Bought Zenfone 2 Z00AD from AmazonUK... but OTA doesn't work

Right... so, I think I traced down why OTA doesn't work.
Namely, whenever I click on system update to search for update, it searches, but nothing happens.
Online I found that this is likely because a WW custom ROM was flashed... and so OTA doesn't work.
My phone is brand new (got it today actually), but 'stuck' on Android 5.0 (ugh).
So... I would like to ask for the recommended course of action so I can get either latest OTA, or just install a stable and up to date clean Android ROM (without all the Zen bloatware) that works.
Also, I'm relatively new with flashing this phone and there's tons of info on rooting, different CWM and TWRP's, etc.
Problem is, which ones to use?
How to determine if you're using the right one and avoid bricking the phone in the process?
My phone arrived with SuperSU... which would indicate it's been rooted (and I was able to install AdAway).
So bearing that in mind... what would you recommend?

Your phone should not be rooted when bought in a store. So it seems to be used before, and not correctly refurbished.
Anders
As there is no possibility to get evidence that you did not do that yourself, you can only hope to get a replacement from the vendor,or any warranty.
On the other side: the device is already rooted, so you can flash a 6.01 rom yourself.
Depending on the way the phone was rooted in the first place, OTA will not always work.
I did see an original rom surface recently. With that you can go original, Unrooted and locked, so the vendor will not be able to void your warranty claims.
Verstuurd vanaf mijn ASUS_Z00A met Tapatalk

Sorry for the late reply.
Was busy.
The phone was bought off Amazon UK, and no modifications to the device were done by me apart from installing my apps.
Trouble is, I don't know how to flash a new ROM onto this thing.
The forums are overflowing with information which is all over the place and it is extremely confusing.
Yes, I tried the search function and found some info, but it is all over the place.
I have to be able to figure out the original firmware apparently if I want to flash the CWM or TWRP... and in some cases, flashing TWRP can break the device it would seem (what's up with that?), and I cannot figure out the original firmware because the mobile was not delivered with one (a custom WW ROM was apparently flashed on top of I don't know which version), and I really do not know where to look for this.
So, I'm very confused.
There's too many threads to sift through and each seems to be giving its own unique information and a list of no no's which appear to contradict each other.
I could use some help in sorting through this 'mess' (well, 'mess' for me) so I could try at least flashing the original ROM and get OTA (for which I require concise instructions).
Also, something else seems to be happening... Asus Zentalk forums appear to refuse to load on my laptop for whatever reason.

Settings>About - will show you what rom you have.
I would recommend unlocking bootloader 1st as this seems to have helped me. If you have any recovery but stock or have a white splashscreen then this has already happened... I used the unofficial unlock tool to do this and thus my imei numbers stays off the "no warranty" list..
If you go to the pre-rooted rom thread you can download the newer stock roms. These also have the recovery, boot and droidboot.img files included with the .rar file of a system.img (unrar it of course)...
I believe it may also contain the flashtools, if not look at the CN to WW thread...
Using fastboot you can flash these onto your phone using commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Make sure, if do this the commands are correct. Copy and paste can be your enemy because if you use the same command and just overwrite your boot/droidboot or recovery every time you flash, it may result in a brick...
Good luck and happy flashing...
I seem to get OTA's pushed now..

Tnx.
Now that I look back, it doesn't seem too complicated.
My bootloader seems to already be unlocked though.
One other thing... about flashing that system.img
I think I stumbled upon similar instructions before, however, I couldn't find system.img file (everything else was accounted for).
Also, does the the procedure for flashing new ROM's or possibly just OTA's require repetition of ALL those commands, or just some?
Oh and I was able to access the stock recovery (which the seller said he used to flash the custom WW rom). Could I use it to update OTA's manually? And would I need to first unroot the mobile?

[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