Is anyone else having an issue flashing this update? When I go to flash it in the recovery, it tells me the file is bad I have checked it in bittorrent and the file says it's 100% fine.
i just installed it on my phone, no problems, i got my download direct from cyanogenmod.com
I had no issues when I tried installing it. Make sure you wipe data/cach/etc?
Related
Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?
I have been trying to get my S3 to take the update from LG8 to Ll3, and it fails no matter what I try. I am running totally stock LG8 that I rooted using the toolkit posted in the development section. I don't have any APKs that I altered, but every time I try to flash the update, I get a "status 7" error. I tried it on both internal and external SD using CWM recovery. I tried flashing stock recovery via Odin and then let the phone download it over the air and attempt to install itself, and I even tried running the update in TWRP. Every time I get the same status 7 error.
I am coming from HTC phones and have never had these kinds of issues, so I'm pulling out my hair. Can anyone offer any suggestions? I know it must be something stupid I'm overlooking, but I've searched everywhere and can't seem to find the answer.
Sounds like a bad DL. Just grab it from here. http://forum.xda-developers.com/showthread.php?t=1743923
Or here http://forum.xda-developers.com/showthread.php?t=1904099
Or odin flash LI3- http://forum.xda-developers.com/showthread.php?t=1919919
A lot less stressful
The procedure that myn posted over here is pretty staight forward and foolproof too.
Have you solved your issue yet?
I am getting the status 7 error as well even with Myn's procedure. Others are having the problem. Only thing I can think of is the current image file has changed enough to not allow the update to go through. However, I have not removed or modified any stock apks and backed my whole system up with TB right after rooting so no reason for mine to not work. Binary file should be good since it is working for other S3 users.
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
cfonte100 said:
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
Click to expand...
Click to collapse
I was able to get mine to work using Myn's method. Seems flashing newest CWM recovery did the trick. Was trying to flash via TWRP and didn't think it would matter but apparently it does. Just followed his post and all upgraded without issue.
Back to your issue.....what state is your phone at currently? What recovery is installed and what version are you running? Surely we can get this resolved for you.
what does the log say when it fails? I mean in addition to status 7. If you don't see anything go under advance>show log. it's probably a failure in the checks it does before the flash. Have u modified your build.prop? is your baseband and build both lg8? That log will tell you what's wrong.or as I mentioned above you could follow 1 of my links and avoid tha headache
I have a Yakju Maguro which is currently running JOP40D. I recently installed the ClockWorkMod v6.0.2.3 recovery, and rooted my phone. Now I received the notification for the 4.2.2 OTA update, but as expected CWM gives me an error when attempting to install it. It says "Install Untrusted Package?" and gives me Yes or No as options. Until now, I've always been weary to try the Yes option, so I've always gone for No, and the update obviously didn't install.
So my question is, will it actually work if I select Yes? And if it doesn't, in what condition will my phone be after it fails? Will it boot into the old OS, or will I have to manually re-flash a ROM?
I've tried googling the problem but no one seems to be facing the same exact condition as me. Eveyone reports that the installation simply fails with CWM, and I've never seen any mention of a Yes/No prompt. Also, I haven't found any thread that mentions in what condition the phone will be after the failure, so I'm trying to figure out what's going on.
In addition, I've manually downloaded the "07501b11ad3b.signed-yakju-JDQ39-from-JOP40D.07501b11" zip file from the Google website. Will I be able to flash that instead from CWM, make things simpler?
Thanks for any help.
I'm trying to instal Cyanomodgen, and have it working properly, thats my ultimate goal
I wiped my phone completely
I do CANNOT physically put my SD card to a computer atm, I'm trying to work around it
Odin does recognize my device, I can only install TWRP for some reason and not CWM with Odin ( program stops working with CWM and crashes ) I have tried different types of CWM, to no avail. I used to have it, then switched to TWRP for testing purposes
I would much rather use CWM, honestly. Any ideas why thats not working?
I am using ADB push filename.zip /sdcard/ for my cyanomodgen and when I go into my file manager I do not see my files anywhere at all, but when I go to wipe stuff, I can see there is 200mb in there( obviously its there but i cant see it )
There's a sideload.zip in there idk what that is
I've tried sideloading the cyanomodgen.zip and I get a radio error ( maybe its just the nightly file messed up, not sure )
I have tried installing CWM with heimdall, and I have to replace my phones drivers with theirs and it tells me it was successful but when I reboot I get stuck in firmware upgrade encountered an issue and the only way to fix that is to re-install the original drivers
I just tried heimdall again, failed, bout to reinstall TWRP and await further assistance.
Got CWM working, converted back to stock image and now I'm going to try this all over again, just keeping everyone updated
I fixed my phone completely, full updated and functioning properly except video not working on snapchat, other than that its perfect, i think the nightly build has something to do with my camera.
I'll leave this thread here in-case anyone has the same problem I can come back and help them.