Database Develop

[SOLVED] - Nandroid restore nerfs Kyocera splash screen.

Well, now that we can use clockwork recovery, we can start trying to figure out why a nandroid restore causes the Kyocera splash screen to be replaced by a whit horizontal bar.
Anyone have any suggestions?

My assumption would be that the Kyocera splash screen is hardcoded into the phones "hidden files" and when you flash Clock work and do the Nandroid restores it is probably overwritting them.

Been searching on the net for any instance of a similar issue, to no avail (yet).
Hidden files hmm? Mind elaborating?

Spz0 said:
Hidden files hmm? Mind elaborating?
Click to expand...
Click to collapse
lol I say this b/c we cant find these files anywhere and almost every OS whether it be a computer or a phone has "hidden files" that the user cannot access. These files usually hold important system information that if altered would likely result in unstable operation or even the lack of operation. These files are normally stored on a partitioned part of the "disc" that is not accessible. When I used to develop for the Jailbreak community on the iphone we ran into this a lot. Of course there is almost always a work around when it comes to modding/hacking.
I am trying to learn as much as I can about Android OS and so far I can say it is very, very different than the iphone OS.

I am pretty sure the image is in the boot loader.
There is a 4K header, but only the first 2K are used. Then after that the boot files start.
I can rip the boot loader with either doing a "cat /mtd > file.img" (or something like that, don't remember off hand), or with the dump_image program.
If I use the cat, I get a white bar, if I use dump_image, I get a black screen. dump_image removes empty sectors I believe. That's the difference so it must be in those sectors.
On top of that, if I flash the sprint boot loader, I get a Sanyo image. So basically, someone needs to go in there with a hex editor and manually copy whatever is needed into that useless space after the first 2K and the 4K. At least that's where I think it is. Someone could do a compare between the dump_image and the cat to be certain.
(That's all from what I remember from a few months ago)
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.

phazei said:
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.
Click to expand...
Click to collapse
Would any of the files from the zclusive pc update route be of any help? I still have those.

I'm not really sure if this is any help at all, but in normal linux distros the initrd.gz is stored in the boot partition. This archive contains scripts used to boot the computer. It has been known to contain image files. I do not have the necessary OS right now to gunzip and investigate. If you guys want to find out if that file exists on android and see what is inside, it might be a good lead. If nothing else, it may point to the correct image.

I hace CentOS Ubuntu and a few other live distros, Ill check the boot partition for the kyo logo.
Sent from my Zio using XDA Premium App

NO MORE WHITE BAR!
Mattix724 said:
So, I have dumped my boot.img finally because gregnotcraig and other devs restored with nandroid and lost the Kyocera splash. With this boot image below you can restore your Kyocera splash. NO MORE WHITE BAR.
http://db.tt/zisPRYH
Simply enter fastboot and place this boot image in your SDK folder where fastboot is located.
Run this command...
"fastboot flash boot boot.img"
"fastboot reboot"
And there you have it, the stock splash screen.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Sent from my Zio using XDA Premium App

i said it in #openzio, but i'll say it here, too...
thank the dog you had that. you made several people in irc happy little campers!

Solved!
http://forum.xda-developers.com/showthread.php?t=994754

Mattix724 said:
NO MORE WHITE BAR!
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
For those of us who would like to change up the Kyocera logo, would it be possible to flash the Sprint ZIO boot.img to a cricKet ZIO (and not lose functionality)?

No.
Sent from my Zio using XDA App.

We will be releasing a custom boot image soon. Source is available just need to recompile with new splash1
Sent from my Zio using XDA Premium App

Anyone who is good with boot animations tell me why mine won't work on ICS?

Hi,
I am no noob, been around a while but I am having the most dramas with my ROM with the boot animation? Go figure?
Anyone want to help me out here? works fine in the bootanimation preview windows application?
all of the files I have used to make the boot animation in here (66Mb) as well as several zips and bootanimation previewer

download absolute system from the market. it has a bunch of b.a. to choose from and you can edit to you phone size and fps
sent from my still kicking ass aria

[Q] how change boot logo?

I watched the entire forum but did not find solutions. how to change the boot logo on our device?

Same as on any other android, I use a mixture of romtoolbox by the guys that make cwm and a app called beauty boot to preview the boot animations because I'm too cheap to buy the full thing. Just don't flash cwm just because I'm mentioning rom toolbox and cwm, that would end badly I'm assuming. If you were however talking about the initial kindle fire orange logo that's not animated we cant change that, its built into the boot loader that we can't modify. Basically if you are doing this manually you just replace the bootanimation.zip in the kindles /system/media folder and fix the permissions to user: read write execute, group: read execute, others: read execute. You may want to double check those permissions though first by checking the current ones permissions, as I am on cm 10.1, but I am pretty sure the permissions are the same.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Same as on any other android, I use a mixture of romtoolbox by the guys that make cwm and a app called beauty boot to preview the boot animations because I'm too cheap to buy the full thing. Just don't flash cwm just because I'm mentioning rom toolbox and cwm, that would end badly I'm assuming. If you were however talking about the initial kindle fire orange logo that's not animated we cant change that, its built into the boot loader that we can't modify. Basically if you are doing this manually you just replace the bootanimation.zip in the kindles /system/media folder and fix the permissions to user: read write execute, group: read execute, others: read execute. You may want to double check those permissions though first by checking the current ones permissions, as I am on cm 10.1, but I am pretty sure the permissions are the same.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Change animation easily. I want to change the boot logo

Oh, well that's going to be stuck as is, you might be able to change 2nd bootloader's image if you really know what you are doing, but the m-shield is on on our processor so making any changes to the boot loader is a bad idea, it would cause a hard brick.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Apollo-74 said:
Change animation easily. I want to change the boot logo
Click to expand...
Click to collapse
It would require modifying the bootloader so don't count on it ever happening.

[Q] Removing AT&T boot animation

Now that we have root and are able to remove most traces of AT&T crap from this phone this is the only one left for me. Is this possible to remove yet with root access?

ROM Toolbox Pro does provide this as an option. I cannot say for sure that it will work/brick your phone. There are tutorials you can find on Google to create a qmg file and over write the existing one.
Use caution.
Let me know if you find something usable!

556AR said:
Now that we have root and are able to remove most traces of AT&T crap from this phone this is the only one left for me. Is this possible to remove yet with root access?
Click to expand...
Click to collapse
I have a tool that i wrote that will do exactly this and also enable any standard bootanimation check out this thread http://forum.xda-developers.com/showpost.php?p=53494610&postcount=1 remember it is beta and is being updated also make sure you download the patch file from the attachments its needed to make the bootanimation tweak work

I renamed the boot animation file by adding a ".bak" at the end of it. That took care of the boot animation, however, the sound remained. I disabled the boot sound with Wanam if I remember correctly. No problems so far.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

sutehk said:
I renamed the boot animation file by adding a ".bak" at the end of it. That took care of the boot animation, however, the sound remained. I disabled the boot sound with Wanam if I remember correctly. No problems so far.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where's the animation file at?

/system/bin
The boot sound can be disabled in Wanam under the sound heading. Just double checked to be sure.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

Nexus 6 PIT file? System dump from Att?

Does anyone know if our Nexus 6 requires a pit file for flashing? I managed the throw my partition layout out and remove some files that I shouldn't have. I now have a device that boots but has no sensor support at all. Nothing is showing up in /dev node even when manually creating the node with BB mknod. The logcat has tons of errors all pertaining to not being able to open the require port for the sensors.

Pit file? I'm assuming you're probably coming from a Samsung device since they are the only ones to use those files. If you're unlocked I'd back up my data and flash the stock image
Sent from my Nexus 6 using XDA Free mobile app

I didnt make a backup before messing around, thinking that we would have an att dump soon. And as you can tell, yea I am used to Sammy devices. I deleted a few files and now my sensors will not work. I tried ripping /etc and /system/etc from a friends Nexus 6 but even after flashing a stock image my partition table is really messed up. Flashing a stock recovery does nothing but boot loop and the phones camera responds really slowly. I have Att sending me a new one, but who knows when that will be.