hi softworkz or any body
tried open new i-mate image rom with new er2003 and got message:
"Neither 'HTC' nor '921211' nor '0x25863614' nor '0x12345678' seems to be a correct password for the file. If you are sure this is a WM2003 update file you can try to enter an alternative password:"
is there something to be done?
shayon
Use the following:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
http://forum.xda-developers.com/viewtopic.php?t=7392
@Frog
Have you ever try it? can it be done?
Use ER2003 1.16 to open the ROM files, but i dont know how to cook ext-ROM because it differs from the O2 and T-Mobile ROM. Hope someone help on this matter.
Thanks
The extended rom is encoded
to decode try this:
Code:
xda2nbftool -x ms_.nbf ms.nba 0x25863614
del ms_.nbf
ren ms.nba ms_.nbf
to encode again try this:
Code:
ren ms_.nbf ms.nba
xda2nbftool -x ms.nba ms_.nbf 0x25863614
del ms.nba
frog said:
Use the following:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
http://forum.xda-developers.com/viewtopic.php?t=7392
Click to expand...
Click to collapse
guys. it is not working
here :
*********************************************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x25863614
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x12345678
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 921211
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba HTC
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040305
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040304
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040306
WARNING: this does not look like a nbf header, possible you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf
Usage: xda2nbftool [-u] { -c | -e | -d } inputfile outputfile password
-c : calculate crcsum of file
-u : updates the calculated checksum
-e : encrypt inputfile
-d : decrypt inputfile
-x : xor inputfile with password ( should be a number )
-sd : change devicetype
-so : change operatorname
-sl : change language
-sv : change version
-v : verbose
HimaUpgradeUt v0400, v0500 use password HTC
HimaUpgradeUt v0600 uses password 921211
HimaUpgradeUt v0910 uses xor with 0x89124137, 0x25863614 or 0x12345678
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba HTC
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 921211
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x25863614
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x12345678
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040304
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040305
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040306
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>
*************************************************************
i renamed the xda2nbftool.exe to xda2nbf.exe for faster work.
as u can see, i tried all the possible syntaxs, none works....
If anyone has any idea what is going on, please help, i read somewhre on the forum that er2003 V 1.2 is acting up, and that 1.16 is better, i cannot find 1.16 & sure 1.2 is not working, it keeps asking for a password, which I tried all the given ones in the forum, no luck.
awaiting one's responce.
Thank you.
keyboard file
*************************
Hey guys!
After reading through more pages than I'd like to admit and literally trying for hours I have to open this thread hoping that you guys can manage to figure out, what I did wrong trying to create my own WM6.5-ROM for my Blackstone phone.
I used osKitchen 1.1.3 and tried the following packages:
Topaz - WWE OEM/ROM/XIP/NK, 6.5 kernel
28230 [NEW] All Resolutions (DPIs), All Languages (Locales)
All_New SYS_4 - New Sys 28230/23534
I get an error stating the XPI or OEM versions seem incompatible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit:
Also, how can I test my ROMs without flashing them to my precious phone?
I already got the Windows Mobile SDK 6 and the emulator v3 for win x64 but I don't see how it should work.
What am I doing wrong?
You can't use the stuff for the topaz, the kernel has to be the one for blackstone, same for the xip. Also, the folder structure for the XIP is incorrect, the xip must go in a folder with the number of windows mobile build as name. Try importing a blackstone ROM and starting from that.
So, I experimented some further and using
All_New SYS_1 - New Sys 24001/23519/23102/23096
and
-HTC Touch HD-MR_2009-RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship
I even got to cook my own ROM.
But on flashing my Blackstone phone, after 1%, it stops, stating the ROM is not suitable for the device.
View attachment 285098
What did go wrong?
You want to flash without HardSPL?
I used USLP. Is that wrong?
Why does BlackstonecustomRUU state that my ROM consisting only of files for Blackstone is not suitable for the phone?
Ok now... since finally IoDa00 helped me get the what I hope are the right ingredients (for 24001), I managed to cook my own ROM AND even got to flash it to my Blackstone phone successfully (that is without any error messages).
But now, when the Windows Screen should be visible, there is just nothing and the phone is unresponsive...
What did go wrong?
Same prob here!
Even I am stuck with the same issue. I cooked a ROM for my Artemis using the files from Shady's 28005 original microsoft kitchen. I was able to cook the ROM and it loaded on my phone without any errors. But since the, the phone hangs at first screen.
Any advice!
Here's the log of rom cooked:
======================================
Cleaning up
Starting a new build process. Actual Locale: 0409
Configuring kitchen to USE:
DPI: 96
ResH: 240
ResV: 320
Device name: Artemis
Native 6.5 Kernel: False
Creating folders
Copying OEMs...
Copying XIP...
Copying SYS...
Copying EXT and scanning for all add2* files
Applying ROM tweaks...
OK, Letting Device-specific preparations...
Deleting unneeded resolutions in Titanium
Running Platformrebuilder
----------------------------
Running Tool: Resources\Tools\platformrebuilder.exe
Working Folder: Build
Arguments:
PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Feb 15 2009 22:53:49
Building for old kernel!
Build: Premium
Locale: 0409
Preparing release structure...
... done!
Collecting standard packages and initializing hives...
XIP: 3 packages
IMG: 77 packages
... done!
Processing standard packages...
MSXIPKernelLTK
MSXIPKernel
OEMXipKernel
SIM_TKit
SMIME
AlarmSounds
Bth_A2DP
LockscreenEA
DRM
CHome
MediaOS
RUNTIMES
GPSID
SMS_Providers
ppgprov
OneNote
ConfettiCore
BaseAppsFiles
MediaOSFiles
Riched20
IMPORTANT - NetCF3.7.8345.00
Entertainment
Lockscreen
SQLCE
BronzeEA
OSFiles
SYSTEM_DEFAULT_FONTS
bronze
BROWSINGCORE
CommonEA
Metadata
OS
BROWSING
BaseApps
Webview
Office
browsingie
Shell
PhoneRedist
Redist
Phone
Bluetooth
INTERNETSHARING
Base
Base_Lang_0409
Bluetooth_Lang_0409
browsingie_Lang_0409
BROWSING_Lang_0409
Bth_A2DP_Lang_0409
CHome_Lang_0409
Entertainment_Lang_0409
MediaOS_Lang_0409
Office_Lang_0409
OneNote_Lang_0409
PhoneRedist_Lang_0409
Phone_Lang_0409
Redist_Lang_0409
16 - QuickGPS
16 - QuickGPS_Lang
3 - Comm Manager
3 - Comm Manager_Lang
5 - Ringtone Plugin
5 - Ringtone Plugin_Lang
IMPORTANT - Camera + Driver
IMPORTANT - Camera + Driver_Lang
IMPORTANT - Control Panel
IMPORTANT - Control Panel_Lang
IMPORTANT - DRMMiddleware
IMPORTANT - DShow
IMPORTANT - FILES FROM SYS 28005
IMPORTANT - mHubVO
IMPORTANT - Mortscript
IMPORTANT - OEMAPPS
IMPORTANT - OEMDrivers
IMPORTANT - OEMVersion
IMPORTANT - Optimizations
IMPORTANT - Psshutxp
OEM_Lang_0409
OPTIONAL - WLAN + Driver
OPTIONAL - WLAN + Driver_Lang
... done!
Processing extended packages...
zzz_feROM_version_pkg
Failed to parse value name HKEY_CURRENT_USER\ControlPanel\Sounds!!!
... done!
Finalizing and optimizing ROM structure...
... done!
Memory Map...
SLOT 0: 0x02000000 - 0x01df0000 (END: 0x00060000, 0 MODULES)
0x02000000 - 0x01fd0000 - ROM 0
0x01f90000 - 0x01df0000 - ROM 1
SLOT 1: 0x04000000 - 0x026e0000 (END: 0x02020000, 222 MODULES)
RAM IMAGE: 0x8c100000 - 0x8c3ac460
RAM: 0x8c3ad000 - 0x8c3da000 - Used for kernel modules
0x8c3da000 - 0x8fc00000 - 56 MB free
... done!
Donations...
If you're using one of my tools and feel a need to support development
and/or buy me a drink, please feel free to send a donation through PayPal.
Created link in the root of the kitchen.
Updating all files with add2*:
Inserting XIP
----------------------------
Running Tool: Resources\Tools\implantxip.exe
Working Folder: Build\Temp
Arguments: -xip "xip.bin" -payload "OS.nb.payload" -PP 8 -uldr -imgstart 0 -nocert
Implantxip & Payload Resizer v. 1.1 by ervius!!!
BLOCKS SIZE IS: 00010000
ROM Block is : 00000200
ImgStart MIN Val. SETTED - ULDR Reducing...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target Size: 002AC460 AdjSize: 002AFFFF
ULRD in Payload Start:00000400 Size:0030FBFF End:0030FFFF
XIP in Payload Start:00310000 Size:0030FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000
After:
XIP.BIN Target Size: 002AC460 AdjSize: 002AFFFF
ULRD in Payload Start:00000400 Size:0000FBFF End:0000FFFF
XIP in Payload Start:00010000 Size:002AFFFF End:002BFFFF
IMG in Payload Start:002C0000 Size:0000FFFF End:002CFFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000
XIP PagePool Sign not Found!
XIP PagePool from: 4 Mb, to: 8 Mb
XIP Successfully Nocert patched!
Payload resized and XIP Inserted into: OS.nb.payload
Getting IMGFS from NB
----------------------------
Running Tool: Resources\Tools\imgfsfromnb.exe
Working Folder: Build\Temp
Arguments: "os.nb.payload" "imgfs.bin"
ImgfsFromNb 2.1rc2
Sector size is 0x200 bytes
ImgFs partition starts at 0x002c0000 and ends at 0x002d0000
Dumping IMGFS at offset 0x002c0000 (size 0x00010000)
Done!
Generating IMGFS from DUMP
----------------------------
Running Tool: Resources\Tools\imgfsfromdump.exe
Working Folder: Build\Temp
Arguments: "imgfs.bin" "imgfs-new.bin"
ImgfsFromDump 2.1rc2 TURBO with Prefetching and MultiThreading Support, by Plax
Using compression type 'LZX'!
Sector size is 0x200
Total Sectors: 0x119d2
And putting IMGFS into NB
----------------------------
Running Tool: Resources\Tools\ImgfsToNb.exe
Working Folder: Build\Temp
Arguments: "imgfs-new.bin" "OS.nb.payload" "OS-new.nb.payload" -bigstoragemove
ImgfsToNb 2.1rc2
Using bigstorage mode
Sector size is 0x200 bytes
Writing imgfs to offset byte 0x2c0000, sector 0x1600
Padding ImgFs from 0x233a400 bytes (0x119d2 sectors)
to 0x2340000 bytes (0x11a00 sectors)
Not conservative mode. Changing imgfsEnd from 0x2d0000 to 0x2600000
Partition entry before:
File System: 0x25
Start Sector: 0x00001600
Total Sectors: 0x00000080
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x2c
Last Head: 0x7f
Last Sector: 0x01
Last Track: 0x2c
Partition entry after:
File System: 0x25
Start Sector: 0x00001600
Total Sectors: 0x00011a00
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x2c
Last Head: 0x7f
Last Sector: 0x01
Last Track: 0x25f
ImgFs Flash Region log blocks was 0x1, now is 0x234
No Storage Flash Region found!
Done!
Generating NBH
----------------------------
Running Tool: Resources\Tools\htcrt.exe
Working Folder:
Arguments: /buildrom ".\FLASH\ferom.htcrtproj" ".\FLASH\RUU_Signed_0409.nbh"
Cleaning again
DONE! Now you can flash!
======================================
Hey Ondraster... im currently a user of EVK and want to change to OSKitchen... so i did everything to set the SYS as the doctor said... my oem and EXT pkgs too... but i set UPX compression in EXT pkgs... and the log screen turns white like it stops working.. and it says "Doing UPX on EXT directory" and it stucks i leave it almost 30 minues and nothing.... still stucks. I did something wrong?
Thanks for all your pacience man!
Part of my log
Code:
Copied the directory "Sources\EXT\Must_to_Add\AdvancedConfigurationToolv33" to "Build\EXT\Must_to_Add\AdvancedConfigurationToolv33"
Copied the directory "Sources\EXT\Must_to_Add\AdvancedNetwork_1_0_9_0" to "Build\EXT\Must_to_Add\AdvancedNetwork_1_0_9_0"
Copied the directory "Sources\EXT\Must_to_Add\Apps Flashlight" to "Build\EXT\Must_to_Add\Apps Flashlight"
Copied the directory "Sources\EXT\Must_to_Add\Arcsoft_MMS_5_0_31_98R5" to "Build\EXT\Must_to_Add\Arcsoft_MMS_5_0_31_98R5"
Copied the directory "Sources\EXT\Must_to_Add\BOOTLAUNCHER_1_0_35330_2_IOLITE" to "Build\EXT\Must_to_Add\BOOTLAUNCHER_1_0_35330_2_IOLITE"
Copied the directory "Sources\EXT\Must_to_Add\BT_FTP 1_2_29968_1" to "Build\EXT\Must_to_Add\BT_FTP 1_2_29968_1"
Copied the directory "Sources\EXT\Must_to_Add\ConnectionSetupDB" to "Build\EXT\Must_to_Add\ConnectionSetupDB"
Copied the directory "Sources\EXT\Must_to_Add\ConnectionSetup_HTC_ALL" to "Build\EXT\Must_to_Add\ConnectionSetup_HTC_ALL"
Copied the directory "Sources\EXT\Must_to_Add\DeviceUpdate_v2.1.1.1" to "Build\EXT\Must_to_Add\DeviceUpdate_v2.1.1.1"
Copied the directory "Sources\EXT\Must_to_Add\Dopod_SIM_Manager_1436365_by_NiTroGen" to "Build\EXT\Must_to_Add\Dopod_SIM_Manager_1436365_by_NiTroGen"
Copied the directory "Sources\EXT\Must_to_Add\Dummy_FWUPDATE" to "Build\EXT\Must_to_Add\Dummy_FWUPDATE"
Copied the directory "Sources\EXT\Must_to_Add\IP_fix" to "Build\EXT\Must_to_Add\IP_fix"
Copied the directory "Sources\EXT\Must_to_Add\RingtonePlugin_1_00_080624_2" to "Build\EXT\Must_to_Add\RingtonePlugin_1_00_080624_2"
Copied the directory "Sources\EXT\Must_to_Add\USBTOPC" to "Build\EXT\Must_to_Add\USBTOPC"
Copied the directory "Sources\EXT\OLD_OEM\Files" to "Build\EXT\OLD_OEM\Files"
Copied the directory "Sources\EXT\SIP\Keyboard Layout 8525" to "Build\EXT\SIP\Keyboard Layout 8525"
Copied the directory "Sources\EXT\SIP\MSIMAR_96dpi_BlkSkin" to "Build\EXT\SIP\MSIMAR_96dpi_BlkSkin"
Copied the directory "Sources\EXT\SIP\SIPChange" to "Build\EXT\SIP\SIPChange"
Copied the directory "Sources\EXT\Skins_Themes_UI\Z_UI change for 6.5.1" to "Build\EXT\Skins_Themes_UI\Z_UI change for 6.5.1"
Copied the directory "Sources\EXT\Titanium_plugins\lpaso TitaniumCustomizer" to "Build\EXT\Titanium_plugins\lpaso TitaniumCustomizer"
Copied the directory "Sources\EXT\Tweaks\App Buttons" to "Build\EXT\Tweaks\App Buttons"
Copied the directory "Sources\EXT\Tweaks\Performance" to "Build\EXT\Tweaks\Performance"
Copied the directory "Sources\EXT\Tweaks\Registry - Enable Auto TimeZone from Network and icons" to "Build\EXT\Tweaks\Registry - Enable Auto TimeZone from Network and icons"
Copied the directory "Sources\EXT\Tweaks\touchresponse_azharsunny_enchanced sensitivity" to "Build\EXT\Tweaks\touchresponse_azharsunny_enchanced sensitivity"
Copied the directory "Sources\EXT\Tweaks\zz_MODS 651" to "Build\EXT\Tweaks\zz_MODS 651"
Copied the directory "Sources\EXT\Tweaks\z_Icons" to "Build\EXT\Tweaks\z_Icons"
Copied the directory "Sources\EXT\Utilities\xTask" to "Build\EXT\Utilities\xTask"
Doing UPX on EXT directory
Device Hermes, Native 6.5, build 21644.
EDIT:
well i disabled the upx on ext pkgs and now i have platform rebuilder error crash... some XIP or OEM modules incompatibility
BTW as i have native kernel it must say native 6.5 kernel : true... but mine says false :s
am i doing something wrong?
You should not have any others foders in your oemapps, maybe this is the problem. It was in my case
you can not test roms on emulator, only on your phone
sory for my english
somebody helps me Kane159 the define.txt was wrong set...
Nobody xplains how to use it...
I extracted the ops file from onepluscommunityserver.
Now I have a copy of our partition of my oneplus phone.
Which partition is loaded first.
list partition (file *)
DRIVER.ISO: ISO 9660 CD-ROM filesystem data '20150310_103042'
abl.elf: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, no section header
aop.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), statically linked, no section header
cpucp.elf: ELF 32-bit LSB executable, UCB RISC-V, version 1 (SYSV), statically linked, no section header
multi_image.mbn: ELF 32-bit LSB no file type, ARM, version 1 (SYSV)
qupv3fw.elf: ELF 32-bit LSB executable, QUALCOMM DSP6, version 1 (SYSV), statically linked, no section header
shrm.elf: ELF 32-bit LSB executable, Tensilica Xtensa, version 1 (SYSV), statically linked, no section header
storsec.mbn: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, no section header
uefi_sec.mbn: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, no section header
apdp.mbn: ELF 64-bit LSB no file type, ARM, version 1 (SYSV)
devcfg.mbn: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
featenabler.mbn: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, no section header
hypvm.mbn: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, no section header
km41.mbn: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, no section header
mdcompress.mbn: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, no section header
prog_firehose_ddr.elf: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
prog_firehose_lite.elf: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
rtice.mbn: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, no section header
sec.elf: ELF 64-bit LSB no file type, ARM, version 1 (SYSV)
xbl.elf: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
xbl_config.elf: ELF 64-bit LSB executable, AT&T WE32100, version 1 (SYSV), statically linked, no section header
tz.mbn: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, no section header
dspso.bin: Linux rev 1.0 ext4 filesystem data, UUID=af32c008-2a39-7e5b-a5dc-201456d93103, volume name "dsp" (extents) (large files)
metadata.img: Linux rev 1.0 ext4 filesystem data, UUID=c2f8585a-08b5-4d20-b07c-60b309998030 (extents) (large files) (huge files)
persist.img: Linux rev 1.0 ext4 filesystem data, UUID=1dac5d81-33ca-4a59-9947-9cd94eb010fd (extents) (large files) (huge files)
#Partitions in super.img
odm.img: Linux rev 1.0 ext2 filesystem data, UUID=77ca2d3f-a5c4-5835-bda8-1b80c49c79b9, volume name "odm" (extents) (large files) (huge files)
product.img: Linux rev 1.0 ext2 filesystem data, UUID=e5979201-03d0-5d06-bfe6-2f22e88acda2, volume name "product" (extents) (large files) (huge files)
system.img: Linux rev 1.0 ext2 filesystem data, UUID=81cb80e9-4499-5b28-af79-a719c3610a45 (extents) (large files) (huge files)
system_ext.img: Linux rev 1.0 ext2 filesystem data, UUID=e21cf01c-3cd4-55ad-b8b5-50a3403283ae, volume name "system_ext" (extents) (large files) (huge files)
vendor.img: Linux rev 1.0 ext2 filesystem data, UUID=3bc1e464-718e-5437-a242-1e28a67b800d, volume name "vendor" (extents) (large files) (huge files)
gpt_main0.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
gpt_main1.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
gpt_main2.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
gpt_main3.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
gpt_main4.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
gpt_main5.bin: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)
spunvm.bin: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 3, sectors/track 63, heads 255, sectors 16384 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)
logfs_ufs_8mb.bin: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, root entries 512, sectors 1280 (volumes <=32 MB), Media descriptor 0xf8, sectors/FAT 1, sectors/track 1, heads 1, hidden sectors 16, serial number 0xd27355ea, unlabeled, FAT (12 bit)
BTFM.bin: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 3, sectors/track 63, heads 255, sectors 16384 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)
NON-HLOS.bin: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 11, sectors/track 63, heads 255, sectors 84480 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)
opluslog.img: Android sparse image, version: 1.0, Total of 65536 4096-byte output blocks in 10 input chunks.
oplusreserve2.img: Android sparse image, version: 1.0, Total of 32768 4096-byte output blocks in 4 input chunks.
boot.img: Android bootimg, kernel (0x1060e7c), ramdisk (0x62c)
carrier.img: Android sparse image, version: 1.0, Total of 12288 4096-byte output blocks in 4 input chunks.
super.img: Android sparse image, version: 1.0, Total of 2732032 4096-byte output blocks in 331 input chunks.
vm-bootsys.img: Android sparse image, version: 1.0, Total of 65917 4096-byte output blocks in 30 input chunks.
userdata.img: Android sparse image, version: 1.0, Total of 11796480 4096-byte output blocks in 30 input chunks.
abl_log.bin: data/Unknown
android_log.bin: data/Unknown
devinfo.bin: data/Unknown
dtbo.img: data/Unknown
emmc_fw.bin: data/Unknown
engineering_cdt.img: data/Unknown
frp.bin: data/Unknown
gpt_backup0.bin: data/Unknown
gpt_backup1.bin: data/Unknown
gpt_backup2.bin: data/Unknown
gpt_backup3.bin: data/Unknown
gpt_backup4.bin: data/Unknown
gpt_backup5.bin: data/Unknown
hyp_log.bin: data/Unknown
imagefv.elf: data/Unknown
kernel_log16M.bin: data/Unknown
misc.bin: data/Unknown
ocdt.bin: data/Unknown
oem_stanvbk.bin: data/Unknown
oplus_sec.mbn: data/Unknown
param.bin: data/Unknown
qweslicstore.bin: data/Unknown
qsee_log.bin: data/Unknown
splash.img: data/Unknown
vbmeta.img: data/Unknown
vbmeta_system.img: data/Unknown
vbmeta_vendor.img: data/Unknown
vendor_boot.img: data/Unknown
What are you trying to achieve?
I'm trying to understand how it works.
Like windows, it starts from the fat32 partition and loads the c drive.
I just want information on how it starts.
I'm trying to understand how it works.
Like windows, it starts from the fat32 partition and loads the c drive.
I just want information on how it starts.
Can anyone answer me these questions? What does this mean? DOS / MBR boot sector; partition 1: ID = 0xee, start-CHS (0x0,0,1), end-CHS (0x3ff, 255,63), start sector 1, 4294967295 sectors, extended partition table (last)