Related
You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
There is another image that appears just before the image that has the number of rom and radio.This can be changed if you replace the 601 with 600 in the parameters described above (tip goes to Chri55tof in post 2).
So you just need 2 bmp photos 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy
Downloaded the file (from link you provided), made a 24bit .bmp file I wanted to use ... followed the command line, flashed to my HD2 and it works !!
Great job !
K.
EDIT :
By the way, flashing .nbh file done that way will replace 2nd splash screen. How to replace first screen ? (the one with white background and green htc trademark) ???
EDIT2 :
Just found it !
0x600 is changing 1st splash screen
0x601 is changing second (not like you stated in topic of this thread !)
What you mean ?
The second screen is the animation which is an animated gif file.
-T is the header type.
I attach the kind of settings:
Mandatory arguments:
-F <filename> Filename to convert.
If the extension is BMP it will be converted to NB.
If the extension is NB it will be converted to BMP.
Optional arguments:
-w <width> Image width in pixels. If not specified will be autodetected.
-h <height> Image height in pixels. If not specified will be autodetected.
-t <pattern> Manually specify the padding pattern (usually 0 or 255).
-p <size> Manually specify the padding size.
-n Do not add HTC splash signature to NB file.
-s Output smartphone format.
NBH arguments: (only when converting from BMP to NBH)
-D <model_id> Generate NBH with specified Model ID (mandatory)
-S <chunksize> NBH SignMaxChunkSize (64 or 1024)
-T <type> NBH header type, this is typically 0x600 or 0x601Example to convert a NB to BMP:
I mean `the very first screen`
This is the one with white BG and green `htc` trademark (the one before `reds` coming out)
0x600 is responsible to change this
0x600 next splash screen
Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?
pepesz said:
Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?
Click to expand...
Click to collapse
The sound is the HTC-QuietlyBrilliantBoot.wav in windows folder and the original animated gif (LEO_animated.gif) also in windows folder is attached
Read here
http://forum.xda-developers.com/showthread.php?t=625911
Thanks a lot
0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)
chri55tof said:
0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)
Click to expand...
Click to collapse
You dont have to do the procedure for changing the welcomehead,bmp because you just replace directly in windows file or cook the bmp file.
The 1st screen with the red letters at the bottom with radio and rom numbers needs to be flashed as is the only way to replace it.
My little contribution ^^
Enjoy !
NIKOSXRI said:
You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
So you just need a bmp photo 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy
Click to expand...
Click to collapse
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?
daleandla said:
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?
Click to expand...
Click to collapse
Check again and follow the command line exactly
My Contribution
NIKOSXRI said:
Check again and follow the command line exactly
Click to expand...
Click to collapse
Boom baby. Got it. Here's my contribution...
How do change from second splash screen. (Not the first screen or bios animation)
technomania34 said:
How do change from second splash screen. (Not the first screen or bios animation)
Click to expand...
Click to collapse
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.
is there anyone that has the original 2nd splash bmp file or as a nbh file?
Found it
NIKOSXRI said:
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.
Click to expand...
Click to collapse
Thanks mate
why isn't this or a link to this thread (or similar) in the sticky/wiki at the top?
A word of warning. when you create and flash a splashscreen using the 0x601 memory location, it is not removed when you flash a stock rom. (Tested with several stock roms)
Stock splashscreens are flashed to the 0x600 memory location, and shows for 14 seconds. 7 Seconds when teh phone boots, and 7 seconds when the RGD info shows.
When you have a second splash in place, it shows the first splash for 7 seconds, then the second splash when the RGD info shows for 7 seconds.
The implications of this are that if you need to send back your phone, and you flash a stock rom, your custom second splash will still show.
To remove it (well, make it look like it was gone) I had to make a duplicate of the stock splash and flash it to the 0x601 location, so that it looks like one long splash. (As i found out when i had to return mine to o2.)
More reading
[1st boot & 2nd splash ]
4 HD2 Leo :: choose your BMP shot for it
HERE
Okay, folks this is my first tutorial on xda. I am a loyal member that gets most of his info from searching and rarely needs to post. But, I just spent the last few hours figuring out how to install a specific font. I thought I would compile that info here so it is a lot easier for folks in the future.
You will need:
-Basic understanding of cmd and adb
-A file called UnSigner.exe (thanks baniaczek http://forum.xda-developers.com/showthread.php?t=329160)
There are many free fonts you can find online and for many of them you will not need to follow the directions pertaining to UnSigner. For the sake of this tutorial, lets assume you want to use a font from windows. You should pick 2 variations of the same font file; one for regular and one for bold.
1. Find the font file. On Windows 7, C:\Windows\Fonts
2. Copy the font file to a folder on your desktop called "Fonts"
3. Download and extract UnSigner.exe to the same folder called "Fonts". Download from the link above.
Now, in the Fonts folder you should have the desired font file(s) and the UnSigner.exe.
4. Rename the font file(s) to DroidSans and DroidSans-Bold, respectively.
5. Open cmd. In Vista and above; hit windows key, then type "cmd". Right click on "cmd" & run as administrator.
6. Change directories to the Fonts folder on your desktop.
Code:
cd c:\users\NAME\desktop\fonts
7. Run the UnSigner.exe on the desired font file
Code:
UnSigner.exe DroidSans.ttf
(Repeat for every font file desired)
For the following you should be in Unrevoked Recovery and already have made a backup.
8. In command prompt, start adb shell
Code:
cd c:\sdk\tools
adb shell
9. Mount system directory on your phone
Code:
mount /system
10. Copy font file from your sd card to the system directory overwriting the current one
Code:
cp /sdcard/DroidSans.ttf /system/fonts/
*It may be wise to backup the current fonts before overwriting them. I never worry tho, because every ROM has them & I can just pull it out and do the above for them, too.
(Repeat for every font file variation)
Tips: I use a light variation of the font for DroidSans.ttf & the regular variation for DroidSans-Bold.ttf, Clocktopia.ttf, gcsh00d-hkscs.ttf, & ucsh00d_c.ttf. The last two are the htc fonts in the widgets and such, I think. Also, a font file degrades with each copy that is made. It is best to make one copy of each font file desired and then rename them accordingly.
Have fun!
Or you could just put them all in one folder named fonts in sdk and adb push to system/fonts. That way you don't have to do all of them individually. Just my 2 cents.thanks for the tutorial though.
coolingout said:
Also, a font file degrades with each copy that is made.
Click to expand...
Click to collapse
Wut? Doh, the unsinger requirement. Even that should only make a difference the first time it's run on a file. Running it again shouldn't modify the file any more -- anything else is a bug.
Do you have links to any fonts that this actually does something with?
I installed Microsoft's Calibri, Cambria, and Consolas fonts (the Windows 7 versions) on my phone w/ Type Fresh without using that and they work fine. (Looks awesome too!)
I tried running unsigner.exe on those and some other fonts I had on my system that the font viewer say have digital signatures and it didn't modify them at all. They have the same MD5 hash.
First time doing a splash screen hope you guys like it...
ADB:
if you have your evo connected to pc just do the adb on cmd or reboot to bootloader.
cmd:
then type: adb reboot bootloader
then type: fastboot flash splash1 evosplash1.rgb565
then type: fastboot reboot
In a Zip file
Great splash screens. I added it to a zip file and loaded it that way.
Zip File is named PC36IMG.zip, upper case like this. In the zip is a text file and the the splash screen.
Rename the splash screen to splash1.img (for example I renamed evosplash1.rgb565 to splash1.img in the zip.)
The text file is named "android-info.txt" and contains the following:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.26.651.6
hbootpreupdate:3
DelCache: 0
DelUserData:0
The text file is in the attached zip.
Boot to the boot loader - holding down VOL Down and Power on buttons. Answer yes to install.
And your splash screen is there!!!
You can build them on the PC and email them to the EVO!!!
How do yout create your own splash screen? I created a jpg on photoshop with 480x800. How what?
Sent from my PC36100 using Tapatalk
You will probably need to delete the original files and upload your jpeg. Your phone should know what to do.
soulassasin187 said:
How do yout create your own splash screen? I created a jpg on photoshop with 480x800. How what?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
if you want to create your own splash screen. its really not that hard once you get it. first i use photoshop cs5 to make my splash screen 480x800 then save as bmp 24bit then you will be needing a program called nbimg once you have that extract it put your bmp image on the folder then on your pc go to run>cmd>type>cd "drag wherever you put the folder" and your done.
Hey there,
This is a guide on How to create a ROM
For boot sound, boot animation and themeing
Installing cygwin and Setting the kitchen up!
Finalizing , de-odexing, additional option and packing the ROM
Things you will need
-Cygwin
-Android Kitchen
-Patience
-Base ROM
--All files attached at the end--
-MagicISO
PS-> WIndows 7 users set the UAC level to minimum until you finish the whole thing. And also, make sure that nothing wxcept the META-INF folder in your ROM ins capital in letters! Just a small obseravtion in my third ROM! =P
First of all, let us extract the ROM files:
As you can see, In the folder of the XXKPH ROM, you have a system.rfs file. Copy that out to a seperate folder. In case, of any other base ROM, you can find it in the PDA file.
Now use MagicISO in order to extract the system.rfs into a seperate folder!
After that, you may find something with folders like, : app, vendor,etc,media and xbin.
Adding your apps!
Step 2
You are done with the first step!
Now, rename the folder where you have extracted system.rfs to “System” (without quotes) and move it to another folder. Call the new folder as “Custom FW”. Now create a folder called data, in which you create a sub-folder “app”. All the apps what you want to be pre-installed and can be deleted by the user go in here. (only .apk format). If you want apps which the user can not un-install, put the .apk in system/app.
Step 3
You may want to add custom boot sound and some themes,right? Okay! So here is the method.
Cutom Boot sound
First, navigate to /system/etc and find PowerOn.wav. This will enable you to change the boot sound. Replace it with a short tone of .wav format only. Now you,have changed the boot sound
To change the boot animation
1) Download the bootanimation and samsungani file attached below.
2) Put them in the /system/bin folder and replace the existing files there
3) Now download any boot animation, and rename the bootanimation to “sanim.zip”.
4) Now, navigate to /system/media and replace the “ODEanim” with “sanim.zip”
You are done with the bootanimation change
TO change the theme
Just replace the framework-res.apk and twframework-res.apk in the /system/framework folder
Installing Cygwin
Installing the Cygwin and Setting up the Kitchen
Download the Cygwin files attached below. Extract the zip to a folder. Now, you can see 3 icons, a read-me,a setup, and a folder. Choose the setup. Here You will choose install from local directory. Next, Navigate to the the folder of extraction of cygwin and choose the folder Cygwin_packages inside the cygwin extraction folder. Wait for some time. Then, You will come across a list of file. Click the 2-circle-arrows,untill, it displays “install”
After the procedure is complete, run the batch file. Now, minimise it and extract the android kitchen.
Keep it in some location like C:\Kitchen
Now, open the batch file window and type
cd C:\Kitchen
Wait for some time and then when the location the changed, type
./menu
As this is a HTC kitchen, you can't use all the features,
Now, go back to the folder “custom FW” and create a zip ( I repeat zip and NOT rar) of all the folder in the “Custom FW”. After that is done, navigate to the kitchen folder (C:\Ktichen) and palce the .zip in the “original_update” folder
Come back to the Cygwin Batch window. Now you select 1 (i.e. the first option and press enter.
Then, again press 1 twice!
Now after this is done, you can also use option 2 (rooting). You can change the ROM's name using option 8.
Step 5
De-odexing the FW.
In the batch window, choose option 0 and then choose 1.
Using this you can de-odex your FW.
Next, choose 99 to build and pack you ROM
And you are done with the custom ROM
---------------------------------------------------
Thanks to @sakindia123
Extracting and odin build
Code:
xvf ODIN_FILE.tar.md5
NOTE:.md5 is optional
Rebuilding
Code:
$ tar -H ustar -c amss boot.img csc.rfs recovery.img system.rfs >ODIN_FILE.tar
$ md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar (signing the file)
$ mv ODIN_FILE.tar ODIN_FILE.tar.md5
Of course,u Have to put the name of ur file in place of ODIN_FILE
Mounting rfs(on linux)
Code:
mkdir system_mount
$ mount -o loop system.rfs system_mount
$ cp /folder/application.apk system_mount/app/ (adding aplications)
$ rm system_mount/app/application.apk (removing applications)
$ cp /folder/application.apk system_mount/app/application.apk (replacing aplications)
$ umount system_mount
Regards,
Rohan Mallya! =D
The essential files!
For the Kitchen ( thanks to dsixida)
For cygwin
Remeber to thank and vote in the POLL!!
Custom booting files ( one you have to replace for the bootanimation before you add sanim.zip!)(samsungani and bootanimation files)
MagicISO
Credits -.-
Misledz
Ganaboy
ronhoover88
Namaless
Vivek
Erahgon
Very informative posts. I hope this will lead to more ROM for our cellphone.
More things! ☻☻
You can zipalign and sign the ROM in HTC Android Kitchen itself! While COmpiling your ROM, Just select the interactive method! You can do it all there!
If you want to changes the build date and all, you can open the build.prop(present in /system folder) and change the values!
Reserved for future
If I may ask, do you have a source link for this or is it from you?
I typed it WHOLE? So..?? I did not get you well?
No worries, it's just I like to read the comments which are usually a good complement for every tut/info, so if it were from elsewhere I would have been happy to read them, that's all
can i use this port the miui rom?
r u sure u hav not copied this from elsewhere....bcoz the boot ani thing is wrong......i9003 has different format.....(i mayb wrong)
What boot ini,sak? Elaborate please??
You could also use the link below
http://forum.xda-developers.com/showthread.php?t=1168916
Sent from my GT-I9003 using XDA App
@ronhoover88 I went through it now. But, I think you cant use that meta-inf folder, the kernel adn the root script from that guide..If you feel this is thread is a WASTE OF TIME..Please tell me..I will make an attempt to delete it!
You dont have to delete...you have put a lot of effort...what i feel is, its better if you have created a rom using this guide and got it working...
Sent from my GT-I9003 using XDA App
Dude combined all this info in a single post
Sent from my GT-I9003 using XDA Premium App
The bootanimation thing is totally from vivek's thread..try it! It woooorks!
Tutorial for Porting Cf-root To Newer Firmware's
There were quite a few requests for a tutorial to create ginger bread cf-root. So here it is folks.
Big Thanks to skin1980 for helping me out.
Credits:
Chainfire for the cf-root.
Skin1980 for porting it to Samsung Galaxy SLCD.
Prerequisites:
Any Linux. Basic knowledge of linux is mandatory.
Tools for Unpacking and Packing images.
Base Samsung Galaxy SLCD Gingerbread Cf-root.
Samsung Galaxy SLCD Gingerbread Firmware ROM for cf-root creation.
Downloads & Setup
Any Linux: For this tutorial I am using Linux Mint KDE. You are free to use the Linux of your choice. Ideal starting point for downloading and installing Linux would be Distrowatch.com.
Tools for unpacking and packing images: These are sets of tools that allow you to unpack and pack boot images. Basically one requires just a few tools to achieve.
Link to Download: cfroot-tools.zip - 19 KB.
Download and exatract it into your home folder. It will create a cfroot-tools folder under home folder. Go to the folder and execute the following comand:
Code:
chmod +x *
Base Cf-root: Download any latest cf-root from this Link. Extract the normalboot.img from the cf-root tar file.
normalboot.img: Require normalboot.img extracted from downloaded Gb ROM.
Hex editor: You will require and Hex Editor. I am using bless hex editor. You can use any one which you are comfortable or the one available under your linux distribution.
Open terminal window and enter the following commands:
Code:
[FONT=Microsoft Sans Serif][SIZE=2]cd
[/SIZE][/FONT][FONT=Microsoft Sans Serif][SIZE=2]gedit ~/.bashrc[/SIZE][/FONT]
You can use any editor of your choice. The main purpose is to set the tools path. At the bottom of this file, add the following lines:
Code:
PATH=$HOME/cfroot-tools:$PATH
export PATH
Save and close the file.
Logoff from linux and login again for the new path to take effect.
The Actual Process
For the purpose of tutorial, I am going to use XXKPQ cf-root as the base and DDKP3 for creating new one.
Create a folder called “cfroot” with out the quotes under home.
Go to the created folder and create two more folders: DDKP3 and XXKPQ.
Now copy the normalboot.img extracted from XXKPQ cf-root and copy it into the XXKPQ folder. Next copy the normalboot.img fromDDKP3 firmware and copy it into DDKP3 folder.
Now go to the cfroot-tools folder under HOME and copy the decom.sh and recom.sh into XXKPQ and DDKP3 folders.
The above steps can be accomplished by the below code. Open command window and type the following:
Code:
cd
mkdir ~/cfroot
mkdir ~/cfroot/XXKPQ
mkdir ~/cfroot/DDKP3
cd ~/cfroot/XXKPQ
cp ~/cfroot-tools/*.sh .
chmod +x *.sh
cd ~/cfroot/DDKP3
cp ~/cfroot-tools/*.sh .
chmod +x *.sh
You need to press enter after each command.
From terminal window, first to change directory to XXKPQ, type the following commands:
Code:
cd ~/cfroot/XXKPQ
./decom.sh
After the execution of the above command, the following files and folders will be created:
normalboot.img-base
normalboot.img-cmdline
normalboot.img-pagesize
normalboot.img-ramdisk.gz => Ramdisk
normalboot.img-zImage => Kernel
Click to expand...
Click to collapse
Apart from these files, a folder called ramdisk will be created, into which the contents of normalboot.img-ramdisk.gz would have been extracted.
Now once more from the terminal window execute the following command:
Code:
cd ~/cfroot/DDKP3
./decom.sh
Also make note of the following values, which are shown, when the decom.sh script is executed.
Code:
BOARD_KERNEL_BASE 81800000
BOARD_PAGE_SIZE 00001000
Now under DDKP3 folder, edit the recom.sh file. Replace the value after --base with the value after BOARD_KERNEL_BASE. Replace the value after --pagesize with value after BOARD_PAGE_SIZE. Save the file.
Now we can switch to file manager. It will be easier to work using a file manager from here on. Open the XXKPQ/ramdisk and DDKP3/ramdisk folders separately in file manager.
Copy the folders res & sbin from base cf-root (XXKPQ in our case) and paste into DDKP3/ramdisk folder. Overwrite all when prompted.
Copy all the files under XXKPQ/ramdisk (in the root) to DDKP3/ramdisk.
From XXKPQ/ramdisk/lib/modules/2.6.35.7/kernel/ copy the fs folder into DDKP3/ramdisk/lib/modules/2.6.35.7/kernel/.
At this point of time, we no longer require the XXKPQ folder. So we can close the file manager window browsing XXKPQ folder.
Now comes the tricky and critical part. This must be done very carefully. We need to edit the .ko files using a hex editor.
Under the kernel/crypto/ folder, there is a pcbc.ko file, edit it using an hex editor. Search for 2.6.35.7 using find option in the editor. Now note down the six digit numbers starting immediately after 2.6.35.7-CL. In our case the magic number is 882023. Close the file and the editor.
Now we open the kernel/fs/ folder in the file manager.
Now open the mbcache.ko file in the hex editor. Search for 2.6.35.7 again. As we can see that the six digits after 2.6.35.7-CL is not 882023. In our case it is 709629. We need to change 709629 to 882023 and save the file. Different editors provide for different methods of editing. In my case I can just simply click on starting number that is 7 and start typing 882023 and save the file.
Now you need to do the same for two more files under kernel/fs/jbd2/ and kernel/fs/ext4/.
Now go back to ramdisk folder. Under ramdisk/sbin/boot/ there is a file called install.sh. We are now going to edit this file. This not important that you edit this file.
Edit the first line and replace XXKPQ with DDKP3.
Similarly under the “# Once be enough”, there is another XXKPQ which is to be replace with DDKP3.
Now save this file.
Now back to command prompt and execute the following commands:
Code:
cd ~/cfroot/DDKP3
./recom.sh
Executing the above script recreates the normalboot.img-ramdisk.gz, the normalboot.img and create DDKP3-CFROOT-16-02-2012.tar.
The DDKP3-CFROOT-16-02-2012.tar is the cf-root for DDKP3 and can be flashed using ODIN as Pda file.
*
Thats it folks. Hope my effort is worthwhile and benefits some of you.
*
Additional Links:
A text file Create Custom Rom (though not for our phone but is quite useful all the same) - Found it while searching google. Don't know who created it. But here is the link. Create_Custom_Rom.txt - 5 KB
The link to tools zip mentioned in the above text file. tools.tar.gz - 49 MB
Script to uncompress and compress UC Kernel
uc_decom.sh - 258 b
uc_recom.sh - 382 b
10 Chars ......
For Future Use
Whoa! This is huge! Awesomr work man! Thanks.
Edit - No offence meant, but it would be appropriate if the title is How to "port" or similar. Since it ws "created" by ChainFire and we just porting it.
ganeshbiyer is good, very patient, did not think that my trouble!
Has been helping me! Am very grateful!
great job! & i already translate it into chinese^^
and a problem:
after i run the script "decom.sh",it display following words:
[[email protected] xxkpq]# ./decom.sh
./decom.sh: line 5: unpackbootimg: command not found
gunzip: ../normalboot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
[[email protected] xxkpq]#
help me please~what's going on?
cRainin said:
great job! & i already translate it into chinese^^
and a problem:
after i run the script "decom.sh",it display following words:
[[email protected] xxkpq]# ./decom.sh
./decom.sh: line 5: unpackbootimg: command not found
gunzip: ../normalboot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
[[email protected] xxkpq]#
help me please~what's going on?
Click to expand...
Click to collapse
unpackbootimg must be in the path.
also it must be executable.
ganeshbiyer said:
unpackbootimg must be in the path.
also it must be executable.
Click to expand...
Click to collapse
sorry,i paste the wrong code. my problem is this:
[[email protected] XXKPQ]$ ./decom.sh./decom.sh: /home/chenyu/cfroot-tools/unpackbootimg: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
gzip: ../normalboot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
[[email protected] XXKPQ]$
cRainin said:
sorry,i paste the wrong code. my problem is this:
[[email protected] XXKPQ]$ ./decom.sh./decom.sh: /home/chenyu/cfroot-tools/unpackbootimg: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
gzip: ../normalboot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
[[email protected] XXKPQ]$
Click to expand...
Click to collapse
Need to install the missing file ld-linux.so.2
Sent from my GT-I9003 using xda premium
Thank you Ganeshbiyer! this is the tutorial for which send multiple private messages and never answered .. Thanks again, nowI can make a version for Gingerbread UBKPD.
goodbye
Yeah ganesh! A superb work..well done bro
thanks bhaiya....
Thanks for the tutorial buddy
Hope it has been useful.
_
Release all PERFECT! I had no problem in making the entire guide .. BUT ... when flashing in ODIN, and says that when it failed to finish.
I knew that I would be so easy, so I started to analyze both folders (my UBKPD and XXKPQ) and did not get that at the root of KPD I have 12 files and only 11 KPQ. The 12th file executable type KPD called RECOVERY. This file should remove it before using recom.sh?
Thanks again for the guide. goodbye
Edit2:
Well, my little patience led me to delete that file and then went back to RECOVERY recom.sh run and throw me error that could not erase normalboot.img and did not understand, but looking at the files in the root, not the size you normalboot.img was higher than the stock then replace the stock normalboot (+5 mb), run again and finally he created recom.sh cf.root, I flash with ODIN successfully without any problem in these +30 minutes.
Thanks (again).
Now I have as including UV & OC (freqmax 1100MHz is very good speed and would think you do not need more with this phone)
maybe a stupid question:
would it work with other phones as well? natually with the files of the other phone and not with the 9003 files
fabsau said:
maybe a stupid question:
would it work with other phones as well? natually with the files of the other phone and not with the 9003 files
Click to expand...
Click to collapse
Well you can always try
thanks for your reply
I will try it soon^^
wait for my next reply
greetings fabsau
i do it all at this tutorial and it create .tar fine without trouble.. i flash with odin also no problem happen.. but while device open.. at boot logo get stuck or freeze at long time.. why it happen???
i confuse with this line:-
-Copy the folders res & sbin from base cf-root (XXKPQ in our case) and paste into DDKP3/ramdisk folder. Overwrite all when prompted.
-Copy all the files under XXKPQ/ramdisk (in the root) to DDKP3/ramdisk.
-From XXKPQ/ramdisk/lib/modules/2.6.35.7/kernel/ copy the fs folder into DDKP3/ramdisk/lib/modules/2.6.35.7/kernel/
Click to expand...
Click to collapse
why do not copy all the file in ramdisk n skip copy file inside the ramdisk folder.. it is difference?? please tell me if i do a mistake.