I want to extract the registry from the ROM dump of "RUU_Excalibur_DOPODASIA_WWE_1.15.707.2_4.1.13.28_ 02.63.90_Ship". However I got the following error message when I run >> rgucomp.exe -o default.hv -> default.txt
DisplayHiveFileAsText: (RGUComp) !ERROR unable to mount hive file "default.hv"
Anyone has a clue?
hi,
my device is p3700(diamond gsm), and i'm trying to cook a rom.
I had used nbhtool.exe to get the os.nb from the os.nbh which is shippd with offical successfully. and then used the "Platformrebuilder - New ROM Kitchen " toolset (the list of toolsets which can be found here, or download the zip file from the attachment which is the mht file of that url. ) to get a os.nb.payload file. but I met a prompt in the end which said the imgfs.bin is refused to access.
i've searched the forum and can't find the answer. can anyone help to solve this? thank you.
Didn't take a look at your files, but check the bat file for paths.
Maybe it's expecting the file somewhere else?
adwinp said:
Didn't take a look at your files, but check the bat file for paths.
Maybe it's expecting the file somewhere else?
Click to expand...
Click to collapse
hi, adwinp, thank you for you reply.
i look the dump_800.bat, and try the following codes ONE BY ONE(SPLIT THE .BAT INTO TWO .BAT:
FIRST(TO CREATE THE IMGFS.BIN):
Code:
@ECHO OFF
if "%~1"=="" goto :error
set path_exe=%~d0%~p0
set path_arg=%~d1%~p1
cd /D %path_arg%
"%path_exe%bin\NBSPLIT" -data 2048 -extra 8 "%~1"
del "%~1.extra"
"%path_exe%bin\IMGFSFROMNB" "%~1.PAYLOAD" IMGFS.BIN
pause
goto:EOF
and the results:
Code:
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file D:\MyROMs\[MyCooking]\Windows.nb
Done.
ImgfsFromNb 2.1rc2
Sector size is 0x800 bytes
ImgFs partition starts at 0x00780000 and ends at 0x07fa0000
Dumping IMGFS at offset 0x007c0000 (size 0x077e0000)
Done!
SECOND(TO GET DUMP FROM THE IMGFS.BIN):
Code:
@ECHO OFF
if "%~1"=="" goto :error
set path_exe=%~d0%~p0
set path_arg=%~d1%~p1
cd /D %path_arg%
"%path_exe%bin\IMGFSTODUMP" IMGFS.BIN
REM del "IMGFS.BIN"
del "dump_MemoryMap.txt"
REM rename "dump" IMGFS
pause
goto :EOF
and i don't see the error any more, but i'm not sure if the following results seems the right one while the bat command finished.
Code:
Header type: FFFFFFFF, Addr: 064FD688
Empty header
Header type: FFFFFFFF, Addr: 064FD6BC
Empty header
Header type: FFFFFFFF, Addr: 064FD6F0
Empty header
Header type: FFFFFFFF, Addr: 064FD724
Empty header
Header type: FFFFFFFF, Addr: 064FD758
Empty header
Header type: FFFFFFFF, Addr: 064FD78C
Empty header
Header type: FFFFFFFF, Addr: 064FD7C0
Empty header
and if directly use the dump_800.bat, then get the error:
Code:
Header type: FFFFFFFF, Addr: 064FD688
Empty header
Header type: FFFFFFFF, Addr: 064FD6BC
Empty header
Header type: FFFFFFFF, Addr: 064FD6F0
Empty header
Header type: FFFFFFFF, Addr: 064FD724
Empty header
Header type: FFFFFFFF, Addr: 064FD758
Empty header
Header type: FFFFFFFF, Addr: 064FD78C
Empty header
Header type: FFFFFFFF, Addr: 064FD7C0
Empty header
D:\MyROMs\[MyCooking]\IMGFS.BIN
access refused.
and i synchronize the two imgfs foder generated by above 2 method by totoal commander, it seems all the files are the same...
so does it mean i can ignore the error?
ok. now it works since i change the bat as follow, the error maybe generated by the del cmd. see the REMs:
Code:
@ECHO OFF
if "%~1"=="" goto :error
set path_exe=%~d0%~p0
set path_arg=%~d1%~p1
cd /D %path_arg%
"%path_exe%bin\NBSPLIT" -data 2048 -extra 8 "%~1"
del "%~1.extra"
"%path_exe%bin\IMGFSFROMNB" "%~1.PAYLOAD" IMGFS.BIN
pause
cd /D %path_exe%
cd /D %path_arg%
"%path_exe%bin\IMGFSTODUMP" IMGFS.BIN
pause rem this command used to judge if the imgfstodum works or not. it seems work normally
cd /D %path_arg% rem add this to change the dir again distinctly
pause
del "IMGFS.BIN" rem the previous error should be generated by this. after the change dir cmd above, the error is gone.
del "dump_MemoryMap.txt"
rename "dump" IMGFS
pause
goto :EOF
:error
echo Usage: Dump_xxx.bat "nba file"
pause
When using Ervius Kitchen,
I dumped the stock rom and completed.
i extracted all into the root folder, ervius is starting correctly.
When started,
i click on DEVICE and select RHODIUM
then i get the following error:
"Os Value on: 'NBHUTIL.xml' for RHODIUM not found...
Set 0x400 as default!!!!"
how do i fix this?
Just for the hell of it, I'd like to unpack a system.img the easy way. I tried unyaffs for Windows but it doesn't seem to work. Does the factory images from Google even use the yaffs format?
When I try to unyaffs system.img, I get this which I condumped:
Code:
0 [main] unyaffs 6232 exception::handle: Exception: STATUS_ACCESS_VIOLATIO
N
831 [main] unyaffs 6232 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
What am I doing wrong? I open a command window in the directory of the image file, make sure unyaffs.exe and cygwin1.dll is there and then type "unyaffs system.img"
Same question here
Don't forget to hit thanks
I have already posted how to do this in this post... Have a look at the last few lines of the "How to flash" section in blue.
Hi, if you try install the cab's on your w10m you can get the errors. Sometimes package can be installed incorrectly. Today I show you how reinstall cab package.
WARNING: IT'S IMPORTANT SYSTEM PART, YOU CAN GET BOOT LOOP.
you need:
PC with telnet;
device on w10m build higer 10586;
interopTools;
Let's go:
//if you don't have telnet and reg.exe(if you have go to 2)
1. you need get ssh access https://forum.xda-developers.com/windows-10-mobile/guide-filesystem-access-sftp-windows-10-t3185766
(interopTools have section about this. you need: set password, allow tmp cmd access, allow application running)
download attachment file and extract it
upload it on you device in documents directory.
connect over ssh(telnet if installed) and go to documents directory
enter: install
(it's installing: telnetd,ftpd,bootsh,reg,xcopy,reboot,shutdown)
2. (optional)(or not if you try remove package)
PS1: I think if you try reinstall package, files be rewrited automaticly. but i not sure...
PS2: try ignore this step, if next instalation be failed try do this step
now you need find cab file which you tryed install and extract it(can use 7z)
open .manifest file, whom name consist mainos1
// only if you removing package
it's registry editions doed by this package you can try restore it back.
but facticaly you need remove only drivers and services
for edit registry use reg.exe because interopTools can't remove some keys
// only if you removing package
open .mum file with notepad++(or other program with color xml code)
you find list of files, like this
<file name="..." cabPath=".." />
for you intrested field "name" - it's path to this file in system
you need try remove this files(if you can't delete some file ignore it =) )
3. open cmd.exe on your PC and enter telnet "phoneIp"
now you need remove keys, use "reg.exe delete"
keys to delete you can find in key:
HKEY_LOCAL_MACHINE\software\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\
and
HKEY_LOCAL_MACHINE\software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\
here keys of all installed packages
in final you get command like this:
reg delete "HKEY_LOCAL_MACHINE\software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\PACKAGENAME"
then reboot
//for install package agin
4. connect over telnet, agin)
cd /windows/servicing
UpdateApp.exe getinstalledpackages
if in this list no your package, you doed step 3 correctly
now you can upload correct cab file and enter this command:
updateApp install "fullPathToCab"
PS dont try write in c:\windows\servicing
good luck!
Code:
UpdateApp - Update Application for Windows Mobile
[B]UpdateApp.exe install[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Installs the list of packages to the existing/mounted image. Same as stage + commit.
Note: this may cause a device reboot.
[B]UpdateApp.exe installinprocnoreboot[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Same as stageinproc + commit noreboot.
[B]UpdateApp.exe installfromsdinprocnoreboot [/B]<path to package/actionlist> <path to package/optional actionlist root> ...
Installs the list of packages to the existing/mounted image. Same as stagetosdinproc + commit noreboot.
[B]UpdateApp.exe installfromsd[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Installs the list of packages to the existing/mounted image. Same as stagetosd + commit.
Note: this may cause a device reboot.
[B]UpdateApp.exe mountandinstall[/B] <path to image> <path to package/actionlist> <path to package/optional actionlist root> ...
Mounts the given image, runs the 'install' path, then dismounts the image.
Note: this may cause a device reboot.
[B]UpdateApp.exe stage[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Stages the list of packages to the image.
Can also be a single action list ending in .xml.
Use the commit option afterwards.
[B]UpdateApp.exe stageinproc[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Stages the list of packages to the image in proc instead of via service.
Can also be a single action list ending in .xml.
Use the commit option afterwards.
[B]UpdateApp.exe stagetosd[/B] <path to package/actionlist> <path to package/optional actionlist root> ...
Stages the list of packages to the SD card.
Can also be a single action list ending in .xml.
Use the commit option afterwards.
[B]UpdateApp.exe stagetosdinproc [/B]<path to package/actionlist> <path to package/optional actionlist root> ...
Stages the list of packages to the SD card in proc instead of via service.
Can also be a single action list ending in .xml.
Use the commit option afterwards.
[B]UpdateApp.exe commit [/B][migratedata] [noreboot]
Commits a previously staged update to the image.
data migration will run only if specified.
Note: this may cause a device reboot unless noreboot is specified.
[B]UpdateApp.exe cleanup[/B]
Cleans up all update-related files.
[B]UpdateApp.exe renamepackages [/B] <folder>
Renames filenames to PackageName.cab. Useful for renaming numbered cabs or mangled filenames.
[B]UpdateApp.exe getinstalledpackages[/B]
Prints all installed packages in the image to the console.
[B]UpdateApp.exe loadlibrary [/B]<dll>
Loads the library given in the path. Good to test downlevel compatibility.
[B]UpdateApp.exe compress[/B] <file/folder> [compress (default)|decompress] [recursive for folder]
Compresses the file at the given path, or if a folder, all files within the folder, optionally recursive.
[B]UpdateApp.exe getlatestpayload[/B] <existing payload dir> <root of udpates> <output folder> <canonical|canonical_paper>
Loads the existing payload and copies files with identical names out of the update root to the output folder.
Root of updates for a diff is the v2\<build>, while for canonical/canonical_paper use v2\common.
[B]UpdateApp.exe precommitfixup[/B]
Saves the last boot committed information after a warm boot.
[B]UpdateApp.exe postcommitfixup[/B]
Fixes up merged REG_BINARIES and Capabilities.
[B]UpdateApp.exe getupdateresults[/B]
Get update result from the last commit.
Any option that has a list of packages supports wildcard mode.
Example: UpdateApp.exe [install|installwithcopy|mountandinstall <path to vhd>|stage] <path to directory with packages>
A directory alone will include all files in the directory non-recursively, this is equivalent to <directory> *
Code:
D:\>C:\Windows\servicing\UpdateApp.exe install D:\BackUp\*.cab
UpdateApp - Update Application for Windows Mobile
Staging update...
[00:00:00] Generated new CbsLite session ID: {632E4775-694B-448E-B997-BE4E65F0372C}
[00:00:00] Entered IUPhase Staging
[00:00:00] Entered IUSubphase Default
[00:00:00] Staging progress: 1%
[00:00:00] UpdateDLL: Staging update.
[00:00:00] Cleaning staging root.
[00:00:00] - UpdateOS dismounted.
[00:00:00] - StagingRoot cleaned.
[00:00:00] - Default StagingRoot cleaned.
[00:00:00] Entered IUSubphase WimMount
[00:00:07] onecore\base\cbs\mobile\iucore\iustore.cpp, IUStore::MountPendingUpdateOS, line 707, Failed to mount UpdateOS WIM at '\\?\U:\USERS\System\AppData\Local\UpdateStagingRoot\Pending_UPDATEOS.wim' to '\\?\U:\USERS\System\AppData\Local\UpdateStagingRoot\UPDATEOS_Mount', error is 0x80070522
[00:00:07] Staging progress: 5%
[00:00:07] onecore\base\cbs\mobile\iucore\iustore.cpp, IUStore::AddPackage, line 472, Failed to add partition updateos, error is 0x80070522
[00:00:07] onecore\base\cbs\mobile\iucore\iustore.cpp, IUStore::AddPackage, line 419, Failed to add package \\?\U:\SharedData\DuShared\PackagesToInstall\*.cab, error is 0x80070522
[00:00:07] onecore\base\cbs\mobile\updatedll\lib\updatemain.cpp, UpdateMain::ReadConfig, line 252, Failed to add package \\?\U:\SharedData\DuShared\PackagesToInstall\*.cab to store, error is 0x80070522
[00:00:07] onecore\base\cbs\mobile\updatedll\lib\prepareupdate.cpp, UpdateMain::PrepareUpdate, line 102, Failed to read input file, error is 0x80070522
[00:00:07] Cleaning staging root.
[00:00:07] - UpdateOS dismounted.
[00:00:07] - StagingRoot cleaned.
[00:00:07] - Default StagingRoot cleaned.
[00:00:07] UpdateDLL: Staging completed unsuccessfully
[00:00:07] hr = 0x80070522
[00:00:07] Output file written to: \\?\U:\SharedData\DuShared\UpdateOutput.xml
[00:00:08] Staging failed at: 5% progress
[00:00:08] UpdateDLL: Performance Measures:
[00:00:08] Total staging time: seconds = 8 (tickcount=8281)
failed, error is 0x80070522. Internal storage bytes required: 0, SD bytes required: 0
install completed unsuccessfully
hr = 0x80070522
Thanks for posting this.
Also @spavlin thanks for the extra tool info for updateapp.exe.
I recently pushed an incorrect .cab file to a phone, or so I thought...Iutool will not let you send the same package again if an already higher version one is there or the same version number is there. I found also that if you have full filesystem access you can go to path C:\Windows\servicing\Packages and remove the associated .cat and .mum file for .cab/package file you sent. This will then let you resend the same package or different version of the same .cab/package again.
nate0 said:
Thanks for posting this.
Also @spavlin thanks for the extra tool info for updateapp.exe.
I recently pushed an incorrect .cab file to a phone, or so I thought...Iutool will not let you send the same package again if an already higher version one is there or the same version number is there. I found also that if you have full filesystem access you can go to path C:\Windows\servicing\Packages and remove the associated .cat and .mum file for .cab/package file you sent. This will then let you resend the same package or different version of the same .cab/package again.
Click to expand...
Click to collapse
this directory can be protected for write. more correctly edit registry
Correct and why I worded what I wrote with "if". Most folks pushing cabs to their phones are familiar with interop unlocking anyway so figured I would mention that even if it was already known.
Edit: Also I only had to reinstall the same services just different version. I see now your instructions aid in removing everything (drivers reg settings etc.).
Are we using the user system/LocalSystem for this access (telnet/ssh)?
nate0 said:
Are we using the user system/LocalSystem for this access (telnet/ssh)?
Click to expand...
Click to collapse
yes, because other defApps don't have access to same folders and registry values.