So i updated to CM9 and all was quite ok... But the video was not working, so i decided to downgrade to cm7 again.
so i did. After first start i had to realize cm7 was quite crashy suddenly.
So i went back to cwm and wiped system, data and cache.
And now i suddenly cannot install any CM zip files. tried both cm9 and cm7. flashed the included boot.imgs and booted up into cwm.
When trying to install the CM zip file, it just gives me some getpro messages (mk16i, mk16a and iyokan) and then Status error 7: Error in update.zip.
I tried several CM versions and redownloaded them multple times.
Anything i can try?
Related
Hi.
Yesterday night I was trying out a couple of different ICS roms. I tried one, and I was not happy with it, so I tried another one. When I was flashing the other one(JJ's Hybrid rom), the installation just froze and the progress bar didn't move, I waited half an hour, and decided to take off the battery.
I downloaded the rom again, because I thought it was a corrupt download. Well, it wasn't, once again the installation froze. I then downloaded another ICS rom( I guess KA13), and now it didn't freeze during the installation, but instead gave me error;
E: Can't open /sdcard/update.zip
(Bad)
I tried different kernels with different recovery images, but wasn't able to install anything.... Except CM9 Nightly. I don't know why it was possible, but I flashed FXP's CM9 kernel, and my phone is working(I just needed an alarm clock and something to play at school ).
But still, I can't install any roms. Any suggestion what could I do? Format SD?
CM9 is a good rom, but that doesn't mean I don't wanna try other roms!
Thanks in adv.
Hi,
I've had a similar problem. Try to flash a full official rom: http://forum.xda-developers.com/showthread.php?t=1330314
Maybe it helps?
Didn't work. Thanks anyway.
Try charging your phone to 100%
Sent from my LT18i using Tapatalk 2
Placed an item in the original topic already, decided to make a seperate one for more attention:
I'm running FXP151 on my Xperia S, with a NovaKernel flashed on top of it. Now I want to update FXP to 201, but the last times I tried flashing a newer version straight on top of the current setup, it will always halt with an error. Which in turn makes the phone unusable until I flash the original boot.img, wipe all data and restore a backup.
What should I do in order to update FXP properly? I've got the feeling that the NovaKernel shouldn't be there when I do, but I'll leave it to the experts.
Thanks in advance!
----
What I do to prevent this from happening again, is flash the FreeXperia Recovery by Bin4ry via fastboot before I update. That recovery seems to work out of the box. After doing the update, I flash Nova back and it boots without issues.
rc_enzo said:
Placed an item in the original topic already, decided to make a seperate one for more attention:
I'm running FXP151 on my Xperia S, with a NovaKernel flashed on top of it. Now I want to update FXP to 201, but the last times I tried flashing a newer version straight on top of the current setup, it will always halt with an error. Which in turn makes the phone unusable until I flash the original boot.img, wipe all data and restore a backup.
What should I do in order to update FXP properly? I've got the feeling that the NovaKernel shouldn't be there when I do, but I'll leave it to the experts.
Thanks in advance!
Click to expand...
Click to collapse
I don't know about any one else but I always had problems flashing zips from nova kernel so just extract fxp kernel from the Rom and install with fxp kernel, then just flash the Rom with out any wipes
Sent from my LT26i using xda premium
Try flashing the update, boot it, wait a bit, then reboot and install the kernel. Wipe dalvik.
Sent from my LT26i using Tapatalk
Tried flashing 202 over 201 today. Immediately got a "some symlinks failed"-notice and was forced to do a restore onceagain. Without any changed kernels. Gives me an 'error while formatting cache' when restoring, seen that before. It is starting to get on my nerves.
I'm keeping up Titanium backups from now on...
Update: did a dalvik wipe, fixed permissions, tried rebooting and erasing cache multiple times (to no avail), but it managed to boot to the launcher somehow. Can't see why, because the cache is crappy.
Hey all, I've tried searching but haven't had any luck. I believe I have a somewhat unique issue.
Back in June 2012 I originally tried flashing FXP CM10 but kept getting a boot loop. Since then I put on JJ's Hybrid rom and MIUI until I decided to try FXP again. (147 or something) It worked fine and I used it for quite a while until I just recently updated to FXP 203 without issue.
I got a new Nexus 4 and decided to do a complete wipe on my Arc so that I could give it away. I wiped cache, data and (stupidly) SD card.
After the wipe it froze on "Android is upgrading" and a battery pull made no difference.
After that, I decided to re flash the kernel and ROM, but made no difference. I flashed MIUI (a version I knew that worked) and the phone worked fine, but then I tried with FXP205 and right back to boot looping. (even tried downloading the rom to my work computer)
Most recently I left the phone to boot loop for a while and it actually managed to startup, and I could use it for a few seconds before it froze and restarted again.
Does anyone have any suggestions on what to try? I feel like I've tried everything, and it's strange that FXP worked totally fine for 6+ months and now this issue. I don't have any nandroids unfortunately since I wiped my SD card (like I said, stupid)
Youre flashing the following kernel by fxp inside the zip?
Remember to remove the boot.img from zip before installing.
Are you factory resetting, system format and dalvik wipe with cwm before installing zip?
Hey, thanks for the reply. I followed your instructions exactly, but I'm having the same problem. Any other ideas?
Flash a stock ftf as advised on the hundreds of other "bootloop" threads. CWM shouldn't even come into it.
XperienceD said:
Flash a stock ftf as advised on the hundreds of other "bootloop" threads. CWM shouldn't even come into it.
Click to expand...
Click to collapse
Tried that, no luck. Thanks for the suggestion though.
I had SGH T999, rooted android with CM10.0. under settings->about phone->cyanogenmod updates I found CM-10.1.0-RC2. I tapped on it and applied the update. After doing that following problems started to occur.
1. none of the Gapp could work! I opened Titanium Backup, it threw an error that phone need to be rooted again and SU need to be reinstalled.
2. I used odin to root the phone again. I installed gapps-jb-20130301-signed.zip. while doing that it threw an error that it is unable to mount /sdcard. To my surprise there were only 3 folders. under the folder "/0" ... i found all my content and the gapps zip file under this folder!
3. installation was successful. but after rebooting, a lot of apps started not working. YouTube, gmail, keep failed to start!
4. I thought it is a problem with the RC hence I downloaded the cm 10.0 stable version and tried to install that using rom manager (for some reason, rom manager had vanished! I had to reinstall it). Rom manager rebooted the device to install 10.0 but then again the error appeared "unable to mount /sdcard" a counter appeared from 20 till 0. it failed. I tried to browse to the zip file under /0. i could locate it but it also didnt work.
Now I am stuck with cm 10.1 rc2. gmail, youtube, keep aren't working. Some other apps also are reporting failure.
How do i fix it or how do i roll back?
You shouldn't have updated your phone in the settings. You should have downloaded gapps for cm 10.1 + rc2 in the cyanogenmod link then flash it (first rc2 rom then gapps) with the 3 wipes.
Dyn4m1c said:
You shouldn't have updated your phone in the settings. You should have downloaded gapps for cm 10.1 + rc2 in the cyanogenmod link then flash it (first rc2 rom then gapps) with the 3 wipes.
Click to expand...
Click to collapse
how do I fix it now?
rohit.bhosale said:
how do I fix it now?
Click to expand...
Click to collapse
Have a look here "http://forum.xda-developers.com/showthread.php?t=2172271" flash that rom as they explain it
Drop to recovery.
Wipe cache.
Wipe Dalvik.
Flash the latest CM nightly (http://get.cm/get/jenkins/27987/cm-10.1-20130514-NIGHTLY-d2tmo.zip)
Flash the latest gapps (http://goo.im/gapps/gapps-jb-20130301-signed.zip)
Fix permissions.
No more problems.
I have updated my rom to CM12 a while ago and after that my recovery (TWRP) stopped working. Yesterday, I finaly decided to fix it, so I flashed CWM (it worked!) and I tried to update my rom to the latest CM 12 nightly build. When it booted into the OS, I get a bunch of error for Text-to-speed, Google play service, UI System, etc. I tried to wipe, reflash, reinstall gapps... same thing. Then, I tried to only install the os : Wipe, install the rom, boot still get the errors.
Anyone, has any idea on how to fix this?
I have a SGH-M919 (Samsung galaxy S4 - T-Mobile), I downloaded the JFLTETMO version of CM12.
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
PanchoPlanet said:
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
Click to expand...
Click to collapse
Thanks for the reply, I downloaded a Stable build of CM11 and flashed it, but my phone kept rebooting in Recovery. I noticed that the sdcard/ folder is empty like if nothing was installed in the phone. I decided to flash TWRP. And when i flash the rom I get an error:
"E: Unable to open zip file."
"Error flashing /sdcard/rom3.zip"
Edit : Forget about the error I think the file was corrupted during transfer. Still getting the boot into recovery thing.
Try removing your SDCARD from the phone.
Turn phone off, remove SD card and start over. This may allow you to flash without errors.
Afterwards if successful tryout phone and then reinsert SD card.
Pp.