Database Users

Can not flash other ROMs?

Hello. My EVO is updated with all the new firmware and such as I just got it. I have my EVO rooted using the unrevoked method. The PC36IMG is the only thing I can flash to. When I remove the PC36IMG from my sd card and try to flash another ROM I get errors. When I put the PC36IMG back on the card it will find that image and load it and it goes back to sprint lovers. What do I have to do to flash another ROM?

It would help if you said what kind of errors you got.
Did you do a nandroid backup before you tried to flash? If you can't, you didn't root correctly or somehow broke your root.
The bootloader will always look for PC36IMG because it's the default recovery image name. Remove it and it will just tell you it's missing, at which point you flash a different ROM in the recovery menu (go to install zip from SD card).
Obviously you can flash to sprint lovers so I guess you got it rooted ok at some point.
Have you tried doing a full data/cache wipe before flashing to the new rom?

I cannot remember what errors I got at the time. I finally got my phone back to sprint lovers. Everytime I try to do a backup it will not do it, it will just reboot and loop on the white Sprint evo screen. I've tried to flash fresh and others and I get errors. I put the PC3IMG back on and it will find it, and load sprint lovers back on. I don't know what else to do at this point except just stay where I am at and hope nothing goes wrong.
Sent from my PC36100 using XDA App

Oh. I did do a android backup but when I tried to go to it, it says it does not match MS5 or something like that?
Sent from my PC36100 using XDA App

randyreed1971 said:
Oh. I did do a android backup but when I tried to go to it, it says it does not match MS5 or something like that?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
MD5 checksum is corrupt? File is maybe bad download. Re download it
Sent from my PC36100 using XDA App

Rom Manager ClockworkMod 2.5.1.4

Just got updated ClockworkMod 2.5.1.0 to 2.5.1.4
When I go to reboot in recovery my N1 is stuck on the nexus x
Sent from my HTC Desire using XDA App

There's been a problem with it recently, apparently that does just this. Check Koush on Twitter for actual info.

Thanks for your answer.
Because of that I can not switch roms. Does anyone know another way to switch roms
Sent from my HTC Desire using XDA App

Boot back into your phone and flash an older recovery. Just scroll in Clockwork Mod and choose amon RA or clockwork recovery 2.5.1.0.
Sent from my Nexus One using Tapatalk

Thanks
Sent from my HTC Desire using XDA App

Updated to 3.0.0.5. Looks purty.

I tried 3.0.0.5 and it still gets stuck on the nexus x. Had to go back to 2.5.1.1
Sent from my HTC Desire using XDA App

Just updated to 3.0.0.5 from Rom Manager. No issues here
Sent from my Nexus One using XDA App

Will try it again
Sent from my HTC Desire using XDA App

Just updated to 3.0.0.5 myself through Rom Manager (only thing I really use it for is flashing a new recovery, and knowing when they come out). Can't enter recovery, just bootloader, going to reflash it via fastboot (gotta grab it real quick).
Flashing 2.5.1.4 from RM works, but 3.0.0.5 did not. However, I was able to flash it via fastboot.

3.0.0.5 still does not work
Sent from my HTC Desire using XDA App

Had to flash Clockwork 3.0.0.5 two times from RM for it to work (got into bootloader the first time). Works like a charm now.

3.0.0.5 working fine so far...

Will give it one more try
Sent from my HTC Desire using XDA App

I think for the newer version you gotta give it some time cuz it's its first boot.
Sent from my Nexus One using XDA App

3.0.0.5 Does not allow you to flash. Have to use 2.5.1.1
Sent from my HTC Desire using XDA App

The bigger problem is 3.0.0.5 will let you flash a new ROM but you will be screwed if you have any apps to SD on EXT if you try and go back to a recovery! You will have to format your entire SD card, repartition and then restore a backup after panicking for a while! Ask me how I know...needless to say this longtime supporter of CW has jumper ship and is now using RA...

Galloway said:
The bigger problem is 3.0.0.5 will let you flash a new ROM but you will be screwed if you have any apps to SD on EXT if you try and go back to a recovery! You will have to format your entire SD card, repartition and then restore a backup after panicking for a while! Ask me how I know...needless to say this longtime supporter of CW has jumper ship and is now using RA...
Click to expand...
Click to collapse
Yup happened to me too.
It flash rom fine and even back up work fine. When I try to do nandroid restore it messed up my sd card EXT. long process to get everything working again.
Sent from my Nexus One using Tapatalk

baseballfanz said:
Yup happened to me too.
It flash rom fine and even back up work fine. When I try to do nandroid restore it messed up my sd card EXT. long process to get everything working again.
Click to expand...
Click to collapse
Did you change the name on your new restore point? This happened to me on an earlier cm recovery. RM automatically updated me to 3005 and now I'm having some reservations.

3.0.0.5 works fine for me for every rom

MD5 file error. give me some help?

ive been rooted for quite some time, and never have had trouble with pulling backups form clockwork recovery. last night i made a backup of my CM7.0.3 that i was using for a while to try out virtuous unity. today on my lunch break at work i attempted to load the backup and i was getting that error message.
i did a "superwipe for g2" right before i tried to recover.
then i attempted to recover my stock rom i have had for months an i got the same error message. any ideas? the only thing i could think of is a few days ago i cleared out a HUGE cache in my clockwork from my SD to clear up my card. could that be it? any help would be appreciated.

bump.
someone please give me some help! i would really appreciate it.
i attempted this
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
but go no response and still had a md5 mismatch.

Had that issue before... The back up process didn't go right unfortunately. I would recommend you to download another Rom and transfer it to your SD card.
Sent from my HTC Vision using XDA Premium App

what do you mean by that?

PatrickHuey said:
what do you mean by that?
Click to expand...
Click to collapse
Well it rarely happens. I remember when I got the same error and told somebody in XDA they told me that during the back up process clockwork didn't back it up correctly which leads you not being able to restore your back up. Had virtuous 2.2 back then, good thing was I had 2 back ups just in case so I was able to restore a later version of my back up.
Sent from my HTC Vision using XDA Premium App

Did you by any chance change the name of the folder of the backup? I once 'annotated' the default date-time format that Clockworkmod uses with something more meaningful to me, but found that it breaks the MD5 check.
I'm just asking on the off-chance because changing the folder name back to what it was when the backup was made will fix it, if that's the case.
Good luck.

Yeah I did, but I hadn't had any problems with renaming it with it before. I attempted to change it back to a default name and that didn't work. Is there anyway to try and recover my backup, or just my data?
Sent from my HTC Vision using XDA Premium App

I also had this problem before when switching between cyanogen and a Sense ROM. The way I fixed it was I downloaded, wiped and installed a fresh new cyanogen ROM. After it was installed I was able to restore my old backup from CWM.

ill have to give that a try. thankyou sir.

PLEASE HELP. Boot loops to recovery

I installed the HORSEMAGEDDON ROM and it worked - for the most part. But it kept giving me annoying errors about different apps that were attempting to update every time I turned it on. So I tried to restore my backup that I had made with CWM 6.0.2.8. However the backup apparently did not restore properly because it now boot loops back into CWM any time I try to start it. I get the errors:
E:Can't open cache/recovery/log
E:Can't open cache/recovery/log
E:Can't open cache/recovery/last_log
E:Can't open cache/recovery/last_log
So I tried to reflash HORSEMAGEDDON but it still loops back into the CWM recovery screen.
I have wiped everything according to the instructions on the HORSEMAGEDDON thread.
HELP!! This happened to me on another U8800-51 phone and I wound up hard bricking it trying to get back to stock.

Anybody???
Does anybody have any ideas on how I can fix this?

Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

iheartsamsung said:
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I did a wipe of data and factory reset as well.

What I would do is get an SD card with a custom rom on it and try installing it from recovery menu
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

iheartsamsung said:
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay. Here is what I did step by step:
1. I was on Stock 2.2.2 Froyo and flashed HORSEMAGEDDON successfully. But I had some errors related to updates since it was such an old ROM the updates were all for much newer versions of the apps tied to 4.x.x.
2. I attempted to restore my backup made with CWM 6 to return to the stock. It said it completed successfully but when I rebooted it just looped into the recovery screen with the error messages posted in my first post.
3. So I tried to reflash HORSEMAGEDDON and it said it completed successfully. But it still bootloops into recovery.
4. I can access most of the features of the recovery. I can access the pink screen and swap recovery versions. I can access my SD card from my PC when I mount it from recovery.
5. Yes, I did do full wipes with each attempt to reflash.
The ROM was not the problem. It worked and worked well other than update issues for apps. It was only after attempting to restore to stock I ran into issues.
The problem appears to be something was corrupted when I tried to restore my backup, even though it said it completed successfully.
So if I try to flash yet another custom ROM, even if I could find one I trust given all of the version issues etc., I don't think it would act any differently. But if somebody can recommend one I am all ears. Keep in mind I have a -51 phone so it will have to be for that or the PRO.
Given that, how can I get back to stock? Am I the only person who has ever had this problem? I don't believe that is the case, so somebody must know how to fix it or can point me to a procedure to repair the internal memory.
Help!!

I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Thanks but.....
iheartsamsung said:
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
None of the fixes on this link seem to apply to my situation.
When I said "bootloop" I may have misused the term. What happens is I power up, it goes to logo screen for about 10 seconds, shuts down and restarts to logo screen then goes into recovery after about 5 seconds. From other info that I have found it is due to a corrupt bootloader and I need to reflash the bootloader. Problem is, reflashing the bootloader i.e. CWM, does no good at all.
I am also hampered by lack of info specific to the -51 model. And I cannot find a copy of the stock ROM anywhere that is for the -51.
So essentially I am screwed. All of that said, I have found a new phone for $40.00 so all is not lost. It's a U8800 but not the -51 or PRO. I don't plan on customizing it, I'll just stick with stock. After trashing two phones even after following the advice to "BACKUP" I think enough is enough. Backing up did me no good whatsoever in both cases.
In my estimation, the culprit is CWM, or at least the versions I used.
If anybody has any advice I'm all ears.

Did I ruin my G2 (won't boot, can't reflash)

So today I tried to install Omnirom on my rooted G2. I did all of the usual steps (using CWM) and then rebooted. It got stuck in a boot loop, and I realized I forgot to factory wipe/cache wipe after installing the rom. I went back to recovery and tried to wipe, but it got stuck on Formatting cache. I then noticed that CWM had problems wiping, mounting and accessing /cache. I searched around but found nothing to help me.
I then tried to unroot and return to stock using LG FlashTools and the device's Download Mode but everytime I try to flash the kdz file it fails on 47% with some "Page Error" followed by garbled Unicode characters...
Is there anything I can do?

You are not dead but you have work to do. Go to this thread.
Forum.xda-developers.com/showthread.php?t=2582142
Good luck
Sent from my LG-LS980 using Tapatalk

cityneversleepz said:
You are not dead but you have work to do. Go to this thread.
Forum.xda-developers.com/showthread.php?t=2582142
Good luck
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply and the link! I, however, don't have access to ubuntu, is there anyways to do this on Windows? Also, I can go to both Recovery and Download modes, if that helps.

Wipe system then retry reflashing stock.
Sent from my LG-D802 using XDA Premium 4 mobile app

elitekill said:
Thanks for the reply and the link! I, however, don't have access to ubuntu, is there anyways to do this on Windows? Also, I can go to both Recovery and Download modes, if that helps.
Click to expand...
Click to collapse
If you still need a ubuntu, use a portable version of Ubuntu or run one from Virtua Machine. It's very difficult to boot one from your flash drive..