I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Kyuubi10 said:
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Click to expand...
Click to collapse
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
nerodarknight said:
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
Click to expand...
Click to collapse
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Kyuubi10 said:
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Click to expand...
Click to collapse
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
nerodarknight said:
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
Click to expand...
Click to collapse
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Kyuubi10 said:
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Click to expand...
Click to collapse
Doesn't not seems to work, formatted the system partition but it still failed
If this is any help, I successfully converted it to WWE but since I got a bug with the service : LTE (data) is good but no call or text whatsoever so that's why I'm trying to convert back, flashed the firmware zip and then restore back up. The firmware zip worked out fine but the restore always failed. To add to that, when I'm on WWE firmware I can restore the WWE firmware backup just fine.
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
nerodarknight said:
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
Click to expand...
Click to collapse
I believe TWRP should be capable...
Google for a guide.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
I have the same problem this happened after I formatted the date to blink rom
How can I solve this problem after I tried to install the rom maximos hd and I did not succeed I returned my bachup from the stock more now this giving error in the horade do the same I am with bild 2.41.401.3 cid HTC__M27 mid 2PS62000
Can someone help me please ???
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.