I am flashing OmniROM-4.4.2 for my Huawei Ascend P1 using Philz Touch Recovery based on cwm 6.0.3.7.. I did it successfully once, created a backup and got back to my old liquidsmooth rom by Spanorg so that I could do a proper backup of my files to transfer it to the new rom. However, upon wiping everything, now everytime I try to flash the OmniROM-4.4.2, it says 'set_perm some changes failed status 7 installation aborted'.. I have the backups, but it says they have md5 checksum mismatched.. and when i try to go into my old rom, it gets stuck in the boot loop..
I have tried clean installing a couple of times, but nothing seems to work..
Any fixes, guys?
Related
ok so the tf wont boot anymore it will get past the encryption process then just continue to go into boot loop until it eventually freezes up.
i have tried to reflash the rom and still the same. i have factory wiped and reset it also and flashed two different roms but nothing is working. also tried to do the restore option but it just gives me a md5 mismatch on all 3 of my restores so im pretty stuck as to what to do next.
also ive updated to the latest cwm so maybe this is the md5 mismatch in the restores ?
was trying out the revolution hd rom from the revolver rom all was working until i tried to go back to revolver rom so now im stuck with nothing lol
any help is appreciated
should have stuck to the old saying
dont fix it if it isnt broke!
had to resort to using the nvflash in dev section but still lost all my back up data
md5 mismatch everytime i try and restore it
Hello everyone
i am new to xda and Android
i have a htc evo 3d smartphone, i unlocked the bootloader via htc dev method and rooted phone by binary4 script. next i installed rom manager and clock work mod recovery. i downloaded the wild-for-night 8th feb 2013 android 4.2.2 zip file and gapps. i installed these two zip however my phone is always stuck in boot logo of cm screen. i tried installed 3 other roms but the same problems happen. no matter how many times i try to wide data/factory reset,cache, delvic and system is still is stuck. i have also tried flashing the boot file in the zip but that makes it even worse it boot halfway then keeps rebooting forever, i fixed that but restoring the boot from a nandroid backup i made from the official rom. after 5 weeks of searching i still couldn't find any solution.:crying:
any help will be appreciated thanks
i am s-on hboot 1.53.0007 and my evo is gsm
sorry guys i forgot to mention that i have tried various other recover including 4ext. in 4ext after installing custom rom phone goes to the custom rom logo and then keeps rebooting i have to flash the ruu backups boot.img file in order to install the original backup back on
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
My Pico is stuck at the HTC logo at startup. I was using CM11 RC2 with mounts2sd, then it rebooted suddenly and struck at the logo. I tried to reinstall the rom but it says the installation failed. I tried it many times with many roms (cm11 weekly, omni, carbon and even cm9)and it sometimes gets installed but struck at the HTC logo. Will there be any use if I tried to restore a backup? If so where can I find the backup coz I deleted my previous one and don't have one currently.
And...
When I tries to change the recovery to aw3sm3 or twrp or cwm it says 'malformed 1 byte' error. I tried to open the img file with rar but it gives an error. I tried downloading from the internet but all the recovery files were like that. I even tried on my friends laptop. What might be the reason?
expguy said:
My Pico is stuck at the HTC logo at startup. I was using CM11 RC2 with mounts2sd, then it rebooted suddenly and struck at the logo. I tried to reinstall the rom but it says the installation failed. I tried it many times with many roms (cm11 weekly, omni, carbon and even cm9)and it sometimes gets installed but struck at the HTC logo. Will there be any use if I tried to restore a backup? If so where can I find the backup coz I deleted my previous one and don't have one currently.
And...
When I tries to change the recovery to aw3sm3 or twrp or cwm it says 'malformed 1 byte' error. I tried to open the img file with rar but it gives an error. I tried downloading from the internet but all the recovery files were like that. I even tried on my friends laptop. What might be the reason?
Click to expand...
Click to collapse
For your first problem: Its may be because your nand is burnt.
Solution:
1. Download superwipe
2. Flash superwipe
3. Flash your desired Rom
For your 2nd problem: First try to flash the recovery in fastboot, if it doesn't work try this http://forum.xda-developers.com/showpost.php?p=54475962
Hit thanks if i helped
Hi everyone!
I figured, why not give MIUI a try. I downloaded the rom, made a full TWRP backup, then installed the ROM. It just froze after the MIUI logo appeared, so I decided to restore.
All the while, I noticed a new red Oneplus logo where the old one had been white. But even after restoring my backup, the startup logo was still red, and my previous rom was freezing during the boot animation. I tried again, no luck.
Then I thought, I'll just load my old rom (Vanir/Exodus) from the downloaded zip OVER my restored rom, maybe that will fix things. It won't let me do that, however, due to an error in TWRP which I've never gotten -- "Error executing updater binary in zip".
So I went to the bootloader to update TWRP, and noticed the whole bootloader looks different and is in Chinese. So it must've been part of the MIUI ROM.
What do I do now? I'd love to just fix the bootloader but not sure how. Maybe if I did that I could then restore my backup. As a precaution, I've ADB Pulled the backup folder just in case I have to start over, then I can copy the backup folder back in and try to restore it........
Thanks for the help!
Well, I figured it out on my own. I went to download the latest version of CM12 from here, and ADB Pushed it while in TWRP. I then installed it, and it didn't give me that assert error. I rebooted, but powered down while it was starting up, went back to TWRP, and restored my backup, no problemo. I wonder what happened.
It would be nice to understand what the issue was that prevented me from restoring it initially, and what I could have done manually to update the particular thing that I needed to update.
Pretty sure it was an the firmware ColorOS uses and is incompatible with the newest roms based on the CM firmware