Develop Bugs

Stuck in bootloop, can't flash

Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance

Bump in hopes of a solution

And another bump, any help would be greatly appreciated

I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.

bumping because I'm having the same issue, coming back to stock after having CM12.1

As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working

I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.

Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.

KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk

ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.

KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...

Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?

Unrooting HTC One M9 with S-On without backup

First of all, I really have to apologize for making this thread - after all the effort people here put to ensure that everyone could be able to handle their phones safely, after many hours of trials and errors, I have to ask for your help.
HTC One M9 that I'm dealing with here is S-On. I need to get the latest OTA update for it to update it with Android 6.0 - so forcing the update will be completely good solution.
Bootloader is currently unlocked and the phone is rooted.
It has currently firmware version 1.32.401.15 (Europe)
I am currently not able to flash the stock firmware I found here for my version through SD card, I'm guessing that one of the previously mentioned conditions could be prerequisite for this to work properly.
Any help would be extremely appreciated.

@KamilaS you have the WWE edition of the One M9 as far as I can see from your firmware number. I'd advise to download the RUU for your device and flash it via PC to go back to stock and apply the OTAs up to Android M.
Here you go:
1) download this RUU
2) reboot to bootloader and relock it
3) apply above downloaded *.exe
If you got any further questions feel free to ask!
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Don't use that RUU. That version isn't able to receive OTAs. You can find a RUU for the latest WWE firmware (2.10.401.1) in this thread. But there is no official Android M OTA at the moment.

Flippy498 said:
Don't use that RUU. That version isn't able to receive OTAs. You can find a RUU for the latest WWE firmware (2.10.401.1) in this thread. But there is no official Android M OTA at the moment.
Click to expand...
Click to collapse
I used it in the past and got the OTA to 2.10.401.1 without any problems.
Of course there always is the second option to use a RUU.zip...
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

HTCNerdYoda said:
I used it in the past and got the OTA to 2.10.401.1 without any problems.
Of course there always is the second option to use a RUU.zip...
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.

Flippy498 said:
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.
Click to expand...
Click to collapse
Weird as in my case everything went without any problems. But that's something one could dig into and be discussed in another thread.
Hope we help the OP first of all
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Flippy498 said:
I've tested every RUU for the SKU 401 when I created my TWRP backup collection and those for 1.32.401.15R2 and 1.32.401.17 were not able to receive or install OTAs.
Click to expand...
Click to collapse
Only certain regions got 1.32.401.17 update while rest stayed on .15

liam_davenport said:
Only certain regions got 1.32.401.17 update while rest stayed on .15
Click to expand...
Click to collapse
Yeah, I know that. I didn't want to get too OT in my last post. If I remember correctly only CID HTC__Y13 HTC__J15 got that update and since we don't know the OPs CID and all other ones cannot receive OTAs with that RUU I would say it's better not to recommend using that RUU.

Thanks a lot for such fast replies
Am I understanding then correctly, that locking again bootloader will be necessary to flash firmware?
In such case, will "fastboot oem lock" command in download mode be sufficient?

Re-locking is only needed if you want to flash a RUU.exe. The fastboot oem lock command would be sufficent in that case. But as said before I wouldn't recommend using the 1.32.401.17 RUU (which is the only RUU.exe for the SKU 401).
TL;DR: Don't relock.

I am not eager to use executable file to flash the firmware, .zip option would be great - either through SD card or fastboot commands. But seeing as I keep failing with the update through both options I am assuming, that I'm stil doing something wrong. Are there any other prerequisites that I haven't yet consider? Is relocking OEM not necessary then when using ZIP options?

Relocking is definitely not needed. Did you follow the instructions in my google sheet? If yes what kind of error was stated when you tried to flash the RUU in Download Mode? What kind of error was stated when the fastboot flash failed?

I have just tried once again with the RUU.zip file that I have found. I can see that your google sheet points to another RUU.zip file, that I will try next on the SD card and see if I have better luck with it.
In the meantime, this is the output that I have from trying update in fastboot:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
OKAY [ 1.003s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.009s
From what I googled, it can be avoided when updating through SD card, but then again the errors aren't very descriptive that way

KamilaS said:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2064449786 is not a multiple of the block size 4096
OKAY [ 1.003s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.009s
Click to expand...
Click to collapse
Which fastboot.exe are you using? Or better did you use the htc_fastboot? The first line of the error regarding max download size happens quite often if someone uses fastboot from Android sdk instead of htc_fastboot. htc_fastboot can be found in sneakyghost's thread.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Ok, thank you very much! With your help I was able to finally figure out the way that worked on my device
I followed your suggestion and used htc_fastboot - as expected, the fastboot that I have used so far with other devices was not the best solution here and I haven't really realized before that people could be using different one.
Together with the RUU file that you have linked in your google sheet (that for some reason could not be copied on SD card) I have managed to install firmware successfully on the device and now I'm installing the latest OTA update
Thank you once again for all your help, is there anything that I can thank contributors by liking their replies?

KamilaS said:
Ok, thank you very much! With your help I was able to finally figure out the way that worked on my device
I followed your suggestion and used htc_fastboot - as expected, the fastboot that I have used so far with other devices was not the best solution here and I haven't really realized before that people could be using different one.
Together with the RUU file that you have linked in your google sheet (that for some reason could not be copied on SD card) I have managed to install firmware successfully on the device and now I'm installing the latest OTA update
Thank you once again for all your help, is there anything that I can thank contributors by liking their replies?
Click to expand...
Click to collapse
You're welcome. That's what this forum is for.
No need to hit the thanks button. It's the thumbs up below the post

Help me root phone please - can't figure it out

Hello! I'm new to this forum but love the assist people lend others.
Now ofcourse I'm here because i'm struggling,
i cant get my phone to load a TWRP recovery..
i've been following the instruction of this vid: /watch?v=WuHFcGvUjwA and everything went as planned until 20:00 min of the vid, i cannot load or flash the recovery..
I've checked every single file there is to download for the HTC one M8 from the official TWRP website
it gives an error on the 1/2 recovery saying :
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
sending sparse 'recovery' 1/2 (15836 KB)...
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
OKAY [ 1.639s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.643s
now like i said - ive tried the newest version all the way down to the oldest one.
Although the versions 2.7.0.1 and 0.2 DO load or flash, as soon as i hit the recovery option in my bootloader is gets stuck on the HTC logo.
What i see in bootloader menu:
***UNLOCKED*** (since i've followed those steps unlocking my bootloader menu
S-on
Hboot 3.19.0.0000
[email protected]
OS-2.10.401.1
I also read something about using an SD card since my phone doesnt have enough room for it to flash the image, so i did buy a 32gb one, formatted it to be part of the phone and tried it all again, still no effect.
please see the vid, or skip through it to know my proccess and know where i am at atm.
Thanks you very very much in advance! every help is appreciated

Are you sure your device is M8 ?
Your details don't look like one.

ckpv5 said:
Are you sure your device is M8 ?
Your details don't look like one.
Click to expand...
Click to collapse
Yes, well it's a M8s.
but many downloads said it was for all types of m8

All type of M8 means applicable for GSM, Sprint & Verizon.
M8s is not regular M8, it's totally different device.
Check M8s section for your device version. One of the thread has TWRP for M8s.
http://forum.xda-developers.com/htc-one-m8/one-m8s-general
Any question, ask in that section.

ckpv5 said:
All type of M8 means applicable for GSM, Sprint & Verizon.
M8s is not regular M8, it's totally different device.
Check M8s section for your device version. One of the thread has TWRP for M8s.
http://forum.xda-developers.com/htc-one-m8/one-m8s-general
Any question, ask in that section.
Click to expand...
Click to collapse
Okay, i realise now that im in the wrong section of the forums - but if you could lend me some help it would be highly appreciated.
I now did the HTC_fastboot flash recovery twrp-3.0.2-0-m8.img and it loaded just fine, giving me the message:
sending 'recovery' (20046 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but when i go to bootloader and select recovery it still freezes at the HTC powered by.. logo
Any suggestions pls?

twrp-3.0.2-0-m8.img is for regular M8 only, won't work for your device.
You need something that read twrp-x.x.x.x-m8s-qlul.img
I think you can still use twrp-recovery-2.8.6.0-m8s-qlul.img to root ... available and all details are here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Important : When using this recovery, do not accept root offer by the TWRP .. you need install the latest SuperSU 2.76 because yours is Marshmallow.
http://download.chainfire.eu/supersu-stable
You can ask there whether they have any newer TWRP version for M8s.
I can't help much as I don't have this device .. sorry.

ckpv5 said:
twrp-3.0.2-0-m8.img is for regular M8 only, won't work for your device.
You need something that read twrp-x.x.x.x-m8s-qlul.img
I think you can still use twrp-recovery-2.8.6.0-m8s-qlul.img to root ... available and all details are here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Important : When using this recovery, do not accept root offer by the TWRP .. you need install the latest SuperSU 2.76 because yours is Marshmallow.
http://download.chainfire.eu/supersu-stable
You can ask there whether they have any newer TWRP version for M8s.
I can't help much as I don't have this device .. sorry.
Click to expand...
Click to collapse
Fixed it and got it all running now. thanks for the assist about needing the m8s twrp file, got that, used the HTC_fastboot flash recovery <recovery file name>.img and got it to work

LG G5 (H850) after update to 14.1-20170822-nightly-h850 bricked after second reboot

Hi, i installed the latest LG G5 Update (lineage-14.1-20170822-nightly-h850-signed), the first regular reboot was fine.
The second reboot has "bricked" my phone.
Please check the attached Picture from the phone.
Anyon a idea how to get back the phone to "life"??? :crying:
Thank you in advance for any assistance
MoPhat

This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.

Thank you marco-v
I can't check the crc from the file because i have updated the latest Version with the build in update function...
I have tryed to boot in the recovery menu by pressing the power und volume down button, realising when i see the lg logo an pressing again both to (normaly) enter the recovery mode. it appears the same message
http://androidflagship.com/20275-boot-lg-g5-recovery-mode
the only menu that Comes are the "factory data reset" menu, but this makes no difference...
any further ideas?
marco-v said:
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Click to expand...
Click to collapse

So it looks like your Recovery mode is messed up too? Not sure how that might have happened unless you instructed LOS to "Update Recovery" .
Have you tried to see if you are able to enter fastboot mode and reflash your custom recovery image again and try to enter Recovery mode again? The one I use on my device (Oppo Find 7) is a TWRP image and I find it very reliable.
You can see if you can boot to Recovery by running the following command from fastboot mode (assuming you have a TWRP image)
fastboot boot twrp-x.x.x-x-h850.img
Replace x.x.x.x with the version of the file.

Tryed, result is:
Code:
C:\Temp\root_H850>fastboot boot twrp-3.1.1-0-h850.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.451s
With "adb.exe devices" are the phone not listed

Ok, my device is locked!?!?
Code:
C:\Temp\root_H850>fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.456s
So i have tryed to unlock the device again with the unlock key i get:
Code:
C:\Temp\root_H850>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s
How can i disable the " Enable OEM unlock" in the developer Settings without a gui???

Ok, fastboot works, that's good but it looks like your bootloader is locked again.
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Try following these instructions: https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 and see if you can get TWRP running and if you do, you can try flashing LOS again but format data + system (you will lose all data) and if you are not careful, you might lose data on internal storage + external storage so read carefully what's displayed on the screen before going ahead.
Also: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS and this will show you how to unlock your bootloader.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
I just read your post, you can try:
fastboot oem unlock
and see if it works. May be it will because it was unlocked already once but can't tell for sure.

Sorry, nothing has worked.
I will try set "upgrade error" back in the lg update tool to flash the original firmware, but i need a SERIAL or the IMEI number, how can i find this out?

Normally, IMEI numbers are located right under the battery on phones that come with removable back covers and batteries. Yours however slides out, it might be somewhere there or perhaps you can check the box / packaging. So the following command didn't work?
fastboot oem unlock
What's the error you got? The official bootloader instructions on LG's website should have worked as it supports your model. To me the only issue you seem to be having is a restricted booloader and once you unlock it, everything should be fine. This is why you can't boot into TWRP using the boot command.

Not worked, the result is:
Code:
C:\Temp\root_H850>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.025s

I see, thx, if the LG official unlock instructions did not or no longer work followed by the instructions here https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047, I am out of ideas. Perhaps someone else can help and provide further hints.

HTC 10 UK Version

Hi, i have HTC 10 UK Version. OS 2.41.91.31 Rooted S-ON. i accidentally delted my internal storage and Rom in TWRP. I have backup in SD CARD but it is not workin when i restore it just stuck on HTC logo then reboot and in a loop.
Any help?

Em.. How you can accidentally click internal storage and System?
Nevermind. If you restored system successfully and it's stuck in htc logo then... I think you deleted something else too and the best option is restore full system image or RUU. It's my opinion and i can be wrong. I have only oreo images unfortunately and with .401. so i can't help you maybe someone else have backups of nougat rom.

Hi, thanks for responding. I amnot very expert in Roms etc. You can give me oreo image that wiill be fine. I can't find any RUU for this model. I just want it to get it work again.
HTC Dev website nly has kernals for EE UK HTC 10. There isn'ta anything else on whole internet. In XDA i found a stock recovery for this model EVE__XXX. Which caused this issue.

imDCStar said:
Hi, thanks for responding. I amnot very expert in Roms etc. You can give me oreo image that wiill be fine. I can't find any RUU for this model. I just want it to get it work again.
HTC Dev website nly has kernals for EE UK HTC 10. There isn'ta anything else on whole internet. In XDA i found a stock recovery for this model EVE__XXX. Which caused this issue.
Click to expand...
Click to collapse
That stock recovery didn't caused this issue. You yourself caused this issue.
You need a RUU 2.41.91 or a higher one (example) 3.16.91. I know firmware gem flash (website) holds many RUU's..... have a look there and pray they have it.

Mr Hofs said:
That stock recovery didn't caused this issue. You yourself caused this issue.
You need a RUU 2.41.91 or a higher one (example) 3.16.91. I know firmware gem flash (website) holds many RUU's..... have a look there and pray they have it.
Click to expand...
Click to collapse
You mean this. Will this RUU work. https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2035

imDCStar said:
You mean this. Will this RUU work. https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2035
Click to expand...
Click to collapse
No 2.41.91. I don't see any. 2.41.91 in any of those files, please read well. No idea how you came up with those. When i type your OS number i get a instant hit.
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51637

Mr Hofs said:
No 2.41.91. I don't see any. 2.41.91 in any of those files, please read well. No idea how you came up with those. When i type your OS number i get a instant hit.
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51637
Click to expand...
Click to collapse
Got it. I cant make payment using my Credit Card as there is no option there. Can you help. I do not have paypal.

imDCStar said:
Got it. I cant make payment using my Credit Card as there is no option there. Can you help. I do not have paypal.
Click to expand...
Click to collapse
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved

Mr Hofs said:
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved
Click to expand...
Click to collapse
Downloaded the firmware flashing in downloadmode using SDCARD. Getting 22 RU_HEADER_ERROR :crying:

Try download again, check md5 of that file. It can be something wrong with that downloaded zip.

Mr Hofs said:
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved
Click to expand...
Click to collapse
ShadoV90 said:
Try download again, check md5 of that file. It can be something wrong with that downloaded zip.
Click to expand...
Click to collapse
Ok checking and re downloading.

I was trying to flash using ADB Fastboot getting this error.
JUST TO MAKE SURE
DEVICE: HTC 10 UK EE VERSION
SYSTEM MODIFIED, S- ON - Bootload UNLOCKED.
OS: 2.41.91.31
Problems:
- Htc logo reboot loop even from stock TWRP Restore.
- Cant flash any rom successfuly.
ADB Log
C:\adb>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
OKAY [ 1.023s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_l
(bootloader) 3gExy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.346s

imDCStar said:
I was trying to flash using ADB Fastboot getting this error.
JUST TO MAKE SURE
DEVICE: HTC 10 UK EE VERSION
SYSTEM MODIFIED, S- ON - Bootload UNLOCKED.
OS: 2.41.91.31
Problems:
- Htc logo reboot loop even from stock TWRP Restore.
- Cant flash any rom successfuly.
ADB Log
C:\adb>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
OKAY [ 1.023s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_l
(bootloader) 3gExy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.346s
Click to expand...
Click to collapse
No idea why it's not working, the ruu should be fine. Did you download the full RUU right ? Not the firmware.....those are 2 different things.
If you want your phone up and running at least i have a custom rom that will work. At least for now so at least you can use your device again.
https://www.androidfilehost.com/?fid=1322778262903991031
Flash that with TWRP and your phone should boot up. I'm brainstorming when i have more time. But the full RUU 2.41.91 (around 2 gig) should do the trick.

Mr Hofs said:
No idea why it's not working, the ruu should be fine. Did you download the full RUU right ? Not the firmware.....those are 2 different things.
If you want your phone up and running at least i have a custom rom that will work. At least for now so at least you can use your device again.
https://www.androidfilehost.com/?fid=1322778262903991031b
Flash that with TWRP and your phone should boot up. I'm brainstorming when i have more time. But the full RUU 2.41.91 (around 2 gig) should do the trick.
Click to expand...
Click to collapse
Yeah i downloaded the RUU. It a zip with some zips inside it. around 1..8gigs there are two RUUs on https://firmware.gem-flash.com/index.php?a=search&b=2.41.91.31 I downloaded the first one.
The link you provided is showing 404 error.

"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.

ShadoV90 said:
"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.
Click to expand...
Click to collapse
I see the combined signed and the signed indeed, i did offer somebody else here at xda some assistance and sent that user to gem flash too and he flashed a combined signed version to its S-ON unlocked device so i assumed this would be appropriate too now.........but then again assumption is the mother of all f ups........
In my humble opinion signed is signed, combined or not. So that would not be the issue here. I had another case lately where the absolute correct RUU didn't flash and up to today i still don't know why
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
imDCStar said:
Yeah i downloaded the RUU. It a zip with some zips inside it. around 1..8gigs there are two RUUs on https://firmware.gem-flash.com/index.php?a=search&b=2.41.91.31 I downloaded the first one.
The link you provided is showing 404 error.
Click to expand...
Click to collapse
My apologies, link is fixed......was a typo

ShadoV90 said:
"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.
Click to expand...
Click to collapse
I redownloaded and checked MD5 for both files. It is same. Can you please guide how to S-OFF

I understand. You are more experienced than me, so probably you are right.
But don't hurt trying:
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51635
Maybe this just signed file will be good...
EDIT: In order to be S-OFF you need working system, and sunshine app (and 25$ because S-OFF is paid feature), so it's AFAIK impossible for you at this time.
I am trying to figure out solution for this situation... if just signed file won't work.

ShadoV90 said:
I understand. You are more experienced than me, so probably you are right.
But don't hurt trying:
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51635
Maybe this just signed file will be good...
EDIT: In order to be S-OFF you need working system, and sunshine app (and 25$ because S-OFF is paid feature), so it's AFAIK impossible for you at this time.
I am trying to figure out solution for this situation... if just signed file won't work.
Click to expand...
Click to collapse
Already gave a link to a working (custom) rom. Sunshine should work with it. If not we will find another stock like rom to enable sunshine.

Mr Hofs said:
Already gave a link to a working (custom) rom. Sunshine should work with it. If not we will find another stock like rom to enable sunshine.
Click to expand...
Click to collapse
Downloading rom. I hope this one works. I tried another custom OREO rom. It installed but same loop on boot logo. After i cant flash anything even cant restore backup using TWRP. (Backup used to restore fine earlier but loop on boot logo)
This device is getting worse and worse. I hope this Rom works. Lets see. Thanks for helping out. I will give feedback after flashing it.