In case other people have the problem: Update to the latest version of ppckitchen!
Hello,
I was not satisfied with the current available rom's and decided to cook my own, I used the ppcgeeks kitchen to cook a 21042 wm6.1 rom and included quite some OEM packages. After building and flashing the ROM my device started, and got in the SPL (where you can see the radio/rom version). But it would not get past there. I tried flashing again (without sim and or memory card), hard resetting after flashing, and upgrading the hardspl to 3.59. All to no avail.
I thought it might be an issue with one of the OEM packages, so I started a new project in the kitchen and left everything to default and directly build the bare ROM. The problem still persists. I noticed the only carrier available as a choice in the kitchen was AT&T, I live in europe so this might cause a problem? (absolutely not sure about this, just poking around).
Some more details:
R: 1.70.19.09
G: 25.83.40.02H
D: 3.14.00.00
Luckily I can get in the bootloader and flash whatever I want and just go back to the stock ROM, but I rather want my own, so I was wondering, can anyone help me with this issue?
Thanks in advance, peterrus
Does the backlight dim or does it stay on constantly? If it dims, then you have an issue with your SYS or OEM. If It doesn't dim, then you have an issue with your XIP. Was the kitchen already ported to run on a Kaiser? Which kitchen did you use from ppcgeeks? A little more information will help figure out your issue.
It does dim indeed, so it seems I have an issue with my SYS or OEM, tell me more.
I used the latest version but I am not aware of any versionnumbers, this is the announcement post: http://www.ppckitchen.org/forums/showthread.php?t=650
I could get the versionnumber from the kitchen, but I just uninstalled to try an older version, and updating it takes about 2 hours.
The kitchen is said to be kaiser compatible
I see however that there are others experiencing the same issues. I am gonna try an older version of the kitchen and see what happens.
Test the older kitchen like you are already doing. I suggest creating a base build without any packages included, so you can verify that the base ROM is OK. This will help with the process of elimination. Now, you should also read any documentation with that kitchen to verify that the OEM folder is exclusively for the kaiser. The OEM folder contains device specific settings and drivers. So using an Elfin or Polaris OEM with you kaiser will cause lots of issues (mainly the one you're experiencing now, stuck at splash screen). Again, give the older kitchen a try and post how that goes and we'll go from there.
Using the old kitchen () I can not succesfully produce a working 21042 ROM.
Using the old kitchen I can produce a working 20931 ROM.
I have not tested the new kitchen yet. But when I find time for that I will post results.
So, using the new kitchen I also can not produce a working 21042 ROM, a 20931 ROM works fine though, so I think i'll just leave it like this.
Unzip and add
This to your sys and see if it helps.
The ppckitchen authors have pushed an update which seems to fix the issue, so josh: I haven't tried your fix yet because I prefer the official update over other solutions, but thanks anyway it seems I can now succesfully boot the rom.
Ok, so wanted to start this because I have seen ALOT of people have this issue and I myself have loaded Hero and Non Hero ROMs onto a few MyTouch's and get this issue randomly. Figured we could start a thread devoted to people willing to test what the issue could be and people willing to try and help come up with a solution or at least pinpoint the cause of the problem.
Please try to keep this thread to the point as always guys!
I can tell you right now that I had two brand new MyTouch's today and did the exact same procedure on both and put QTek's latest Hero ROM on them and one has the blurry screen and one does not. The SPL was NOT changed from the .2006 SPL, simply loaded the FlashRec.apk, loaded Amon Ra's Recovery image, and wiped and applied the Qtek Hero ROM.zip.
Also it only happens to me when loading a Hero ROM, Cyanogen or any Non Hero works fine without any blurriness on BOTH devices.
This has happened multiple times ALL with the exact same procedure. So as far as I can tell it isn't the SPL or the ROM.
Any ideas what we can do to these MyTouch's to try and narrow something down to what the difference is between the two?
I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window
spyz88 said:
I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window
Click to expand...
Click to collapse
Kernel is a good place to start
Do you know what kernel versions the 4 ROMs you mention use or where we can find that info (short of bugging the crap out of the 3 developers lol)?
Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...
Wysie said:
Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...
Click to expand...
Click to collapse
That is most likely the "Animation" option being on or off.
Goto Settings > Sound and Display then turn ON Animation and see if that brings back you darkening/blurriness you are referring to.
If it does then it isn't the issue we are referring to, but thanks for the input! Appreciate any help/ideas we can get to solve this crap lol
Just tried that, no difference. So it may be the kernel... I've posted about it on Amon_RA's thread, maybe he can help with it more .
I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.
Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...
really stupid question but what sdcards are you guys using with blurry screens?
zambezy said:
I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.
Click to expand...
Click to collapse
I got these from others (didn't purchase them myself) so not sure when or where they got them, can't really ask them either.
But I am noticing the problem more and more frequently than when the phone first came out, so maybe there is something to the purchase date idea.
But again, how could it JUST be hardware, if some people can get other ROMs to function properly, ya know? It seems so random, certain ROMs work and certain ones don't and the ones that work for one person don't for another so the ROMs themselves must play some part, right?
spyz88 said:
Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...
Click to expand...
Click to collapse
Yea and I found that the kernel is the same on the two phones I am using right now (one works and one doesn't)...
Not kernel safe to say I think...
I was having this same problem on jacxrom orginally. Currently i unrooted, did the one click root, used the modified spl and cyanogens recovery and flashed the new jacxrom and working like a chram now.
Jrbourque said:
really stupid question but what sdcards are you guys using with blurry screens?
Click to expand...
Click to collapse
A brand new 8gb class 6 card
im just givin my 2cents in this and i think its the kernal i once used one of evil d's roms and gave mt the blur then he did another rom and fixed that so iunno but i feel its the kernal cuz wen i uploaded his new rom no blur just my 2cents
Not sure how much this adds BUT, I just unrooted my MT3G today and went the Goldcard method instead of One-Touch method. I first installed the ZeroXD with RAv1.2.1. This resulted in a blurry screen. I wiped and reformatted and tried my luck with eViL HeRo v2xx 32B and RAv1.2.1 and its running fine. First Hero ROM I have actually gotten to run without Blurring.
Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.
Amon_RA said:
Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.
Click to expand...
Click to collapse
I have tried this kernel with RAv1.2.1H ROM, and the screen still blurry.
Only RAv1.1.0H ROM have no blurry screen on my 32A.
Could you add Chinese Simplified to RAv1.1.0H ROM for me?
http://forum.xda-developers.com/showthread.php?t=554653
Thanks a lot!
I have the blury screen using any cyanogen mod ROMs...hero Roms are okay, just slow.
Used Amon's HBR to unroot, then flashed with the RAV1.2 recovery
Using red T-Mo mytouch (manf. 7/26)
About to replace with an entire new device.
Long shot.... : Could someone extract /system/lib/hw/lights.msm7k.so from RAv1.1.0 and push it to their blurry ROM and reboot?
My mytouch is same to this
pintspin said:
i am using following
1.33.2010 Engineering SPL 32Aboard HTC brand
i have flashed followign roms in sequence with results.. against them .
1, AMon _Ra rom ( 1.1.0) working perfectly fine...! no BLUR
2, H-hero-1.79.482.3-32A-RAKrnl.zip blurring
3, v3_Full_Hero_32a-gbo_v2 blurring
4, hofo ion rom 1.05 32a blurring
5, JACxROM v1.3 blurring
6, myhero-1.0.0 blurring
7, RA-IONv1.2.1H.ziRom-RA-IONv1.2.1H.zip blurring
8, Rom-RA-IONv1.2.0H.zip blurring
9, cyanm-4.0.2-32a.zip blurring
1o .....again.... went back to AmonRa 1.1 the best working rom for me so far....! i beleive all the new roms after 1.1 update are having some problem ....
one more thing i noticed that after flashing...every rom was working perfectly means NO BLUR but it will be blurring just after the screen go to sleep for once and when it came back from sleep it becomes blurry and the GAMMA seems to be increased automatically
Click to expand...
Click to collapse
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
i just had the same prob. im on moto droid. comming from droidmod 1.0 after reboot after flashin newest cgnmod it jut hangs on moto logo. went back to last backup
Cyan doesn't support the droid does it? :S
Mraellis said:
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
Click to expand...
Click to collapse
Make sure the death spl was installed and make sure to wipe before installing. Install cyan and then gapps without rebooting in between.
I usually have to install gapps after cyanogen. Some people before, some people after. It's kinda odd.
Also, for the droid, there is a cyanogenmod. Dunno if CM5 is on there yet, though. Don't really know anything about the Droid.
I read somewhere that there was a bug in 5.0.7 where you can't use the terminal method to install it, you have to use amon-ra recovery instead (I can't find the page anymore)
I think CM 5.0.8 fixes this
I've been using Skyraider ROMs since 2.5.x and have been more than satisfied with them. However, I felt it was time to change things up a bit... so I went ahead and flashed Myn's Warm TwoPointTwo By Incubus26Jc.
The ROM is great so far. However, I can't get used to the Gingerbread keyboard or the black and green theme. So I was wondering if there was a way to get the android keyboard from the Skyraider ROMs onto my phone.
Your help is appreciated!
So I did a little more searching around and think I may have found a solution; I just need to know if this is the right thing to do.
Would I be able to simply pull the
/system/app/LatinIME.apk
/system/lib/libjni_latinime.so
Click to expand...
Click to collapse
out of the Skyraider .zip and push it to my phone?
Incubus offers a smorgasbord of options. If you go check the thread, there are a few different keyboard options that you can flash from recovery.
I am interested in making my own theme with UOT Kitchen for the ROM I am currently using, PureAOSPtheory. I tried building a theme, and used a rom listed in the kitchen, the Cyanogen 7 one. Is there perhaps a better setup for this? When I tried flashing it, I got stuck in a bootimg loop.
Thanks.