Related
Has anyone been able to customize the welcome screen of WM6 or WM5?
Or anyone has got some suggestions on this issue?
Regards,
Hassan
Hassan101 said:
Has anyone been able to customize the welcome screen of WM6 or WM5?
Or anyone has got some suggestions on this issue?
Regards,
Hassan
Click to expand...
Click to collapse
If you look a bit further down this section you may find what you're looking for.
Jay
responderman said:
If you look a bit further down this section you may find what you're looking for.
Jay
Click to expand...
Click to collapse
Thanks a lot but the issue u r pointing at is about the boot splash and I want to change the welcome screen (green wm6 spash).
Any clue
You need to overwrite the Welcomehead.192.png in Windows\ with yours one.
Try search more on the forum!
unapproachable2kx said:
You need to overwrite the Welcomehead.192.png in Windows\ with yours one.
Try search more on the forum!
Click to expand...
Click to collapse
Wow ! .. Its all DONE !!!
I Reallyyyyyy appreciate ur help !!!
Regards
Your solution works, but look, there are 2 splash screens, that you talks are the second one, how i change the first?
gajodafeira said:
Your solution works, but look, there are 2 splash screens, that you talks are the second one, how i change the first?
Click to expand...
Click to collapse
Ah, on most HTC devices I've used the welcome screen is not the same as the splash screen and I think that might be the problem here. The welcomhead file is your welcome screen and easily replaced in your kitchen, but the splash screens (2 of, although sometimes seems like 1 as they might be identical) are installed as part of your ROM.
When you use get to the point in a kitchen of having an OS.nb or Windows.nb or however it's phrased, and you're ready to turn this into a full ROM file, you can add in other things like the IPL, SPL, 1st and 2nd splash screens, radio and extended ROM, each of which has its own .nb file.
Welcomehead is easy to change. The splash screens aren't hard to change and you should find instructions somewhere in any kitchen manual probably. Haven't time to look for you now though, you'll have to scan about in any kitchen-related docs or web pages you have or know of.
chunkymonkey said:
Ah, on most HTC devices I've used the welcome screen is not the same as the splash screen and I think that might be the problem here. The welcomhead file is your welcome screen and easily replaced in your kitchen, but the splash screens (2 of, although sometimes seems like 1 as they might be identical) are installed as part of your ROM.
When you use get to the point in a kitchen of having an OS.nb or Windows.nb or however it's phrased, and you're ready to turn this into a full ROM file, you can add in other things like the IPL, SPL, 1st and 2nd splash screens, radio and extended ROM, each of which has its own .nb file.
Welcomehead is easy to change. The splash screens aren't hard to change and you should find instructions somewhere in any kitchen manual probably. Haven't time to look for you now though, you'll have to scan about in any kitchen-related docs or web pages you have or know of.
Click to expand...
Click to collapse
When i changed for wm6 the rom changed the 1st and the second splash. I changed again into the 6.1 and only the 2nd was changed, so i think that the 1st aren't directly connected to the ROM.
gajodafeira said:
When i changed for wm6 the rom changed the 1st and the second splash. I changed again into the 6.1 and only the 2nd was changed, so i think that the 1st aren't directly connected to the ROM.
Click to expand...
Click to collapse
It just depends on whether the ROM you install happens to come with 1 or 2 or no splashscreens. There's a splash1.nb and splash2.nb (might be slightly different names to that but will be similar) in a full, original ROM - and a radio, IPL, SPL and Ext-ROM too. Each has its own .nb file. (The names of them vary a bit between devices but they're pretty much always easily-recognised.)
Cooked ROMs usually are OS-only, and only made from an OS.nb (or Windows.nb sometimes - you could actually call it anything and still use it). Sometimes however, someone bundles a splash1 or a splash2 with it or both. You could install a ROM and find no splashscreens change afterward - which is usually the case. Whenever I download a ROM and it comes with a splashscreen, I almost always break the ROM down into it's .nb files and then put it back without the splash1 or splash 2 in it.
If you have a go with any ROM using HyperCore you'll find ROMs with 1 splashscreen have 1 .nb file relating to splashscreen and ROMs with 2 splashscreens (or a splashscreen which apears to last ages, which is just identical splashscreens) have 2 .nb files relating to splashscreens.
I don't think not having splashscreens saves any space though as I'm fairly sure that the space is essentially allocated to the relevant .nb files (for splashscreens they're 256k each, the nb files, even if the picture you used was 1 0.5k black mono pic).
Learning to use HyperCore obliquely taught me and many others a fair bit about how these things tick. Not a techie, mind - just done a lot of phone flashing. It's brilliant.
By way of example, here's the .nb file-list from an official (OrangeUK) Hermes ROM. (The basic format is generally the same between devices, even if the names alter - it just happens to be the most recent ROM I broke up in this way and still have the files to list for you.)
RUU_Signed.nbh is the file one would flash. This is made up from:
Windows.nb
Herm_ExtendedRom.nb
IPL.nb
Radio.nb
PrimarySplash.nb
SecondarySplash.nb
SPL.nb
The format doesn't change much between most devices, even if the names change.
I used to have a tool (can't remember who made it) for creating the .nb files for splashscreens. If I find it I'll attach it.
chunkymonkey said:
I used to have a tool (can't remember who made it) for creating the .nb files for splashscreens. If I find it I'll attach it.
Click to expand...
Click to collapse
I think this is what you were looking for:
http://forum.xda-developers.com/showthread.php?t=317436
However, would you mind helping me with something? How in the world did you split the nk.nbf into Windows.nb, IPL.nb, PrimarySplash.nb, SecondarySplash.nb and SPL.nb?
Aaaany help would be muuuuch appriciated.
(and yea, I have hypercore and I'm too stupid to understand how to make use of it )
Verbato said:
I think this is what you were looking for:
http://forum.xda-developers.com/showthread.php?t=317436
However, would you mind helping me with something? How in the world did you split the nk.nbf into Windows.nb, IPL.nb, PrimarySplash.nb, SecondarySplash.nb and SPL.nb?
Aaaany help would be muuuuch appriciated.
(and yea, I have hypercore and I'm too stupid to understand how to make use of it )
Click to expand...
Click to collapse
Good news is you're okay with this already if you've got hypercore. Duttythroy's made a genius tool for it, appropriately entitled Dutty's Good NBH Tool. It splits .nbh files into the .nb files that comprise it, and that tool is in your hypercore.
It's also in just about every kitchen. Definitley on your hard drive somehere. Just use the page that disassembles (not in the programmer's sense) an .nbh file, not the page that puts one back together form the parts we've been talking about.
Good spot on Oli's tool, but it was another one. Had a very simple interface 1-click interface. Wish I could remember whose it was now 'cause I definitely don't have it any more. (Unfortunately, my external HDD went down recently and took ... well, everything with it from the last, ooh, 12 or 13 years. And yes I did have a backup: that was it; the proper HDD went down a few months earlier and, like a complete tool, I left it till the backup died before replacing it.)
EDIT: here it is, to save you searching mate.
Thanks
Uhm... Yea, I've been on the "right path" for so long, I have HypeCor, L26.v7, Helmi kitch r0... and I still haven't figured out how to make anything from the nk.nbf-file.
Reading a bit I thought typho5 would -x it into an nbh-file. No such luck. Just died on me telling me the .nbf-file has an "unknown header format".
I've even tried dumping from the phone with some "grab-it"-program.
http://forum.xda-developers.com/showthread.php?t=238945
It works, it spits out something. But what it is, what format etc I am unsure of.
Heeelp!
I am totally lost here...
Verbato said:
Thanks
Uhm... Yea, I've been on the "right path" for so long, I have HypeCor, L26.v7, Helmi kitch r0... and I still haven't figured out how to make anything from the nk.nbf-file.
Reading a bit I thought typho5 would -x it into an nbh-file. No such luck. Just died on me telling me the .nbf-file has an "unknown header format".
I've even tried dumping from the phone with some "grab-it"-program.
http://forum.xda-developers.com/showthread.php?t=238945
It works, it spits out something. But what it is, what format etc I am unsure of.
Heeelp!
I am totally lost here...
Click to expand...
Click to collapse
Ooh, I wouldn't go messing with that just now. If all you want is to take an .nbh file and break it up into the various .nb files, just run dutty's tool, browse to your nbh file and go. it'll dump all he .nb files in no time at all, maybe less.
If that's not what you're trying to do then I'm barking up the wrong tree and therefore not helping, but if that's the case just re-explain your needs and I'll have another go.
chunkymonkey said:
Ooh, I wouldn't go messing with that just now.
Click to expand...
Click to collapse
Oooohh... I love to mess around
Okay, exact mess I want to get my self in to:
swat4 was as kind as to drop a WM5-image with sdhc-drivers. I want to take out those .dll-files and add them to another image. Namely Helmi_UNI_AKU3.5_v1.3.1.
But so far all I have is this nk.nbf-image. That, and I found this grab-it-tool, which copys the roms image straight over to SD-card in raw format.
Hmmm... Any hints to point me in some general direction as to what to do next?
Verbato said:
Oooohh... I love to mess around
Okay, exact mess I want to get my self in to:
swat4 was as kind as to drop a WM5-image with sdhc-drivers. I want to take out those .dll-files and add them to another image. Namely Helmi_UNI_AKU3.5_v1.3.1.
But so far all I have is this nk.nbf-image. That, and I found this grab-it-tool, which copys the roms image straight over to SD-card in raw format.
Hmmm... Any hints to point me in some general direction as to what to do next?
Click to expand...
Click to collapse
Righto.
If I was trying to add SDHC drivers to a ROM that didn't have them already, I think I'd be using HyperCore to turn the nbh of that ROM into .nb files and then into the series structured files and folders that kitchens usually use, OEM, SYS, ROM, etc., and then just adding an SDHC OEM. After which HyperCore becomes very similar to most kitchens.
OR I'd be just popping a line into the preconfig file if there is one, such as "CAB: /Windows/SDHC_drivers_that_I_wish_were_already_included_in_this_ROM.CAB" for example and letting it install as a cab at the preconfig stage instead of an OEM. (I'm a big preconfig fan.)
Might be quicker to use a kitchen from scratch than HyperCore to edit a pre-existing ROM though.
Hey, wow, thanks for all your help!
I still don't understand how to make an .nbh-file out of an .nbf-file though.
However I've tried copying sdbus.dll, SDHC.dll and SDMemory.dll to /Windows on the device, like I was recommended by someone else.
All that did was make my sdhc dissapear. No luck there.
I'm so frustrated, just looks like getting a proper WM5-image to work with >4G sdhc isn't feasible. Or at least, not for now.
Which is so frustrating, since there is one that does work. Gnh!
However, thanks for your time. I appriciate it.
I use this one
Try the linked one. Easy to use, I find it somewhere here.
http://zolee-ka.uw.hu/CreateBootScreenPackage.rar
And here's an alternative one - the one I was referring to earlier. By a mad coincidence, I just came across this when I was looking for someting else entirely.
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?
To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Before you start be aware that you will may end up wiping your phone once, if not more. So lets go over the things that you will need.
You will need JF's RC30, RC8, or ADP1 V1.3, depending on what version you intend to create for.
Here is the link to these: http://forum.xda-developers.com/showthread.php?t=466174
You will also want to get the dev bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
Link to dev bootloader: http://forum.xda-developers.com/showthread.php?t=455860
You will also need to resign all the apks located in /system/app and framework-res.apk located in /system/framework. When you push all of these to your phone.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Here is the link: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
I will assume that you have the sdk downloaded and extracted somewhere(if not, do that now), extract both files to the tools directory of your sdk.
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.(This is for XP, Vista coming soon)
To do this, right click on My Computer click properties, then choose the tab that says advanced. Click the button that says environmental variables. Go to system variables find the one that says CLASSPATH, double click it, go to the end of variable value. There should be a semicolon ; at the end. type in the path to the testsign.jar located in the tools directory of your SDK, for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar If CLASSPATH is not in your system variables then create it. Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory. For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
You will also need a version of linux installed or running vmware with linux, if you want to create, or edit, an update script, which will install the theme onto the users phone.
You will need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure every file gets signed. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of itself. To find these images open up the apk, you can rename it to .zip or open it with an archiver of your choice, winrar, winace, etc. Then after opening the apk open the folder called res and inside of that there are folders that are named Drawable, drawable-land, drawable-port, etc. This is where the images are stored.
Ther are some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png. If you do you will have problems...Trust me. These are special images called ninepatch images and android resizes these images to fit wherever android, or any other apk, needs it to. if you do open them or edit them they will no longer render correctly when resized. I believe that in order to edit these you must do so and then put them into the source and rebuild the entire apk.
Before getting started you must also realize that you cannot simply resign one or two apk's and stick them in your phone and expect them to work. You must resign every apk inside of /system/app and framework-res.apk and put them on your phone at the same time.
To simplify this process for you though, I have provided an empty update.zip which you can place all of your resigned apps into and use to update your phone to your custom theme. You can also download someonelses theme and use there files, since they are resigned already. It may also be easier to see what files do what and go where since they have already been edited and are easy to point out.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. Note that if you are using windows you will need to unhide known file extension types. you can also use your favorite archiver such as winrar, winzip, etc.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsoft/windows/extension-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-vista/how-to-change-a-file-extension/
After opening the apk go to res and copy the folders that have drawable in their name. Go to your desktop, or wherever, create a new folder called Images, or whatever. Open the folder, paste the drawable folders in there. Now you can see what the files look like without opening them. Btw, you may also want to add -frame, or -launcher, to the end of the folders you cope over to keep them separated from others.
Finally, you've edited the images put them all in the apk renamed it back to an apk and resigned it. Now it's time to push it to your phone and see the changes you've made.
Important! : Whenever pushing files to the phone NEVER do it while the phone is running. Do this in recovery mode! If you do this while the phone is running normally you will begin to lose space in /system.
So, boot into recovery plug your phone in and open a cmd prompt. From the cmd prompt type adb shell mount /system then type the following: adb push c:\whereveryourfileis\whateveryourpushing.apk /system/app (system/framework if your pushing framework-res.apk)
Now reboot your phone. If it doesn't boot, try doing a wipe, if that doesn't work reinstall an update and try again. There are alot of things people can do wrong, I can't explain them all here. If you get real stuck, you can ask for help here or contact me on Gtalk [email protected].
So now your theme is done and your ready to make an update.zip for others to install your theme.
I have created a template for you to make your own update.zip. Just download, add the system apps to app, and framework to framework. Zip it up, SIGN IT, TEST IT YOURSELF, and then distribute it!
Empty update.zip template: Http://www.FightForthePits.com/Androidstuff/update_empty.zip
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Stericson
Links of interest:
Downloading SDK: http://code.google.com/android/intro/installing.html
Using ADB: http://code.google.com/android/reference/adb.html
Working with ninepatch should be straightforward if you use the draw9patch tool included in the SDK. Documentation on usage here:
http://code.google.com/android/reference/draw9patch.html
JF could also save theme users a wipe by resigning /system/app/* and /system/framework/framework-res.apk in his builds with the test keys. Nice tutorial, btw.
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Stericson
Stericson said:
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
Click to expand...
Click to collapse
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Click to expand...
Click to collapse
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
thx stericson this will help big time how long before I can get resigned rc30 last night when you said all the apk. need to be resigned I was like this is going to be a long night but I see jf hooked you up save some big time with his resigning tool
jashsu said:
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
Click to expand...
Click to collapse
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Stericson said:
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Click to expand...
Click to collapse
The resigned apps have been released, each update file will resign all of apps in /system/app and framework-res.apk. However, these updates make no changes to them whatsoever...Meaning your phone will look just like a brand new phone without any modifications.
rc30 works thx Stericson made it easy for use
Issues with using the update.zip above
Hi all,
I just wanted to point out that after I applied the update.zip above and rebooted applications kept force closing randomly and constantly even through the initial setup (where you have to click the green android to start).
Prior to this, I had JF's RC30 1.3, and the engineering bootloader V2 no sigcheck.
First I did just a alt+s then a alt-w and alt+s. And still nothing.
I'm new to all this so I'm not even sure where to begin troubleshooting. Should I be using the HardSPL?
Thanks in advance and I appologize if this isn't the right place for this post.
Update:
After reflashing with JF's 1.3 RC30 and the problem persisted I noticed that there was a new release 1.31 and this has fixed the problem. I hope this helps anyone else who runs into the same problem.
I still don't know what went wrong though, can anyone shed some light on this? thanks.
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Alright, I am a little confused........
So I downloaded testsign.zip and extracted it to the tools folder. Then I went into environmental variables and added CLASSPATH with the value D:\Android\tools\testsign.jar and now I am not sure what to do next. Can someone give me some clarification. And btw I am on XP but I can get on linux at home if I need it, but I am a total noob to all this stuff so be gentle.
I'm using http://www.fightforthepits.com/Androidstuff/update_Rc30.zip and have been encountering issues when the phone boots up. As soon as the initial phone setup comes up I get process force close errors, I extracted launcher.apk, edited the files I wanted, repacked it, signed it and then resigned the update.zip. Any ideas what I'm doing wrong? I'm already running JF's RC30 1.31
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Stericson said:
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Click to expand...
Click to collapse
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
I also had the issue with force close when installing the resigned update from the first post, apps that shouldn't even run on start up were force closing.
Also the IM application was gone, had to do a wipe and go back to jf 1.31 to correct it
I will take another look at the update I provided...
Stericson
did you ever figure out how to change the text on the status bar from black to white?
to do that you have to rebuiuld the entire apk from source and edit an xml document
Stericson
has anyone tried making the icons bigger? I noticed they are 48x48 if we go bigger will that affect anything? Also has anyone been able to remove the text below the icons on the home screen? Oh and where is the tab located that has been made invisible?
*edit
well I tried making the icons bigger and it doesn't really do anything, they don't show up bigger on the screen. Might have something to do with the text underneath, not sure.
Kyeld said:
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
Click to expand...
Click to collapse
yes they must be signed.
Hey guys, I've been reading for a while now, finally decided to sign up.
I'm making some modifications to the Galaxy Tab, just playing around and seeing what all is possible. Before I go start deleting potentially important system files, I wanted to get myself a little 'brick insurance'. I'm looking to get a copy of the stock firmware for the US Verizon Wireless version of the Tab (SCH-I800). It is currently running DJ11.
I don't think it is available from either Samsung or Verizon currently, although Samsung HAS provided all of the source code. If I wanted to make a backup of the firmware, something that I could load from the SDCard (ideally, just give it one of those update.zip files) how would I go about doing that?
This is my current plan, tell me if I'm not on track here. I have downloaded the Android Froyo source code available on the Android site. I downloaded the SCH-I800_OpenSource files from Samsung's open source center. If I combine these files as described in the readme from Samsung, and then build the whole project, I should get some sort of "stock" software, in basically the exact same state that it was when I got it from Verizon. Does this sound right?
I want to be able to quickly revert back to like-new set up, so I would prefer to not have to use one of the modified European/International versions if possible. Is there any other trick to getting an unmodified firmware to revert to? Any suggestions?
Thank You
I don't think it'll matter until someone creates a new recovery image. If you could get a clockwork recovery image, you'd be a hero
DavidThompson256 said:
This is my current plan, tell me if I'm not on track here. I have downloaded the Android Froyo source code available on the Android site. I downloaded the SCH-I800_OpenSource files from Samsung's open source center. If I combine these files as described in the readme from Samsung, and then build the whole project, I should get some sort of "stock" software, in basically the exact same state that it was when I got it from Verizon. Does this sound right?
Click to expand...
Click to collapse
Not even close i'm afraid!
Samsung are only required to release the Linux kernel source. The actual OS is not licensed under a "copy left" license, so Samsung are under no obligation to release their customized Android code.
So, you could create your own AOSP build, but this would be absolute stock Froyo - no Samsung launcher, or any of their custom apps.
Regards,
Dave
Yaotl said:
I don't think it'll matter until someone creates a new recovery image. If you could get a clockwork recovery image, you'd be a hero
Click to expand...
Click to collapse
You can use odin or redbend_ua to flash firmwares, you don't necessarily need clockwork - although it would be nice!
Hey infamousjax,
Do you happen to have an update.zip for the verizon tab you can upload? I managed to ninjamorph my framework so nothing opens anymore. I must have used a file that was the wrong png format or something. Anyway I do have the backup framework-res.apk, but I am unsure on the "update-script" as I can't get programs on my tab at the moment.
ninja4hire said:
Hey infamousjax,
Do you happen to have an update.zip for the verizon tab you can upload? I managed to ninjamorph my framework so nothing opens anymore. I must have used a file that was the wrong png format or something. Anyway I do have the backup framework-res.apk, but I am unsure on the "update-script" as I can't get programs on my tab at the moment.
Click to expand...
Click to collapse
I have the Sprint version... and the stock recovery can't flash update.zips unless they are signed.
infamousjax said:
I have the Sprint version... and the stock recovery can't flash update.zips unless they are signed.
Click to expand...
Click to collapse
Yeah I just tried to make an update.zip and sign it with a test signer. Now when go into recovery and run the update.zip it freezes on an Android icon with an exclamation point.
ninja4hire said:
Yeah I just tried to make an update.zip and sign it with a test signer. Now when go into recovery and run the update.zip it freezes on an Android icon with an exclamation point.
Click to expand...
Click to collapse
Can you boot up regularly?
yeah, it's just that I can't open programs or the settings menu.
edit: I have been trying to do an update.zip, but I keep getting "E: signature verification failed". I have tried to different signers already...
This one
http://www.robmcghee.com/android/creating-an-android-update-zip-package/
and this one
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
Your not going to able to sign it without Samsung's signatures... and good luck finding those
yeah I pretty much gave up. I called last night and got the verizon insurance. So now I'm just gonna wait a few days then tell them I dropped it and pay $80 for a new one.
just tell them it started bootlooping for no reason... they should replace it for free if its within 30 days
So it sounds as though I'm not really on the right track here, perhaps I don't need to recompile this thing myself. From some of the replies, I've gathered that there IS at least some way to create a backup of the firmware, in case I screw it up.
Can anyone point me to specific steps on how to do a backup for the Tab? I've seen several guides for other phones before, but I believe that each device is slightly different, and may take different steps. Any suggestions?
Thanks again.
For your stock recovery
Code:
cat /dev/block/bml8 > /sdcard/recovery.bin
For your kernel
Code:
cat /dev/block/bml7 > /sdcard/zImage
Thanks a lot, that info was really helpful!
So, unrelated now, but just kind of curious... is there a reference sheet somewhere or something that explains what each of the files in /dev/block is for? I know they are different sections of the filesystem.
I have about 60 different files in that directory, and was just curious to know what each of them was for.
Thanks again for all the info.
DavidThompson256 said:
is there a reference sheet somewhere or something that explains what each of the files in /dev/block is for? I know they are different sections of the filesystem.
Click to expand...
Click to collapse
What they represent is different devices, not different sections of filesystems. At best (without RAID or LVM) each device holds one filesystem. In unix, filesystems can be mounted at various points into the root filesystem to appear as a single namespace, but they will still be separate filesystems.
Under the block dir you will see anything that is a block device, anything that can be written to randomly, as opposed to a serial type of device. So, all the random access hardware on your device (SDCARD, NAND...) will be represented there except for your RAM. Each physical device will likely have partitions on them so, if a device is named xxx, xxx01 will likely mean partition one on device xxx. Sometimes the same device will appear with several names, one may be buffered access, the other may be raw.
Your internal NAND is likely on the same device, just different partitions of that device. Some of these partitions may not hold filesystems, they may hold other blobs such as a boot loader, or the kernel. To see which ones hold filesystems, you can type df in a terminal and you will likely see which devices are mounted where in the filesystem namespace.
As for the rest of the devices and partitions, they are very hardware device specific. And I don't own a Galaxy tab, so I can't help with that, sorry. But, I hope I didn't give you info you already knew and I hope it might have been at least somewhat helpful...
Hi All
I've searched and not found much info on this.
I've got a dump of an HTC HD7 using the Riff box (JTAG). The file is a 512MB BIN file.
Basically I would like to be able to see the files inside it. Ideally I would like to see the files/folders/structure inside the dump. I don't know how difficult or easy this is, so forgive me if I'm asking for the impossible. But is there a way of converting the bin file to something like a cab/nbh or even the files/folders so that I can view them in explorer or some similar tool?
At the moment I'm viewing the file in a hex editor trying to carve out certain files. But I figure since the file system and structure is known on Windows Phone 7, there may be a way of converting the entire image to a better support format.
So if anyone can suggest any tools or ways of doing this, it would be much appreciated.
Thanks
How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Sent from my SGH-i917 using XDA Windows Phone 7 App
snickler said:
How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Click to expand...
Click to collapse
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far
puunda said:
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far
Click to expand...
Click to collapse
Where do you get a riff box from? I want to dump my rom. I would look into the Windows Mobile threads and see if there is a tutorial OR pm ansar or xboxmod and see if they can help out. If possible can you provide how to obtain an use the riff box?
Sent from my SGH-i917 using XDA Windows Phone 7 App
nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.
ted973 said:
nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.
Click to expand...
Click to collapse
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks
puunda said:
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks
Click to expand...
Click to collapse
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.
snickler said:
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.
Click to expand...
Click to collapse
I've looked on that thread and have downloaded the tools. I've also messaged the author of the tool, but not got a reply yet. It looks like the tools which does work on the raw dump/bin files are for the logo and bootloader, not the entire image.
I'm still working on it, but there seems to be a lot of info that I need to sort though.
You may use Qualcomm tool from riff plugin. It's view all partitions
Missed this one.
No questions in the development section please!
Thread Closed