Hi, last night I was trying to turn my phone on and it got as far as the white "HTC" screen then cut out and kept restarting and getting that far again and restarting in a loop.
I've tried the generic solutions I've seen on various forums - wiping the cache partition and doing a factory reset, but no success.
official software, locked, s-on
recovery mode says:
handle_cota_install: install cwpkg to /cache/ cota/cwpkg.zip
handle_cota_install: install cwprop to /cache /cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
write host_mode error
handle_cota_install: can't mount /sdcard
Anyone have any ideas for what I can do next?
You'll either need to send your device to HTC or to buy a new phone. It's the dead nand issue that you're facing (c.f. the FAQ of the ReadMe thread.)
Sent from my HTC One M9 using XDA Labs
Hi all,
Noob here, having traversed the immense help for the past two day and trying everything i can find here and on other forums, I'm still stuck on bootloader/recovery/download mode.
When trying to reboot the phone, it sticks pn the HTC screen.
ive tried using ADB to sideload Roms/RUU but it looks like my OS has been completely wiped.
Any help would be Greatly appreciated!!!
errors:
E: missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bf_no
handle_cota_install: install cwplg to /cota/cwpkg.zip
handle_cota_install: install cwprop to /cota/cw.prop
E:fail to open file: /sys/devices/platform/android_usb/host mode
write host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can'y mount /sdcard, 5 times
E;find no match PARTITION: for package path /sdcard/ptt.zip
E:unknown volume for path []
E:Can't mount
E:Failed to open last_install: No such file or directory
After trying to apply from SD CARD:
Finding update package...
Opening Update Package...
E:failed to map drive
File on sd card: 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.40.401.8_Radio_01.02_U11440261_60.03.50505G_F_release_435816_signed
changed to 0PJAIMG.zip then transfered to SD card.
Are you sure that the RUU matches your current firmware? If not, get the correct RUU. If yes, does the MD5 checksum match the desired value? If not, re-download the file until the values match. If they do you're probably suffering from a dead nand. It's a hardware issue caused by the infamous heat of the SD810. All phones from all OEMs that use this processor are suffering from similar issues.
Hey guys,
im completly new to this flashing thing an i think i made a big mistake.
I tried to flash a new miui version (Global) via the already installed TWRP on my phone.
But that didnt quiet work, after the installation it just booted back in TWRP and i couldnt get the phone to do otherwise.
I googled a bit and found this tool called MIFlash (ver. 2017.4.25.0)
i also downloaded the fastbood rom from the Offical miui site and saved it on C: in a folder called rom
So i put the Phone into Fastboot and tried to flash it with MiFlash but in the end i got an error ( error:FAILED (remote: Check CRC failed))
And after that i couldnt even wipe the Data via TWRP i got an error there too
"Could not mount '/data' and unable to find crypto footer."
"Failed to mount '/data' (invalid argument)"
"Unable to recreate /data/media folder"
"Unable to mount /data/media/TWRP/.twrps"
"Unable to mount Storage"
PLS HELP!!!! :crying:
As explained in an other thread i got this issue :
with TWRP-offain and original one downloaded from TWRP website i received this error message after installation attempts of different custom ROMs
No OS installed
I wiped System and Data partition on each A and B slots and then tried to install on each slots some custom ROMs
At the end of each installations i received also this error message :
failed to mount "/System" (Permission denied)
How can i solve the issue ?
updater process ended with ERROR: 1
i have also tried to solve issue installing dm-verity disabler KO again
now when i try to install custom ROMs smartphone returns this error :
updater process ended with ERROR: 1
Error installing zip file "/external SD/name_custom_rom.zip
johnjohnmel said:
i have also tried to solve issue installing dm-verity disabler KO again
now when i try to install custom ROMs smartphone returns this error :
updater process ended with ERROR: 1
Error installing zip file "/external SD/name_custom_rom.zip
Click to expand...
Click to collapse
You need to use this twrp. Then it will work. About twrp errors: just ignore...
I've already used also that TWRP version
twrp-installer-daisy-3.3.0-0-offain.zip
KO
Voodoojonny said:
You need to use this twrp. Then it will work. About twrp errors: just ignore...
Click to expand...
Click to collapse
I started and completed successfully installation of TWRP and custom ROM in a slot, but when i try to change slot i received this error message "Failed to mount /system (permission denied)"
In TWRP > advanced i'm not enable to mount /system partition
How can i solve ?
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?
Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.
SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.
For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…