Any help would be greatly appreciated I have a boost htc evo design 4g firmware 1.11.653.0 710RD its unlocked s-on, it is stuck on the htc screen and can only boot to the hboot, and cwm recovery screen. Prior to it I was just reading on my phone, wasn't doing anything special and then it restarted and got stuck on htc screeen.
I tried to use restore a backup I had in cwm but it gives me these errors and it fails to go thru:
E: Can't mount/ cache/ recovery/command
E: Can't mount/ cache/ recovery/Log
E:/ Can't Open/ cache/recovery/ log
E:/ can't mount/ cache/recovery/last_log
E:/ can't open/cache/ recovery/last_log
I was advised to download the latest stock ruu which I only could find: RUU_Kingdom_ICS_35_S_Sprint_WWE_Boost_1.10.653.2_Radio_1.11.00.0418_2_NV_Boost_3.42_0418_PRL61007_release_262178_signed.exe
I made it as a zip and updated the mainver: 1.11.653.0 so that it can go through hboot. All it does is act like it will parse then stop.
When I use fastboot to load the zip file and I get this:
C:\Android SDK\platform-tools>fastboot flash ph44img ph44img.zip
sending 'ph44img' (400670 KB)...
OKAY [ 61.336s]
writing 'ph44img'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 130.663s
I have no idea what this means and why it isn't working. Does anyone have any clues to how to fix this, if there is even a way too? Any help would be great.
update
exchanged phone new phone.
Hi, my phone model is Moto G (XT1032), after some mistakes I stuck in this situation. I can only boot to TWRP. I can boot, but I cannot flash it.
If I try to flash TWRP I get this error message:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9488 KB)...
OKAY [ 5.339s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.406s
Click to expand...
Click to collapse
If I try to erase recovery partition I get this message:
fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.038s
Click to expand...
Click to collapse
When I boot in TWRP I cannot push ROM file to phone via adb.
When I try to boot CWM I get this error:
fastboot boot cmd.img
downloading 'boot.img'...
OKAY [ 5.321s]
booting...
FAILED (remote failure)
finished. total time: 15.389s
Click to expand...
Click to collapse
Any advice? Pls...
Looks like a MMC hardware fault. Boot TWRP and run "adb shell dmesg > dmesg.txt", search for mmc error messages or post the file to verify.
_that said:
Looks like a MMC hardware fault. Boot TWRP and run "adb shell dmesg > dmesg.txt", search for mmc error messages or post the file to verify.
Click to expand...
Click to collapse
Thank you for the reply. Here is the file.
Some update. I can push .img file to /sdcard/. But when I try to install via TWRP I get this messages:
Update process ended with signal: 9
Error installing zip file '/sdcard/name_of_the_file'
Updating partition details...
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/fsg' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/persist' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/pds' (Invalid argument)
...done
Unable to mount storage
Click to expand...
Click to collapse
""//
C:\Users\ASUS\Desktop\platform-tools>fastboot boot C:\Users\ASUS\Desktop\MiUi-Wolf-DC.img
Sending 'boot.img' (43024 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
//""
and
//
C:\Users\ASUS\Desktop\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (38924 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
//
this error occurs when ever I want to boot trrough twrp or any custom recovery
Hello there,
I just got a Nokia 6.2 to use for my app reverse-engineering/development needs, but I would need to root it.
Recovery is just saying "no command" and fastboot does not want to flash recovery.
Code:
C:\Users\<user>\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot flash recovery twrp-3.3.1-PL2.img
Sending 'recovery' (38736 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Apperently the device's flashing functionality appears to be encrypted.
per the how-to at https://www.androidweblog.com/nokia-6-2-ta-1198-root-install-twrp-recovery/:
Code:
C:\Users\<username>\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot oem unlock-go
FAILED (remote: 'Failed to unlock, decrypt failed!')
fastboot: error: Command failed
Device state is listed as unlocked.
Try
HTML:
fastboot flashing unlock
I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.
paulLi_01 said:
I just realized that I probably bricked my phone while trying to install a ROM.
After failing to install the custom ROM, my phone displayed that it is unable to mount:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I have tried to use TWRP to:
Change file system for all of these partitions by switching to EXT2 back to EXT4 but resulted in error messages like this:
Unable to wipe Vendor
Error changing file system
Next I tried to repair these partitions but only resulted in this error message:
Repairing Vendor using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Vendor
I concluded that perhaps the cust, vendor, and product partitions don't exist.
I then tried to use bootloader to erase the existing partitions of cust, vendor, and product and since my device originally doesn't have a vendor, I decided to just delete and reinstall it (except for cust & product):
platform-tools> .\fastboot.exe erase vendor
Erasing 'vendor' FAILED (remote: 'Command not allowed')Erasing 'vendor'
fastboot: error: Command failed
platform-tools> .\fastboot.exe erase cust
Erasing 'cust' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
platform-tools> .\fastboot.exe flash cust .\System\CUST.img
Sending 'cust' (258509 KB) OKAY [ 6.442s]
Writing 'cust' FAILED (remote: 'partition error')
fastboot: error: Command failed
After these error messages, I tried installing another custom OS that worked previously but it seems like the phone is stuck in the "your device is currently booting" screen although the initial installation of the OS was successful in TWRP besides the error messages of:
Failed to mount '/cust' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument)
I searched online and found that I could use the dload method by having an UPDATE.APP inside a folder called dload on a SD Card which should allow your huawei phone to boot into the stock image. Unfortunately, that did absolutely nothing.
I have then tried to flash the stock BOOT.img from the UPDATE.APP through fastboot:
platform-tools> .\fastboot.exe boot .\System\BOOT.img
creating boot image...
creating boot image - 15863808 bytes
Sending 'boot.img' (15492 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
but unfortunately with no success...
I have tried connecting HiSuite with the phone in bootloader but HiSuite returned a message saying that this device isn't supported.
I have lastly tried to relock the bootloader which did nothing with the factory reset failing at ~15%.
Erecovery mode doesn't work for this phone due to a failure to get the packets as well...
Now I am just left with a phone with no OS with TWRP installed...
Are there any solutions to installing an OS on this phone to get this phone running? Thanks in advance!
Some additional information:
My phone displayed that its a FRD-L14C567 before installing a custom OS
After installing the custom OS, it displayed that my phone is a FRD-L04
Since I cannot find any free ROM for FRD-L14, I decided to use the ROM for FRD-L04C567 which are the .img files I flashed to the phone.
Click to expand...
Click to collapse
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.
sircamot said:
Unlock bootloader with PotatoNV or DC Unlocker or DC Phoenix
then u will allowed commands.
Click to expand...
Click to collapse
Yes, I have already done that! Unfortunately, I believe that these commands requires root access which I have tried installing super SU with which did not help with my problem...
I have already bought a new phone since there are no official huawei repair centers in the US with the Canada one not supporting repairs on this huawei honor 8 international model. However, fixing it would be nice though...
In addition, I have tried installing Havoc OS for hopes to have the partitions rewritten for android 9 but it didn't help at all
Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again
sircamot said:
Really used DC Phoenix? this tool will rewrite all phone firm to DC Original firmware like OFW
after all, unlock bootloader in phone's setting, now again DC Phoenix, choose Update by TP,
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
(Maybe Kirin650 will success after all)
now, u can use PotatoNV and make ur bootloader unlock num
then open windows powershell, enter like this
fastboot oem unlock numbers (PotatoNV generated)
u know? u already can use fastboot command at this time but wait patiently
next, push vol+ buttom to toggle bootloader unclock and push power to comfirm.
ur phone will reboot and initialize user data
again enter bootloader mode and open DC Phoenix
check Load and temporally unclock boot loader, select ur cpu at bootloader files, and press Do job
now u can use fastboot commands
Note: this method means reflesh ur phone at all so of course ur root should lost
u need to flash TWRP and super su after all again
Click to expand...
Click to collapse
I haven't used DC Pheonix. I can try it right now! Thanks!
paulLi_01 said:
I haven't used DC Pheonix. I can try it right now! Thanks!
Click to expand...
Click to collapse
Welcome, cheers!