The attached zip file are the actual *.tga files from the boot image of the TP.
Every time there is an issue an image will be display.
It could have help to not only provide an image (universal language) but also a basic description of the meaning and what to do next.
There has been so many confusion of their meaning that has created more problems than fixes.
Not everyone will describe an image the same, seen is believing!
Now here they are for your viewing pleasure.
Download and decompress it, open each file and read the title or name, is self explicatory.
thanks i am going to verify i have three with interogation sign i should have something special for these cases automated for chip A5
Related
Hi - first major post so bear with me!
After 'cookin' my own extended ROM a few times, I realised that harvesting the various CABs was only the first step - I then had to trawl this (fabulously informative) forum (and wiki) and identify each CAB to see if I actually wanted it in this particular ROM – sometimes I’d find a picture (really helps), and sometimes not, either way I would always forget what something was and have to re-find it.
So I wrote a utility to help me - and I'm sharing with everybody else 'cos that's just the kinda guy I am. XtendROM scans a folder (I’m old-school so I still call ‘em directories, but I’m trying to speak windoze here) and treats that folder as the ‘library’ – it is from there one can select which CABs you want to include. I’ve set things up for the Himalaya (I have an XDAII) so the default extended ROM size is 64Mb, although it only warns you if you go over that.
The principal is simple - deliberately so. Information on the CAB files is stored in TXT files and the preview images are stored as GIFs, BMPs or JPGs (always the same name as the CAB file, with an extra file-extension). I’m thinking that we could post TXTs/images and maybe even CABs in this thread, thereby making cooking a ROM as easy as downloading the CAB/TXT/image, saving it to the ‘library’ and choosing it for your ROM.
Drag & drop should work (to some extent at least) and the ROM files can be moved up/down in the config.txt file easily enough – after all I made this for my own use and getting the information from the web-pages is sometimes the trickiest part. I’ve recently added an option to copy the selected CAB files into a separate folder, this way I can easily copy the new files into the new ROM without having to search manually (computers ARE here to make life easier – allegedly).
Um, I think that’s about it – consider this a first-release so I’ve undoubtedly missed stuff, and I’m pretty sure I’ve forgotten to save some settings into the registry (I’ve had to get on with some real work, but this version works okay – mostly). Of course, if this utility kills your system, turns into potted-plants or does anything else I’m not expecting then you’re on your own – if you have doubts then don’t use it, I ain’t getting sued just for sharing my stuff.
I'll be adding some TXTs/images/CABs here myself at some point - I'm just too busy with other stuff at the moment (patience, I'm told, is a virtue).
Any problems, comments, questions or thoughts then please post here – knowledge is a thing best shared.
:edit: - I forgot to mention above, but when a file is copied the file-extension is automatically checked and the approriate command inserted into the CONFIG.TXT - for example, copying a .EXE file will default to 'EXEC', whereas a .TXT file would generate a CPY1/CPY2 command (to copy into \Windows).
Toodz,
- StarFux -
Excellent, let's me try and I will post my feedback later.
Thank a lot.
cool program.... downloading now...
thanks
No further comments?
Just checkin'-in... so, no feedback? Must be just that good then ...
-sf
Thank you krab.. Let's me try..
Some TXT files to get things started
Attached are some TXT descriptions from xda-developers - the zip-files are named according to the username of the person who wrote the text (all credit to them, not me) - I've just compiled the data into a format that XtendROM will make use of.
yann.zip - from http://forum.xda-developers.com/viewtopic.php?t=6470
sin.zip - from http://forum.xda-developers.com/viewtopic.php?t=16916
Just unzip into your chosen library folder.
S'all - have fun.
-sf
besides of having one error on my first run .. just forgot wat it is .. i think you've done a greate job .. now its much easier to create config.txt and to avoid .. further error if i created it in notepad .. btw tnx for the tool m8 ..
...very nice looking tool )))
THANX
buzz
What a great application
Thanks for sharing
Now maybe we can create all huddle together and create a central library for all known extended ROMs so we can cook our own ExtROM
Thanks for all the positive feedback! - I'm working on some tweaks to cope with creating compressed ROMs at the moment (thanks to some great feedback) - I'll post here when I've sussed it
Thanks again!
-sf
Giving up
Hi all - well excessive demands on my time from work & home have meant I've been unable to tinker with my util, so I'm giving-up trying to find time and have decided to sleep more instead.
If anybody else wants to play with it (it's written in Delphi 7 & uses a few libraries but could be played with), then PM me and I'll send you the source so that you may continue development (if desired).
Hope everybody continues to enjoy the util anyway - L8rz.
-sf
Hi
I have been cooking ROMs for a week or so now and all has been great. I can't recall making any major changes, but I now get the following when the phone does it's initial boot (and every boot after that)...
"The file 'poutlook' cannot be opened. Either it is not signed with a trusted certificate? or one of its components cannot be found..." And I can't do anything. i have searched but i have nothing found related to this problem
I am using (and have been using) IOLITE 20765 ROM and SYS and OEM 5.50.
I have made no major changes - I was testing other ROM's and SYS's, but I have reverted back to 20765 and I get this error - I never got this error on the other versions of ROM's and SYS's.
I have also redownloaded the files and created a new Kitchen folder to cook in...
Please can someone help???
DT
An update.
Redownloaded SYS, ROM, OEM and Kitchen 1.2b and started from scratch. It now works, so I am not sure what the heck I did to the other folders ...but I am sure glad it is functioning again
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Thanks
DT
d_train said:
...but I am sure glad it is functioning again
Click to expand...
Click to collapse
That's why we have HardSPL. Some cooked ROMs will not even boot. In those cases, take battery out, replace battery, turn phone on with camera button held down. This will drop phone into bootloader mode and allow a new ROM to be flashed.
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Click to expand...
Click to collapse
These associations are done in registry. For packages, you need to hunt through the kitchen for the registry and make the appropriate changes.
When I needed to change association for videos to TCPMP, the way I took was:
1) Snapshot of registry
2) Ran TCPMP. Made the association changes in its options.
3) Resnapshot registry.
4) Compare the changes.
5) Scan through the entire kitchen and find and substitute the registry keys in the RGU files and also .dat files
6) An alternative is to create a registry change, to be applied after the main ROM is built (or run at first bootup) like all the registry packages.
Total Commander is great for this. It allow search of strings of text within files in a folder and display all files with the search text. It also allows comparison of 2 files, and highlights the differences. Good luck. This is very time consuming.
This thread suggests that to change splash image, one needs a proper android-info.txt
Google and forum search have not located one for viewpad 7, and I'm not cool enough to make my own from scratch without severe risk of bricking the device.
So the questions are, does anyone here have one and would said person kindly share it ?
Also, any ideas on how to extract the original splash (so that I can "work from it" to ensure that size and whatnot are right) ?
ISSUE RESOLVED (THOUGH VIA A DIFFERENT APPROACH) http://forum.xda-developers.com/showthread.php?p=24284512#post24284512
Hi,
I've been trying to locate the "boot photo" on an Amlogic S912 TV box that I have in order to change it. It is the first image that you see when you power the unit on, followed by the boot video which I have already changed and is located in the "etc" folder of the unit. I cannot find the location of the initial photo though. If anyone can tell me what folder it is located in I would certainly appreciate it! I believe it is either in bmp format or png format. The unit is running android 6 and these are the folders that are in the unit. (If this question is in the wrong section I apologize in advance!)
Thanks for any help anyone can offer.
It's not gonna be there. That image is stored in one of 2 places in every device I have had. It was either on the boot partition or bundled with the kernel. Either way you would have to flash the device to change it.
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
fxbill said:
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
Click to expand...
Click to collapse
You would need to extract that partition and find the file that it is placing in temp. Change the file and refresh the partition. Mind you this is dangerous and doesn't always work. But as long as you ha e an unlocked bootloader you should be able to recover.
The "logo.partition" is a single file in the level 1 temp file directory. It is actually a single file type, but I don't know how to disassemble the file or what program would open it. I can get a hex editor to open it, but that doesn't help me much since it is a 6 megabyte file and the hex, of course, is unreadable...at least to me. There are about 20 files in the level one temp folder of which this is just one. The program works just fine with Amlogic devices that are running Android 5 and below and does almost everything with Android 6, but this is one of the things that it won't do in Android 6 and the Customization program has not been updated for a couple of years. I'm hope that eventually it will be but at this point I need another way or program that will allow me to do it!
Found it..... It's in the Level 2 folder. Easy to put into the firmware once you know where it is!
I have an offline game that does a file verification check each time you open the game. This game is a port of a PC game and as such the file structure is identical. With other games like this I have been able to use mods available on the PC version but in this case the file check is recognizing that certain files are larger(HD res models and such) and won't get past the file check. I'm curious if anyone has any experience with file checks like this and how exactly they are being performed and how I could remove them whether that be modifications to the APK, EXE, or whatever it is. Any help would be much appreciated and I'd be more than happy to provide answers to any questions you might have.