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
Related
I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
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.
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?
I accidentally (don't ask) wiped my system while trying to install cyanogenmod. After doing that CM seemed to finally successfully install but it was stuck at a bootloop. I went back into recovery to restore my backup but it resulted in an error the first time. I tried it again and it said it was successful. I tried booting that up but the boot logo looked different than before and it wouldn't boot. It wasn't a bootloop but it was stuck on the boot logo. After trying a few more different things nothing worked and I decided to flash the stock firmware back. When I tried RSDlite failed the flashing process. Maybe I don't have the right firmware for my phone or something. I can't figure it out. I'd really appreciate anyone input on this. I need to get my phone up and going again as soon as possible. It's a Droid Maxx. It's not the Dev Edition but it does have an unlocked bootloader.
Thanks
EDIT:
I tried flashing that firmware again and for some reason it worked the second time. This thread can be deleted.
If you find it wont boot past the CM bootanimation, go back to recovery and Factory Reset - that normally will get it to complete the boot process. Make a backup first so you can easily restore back if you choose. Beats RSD back to stock and starting over...
I also run an unlocked Droid Maxx, non dev, currently on AICP ROM or CM, whatever flavor I feel like and who is updating their ROM the most often.