I have made a rom using new ervious visual bepe's kitchen.
i dumped two stock roms
1:- 1.66 stock
2:- 1.72 t-mobile stock
i simply replaced some folders from 1.66 stock into 1.72 stock which were operator package and operater pt.
and i converted a manila document tab from cab into EXT and copied into the dumped EXT. whose Path is like this ( C:/ dump/ext/leo/21869/Leo_external_packages)
and then i opened the kitchen and clicked on Button " REAL WM 6.5 AKU and changed its pagepool to 18mb and and changed the value of modules to 1000 in other options.
clicked on create rom and rom created succesfully without any error..
I flashed the rom into my hd2. it completed with no error and i performed several times hard reset also.
Now when i am trying to start the hd2 it stucks on welcome screen setup. no hardware buttons working.
what i have done wrong????
what mistake i made in between making the rom???
Kindly help..!!!!!!!!!!!!!!
no one have the answer for this problem?????????
c'mon friends.. help me out...
By 1.72 Tmobile ROM I assume a NON USA Tmobile ROM. If that's the case then it should work fine.. however if you cooked up a Tmobile US ROM, your phone will not boot unless you also flash a TMO US radio. Try a different radio and see if your ROM boots.
mon_money said:
I have made a rom using new ervious visual bepe's kitchen.
i dumped two stock roms
1:- 1.66 stock
2:- 1.72 t-mobile stock
i simply replaced some folders from 1.66 stock into 1.72 stock which were operator package and operater pt.
and i converted a manila document tab from cab into EXT and copied into the dumped EXT. whose Path is like this ( C:/ dump/ext/leo/21869/Leo_external_packages)
and then i opened the kitchen and clicked on Button " REAL WM 6.5 AKU and changed its pagepool to 18mb and and changed the value of modules to 1000 in other options.
clicked on create rom and rom created succesfully without any error..
I flashed the rom into my hd2. it completed with no error and i performed several times hard reset also.
Now when i am trying to start the hd2 it stucks on welcome screen setup. no hardware buttons working.
what i have done wrong????
what mistake i made in between making the rom???
Kindly help..!!!!!!!!!!!!!!
Click to expand...
Click to collapse
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.
HD2Owner said:
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.
Click to expand...
Click to collapse
Ah! Didn't think of that... He wasnt really clear what the "welcome" screen means, I assumed that would have been the initial splash screen.
But if the ROM boots past the 'red letters" then yeah, recmodding the notification manager DLLs will fix that
HD2Owner said:
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.
Click to expand...
Click to collapse
first of all thanks for your help..
HOw can i change the ntconfig.dll module into a file???????
rom which i am using is a branded rom from t mobile uk.. and have mix some content of generic 1.66 rom with this t mobile rom which i already mentioned above..
NRGZ28 said:
Ah! Didn't think of that... He wasnt really clear what the "welcome" screen means, I assumed that would have been the initial splash screen.
But if the ROM boots past the 'red letters" then yeah, recmodding the notification manager DLLs will fix that
Click to expand...
Click to collapse
thank you nrgz for your help..
kindly tell me how to do that??? how can i fix notification .dll modules??
Look for an exe called recmod.exe or reversemode.exe. For now. to see if this is your problem just exclude the notification manager form you rom
Related
Hi all,
I'm trying to install an ExtRom cab from Orange French rom which include the PVPlayer (necessary for live TV).
However, I get a message "install was unsuccessful .... not digitally signed with a trusted certificate"...
I've run Buzz ExtRom unlocker tool with success, but now I dunno what to do to install this cab.
Anyone can help me on this?
Thanks
mm, tried various time and no success
I think i'm missing how works ext rom...
Nobody can help me on this?
cedrick said:
Hi all,
I'm trying to install an ExtRom cab from Orange French rom which include the PVPlayer (necessary for live TV).
However, I get a message "install was unsuccessful .... not digitally signed with a trusted certificate"...
I've run Buzz ExtRom unlocker tool with success, but now I dunno what to do to install this cab.
Anyone can help me on this?
Thanks
Click to expand...
Click to collapse
Try to copy all that you need to have into the extended rom folder, inclusive of the config.txt file (make sure the parts that you want are referred to in this txt).
Do a hard reset and let your device customize automatically.
If it does not work, try with all original extended rom files.
Ok, so it can't be installed like any programs... you need to install them at the same time as the rom after a hard reset.
Damn, should have asked before then, now I have so many things installed...
I guess I'll try to find another way before trying this.
Thanks anyway for your reply!
cedrick said:
Ok, so it can't be installed like any programs... you need to install them at the same time as the rom after a hard reset.
Damn, should have asked before then, now I have so many things installed...
I guess I'll try to find another way before trying this.
Thanks anyway for your reply!
Click to expand...
Click to collapse
With some you can, with others you cannot. I think it has got something to do with loading the certificates first before you can install the signed versions of the cabs in the ex-rom.
You could try to install the certificates cab (is you can find which one that is) and then install the signed cab after it.
Let us know if and how it works!
Bon Success!
I should be able to find a cert cab somewhere... that's a good idea, I'll try this and let you know.
Thanks :wink:
Well I have installed two cert cabs :
Cert_SPCS.cab (from LokiWiz tools)
and PP_Certificate_OR_Jan23_Wizard.cab (from Orange Ext Rom)
But nothing changed before and after soft reset
I don't understand why adding this screen rotate icon on tray is signed...
The other cab I want to install is the PVplayer used for live TV.
Must be a simple way to install those cabs.
robincop deel 2 said:
cedrick said:
Hi all,
I'm trying to install an ExtRom cab from Orange French rom which include the PVPlayer (necessary for live TV).
However, I get a message "install was unsuccessful .... not digitally signed with a trusted certificate"...
I've run Buzz ExtRom unlocker tool with success, but now I dunno what to do to install this cab.
Anyone can help me on this?
Thanks
Click to expand...
Click to collapse
Try to copy all that you need to have into the extended rom folder, inclusive of the config.txt file (make sure the parts that you want are referred to in this txt).
Do a hard reset and let your device customize automatically.
If it does not work, try with all original extended rom files.
Click to expand...
Click to collapse
I should try this then, so I have to make the Ext rom folder appear with Buzz tools, then copy what I want in it and hard reset right?
Try this one.
PVP player does not work with my dopod rom.
Wow thanks, it worked this time and I have now that screen rotate thing in my tray bar... great !!!!
How did you do this, did you took it from another extrom? or did you signed it somehow?
anyway, about PVPlayer, I suceeded to install one (in attachement), but I need to pass through pocket IE and Orange web to click on a live tv link (then I think it open the pvplayer).
But it didn't worked with the one I installed, I guess something was missing to make the link between IE and PVP
That's why I wanted to try the cab in orange fr extrom (also in attachment).
Well anyway, thanks you very much for the above cab that worked, at last I have the screen rotate on Today screen !!
cedrick said:
How did you do this, did you took it from another extrom? or did you signed it somehow?
Click to expand...
Click to collapse
No, it comes standard unsigned with the NL Orange ex-rom.
Glad it worked out for you.
Hi, me again on this topic...
So I have modified the ext rom so that at the hard reset it could install that cab (which I have attached to my last post):
MP-Shortcut-MMS1-JAVA5XX-CV-VOICE-PVPLAYER-Orange-FR-060118.CAB
But it seems that it has not worked since I have no PVplayer installed on my prophet... maybe the signature is prohibing the install from ext rom too.
Well, is there anyway to remove the signature of this cab or install a signature on it so that it could be installed on my dopod rom ?
Is there a cert cab I could use to install the sig on the prophet and then install this cab?
sorry if my question seems stupid, quite new on that part.
Thanks
Hey, i got the I-mate JAMin, but there's no config.txt in the EXtRom. ANybody knows the language and the way it should be coded?
not sure about this, I've seen 2 ext rom so far and both had text files config.txt or something...
But that's a bit of topic :wink:
cedrick said:
Hi, me again on this topic...
So I have modified the ext rom so that at the hard reset it could install that cab (which I have attached to my last post):
MP-Shortcut-MMS1-JAVA5XX-CV-VOICE-PVPLAYER-Orange-FR-060118.CAB
But it seems that it has not worked since I have no PVplayer installed on my prophet... maybe the signature is prohibing the install from ext rom too.
Well, is there anyway to remove the signature of this cab or install a signature on it so that it could be installed on my dopod rom ?
Is there a cert cab I could use to install the sig on the prophet and then install this cab?
sorry if my question seems stupid, quite new on that part.
Thanks
Click to expand...
Click to collapse
I have the same problem with the Dutch Orange version when installing on the Dopod ROM. It does install, but I get a "non-imaged" icon in my programs folder that gives me a error message when I click it.
I have decided to forget about it all together.
Robin
I've unlocked my Jamin extended ROM and deleted "ALL" the files in it. Then I did a hrd reset and guess what..... all the files were restored.
This means that there is another ROM that the files are stored in even if you delete or cook the ext Rom, hard rest just igores it totally.
I guess i'll just wait for the possibility to go back to the orange rom from the dopod one :?
What a numpty!
I was trying to get HTC Home Weather working thru T-Mobile UK using v1.5HTCHomeproxy0409.cab (without success), so went into the registry using Total Commander to check the Proxy settings.
Unfortunately I got as far as \\\Registry\HKLM and was trying to double click the "Software" folder but instead it went into edit folder name mode and whilst distracted by the wife managed to change the folder name to "n"
Whatever I try, I can't rename it "Software". I've tried creating a new "Software" folder and copying the files across, but a few won't copy:
/Apps/Shared/ "\Windows\mscoree.dll" and
/Apps/Shared/ "\Windows\Intellipad.dll" and
plus some .NET Compact Framework files in /Microsoft/ folder - but I'm guessing these are something the prev user had and wont affect the normal functions / programmes I will use
so... is there any way I can put the files I moved from
\\\Registry\HKLM\Software back, do I need to etc ????
Would appreciate a bit of advice from someone less accident prone!!!!
Its a (recently bought off eBay) , ex T Mob (UK I think) unbranded with HTC home etc. Can't work out how to see what version of HTCHome was on, but guess I've written over it with the proxy.cab now - the icons have changes and have lost today screen battery indicator, but that's a problem for another day!
Not sure what the ROM is, if its an original or cooked (OS ID looks normal to me, WM5?), but ExtROM looks like its been hacked by its name - dferriera WM5SE
G4 Wizard
ipl 2.21.0001
spl 2.21.0lip
gsm (radio?) 02.71.11
os 2.26.10.2 WWE
Well, if it wont change back, you can always hard reset or reflash to a new ROM...and if you do the later, all of the prerequisites have been done for you, you have HardSPL allplied already, and the correct radio ROM version for most of the ROMs, so you can flash away!
Thanks Ashasaur.
As you've probably noted from my profile and foolish behaviour, I'm new to this, does anyone mind just explaining the above comments on the ROM flash for me please?
-all of the prerequisites (?) have been done for you
-you have HardSPL (?) applied already: Is this related to the Server Proxy I've been trying to patch to HTC home for the weather fix?
-and the correct radio ROM version for most of the ROMs: does that mean I need to be careful I pick a ROM to match my radio version somehow?
If I can't find a way to rename the registry file, I'll have to go for a hard reboot, ROM flashing will be my next project once I feel I've done enough reading to understand what I'm doing and what not to do!
Thanks.
In order:
1-Prerequisites)-You have got HardSPL flashed succesfully to your device which leads to;
2-HardSPL)-Since you have a G4 device, in order to flash a non-carrier ROM you have to have HardSPL applied to your device, and you can tell that yours has been done by your IPL and SPL. Your IPL or 2.21.0001 indicates that you have a G4 Wizard, and your SPL or 2.21.Olip means that you have HardSPL applied already, otherwise you would have had to do it in order to be able to flash any ROMs...which leads to;
3-Radio)-What I mean by correct radio for most of the ROMs is that 2.71.11 is regarded as one of the more stable radio ROMs out there, and together with version 2.19.X, they are the preferred versions, though any version will work with any ROM, some work better than others.
Hope that helps!
Yes it does, thanks - especially now it has prompted me to read the wiki on hardSPL.
So maybe flashing a new ROM is not too far away...
Does the ROM contain the Windows operating system, in which case can I upgrade to WM6 / 6.1 (version currently says WM5) on my device, will I find a selection with info on what's in them on the downloads pages? (can't get access right now for some reason)
Cheers
I just did this today with my Touch Pro, it's alarmingly easy to break your device like this.
I think I have it fixed ... after I made the mistaken renaming, the device had locked up (or grown very slow) so I soft reset it. That rebuilt a large portion of the Software folder. After that, I copied the remaining keys in the renamed folder to clipboard and overwrote whatever was in the new Software folder.
Phone seems to be back to normal, but I'll be on the lookout for anything that didn't quite work. If that's the case I may have to hard reset.
@burnsy, yes, most of the download pages contain what the ROMs have in them, but I would look at my review thread in the Wizard Mobile 6 section...its called ROM Features......such such such, its got a list and ratings of the ROMs that you may find interesting.
Nice one ashasaur, sounds like just what I want. Should keep me off he streets...
Dr G, seems you're getting on a bit better than I am - my device won't let me copy all the files into the new folder. Noticed that I can receive but no longer send email, even after deleting and reinstalling my account, but that could equally have been caused by the htc home proxy files I was playing with!
I feel a hard reset coming on...
I've decided to switch my ROMs back to 1.72 from 2.10 as I'm fed up with terrible phone call quality.
Ive swapped over from 1.72 to my 2.10 kitchen OEMDrivers, OEMDriversHigh and OEMMisc folders in OEM and carried over rgu entries from OEM Drivers. Also OEMXIPKernel has been copied from 1.72 to my 2.10 base.
This wors great but when I use 2.09.51 radio it works ok on first boot. But if I soft reset the phone hangs on the HTC boot screen and I need to hard reset.
Does anyone know what is stopping the 2.09 radio from working on soft reboot?
the_scotsman said:
I've decided to switch my ROMs back to 1.72 from 2.10 as I'm fed up with terrible phone call quality.
Ive swapped over from 1.72 to my 2.10 kitchen OEMDrivers, OEMDriversHigh and OEMMisc folders in OEM and carried over rgu entries from OEM Drivers. Also OEMXIPKernel has been copied from 1.72 to my 2.10 base.
This wors great but when I use 2.09.51 radio it works ok on first boot. But if I soft reset the phone hangs on the HTC boot screen and I need to hard reset.
Does anyone know what is stopping the 2.09 radio from working on soft reboot?
Click to expand...
Click to collapse
When I change a core base I always copy the os.nb.payload, romhdr.bin, xip.bin as well as the OEMXIPKerenl from the base I want to use. When copying the OEM folders copy the entire folders QEMDrivers, OEMDriversJigh, OEMMisc.
This has always worked for me. It may not all be necessary but it works.
I thing that if you use ROM OS 2.07... you must use Radio 2.07 0r 2.08 that avoid conflict between Radio&OS.
longnguyen30 said:
I thing that if you use ROM OS 2.07... you must use Radio 2.07 0r 2.08 that avoid conflict between Radio&OS.
Click to expand...
Click to collapse
Yes but he says he is using 1.72 which is not a TMOUS so any Radio with a 2.xx.51.xx.xx should work.
Maybe im stating the obvious, but did you try including the 2.09 rilphone.dll?
bobsbbq said:
When I change a core base I always copy the os.nb.payload, romhdr.bin, xip.bin as well as the OEMXIPKerenl from the base I want to use. When copying the OEM folders copy the entire folders QEMDrivers, OEMDriversJigh, OEMMisc.
This has always worked for me. It may not all be necessary but it works.
Click to expand...
Click to collapse
Hmmm...thanks for the reply. I never thought about those other 3 files in the XIP...I'll try copying them over too.
Thanks again, I'll post back with results.
Mikenif said:
Maybe im stating the obvious, but did you try including the 2.09 rilphone.dll?
Click to expand...
Click to collapse
I didn't think this would be necessary for the 2.09 radio to work.
Well that worked...must have been those other 3 XIP files I didn't copy over.
Thanks bob!
Hello everyone.
I was going to learn how to flash my hd2 to personalize boot and splash image.
I can't deny that i'm a bit confused.
I readed some guide here, like 'how to flash everything' and 'flashing your first leo 512mb' but there is not explained how to proceed to change boot and splash images.
Let's go then to know more about it.
First at all i got that i need to install HSPL2 on the device.
Doing this, we will able us to flash everything on the hd2.
But there are also other progs that i do not undestand if i can use instead the HSPL2, like leo_CustomRUU, or SSPL_RUU.
Maybe can be helpful if someone tell me/us ( noobs ) what is better and easy to use.
After this, there are two 'images' that we can personalize:
-the first is when we turn on the device, with the htc logo and the hand writing word;
-the second, the Windows word on the red desktop color.
The first is the boot image, the second the splash screen.
Is it right?
Okay, if it's correct, i suppose that we need to 'operate' on two different kind of 'image file'.
I downloaded a .zip file that contains various kind of images ( static ) with .nbh extension.
That are splash images, so it will change only the splash image.
I don't know if i can use it directly without rename it, if i must put that file in a specific position on the device or only in the sd root ( formatted ), and then launch the progs ( what kind? ).
Yes...need help for this.
Thanks
p.s sorry for my poor english
hspl2 unlocks the phone for flashing.
sspl is a one shot alternative to hspl, you don't need it.
customruu is a slightly altered version of the rom loader that comes with official roms. it is altered to allow flashing cooked roms.
you flash boot image just like roms, and it is actuallya small rom.(no hard reset needed, doesn't affect your rom at all.)
there are three parts to the boot screens, as you correctly noted, only the first part is flashed, the second and third are changed within your setup by cabs or replacing image files.
start here
forum.xda-developers.com/showthread.php?t=625911
samsamuel said:
hspl2 unlocks the phone for flashing.
Click to expand...
Click to collapse
ok.
then first at all i need to install it on the device for flashing .nbh images.
right?
sspl is a one shot alternative to hspl, you don't need it.
customruu is a slightly altered version of the rom loader that comes with official roms. it is altered to allow flashing cooked roms.
Click to expand...
Click to collapse
i see.
well i downloaded HD2 splash screen V1.zip ( inside the link that you posted here ) and inside it there is already Custom_RUU.
I think then that i must use it to flash the custom splash on the device.
Right?
and...i must put the .nbh file not inside the sd card, but in the device root.
right?
you flash boot image just like roms, and it is actuallya small rom.(no hard reset needed, doesn't affect your rom at all.)
there are three parts to the boot screens, as you correctly noted, only the first part is flashed, the second and third are changed within your setup by cabs or replacing image files.
Click to expand...
Click to collapse
well i thought was just two, as i wrote in my first post.
the white with handwriting and the Windows on red background color.
start here
forum.xda-developers.com/showthread.php?t=625911
Click to expand...
Click to collapse
thanks
i successfully installed HSPL ( not hspl2 ) on my device.
Now i'm trying to flash the device with an .nbh image, for the splash screen.
My doubt is:
1- where to put the .nbh file
2- if i need to copy custom_ruu.exe also inside the device where is located the .nbh file and then launch another copy of it from my pc.
I did it but the custom_ruu.exe tell me to upgrade the rom from 1.66 to 1.0...
a bit strange i think....or not?
thanks
to flash roms and splashscreens - put the nbh into a folder with customruu (customruu usually comes with the rom, if not use one from another download, all customruu.exe's are the same)
just those two files in folder, run customruu as administrator, done.
samsamuel said:
to flash roms and splashscreens - put the nbh into a folder with customruu (customruu usually comes with the rom, if not use one from another download, all customruu.exe's are the same)
just those two files in folder, run customruu as administrator, done.
Click to expand...
Click to collapse
done
i was a little afraid when the app told me to 'update' the rom to 1.0 hehe.
ok then, it's flashed
well, it's also possible to modify the Windows on red background image in some way?
i just installed an .nbh image that allow me to modify the standard htc logo, then a .cab with a post simulation ( like a pc post; unfortunately if i do an hard reset i must reinstall it.... ), but i didn't found nothing for the Windows on the red background colour.
Thanks a lot again for your support
hehe, ignore what it says in the update version bit, its usually blank or wrong.
about the other two images, and re: ' have to reinstal it when hard reset', , , well yea, cos theyre adjustments to the loaded rom, the first part is unconnected, youd get that even if there were no rom, after task29 for instance.
samsamuel said:
hehe, ignore what it says in the update version bit, its usually blank or wrong.
about the other two images, and re: ' have to reinstal it when hard reset', , , well yea, cos theyre adjustments to the loaded rom, the first part is unconnected, youd get that even if there were no rom, after task29 for instance.
Click to expand...
Click to collapse
got it
do you know if it's possible to change also the Windows word on the red background?
it's the last image that appear before the sense interface start to load.
i didn't find thread that talk about the possibility to change it or not.
thanks
sorry no idea, i've never tweaked that. i flash too often for it to be an issue.
samsamuel said:
sorry no idea, i've never tweaked that. i flash too often for it to be an issue.
Click to expand...
Click to collapse
ok then.
i'll bump this thread with the hope that someone can help us.
The last question is:
it's possible to change with a flashing ( maybe permanent modify then ) the Windows word on red background?
Thanks to you sam for your help, and to those that will answer to this last question
The windows splash screen is a file called welcomehead.png in the windows directory. Just replace this with an image of your choice and it'll be changed.
im pretty sure i can answer that question as no, you cant modify it so that it survives a hard reset without cooking, and then flashing the cooked results, you cant modify the rom. you would need to get the rom in a kitchen, repolace the images, cook the rom and flash it.
In reality, of course, all you need do is keep your replacement images on your sd card, then copy them back after the hard reset.,
in fact i tryed to delete the welcomhead.png, but nothing to do, even if i change the permission with total commander...
i think that there is no easy way to replace it ( aside to cook a ROM with a different image and then install the modified ROM ).
i think ill give up about this...ill keep the standard ( and not really good looking ) Windows word....
thanks to you all
rather than delete the original which you can't cos it's in the rom, just copy replacement over it, that should work.
O2 splash screen
bump... related questions:
1. It's been a while, when I had the TP1, I used Schaps Advanced Config v3.3 to change the 2nd and 3rd items, does v3.3 still work for the HD2 ?
2. Does anyone have the O2 Splash screen GIF with animated rising bubbles? I had it in a samsung flip phone, searched but could not find a WVGA one. Searched Youtube came up blank. something like this on the O2 XDA
3. These are the 2 threads I used on the TP1, I don't think the HD2 has an equivalent thread:
Touch Pro Splash Screen Repository and
Touch Pro Steps to change your 1st Splash screen
I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
millski said:
I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
Click to expand...
Click to collapse
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
TMartin03 said:
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
Click to expand...
Click to collapse
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
millski said:
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
Click to expand...
Click to collapse
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
TMartin03 said:
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
Click to expand...
Click to collapse
Tried that, still wouldn't work. If I cook without RunCC the ROM will boot without error, but then the initial customisation doesn't run i.e. no SIM or operator settings are made.
I don't think I'm going to get to the bottom of this so I've started building a new kitchen. Does anyone know which packs from Leo 2.14 will make my ROM TMOUS HD2 compatible? I can't remember...