We are now able to create patches for the FFS, SHPAPP and CSCfs areas using the PFS format, but I haven't found anything similar for the RC1 area. This would be immensely useful, as we'd be able to make design changes (like icon replacements, quickpanel, ...) without replacing the full RC1 file (which might lead to other problems, as these vary between different FWs).
Is there any possibility to patch the RC1 area via a MultiLoader patchfile (similar to PFS)? Any ideas?
k8500 said:
We are now able to create patches for the FFS, SHPAPP and CSCfs areas using the PFS format, but I haven't found anything similar for the RC1 area. This would be immensely useful, as we'd be able to make design changes (like icon replacements, quickpanel, ...) without replacing the full RC1 file (which might lead to other problems, as these vary between different FWs).
Is there any possibility to patch the RC1 area via a MultiLoader patchfile (similar to PFS)? Any ideas?
Click to expand...
Click to collapse
Nice idea...
This would make some changes much more easier...
1.
RC1 is mounted Image with READ Only access...
No writing...
No idea how to add Write access...
2.
Paths could be spread over more then 1 file...
apps_compressed.bin and/or *.so files involved...
http://forum.xda-developers.com/showpost.php?p=33706880&postcount=247
See here... its seems mirror paths... maybe we can use them...
3.
Reduce RC1 for faster testing.
This is 1 reason why I have create such files.
http://forum.xda-developers.com/showpost.php?p=32439954&postcount=112
Best Regards
http://wapinet.ru/files/show.htm?d=1885&f=nv_default.ini
Seems from U800...
But check this:
Code:
NV_SI_SKIN_COLOR_BASE_BITMAP_PATH=/System/Rsrc/Bmp/Black/
NV_SI_SKIN_COLOR_USED_BITMAP_PATH=/System/Rsrc/Bmp/Black/
Best Regards
Edit 1...
Seems also in Wave... Check this Thread:
http://forum.xda-developers.com/showthread.php?t=1507782
I will try...
Code:
/System/Rsrc/Bmp/Black/
/Media/Others/Bm/Black/
---------- Post added at 06:08 AM ---------- Previous post was at 05:36 AM ----------
Seems working...
Easy Text Edit...
Step 1.
FmSecureMode off
Step 2.
Copy folder NV... you need only nv_default.ini
Step 3.
Change paths...
Example:
Code:
/System/Rsrc/Bmp/Black/
[B]/Media/Others/Bm/Black/[/B]
Step 4.
Copy back nv_default.ini
CAUTION!!!
At your own risk.
Better create before folder /Media/Others/Bm/Black/
And copy all RBM files you need.
Best Regards
Cool !! How to disable FmSecure ?
http://forum.xda-developers.com/showpost.php?p=12436452&postcount=1
With QuB or other Tools possible...
Remember Screenshot Tool from User Dokugogagoji...
1 Click
Best Regards
I was just in the process of giving up, and then you come up with this. Absolutely great! Now, I'm going to do some experiments of my own. This will make everything that much easier.
k8500 said:
I was just in the process of giving up, and then you come up with this. Absolutely great! Now, I'm going to do some experiments of my own. This will make everything that much easier.
Click to expand...
Click to collapse
I didn't have success.If you'll be get it.Just tell me
hero355 said:
I didn't have success.If you'll be get it.Just tell me
Click to expand...
Click to collapse
It didn't work for me either... FMSecureMode Off and editing nv_default.ini works without trouble. Regardless of any changes, the actual RBM path does stay the same: Changes in the new Rbm path don't show up, and flashing a RC1 with an empty Rbm folder leads to bad graphical errors. Doing the changes via a full flash (nv_original.ini edited and Rbms in SHPAPP or FFS) doesn't change anything either (checked nv_default.ini after the full flash, paths are changed).
Adfree, I guess we did something wrong :-|.
k8500 said:
It didn't work for me either... FMSecureMode Off and editing nv_default.ini works without trouble. Regardless of any changes, the actual RBM path does stay the same: Changes in the new Rbm path don't show up, and flashing a RC1 with an empty Rbm folder leads to bad graphical errors. Doing the changes via a full flash (nv_original.ini edited and Rbms in SHPAPP or FFS) doesn't change anything either (checked nv_default.ini after the full flash, paths are changed).
Adfree, I guess we did something wrong :-|.
Click to expand...
Click to collapse
+++ I agree Waiting adfree's response
Big sorry, seems false alarm.
Best Regards
adfree said:
Big sorry, seems false alarm.
Best Regards
Click to expand...
Click to collapse
No problem, but that would have been great . BTW, I risked it today and flashed the Android boot loader. No bad consequences so far .
Next attempt... according to this. I made test...
http://forum.xda-developers.com/showpost.php?p=33706880&postcount=247
1.
Created second folder in RC1:
Code:
/System/Rsrc/Bmp/Red/
2.
Changed black folder to red in nv_default.ini
Not working...
Next attempt will be then ShpWindow.so
Maybe I can change to /System/Rsrc/Bmp/Red/ to think about further steps...
Best Regards
Edit 1.
It seems this time more luck with ShpWindow.so.
First succes 2 folders in RC1
Code:
/System/Rsrc/Bmp/Black/
/System/Rsrc/Bmp/Bl[B][COLOR="Red"]o[/COLOR][/B]ck/
Folder Black nearly empty... Block contain whole files from Black.
S8500 starts normal and shows all RBMs...
Now I'll try to change path again to MEdiablablbal...
Best Regards
Edit 2.
It seems ShpWindow.so can only look into RC1 Image...
So it checks System folder only.
Otherwise it jumps to given path by apps_compressed.bin... :crying:
And here I can see only .Rsrc/Bmp/Black/ ...
So I can't here change into /Media/Others/ :crying: :crying:
Best Regards
Related
THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're using the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
DISCLAIMER:
I take no responsibility for anything that may happen to your phone/computer. Use at your own risk.
PURPOSE:
This is for informational/testing purposes. And for people to stop asking, "can somebody port X rom!!! PLZ!!!"
PREFACE:
I made this as a quick tool to port ROMs from the Dream/Sapphire forums to work with our phones. It's a very quick and dirty script I threw together using bash, so there's probably some problems with it. This tool is simply designed to make a copy of the Dream/Sapphire ROM. Once you get the setup, it's really easy and you'll be porting like crazy.
I did this all on Ubuntu 9.10 so things might not work properly if you're using another distro.
THANKS:
All credit goes to the people that made this possible, in no particular order...
dzo, vilord, mssmison, zen, enatefox, pmos, jamezelle, craig0r, cyanogen, and so many more. If I forgot you, I'm sorry, but you know if you helped in some way.
THE SETUP:
1) Download this file
2) Extract the folder to your desktop. Then copy and paste the following code into the terminal:
Code:
sudo mv -f $HOME/Desktop/Android/genext2fs /bin/genext2fs; sudo chmod 755 /bin/genext2fs; sudo dpkg -P squashfs-tools; sudo dpkg -i $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo rm -r $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo chmod 777 $HOME/Desktop/Android/*.build.script
3) Now go into synaptic package manager, search for squashfs-tools, select it and under Package, check Lock Version so that way it won't try to update.
4) Now cruise over to the Dream android development forum or the Sapphire android development forum and download the ROM you would like to port. Place the zip file in the Android folder. (no need to rename)
5) Place any .apk's you would like built into the system in the Apps folder.
ADVANCED SETUP:
If you would like to tweak the system before building, open the script in a text editor and you'll find a line to uncomment that will halt the script until you are ready.
HOW TO RUN:
Either run the script from a terminal
Code:
./$HOME/Desktop/Android/HERO.build.script
or
./$HOME/Desktop/Android/Donut.Build.script
Or double click and Run in Terminal
You will get a prompt for your password to use the sudo command. THIS IS NOT SAVED ANYWHERE OR MAGICALLY SENT TO ME. It is just to get the system.sqsh setup for you to use.
You will now see a Donut/Hero folder inside the Android folder. Inside that will be a nice little system.sqsh with the date ready to boot!
*Rename to system.sqsh when you put on your SD card*
Grab the latest basefiles from vogue-android and you're good to go.
~~~~~~ To get an output of what's happening run in a terminal as described above but add " > build.txt" and you'll see a txt file in the Android folder. ~~~~~~~
CHANGING SYSTEMS:
If you want to port a new rom, replace the .zip.
UPDATES:
1) Download the updates from HERE
2) Extract to the Android folder overwriting if necessary.
3) Copy and paste the following code into a terminal:
Code:
sudo chmod 777 $HOME/Desktop/Android/*.script
CLEANUP:
If you follow the advanced setup and/or accidentally closed the terminal before the build finishes, run the cleanup script. This will unmount everything that might be mounted and delete all folders that are made during the process.
DOWNLOADS:
If you're too lazy or just want a quick link:
Main "Android porting" folder
Updates
Input, testers, bugs, and tweaks to the scripts are appreciated!
FAQ:
Why does my system.sqsh not work?
Most likely cause is that you're not using the correct version of squashfs-tools. You'll have to find version 3.X for the distro you're using. Version 4.X will NOT work!!!
When I try to boot a system.sqsh I just made I keep getting something about android power wake locks. WTF?
You're probably trying to port an eclair or cyan ROM. These don't work at the current state. Hopefully soon I'll get these working.
Will update more when they arise.
CHANGELOG:
11-27-09:
-Created a cleanup script in case the terminal is closed during the build process.
-Bug fixes in Donut and Hero scripts
11-24-09:
-Added an Apps folder for apk's you want built into the system.
-Bug fixes in scripts
11-22-09:
-Combined everything needed into a zip file
-WAY easier to setup
11-20-09:
-Added feedback to make more user friendly
-Append time to system.sqsh
loserskater said:
Input, testers, bugs, and tweaks to the scripts are appreciated!
Click to expand...
Click to collapse
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
garynsa said:
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
Click to expand...
Click to collapse
What did you change?
Glad to see it's working.
loserskater said:
What did you change?
Glad to see it's working.
Click to expand...
Click to collapse
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
garynsa said:
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
Click to expand...
Click to collapse
Make sure you use the genext2fs that I referenced.
That one works with -a and might take care of some issues. try that and see if it works.
Updated script to now move system to a Hero or Donut folder.
Working on the cyanogen build now...
EDIT: Here's a cyanogen script that gets it to boot, but sits at a black screen. I haven't had much time to test it so it might boot further than that if you leave it. If somebody wants to test this out or tweak it in some way go for it.
It uses the donut.sqsh in the Android folder so you shouldn't have to do anything with it except make it executable.
EDIT 2: Still working on cyan builds... that script didn't work.
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
jamezelle said:
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
Click to expand...
Click to collapse
Good point, forgot to mention that. Updated first post.
I'm hoping it will help people start to learn to tweak system's. But I have a slight feeling wer're going to start seeing a lot of "MLIGN/DWANG/etc's Android Rom" threads from random people.
Hi
Was able to port the DWANGs build using your script. Thanks a lot for making life this simple. Howev3er, hero build is still not working. Tried your genesxt2fs. Is it possible to get the links to correct base hero version to use? I tried magic and normal version. It keeps giving me black screen and doesnt completely boot. I think the base hero version is not the right one i am using
Thanks
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
loserskater said:
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
Click to expand...
Click to collapse
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
garynsa said:
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
Click to expand...
Click to collapse
Glad to see its working. Thanks for the feedback!
Most things working
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
garynsa said:
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
using u
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
Click to expand...
Click to collapse
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
loserskater said:
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
Click to expand...
Click to collapse
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
garynsa said:
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
Click to expand...
Click to collapse
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
loserskater said:
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
Click to expand...
Click to collapse
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
garynsa said:
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
Click to expand...
Click to collapse
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
loserskater said:
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
Click to expand...
Click to collapse
Android folder... but its not a big deal as one can easily change it while startign the script
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.
heartsurfer008 said:
Well I am desparetly trying to cook a NAND build for my HD2 but there is pretty much less info available for me [a big NOOB in cooking] to try out my luck at cooking..!!!
So I'll appreciate if someone would put some light on it..!!!
PS: - I would appreciate if somebody can provide a detailed info..!!!
Click to expand...
Click to collapse
Finally the tutorial
Make your own Android Build for the HD2 by domineus I have always lived by these words- if you give a man a fish, he can eat for a day; but if you teach a man to fish you can eat for a lifetime. Android on the HD2 has always been an interesting thing for me and I know a lot of people that want to create their own builds, but have no idea how. If you ask a build creator or maybe someone in the htc-linux-chat how to get started, there may not be an answer. In fact, some of the perplexing behavior has left me puzzled in several ways - as if how to get an android build is a vaulted secret of knowledge like the holy grail. To be honest, it's not. It's a bit of hard work, a few nods in the right direction, and ultimately it's a community involved project. Just like miui development is a community project spanning actual continents to get this thing on our device every single week! It has led to a lot of questions, in my inbox, of how to begin. For a long time, the answer to the question was not answered until Cass helped me out. I want to do the same and contribute how to get a build of miui (or any android build) to the HTC HD2.
Things you will need
In order to properly start android development, it would be a good idea to make sure you have the following (a lot of it is no duh when you think about it)
A computer running linux
I can't stress that enough. While there is a lot of things you can do in windows, you will need some sort of linux distro in order to get android properly running on your HD2. There are a lot of linux distros you can use; with many using ubuntu as it is the most user friendly. I use Fedora and I am quite happy with the results. It's simple and effective. It gets the job done. Get a distro that you feel can get the job done.
Android SDK - either windows or linux
Android SDK is something that can be freely accessed and downloaded from the following location:
http://developer.android.com/sdk/index.html
It is a developer environment, but probably the most important thing you can use here (for the time being) is logcat. Logcat provides you to visually see the libraries and files working together to get android to work as well as if you run into an issue, it is the first thing you should resort to. For instance, boot reloop? Take a look at your logcat and try again.
A kernel
There are quite a few kernels available for android previously and they are divided into evo kernel or nexus one kernel. Many builders have transitioned to an evo kernel for PPP and a few other nice details but it is totally up to you. I highly recommend hastarin's kernel. For most of the time, it works well. But as you have noted, on MIUI, it hasn't been working as fantastic on other builds.
Donor Files
This is a bit difficult to find because it appears that the files that work best are nexus one builds without CM6.1 modification. So far, only one chef has that and it is tytung's nexus one build. Regardless of whose files you're using (e.g. tytung or darkstone's system which is the preferred choice) you will need a well working android build. You will be pulling several files in order to port.
MIUI itself (well any build honestly just miui is a good example)
This is a given. However, if you download from miui.com you will probably have an untranslated rom with odex files. That's bad. And in Chinese! It would be a good idea to browse the English forum for a deodexed rom with appropriate english translation (apps and frameworks)
-If pulling files from windows, you will need this
system extractor
http://uranus.chrysocome.net/linux/explore2fs-old.htm
I use that if I download in windows. It's relatively straight forward and it allows you to pull the files you need from the system.ext2 you're using and copying them to folders necessary.
build.prop
This you will need. You can find one here:
http://www.multiupload.com/B59IU3S6XY
Patience
Probably the most important thing. One thing I have noticed is you need patience to make it through. Sometimes, your build works, sometimes it doesn't. And it is difficult to still keep going. But gotta pull it all in and keep trying...it does pay off.
Okay so you have your files, a nice linux distribution, your build you want to port (MIUI preferrably) and you're ready to go. Now it's time to begin the process!
Step One - The Setup
I usually grab my files in windows before transitioning to my linux distro to finish the process. If you using windows 7 and you are using explore2fs, you will definitely have to right click on the exe and make it compatible by selecting compatible with windows vista. The file should also need to be run by administrator. If you don't know how to do that you can google compatibility in windows 7.
First thing is first. Create a new folder, you can call it donor_files if you want because name is arbitrary. The most important thing is to just name it. Within that folder, create a new folder called system. Enter the system directory and create a new folder called etc. Within etc, select Once that is done, create a new folder within etc called firmware. Once completed, return back to the system folder, create the folder called lib. In the lib folder, create a new folder called hw. So your folder should look like this:
Folder Name
-system
--etc
---firmware
--lib
---hw
So far so good? Excellent. Now, if you're in windows you will need to do a few things. Extract the system.ext2 of your donor build and place it somewhere you will remember (like your desktop). Now open up explore2fs, select file, and open image file. Under files of type (drop down), select all files and navigate to your system.ext2 file. You should now see the ext loaded on the left side of the program's workspace. Located is a very small + that allows you to view all directories in your ext2 file. Click that.
You will see several system folders on the left and files on the root. Since you haven't selected a specific folder, in the right hand view, you should see the file build.prop. If you did select a folder (like app) you will see some files. And that's okay too. Get a feel of the program.
Now you will do a test file pull. On the left hand side, select the folder etc. On the right window, you will see several files. We want AudioBTID.csv. Once you see the file, right click on AudioBTID.csv and select export file. Navigate to the donor file folder (or whatever you named it) and place the file in system/etc of that folder. Congratulations you just pulled your first file! But you will need a lot more files. Within the same directory, pull gps.conf, hosts, media_profiles.xml and the ppp folder. Now, navigate to firmware and pull the following files:
BCM4329B1_002.002.023.0360.0362.hcd default_france.acdb htcleo.acdb
BCM4329B1_002.002.023.0436.0439.hcd default_nel.acdb yamato_pfp.fw
bcm4329.hcd fw_bcm4329_apsta.bin yamato_pm4.fw
default.acdb fw_bcm4329.bin
Ideally you should not be able to find htcleo.acdb. You can find it here
http://gitorious.org/xdandroid_leo/q...eo/htcleo.acdb
Now in explore2fs, go to the lib directory and pull these files and place them in your lib directory:
libcamera.so
libcamera_client.so
libcameraservice.so
libhtc_ril_wrapper.so
libmm-omxcore.so
liboemcamera.so
libomx_aacdec_sharedlibrary.so
libomx_amrdec_sharedlibrary.so
libomx_amrenc_sharedlibrary.so
libomx_avcdec_sharedlibrary.so
libomx_m4vdec_sharedlibrary.so
libomx_mp3dec_sharedlibrary.so
libomx_sharedlibrary.so
libomx_wmadec_sharedlibrary.so
libomx_wmvdec_sharedlibrary.so
libOmxCore.so
libOmxVdec.so
libOmxVidEnc.so
libqcomm_omx.so
libstagefright_omx.so
Once those files are pulled, navigate to the hw folder of the system and pull the following files:
sensors.htcleo.so
lights.htcleo.so
Once those files are pulled, you can save your donor files to a flash drive and then boot into your linux distro. Login to superuser in terminal. For fedora, the proper method involves typing in su --login and entering your password you set up. Minimize your terminal window.
Extract the miui (or any other build) to your desktop (the focus is the system folder). Ensure the rom is deodexed and in your own language (if its miui, you will have to apply the proper language translations). Now copy the files you pulled from your donor build and apply it to the appropriate folders (usually a copy and a paste-literally). In this instance there will be duplicate files, overwrite them. That's the point! Do not forget the build.prop file I linked to earlier. You should add that to system folder.
So the files are copied, the next step is to restore the minimized terminal window (the one that is logged in as root). cd to where your system is located (not to the system folder itself). Now you will have to enter the following commands in terminal
chmod -R 777 system/etc
chmod 755 system/bin/*
chmod 755 system/xbin/*
rm system/etc/firmware/default*acdb (if you have sound in call issues)
touch system/etc/ppp/active (If you have latest wrapper and need ppp)
chown root:2000 system/bin/pppd
chmod 4755 system/bin/pppd
chown root:root system/xbin/su
chmod 4755 system/xbin/su
chown root:root system/xbin/hci*
chmod 4755 system/xbin/hci*
dd if=/dev/zero of=system.ext2 bs=1048576 count=256
mke2fs -F system.ext2
sudo mount -o loop system.ext2 /mnt2
cp -rp system/* /mnt2
sudo umount /mnt2
A few words on this that I must bold. the /mnt2 directory may not exist. If not, try mnt, that usually works
Once this is done, you will have a nice system.ext2. The only thing you'd need now is a rootfs, a kernel, clrcad.exe and a startup.txt file. Once that is done, you can test your build out.
Any questions
Special thanks to Cass and the htc-linux-chat for the few pointers they gave me.
The guide is by "domineus - http://www.miui-dev.com/" & I take no credit what so ever
Thanks to "white-energy" for giving us the link..!!!
Hope to have many more Chief's for our HD2, so that we [especially me] can satisfy our hunger to try different builds/ROM's..!!!
Happy Cooking..!!!
PLEASE PRESS THANKS IF YOU FOUND THIS THREAD USEFUL..!!!
+ 1... nobody wants to share information?
I don't know if this help but you can try
http://forum.xda-developers.com/showthread.php?t=897940
These kind of thread pop up once in awhile, but it's going no where, I've never seen well known chef show up in this kind of thread.
knowledge is power, maybe they dont want to share the power
Can anybody out there give us a step by step guide for cooking a NAND ROM for HD2..???
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Thank you, please check post 1..!!!
I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.
velayo said:
I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.
Click to expand...
Click to collapse
I was lookin for the same & credit goes to domineus & white-energy
& "white-energy" comes up with a NAND ROM..!!!
Congrats..!!!
white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Are you sure its the only difference? Are the nand drivers stored only in the bootimg/initrd and not somewhere in the system.img?
yes or no will do for me thx
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
i am confused
Which explore 2fs do I download? There are 3 different ones one for binary one for code and optional update source code. I am a noob and tired of not having roms I am happy with. I have windows 7 and xp. I realize this will take time and I am good with it everything thats worth anything takes time.
deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
anyone know how to edit or anything about initrd.gz?
hnamanh said:
anyone know how to edit or anything about initrd.gz?
Click to expand...
Click to collapse
It's an archive that can be decompressed and edited thru linux.
White-Energy use system.bin in his rom
Regarding initr and zimage, there is a guide that you can point me on ?
Thank you
KillaHurtz said:
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
Click to expand...
Click to collapse
I have only green HTC
Hello
I would like to use Android on my HD2. I was searching and testing many ROMS but I didn´t find any rom which is usable for me. I would like to have a ROM that is without Sense, has Multilanguage support and is on Android 2.2 version.
So I decided that I would make my own.
0) I was reading
HTML:
http://forum.xda-developers.com/showpost.php?p=10291851&postcount=1
and made this procedure.
1)downloaded some ROM from here
2)unpacked this rom in linux with :
Code:
unyaffs system.img
then I got this directories:
Code:
app bin build.prop etc fonts framework lib media usr xbin
3)I downloaded update-cm-6.1.1-N1-signed.zip from CyanogenMod Forum > Downloads > Stable Mod > Nexus One and unpacked. I got : META-INF system boot.img.
4)I copied everything what was described step 0 from directories from step 2 to directory system from step 3
5)I downloaded and copied build.prop from step 0 to system
6) I updated permition like it is described in step 0
7) I created system.img with command : mkyaffs2image . ../system.img
Then I copied this system.img from linux to my windows and put this file in directory in which was different NAND rom. (replaced system.img). After that I flashed my phone and it did not work. Screen was frozen after booting and only green HTC was on display.
Can somebody please help me and give me some advice or some small howto. Does anybody know what can be wrong?
Thank you
Michal Fichtner
I appreciate the guide but damn that is hard to read. It really needs some sort of structure to it, titling proper paragraphs etc.
Hi,
it is possible to combi the dropdown energy widget froom miui and the gingerbread lockscreen into Desire HD Build?
Thats was awesome !
Sorry for my bad english
So, it seems that more people are taking an interest in making custom frameworks. This isn't really a full tutorial, but I thought it would be helpful to just post some tips on how to go about making your own framework-res.apk, save others a bit of time retreading old ground, since the methods are scattered around the site a bit!
Thanks to wdl1908 for prompting me to do this - should really have done this sooner!
Okay, so basic requirements:
Rooted Gen 8 (Uruk or chulri method)
Original Archos framework-res.apk
zip editor
image editing software
.png's to replace the stock ones with
That's about it! I've been using GIMP on Ubuntu for the image editing, and Phatch for batch resizing, but Photoshop will work just as well on Windows.
Edit: Thanks to wdl1908, have found that Gwenview gives much better results when resizing, compared to Phatch or GIMP. Works on both Ubuntu and KDE.
Use your preferred zip editor to unzip the contents of framework-res.apk to your chosen folder. The main folder of interest is "drawable-mdpi".
The Gen 8's use MDPI resolution images (well, A70 and A101 to at any rate. I think someone mentioned the A32 or A43 used HDPI images). Depending on your .png source, you may need to resize the images. I took my images from themes made for the Desire, which is an HDPI device, so I used GIMP/Phatch to resize them.
In terms of resizing, I compared the size of each new png with the original one, and resized. I know p0rkburn just resizes the images to 66%, but I've had problems with some images not coming out the right size that way. The other thing to watch out for is that not all the images need resizing. Also, some of the textfield and tab_select images are different proportions to their phone equivalents, so again watch out for that.
Once you've replaced the images you want to, they need to be put back into the .apk. I used to copy and paste into the framework-res.apk, but that doesn't work for 9patch files. Also, wdl1908's FrameWorkBuilder makes the compile process so ridiculously easy, there is no reason not to use that instead.
To put the new framework-res.apk on the device, I use this method via ADB wireless, which works fine.
Happy theming!
EDIT: 9patch files
These can be a PITA, until you understand how they work. I used the following two sources to finally crack it :
http://developer.android.com/guide/developing/tools/draw9patch.html
http://forum.xda-developers.com/showthread.php?t=580351
If you are changing 9patch files, you have to decompile and recompile using the FrameWorkBuilder.
I prefer using the draw9patch tool, as it lets you check that the 9patch works as expected.
Spent enough time bashing my head against a brick wall trying to sort out 9patch files, so if I can spare anyone else that, feel free to post/PM..
I'll leave this post here for my recommendations that will be more complex when you need to modify xml files.
In short the procedure is a follows (this needs to be expanded)
unpack the apk to framework-res-UNPACKED dir
decompile the apk to framework-res-DECOMPILED (with apktools)
copy framework-res-MOD to framework-res-DECOMPILED
compile framework-res-COMPILED (with apktools)
unpack the compiled apk to framework-res-COMPILED (with 7za)
remove all the files that are present in framework-res-MOD from the framework-res-UNPACKED dir
remove the file resources.arsc from framework-res-UNPACKED
copy all files from framework-res-UNPACKED to framework-res-COMPILED
zip all files in framework-res-COMPILED to the new framework-res.apk
remove the resources.arsc from that apk file
readd the resources.arsc file without compression to the new apk file
Done
The reason this is so complex is that their are bugs in apktools and the signature needs to be preserved.
FrameWorkBuilder v0.3
README.txt
-------------------------------------------------------------------------------------------------------
Place the script FrameWorkBuilder.sh in a directory and execute.
The script will download all the needed tools.
Place framework-res.apk in the dir framework-res-STOCK
Place mods in framework-res-MOD follow the usual directory structure.
Example:
framework-res-MOD
framework-res-MOD/res
framework-res-MOD/res/drawable-hdpi
framework-res-MOD/res/drawable-mdpi
framework-res-MOD/res/drawable
Execute FrameWorkBuilder.sh to apply the mod.
Modded framework-res.apk will be stored in the directory framework-res-MODDED.
-------------------------------------------------------------------------------------------------------
Changelog
-------------------------------------------------------------------------------------------------------
v0.3 Added xml png duplication check to avoid that animations don't work. .9.png support
v0.2 Added mod checks Added compile failure test
v0.1a BUGFIX cp dirs
v0.1 Initial version
-------------------------------------------------------------------------------------------------------
Have fun modding.
wdl1908 said:
I'll leave this post here for my recommendations that will be more complex when you need to modify xml files.
If you don't mind we'll make it a joined tutorial. I have no time now it's time I got some sleep.
Click to expand...
Click to collapse
I have no idea about editing XML files, but that was the next thing on my "To learn" list. I would be very happy for you to add your knowledge to this thread.
Also, if anyone has info to add/corrections to make, please feel free.
Good stuff, guys. At the very least we can make this a three man party.
The more the merrier!
Guys, can I ask what device you're both using?
fisha21 said:
Guys, can I ask what device you're both using?
Click to expand...
Click to collapse
A101IT with archangel root
A70IT with chulri's root
fisha21 said:
The more the merrier!
Click to expand...
Click to collapse
well, if i can do something, i'm here ;-)
wdl1908 said:
A101IT with archangel root
A70IT with chulri's root
Click to expand...
Click to collapse
Cool, thanks. Also, can I ask how you're viewing the XML files? Every program I've tried won't open them - keep getting error messages about invalid character content.
woti23 said:
well, if i can do something, i'm here ;-)
Click to expand...
Click to collapse
Welcome...
fisha21 said:
Cool, thanks. Also, can I ask how you're viewing the XML files? Every program I've tried won't open them - keep getting error messages about invalid character content.
Click to expand...
Click to collapse
You have to decompile the framework-res.apk with the apktools then all is revealed.
I have an A43it, and I find it to use a mixture of the hdpi and mdpi drawables, it is quite odd how they have it. I am drawing this conclusion because I only changed the hdpi drawables, and some things (status bar pull down for one) stayed original. I am going to work some more on it later today and will update here. My method for pushing to the device uses adb like such:
Code:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk (only needs to be done the first time, as the permissions will adopt those when replacing in the future)
start
This causes the device to do a little soft-reboot (does not perform a proper full shutdown/reboot) that is pretty quick, and avoids any f/c situations you may encounter replacing the file while the system is live.
Edit 2 - ok, I just plain old missed the drawables earlier, they are all in hdpi for the A43. Posting screenshots of what I have put together shortly.
daveid said:
My method for pushing to the device uses adb like such:
Code:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk (only needs to be done the first time, as the permissions will adopt those when replacing in the future)
start
This causes the device to do a little soft-reboot (does not perform a proper full shutdown/reboot) that is pretty quick, and avoids any f/c situations you may encounter replacing the file while the system is live.
Click to expand...
Click to collapse
Great I was looking for that.
wdl1908 said:
[*]compile framework-res-COMPILED (with apktools)
Click to expand...
Click to collapse
Getting stuck on the above step. Have got a folder called framework-res-DECOMPILED. When I try to compile it, the first message I get is:
Code:
w:Could not find sources.
It then runs through the process throwing up multiple error messages, and at the end I am left with an empty Build folder. Any ideas? I read on the Apktool thread that you need to add a classes.dex file to apk that don't already have one?
Thought I'd try your method as my primitive version keeps resulting in faulty apk's the last day or two!
fisha21 said:
Getting stuck on the above step. Have got a folder called framework-res-DECOMPILED. When I try to compile it, the first message I get is:
Code:
w:Could not find sources.
Click to expand...
Click to collapse
No problem there thats only a warning.
fisha21 said:
It then runs through the process throwing up multiple error messages, and at the end I am left with an empty Build folder.
Click to expand...
Click to collapse
What error messages?
fisha21 said:
Any ideas? I read on the Apktool thread that you need to add a classes.dex file to apk that don't already have one?
Click to expand...
Click to collapse
What version of apktools do you have?
never needed any classes.dex in framework-res.apk
fisha21 said:
Thought I'd try your method as my primitive version keeps resulting in faulty apk's the last day or two!
Click to expand...
Click to collapse
I'll try to cleanup my script and post it soon.
I just found out we can have custom boot animations on our gen 8 devices.
search for some bootanimation.zip on the web or go to UOT Kitchen and download one from the kitchen. place it in the directory /data/customization/ and reboot. This works even for the stock firmwares with archangel root.
Enjoy
I've added the first version of my FramWorkBuilder script in the second post.
wdl1908 said:
I've added the first version of my FramWorkBuilder script in the second post.
Click to expand...
Click to collapse
Thanks for the hard work!
Gave it a run through but get the following error messages:
Code:
Applying MOD...cp: cannot stat `/home/sarju/FWB/framework-res-MOD/*': No such file or directory
and
Code:
Copy files from UNPACKED to COMPILED that are not modified...cp: cannot stat `/home/sarju/FWB/WorkSpace/framework-res-UNPACKED/*': No such file or directory
The script is located in the "FWB" folder.
fisha21 said:
Code:
Copy files from UNPACKED to COMPILED that are not modified...cp: cannot stat `/home/sarju/FWB/WorkSpace/framework-res-UNPACKED/*': No such file or directory
The script is located in the "FWB" folder.
Click to expand...
Click to collapse
yeah download the 0.1a version and try again.
wdl1908 said:
yeah download the 0.1a version and try again.
Click to expand...
Click to collapse
Ok, think I'm just being stoopid here. Ran the v0.1a, no error messages BUT
If I use the folder structure "framework-res-MOD>drawable-mdpi", the resulting apk just has the original contents of drawable-mdpi. If I use "framework-res-MOD>res>drawable-mdpi", the resulting pak has an empty drawable-mdpi folder.
fisha21 said:
Ok, think I'm just being stoopid here. Ran the v0.1a, no error messages BUT
If I use the folder structure "framework-res-MOD>drawable-mdpi", the resulting apk just has the original contents of drawable-mdpi. If I use "framework-res-MOD>res>drawable-mdpi", the resulting pak has an empty drawable-mdpi folder.
Click to expand...
Click to collapse
the structure should look like this.
Code:
framework-res-MOD
framework-res-MOD/res
framework-res-MOD/res/drawable-hdpi
framework-res-MOD/res/drawable-ldpi
framework-res-MOD/res/drawable-mdpi
framework-res-MOD/res/drawable
but make sure you remove empty dirs.
I suspect it has to do with empty dirs I'll check that....
Nope tthats not it.
can you zip up the files files-to-remove.txt and log.txt in the WorkSpace dir and post them or via pm if thats possible.
Hi everyone
you know that a big problem of upgrading using multiloader is that all of applications and our data will be deleted due to a firmware upgrade
*This method is found by mylove90 so all credits goes to him
special thanks to mylove90, adfree, and everyone who have helped this developement
Upgrading using this method is by using "PFS" file like kies upgrades
1. first you should prepare two firmwares, one is the firmware which is installed on your phone and the second is the firmware you want to upgrade to
2. Then you need to extract files of the new and the old firmware so download Trix, Select input file (You can make PFS file from a mix between FFS , ShpApp , CSC (Not Rcrs compressed part)) but just FFS is enough
then go to "scripts" tab and select "fs_shell.trx" and add it then run the script and ...
3.then download Winmerge (google it!) its an open source application which compares two files or folders with one click
then compare the new firmware folder and old firmware folder
then in view tab choose the files we want for upgrading
4. the files which are needed are "Different files" and "Unique files" from new firmware, so copy them to a new folder
also the "unique files" from old firmware must be deleted so "copy path names" and change path names to the correct pattern ex:"/appex/sys/blabla"
5. we can delete these files during PFS upgrade by adding the file paths to "/debug/PfsDeleteList.txt" file which we'll include it in our PFS
5. every thing is done
now just download wave_remarker and in FW view select "open dump" and select the files which we put into a new folder!
make a new folder named "debug" and put a txt file named "PfsDeleteList.txt" which contains the path of files which should be deleted during pfs upgrade
then save file as PFS
6. open multiloader and first check "boot change" and flash the new firmware's boot files
then again flash other firmware files (which does not contain FFS, CSC, shpapp (just the files which you extracted)) and includes pfs file
*note that no checkboxes in this level should be checked in multiloader
Thanks I will test this method
I have some questions from who have made this method
when i try dumping just FFS and making pfs of that in flashing it says error: shpapp write
when i try dumping FFS and Shpapp it says error: csc wite
when i try dumping FFS and shpapp and csc it says error: pfs write
edit
for deleting extra files i try putting all file paths into pfsdeletelist.txt
should i use _CSC_FsDeletelist.ini for some of them?
Sorry
I got no clue what you did wrong
Never tested the update from bada 1.2 to 2.0
Best Regards
when i tried bada 2 to bada 2 upgrade
everything was ok but at the end it says CMD_USB_LOCK fail
i could successfully turn my phone on but after some seconds a blue screen appears and it says:
platform "so" checking is failed
Platform "so" modification is detected!!!
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
platform "so" checking is failed
Platform "so" modification is detected!!!
Click to expand...
Click to collapse
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
mylove90 said:
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Click to expand...
Click to collapse
adfree said:
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
Click to expand...
Click to collapse
I havent touched .so files ever
but as this is a custom rum which i want to upgrade to maybe the problem is here
so i try upgrading to another fw
in learning these things nothing else is important for me
i have backup of my apps that are important for me
so i try everything with your help
I havent touched .so files ever
Click to expand...
Click to collapse
This Error message is for wide range of Security issues...
Only if you enable Debug Level to see Blue Screens for more details...
Example for Blue Screen is attached...
1.
Post your Blue Screen...
Maybe we can help you...
2.
Or upload your files.
MAYBE someone has time to check...
Maybe with password and password only via PM, to prevent noobs to kill their handsets...
3.
To add any other Apps is not good idea... also leads to fail...
Security HIGH
Best Regards
Now i have full flashed to another rom so i dont have that bluescreen to post it for you
but bluescreen is showing just that 2 lines i wrote
first of all i'll try another fw to upgrade to
maybe the problem was with this fw
if again i failed, i'll try to upload my files (cuz my internet speed is very low!!)
Oh WTF i think i've found the problem
when i make a pfs using wave remarker then i add it into multiloader, it writes s8500 in front of pfs
but my device is s8530
how can i solve this problem
i havent seen such settings in wave remarker
i myself found a solution for this and made a correct pfs
but again multiloader says CMD_USB_LOCK fail
I think the best way for me is to make a video of what i do yes?
and someone do me a favor and kindly check whats my fault
I'll make a video in the next days
but again multiloader says CMD_USB_LOCK fail
Click to expand...
Click to collapse
Depend what you did... you could ignore this from Multiloader...
I see this Info often if I play with my modified apps_compressed... or do other stuff. Then Autorestart not work with Multiloader...
Try to press ON OFF... (hold Button to force Restart)
At your own risk.
Not during Bootloader write.
Best Regards
I have encountered this error while using modified apps_compressed and rebooting was fine
but in this case when i try to reboot i see the blue screen or the handset stops on the first screen:
"WAVE 2 S8530"
"WAVE 2 S8530"
Click to expand...
Click to collapse
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
adfree said:
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
Click to expand...
Click to collapse
Thank you but you didnt understand what i mean !!
i said i see this error while editing apps_compressed too
but in this case i'm not doing that but again i see this error
this is the video of all i do:
http://dolphintest.co.cc/video.rar
i want to make a pfs for upgrading from JPKA1 to XXKL6
here i encounter error: pfs write
if you can't understand a part, mention here
Please check the video so we can solve my problem!!
video is just 10 mins so it doesnt take so much time
JPKA1
Click to expand...
Click to collapse
XXKL6
Click to expand...
Click to collapse
This is bada 2.0... I'm sure, I used often...
But is JPKA1 not bada 1.x
You can't mix bada 1 with bada 2...
Please correct me, if I'm wrong.
Best Regards
yes your right
but why we can't upgrade from bada 1.2 to bada 2?
by the way i've tried bada 1.2 to bada 1.2 upgrade and bada 2 to bada 2 upgrade but same problems
but why we can't upgrade from bada 1.2 to bada 2?
Click to expand...
Click to collapse
Samsung did some funny things...
"New" Bootloader, new Memory Map...
Compare adresses in Multiloader... so NOT same position...
So major changes... maybe not impossible for Samsung to convert some...
Anyway. Its Security reason and to have "clean new" OS.
Maybe also to clean all Spoofer...
I have not seen whole Video...
No idea yet.
Maybe someone else...
Best Regards