Develop Bugs

HTC One M8. Is it possible to update to Marshmallow?

Hello i currently have HTC One M8, Software Version: 4.18.720.8 & Android Version: 5.0.1
I have OTA_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.10-4.18.720.8_release_449296.zip but when i try to install this update from recovery by using "Apply from phone storage".
I kept that file in internal storage as well as tried to rename it to update.zip but error keeps showing:
Code:
E: Find no match PARTITION: for package path /data/medai/0/pt.zip
E: unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package...
Opening update package...
E: failed to map file

M9 failed to mount partitions

HI
I have a HTC one M9 hima. Lastly, it has suddenly rebooted. I have not use it.
But it have not stuck in boot. It has boot to the withe Logo screen then go off and boot again, again and again.
If i push power + vol down, the Black screen with e HTC logo comes and the loop go faster.
The only way to come to the bootloader ist to push power + vol down + vol up.
From there i come to the recovery or download Mode. I have twrp installed.
In twrp i discovered that some Partitions can not mount:
mount: mounting /dev/block/mmcblk0p65 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p67 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p36 on /devlog failed: Invalid argument
mount: mounting /dev/block/mmcblk0p50 on /carrier failed: Invalid argument
mount: mounting /dev/block/mmcblk0p69 on /cota failed: Invalid argument
mount: mounting /dev/block/mmcblk0p68 on /preload failed: Invalid argument
mount: mounting /usb_otg on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
I tried:
- wipe Data --> mount error
- formate Data --> mount error
- flash new rom --> mount error
- install new Firmware --> requiret new start then loop
- mount manuel over adb --> invalied argument
- e2fsck /dev/block/mmcblk0p* --> bad magic number in super-block
- flash rom with fastboot --> invalid zip file
- new recovery --> after flash and boot to recover: exist old recovery <-- with dd, twrp and with fastboot
- twrp repair or change File System --> mount error
- twrp resize File System --> end with ERROR: 8
- twrp Change File System --> ERROR: 8
pls help me!!
sorry for my bad English

anyone here who knows the solution for above errors please? coz it did happen to me also. Thanks XDA for your help.

my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".

Radianer said:
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Click to expand...
Click to collapse
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"

kmx0101 said:
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
Click to expand...
Click to collapse
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.

shivasrage said:
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
Click to expand...
Click to collapse
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?

kmx0101 said:
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-m9/help/download-modepossible-fix-t3555678

How to Unbrick SM-A720F ?! (FRP = On) | E:failed to mount /efs | Combination not work

Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!

same problem
My phone also same problem
1) i try to solve from twrp but any rom flashing time - E:failed to mount /efs (Invalid argument)
2) i flash from odin its showing pass but till now mobile booting not complet.
3) i tryied from smart switch also s/n not correct.
please help me before i was used hadesh rom.
SM-A720f/ds
Android IR said:
Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!
Click to expand...
Click to collapse

Unable to install ROM via TWRP.

Tablet is reporting " E: unknown command [log]
E: Error executing updater binary in zip "/sdcard/lineage-15.1-20180815-UNOFFICAIAL-flo.zip"
E3004: This package is for device: flo; this device is .
WTF?

nvm. I figured it out. old TWRP.

[SOLVED] Unable to flash a rom or restore after motherboard replacement (t700)

Hello,
My tablet had a battery drain problem so I changed the motherboard and tried to install lineageos 14.1 again.
After replacing the motherboard, I turned on the tablet to activate usb debugging. The rom installed wasn't "complete", it looked like an interface for professionals to copy data from the old motherboard to the new... Maybe one of you knows what I'm talking about.
I flashed twrp and booted in recovery mode. Then I tried to wipe data but got errors (for instance "cache partition not found" or "hidden partition not found" or something like this. I'm sorry I didn't copy the error message :/
I tried to reboot anyway but I'm now unable to boot on the rom nor on recovery mode. I have a message : "POWER RESET or UNKNOWN UPLOAD MODE" and "ATconsole=ram loglevel=4 sec_debug. Level=1 cluster_power=1 androidboot. debug_level=0x494d sec_"
Only download mode is working.
So I'm trying to install the stock rom, downloaded from sammobile. On linux via Heimdall I got this error when flashing system.img and hidden.img :
Code:
Uploading SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
On windows via Odin, I cannot flash the tar.md5 file either, it fails.
Someone could help ?
Or at least explain why I got these errors in twrp?
Thank you very much !!!!!!

Update :
I found a way to boot in recovery mode (twrp 3.3.1-klimtwifi) : unplug the battery, replug it and home + vol up + power.
So here is the error when I try to wipe data : "Failed to mound '/hidden' (Invalid argument)"
I installed the old motherboard and I'm doing a full backup on my sd card on TWRP, including EFS partition.
On the new motherboard I can't restore the backup because in twrp > restore > sd card : "No partitions selected to restore".
So here's where I am now :
I can boot into twrp but have an error message when trying to wipe data.
I have a full backup of the old motherboard with lineageos installed and working but i'm not able to restore it
Any help appreciated

And also, when I try to sideload the lineageos zip file I get this :
Code:
Starting ADB sideload feature ...
Installing zip file '/sideload/package.zip'
Target: samsung/klimtwifixx/klimtwifi:6.0.1/MMB29K/T700XXU1CRF1:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc.0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7

Ok, I fixed the restore issue by moving the backup files to : sd_external/twrp/BACKUP/[myserialnumber]
So now I can restore all partition except System, System Image and Hidden.
Error : extractTarFork() process ended with ERROR: 255
I still can't sideload the custom rom. But the error message "Failed to mound '/hidden' (Invalid argument)" disapeared

I fixed/unbricked the tablet by using SamFirm to download a 3 files stock firmware.
I installed it with Odin and it worked like a charm.
Then I could install a custom rom