Related
It seems like no matter how many ROMs i test out either one or the other will not work correctly or completely.
I'm not the most proficient when it comes to dumping or decompiling the work you guys do so i hope someone can make a ROM that both components are working.
The last stable BBC friendly ROM i used was VP3G 3.60 version but with that ROM i could never get the PTT to work.
I have compiled a few different configurations with the Pandora Kitchen and have been happy that the PTT is working but have been unable to get the BBC to work with those builds.
Anyone out there who can offer any help???
no one can help out at all??
Try this one...
HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108.exe
http://rapidshare.com/files/46467733....00.10_108.exe
tried that ROM and could get the BBC working but not the PTT function. I should be more specifis i suppose...
I need an AT&T based rom that can handle both tasks.
If i was more secure in my understanding of HEX editing i'd attempt it myself base off of the ROMs i've collected.
Lots of you have viewed the page but i wonder if anyone has any ideas to help???
I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571
Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?
Stingray66 said:
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
Click to expand...
Click to collapse
Hmm, at first glance you actually seem to be right which is good news for many among us
I had never installed that CAB before, and I learned to live with lost passwords etc. (never got around to trying the workaround), but that's all about to change with this easy fixSome more tests have revealed that in my case the "first glance" must have been sheer luck
I mainly checked whether wifi passwords were required again, and tried uninstalling/re-installing/rebooting/resetting/... but all I can conclude is that only sometimes the settings are preserved and still most of the times the settings are lost - this regardless of the aforementioned CAB.
Well, I haven’t lost hope yet, though. Maybe someone will figure it out, but the sooner the better
MANY THANKS,
It's seems works fine...
Many thanks again...
Stingray66 said:
I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571
Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?
Click to expand...
Click to collapse
This would be VERY cool if it works! I hope that's all there is to it.
Thanks again Stingray66! PS: Do you drive a Corvette?
StefanoRuleZZ said:
MANY THANKS,
It's seems works fine...
Many thanks again...
Click to expand...
Click to collapse
Work here again too on the ROM FInixNOver 3.1
SuperSport said:
Thanks again Stingray66! PS: Do you drive a Corvette?
Click to expand...
Click to collapse
I did a couple of times, but I'm not in the position right now to buy one. Priority is my wife, kids and moving to another house right now, but a Corvette from 1966 is a great car ..... beautiful!
I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.
I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.
Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
But where???
Translated by Google, sorry!
sergitec said:
Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
But where???
Translated by Google, sorry!
Click to expand...
Click to collapse
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.
adewidt said:
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.
Click to expand...
Click to collapse
well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip
themaskfly said:
well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip
Click to expand...
Click to collapse
I did not experience any of the problems you describe.
adewidt said:
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.
Click to expand...
Click to collapse
So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP
firiel said:
So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP
Click to expand...
Click to collapse
As I already said, I managed to fix A2DP using the old bootkernel (nk.exe part of XIP).
This works for wm6.1 and wm6.0.
There is no reason good reason to use the new kernel in stead of the old kernel.
As i say 4 months before here:
http://forum.xda-developers.com/showthread.php?t=342269
the old xip section (nk.exe) is working better with trinity 400mhz.
All my rom in this 4 months is builded with old nk.exe and i tell to cookers to use them to.
I dont see any reason to use the new (dopod) nk.exe with that very iportant bug.
No problems and nothing, nk.exe is the kernel from the device no nead to update that in the future.
The only problem it was in a2dp sound but after the fix from adewidt (Thanks again) the sound it is perfect!
Thank's
adewidt said:
I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.
I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.
Click to expand...
Click to collapse
Well after some resets, it does loose it's settings.
@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))
Stingray66 said:
Well after some resets, it does loose it's settings.
@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))
Click to expand...
Click to collapse
Yes it change your device ID.
Hello All,
I ram the Hermes Shadow 2.1 ROM for almost 6 months and nothing was stabler than that, i finally upgraded (to AlmostNak3d Manilla v11)to get the keyboard fix during call on all the new ROMs and none of the ROMs have been any good to my device. The device after a day or so, just freezes and I'm unable to restart it, it just gets stuck at the boot screen, and sometimes appears as if it were Hard-Reset.
I've tried almost all of the new ROMs here and all of them have crashed on me. I'm going back to Shadow 2.1TE from Cloudyfa, and I'm hoping this gets fixed.
Is there a patch that I can use to get the keyboard during call fix on the Shadow 2.1TE wm6.1 rom? or is there a way to make my device stable on the new ROMs again? I dont know anything about cooking ROMs, so any help will be appreciated.
Thanks!
EddHead said:
Hello All,
I ram the Hermes Shadow 2.1 ROM for almost 6 months and nothing was stabler than that, i finally upgraded (to AlmostNak3d Manilla v11)to get the keyboard fix during call on all the new ROMs and none of the ROMs have been any good to my device. The device after a day or so, just freezes and I'm unable to restart it, it just gets stuck at the boot screen, and sometimes appears as if it were Hard-Reset.
I've tried almost all of the new ROMs here and all of them have crashed on me. I'm going back to Shadow 2.1TE from Cloudyfa, and I'm hoping this gets fixed.
Is there a patch that I can use to get the keyboard during call fix on the Shadow 2.1TE wm6.1 rom? or is there a way to make my device stable on the new ROMs again? I dont know anything about cooking ROMs, so any help will be appreciated.
Thanks!
Click to expand...
Click to collapse
flash a oem rom and then again the custom rom you want
this should solve your problem
Thanks, Could you give me a link to any of the 6.1 OEM ROMs? also is there a hotfix for the Keyboard bug during calls?
EddHead said:
Thanks, Could you give me a link to any of the 6.1 OEM ROMs? also is there a hotfix for the Keyboard bug during calls?
Click to expand...
Click to collapse
look at this post from Dr Puttingham
Thanks, the Shadow Roms working fine now. I did install HardSPL long ago, so shouldnt be a problem. Whats the best Radio ROM for Hermes in India? any guidance to the keyboard during call fix will be of great help. SHould I ry the original OEM ROM for WM5 which came with my HERMES?
EddHead said:
Thanks, the Shadow Roms working fine now. I did install HardSPL long ago, so shouldnt be a problem. Whats the best Radio ROM for Hermes in India? any guidance to the keyboard during call fix will be of great help. SHould I ry the original OEM ROM for WM5 which came with my HERMES?
Click to expand...
Click to collapse
The reason for flashing the shipped rom is to clear up any issues that the big storage roms can create, like hard resets. They are writing into areas of the flash memory that can get "confused" going from one big storage rom to another. So the stock rom will "freshen" it up.
As for the keyboard issue, I'm not sure.
Thanks, The shadow ROM seems to be working fine for me, the keyboard fix was done by Dillsnik & Fun_Key, and is incorporated into the later ROMs which are all Hard Resetting my device. I wanted to know if there is anyway to Hotfix this into the older ROM that i'm running. also the battery fix the same way.
http://forum.xda-developers.com/showthread.php?t=538874
has anyone gotten this to work with their Uni? need something like this. tried WMWifiRouter but its not free.
Tomals V10 n V12 have it,
+ it works
Hey thanks alot. I cant run those roms as my 64MB Uni cant handle them but they are nice. I was hoping to get it working on one of these other ones.
I have been playing with Thing's and Tomal's latest kitchens trying to make the rom for me. Need more info on cooking though.
Simon_WM, would you be able to provide a cab file for the software to enable the UNI to act as a Wifi Spot please? Thanks.
er....,
i think i've got the package...
ill hav a look for it and upload later
boxchevy said:
Hey thanks alot. I cant run those roms as my 64MB Uni cant handle them but they are nice. I was hoping to get it working on one of these other ones.
I have been playing with Thing's and Tomal's latest kitchens trying to make the rom for me. Need more info on cooking though.
Click to expand...
Click to collapse
I have installed Toma V10 and works all perfect, of course not as fast as a 6.1 but it´s very stable
I also have 64Mb Uni
orb3000 said:
I have installed Toma V10 and works all perfect, of course not as fast as a 6.1 but it´s very stable
I also have 64Mb Uni
Click to expand...
Click to collapse
I have just installed Tomal's V10. So far its working for me. Previously I was experiencing random lockups say if I was using my stereo headphones and playing a game at same time or sending texts. After some changes (ex. disabling the windows default today plugin) I now have 18.95MB free program and 40.20MB storage. The built-in software works great for making Uni a wifi spot. Did Tomal release a kitchen for this rom? Or is it built on his V2.0 kitchen? Either way I seem to have been missing out on a great rom.
Now if I can somehow combine Cotulla's doc format, Thing's optimizations especially TCPMP and Opera being the default programs, and Tomal's great features I may never flash again.
Also for those not using Tomal's V10 but still need this feature check the 1st post here: http://forum.xda-developers.com/showthread.php?t=588099
It worked for me and says its the full version. Im not positive of it but it did work whereas the other cab I was using says trial expired. Thanks all for the help.
Simon_WM, were you able to compile it into a cab file?
@boxchevy
Yeah Tomal release a kitchen:
http://forum.xda-developers.com/showthread.php?t=476544 (thread)
http://www.mediafire.com/?wzymtfmzjvm (download)
@Final5k
Although i've been around a longtime, i cant create a CAB, although i can uplaod the files direct from tomal's kitchen if you want?
I've added it in a ZIP format, you will need to then drop it into either:
OEM packages
or
EXT Packages
if it dont work either: PM me or Tomal and we try to sort it out!
thanks simon. im looking at trying to combine the kitchens if possible for a best fit for me. like i cant play warcraft2 with tomals V10. i tried adding the files for wireless modem to things rom but it didnt work. didnt add the comm manager option. ill keep trying. thanks though.
kwl,
you could try pming tomal for more help,
althouth depending on the kitchen:
Luca16thebig - Visual Kitchen
Thingonaspring - V2.31
Tomal's - V2 Uni kitchen
Hey thanks Simon_WM! I'll see if it works on my rom!
if it does... you could upload it for every1 else to use=]
SO recently i have tried making many roms Each one seems to not work on my device could someone please test this and let me know if it works or if its just my device. Update to HardSPLv7 and flash a stock rom before flashing this. if any thing happens to your device i am not responsible. It is build 23138 has basic things, no titanium, It has manilla version 2.0.2016 (I like it better than titanium but huge ram hog)
Made with +QUEPPC's ervius Kitchen and thanks to his great tutorial.
EDIT: I fixed the problem here is a link if someone still wants to use the rom
http://www.mediafire.com/?svmi62tmjb69dq2
dude new 2016 manilla is build for wvga devices not qvga.... not gonna work.
actually the manilla it is the latest manilla 2d from the mega rom and i got the rom to work it was just that one of the ext file was causing the problem i have reuploaded a new version as a test