I want to remove the file Windows\HH_PEOPLE_16x16_Device.png
It's in ROM (B&B 4.3), so I guess it can't be removed. But a lot of people think it can be done, so I assume there must be some way. Common suggestions I've read are:
- Disable the HTC Home plugin: I already did that, in the "Today" settings. And performed a soft reset after that, for good measure. No luck.
- Use Total Commander: already tried that. No luck. The file attributes show "Read only" and "In ROM". If I try to delete or rename the file, nothing happens. If I try to unset the "Read only" attribute, nothing happens, it stays set. The "In ROM" attribute is ghosted and can't be removed, which makes sense.
- Use Resco Explorer: same as with Total Commander.
In a nutshell, nothing I've tried will work, and I'm inclined to think it can't be done, but for the insistent reports that "if you use Total Commander it works".
What am I doing wrong??
Try to run USPL first and then all the other methods...
I did that already, I wouldn't have been able to flash a cooked ROM otherwise. My SPL version after running USPL is 1.11.
ineluki said:
I did that already, I wouldn't have been able to flash a cooked ROM otherwise. My SPL version after running USPL is 1.11.
Click to expand...
Click to collapse
run USPL after you flashed your ROM (whichever - in your case B&B4.3) again.
A strange solution:
Make a cab file that includes HH_PEOPLE_16x16_Device.png install it and after reboot remove it from add/remove programs.
ineluki said:
I want to remove the file Windows\HH_PEOPLE_16x16_Device.png
It's in ROM (B&B 4.3), so I guess it can't be removed. But a lot of people think it can be done, so I assume there must be some way. Common suggestions I've read are:
- Disable the HTC Home plugin: I already did that, in the "Today" settings. And performed a soft reset after that, for good measure. No luck.
- Use Total Commander: already tried that. No luck. The file attributes show "Read only" and "In ROM". If I try to delete or rename the file, nothing happens. If I try to unset the "Read only" attribute, nothing happens, it stays set. The "In ROM" attribute is ghosted and can't be removed, which makes sense.
- Use Resco Explorer: same as with Total Commander.
In a nutshell, nothing I've tried will work, and I'm inclined to think it can't be done, but for the insistent reports that "if you use Total Commander it works".
What am I doing wrong??
Click to expand...
Click to collapse
Dudes,
If a file is on ROM (= Read Only Memory) it definitely means that the file CANNOT BE REMOVED! Don't try it, it's useless. Flashing a new rom can only remove the files which are BURNT into the rom.
IMO there is only one workabout: to MASK that file. E.g. if it's an image, you can produce another one, with the same filename, and copy it over the original one - certainly with Total Commander or Resco Explorer. So it will "overwrite" the file on rom, but just virtually, when you delete your new file, the original one appears again. But you can use this method for instance to create an empty and 100% transparent image with the same pixel size, copy it over, and your unwanted image will hopefully disappear...
Good luck!
Thanks everyone. About flashing USPL again, well I tried it just in case and it didn't work either.
I already knew that ROM files can't be removed, but then a lot of people said they could, so I guessed: perhaps I'm wrong and Total Commander does a sort of flash-write to erase them.
Perhaps all the people who have been able to remove this file had it in RAM and not in ROM. The ROM version I'm using bundles everything about "HTC Home" in ROM, but perhaps other versions don't.
@ctibor: now that's a really good idea. I'm going to try it now. Thanks!
Yup, it worked I didn't even need Total Commander. As long as the HTC Home plugin is disabled, you can use Activesync to copy the new icon on top of the old one. As you said, the older file is not actually replaced, but masked.
In case anyone else has the same problem, I'm attaching a PNG file with a 16x16 transparent background. Just rename it as the file you want to replace: (HH_PEOPLE_16x16_device.png, HH_PEOPLE_16x16_work.png or HH_PEOPLE_16x16_home.png) and follow the above procedure.
If you can't see the image... well that's the point, isn't it? that image is meant not to be seen you can however save it using the right button menu.
I'm glad to be able to help you )
cheers,
thanks for the pictures, you really helped me
Related
I have made s script which installs all files in my Install-Directory of my SD-Card. The script is based on nscriptm and invoked automatically after HardReset.
It installs silently all CAB-Files, Reg-Settings in REG-Files, a TSK-File.
It copys all wanted files automatically from the SD-Card to the PocketPC (e.g. for the Windows-Folder, etc).
It deletes wanted files from the Pocketpc.
It copies Shortcuts.
So a complete new Install lasts only a few minutes. Great for testing.
Now I am searching an unzip/unrar/uncompress/... - Tool which can be invoked from the command-line with additional parameters to uncompress all Install-Files on the SD-Card.
Anyone knows ?
Sounds like an excellent idea. Can you share your script? Sorry I do not know of a zip utility. All installs on cab files are already compressed though.
Doed Pocket WinRar will do the job?
I also would love to try it...
Very good idea
This sounds like a great idea.
No, Winrar is only with GUI. No Commandline. Have searched for days.
CAB-Files are not Compressed I think. Only the EXE-Files containig the CAB-Files for Install on PC are compressed.
Please HELP !
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
I have also been searching the net for a compresion tool that runs from the command line, but with no luck.
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
Click to expand...
Click to collapse
axbl,
would love a copy of your script. For everyone's benefit, can you attach it to this thread?
thanks in advance.
axbl said:
No, Winrar is only with GUI. No Commandline. Have searched for days.
CAB-Files are not Compressed I think. Only the EXE-Files containig the CAB-Files for Install on PC are compressed.
Please HELP !
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
Click to expand...
Click to collapse
Hi axbl, would be happy to test your script, email is [email protected]
Hi axbl,
Could you please also post me a copy of your ROM / Script ?
Many Thanks,
Justin
[email protected]
Has anyone heard from axbl? While waiting in vain, I decided to give this a shot and see how far I go along scripting my installs. I find the nscriptm tool to be very capable but still I am stuck in a few areas which axbl seems to have excelled based on the initial post.
How can one trigger a cab file install and make it a silent install? I am using the Shellwait("") command to trigger the cab file installs one after the other but those that require input are causing an issue.
Next I have tried automating the response to those user input prompts (i.e YES / NO etc) but I am having trouble catching the window handle of the prompts and then using the Sendkey command.
Thanks in advance for all the help. Regards
I use the software call Autoconfig.exe which is included in O2 Asia ROM.
The Autoconfig.exe will read Autoconfig.txt file and execute according to the command line in the file.
The command line is exactly the same as Config.txt
[.......] <---- Section to be selected
CPY1: <---- copy from
CPY2: <---- copy to
EXEC: <---- Execute Program
CAB: <---- Install .cab file
RST: Reset <---- Soft Reset
I can do what I need about 80%. I say 80% is because after this process ended. I still need to put in name/pasword to all of those s/w or else it will still be trial version.
no more?
so any update in this topic??
....pls
little_frog said:
I use the software call Autoconfig.exe which is included in O2 Asia ROM.
The Autoconfig.exe will read Autoconfig.txt file and execute according to the command line in the file.
The command line is exactly the same as Config.txt
[.......] <---- Section to be selected
CPY1: <---- copy from
CPY2: <---- copy to
EXEC: <---- Execute Program
CAB: <---- Install .cab file
RST: Reset <---- Soft Reset
I can do what I need about 80%. I say 80% is because after this process ended. I still need to put in name/pasword to all of those s/w or else it will still be trial version.
Click to expand...
Click to collapse
hi, if you create an xml file or a cab (need winCE cab manager) you can add all the registry details you need to register your program...but you have to search your registry to find those details.
Yes, I can do it while ago.
The post I did was a year ago. At that time, I didn't know how to do it.
Thanks anyway.
axbl said:
I have made s script which installs all files in my Install-Directory of my SD-Card. The script is based on nscriptm and invoked automatically after HardReset.
It installs silently all CAB-Files, Reg-Settings in REG-Files, a TSK-File.
It copys all wanted files automatically from the SD-Card to the PocketPC (e.g. for the Windows-Folder, etc).
It deletes wanted files from the Pocketpc.
It copies Shortcuts.
So a complete new Install lasts only a few minutes. Great for testing.
Now I am searching an unzip/unrar/uncompress/... - Tool which can be invoked from the command-line with additional parameters to uncompress all Install-Files on the SD-Card.
Anyone knows ?
Click to expand...
Click to collapse
Pls can u share the script with us it would be a great help for all of us.
thx in advance
jeet
You don't have to ask that guy. He'd never come back.
It's not that difficult to do. You need to know how to build CAB file by using WinCE CAB Manager. Then, put those REG, TSK, EXE, File, etc. into your built CAB file. By using (Autorun and Config.txt) or (Autoconfig.exe and Autoconfig.txt) or (Autorun and ExtROM via \2577 folder), You can install any CAB files into the system after Hard Reset.
ok
could you pls post the files to do it?
(Autorun and Config.txt) or (Autoconfig.exe and Autoconfig.txt)
if possible?
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
2nd STEP: You need to get a hold of the ROM file so you can extract the necessary files from it. This is provided by the phone manufacturer.
****To extract the file, someone recomended WinRAR. If you don't have it, follow this: Go to
My Computer
Your Drive (mine is Drive C: )
Show the contents of this drive
Documents and Settings
Choose your folder name
Local Settings
Look for the "Temp" Folder
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
3rd STEP: You need to extract the following files namely and add the MaUpgradeUt_NoID.exe File. These 10 files are found in one of the folders within the "TEMP" folder after running the file you got from Step 2.
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
*****You need these 11 files if you want to upgrade the ENTIRE ROM.
*****If you only want to upgrade to the RADIO VERSION then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf". So there are 9 files on it.
NOTE: The "TEMP" folder has many folders within it. It is your job to look which folder was created upon running the .exe file from step 2. You need to copy those 10 files and paste them on a new folder.
4th STEP: After gathering the necessary files and choosing which part you want to upgrade and keep, you need to put your device to boot loader mode by pressing 3 buttons simultaneously:
Power Button
Backlight Button
Reset Pin
5th STEP: Plug your Universal via USB. Wait for your computer to recognize a newly plugged device.
6th STEP: Now you are ready to upgrade. Double click the MaUpgradeUt_NoID.exe File to run it and follow the on screen instructions.
Hope this helps. Good luck.
Hi...
Nice guide indeed..but u forgot one important step....that is hard resetting after the complete upgrade... :lol:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Thanks for the input guys. I also remember, I did not perform a hard reset myself, just a soft reset at the end. But I choose not to include that on the steps as the computer will show a window as to what you're supposed to do or press during the upgrade anyway.
great post!
AG
radio version? Windows Mobile version? and EXT Rom?
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Re: radio version? Windows Mobile version? and EXT Rom?
tmglobe2004 said:
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Click to expand...
Click to collapse
I have tried all ROMs that came out on this site. The ones I recommend are only 2:
1st: QTEK's latest ROM
2nd: JWright's Modified ROM
From my post above these 3 files determine which part you want to upgrade:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
If you look at my signature below. I am using TMobile's Radio while using JWright's Modified ROM. It all depends on you which combination you feel is more stable. On my Universal, I never had any troble no matter what ROM I used, but these 2 I listed above surpasses any ROM released by other manufacturers on my opinion.
Pantaloonie said:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Click to expand...
Click to collapse
Yeah I heard the same thing, I did a soft reset after installation and it worked fine.
error 120 country id
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
artcsmota said:
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
Click to expand...
Click to collapse
What 3 files? If you are referring to the .nbf files, none of them are responsible. Follow the instructions above and keep repeating them, sometimes it takes more than one try for the Error 120 to disappear according to some who experienced it.
cktlcmd said:
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
Click to expand...
Click to collapse
A great post, Upgraded my O2 Exec using your procedure, worked a treat, Thank you!
Wooky
cktlcmd said:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
Click to expand...
Click to collapse
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
resetting
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
xiasma said:
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
Click to expand...
Click to collapse
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
mavrik64 said:
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
Click to expand...
Click to collapse
YES, if you perform a hard reset. The new upgraded ROM will be the default ROM restored on your device.
cktlcmd said:
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
Click to expand...
Click to collapse
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
I've now ran the T-mobile ext ROM upgrade, hard reset.
When the \extrom autoruns, should I just select T Mobile UK? Or cancel?
xiasma said:
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
Click to expand...
Click to collapse
I think you are doing what I was when it finaly clicked.
By the way, thanks to cktlcmd for the breakdown of the process.
The bit you will need to understand is that when you run the .exe, it unpacks the files into a folder in the Temp directory cktlcmd mentions. All i did then was to search for one of the files listed and i found the folder that way. I then copied the files into a more convinient folder and added the MAUpgrade as per the instructions. Once i did this, running the MAUpgrade does as described.
I know this may seem a bit long winded, but I got there in the end. Also, by saving the contents of the folder elsesware means I can play with it later as also discribed by cktlcmd.
The JASJAR rom is sofar great.
Thanks for all your hard work cktlcmd
regards
Mav
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
fuhayer said:
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
Click to expand...
Click to collapse
Have you tried my instructions yet? Try downloading the files again. Sometimes they get corrupted.
it is fixed by flashing with original t-mobile 1.30.232 rom.
but when i flash ivanb14 it is again freezing at 19% of stage3.
what can be the problem ? i have downloaded the ivanb14 rom 3 times and i receive the same error message.
I've seen a lot of people asking how folks have changed the Windows logo to the HTC one and so on. I am one of those people!
There's a thread over in the Diamond Forum here, http://forum.xda-developers.com/showthread.php?t=437307, that discusses altering the taskbar icons.
I've had a read of that but it doesn't appear to discuss the start button. I've currently got a cab installed that gave me coloured icons on the taskbar but also the 3d MS Office style start button. I like the icons but not that start button.
Is there anyway someone could provide an idiot/noob style guide for altering that icon. I'd love to have the Vista start button on my HD (attached image) but have no idea how to go about it aside from I think it has something to with .dll files.
Can anyone explain this? Anyone? I know there would be a lot of people grateful for it! I've Googled and used the search but just cannot seem to find anything!
I've attached a mock-up of my ideal; I've got the coloured icons, just the start button to go!
I think....
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
I believe you can do it with Wisbar.
Wisbar is not free.
http://www.lakeridgesoftware.com/
sk806 said:
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
Click to expand...
Click to collapse
you had a chance at it yet? did it work?
...........
This is the thread I used to alter the Windows logo to a HTC logo among other things in this thread. It's dead easy,
1) Unsign the file using Unsigner linked to in the thread further up (on page 2 of the Unsigner thread there's a .bat file that I found gave a better idea of whether it had worked or not).
2) Open the file in Reshacker and go to Icon on the left hand side and click it to expand it. Go to number 292, click it and it will expand to show 1033. Click 1033 and it should be the start menu icon. Right click on 1033 and select Replace Resource. Select Open File With New Icon and find your new (resized) icon. Double click it and it will show a preview of new and old. Click Replace in the bottom right corner.
3) Save the newly modified file.
4) Sign the modified file using Ssigner linked to in the thread above. CHECK THE TEXT FILE IT CREATES TO MAKE SURE IT SIGNED OK. Don't forget this bit as it will mean a hard reset if you do (as I learnt).
5) If you've not installed SDKCert.cab some time in the past. download it from here, copy it to the phone and install it.
6) Copy the file to the Windows directory on the phone using Resco Explorer or Total Commander.
7) Reboot the phone.
how did you copy shellres.192.dll? it says "Acces denied" even with resco. No chance to renaming also
To get the file in the first place you need a program called ROM Extractor on the phone to get the file from ROM. There are also different varients of the ROM for different locales. There's a description in the link above.
thanks for your efforts but seems a little complicated TotalCommander did the trick, resco seems to have some security check problems
anyway, unsigner doesn't work so i'm stuck
guap said:
anyway, unsigner doesn't work so i'm stuck
Click to expand...
Click to collapse
Try the .bat file in the second page of the Unsigner thread. Copy Unsigner, the .bat file and the file you want to unlock to the same directory and double click the .bat file. Also, because the file is from ROM make sure it's not marked as Read Only when you get it to your PC before unsigning it. If it's from ROM they're usually Read Only for a start.
frostywrath said:
you had a chance at it yet? did it work?
Click to expand...
Click to collapse
Not yet. Just got back from work. I need a different job...
I will try tomorrow. I have been meaning to give this s shot for a while now, and the icon you posted is what I have been looking for.
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
guap said:
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Click to expand...
Click to collapse
True, but when I tried Unsigner on it's own it didn't give any feedback as to what it was doing (or if it did I missed it) so I changed 150+ icons only to find it hadn't been unsigned and therefore couldn't be resigned. At least with the batch file I can check it's been properly unsigned before making changes.
Does it give you any error messages when you try Unsigner?
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean me or someone else?
Prof. Yaffle said:
Does it give you any error messages when you try Unsigner?
Click to expand...
Click to collapse
that's the point: no errors from unsigner, but resourcehacker can't open my file (not valid bla bla bla)
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean this cab?
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/Colored Top Bar.cab
Don't forget you'll need to install this first:
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/1SdkCerts.cab
Hope this helps.
Prof. Yaffle said:
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
Click to expand...
Click to collapse
uhm seems reasonable
but I don't want to extract all my whole rom for a stupid dll... I extracted with total commander, isn't supposed to work this way?
Nope, certain ROM files can't be copied using normal file copy programs. I've found that they try and copy, then say the "File already exists, do you wish to replace?" and then whatever you select you're left with a 0k file with nothing in it. The ROM extractor doesn't copy the whole ROM. When you launch it you get a list of all the ROM files. Double click the one you want to extract, give it a location (\ usually for the root directory of the phone) and a name and click Extract.
Ok, I will try. But how to replace when modified? If I can't even read it, how will I replace it?
Hi.
I made a quick and crude patch to the TilewavePanel.dll file to cruedly but effectively correct the Daylight savings problem that I and lots of others were having.
----------
To use this...
1. Download THIS - TilewavePanel.dll which is 920KB in size... or use the 355KB ZIP file attached to this post.
2. Copy the new TilewavePanel.dll file to My Device\Program Files\Panels\TilewavePanel. Replacing the original.
-----> You may need to rename the old file first as it is "in use" but it still lets you rename it.
-----> If you are using the basic File Explorer built in to Windows Mobile then you may need to go to the Menu and check Show all Files before the dll files become visible.
3. Go to the Registry using Resco or PHM... Navigate to, HKLM\Software\SonyEricsson\TilewavePanel\City\0, edit the DaylightSaving key and change it to 0.
3. Do a soft reset.
-----> If the time is still 1 hour fast, then go back to the registry and check that the DaylightSaving key is still set to 0.
----------
What this does is... Whenever the Tilewave Panel weather gets updated, instead of overwriting the DaylightSaving key in the registry it writes to a different key DaylighSavinX. But the Daylight Savings time is still read from the original key. So you can change it to 0 without it being overwritten.
Hope this is useful!
Wow, another potential person in XDA
thanks!!
after installing patched DLL panel manager hangs...
panel is not workin after copy .dll file bro
what happen??
Excellent, thanks allot for your updated dll file. It solved my problem with the wrong time and can now have the weather updated automatically
It freezes after a reset?
The patch is tested will all jerpelea's first 5 test ROM.
------------
EDIT: Just tested as working on Jerpelea's 6th test ROM too.
dave-ro-mex said:
It freezes after a reset?
The patch is tested will all jerpelea's first 5 test ROM.
------------
EDIT: Just tested as working on Jerpelea's 6th test ROM too.
Click to expand...
Click to collapse
working very well
i like the way you thinking, making the weather update false string and system still reading the original key XD
thanks!!
Now it works with the same time as on wm 6.5 thanks alot!!!
Works just fine. Cheers mate.
Very good work, mate.
Just like everything in coding, very simple fix. If I knew how to amend .dll files, I would have tried to make it not write to a key at all, and completely remove that line of code.
Thanks for this, makes the panel so much better!
Does not work for me :-(
Yeeeeeeeeees!!!! It works!!! Thank youuuuu!!!
papa Marco said:
Does not work for me :-(
Click to expand...
Click to collapse
Agreed. I can't get this fix to work either. It works until automatic update and reverts back to being one hour ahead.
augie7107 said:
Agreed. I can't get this fix to work either. It works until automatic update and reverts back to being one hour ahead.
Click to expand...
Click to collapse
Sounds like you are not actually replacing the original dll file correctly. As the patch works just fine.
Go to My Device\Program Files\Panels\TilewavePanel.
Make sure Show all Files is checked on the menu. Then rename the TilewavePanel file that is 918K in size to "Old" or "Backup" or something like that.
Then Copy the patched TilewavePanel file from your Storage Card or using ActiveSync to My Device\Program Files\Panels\TilewavePanel.
Soft-Reset the device.
Go to the Registry and Set DaylightSaving to 0.
-------
You can confirm if the patch is installed by... First updating the weather on the Tilewave. Then, going to HKLM\Software\SonyEricsson\TilewavePanel\City\0 in the registry. There should be a new DWord value called "DaylightSavinX". If that key isn't there, it is not installed.
dave-ro-mex said:
Sounds like you are not actually replacing the original dll file correctly. As the patch works just fine.
Go to My Device\Program Files\Panels\TilewavePanel.
Make sure Show all Files is checked on the menu. Then rename the TilewavePanel file that is 918K in size to "Old" or "Backup" or something like that.
Then Copy the patched TilewavePanel file from your Storage Card or using ActiveSync to My Device\Program Files\Panels\TilewavePanel.
Soft-Reset the device.
Go to the Registry and Set DaylightSaving to 0.
-------
You can confirm if the patch is installed by... First updating the weather on the Tilewave. Then, going to HKLM\Software\SonyEricsson\TilewavePanel\City\0 in the registry. There should be a new DWord value called "DaylightSavinX". If that key isn't there, it is not installed.
Click to expand...
Click to collapse
I'm sorry but my ignorance is frustrating me.
First download link is bad. Zip file can't be downloaded to device with IE because it opens straight to Total Commander and won't extract.
Opera 10 Beta keeps hanging up and I can't get it that way either.
Downloaded to PC, extracted dll and emailed it to my account.
Accessed with device and followed instructions. Still not working for me.
Extracted dll is 918.7kb just as original.
Can you possibly enlighten me?
After Hardrest my device it works - only the Mail-Button has no functionality right now.
very very good. thanks, now the panel is useful
Thank you. I love you, mon.
Simply changing the daylight saving time from 1 to 0 or vise versa wortked for me - did not need to change dll.
Ctrl+A said:
Simply changing the daylight saving time from 1 to 0 or vise versa wortked for me - did not need to change dll.
Click to expand...
Click to collapse
Do an update for your weather and check again.
warning: this tool is for flashaholics. The ones who know all risks of flashing roms and like to live in the fast lane
Note for HD2-users: Although this version can be also used for the HD2, you may like this version more (the HD2 version doesn't require that you provide a "preflash" .nbh file - see further).
- Description:
FlashaholicRUU (FRUU) is a customized version of the HTC Rom Update utility that will simplify the rom update proces by:
1. performing a task29 before updating a rom
2. allowing the user to navigate through the dialog windows without having to check checkboxes (s)he has seen a gazillion times before.
3. allowing the user to use only the keyboard to go through the dialog boxes (enter -> next window, esc -> quit fruu)
- Prerequisite
Task 29 is performed by flashing a .nbh file before the (custom) rom file. Because the tool is meant to be general applicable for all devices you need to provide this "pre flashable" .nbh file yourself. In principle you can use any .nbh file for this. To speed up this first step though it is recommended to use a radio for your own device or better yet, a .nbh file containing only the splashscreen for your device. Rename this file (radio, splashscreen ) preflash.nbh and put it in a directory together with your custom rom file (may have any name as long as it has an .nbh extension) and the general_FlashaholicRUU.exe. Make sure there aren't any other files in the directory.
For the rest follow the instructions described in the section Usage
- Usage:
This program will take you through the steps of performing a Task29 (formatting your roms storage memory) and then flashing a new rom. It is not advised to use this if you are totally new to flashing roms as if it is done incorrectly you will end up with no rom on your phone and a permanent look of terror on your face
This is not for noobs!!
1. Make sure your phone is booted up
2. Sync your pc and phone
3. (you may skip this step if you've read the prerequisite) Copy the general_FlashaholicRUU.exe file to a new folder with JUST the roms .nbh file present and a rom you want to flash before you flash your rom. Rename this last rom file, the one you want to flash first, preflash.nbh
4. Run the general_FlashaholicRUU.exe and follow the instructions in the program
5. Click on the "perform task29" button to format your roms memory
6. As soon as the percentage bar reaches 100% hold your "volume down" button and continue holding until the phone reboots and enters the bootloader screen
NOTE: If you get a white screen with "hTC" in the middle then you need to take out your battery and enter bootloader mode manually before continuing (take battery out and put it back in, then hold the volume down button and briefly press the power button. Keep holding the volume down button until the bootloader screen appears).
7. When the white box in the bottom of the bootloader screen says "USB" then click on "Flash Rom" in the Flashaholic program
8. Follow the onscreen instructions and lastly click on "Flash" to flash the rom to your phone
9. You will now have a percentage bar on your phone and your new rom is being flashed
10. Once your Rom has flashed your phone will reboot and you can go through the setup screens.
Run your new Rom for a few hours, search for another one and start again with step 1 (if you want to become a real senior flashaholic)
NOTE: There is no need to perform a Hard Reset after flashing the Rom using this program as the Task29 performs a much more thorough job.
--------------
When you want to flash a rom without performing task 29 (for example when you want to flash a new radio) just hit <ESC> on the first screen of step 1. This will take you right to step 2 in which you can flash your rom
Click to expand...
Click to collapse
(Thanks to mskip for writing this brief but comprehensive manual)
- Video:
Video of the app on a computer of a fellow flashaholic: http://www.youtube.com/watch?v=hn3pGbW-vag. Thank you claub. Keep on flashin'
- Note to chefs:
You can pack FRUU with your Roms. You can even customize FRUU for your Rom series. For example you can use your own images, text, info etc. I have written some general instructions about customizing the RUU here. (Notice that in FRUU ModelID.fig is used for the first task29 step and RUU.fig is used for the second step. The dialogs for the first step are part of RUUResource.dll. Dialogs for the second step you will find in CustomizedRomResource.dll. Instead of the setup.bat and setup.vbs I mentioned in the aforementioned post I used the files run.bat and run.vbs. For exra information you can PM me)
- Donations:
Thank you!
Thanks to: doloop (for his non-mtty task 29 tool)
---------
Note: this tool should work for any (newer) htc device. Nevertheless make sure that your bootloader will support task 29 and that experiments with mtty task 29 has positive results for your device (look at the development section for your device forum)
Devices on which this tool is reported to work:
* Leo (HD2)
* Rhodium (Touch Pro 2, Tilt 2)
* Topaz (Diamond 2, Pure)
* Raphael (Touch Pro, Fuze)
* Diamond
(please pm me or report your device in this thread if the tool worked also for your device and that device is not in this list yet)
Click to expand...
Click to collapse
Happy flashing
appelflap said:
Rename the radio rom file to radio.nhb[/COLOR]
Click to expand...
Click to collapse
Not Radio.nbh? Isnt it typo?
Petulinek said:
Not Radio.nbh? Isnt it typo?
Click to expand...
Click to collapse
Yes, it is a typo. Should be radio.nbh
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
core7x said:
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
Click to expand...
Click to collapse
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
Click to expand...
Click to collapse
clear, will do that
core7x said:
clear, will do that
Click to expand...
Click to collapse
You naughty boy... naughty naughty naughty
appelflap said:
You naughty boy... naughty naughty naughty
Click to expand...
Click to collapse
joke only, by the way. im flasholic rom person.
core7x said:
joke only, by the way. im flasholic rom person.
Click to expand...
Click to collapse
I kinda hoped that you noticed the ironic undertone of my reply
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Click to expand...
Click to collapse
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
gguruusa said:
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
Click to expand...
Click to collapse
Not when you just want to update your radio without updating or resetting the os
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
Click to expand...
Click to collapse
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
and with respect to your other advice, this is a tool for flashaholics you know. I don't think flashaholics worry very much about the memory of a device they use for 1-2 years max.
appelflap said:
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
Click to expand...
Click to collapse
I totally quote appelflap on this one.
I've never ever had battery drain problems with my flashes, the very first time I had those is when I attempted at flashing just a new radio radio keepin the rom and the data. Before thatm, flashing a new radio always was done when flashing a whole new rom, and after a task29 anyway.
After that "radio only" flash, hell ensued, as no matter the radios I changed thinking it was the radio version's fault, I was getting up to 16% drain overnight, and anyway not lower than 12%, against a normal 4-5%, with a standby drain of 20mA and more, against a normal of 4-7mA.
Next thing I did, task 29 + radio + rom and now I'm getting a whopping 3% drain overnight with my current rom combo, never went so low.
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
resqman said:
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
Click to expand...
Click to collapse
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
appelflap said:
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
Click to expand...
Click to collapse
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
resqman said:
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
Click to expand...
Click to collapse
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
appelflap said:
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
Click to expand...
Click to collapse
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Obviously I am missing something here
resqman said:
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Obviously I am missing something here
Click to expand...
Click to collapse
Thanks for your feedback! This was exactly the feedback that I was looking for.
The task29 tool from the rhodium forum flashes a ruu_signed.nbh that is specifically brewed for the rhodium. Indeed flashing this file doesn't touch anything.
Problem is I can't use such device specific files for a universal flashing tool. That's why I use radio nbh. So that I'm sure that the tool runs task 29 with a nbh file that is accepted by the device that is flashed.
The ruu_signed.nbh that task29 uses for the rhodium is 8.5 mb large. This will take more time to flash than a bootscreen (which is 0.7mb) but less than a radio (which is > 10 mb). May I suggest to use this tool with a bootscreen nbh it is soooo much faster.
Anyway when I get my device back I will look if I can brew a small nbh file that doesn't change the bootscreen or radio. I will target it to different devices and wrap it up for each specific device.
Again, thanks for your input.
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
appelflap said:
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
Click to expand...
Click to collapse
I understand now. It's not really a big deal for me to flash a radio. It would be a lot of work for you to have to create a signed ruu for every device.
Thanks
Thanks!!!!