Hi,
I have stupidly renamed my official htc rom cwm backup.
And cant remember the original name!
cwm says that here is a md5 sum mismatch!
Has anyone got a backup they could zip up and upload?
If not how to get it back
Can i flash the .img files in fastboot?
RUU? Would that get me back too stock HTC 2.2.1?
Make sure that there are no spaces in the new renamed folder. Then it may clear the md5 checksum error.
And you can also flash the img files from fastboot.
Commands are
fastboot erase boot
fastboot flash boot boot.img
fastboot erase userdata
fastboot flash userdata data.img
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
Sent from my HTC Wildfire using XDA App
Thanks
when i add a name cm7's standard file manager ands spaces the .number(1,2,3 etc.)
edit:
figured it out!
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.
Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes
Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)
Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?
Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.
algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.
I have the same problem, someone could explain it to me step by step, please
ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]
A friend accidentally erased system partition. Phone enters TWRP and fastboot but I can't update with update.App so I'm looking for a dumped system.img (or a way to make a system.img from the unsparse files (unsparse joiner didn't work) to try to revive the phone.
Thank you
Hey, I need to flash a persist.img file, because my phon restarts every 2 Minutes and does not find any WiFi, but it gives me out the error: remote:Error : persist partition not allowed download. Is there a way to flash it without twrp, since when I try to flash a custom recovery, it says partition table not found. Is there a way to flash persist.img in Mi Flash Tool?
use the link given below
it will help you
https://forum.xda-developers.com/showpost.php?p=75782887&postcount=2
raaz1431994 said:
use the link given below
it will help you
https://forum.xda-developers.com/showpost.php?p=75782887&postcount=2
Click to expand...
Click to collapse
Don't have Twrp, can't flash custom recovery, it says partition table does not exist
boot to fastboot and
give the command
fastboot boot twrp.img
instead of fastboot flash recovery twrp.img
hell guys
First my phone is : Moto G5 Plus
Product/Variant : potter XT1685 32GB P3B
i made mistake guys and flash wrong gpt.bin and bootloader.img
after some research i find that the gpt.bin changed the size of all partitions i have
i flash TRWP and use this guide iwf1.com/how-to-re-partition-your-android-tablet-or-smartphone-all-options-included-change-size-fs-type-etc/2
i use adb and i can't delete userdatra and system partition to resize them
i can delete oem partition and recreate it and when i try to resize recovery partition it can't allow me
but i can delete and recreate it but phone going dead , then i use blankflash to back to life
and in singleimage.bin i try edit gpt.bin by the original gpt.bin and it is going will in flashing
but here is the problem when i back to TRWP to see the size of partition it back as same , i need 21MB in recovery but i find it all time 16MB :crying::crying::crying:
i have problem on my recovery partition
i can't flash the recovery.img of this Roms
POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
recovery.img required 20 MB :crying: and my recovery partition have 16 MB :crying:
i try Debloated ROM ... i know it works fine but i need this issue to fix
if someone know please help me :crying::crying:
i need to resize recovery partition
What error are you getting when trying to flash the Motorola stock recovery? Is your bootloader locked?
Which GPT/bootloader did you flash that caused this to happen?