Related
Hi, I followed the thread: "How to reconstruct a dumped ROM"... (obviously I had, before, did a rom dump!). Now I have a directory named "dump" with several subdirs.
In the step 3) there is written: "After this step you can optionally edit the OS files with the proper tools"... now the question is: what are these proper tools? I searched in the forum, in the other threads but I didn't find anything... My needs are: to delete some programs that are in the rom (for example Pocket Word, Pocket Excel, other..) in order to obtain more space, but to install other tools at the free space.
Thanks in advance for your help....
Great question ! i can't help you , but i wait for answers ....
I asked the same thing the other day, and got an answer(thx again to him).
Actually, I'm doing it right now, as a test I've successfuly dumped and rebuilt lsvw's rom using enhanced imgfs tools batch files, nbdump.bat nbname.nb & nbbuild nbname.nb, now I'm removing files from the rom and maybe add some other, like that quick gps thingy, latest msn(optimized for trinity, removed vga resources), phone pad, and some other thing on my custom extrom.
I had the same doubt as you, but it seems that we're overcomplicating things, you can simply use the file explorer to remove files from that dir, beware of which files you remove/alter.. initflashfiles.dat has some operations to be done after flashing the device(creating folders,renaming files, moving them to startup/start menu/etc folders), I thought that if the file didn't exist on the windows folder, whatever invoques initflashfiles.dat would crash, but it doesn't seem to be the case, I haven't put this to test, but I've found several missing files on the initflashfiles.dat(and a typo, "floder", go figure what it means - lazy/rushed editing IMO), so there seems to be some tolerance to the operations contained in that file.
I won't edit the wiki until I'm 100% sure that what I know is correct, but to sum it up:
dump the files
add/delete files with explorer
edit the registry using rgucomp
edit initflashfiles.dat using the original windows notepad & use an hexeditor to remove the 1st 2 bytes
run NBBuild.bat to create the *.nb file
OSchecker.exe to validate the *.nb file
nbhtool.exe to create the nbh
flash it(I prefer the sd card method)
Code:
rgucomp needs setting _FLATRELEASEDIR environment variable to current directlry like this:
set _FLATRELEASEDIR=.
Dump default.hv/user.hv file to .reg with:
rgucomp.exe -nologo -o default.hv > default.reg, then add line "REGEDIT4" to the beginning of REG file.
Modify the .reg file to your liking, (save it in UTF-16 with CR+LF terminations and a new line at the end of the file) and convert it back to .hv
And don't forget to flash Olipro's Hard SPL before, it may save your device.
"and convert it back to .hv"
http://forum.xda-developers.com/showpost.php?p=1186635&postcount=1
(no wonder I didn't find this info, forum search is almost useless, googled for rgucomp and voilà, first result(above) right answer)
Help!
I've followed the instructions on the wiki about dumping a ROM, which I've done and it worked fine.
Then i started to follow everything to rebuild the ROM, which worked until I got to the buildimgfs.exe stage, and all I get is an error message that it cant find the compression dll, even though I know the dll is in the directory with it.
Any help much appreciated as I'm trying to rebuild a Orange UK M700 rom
Cheers
use these batch files to dump/rebuild the rom&hive, nbhtool to create the Signed_RUU.nbh
Make Sure You Have A Valid Imgfs_raw_data.bin In The Folder You Are Issueing The Command From, That Stopped My buildimgfs.exe Working.
Cheers
still not working...
message about missing compression dll still happens, even though viewimgfs works fine.
@apoc - not entirely sure which bat files to run, the dump ones didnt seem to do anything?
hollandg said:
still not working...
message about missing compression dll still happens, even though viewimgfs works fine.
@apoc - not entirely sure which bat files to run, the dump ones didnt seem to do anything?
Click to expand...
Click to collapse
command prompt:
NBDump.bat OS.nb - to dump
NBBuild.bat OS.nb - to rebuild
HVDump.bat user | HVDump.bat default - to dump the user.hv or default.hv,
The HV bat files must be on the same dir as the .hv files.
there are a bunch of hidden files, and I've mistankenly hidden OSChecker.exe, I think it's not exactly necessary to check the created .nb files, but the file is there and you can use it.
@APOC, another bit of help if you dont mind?
I've run the NBBuild.bat and it produced a file but someones tested it and says it doesnt work so I had a look at the .bat and some of the steps seem to pull information from an exisiting NBH file? I downloaded a file as part of the wiki step by step to dump and rebuild a file so the NBH I have is nothing to do with the one I'm trying to rebuild ... is that a problem?
As before I've got as far as running viewimgfs to create the dump directory but buildimgfs refuses to work still!
-----
I've jsut read tadzio's thread about the enhanced imgfs tools so I'm going to try that again and see what I can do
Please rate this thread if it was useful...
I know that stuff like this has been posted before but I have never seen a full guide begining to end on how to backup your rom so here is the complete guide (with links) beginning to end of how to backup your WM6X ROM on HTC's Shift to an NBH
To do this you will need a HTC Shift (dir), and basic knowledge of Windows Mobile, Vista, the command prompt and Syncing a WM device with a computer.
NOTE: I am NOT sure if you need HardSPL on the device to flash the ROM back onto your Shift (if someone could let me know that would be great), my guess is that you do as the created nbh will not be signed with HTC's Cert - HardSPL can be found here http://forum.xda-developers.com/showthread.php?t=406606 and is compatible with GSM Shifts only (x9500)
If anyone has any suggestions as to how this post could be improved or tell me if something needs a more in-depth explanation, let me know - Thanks.
First you will need to Liberate your shift; instructions on how to do this can be found here: http://www.modaco.com/content/windows-mobile-news/266537/liberate-your-htc-shift/ (this step will "unlock" the restrictions on windows mobile - this is not necessary but makes installing RAPI tools and other files easier later.
Download HardSPL (we are not going to install HardSPL in this post, but the download includes RAPI that is needed prior to the next step) from here: http://forum.xda-developers.com/showthread.php?t=406606
When the download has finished extract the contents and copy EnableRapi.cab to your device (To do this select Settings from the today screen > USB Tool > Options > Detach from Vista > Options Attach to Vista - yes detach is not always required but seems to solve some issues with syncing).
Your device will now appear in "My Computer"; copy the file somewhere to your device then switch to Windows mobile and run the file.
Download the latest version of itsutils from: http://www.xs4all.nl/~itsme/projects/xda/tools.html (Look under download section) then follow the instructions on http://forum.xda-developers.com/showthread.php?t=382609
After you have followed the instructions there you will have created RAW files of your Windows Mobile ROM (on the post you will notice the the code window in color - these may be different depending on your device and may need to be changed)
Now we need to convert the raw file to an nbh to do this you will need to download the shift kitchen from: http://forum.xda-developers.com/showthread.php?t=422914 then extract the files from the rar archive (using winrar, winace etc)
On some computers the below operation may fail saying "Error loading dll msvcr71.dll" so you should download and extract the attached zip file (msvcr71.zip) to the Tools directory
When you have done that put the *.raw files created by itsutils into the BaseROM directory and run the !BEGIN.cmd file
Select option 2 when asked to rebuild a ROM and follow instructions.
When the command has completed run the !COOK.cmd file; When a window appears titled BuildOS Click on the Play button and wait for the process to complete then close the BuildOS window
Follow further instructions; until another window appears, Select Shift as the "Target Device" and under "OS" select os-new.nb, then click "Build NBH!",
A window will appear asking you to save the NBH - DO NOT CHANGE THE PATH as it kept crashing when I tried to save elsewhere and call the file RUU_Signed.nbh
Copy the file RUU_Signed.nbh where you want and download and extract CustomRUU.zip (attached) to the same path
To restore the ROM all you need to do is Sync with Vista and run CustomRUU.exe
Feedback is always welcome,
Thanks,
Kris
*RESERVED*
All done! But when performing this process
BuildOS Click on the Play button and wait for the process to complete
I have Error window:
Error: File `ROM\XIP\boot.rgu` not found.
and when I click `OK` - process stops!?
What is wrong?
All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...
sardonix said:
All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...
Click to expand...
Click to collapse
When you flash your ROM it will be the Russian ROM ... the WWE setting there and the version are just what is displayed in the ROM flashing tool (CustomRUU.exe)
I had the Spanish version and used this process beginning to end - and it says WWE in the flasher but still installs the Spanish version
Kris
Kris, thanks! Believe that I`ll not have reason to use it. But with this reserved ROM it is composed to make any ROM manipulatios.
Thanks once more!
can i request this to be a stickey?
thanks
Great work i00
I have added it to the WIKI and the FAQ thread.
I confirm that you DO need to install HardSPL on the device PRIOR to flashing the ROM back onto your SHIFT.
it's work
someone got shipped UK rom backup ?
kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Radio is here .. will upload the ROM shortley
http://rapidshare.com/files/232295760/Shift_Origional_UK_Radio.zip
Regards,
Kris
kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Orig UK ROM can be downloaded here:
http://rapidshare.com/files/232298625/Shift_Origional_UK_ROM.zip
Regards,
Kris
Sorry when I try following your tutorial,
I have not os-new.nb file what could I do wrong?
Back-up the rom and radio files
Hi i00, absolutely great guide, thank you for the hard and tidy work!
Since I'm a beginner in this area, before doing the dump job myself, kindly ask you to advise if the dump operation leaves the Shift unchanged on the winmo side and I can use it further, i.e. it is a read-only operation OR do I need to load back (flash back) the resulting back-up files (ROM and radio)?
Thank you!
rom
Hi all
i just bought a brand new shift and want to have a back up of the ROM
I've exacted 4 parts of the rom, but unable to convert it back into a NBH
i cant seem to figure out if i need the RUU_Signed.nbh , and where do i get it from, i thought i was making RUU_Signed.nbh from the 4 raw part files.
if anyone can re upload the complete UK ROM.NHB i would be grateful
i have uploaded the 4 part files and the boot loader
www(dot)filedropper(dot)com/rawfiles
part00.raw
part01.raw
part02.raw
part03.raw
SPL.nb
also do i need hardSPL to even load the original back up rom?
thanks
is this the file i need to include in my baserom folder?
forum(.)xda-developers.com/showthread(.)php?t=1875806
Need Radio ROM GPS+Phone Modded 1.27
here is my error code:
Welcome to Kaiser ROM Kitchen
-----------------------------
Please choose the way for Kaiser ROM Kitchen to work:
Enter 1 if you want just to cook ROM
(RUU_signed.nbh required in BaseROM folder)
Enter 2 if you want to rebuild and cook dumped ROM into flashable ROM
(RUU_signed.nbh, dumped part01.raw and part02.raw required in BaseROM folder)
Please choose 1 or 2: 2
Could Not Find C:\kaiserkitchen\baserom\os.nb
Could Not Find C:\kaiserkitchen\baserom\0*.*
Path not found - C:\kaiserkitchen\temp
The system cannot find the file specified.
The system cannot find the file specified.
=== NBHextract v1.0
=== Extract contents from HTC NBH files
=== (c)2007 xda-developers.com
=== by: pof & TheBlasphemer based on itsme perl scripts
Error: Could not open 'RUU_signed.nbh'
The system cannot find the file specified.
The system cannot find the file specified.
1 file(s) copied.
1 file(s) copied.
Press any key to continue . . .
Hello fellow HTC-ers!
I've made a dump of my Blackstone (using pdocread -l), all seems fine. Got 4 .raw files. Now, Dr. Jay in his movie says to "get" a .nbh file. From where?? I'm confused. Read several postings about IMGFS, but those didn't help me to get to the next step.
To be precise : I want to have a flashable backup of my original (NLD : Original NLD ROM - 1.14.404.3_Radio_52.49a.25.26_1.09.25.14) ROM before I install HSPL and start cooking my own. Preferably, I want to create this original flashable ROM myself, just to get familiar with the tools and the process.
Could anyone tell me where to go from here? (4 .raw files)
Thanks.
Grt., K.
ps. when I search this forum for ".nb" or "nbh" I get no hits.. Does the searchkey have to consist of a minimum number of characters?
kkoenen said:
Hello fellow HTC-ers!
I've made a dump of my Blackstone (using pdocread -l), all seems fine. Got 4 .raw files. Now, Dr. Jay in his movie says to "get" a .nbh file. From where?? I'm confused. Read several postings about IMGFS, but those didn't help me to get to the next step.
I want to create this original flashable ROM myself, just to get familiar with the tools and the process.
Could anyone tell me where to go from here? (4 .raw files)
ps. when I search this forum for ".nb" or "nbh" I get no hits.. Does the searchkey have to consist of a minimum number of characters?
Click to expand...
Click to collapse
Please read and use this very usefull tool from here: http://forum.xda-developers.com/showthread.php?t=438456
You need to download an official stock rom. Copy your part1 and part2 raw files and the RUU_signed.nbh (from the downloaded and extracted stock rom) into the baserom folder. You need to launch the BlackStoneKitchen.cmd from the rom kitchen folder and follow the on-screen instuctions: extract the content (push e then b), then re-cook it (push c then a).
thanks, tsummer.. I've downloaded the kitchen and the original stock ROM's a few weeks ago. The stock package consisted of 4 .rar files, extracting to one .exe file. No .nbh! So, where should I get it from? If I start the .exe, an application pops up, wanting to flash my device.. The thread you posted does not shed any light on where to obtain or how to extract the right .nbh file..
I really read in to this stuff, but somehow the whole "getting the .nbh-file" remains foggy to me. Please advice.
/edit : I've got a "RUU_Signed.nbh" from a zip called "Restore_Stock_SPL_114_2.zip". Is that the right one? It's 513 KB (526.193 bytes) big. Question remains : How should I extract the existing .nbh from my running ROM / Device?
Found it!
To get the .NBH file from a Stock ROM .exe file, right click the .EXE and select "Extract Files..." from your rar-quickmenu!
Wow.. took me "only" 8 hours to figure this one out...
*shame* dr.Jay does explain it in his movie "rebuilding".. ouch.
kkoenen said:
thanks, tsummer.. I've downloaded the kitchen and the original stock ROM's a few weeks ago. The stock package consisted of 4 .rar files, extracting to one .exe file. No .nbh! So, where should I get it from?
Click to expand...
Click to collapse
Open the exe with winrar and you will see the RUU_signed.nbh (this is the correct nbh). Copy this nbh into the baserom folder and use the BlackstoneKitchen.cmd.
[/QUOTE]/edit : I've got a "RUU_Signed.nbh" from a zip called "Restore_Stock_SPL_114_2.zip". Is that the right one? It's 513 KB (526.193 bytes) big. Question remains : How should I extract the existing .nbh from my running ROM / Device?[/QUOTE]
The SPL in an another issue.
I was just wondering if I wanted to re-cook a rom such as Dutty's or L26 to add one extra package is that the same procedure as above assuming I dump their rom from my device?
LG BIN/TOT Extractor
This is a tool for extracting LG Bin/Tot Firmware files.
I update the git a lot more than what I update the thread so check there for latest news.
Features
Split Bin file into relevant partitions
Split Tot file into relevant blocks and merge blocks into partitions
Display AP Header
Display GPT Header
Extract Header from Bin/Tot File
Features I like to implement (and probably won't get around to)
Extracting boot img (The tools currently available don't work in all cases and it's very easy to read the header since it's open source.)
Extracting ext4 partitions. So that it's easy to access the file. Theres already other tools that can do this so this isn't essential.
Mergeing tot partitions based on data from partitions itself and not GPT
Inject Alternate Data into partitions. I'll block access to X-loader,U-boot and GPT so that You can't kill your phone.
Source
https://github.com/Xonar/LGBinExtractor
Confirmed to work with
Quite a few phones.
I lost track of which ones work.
To check just run with -daph. You'll get file information if it works and either garbled data or an error message if it doesn't.
If your phones not supported follow the steps on git readme.
Thanks
SnowLeopardJB - for lots and lots of testing
navossoc - his tool that extracts kdz and wdb files
vim1 - D821 support
scotty755 - LGL22 support
tkawajir - L-04E and LG G Flex F340K support
If you feel I forgot to thank you, msg me and I'll add you.
If it can extract BIN files then yes. We believe the nandroid V30* of KU5900 that was supplied was incomplete. So If KDZ is converted to BIN and FLS (which we can), then extract contents of BIN, then you can have complete files without looking for Koreans and Chinese to relay that the nandroid was incomplete and can have untampered files.
xonar_ said:
Question to other Devs
Will you use a tool like this or am I wasting my time?
Is a tool like this allowed or would it be considered reverse engineering? (If its not allowed I'm going to stop IMMEDIATELY)
Click to expand...
Click to collapse
Yes I will. If I myself can build a program to extract this EFI partition..
It is reverse engineering, but I don't know if it's legal or not (in this case), but for me it's legal as I'm considered this to educational purpose
Many others tool was created to have purpose like this, for example http://psas.revskills.de/?q=node/5
-CMIIW-
I've attached an image of the system partition of the V20E_00 for you guys to see.
I am going to download the v30H_00.kdz today. So I'll keep you posted about how the extracting goes. I probably won't have time to check it out until the weekend so please don't hold your breath.
I've only recently managed to find the necessary information about the ext4 file system to integrate the functionality into my tool. For now Ext2Read can extract the ext4 file system just fine. I'll add that somewhere over the weekend (Provided something doesn't come up).
Could you as soon, as you are able to unpack it fully maybe upload a complete backup of the system partition and also system2, cause we think, that in the nandroid there are some files missing and we need those, to probably be able to boot that system. Great job btw
Thanks for the positive feedback.
I am getting the v30h_00.kdz in a few hours (I got a friend to download it for me, I don't have that much cap ).
There is no way I will be able to upload the file since it will be big but if it works I'll post the tool and how to do it.
GitHub is giving me an error : "Page did not respond in a timely fashion". I am going to try again tonight to post the source.
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
navossoc said:
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
Click to expand...
Click to collapse
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
xonar_ said:
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
Click to expand...
Click to collapse
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
navossoc said:
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
Click to expand...
Click to collapse
Yes the BIN. They are using little endian. All the offsets and sizes are in LBA's (512 bytes in this case) with LBA 0 starting at 0x100000.
Sent from my LG Optimus Black
Source of Bin Fls Extractor (So far)
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
EDIT2: These sources are old. I'll upload my fixed ones later. Reads in chunks and works on P970 and KU5900 ( I don't have any other files to test it with but it should work with almost all BIN files extracted from kdz files )
xonar_ said:
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
Click to expand...
Click to collapse
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
Nice! Great job you guys. :good:
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
can you upload system files asap?
George Jetson said:
can you upload system files asap?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=31443301&postcount=270
Thanks to navossoc there
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
That's good news.
I won't be able to work on the program during the rest of this week. With the system files extracted there's nothing that needs to be urgently done.
Next Step is to to try and build the BIN from other files. I think I can improve on your recovery.exe to add su binary and apk aswel (Might take a bit longer since I need to extract the ext4 partition, add su then put it back together )
Well, it's just a beta, because it use too much ram to write the files.
I need to read the file in chunks, but, for now it's a good prototype, we can using it.
extract.7z
Code:
CRC32: 2199d10f
MD5: 5b8d8031ff5d66ec2832d182e98505be
SHA-1: b6d729a20d4370e25ebc4eddfc27e25673b1d2f2
To use the tool is just run...
Code:
extract.exe filename_AP.bin
It should work on any bin file, tested on P920, P970 and KU5900.
Please report any error.
[]'s
Thanks navossoc its working well on ginger p970 bin file.
Great stuff thanks alot! You to make a great team.
Sent from my LG-P920 using xda app-developers app
Now how can we make a new bin file with that img files?