Develop Bugs

[Q] Cyanogen 6.1.2 Theme Help

I will admit that I am a noob at this so... bear with the noobness
I have rooted my 3.30 EVO and have installed the Cyanogen 6.1.2 ROM. I backed up my nandroid and wiped using the partition option and the factory option as instructed in every tutorial. Cyanogen 6.1.2 works great in itself, the problem I'm running into is trying to install any CM themes...
I've tried installing the Project_BlissHD-v2.0_EVO_CM_6.1.2_signed theme .zip for CM 6.1.2 through the recovery (not even sure if this is the right way to do it), but every time I try, it tells me that the installation is aborted.
I wipe before each try and have even completely restored a backup and reinstalled with no success.
I have searched and searched for a thread that could help, as I didn't want to have to post a question if I could avoid it. So, how to I apply specific themes through CM? Here's what I've got:
ClockworkMod Recovery 3.0.0.2
Build 3.30.651
Used Unrevoked 3.3
And again, please forgive the noobness....

Clockwork 3.0.0.2 is only compatible with the new hboot. If you're on the old hboot, roll back to 2.5 and try it again.

I had the same problem .. I made a thread about it .. I'm about to try what BIG CHEEZE suggested

I use Amon_Ra ,myself. I would suggest using that one perhaps since it does a better job emptying the delvik cache.

Cheese, I'll try your suggestion about the rollback. I can just do that right in clockwork, correct? If that doesn't work, I'll try Jason's suggestion. Jason, which amon ra version?
And thanks to both of you!

Just use ROM Manager to roll back. You can flash Amon RA through ROM Manager as well.

You're welcome.
Use version 1.8 since I've been hearing some weird things about 1.9.

hummm
i get "An error occured while flashing your recovery" error when i tried to rollback to 2.5.1.4

I'm going to flash RA 1.8 right now.... let you know how she goes.

Ok, so here is how it went:
Flashed AmonRa 1.8 through Clockwork
Success
Booted into AmonRa recovery. Backed up a fresh nand, wiped DATA, CACHE and Delvik. Installed Cyanogen 6.1.2
Success
Cyanogen boots.
Success
Boot back into AmonRa. Repeat all the wipes. Proceed to install BlissHD pack for CM. Installs succesfully.
CM attempts to boot again, but just gets hung up on the splash screen, repeating a new splash every 3 seconds or so. Rebooted several times to see if that would help. No dice. Restored back up nand and am back to square one.
Suggestions?

It sounds like the theme you want is not gonna work with the stock cm6.1.2 kernel...my suggestion would be to try a different theme
I recommend barnacles10 ginger bread theme.
Sent from my PC36100 using XDA App

Also when you flash a theme...be patient on its first boot. Restarting during a boot that is loading files for your droid has had horrible results with my experience.
I was flashing a radio update and thought that boot loop was frozen..so I pulled the battery..restarted..and was stuck on the boot screen..then my battery dies while in the process of using hboot...and my usb cord wouldn't charge the battery..so I had to wait 7 days for a standalone battery charger to be shipped
Sent from my PC36100 using XDA App

That's kind of where I figured I was heading, jst. I'm going to play around with it tonight and I'll let you know tomorrow how it went. Might try completely different mods too... thinking about fresh.
Again, thanks a lot guys. BIG help.

The theme works great with cm 6.1.2. There are many people using it right now. I'm unsure of what could be happening here. Some phones are just picky. Mine for instance bootloops with any of myns roms as well as virus rom but I have no problems with other roms. I'm sorry my theme didn't work out for you.

t3project said:
The theme works great with cm 6.1.2. There are many people using it right now. I'm unsure of what could be happening here. Some phones are just picky. Mine for instance bootloops with any of myns roms as well as virus rom but I have no problems with other roms. I'm sorry my theme didn't work out for you.
Click to expand...
Click to collapse
Hey, it's no sweat! I've seen all the pics of your theme and I really wanted it. It's slick as all-hell, lol. And as for certain phones being picky, that's more than likely the case with my EVO. Since day one, my phone won't charge if turned off, and if I plug it in while it's off, I have to remove the battery to get it to turn on again.
Don't need to apologize to me... I should be thanking you for making something like this accessible to me!!!

You need the correct amonra recovery.
t3project said:
The theme works great with cm 6.1.2. There are many people using it right now. I'm unsure of what could be happening here. Some phones are just picky. Mine for instance bootloops with any of myns roms as well as virus rom but I have no problems with other roms. I'm sorry my theme didn't work out for you.
Click to expand...
Click to collapse
mikfroyo evo, with a side of aloysius 5 !

Alright, think I know whats up... I decided to humor a thought I had and install a fresh Cyanogen after a nand backup. I installed 6.1.2 and then installed the Gingerbread as recommended by jst. Only this time, I didn't wipe before I installed the theme. Worked like a charm. I'm going to try this with other themes too and see how it goes.

Kush explains why they don't work right here. http://forum.xda-developers.com/showthread.php?t=897026
Sent from my PC36100 using Tapatalk

stricklerjosh said:
You need the correct amonra recovery.
mikfroyo evo, with a side of aloysius 5 !
Click to expand...
Click to collapse
really? lol

I got it to work fine by not wiping before theme install, just mod install. t3, your theme looks awesome on my EVO. Thanks!!!

[Q] CM7 Nightly Reboots

Hey all, this is my first post here and unfortunately its a question I have with CM7 Nightly #8..
I've been running CM7 RC1 since it's release and I've had no problems, no reboots, no lag- nothing. I've steered clear of nightlies because every time I flash one I get random reboots.
Today I picked up #8 did a factory reset/davlik/cache wipe and did a clean install and flashed over Chad's incredikernel for GB as thats the Kernel thats worked best for me on RC1. I restored my apps via Titanium Backup like usual and set up everything back to what I had.. ten minutes later my phone goes into a boot-loop.
Anyone else having these issues?

What verison of CWM recovery do you have?

I flashed 3.0.0.8 shortly after it was released. Prior to that I was on the 2 series and still had the issue. I just went and flashed back to RC1 which was more stable for me. Any thoughts?
Sent from my ADR6300 using XDA App

[Q] one quick question about rooting mts3g

for installing cm7 do you need cm6 then upgrade to cm7 or you can just get cm7, and also, is cm7 a good build or should i wait until its more stable?

There's already been a Release Candidate for CM7 which is pretty stable, so far it's running wonderfully. It just doesn't have all the features and tweaks of CM6.
As for the first part, no you don't have to have CM6 first. You can just flash CM7.

You don't need CM6 to install CM7. Just make sure you also flash the correct Gapps.zip for the market to work.

jimczyz said:
You don't need CM6 to install CM7. Just make sure you also flash the correct Gapps.zip for the market to work.
Click to expand...
Click to collapse
Yes it should be gapss-gb-01202011.zip, if you flash an earlier one for froyo you get boot loops.

HELP
so i downloaded cm7 im stuck at the page where it says welcome to t-mobile touch the android to begin so i touch it and nothing happens then it goes back to the android mascot on the skateboard...any help

Deion123 said:
so i downloaded cm7 im stuck at the page where it says welcome to t-mobile touch the android to begin so i touch it and nothing happens then it goes back to the android mascot on the skateboard...any help
Click to expand...
Click to collapse
Did you flash Gapps?

You have to flash the rom, then before you reboot, flash the gapps.zip. Do a wipe and then flash them one after the other.

[Q] 6month of flashing and finally stump!!!

ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..

losphn said:
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
Click to expand...
Click to collapse
Strange indeed my friend. There have been many reports of bootlooping with cm7, and many can't recover. See the thread titled bootloops and no recovery. Its odd that older cm builds and sense work fine for you, and newer ones don't. Its interesting, your observation about the HDMI kernels. I wish I had some suggestions for you, but it appears as though you've exhausted all the things I would've suggested to you already. You've even ran ruu and rerooted. If that didn't work, I'm not sure what will...
Sent from my PC36100 using XDA App

going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..

losphn said:
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
Click to expand...
Click to collapse
Sounds like you tried everything before you even posted! At least you can run sense roms and older cm in the meantime, while you try to figure it out. Do other newer gingerbread builds flash and run for you? Or is it just cm7? I wish I had more to suggest, but like I said, it seems like you've covered your bases..
Sent from my PC36100 using XDA App

i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..

losphn said:
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
Click to expand...
Click to collapse
I will also say that I had good experiences with cm. It always ran smooth for me, and as you stated, everything worked. Same with all the other recent gingerbread roms have been flawless for me too. All the boot loop and no recovery issues, take it for what its worth. To each his own. I like all roms, but ill be on sense for a little while.
Sent from my PC36100 using XDA App

Have you tried flashing the FORMAT_ALL.zip from calkulin?

housry23 said:
Have you tried flashing the FORMAT_ALL.zip from calkulin?
Click to expand...
Click to collapse
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
From the OP ^^^^ He's wiped with calk's format all, used different recoveries, he's gone as far as unrooting and then re rooting. wiping again. He's tried everything I could think of. Reflashing recoveries(different versions), ran RUU's, re rooting....what's left?

thanks buckley
Sent from my PC36100 using XDA App

Guys, this is all over the forums now. Something in CM is causing these major problems that people are not able to recover from. One theory is that it's causing a bad block in the internal memory, which apparently, the Evo can't recover from.
I think I got lucky when it happened to me last month, where I suddenly white screened for no reason, while running a CM ROM, and I RUU'd my way out of it, but the problem has gotten much worse, obviously.
I loved CM, but at this point, I'm not stupid enough to try and run it anymore.
I hate to sound rash, but I'd lose any CM Rom's you guys are running until the Dev's can figure this one out.

Multiple problems with MIUI 1.5.6

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