So I downloaded pandora's naked rom and started putting in my own programs.
When I hit the BuildOS button, near the end, it gives me an error:
'Error building default.hv and user.hv!
Anybody help?
When errors occur in creating registry process, the window says:”error building default.hv and user.hv!” they are mostly rgu file errors. Please enter temp folder, open log.txt to check which rgu file has problems.
i have the same problem: i've saw the log, and it tells me about a key from a package that i've created. the rgu looks like this:
REGEDIT4
[HKEY_CLASSES_ROOT\.smv]
"Default"="smvfile"
[HKEY_CLASSES_ROOT\smvfile\shell\open\command]
@=""\Storage Card\Program Files\CorePlayer\player.exe" "%1""
[HKEY_CLASSES_ROOT\smvfile\DefaultIcon]
@="\Storage Card\Program Files\CorePlayer\player.exe,0"
[HKEY_CLASSES_ROOT\.sma]
"Default"="smafile"
[HKEY_CLASSES_ROOT\smafile\shell\open\command]
@=""\Storage Card\Program Files\CorePlayer\player.exe" "%1""
[HKEY_CLASSES_ROOT\smafile\DefaultIcon]
@="\Storage Card\Program Files\CorePlayer\player.exe,0"
and in the log i have this ending message:
Failed to parse value name HKEY_CLASSES_ROOT\smvfile\shell\open\command!!!
InitRegistry FAILED in file ".\Registry\f99d2910-9559-4c48-99d0-ea80a73f7659.rgu" within a few lines of line 5.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\f99d2910-9559-4c48-99d0-ea80a73f7659.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
I think,
First, the path should be "\\", not "\", so the main problem is that line 6 should be @=""\\Storage CARD\\Pro..............
Second, the rgu file should be saved as "unicode" code.
And, you should add a blank line at the bottom of the rgu files.
ady_uaic said:
i have the same problem: i've saw the log, and it tells me about a key from a package that i've created. the rgu looks like this:
REGEDIT4
[HKEY_CLASSES_ROOT\.smv]
"Default"="smvfile"
[HKEY_CLASSES_ROOT\smvfile\shell\open\command]
@=""\Storage Card\Program Files\CorePlayer\player.exe" "%1""
[HKEY_CLASSES_ROOT\smvfile\DefaultIcon]
@="\Storage Card\Program Files\CorePlayer\player.exe,0"
[HKEY_CLASSES_ROOT\.sma]
"Default"="smafile"
[HKEY_CLASSES_ROOT\smafile\shell\open\command]
@=""\Storage Card\Program Files\CorePlayer\player.exe" "%1""
[HKEY_CLASSES_ROOT\smafile\DefaultIcon]
@="\Storage Card\Program Files\CorePlayer\player.exe,0"
and in the log i have this ending message:
Failed to parse value name HKEY_CLASSES_ROOT\smvfile\shell\open\command!!!
InitRegistry FAILED in file ".\Registry\f99d2910-9559-4c48-99d0-ea80a73f7659.rgu" within a few lines of line 5.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\f99d2910-9559-4c48-99d0-ea80a73f7659.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Click to expand...
Click to collapse
something like this?
REGEDIT4
[HKEY_CLASSES_ROOT\.smv]
"Default"="smvfile"
[HKEY_CLASSES_ROOT\smvfile\shell\open\command]
@=""\\Storage Card\\Program Files\\CorePlayer\\player.exe" "%1""
[HKCR\smvfile\DefaultIcon]
@="\\Storage Card\\Program Files\\CorePlayer\\player.exe,0"
[HKEY_CLASSES_ROOT\.sma]
"Default"="smafile"
[HKCR\smafile\shell\open\command]
@=""\\Storage Card\\Program Files\\CorePlayer\\player.exe" "%1""
[HKCR\smafile\DefaultIcon]
@="\\Storage Card\\Program Files\\CorePlayer\\player.exe,0"
blank space.
(blank space without nothing, or an empty key?)
i have the same problem. still persists the error. and what do you mean "to be saved as unicode"? it's saved with win ce cab manager.
i've tried also with "default" instead of @. still same problem.
Hello,
I am new to this HTC diamond forum but i want to CID unlock my HTC Diamond with the lokiwiz tool. My HTC is new (1 week old) i followed all instructions given by Ricardo Alfonso but i keep getting these errors.
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
CopyTFFSToFile(0x0, 0x10000, lock_backup.bin)
ERROR: ITReadDisk: outbuf==NULL
reading lock_backup.bin:
This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
ERROR: Unable to open host/destination file - The system cannot find the file sp
ecified.
result=80072746
Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
ECHO is off.
"Standing on the shoulder of giants"
Ricardo Afonso, 2005
WHAT is wrong, anybody any suggestions.........
ERROR: Unable to open host/destination file - The system cannot find the file sp
ecified.
Here's your problem.
Anyways, lokiwiz is for the Wizard.
This tool can be used to either decompile or compile ROMs for various Asus devices that used the ABI firmware format (Can also be used in O2 XDA Zest ). The current version can support P835 unencrypted ABI, and even encrypted ABI from updater EXE! Current finding is this tool also supports unreleased Garmin-Asus ROMs!
Thanks (Especially )Harshal and Leon in AsusPda for testing.
Usage:
- Decompiling ROM
1. p835abisplit2 <abi/exe file>
2. os.nb0 and extrom.img released (Only for Pre-P835 devices), os.nb0 cab be processed by imgfsfromnb or osnbtool, extrom.img can be processed by WinImage.
- Compiling ROM
1. First rename the new os.nb0 to os-new.nb0, and rename extrom.img to extrom-new.img (If the new files do not exist, then the compiler will use the parts from original ROM)
2. p835abisplit2 /b <abi/exe file>
3. out.abi releases, which can be used to flash directly (Only for Pre-P835 devices or Post-P835 devices with unencrypted ROM).
4. If you input the updater EXE to p835abisplit2, it will also produce out.exe with region locked patched which can be used to flash your new ROM directly on devices with any region!
- Note when building ROM
1. If you need to modify XIP, make sure the modded XIP is the same size as the original one before merging back to nb0, otherwise booting will fail
2. For Pre-P835 devices, current version can create big-storage ROMs with variable size of imgfs. If the new OS is smaller than the original one, the freed space will be allocated to user space (The left part as shown in Memory setting) after flashing. However the user space display will only reflect the change on second flash.
3. For Post-P835 devices, all partitions must be exactly same size with the original one (i.e. you need to pad the partition before putting it back), otherwise the device won't boot.
4. For Pre-P835 devices, you can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Final Warning: Customizing a ROM always has risks, I won't be responsible for any damages lead to your custom ROM!
Release Notes:
v2.40:
- Added support for M930
v2.32:
- Support extraction of encrypted ABI file resource from P835 updater exe
- Support reconstruction of P835 updater exe
- When rebuild to exe, the produced out.exe is patched to install in devices of any region.
V2.20:
- Support extration and rebuilding of P835 ABI file (Note that not for ABI inside EXE)
- When rebuild with exe, OUT.EXE will be produced for direct flashing
starkwong said:
This tool can be used to either decompile or compile ROMs for various Asus devices that used the ABI firmware format (Can also be used in O2 XDA Zest ).
Thanks Harshal and Leon in AsusPda for testing.
Usage:
- Decompiling ROM
1. p565abisplit2 <abi/exe file>
2. os.nb0 and extrom.img released, os.nb0 cab be processed by imgfsfromnb or osnbtool, extrom.img can be processed by WinImage.
- Compiling ROM
1. First rename the new os.nb0 to os-new.nb0, and rename extrom.img to extrom-new.img (If the new files do not exist, then the compiler will use the parts from original ROM)
2. p565abisplit2 /b <abi/exe file>
3. out.abi releases, which can be used to flash directly.
- Note when building ROM
1. If you need to modify XIP, make sure the modded XIP is the same size as the original one before merging back to nb0, otherwise booting will fail
2. OS part doesn't need to be the same size as the original. If the new OS is smaller than the original one, the freed space will be allocated to user space (The left part as shown in Memory setting) after flashing. However the user space display will only reflect the change on second flash.
3. You can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Final Warning: Customizing a ROM always has risks, I won't be responsible for any damages lead to your custom ROM!. Moreover, don't use it in P835 abi, it won't work
Click to expand...
Click to collapse
Nice we all waiting for it
Many Congrats for successfully ripping through the ROM !!
Partition offsets and checksums reported by the tool are :
Part #0002 sz:0003e000=>0003e000 cs:625f94b2=>625f94b2 of:000003a0=>000003a0
Part #0004 sz:00100000=>00100000 cs:ffe5f731=>ffe5f731 of:0003e3a0=>0003e3a0
Part #0103 sz:00452a8c=>00452a8c cs:99f65978=>99f65978 of:0013e3a0=>0013e3a0
Part #0104 sz:000fffc0=>000fffc0 cs:5e03943f=>5e03943f of:00590e2c=>00590e2c
Part #0005 sz:07e00000=>07e00000 cs:674f4072=>674f4072 of:00690dec=>00690dec
Part #0013 sz:00a00000=>00a00000 cs:56994bf9=>56994bf9 of:08490dec=>08490dec
I am a little scared to use this tool for following reasons :
1. Actually, the IMGFS & ExtROM offsets are '00690dfc' & '08490dfc' respectively.
2. Checksums( 674f4072, 56994bf9....) can not be located in the Header.
3. The Adler32 checksum for the ExtROM is '5ff94bfa', while your tool reports '56994bf9'.
Any clues ?
rishi2504 said:
Many Congrats for successfully ripping through the ROM !!
Partition offsets and checksums reported by the tool are :
Part #0002 sz:0003e000=>0003e000 cs:625f94b2=>625f94b2 of:000003a0=>000003a0
Part #0004 sz:00100000=>00100000 cs:ffe5f731=>ffe5f731 of:0003e3a0=>0003e3a0
Part #0103 sz:00452a8c=>00452a8c cs:99f65978=>99f65978 of:0013e3a0=>0013e3a0
Part #0104 sz:000fffc0=>000fffc0 cs:5e03943f=>5e03943f of:00590e2c=>00590e2c
Part #0005 sz:07e00000=>07e00000 cs:674f4072=>674f4072 of:00690dec=>00690dec
Part #0013 sz:00a00000=>00a00000 cs:56994bf9=>56994bf9 of:08490dec=>08490dec
I am a little scared to use this tool for following reasons :
1. Actually, the IMGFS & ExtROM offsets are '00690dfc' & '08490dfc' respectively.
2. Checksums( 674f4072, 56994bf9....) can not be located in the Header.
3. The Adler32 checksum for the ExtROM is '5ff94bfa', while your tool reports '56994bf9'.
Any clues ?
Click to expand...
Click to collapse
Tool works properrly.No harm is trying
starkwong, is there any tool to decompile P835's ROM in the same way?
New version posted.
rishi2504:
The image checksum is not calculated by plain Adler32, actually is uses the same formula as older Asus ROMs, however it is not a one-time calculation.
Checksums are inside header, given you decoded it correctly.
starkwong, here's what I get when trying to decompile a ROM:
Code:
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load G5_ALL_V4.11.0_V3.6.12.P2_Ship_WWE_app_MYS00_V2.3.6.exe...
Module loaded, searching for BIN resource...
Found matching resource at BIN #211!
GetPartitions(): Getting Partition Information...
*** Encrypted ABI detected
ABI Version 0x00030012
Project Name: G5
Partition Type: 000f [email protected]
Partition Type: 000e [email protected]
Partition Type: 000e [email protected]
Partition Type: 0004 [email protected]
Partition Type: 0004 [email protected]
Partition Type: 000f [email protected]
Partition Type: 000f [email protected]
Partition Type: 0102 damage [email protected]
Partition Type: 0005 UnKnown [email protected]
Partition Type: 0002 [email protected]
Partition Type: 0003 [email protected]
ProcessABI(): Writing OS data...
* BIN(P835) Image Detected
Warning: OS.nb0/flash.bin is not a NB image, not modifying MSFLSH50 headers
ProcessABI(): No ExtROM partition found.
OK!
So it seems that partitions are not detected correctly, there's no os.nb0 at the output, and the flash.bin apperars to be of no use. Even when I found imgfs partition inside of it, there's still something wrong with it, e.g. bad start block offset, and everything else is also broken.
Can you help me with this?
In fact it is correct, as Asus uses B000FF image on P835, not a plain NB0 image.
You need to use osnbtool to get a nb0 with extra bytes, then use nbsplit -data 2048 -extra 8 to get a nb0 with sector size 0x800.
ginkage said:
starkwong, here's what I get when trying to decompile a ROM:
Code:
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load G5_ALL_V4.11.0_V3.6.12.P2_Ship_WWE_app_MYS00_V2.3.6.exe...
Module loaded, searching for BIN resource...
Found matching resource at BIN #211!
GetPartitions(): Getting Partition Information...
*** Encrypted ABI detected
ABI Version 0x00030012
Project Name: G5
Partition Type: 000f [email protected]
Partition Type: 000e [email protected]
Partition Type: 000e [email protected]
Partition Type: 0004 [email protected]
Partition Type: 0004 [email protected]
Partition Type: 000f [email protected]
Partition Type: 000f [email protected]
Partition Type: 0102 damage [email protected]
Partition Type: 0005 UnKnown [email protected]
Partition Type: 0002 [email protected]
Partition Type: 0003 [email protected]
ProcessABI(): Writing OS data...
* BIN(P835) Image Detected
Warning: OS.nb0/flash.bin is not a NB image, not modifying MSFLSH50 headers
ProcessABI(): No ExtROM partition found.
OK!
So it seems that partitions are not detected correctly, there's no os.nb0 at the output, and the flash.bin apperars to be of no use. Even when I found imgfs partition inside of it, there's still something wrong with it, e.g. bad start block offset, and everything else is also broken.
Can you help me with this?
Click to expand...
Click to collapse
B000FF image cannot be modified without osnbtool or viewbin or cvrtbin tool..For Ext ROM there is no partition in the abi file which can b read as .nb0 Ext ROM is inside the OS and is not as a partition.So what the output u get from the tool is correct.Whatever ROMs u saw mine are from using the same tool
I hope this clarifies.
starkwong, Thank you so much, it worked perfectly!
Can't use this tool on my Asus M530w. Getting this message:
Copyright(C) 2009 Studio KUMA(starkwong). All rights reserved
v2.40 (Jun 16 2009 19:56:06)
ExtractABI(): Trying to load nk.abi...
Failed loading as module (193). Perhaps ABI?
Trying as ABI directly...
Creating file mapping...
GetPartitions(): Getting Partition Information...
Error: AES Key not suitable for this ROM
unencrypted vers encrypted
There is little bit mess in description.
If you will use unecrypted rom + p835abisplit2 you will get os.nb0.
With encrypted rom + p835abisplit2 you will get flash.bin.
starkwong said:
4. For Pre-P835 devices, you can modify ExtROM as you like, but not remove or rebuild the image file, otherwise you may get a brick! (Not able to enter bootloader)
Click to expand...
Click to collapse
Hi,
Can i add my own cab/xml files to this Ext_ROM, after removing the files not needed ?
rishi2504 said:
Hi,
Can i add my own cab/xml files to this Ext_ROM, after removing the files not needed ?
Click to expand...
Click to collapse
Don't bother dude , figured it out ...
Is there anyway I can extract the flash.bin file from a .abi file using this tool?
My P835 is unable to upgrade from the SD card with the .abi file on it.. so I wanted to extract the flash.bin and see if I can use the QPST tool to update the image with flash.bin file..
Sorry if I'm being stupid here (not unusual!). I'm trying to use this tool to get a .abi file out of O2's "Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20.exe" so I can stick it on the SD card and flash the ROM, but of course I'm only ending up with the two files you mention, os.nb0 and extrom.img, no .ABI file. I can look in the extrom.img file with winrar, but the file only contains FINDMA~1.000 (300 bytes), 000dummy.001 (0 bytes) and _setup.xml (1205 bytes).
Plainly I'm thick - where am I going wrong, and how do I get the .ABI file?
Has anyone been able to get the android kitchen to actually work on Fedora 16 and if so, how?
The reason I ask is because it does start and it does find the system.img and boot.img but its complaining during the working folder set up. See below:
Code:
Creating working folder WORKING_112911_011054 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
Chunk size is 2048 bytes in system.img
Spare size calculated to be 64 bytes
Compiling unyaffs ...
In file included from /usr/include/features.h:387:0,
from /usr/include/sys/types.h:26,
from unyaffs.c:10:
/usr/include/gnu/stubs.h:9:27: fatal error: gnu/stubs-64.h: No such file or directory
compilation terminated.
Error: unyaffs not successfully compiled!
Never mind. I fixed it already.
So I'll share. If you run into that error just open up a new terminal and type:
Code:
su -
yum install glibc-devel.x86_64 --disablerepo=adobe\*
Simple enough, lol
sir
wildstang83 said:
Never mind. I fixed it already.
So I'll share. If you run into that error just open up a new terminal and type:
Code:
su -
yum install glibc-devel.x86_64 --disablerepo=adobe\*
Simple enough, lol
Click to expand...
Click to collapse
do you know how to add device in android kitchen?
Did some investigations in bada SDK program folder in my Windows installation.
There I found some well known files.
So there were several *.bin and *.so files.
Obviously the SDK has a structure of a firmware given.
Maybe someone can modify it.
Not enough brain and not enough skills at the moment...
After a emulator run I got this in stdout.txt :
Code:
==================== emulator properties ====================
qemu.path = ../Bin/
qemu.name = badaEmulator.exe
kernel.name = apps.bin
filesystem.fs = FactoryFs_Emul_Wave.img
filesystem.csc = CSC_Emul_Wave.rcs.org
filesystem.rc1 = Rsrc_Emul_Wave.rc1.org
filesystem.rc2 = Rsrc2_Emul_Wave(Low).rc2
reboot = no
use.ide = yes
serial1 = yes
serial1.port = COM90
serial2 = yes
serial2.port = COM91
injector.path = ../EmulatorTools/
injector.name = wxBada_EI.exe
format.needed = no
window.x_pos = 100
window.y_pos = 100
window.scale = 0.5
window.topmost = no
window.maxtouchpoint = 6
=============================================================
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/apps.bin)
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/FS/CSC_Emul_Wave.rcs.org)
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/FS/Rsrc_Emul_Wave.rc1.org)
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/FS/Rsrc2_Emul_Wave(Low).rc2)
[err:aqua:log][read_debug_config_params:118] read_debug_config_params: not find aqua_log.conf((null))
[info:aqua:tty][aqua_tty_init:365] Modem Port is not connected. (Running without 1st -serial option.)
[info:aqua:tty][aqua_tty_init:379] Diag Port is not connected. (Running without 2nd -serial option.)
[info:aqua:audioout][aqua_audio_out_init:538] GetVersion() = 393347078
[info:aqua:popupmenu][SDL_WM_LoadSkinProperties:821] SDL_WM_LoadSkinProperties : loaded.
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/FS/FactoryFs_Emul_Wave.img)
qemu_find_file (C:\Bada_SDK\Model/WaveWVGA/Emulator/FS)
[err:aqua:injector][connect_emulator_manager:375] connect_emulator_manager : EmulatorManager is not running
[err:aqua:injector][event_injector_agent:252] event_injector_agent : connect emulator managaer is failed. event injector not used.
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Images)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Videos)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Sounds)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Images\Camera)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Videos\Camera)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Sounds\Recorded files)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Sounds\Ringtones)
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Tmp_Br_Download)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4OPP)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4FTS)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4FTC)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4OPP)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4FTS)
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\_Temporary_Folder_4FTC)
[warn:aqua:hostfs][print_error:47] Le fichier spécifié est introuvable.
(2)
[err:aqua:injector][connect_emulator_manager:375] connect_emulator_manager : EmulatorManager is not running
[warn:aqua:hostfs][aqua_hostfs_emul:1185] No such file or directory(C:\Bada_SDK\Model\WaveWVGA\Emulator\FS\Media\Others\[email protected]@@[email protected]@@_)
[warn:aqua:hostfs][aqua_hostfs_emul:1255] Unknown error
[info:aqua:wdt][aqua_wdt_write:52] HW_SHUTDOWN - offset(0x0) value(0x2)
We can see the firmware files running. They must be somewhere in SDK
---------- Post added at 12:05 PM ---------- Previous post was at 11:53 AM ----------
Yes it is the firmware files. I tried to change them with another firmware and it don't boot . Now we must find something else...
The firmware files are in :
C:\Bada_SDK\Model\WaveWVGA\Emulator
and C:\Bada_SDK\Model\WaveWVGA\Emulator\FS
Can someone tells me what is FactoryFs_Emul_Wave.img file ?
You must Modify the Boot Files from Firmware
than make you a x86 Kernel for the Firmware
Than make you a ISO:
Boot-Data
Boot-Data
Boot-Data
Firmware Folder
Firmware Folder
Firmware Folder
Firmware Folder
etc.
etc.
Make the ISO bootable than you can use Bada on VM
Thanks guy but no idea how to do this for the moment...
Nevertheless I understand.
It actually is already running in VM. If you browse through SDK files you will find Qemu installation there - that's virtual machine. ;d
Just a question why does the boot files are not in .rc1 or .csc but in .org and .img ??
About *.img
http://forum.xda-developers.com/showthread.php?t=1248417&highlight=bada+sdk
Best Regards
Soxix said:
Just a question why does the boot files are not in .rc1 or .csc but in .org and .img ??
Click to expand...
Click to collapse
It's just a guess, but I think the only difference between .rc1.org and .rc1 is multiloader footer added on the end. That would expand "org" to "original". Back to .img - I think that it's image of filesystem understandable for qemu, allowing to make easy bridge between host filesystem and this virtual one, mounted by qemu. Again difference between this and .ffs&.app would be probably only abit different format, but I'd expect data to be similiar.
Well...
Maybe someone is skilled enough to write a tutorial or a program, that every bada firmware can be mounted with the SDK...
As far as I can see, it should be possible to virtualize it.
1.
IMG is an problem...
You can't extract...
Find first way or Tool to play with bada 2 SDK...
Code:
[B]filesystem[/B].fs = FactoryFs_Emul_Wave.img
2.
Look at apps_compressed.bin... from Firmware
DEcrypt and DEcompress... result is around 48 MB
Code:
[B]kernel[/B].name = apps.bin
apps.bin is much smaller... around 8 MB...
FULL Emulator from Samsung works similar, but in bada SDK are only "Lite Version"...
Kernel is written for bada SDK... this is not for handset...
So many things removed/disabled... in bada SDK...
Best Regards
http://forum.xda-developers.com/showpost.php?p=25640091&postcount=9
Not amazing, but little progress...
Best Regards