Has their been any definitive development on how to inject our own splash screens into the Universal's ROM either by 1. decrypting the NBF file, injecting a splash screen, re-encrypting the NBA file to NBF, then flashing, or 2. dumping the ROM to an SD card, dumping the SD card into a file, injecting the splash screen, etc., or 3. installing a file in the Windows folder (similar to previous HTC devices, i.e. Splash1.nb)?
The Qtek ROM seems to be the cleanest and being able to remove that last touch of branding would make it a true universal Universal.
Anyone?
I know for certain it's not encoded in the Extended Rom NBF as it is in Blue Angel, Magician, Alpine... Cause I have a decoder/encoder for NBF for Universal machines.
Must be in a cab file within the rom somewhere...
Bal
Can you provide the decryption/encryption utility?
I'm sure I can find it in the nk_.nbf file.
Ahhhh, could be there - but it's pretty unusual (from my limited experience).
I've only ever encountered it in the Extended ROM image ....
I'll post the utility in a couple of days - I'd like to finish the help file first, so it'll save me cross-posting it everywhere.
If you do need it quickly, I'll be happy to pm it to you - and you can help me test it :lol:
Bal
Hey,
I cooked a Trinity ROM, made a bunch of modifications to maximize the internal storage, built it, flashed, booted okay, installed the extrom and soft-reset auto., but after that it.. well, it gets stuck on a hard-reset loop
Does anyone know what can be causing this?
I edited initflashfiles.dar using winxp notepad, saves, and removed 1st 2 bytes using winhex.
As for the registry files, I used rgucomp and saved the reg in UCS-2 Little Endian, which I believe to be equivalent to UTF-16(Big Endian made rgucomp spew out an error), and I made changes to the today softbuttons which are visible while the extrom is installing, so I think the problem can only be in the initflashfiles.
Also, I noticed the phone icon indicates no network while installing the extrom, and it used to, it may help to pinpoint the cause of the hard-reset loop.
I've been looking all over about information concerning porting a ROM over to the Herald phone, but I can't seem to find the information that I need. I can cook ROMs just fine, but this still escapes me. I've picked up a few things here and there but nothing conclusive that I can put together. I need some guidance on the department.
On a side note, does anyone know how to bypass the 51.2mb size requirement that the Herald RUU imposes? It seems that any OS down to this size with resize the storage accordingly with the extra space, but if I try to make a smaller ROM, it'll give me a corrupted image error. I can pad the os.nb with nothing using a hex editor before I convert it to a NBH file, but the file size seems to be what actually sets the storage size, not the actual partition table set on the ROM.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
Any chance that Task 29 working on Trinity or something similar ?
( see http://forum.xda-developers.com/showthread.php?t=653604 )
If I understand Task29 correctly, I've done exactly that. My understanding is that Task29 overwrites the ROM space, in effect, erasing any previous information that resided there.
What I've done is create a ROM that is completely blank! It does not include any OEM, Drivers, SYS, EXT, or any other part of Windows Mobile. This file I've called my Quick Format as it only overwrites the first portion of the ROM Space, much like a Quick Format does to a drive.
The Second Task29 I built is the same ROM except that I've added 3 very large bmp files that fill the ROM Space completely. This file I've called my Full Format as it replaces the whole ROM Space with NOTHING! (Well, bmp files that are nothing).
If I have totally misunderstood the Task29 concept, I apologize. I've used these a couple times and they SEEM to work. The next ROM Flashed seems to boot quicker and smoother.
Anyone have any feedback that might help?
Task29 Quick Format for Trinity by SuperSport.exe 1.66MB
Task29 Full Format for Trinity by SuperSport.exe 54.1MB
PS: I've made these into my AutoFlash file format for ease of use. Just place phone into Bootloader mode and run the file, then follow directions.
After flashing these, you will need to place your phone back into Bootloader to flash another ROM as there will be Nothing to boot to at this point.
Also, these do NOT touch the Radio or HardSPL. Those will remain as you had them previously.
task 29
i recently got back my hd2, which was sent to america to be fixed (digitizer change). But when I got it back the volume button wasnt working and i was here fooling with it and did a task 29, now am stuck at the stick together screen. any help?????
law48 said:
i recently got back my hd2, which was sent to america to be fixed (digitizer change). But when I got it back the volume button wasnt working and i was here fooling with it and did a task 29, now am stuck at the stick together screen. any help?????
Click to expand...
Click to collapse
Did you use Task29 that was made for the HD2, or the one here? The one here is only for the Trinity P3600.
Either way, you now need to flash a ROM to your phone. You can use the stock one, or select a custom one from these forums. ONLY use one made for your specific phone though. And remember, there are TWO versions of the HD2. Be sure you use the right ROM, or you can brick your phone for good.