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
Related
Hi!
This is my first time posting, but I have been using MIUI for about 6 months now. Its phenomenal. I recently updated to MIUI 1.5.6 on My EVO 4G. Ever since I did it The battery drains extremely fast compared to the previous version of MIUI i was using which was 1.4.3, I think.
The camera is also not working, it just goes to a black screen and then force closes.
I tries to change the kernel to Tiamat 4.0.1 and 4.0.2 but it fails each time I try to do it. I have tried other kernels including 2.6.35.8-bcblend-CFS-sim_io-classRCU, which may not be for gingerbread. Nothing works. I currently have 2.6.37.6-cyanogenmod-01493-g70877de Kernel installed and I need help getting a new one on here.
The phone burns through so much power now its insane. I used to get at least 14 hours out of it. Now, I had it fully charged about 20 minutes ago and its already down to 88%. Can anyone help?
Sorry if this is the wrong format or whatever:
Specs:
EVO 4G
Model: PC36100
Android Version: 2.3.4
Baseband Version: 2.15.00.11.19
Build: MIUI 1.5.6
I am almost a complete novice when it comes to this, so any help would be appreciated but if you could give explicit instructions on how to do everything that would be amazing.
Thanks!
Are you wiping cache and dalvik before flashing the new kernal?
Yeah, I reloaded MIUI after doing a format all and nothing changed. It still wouldn't let me flash the new kernel.
Use juicedefender beta for battery, use the camera fix from the miui.us forums (camera is a known issue, I had it at first, applied fix and all was fine) and flash a tiamat kernel manually through recovery, not kernel manager as for some reason kernel manager seems to screw up for me when flashing tiamat kernels.
edit: heres a link to the fix.
http://forums.miui.us/showthread.php?236-If-you-re-having-issues-with-your-camera-on-1.5.6
Also, I could be wrong but I believe some of the recent updates came stock with cm kernel, so flashing tiamat could also greatly help with battery. Try Tiamat 3.3.7 if youre having problems with newer releases as 3.3.7 seems to be the most stable.
I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!
Jasonectomy said:
I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!
Click to expand...
Click to collapse
Posted the link for the camera fix! and what do you mean your having a problem flashing kernels? Your still s-off correct? And make sure when you are transferring kernels to sdcard you unmount sdcard when done, some of the newer kernels have problems with transfering data to sdcard quickly, and when you unmount or eject your card it insures the transfer is successful instead off cutting it off half way through.
I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.
Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App
Jasonectomy said:
I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.
Click to expand...
Click to collapse
Usually mismatched libs mean youre using the wrong kernel. Cayniarb puts out multiple versions of tiamat for multiple devices. Make sure you downloaded the one for the evo (should say evo in file name) and not the one for the incredible, xoom, etc.
njonas01 said:
Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Like I said, I recommend not using kernel manager lite for flashing Tiamat as I've had some problems flashing tiamat through kernel manager, most other kernels seem to be fine for me? Odd but it is the case. Although kernel manager would be good for downloading the kernels since it automatically picks out your device and you can be sure you download the correct kernel.
Thank you! Kernel Manager Lite seems to have worked! I'll see how the battery problems go after this flash.
The camera is the only problem left, and I can't apply the fix, I can't seem to find the /system folder...
You need to use root explorer as astro file manager and other basic file managers dont have the elevated privileges to view /system. The app is a couple of dollars but I HIGHLY recommend it to any and every rooted phone user.
MIUI 1.5.6
I downloaded and redownloaded the rom twice and flashed it twice, did the wipe/factory data reset and calkulin wipe and both times it would install different things for the rom, like the first time it didn't install Gmail or market den the next time it only installed market and settings and 3 or 4 other apps and thats it, and when i try sending a text, i choose a person and type the message, when i hit send it says, no valid user, message can't be sent, will someone please respond and let me know whats wrong? I would really appreciate it, my brain is going in all different directions, i hope you can understand what im typing because im very confused right now
Thanks,
Tj
i'm trying install cm9 or miui 4 or aokp but am running into a problem where i can't flash anything from cwm bundled with cm7. i'm doing these exact steps as stated here in Part 1:
with calk's el29 installed (with Rogue 1.1.2 based off cwm 5.0.2.7), i booted into recovery and wiped data except for battery stats. i flashed cm7 from here. i immediately booted into cm7, then immediately rebooted back into cwm recovery. from here, i tried flashing cm9, miui 4, aokp alpha 1, and aokp alpha 2. they all fail saying "E: can't open /sdcard/romname.zip (bad) Installation aborted."
what am i doing wrong?
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
paranoid android85 said:
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i've tried aokp and miui4. no bueno. in fact, it wont flash anything i have, including calk's wipe all script.
Bear gri11z said:
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
Click to expand...
Click to collapse
tried that like 4 times lol. i'm actually gonna try copying all the ics roms onto my sdcard again, this time from within android itself. all the roms had been transferred over while usb was mounted in cwm and i noticed the transfers would pause at times or not complete at all, forcing me to start them over. perhaps that's the problem.
Hi. I tried installing the latest CM9 nightly and when my phone rebooted it was stuck at the FreeXperia logo. I rebooted the phone and tried to get into CWM recovery but couldn't. So I booted into fastboot and installed the boot image from this (I can't like to the rom but it is called cm-9.1.0-zeus.zip) rom. Now I can get into CWM recovery. When ever I try to install the rom I get an error message Status 7. This happens after it says "assert failed: getprop("ro.product.device") == "R800i" etc.
It looks like either my device name on my phone is wrong or the device name for the rom is wrong. I'm pretty sure the rom I downloaded is the right one though. I've installed roms before but never ran into an issue like this so I'm lost. Seeing as I can get in to CWM recovery I reckon I should be able to get it back working again. Would really appreciate some help here.
Cheers.
re flash stock
CyberScopes said:
re flash stock
Click to expand...
Click to collapse
Downloading flashtool now. Will report back if it works or not. Hopefully it does.
I'm back on stock SE 2.3.3 rom now. Thanks a million, CyberScopes.
I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*
AlmightyCushion said:
I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*
Click to expand...
Click to collapse
Make sure you now have a compatible kernel and ROM.
Also make sure you have the recommended basebrand. I use .64
Sent from my Xperia Play using xda app-developers app
OK, I'm back on stock and the baseband is recognised. The guide I have been using for installing CM9 is this one (http://forum.xda-developers.com/showthread.php?t=1600833&highlight=cm9+guide). Is there something missing from that guide. I've never had to check if the kernel and rom were compatible. When using fastboot, I use the boot.img from the rom I download.
Flash kernel using flashtool.
Remember to do complete internal wipe and cache wipe.
I figured out why baseband wasn't working on CM the first time. It turns out that the stock rom I was using was an old one and the baseband for that wasn't working on CyanogenMod. I downloaded a newer one, installed that and then stuck CM9 on it and everything is working fine. Phew. Thanks again for the help. Really appreciate it.
Ure welcome. Im glad i helped u.
Sent from my R800i using xda app-developers app
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
-Hello, I'm new here. This is my first topic so if i did open this at wrong place, forgive me.-
I do flash roms through CWM a lot and i do keep the roms I downloaded as backups in case something happens. Recently I installed Sir Arco's CM12 (5.0.5) rom and I used it for a week. Then when I tried to change my rom to another one, I got stuck at recovery, after wiping cache/data/dalvik cache, saying "installing update..." but not doing anything for nearly 2 hours. FYI, the roms that I'm trying to install are all working (I used them before and they are the same files that I used to install), I even tried the stock rom but that didn't work either. Please help me ;-;
Note: I forgot the most important part! The phone can boot into recovery but there is no firmware installed in it right now since I couldn't install it. You can say it's pretty empty ;-;
If there's some missing info at this post, please ask it, I'm willing give any support I can.
What version did you tried to install? Only the last version of cm11 and cm12 are compatible with the recovery you used to flash cm12. If you want a older version of cm11 or cm10 and so on you need an older recovery. Probably that's your problem
First, I'm sorry for this slow response! Downloading CM11, finding a SD Adapter and etc. took a little bit long. But yeah, it's just as you said. I was trying to flash a 4.0.4 ICS. Flashing CM11 solved all my problems! Thank you so much! :good:
Erinn said:
First, I'm sorry for this slow response! Downloading CM11, finding a SD Adapter and etc. took a little bit long. But yeah, it's just as you said. I was trying to flash a 4.0.4 ICS. Flashing CM11 solved all my problems! Thank you so much! :good:
Click to expand...
Click to collapse
I'm glad I could help . Either way you can flash ICS if you want. You just have to install a older recovery to do it. And also make sure you have the right one
Alright will do! Thanks