Related
Ok devs or whoever....
I am looking for some info and apparently i couldnt find any.. (this where u make me look like an @ss and send me a link or not)
I was able to flash a splash screen (very first screen u see when booting up) on both my G1 and M3GS but havent on my G2 or G2x.. Whats in entail to do so the the G2X... To change the first screen...(aka trinity when u flash morfics kernel)
I read somewhere that the boot.img needs to be split to do so... ??? ... Any info would be nice...... Subtle hints to the right whereabouts for this info would be nice to....
Use root explorer and go into system> media. In that file you'll see bootanimation.zip. You can change that out with another .zip of your choosing and rename it bootanimation.zip. This was how it was done with the Vibrant and I would think it would be the same with the G2X.
Ok Charlie ill check it out... thought that was just the boot animation though without splash screen. Mmk though
Sent from my LG-P999 using XDA App
Ne1 with suggestions
Sent from my LG-P999 using XDA App
I have not been able to change it either using various guides. Changing bootanimation.zip will not change the splash screen, only the boot animation.
twiztidnutzzzzz said:
...[edited]...I was able to flash a splash screen (very first screen u see when booting up) on both my G1 and M3GS but havent on my G2 or G2x.. Whats in entail to do so the the G2X....
Click to expand...
Click to collapse
This is worth the $1 or whatever it is in sooooo many ways. Look at the related apps too (boot installer)... dude... you have no idea the simplicity of this and how clean each install was (I have tried probably 20+ of the boots and was able to customize by ripping one of the zip packets off the SD.... it shows the split too in the zip file.
Welcome to all that is glorious: https://market.android.com/details?id=com.canvs2321.absolute.system&feature=search_result
I'm on 2.3.3 fyi... didnt read the details but follow protocal with backups yada yada... =)
Yuhfhrh said:
I have not been able to change it either using various guides. Changing bootanimation.zip will not change the splash screen, only the boot animation.
Click to expand...
Click to collapse
...oohhhh... I missed that clarification. Ok so you want to change the "LG" splash just before the bootani starts... let me look, I gotta get back to you though... I came across that a while back and the instructions that the dev dropped with it didn't work but I tweaked it and got it. I gotta dig..
Yay the lg screen before bootanimation....
From what I read its un boot.img and that needs to be unpacked which would meen that every new rom flashed would have to b edited I assume
Sent from my LG-P999 using XDA App
twiztidnutzzzzz said:
Yay the lg screen before bootanimation....
From what I read its un boot.img and that needs to be unpacked which would meen that every new rom flashed would have to b edited I assume
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yeah I can see it when I dig with root explorer and then throw the .rle in my drop box. I looked for that installer and was hitting blanks but I will find it today and also tweak that graphics archive. GIve me a few to diddle.
I also have a ViewSonic GTablet, which is also a Tegra 2 device. See this procedure:
http://www.slatedroid.com/topic/162...logos-replace-viewsonic-logo-g-tabletzpad-t2/
Basically you use nvflash to put a bitmap file on a specific partition.
THE ABOVE PROCEDURE WILL NOT WORK ON YOUR G2X, but it's a starting point to figure out how to do it on the G2x.
Hey IB you make any progress?
Sent from my LG-P999 using XDA App
Just wondering if anyone has figured out how to change the names of the images or add images to /mnt/.lfs so you can have a custom start up screen. I have the SGS4G and I highly dislike the tmobile splash screen that comes up. I am not talking about the boot screen as I know how to change that. I have tried renaming and adding a different pic with the same name as the one that is used, but nothing ever changes. I have tried with droid explorer, I tried with an update.zip and pushing with CW in recovery mode, I have tried pushing with terminal emulator, I have tried pushing with adb, and I have even tried just copy and paste with Super Manager. Any suggestions?
Look up a bootanimation tutorial. You can only use this on Froyo since there's no kernel supporting it for GB yet.
Are you referring to the pink screen or the splash before?? I know that the mobiletechvideo guy figured out how to change for a few galaxy phone's first boot screen.
Sent from my SGH-T959V using XDA App
I know...
FBis251 said:
Look up a bootanimation tutorial. You can only use this on Froyo since there's no kernel supporting it for GB yet.
Click to expand...
Click to collapse
I know how to chnage my bootanimations. That is easy. I am talking about the splash screen before that...
The first one
champ1919 said:
Are you referring to the pink screen or the splash before?? I know that the mobiletechvideo guy figured out how to change for a few galaxy phone's first boot screen.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I know how to change the pink crap (which was the first thing I got rid of as soon as I got my phone, then the bloatware). I need to know how to change the first splash screen that comes up... Who is this mobiletechvideo guy? Do you have a link to his work/page?
Its josh at mobiletechvideos.com... He's got links for vibrant and sgs II..
with the vibrant, you have to flash/Odin a param that erased the tmobile/att file then manually push new .jpg file in.
I've tried his i9000 & sgs2 files... Rainbows and reboots...
I've asked if/when/how for us... No response yet though guess he's busy unbricking sgs 2s and such..
Sent from my SGH-T959V using XDA App
If you have any problems or questions about this ROM please post them here so we can try and keep the other thread tidy. Also if you'd like to request something or some sort of feature being implemented into a future release ask away in here. I'll try and answer any and all questions ASAP. Hope you guys enjoy our port of this incredible ROM
Umm yes.... Im looking to flash this ROM... what does this do? .
But seriously... Nice... just noticed this... Good idea.
What all is not working on this Rom? I installed it yesterday and the only thing that bothers me is the fact that no MMS files will download when you receive one from anyone. What's the current outlook on the MMS? I think I saw that Bluetooth isn't working either? Also excellent job on the port/build! My favorite so far.
Sent from my SGH-I997 using XDA Premium App
new issue...I just tried installing the extra kernel and now my phone will not boot normal or to recovery or download mode. Has anyone had this happen on theres?
Sent from my GT-P7510 using XDA Premium App
Under developer settings, would using the options "allow GPU rendering" use more batter than if it wasn't in use? Speed seems to improve slightly but enough to be noticeable, is there a really big downside to this setting? Ohh and is there any way we could get some type of security lock built into the rom to have the option to password protect apps? Kinda like MIUI has it? Thanks in advance
xXMRH09Xx said:
What all is not working on this Rom? I installed it yesterday and the only thing that bothers me is the fact that no MMS files will download when you receive one from anyone. What's the current outlook on the MMS? I think I saw that Bluetooth isn't working either? Also excellent job on the port/build! My favorite so far.
Sent from my SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Hmmm never had any MMS problems myself at all. You might try downloading the latest build posted in the dev section. It should hopefully fix your problem. And correct, bluetooth isn't working and won't until the kernel issues get fixed. But mainly everything works perfect.
SayDfuse said:
Under developer settings, would using the options "allow GPU rendering" use more batter than if it wasn't in use? Speed seems to improve slightly but enough to be noticeable, is there a really big downside to this setting? Ohh and is there any way we could get some type of security lock built into the rom to have the option to password protect apps? Kinda like MIUI has it? Thanks in advance
Click to expand...
Click to collapse
Never used GPU rendering so I honestly can't say for sure. And as for the security lock....never looked into it so I don't really know what adding it would entail.
xXMRH09Xx said:
What all is not working on this Rom? I installed it yesterday and the only thing that bothers me is the fact that no MMS files will download when you receive one from anyone. What's the current outlook on the MMS? I think I saw that Bluetooth isn't working either? Also excellent job on the port/build! My favorite so far.
Sent from my SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I have seen it suggested to set mms proxy to 66.209.11.32 in apn settings for some of the other ice roms.
I got the MMS working. Under apn setting "ATT LTE" where it says "PTA" I changed it to say "phone". Works perfect now.
Sent from my SGH-I997 using XDA Premium App
When flashing this coming from GB (2.3.5) i got blue recovery with half the screen filled with "rainbows". I know this is a boot loader problem, and i followed the instructions with double flashing and also every time i boot it up, right after the Samsung logo i get the whole screen filled with "rainbows". Is there anyway to flash the proper ones?
slicingtaco said:
When flashing this coming from GB (2.3.5) i got blue recovery with half the screen filled with "rainbows". I know this is a boot loader problem, and i followed the instructions with double flashing and also every time i boot it up, right after the Samsung logo i get the whole screen filled with "rainbows". Is there anyway to flash the proper ones?
Click to expand...
Click to collapse
You would need to flash the GB Bootloaders.. You can either use Odin or Heimdell.. I personally used Odin, so thats what i am going to suggest.. HERE IS THE LINK - The part you need is towards the bottom of the page when you go to that link. Here is the part you will need to follow
1.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin. If something happens to cause a flash of these bootloaders to fail, then you run the risk of bricking your phone. See THIS post and THIS post for more of an explanation of why bootloaders weren't included in the rooted UCLB3 Odin packages.
scott.hart.bti said:
You would need to flash the GB Bootloaders.. You can either use Odin or Heimdell.. I personally used Odin, so thats what i am going to suggest.. HERE IS THE LINK - The part you need is towards the bottom of the page when you go to that link. Here is the part you will need to follow
1.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin. If something happens to cause a flash of these bootloaders to fail, then you run the risk of bricking your phone. See THIS post and THIS post for more of an explanation of why bootloaders weren't included in the rooted UCLB3 Odin packages.
Click to expand...
Click to collapse
So just to be clear, you wouldn't highly recommend flashing the proper one's? If you so happen to attempt to flash them and for whatever reason brick the device would you end up with a soft or hard brick, and would it be repairable?
This seems to be an ICS problem, or at least ICS ports for our phones; I have tried two other ICS ROMs, and none of them are playing .wma files, but as far as I have seen are playing .mp3 files just fine. Every time I open try to open up a .wma file it says, "This file could not be played," or "Invalid file extension." Any ideas?
xXMRH09Xx said:
new issue...I just tried installing the extra kernel and now my phone will not boot normal or to recovery or download mode. Has anyone had this happen on theres?
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
I'm having the same issue of not being able to boot into recovery, either through the power menu or through the 3-button method. I flashed the ROM successfully and can boot into it but i have not flashed GAPPS yet. Is there a way to fix this or do I need to ODIN back to stock and try reflashing everything?
Stuck in Recovery
Ok I flashed Beta r3-beta2 and is stuck in recovery....didn't see any instructions so what or where are the directions to flash from gb? and what can I do to get it to boot?
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium
lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????
JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?
The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.
jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium
jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium
I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.
By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium
Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.
I have UCLB3, dman's deodexed version. Entropy kernal. I had stock kernel and was trying this too. "bootanimation.zip" is in the system/media folder but it won't show. All I get is the Samsung screen then the phone's lockscreen. I think dman did something to skip the boot screen, but I can't figure out what. I'm just really confused because what I'm doing worked on CM9. Same animation and same location. Plain and simple. But on UCLB3 it's just not working.
Can you use other boot animations? Try the ones in the AEON thread as those are made for the infuse specifically
Sent from my SGH-I997 using xda premium
Try renamingng bootanimation.zip to sanim.zip
Some of the older roms used sanim.zip instead of bootanimation.zip
If that doesnt work then flash one of entropys or send gb kernels...then usr bootanimation.zip
(Bootanimation is enabled by the kernel-I think...)
Sent from my HTC Holiday using Tapatalk 2
I renamed it and flashed entropykernel but still no dice. What do you mean by "send the kernel"?
JoeyofBladez said:
I renamed it and flashed entropykernel but still no dice. What do you mean by "send the kernel"?
Click to expand...
Click to collapse
Lol...phone auto correct...I meant Zen kernel
And with entropys I think it has to stay named bootanimation.zip
I'll flash back to stock uclb3 later so I can tell you exactly what to do
Sent from my HTC Holiday using Tapatalk 2
First post, gents.
http://forum.xda-developers.com/showthread.php?p=21230579
Edit: btw, flash zen tool kit. A whole bunch of boot ani's
I did name it that and I have entropy kernel... my kernel version says 2.6.35.7-I977RUXKG3-CL366622. I get the Samsung splash screen and then it just boots up, black screen and then lock screen. This animation worked on CM9. It works in the Boot Animation factory preview. I pm'd dman and he said that animations work on all of his ROMs. So why do I get a splash screen then a black screen for 15 seconds.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
I'll try zens kernel too but if it makes any difference I have a modded systemui, framework, and twframework. I put on lidroids quick settings mod, and also custom icons and battery icon. But I don't think that should even matter. Any other ideas guys?
JoeyofBladez said:
I'll try zens kernel too but if it makes any difference I have a modded systemui, framework, and twframework. I put on lidroids quick settings mod, and also custom icons and battery icon. But I don't think that should even matter. Any other ideas guys?
Click to expand...
Click to collapse
Did you modify the build.prop any? There is a command that can be placed there that disables your boot animations
Sent from my SGH-I997 using xda premium
No I didn't. But dman did when he made it. And I read about that line, that disables boot animations. I couldn't find anything that looked like it in es file explorer. I read that he did it to make the boot time faster. But the line isn't there in build.prop. I mean based on the phones behavior, you would think that the line is there. What does it look like again? And would it be anywhere else besides build.prop? Are there any other lines or files that can be modified to disable it? Because that's what I believe I need to look for. It would be nice if he posted here. But like I said, I pm's him and he told me that all of his roms support custom boot animations. That's all he said, besides the part about renaming it to Sanim.zip. but as I said, I did that. I even deleted the two ".qrg" files that made up the Samsung boot animation. They were in system/media as well. Before I did that, the AT&T boot animation would play despite the presence of a custom rom in system/media. Once I deleted them, I just got the black screen until boot.
JoeyofBladez said:
renaming it to Sanim.zip. but as I said, I did that. .
Click to expand...
Click to collapse
in the /system/media
just put 2 copies of the same animation:
"sanim.zip" and "bootanimation.zip"
both are in lower case letters...no caps
That was a good idea but no dice... 10s of the splash screen and 10s of a black screen. But now that I look at dmans topic, maybe I was supposed to flash this kernel? Refer to my first post for the link to dman's topic.
JoeyofBladez said:
That was a good idea but no dice... 10s of the splash screen and 10s of a black screen. But now that I look at dmans topic, maybe I was supposed to flash this kernel? Refer to my first post for the link to dman's topic.
Click to expand...
Click to collapse
You got me there, Joey. I've no idea why your phone is not cooperating...seems to work ok on mine.
qkster said:
You got me there, Joey. I've no idea why your phone is not cooperating...seems to work ok on mine.
Click to expand...
Click to collapse
Which Rom and kernel do you use? im not picky about the Rom and kernel but i just want something like lidroid 's quick settings and extended.power menu (modued system.ui, easily flasable through cwm), i want custom icons through uot kitchen, and i want custom boot animation. if you have a Rom/kernel combination for that, please share it with me. because cm9 was cool but remember i.couldn't change the icons? and it was laggy ! so i need something gingerbread . i also like touchwiz, does your phone have touchwiz still or did you remove it and go stock android?
i mean just share with me what you use. i can't create and mod like you can.but i just want something for the three things i specified above. quick settings, boot animation, and uot kitchen icons. Preferaby quick and.painless heimdall because odin and adb NEVER work for me
JoeyofBladez said:
Which Rom and kernel do you use? im not picky about the Rom and kernel but i just want something like lidroid 's quick settings and extended.power menu (modued system.ui, easily flasable through cwm), i want custom icons through uot kitchen, and i want custom boot animation. if you have a Rom/kernel combination for that, please share it with me. because cm9 was cool but remember i.couldn't change the icons? and it was laggy ! so i need something gingerbread . i also like touchwiz, does your phone have touchwiz still or did you remove it and go stock android?
i mean just share with me what you use. i can't create and mod like you can.but i just want something for the three things i specified above. quick settings, boot animation, and uot kitchen icons. Preferaby quick and.painless heimdall because odin and adb NEVER work for me
Click to expand...
Click to collapse
Run the dman's uclb3 deodex based.
use either entropy's dd or zen's a16 kernel.
http://forum.xda-developers.com/showpost.php?p=23118162&postcount=3
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
Use titanium back up to remove what att bloat you don't want.
Everything should be working properly.
How to start:
Load up the firmware.
Run Zen tool kit.
flash the kernel you want in the tool kit
flash the boot ani you want in the tool kit
run the customization you want.
submit the files to uot etc..it all should work.
if in doubt, odin or heimdall back to complete stock and work from there
Yeah once internet in my dorm goes back up, I'll heimdall back to stock and work from there. Probably in a few hours I'll post back here and let you know how it goes. It's nice having heimdall because this phone is actually a lot harder to root and install cwm on than others I've tried. It's just a very disagreeable phone that gets fussy a lot. But I'll use entropys driver and try everything tonight. Quick question though. When flashing kernels should i wipe system/cache/dalvik before i flash? Just double checking.
One more thing. In that topic you linked to... Is that uclb3 rom from the heimdall one click odexed or deodexed ? Because lidroid states in his thread that his mod for quick settings only works on deodexed Roms. If you know another way for me to add.more icons.to the quick setrings menu (data,brightness, etc.) then.do tell
I flashed lidroid's quick settings and the 8 lockscreens package. So I get the quicksettings app in the drawer and can toggle them off and all. But no matter what I toggle, the quick settings in the notification bar menu stay the same(stock) and won't change. Also, the power menu is stock and not the extended one. Help?
Boot animation is working by the way. =p
Zen's toolkit fixed everything. lmao