Long Long Awaited English Windows Mobile 6 Rom for PDAL is finally translated from a chinese rom.
It has:
PCM Keyboard
HTC Album
WM6Storage (Modified Version)
RealPlayer Support For Windows Media Player
Panoramic Scientific Calculator (OEM Calculator is replaced)
Esmertec Java AMS (JeoDek)
Total Commander
Quick Menu
PIM Backup
Advanced Config
PHM Notepad
CeleTask
and a lot more...
Windows Mobile 6 (Professional)
CE OS = 5.2.1236
PAGE POOL = 12 MB
PDAL Rom Unpacking & Packing procedure can be found in my other post which is here...
PDAL_WM6_US-English_CellSmith.zip [Updated Link (Fully Translated & Everything is working)]
More PDAL Roms:
PDAL WM6.0 English Rom Build:5.2.1236
PDAL WM6.1 English Rom Build:5.2.20757
PDAL WM6.1 English Rom Build:5.2.21109
PDAL WM6.5 English Rom Build:5.2.21159
Thanks a ton! I've been waiting for nearly 6 months for this!
Can you please tell us what all tools did you use and how did you go about customizing and translating the ROM? And how much work is remaining? The reason I ask is because you said you were busy, so I feel the best way to get this done fast is to 'open up' the project a bit. Then we all can chip in as and when we get the time.
Final Q: Considering that the PDAL has only 48 MB RAM, wouldn't it be better to use WM5 AKU 3.3+ ? I mean, any idea how much extra RAM does this consume?
[deXter] said:
Thanks a ton! I've been waiting for nearly 6 months for this!
Can you please tell us what all tools did you use and how did you go about customizing and translating the ROM? And how much work is remaining? The reason I ask is because you said you were busy, so I feel the best way to get this done fast is to 'open up' the project a bit. Then we all can chip in as and when we get the time.
Final Q: Considering that the PDAL has only 48 MB RAM, wouldn't it be better to use WM5 AKU 3.3+ ? I mean, any idea how much extra RAM does this consume?
Click to expand...
Click to collapse
Brother deXter,
I am not a chef, cook or Bawarchi, but here is a list of the things i did:
- I unpacked it
- Replaced few MUI (Modules) files
- Used ResEditor on some executables
- Added some registry into default.hv & user.hv and recompiled
- Added few registry tweaks
- Modified initflashfiles.dat
- And finally repacked it
that's all...
Cool, thanks. But what all things are yet to be translated?
[deXter] said:
Cool, thanks. But what all things are yet to be translated?
Click to expand...
Click to collapse
Did you flash your PDAL with this rom yet or just asking ?
Everything is translated by now and link in the first post is also updated.
Flash this rom and let me know if you find anything else...
PDAL has around 50 MB ram and this rom uses 12.5 MB pagepool aperture...
Code:
System Memory Report
====================
Page Size: 4096
| Pages | Size (bytes) | Size (MB) |
Total Storage (Flash) | 11069 | 45339648 | 43.24 |
Available Storage | 9225 | 37788672 | 36.04 |
Used Storage | 1843 | 7550976 | 7.20 |
[B] Physical RAM (sources breakdown) | 12908 | 52871168 | 50.42 |[/B]
Main Memory | 12908 | 52871168 | 50.42 |
Physical RAM (consumers breakdown) | 12908 | 52871168 | 50.42 |
Kernel Prealloc. | 73 | 299008 | 0.29 |
[B]Paging Pool | 3084 | 12632064 | 12.05 |[/B]
Kernel RAM Map | 1 | 4096 | 0.00 |
Watson Size | 75 | 307200 | 0.29 |
Overhead | 3 | 12288 | 0.01 |
Object Store | 8 | 32768 | 0.03 |
Program Memory | 9664 | 39583744 | 37.75 |
AVAILABLE PROGRAM MEMORY | 4690 | 19210240 | 18.32 |
USED PROGRAM MEMORY | 4974 | 20373504 | 19.43 |
Kernel Objects | 349 | 1429504 | 1.36 |
Misc | 114 | 466944 | 0.45 |
Programs | 4511 | 18477056 | 17.62 |
(S) Stack | 311 | 1273856 | 1.21 |
(H) Heap | 1960 | 8028160 | 7.66 |
(E) EXE Data | 32 | 131072 | 0.13 |
(D) DLL Data | 583 | 2387968 | 2.28 |
(c) Code RAM | 454 | 1859584 | 1.77 |
Process | 221 | 905216 | 0.86 |
Module | 233 | 954368 | 0.91 |
(r) Read only RAM | 471 | 1929216 | 1.84 |
Process | 29 | 118784 | 0.11 |
Module | 269 | 1101824 | 1.05 |
Map/Shared | 173 | 708608 | 0.68 |
(W) Read/Write RAM | 700 | 2867200 | 2.73 |
Process | 282 | 1155072 | 1.10 |
Module | 0 | 0 | 0.00 |
Map/Shared | 418 | 1712128 | 1.63 |
What tool do you recommend btw, for flashing the ROM? Also, does this include the radio and extended too?
Sorry, but I'm new at this and can't seem to find any generic guide here.. All the stuff I seem to find are htc or other newer device specific
Why are we PDAL users being ignored? I mean, getting a WM touchscreen device with WiFi, BT w/ A2DP, Quad GSM, Class 10 edge, 2MP camera etc... for just $120 - it's no joke!
[deXter] said:
What tool do you recommend btw, for flashing the ROM? Also, does this include the radio and extended too?
Sorry, but I'm new at this and can't seem to find any generic guide here.. All the stuff I seem to find are htc or other newer device specific
Why are we PDAL users being ignored? I mean, getting a WM touchscreen device with WiFi, BT w/ A2DP, Quad GSM, Class 10 edge, 2MP camera etc... for just $120 - it's no joke!
Click to expand...
Click to collapse
You don't need any special tool to flash your PDAL, Rom Update utility is included, now don't ask me the whole update procedure, which is:
Connect your phone to active and start update utility and click on few "Next" buttons and wait... and it's done...
I have no idea but i bought this phone after my kjam and i found it smarter...
I can't update via the PC as my USB connector is broken
I thought there was a way to directly update by copying it to the SD card?
This is way to change PAGEPOL for I-mate PDAL WM6:
1. Open in HEX editor WMUPDAT.DIP
2. Found HEX code C0 FA 01 14 EB 00 84 A0 3F 01 84 F0 6F D8 08 B2
3. Change 60 FA 01 14 EB 00 84 A0 3F 01 84 F0 6F D8 08 B2
4. Now you will have 6 MB PAGEPOOL
[deXter] said:
I can't update via the PC as my USB connector is broken
I thought there was a way to directly update by copying it to the SD card?
Click to expand...
Click to collapse
Yes you can flash your device from SD, you need format card to FAT16 and copy to the root directory WMUPDAT.DIP
[deXter] said:
I can't update via the PC as my USB connector is broken
I thought there was a way to directly update by copying it to the SD card?
Click to expand...
Click to collapse
Dexter,
Follow these instructions to flash your phone using SD card.
- Format your MicroSD card to FAT16.
- Copy "WMUPDAT.DIP" to your MicroSD card.
- Insert your MicroSD card in your PDAL
- Remove Battery for 5 seconds and install it again.
- Now Press Left Soft & Power Button simultaneously.
Your PDAL will start flashing itself and will be restarted automatically when done.
NOTE: do it at your own risk, I take no responsibility if you damage your device.
Ah, so it's left softkey and power! I knew the general procedure, but tried everything except that (OK and Power, Camera and Power, etc..) How did you figure it out?
Anyways good news is that the ROM flashed sucessfully!
I have a few suggestions/comments/doubts:
1) How do I get back to the default windows SIP? PocketCM makes it impossible for me to do anything!
About modding the ROM:
2) How do you go about replacing the SIP? I want to remove PocketCM permanently and get back the original SIP.
3) What effect does reducing the PagePool have? Does it mean more Storage Memory, or more Main Memory? And would it have any negative effects, like lower performance or maybe lower number of programs running at the same time?
4) Finally, what tools do you guys recommend for working with ROMs? Like I've said before, every guide/tool I find here seems to be HTC/Device specific, so how do I start off? Also, can we test PDAL ROMs in the Windows Mobile Emulator?
Thanks a MILLION pawaa, for being the FIRST person to contribute anything of significance to the cause of the PDAL! Hopefully this would also encourage other developers/modders/cooks? to start coming up with more cool stuff soon. At the least, you can count on me for releasing some stuff in the near future .... as soon as I figure out how
[deXter] said:
Ah, so it's left softkey and power! I knew the general procedure, but tried everything except that (OK and Power, Camera and Power, etc..) How did you figure it out?
Anyways good news is that the ROM flashed sucessfully!
I have a few suggestions/comments/doubts:
1) How do I get back to the default windows SIP? PocketCM makes it impossible for me to do anything!
About modding the ROM:
2) How do you go about replacing the SIP? I want to remove PocketCM permanently and get back the original SIP.
3) What effect does reducing the PagePool have? Does it mean more Storage Memory, or more Main Memory? And would it have any negative effects, like lower performance or maybe lower number of programs running at the same time?
4) Finally, what tools do you guys recommend for working with ROMs? Like I've said before, every guide/tool I find here seems to be HTC/Device specific, so how do I start off? Also, can we test PDAL ROMs in the Windows Mobile Emulator?
Thanks a MILLION pawaa, for being the FIRST person to contribute anything of significance to the cause of the PDAL! Hopefully this would also encourage other developers/modders/cooks? to start coming up with more cool stuff soon. At the least, you can count on me for releasing some stuff in the near future .... as soon as I figure out how
Click to expand...
Click to collapse
Flashing procedure through SD card is very common, so it was not hard enough to find the appropriate key combination...
Congratulations! You are the 2nd in the world who own a PDAL with English WM6 Professional (I haven't seen anyone claiming that he has English WM6 on his PDAL yet...)
Here are the answers to your questions:
1) - After flashing this rom you can install any Sip which can be found around in a cab file, i made this rom for myself and later on decided to share it with other PDAL users so they can enjoy the benefits of WM6 on their PDAL device too. PCMKeyboard does every thing just fine, nothing is missing in it, you can even copy and paste things by keeping enter key pressed and choosing the desired action from the menu... default SIP has very tiny keys which can't be pressed without stylus, so there isn't any point of taking the stylus out even for a single letter entry.
2) - You have to do it manually (like i do).
How to remove PCMKeyboard:
- Remove the following entries from "user.hv" and "default.hv"...
Code:
[HKEY_CURRENT_USER\ControlPanel\Sip]
"DefaultIm"="{F9A103FF-B5E2-4eae-8C34-0ADC26116C4C}"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="COMP IME"
"Ime File"="\\windows\\compime.dll"
[HKEY_CURRENT_USER\ControlPanel\Sip]
"SuggAutoCorr"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9]
"XT9SupportMSSip"=dword:00000000
[HKEY_CLASSES_ROOT\CLSID\{BB25F2EB-688C-4698-ADFC-F422A148AD4F}]
@="PCM Keyboard"
[HKEY_CLASSES_ROOT\CLSID\{BB25F2EB-688C-4698-ADFC-F422A148AD4F}\DefaultIcon]
@="pcmkeyboard.dll,0"
[HKEY_CLASSES_ROOT\CLSID\{BB25F2EB-688C-4698-ADFC-F422A148AD4F}\IsSIPInputMethod]
@="1"
[HKEY_CLASSES_ROOT\CLSID\{BB25F2EB-688C-4698-ADFC-F422A148AD4F}\InprocServer32]
@="\"\\Windows\\pcmkeyboard.dll\""
- Remove the following files from dump directory...
Code:
pcmKeyboard.dll
Default.skin
Dream.skin
Touch.skin
Light Blue.skin
Simple White.skin
English (small).dict
French (small).dict
German.layout
Polish.layout
Russian.layout
Spanish.layout
Czech.layout
English.layout
Français.layout
Now PCMKeyboard is completely removed from the rom.
You can add any SIP by following these instructions...
- Find your desired SIP package or CAB file (in the case of CAB file you need to unpack it's files and registry).
- Add files to dump folder.
- Add your SIP's registry entries in default.hv / user.hv files. ([HKEY_CURRENT_USER] entries in user.hv and [HKEY_CLASSES_ROOT] & [HKEY_LOCAL_MACHINE] entries in default.hv)
- Set it as your default SIP by adding it's CLSID in user.hv as following and you are done with SIP.
Code:
[HKEY_CURRENT_USER\ControlPanel\Sip]
"DefaultIm"="{CLSID-OF-YOUR-SIP}"
3) - It is said that...
Code:
The "page pool" is essentially cache between the storage ram (where all the db/binaries are written to) and the program ram. certain things have to be loaded into the pagepool before executing in program/main ram. So in general, increasing the pagepool usually speeds up launching applications, however it reduces the actual program ram so you can't run as many things at the same time...
(Copyrights 2007 harwantgrewal)
It really doesn't matter much if you have a 10MB, 8Mb or 6MB Page Pool.
As far as speed and performance is concerned,you can hardly find much of a difference between a 10Mb page pool or 6Mb,it's hardly noticeable over all.So just keep what the cooker has specified in the Rom.Nothing to worry,just enjoy the magic created by the magnificent cookers...
(Copyrights 2007 zabardast_1)
4) - There are a lot of tools you can use to manipulate a rom when it's in a binary file, all you have to do is "To take it's binary out of the ROM", rest of the procedure is same in all devices except partitions structure & memory addresses.
Here is the unpacking and packing procedure for PDAL roms...
Required tools are attached with this post with the name of "PDAL_Packing.Unpacking.Tools.zip", download it and extract it to a folder (Suppose "PDAL")
Unpacking Procedure:
- Place "WMUPDAT.DIP" in the folder "PDAL"
- Execute Unpack.bat, wait and when it's done you will have dump folder to play with.
Packing Procedure:
- Replace/Add/Modify any File/Registry/Package/Module in the dump folder.
- Execute Pack.bat and wait, when it's done you will have updated "WMUPDAT.DIP" file ready to be flashed...
That's all buddy, you can try loading binary rom into an emulator and here is a link to Emulator Rom Kitcken
I don't think that anybody else would cook a rom for PDAL unless he don't own a PDAL device, because they are cooking for their own devices only...
NOTE: Don't mess the things up and don't ask any newbie question which is already answered in this forum, 3 out of 4 of your questions were already asked and answered in this forum long time ago, so please search-a-lot before asking any question, like i do...
(Copyright 2008 CellSmith)
THanks THanksTHanks
THanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanks
No support Thai Launge
sunwork2 said:
THanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanksTHanks
Click to expand...
Click to collapse
WelcomeWelcomeWelcomeWelcomeWelcomeWelcomeWelcome... (LOL)
buledog36 said:
No support Thai Launge
Click to expand...
Click to collapse
Yes, No Thai language, for other then English languages, you are on your own...
sir pawaa
thank you very much and best regards for you.
pawaa said:
Brother deXter,
I am not a chef, cook or Bawarchi, but here is a list of the things i did:
- I unpacked it
- Replaced few MUI (Modules) files
- Used ResEditor on some executables
- Added some registry into default.hv & user.hv and recompiled
- Added few registry tweaks
- Modified initflashfiles.dat
- And finally repacked it
that's all...
Click to expand...
Click to collapse
Hi Mr pawaa
what tools you used for edit or modify for Modules ?
can you upload here your resource editor or other tools for edit Modules.
best regards
PATMAP said:
Hi Mr pawaa
what tools you used for edit or modify for Modules ?
can you upload here your resource editor or other tools for edit Modules.
best regards
Click to expand...
Click to collapse
Search Google for "ResEditor" and you will find it...
Related
New Visual Kitchen for PRB Continuous update
This is a new tool based on bepes PRB(platformrebuilder.exe), simpler and more suitable for novice to use.
Is a function of PRB expansion, OEM package can be selected.Easier to use than the EVK,
Support the HTC family of devices,Samsung_i90X test is successful,Other devices Unknown...
Update:
20-oct: Updated to the full English version, by adding more features in
25-oct: Add more device support, custom insert XIP, multi-language support, etc.
31-oct: add Edition Custom(Press the left directory, point MOUSE right, you can customize version)
09-Nov: add support LZX compression, use osnbtool to insert...
25-Nov: New UI,add save,load config. (Update_25_Nov.zip)
27-Nov: Fix dump NBH, NB tools bug, (Update_27_Nov.zip)
06-Dec: fix UI
15-Dec: add dump dio and nb0 ,TOOLS folder and procedures need to be replaced...
24-Dec: Major update, amend the kitchen to start slow problem, speed over 90%. Sound file editor functions, this version of the file editor functionality is already enough to use. View and edit rgu, reg, txt, xml, provxml, etc. ....
Merry Christmas
01-Jan:fix bug,add support select NK version.
10-Jan:fix bug ,Support the htcrt NB conversion NBH added in Radio.nb and Splash.nb...
24-Jan:build maximize the LOG window, Samsung's device can use the generic version of TOOLS, but to re-switch in the Advanced settings click the type of device.
Download:
update_09-Nov: http://hotfile.com/dl/17071498/77b2706/Kitchen_I90X.rar.html for Samsung devices (only I90x)
update_09-Nov: http://hotfile.com/dl/17067073/cdd8b2b/update_1109.rar.html for htc all devices
updata_31-oct : http://hotfile.com/dl/16268204/d6fd8bb/update_1031.zip.html
chs edition : http://www.darkforcesteam.com.cn/thread-155-1-2.html
eng edition : Attached Files PRB.zip and Tools.zip, Unzip into the same folder
Kitchen sample(P4550): http://www.rayfile.com/files/5390ad47-a5aa-11de-866f-0014221f469f/
10_Jan:http://hotfile.com/dl/23594625/ad18373/Kitchen_Update_10_Jan.zip.html
Basic kitchen (rapidshare premium link): http://rapidshare.com/files/333007755/Kitchen_Update_10_Jan.zip (Thanks zakengen)
Thanks to:
bepe for his platformrebuilder.exe
Ervius for his implantxip.exe
Donate：
If you think this tool is good, you can donate this project.thanks.
Contact me：
MSN: [email protected]
MAIL: [email protected]
rapidshare is a need for paid, free can only be downloaded 10 times. Can only use hotfile
VK Kitchen Frame:
Kitchen_RK
|
|_ EXT (EXT format OEM packages, fonts, tools, patches....)
| |_ Software
| | |_ app1
| | |_ app2
| |_ Tool
| |_ Fix
| |_ Polaris (Official OEM packages, cameras, audio manager, etc.)
|
|_ OEM (Current OEM device drivers)
| |_ BuildInfoPkg
| |_ ConfigAP
| |_ ExtendedPkg
| |_ OEM_DPI_96
| |_ OEM_Lang_0409
| |_ OEMDrivers
| |_ OEMMISC
| |_ OEMOPERATORS
| |_ OEMVERSION
| |_ OperatorPKG
| |_ OperatorPKG_PT
|
|_ RELEASE
| |_ Ruu.exe (ROM is written to your mobile phone tool, please rename RUU.exe)
|
|_ ROM (XIP)
| |_ 21055 (MS Kernel version number)
| | |_ MSXIPKernel (MS XIP Kernel )
| |
| |_ 21850
| | |_ MSXIPKernel
| |
| |_ XIP
| | |_ MSXIPKernelLTK
| | |_ OEMXIPKernel (OEM XIP Kernel )
| | |_ WinCENLS_WWE
| |
| |_ os.nb.payload or os.nb
| |_ romhdr.bin
|
|_ SYS
| |_21055
| |_21850 (SYS Kernel )
| | |_ Base_DPI_96
| | |_ base_dpi_96_resh_240_resv_320
| | |_ Base_Lang_0804
| | |_ Base_Lang_0804_DPI_96
| | |_ Base_Lang_0804_DPI_96_RESH_240_RESV_320
| | |_ BaseApps
| | |_ BaseAppsFiles
| | |_ .......
|_ TOOLS (Kitchen tools)
| |_IMGFS (all tools)
| |_Projects (save VK project )
| |_NK (all NK)
| | |_6.1NK (6.1NK)
| | | |_nk.exe
| | |_6.5NK (6.5NK)
| | |_nk.exe
| |_SplashScreen (all SplashScreen)
Update Kitchen Kernel :
XIP: In the ROM directory New Folder, rename the XIP kernel version, copy the new MSXIPKernel.( for example: ROM\23008\MSXIPKernel)
SYS: Copy the new SYS to the kitchen SYS directory, rename the version number( for example: 23008,SYS\23008),Simpler, no need to convert other formats..
Support multiple versions of NK in the switch in the Advanced Settings to open multi-NK.
Use the steps:
1. Download this Kitchen.rar, unzip it to your disk,
2. Refer to EXT, OEM, ROM, SYS folder structure to EXT, OEM, ROM, SYS replaced by the new version.
3. Alternative RELEASE brush machine tools, it would be renamed as Ruu.exe.
4. Open the DIY ROM Utility.exe, to set the screen, SET paths and patterns \ Ext TYPE = Ext \ * \ *.
5. To change the menu SYS or XIP, began to compile (build).
XIP inserts settings (recommended)
1.PRB default: (..\TOOLS\implantxip xip.bin OS.nb.payload)
A: Set Nb type=os.nb.payload ; set extra=NBMerge ; set NBMerge=Kaiser ; set tool=Imgfs_xxx
B: Set Nb type=os.nb ; set extra=osnbtool ; NBMerge not set ; set tool=osnbtool
2.EVK mode:
A: Nb type is os.nb.payload ; set extra=NBMerge ; set NBMerge=Kaiser ; set tool=Imgfs_xxx
3.osnbtool: (..\TOOLS\osnbtool -c OS.nb.payload 1 xip.bin)
A: Set Nb type=os.nb ; set extra=osnbtool ; NBMerge not set ; set tool=osnbtool
I recommend using OSNBTOOL, it can automatically adjust NB partition size, free up space.
thanx, i will try
what's the difference with New Visual Kitchen (Ervius)?
isn't Ervius edition...
This is a new tool based on Bepe PRB(platformrebuilder.exe), more simple, suitable for novice to use...
Looks good...is there an english version?
looks awesome, a little rough around the edges but i love it so far! thank you for your work!
OMG, great work. Thanks so much.
And, what runtimes needed to run this kitchen? And please update new version with quite English.
nhathoa said:
OMG, great work. Thanks so much.
And, what runtimes needed to run this kitchen? And please update new version with quite English.
Click to expand...
Click to collapse
Has been updated, please update the file, replace the same file, remove the extra language files(cht or chs)
Thank you use and testing, would welcome more good ideas...
How hard is it to migrate a ERV Kitchen to this new version?
Asphyx said:
How hard is it to migrate a ERV Kitchen to this new version?
Click to expand...
Click to collapse
Similar to the EVK (erviuskitchen.exe), it is easier to use a new version of the tool, please refer to the use of image structure transplant.
Asphyx said:
How hard is it to migrate a ERV Kitchen to this new version?
Click to expand...
Click to collapse
I think you don't need to do so... This kitchen tool is for the people who still wants to use OEM packages but want prb
getting:
ERROR! (errorlevel: -1073740777)
cnzqy1 said:
I think you don't need to do so... This kitchen tool is for the people who still wants to use OEM packages but want prb
Click to expand...
Click to collapse
Full PRB format, just click picture to change the structure of ROM and SYS
is it possible to have a rapidshare mirror for the eng kitchen?
thx
greets
Is it possibile to have other localization settings? Like 0407,0410 ect....
Nice.
May I use it for Prophet?
It is not included
this program is cool, just one situation, i can´t work in fullscreen there´s no max buttom, with my screen resolution i can´t see the all buttons.
great job simple, easy to use.
sorry my english
zoko said:
this program is cool, just one situation, i can´t work in fullscreen there´s no max buttom, with my screen resolution i can´t see the all buttons.
great job simple, easy to use.
sorry my english
Click to expand...
Click to collapse
In my case its the same, I also cant see all the buttons and the windows cant be re dimensioned.
Anyways, wassup zoko, how u doing haven't seen u in a long time.
Regards
well, seems to be a good work, and with times, and users suggestions, it could be ever better than now
bye!
wow looks nice ! it would be grate to remade this kitchen to samsung omnia users too... i can help with this vistang Check you PM
br
Hi All,
For the curious here's a diffstat between the EG30 and EK02 kernels. From my first look the changes to dpram (recovery functions) and the wimax drivers are the most interesting. I've pastebin'd the driver files diff at pastebin dot com slash 3eskK04d (I'm a new user so I can't post links yet sorry!)
My first post, I hope it's useful!
Code:
arch/arm/Kconfig | 15
arch/arm/configs/c1_fips_rev02_defconfig | 1
arch/arm/configs/c1_rev00_defconfig | 1
arch/arm/configs/c1_rev00_na_spr_epic2_defconfig | 1
arch/arm/configs/c1_rev00_q1_defconfig | 1
arch/arm/configs/c1_rev01_defconfig | 1
arch/arm/configs/c1_rev01_jpn_ntt_defconfig | 1
arch/arm/configs/c1_rev01_kor_skt_defconfig | 1
arch/arm/configs/c1_rev02_c1q1_defconfig | 1
arch/arm/configs/c1_rev02_chn_defconfig | 1
arch/arm/configs/c1_rev02_defconfig | 1
arch/arm/configs/c1_rev02_jpn_ntt_defconfig | 1
arch/arm/configs/c1_rev02_kor_skt_defconfig | 1
arch/arm/configs/c1_rev02_na_spr_defconfig | 6
arch/arm/configs/c1_rev02_q1_defconfig | 1
arch/arm/configs/c1_rev02_talbot_defconfig | 1
arch/arm/configs/c1_rev02_usa_att_defconfig | 1
arch/arm/configs/c1_rev05_na_spr_defconfig | 11
arch/arm/include/asm/cacheflush.h | 9
arch/arm/include/asm/hardware/cache-l2x0.h | 1
arch/arm/include/asm/pgtable.h | 26
arch/arm/include/asm/smp_plat.h | 4
arch/arm/include/asm/tlbflush.h | 12
arch/arm/mach-s5pv310/c1-wimax.c | 11
arch/arm/mach-s5pv310/mach-c1.c | 31
arch/arm/mach-s5pv310/tmu.c | 316
arch/arm/mm/cache-l2x0.c | 6
arch/arm/mm/copypage-v4mc.c | 2
arch/arm/mm/copypage-v6.c | 2
arch/arm/mm/copypage-xscale.c | 2
arch/arm/mm/dma-mapping.c | 6
arch/arm/mm/fault-armv.c | 8
arch/arm/mm/flush.c | 46
drivers/bluetooth/bthid/bthid.c | 10
drivers/dpram/raffaello/dpram.c | 124
drivers/dpram/raffaello/dpram_recovery.c | 381
drivers/dpram/raffaello/dpram_recovery.h | 12
drivers/input/misc/cm3663.c | 9
drivers/input/touchscreen/mxt224_u1.c | 265
drivers/misc/sec_jack_spr.c | 2
drivers/mmc/card/block.c | 132
drivers/mmc/core/sdio.c | 83
drivers/mmc/core/sdio_ops.c | 34
drivers/mmc/core/sdio_ops.h | 3
drivers/net/wimax_cmc/hardware.c | 66
drivers/net/wimax_cmc/receive.c | 1
drivers/net/wimax_cmc/wimax_i2c.c | 1539
drivers/net/wimax_cmc/wimax_i2c.h | 88
drivers/net/wimax_cmc/wimax_sdio.c | 104
drivers/net/wireless/bcm4330/src/wl/sys/wl_iw.c | 1
drivers/serial/samsung.c | 2
drivers/staging/westbridge/astoria/api/src/cyaslowlevel.c | 7
drivers/staging/westbridge/astoria/device/cyasdevice.c | 20
drivers/staging/westbridge/astoria/device/cyasdiagnostics.h | 1
drivers/staging/westbridge/astoria/include/linux/westbridge/cyanch9.h | 8
drivers/staging/westbridge/astoria/include/linux/westbridge/cyasch9.h | 5
include/config/auto.conf | 893
include/config/auto.conf.cmd | 640
include/config/kernel.release | 1
include/config/tristate.conf | 310
include/generated/autoconf.h | 894
include/generated/mach-types.h |38179 ----------
include/generated/utsrelease.h | 1
include/linux/i2c/mxt224_u1.h | 21
include/linux/version.h | 2
include/linux/wimax/samsung/wimax732.h | 4
scripts/basic/docproc | 44
scripts/basic/fixdep | 41
scripts/basic/hash | 12
scripts/conmakehash | 39
scripts/genksyms/genksyms | 135
scripts/genksyms/keywords.c | 220
scripts/genksyms/lex.c | 2709
scripts/genksyms/parse.c | 2353
scripts/genksyms/parse.h | 139
scripts/kallsyms | 65
scripts/kconfig/conf | 298
scripts/kconfig/lex.zconf.c | 2429
scripts/kconfig/zconf.hash.c | 239
scripts/kconfig/zconf.tab.c | 2468
scripts/mod/elfconfig.h | 4
scripts/mod/mk_elfconfig | 28
scripts/mod/modpost | 165
This is what I have been asking about and I can't understand it..lol. I have never seen such a performance boost between stock kernels. Hopefully someone will explain what exactly has changed in simpler terms but thank you nonetheless.
Sent from my SPH-D710 using xda premium
so does this update us to 2.3.6?
delfin12 said:
so does this update us to 2.3.6?
Click to expand...
Click to collapse
This is just the kernel source diff. The full EK02 update includes an update to Android 2.3.6
I would guess a performance increase is related to the CPU cache fixes.
As in the workaround for erratum 753970 PL310 (r3p0) config ARM_ERRATA_753970
Under some condition the effect of cache sync operation on
the store buffer still remains when the operation completes.
This means that the store buffer is always asked to drain and
this prevents it from merging any further writes. The workaround
is to replace the normal offset of cache sync operation (0x730)
by another offset targeting an unmapped PL310 register 0x740.
This has the same effect as the cache sync operation: store buffer
drain and waiting for all buffers empty.
Click to expand...
Click to collapse
This woudl probably get more attention in the dev section I think it would be fitting for that area... correct me if I'm wrong.
mauricehall said:
This woudl probably get more attention in the dev section I think it would be fitting for that area... correct me if I'm wrong.
Click to expand...
Click to collapse
yeah, but i can't post there yet as a n00b.
JohnCorleone said:
This is what I have been asking about and I can't understand it..lol. I have never seen such a performance boost between stock kernels. Hopefully someone will explain what exactly has changed in simpler terms but thank you nonetheless.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
So if I flash the EK02 rom/kernel and I'm on EG31 radio, would I still see the speed benefits?
mauricehall said:
This woudl probably get more attention in the dev section I think it would be fitting for that area... correct me if I'm wrong.
Click to expand...
Click to collapse
Chris already posted the diff in the Dev forum.
It's great to be able to set up apps with individual display settings through Paranoid Android's built in utilities. The problem is that it often takes a lot of trial and error to get just the right size. I wanted to start a list of Apps and their settings for the Galaxy S3 and its 4.8 inch screen, sourced from the community. It will certainly make setup significantly faster and easier. Please post any Apps that you have I'll add them to the list.
AppName | Size | Layout | Force | Large Screen
The List:
Gallery | 250 | 600px | No | No
GMail | 250 | 600px | No | No
Google Search (Now) | 250 | 500px | No | No
Netflix | 250 | 720px | No | Yes
Play | 250 | 540px | No | No
I started this thread in the international version's App's and Themes section, and that should really be the master list because the settings apply to any GS3, but I'll keep updating the list here too.
link to that thread: http://forum.xda-developers.com/show...php?p=30042353
OK you want people to post the apps DPI and what mode its on ?
Sent from my SPH-L710 using Tapatalk 2
My primary goal is to get to the point where we can unbrick a Glide using download mode and heimdall, no matter what the rest of the MMC looks like. A secondary goal is to learn enough about the boot process and bootloader to be able to arbitrarily change the partition table without bricking the phone.
So, this is currently our best guess as to the stock partition layout on the Glide:
Code:
DM ID | offset | DM Name | DM filename | Device file | filesystem
======|=============|=========|=================|==============|===========
2 | Special | BCT | bct.bin | |
3 | 0x200000 | PT | | |
4 | 0x280000 | EBT | bootloader.bin | |
5 | 0x480000 | EB2 | | |
6 | 0x680000 | GP1 | fusetrigger.bin | |
7 | 0xa80000 | EFS | efs.img | mmcblk0p1 | ext4
8 | 0x1680000 | APP | factoryfs.img | mmcblk0p2 | ext4
9 | 0x26e80000 | CAC | cache.img | mmcblk0p3 | ext4
10 | 0x3a680000 | IMS | | mmcblk0p4 | FAT32
11 | 0x12a700000 | MSC | | mmcblk0p5 |
12 | 0x12a900000 | UDA | data.img | mmcblk0p6 | ext4
13 | 0x1aa900000 | MDM | modem.bin | mmcblk0p7 |
14 | 0x1ab900000 | SOS | recovery.img | mmcblk0p8 |
15 | 0x1abe00000 | LNX | boot.img | mmcblk0p9 |
16 | 0x1ac600000 | OTA | | mmcblk0p10 |
17 | 0x1ace00000 | HID | hidden.img | mmcblk0p11 | ext4
18 | 0x1cce00000 | GPT | | |
I do not presently know how mmcblk0boot0 and mmcblk0boot1 factor into things. I DO know that whatever mmcblk0boot0 is, it's not accessible through mmcblk0, meaning there's something a bit weird going on in the kernel MMC driver... see the hypotheses below. The contents of mmcblk0boot1 occur THIRTEEN times in the beginning of mmcblk0, including right at 0x0. boot1 could point to any one of those, or, again, a different location entirely that's obscured by the kernel driver.
A PIT is NOT a partition table. It's a descriptor of expected partitions and their sizes. There's no offsets or anything that could describe partition locations. So when you feed Odin or Heimdall a PIT, either Odin/Heimdall or the phone itself is making up a partition table on the fly to fit the PIT. Needless to say, flashing a PIT without a bootloader and recovery is risky, even if you're flashing the same PIT twice! it appears the partition table is created in a predictable way; that's how we got the new offsets. But, I'm still way too paranoid to flash a PIT without reflashing BCT, bootloader, and either recovery or download mode in the same go.
Download mode is DEFINITELY in the MMC. Check out the strings around 0x572400. So much for the "separate ROM" theory. There's strings from the bootloader nearby as well (note to self: HOW nearby? That could be crucial...).
BCT is a special something used only by Tegra SoCs: http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html It's a safe bet there's a BCT somewhere in MMC. The BCT should, in theory, give us the precise location of the bootloader, and then some proper disassembly can happen. Assuming our offsets are correct, we now theoretically know the location of everything. Let the dumping begin! Still, picking apart a BCT sounds absolutely smashing so I'll probably do it at some point anyway.
Hypotheses that need testing:
boot0 and boot1 contain BCTs, not bootloaders. (That would explain their size.)
mmcblk0 actually begins exactly 1MB into the MMC. boot0 and boot1 are two halves of that first 1MB.
Alternately, boot0 points to the copy of the BCT that is in RAM; a leftover of the boot process. boot1 is the actual BCT from the MMC.
There are 13 (or 15) copies of the BCT at the beginning of MMC. (In the BCT partition, of course!) Is this necessary? Probably not, but I'm not gonna possibly brick a phone to gain a few KB.
Download mode is built into the bootloader, not a separate binary. Both live in EBT. The newly found offsets put the Odin strings in EB2, so BUSTED.
EBT is the bootloader and EB2 is the Odin code.
In my opinion this topic can and should stay in the development section.
However there are no downloadable file as a result of the development, the topic holds information valuable mostly for developers, debuggers or power users, and average end users obviously has no or minimal idea what to do with the information provided here.
By the way, shall i ask a request? I'd like to see the default mounting points of those partitions witch has any. For the everyday Glide users it may be obvious, but quite often i fix broken partition tables of different phones for example, where such information can be valuable for people with no device specific routine.
Necc86 said:
By the way, shall i ask a request? I'd like to see the default mounting points of those partitions witch has any. For the everyday Glide users it may be obvious, but quite often i fix broken partition tables of different phones for example, where such information can be valuable for people with no device specific routine.
Click to expand...
Click to collapse
It's kinda beyond the scope of this project; you can get this from the volds.fstab of any ROM. Frankly, though, it should be somewhat obvious from the Odin filenames.
Bump because update.
I have done an extended analysis of the FFU file of Windows Mobile 10 for Xiaomi Mi4.
The partition layout is not the same from Android and Windows Phone. But, some partitions have the same starting LBA, ending LBA and size so they are at the same location and have the same size in both partition layouts. Because the FFU doesn't contain data blocks to write in these partitions, we can assume they stay intact during the update from Android to Windows Mobile.
This way I found out that 5 partitions are kept from Android, 13 are written with data and 6 are nulled (content is all zeroes):
Code:
+-----+-----------+-----------+--------+-----------------+---------+-------------------+
+ # | Start LBA | End LBA | Size | Name | In FFU | Status |
+-----+-----------+-----------+--------+-----------------+---------+-------------------+
| 0| 1024| 2047| 1024|SBL1 | Yes | Written |
| 1| 2048| 2559| 512|UEFI_BS_NV | Yes | Nulled |
| 2| 3072| 3583| 512|UEFI_RT_NV | Yes | Nulled |
| 3| 4096| 8191| 4096|UEFI | Yes | Written |
| 4| 8192| 10239| 2048|DDR | | Kept from Android |
| 5| 10240| 12287| 2048|SSD | | Kept from Android |
| 6| 12288| 14335| 2048|PADDING0 | Yes | Nulled |
| 7| 14336| 30719| 16384|DPP | Yes | Written |
| 8| 30720| 30783| 64|DBI | Yes | Written |
| 9| 31744| 32743| 1000|RPM | Yes | Written |
| 10| 32768| 33767| 1000|TZ | Yes | Written |
| 11| 33792| 34815| 1024|WINSECAPP | Yes | Written |
| 12| 34816| 67583| 32768|TZAPPS | Yes | Written |
| 13| 67584| 68607| 1024|BACKUP_SBL1 | | |
| 14| 68608| 68671| 64|BACKUP_DBI | | |
| 15| 69632| 73727| 4096|BACKUP_UEFI | | |
| 16| 73728| 74727| 1000|BACKUP_RPM | | |
| 17| 74752| 75751| 1000|BACKUP_TZ | | |
| 18| 75776| 76799| 1024|BACKUP_WINSECAPP | | |
| 19| 76800| 109567| 32768|BACKUP_TZAPPS | Yes | Nulled |
| 20| 109568| 117759| 8192|MMOS | Yes | Written |
| 21| 117760| 131071| 13312|PADDING1 | | |
| 22| 131072| 134143| 3072|MODEM_FS1 | | Kept from Android |
| 23| 134144| 137215| 3072|MODEM_FS2 | Yes | Nulled |
| 24| 137216| 137247| 32|MODEM_FSC | Yes | Nulled |
| 25| 138240| 154623| 16384|PLAT | Yes | Written |
| 26| 154624| 220159| 65536|EFIESP | Yes | Written |
| 27| 220160| 262143| 41984|PADDING2 | | |
| 28| 262144| 265215| 3072|MODEM_FSG | | Kept from Android |
| 29| 265216| 491519| 226304|PADDING3 | | |
| 30| 491520| 524287| 32768|PERSIST | | Kept from Android |
| 31| 524288| 5537791| 5013504|MainOS | Yes | Written |
| 32| 5537792| 20967423|15429632|Data | Yes | Written |
+-----+-----------+-----------+--------------------------+---------+-------------------+
Regarding the partitions which are in the FFU file, here are all the information I gathered about them:
"SBL1" is a SBL (Secondary Boot Loader) file with a 80 bytes header
The file is not signed (no signature and no certificate chain).
Codeword[4]: d1dc4b84
Magic[4]: 3410d773
Image ID[4]: 15000000 (SBL1_IMG)
Reserved 1[4]: ffffffff
Reserved 2[4]: ffffffff
Image source[4]: 50000000
Image destination pointer[4]: 00c000f8 (4160798720)
Image size[4]: f8480400
Code size[4]: f8480400
Signature pointer[4]: f80805f8 (4161079544)
Signature size[4]: 00000000 (0)
Certificate chain pointer[4]: f80805f8 (4161079544)
Certificate chain size[4]: 00000000 (0)
OEM root certificate selelected[4]: 01000000
OEM number of root certificates[4]: 01000000
Booting image config[4]: ffffffff
Reserved 6[4]: ffffffff
Reserved 7[4]: ffffffff
Reserved 8[4]: ffffffff
Reserved 9[4]: ffffffff
"UEFI_BS_NV" is an empty partition
"UEFI_RT_NV" is an empty partition
"UEFI" is probably an ARM binary file with a 40 bytes header
The file is not signed (no signature and no certificate chain).
Image ID[4]: 05000000 (APPSBL_IMG)
Flash partition version[4]: 03000000
Image source[4]: 00000000
Image destination pointer[4]: 00002000 (2097152)
Image size[4]: 00800d00
Code size[4]: 00800d00
Signature pointer[4]: 00802d00 (2981888)
Signature size[4]: 00000000 (0)
Certificate chain pointer[4]: 00802d00 (2981888)
Certificate chain size[4]: 00000000 (0)
"PADDING0" is an empty partition
"DPP" is a FAT partition
"DBI" is probably an ARM binary file with a 40 bytes header
The file is not signed (no signature and no certificate chain).
Image ID[4]: 1e000000
Flash partition version[4]: 03000000
Image source[4]: 00000000
Image destination pointer[4]: 000080fe (4269801472)
Image size[4]: 982d0000
Code size[4]: 982d0000
Signature pointer[4]: 982d80fe (4269813144)
Signature size[4]: 00000000 (0)
Certificate chain pointer[4]: 982d80fe (4269813144)
Certificate chain size[4]: 00000000 (0)
"RPM" is an ARM ELF (Executable and Linkable Format) file
Class: ELF32
Magic[16]: 7f454c46010101000000000000000000
Type[2]: 0200 (ET_EXEC [Executable file])
Machine[2]: 2800 (EM_ARM [Advanced RISC Machines ARM])
Version[4]: 01000000
Entry point address[4]: 91001000
Start of program headers[4]: 34000000
Start of section headers[4]: 00000000
Flags[4]: 02000005
Size of this header[2]: 3400
Size of program headers[2]: 2000
Number of program headers[2]: 0400
Size of section headers[2]: 2800
Number of section headers[2]: 0000
Section header string table index[2]: 0000
"TZ" is an ARM ELF (Executable and Linkable Format) file
Class: ELF32
Magic[16]: 7f454c46010101000000000000000000
Type[2]: 0200 (ET_EXEC [Executable file])
Machine[2]: 2800 (EM_ARM [Advanced RISC Machines ARM])
Version[4]: 01000000
Entry point address[4]: 000081fe
Start of program headers[4]: 34000000
Start of section headers[4]: 00000000
Flags[4]: 02000005
Size of this header[2]: 3400
Size of program headers[2]: 2000
Number of program headers[2]: 1000
Size of section headers[2]: 2800
Number of section headers[2]: 0000
Section header string table index[2]: 0000
"WINSECAPP" is an ARM ELF (Executable and Linkable Format) file
Class: ELF32
Magic[16]: 7f454c46010101000000000000000000
Type[2]: 0200 (ET_EXEC [Executable file])
Machine[2]: 2800 (EM_ARM [Advanced RISC Machines ARM])
Version[4]: 01000000
Entry point address[4]: 0090fe07
Start of program headers[4]: 34000000
Start of section headers[4]: 00000000
Flags[4]: 02000005
Size of this header[2]: 3400
Size of program headers[2]: 2000
Number of program headers[2]: 0400
Size of section headers[2]: 2800
Number of section headers[2]: 0000
Section header string table index[2]: 0000
"TZAPPS" is a FAT partition
"BACKUP_TZAPPS" is an empty partition
"MODEM_FS2" is an empty partition
"MODEM_FSC" is an empty partition
"PLAT" is a FAT partition
"EFIESP" is a FAT partition
"MMOS" is a FAT partition
"MainOS" is a NTFS partition
-> Boot sector backup at offset 2566913536 match the boot sector from sector 0
"Data" is a NTFS partition
-> Boot sector backup at offset 7899971072 match the boot sector from sector 0
Regarding the FFU file itself (10586.1102.3063.Retail.FFU): the image embedded catalog is not signed. I attached it to this post. I also attached the extracted hash table. Indeed, the cat file only contains a SHA1 of the hashtable: it's enough to ensure the data is fine.
All the informations:
"_SECURITY_HEADER" position: 0
_SECURITY_HEADER
----------------
cbSize[4]: 20000000 (32)
Signature[12]: 5369676e6564496d61676520 (SignedImage )
dwChunkSizeInKb[4]: 80000000 (128)
dwAlgId[4]: 0c800000 (32780)
dwCatalogSize[4]: 48010000 (328)
dwHashTableSize[4]: 00a50600 (435456)
"Signed Catalog" position: 32
"Hash table data" position: 360 (+328)
"Padding" position: 435816 (+435456)
"_IMAGE_HEADER" position: 524288 (+88472)
Image Integrity Validation
--------------------------
Verify SHA-1 hash (91b4b4d9944bd90e36891b26c6ecded90190fcd5) of the hash table against the one from the embedded catalog
-> SHA-1 hash of the hash table match the hash from the catalog
Verify 1783627776 bytes of data per chunk of 128 kilobytes using 13608 SHA256 hashes (32 bytes)
-> Done successfully!
_IMAGE_HEADER
-------------
cbSize[4]: 18000000 (24)
Signature[12]: 496d616765466c6173682020 (ImageFlash )
ManifestLength[4]: f41a0000 (6900)
dwChunkSize[4]: 80000000 (128)
"Manifest" position: 524312
"Padding" position: 531212 (+6900)
"_STORE_HEADER" position: 655360 (+124148)
_STORE_HEADER
-------------
dwUpdateType[4]: 00000000 (0)
MajorVersion[2]: 0100 (1)
MinorVersion[2]: 0000 (0)
FullFlashMajorVersion[2]: 0200 (2)
FullFlashMinorVersion[2]: 0000 (0)
szPlatformId[192]: 5849414f4d49544553542e5869616f6d69383937342e4d49340000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 (XIAOMITEST.Xiaomi8974.MI4)
dwBlockSizeInBytes[4]: 00000200 (131072)
dwWriteDescriptorCount[4]: 25350000 (13605)
dwWriteDescriptorLength[4]: 58520300 (217688)
dwValidateDescriptorCount[4]: 00000000 (0)
dwValidateDescriptorLength[4]: 00000000 (0)
dwInitialTableIndex[4]: 00000000 (0)
dwInitialTableCount[4]: 01000000 (1)
dwFlashOnlyTableIndex[4]: d1000000 (209)
dwFlashOnlyTableCount[4]: 01000000 (1)
dwFinalTableIndex[4]: 23350000 (13603)
dwFinalTableCount[4]: 02000000 (2)
NumOfStores[2]: Skipped because field is only for version 2 FFU image
StoreIndex[2]: Skipped because field is only for version 2 FFU image
StorePayloadSize[8]: Skipped because field is only for version 2 FFU image
DevicePathLength[2]: Skipped because field is only for version 2 FFU image
DevicePath[2]: Skipped because field is only for version 2 FFU image
"_VALIDATION_ENTRY" position: 655608
"_VALIDATION_ENTRY" size: 0
"_BLOCK_DATA_ENTRY" position: 655608
"_BLOCK_DATA_ENTRY" size: 217688
"_IMAGE_PAYLOAD" position: 917504
_VALIDATION_ENTRY
-----------------
Skipped because there is no validation entries
_BLOCK_DATA_ENTRY
-----------------
(Removed because it's really long !)
"Padding" position: 873296
"_IMAGE_PAYLOAD" position: 917504
GUID Partition Table Layouts
----------------------------
GUID Partition Table from data block #0
Code:
+-----+-----------+-----------+--------+------------------------------------+
+ # | Start LBA | End LBA | Size | Name |
+-----+-----------+-----------+--------+------------------------------------+
+-----+-----------+-----------+--------+------------------------------------+
GUID Partition Table from data block #209
Code:
+-----+-----------+-----------+--------+------------------------------------+
+ # | Start LBA | End LBA | Size | Name |
+-----+-----------+-----------+--------+------------------------------------+
| 0| 1024| 2047| 1024|SBL1 |
| 1| 2048| 2559| 512|UEFI_BS_NV |
| 2| 3072| 3583| 512|UEFI_RT_NV |
| 3| 4096| 8191| 4096|UEFI |
| 4| 8192| 10239| 2048|DDR |
| 5| 10240| 12287| 2048|SSD |
| 6| 12288| 14335| 2048|PADDING0 |
| 7| 14336| 30719| 16384|DPP |
| 8| 30720| 30783| 64|DBI |
| 9| 31744| 32743| 1000|RPM |
| 10| 32768| 33767| 1000|TZ |
| 11| 33792| 34815| 1024|WINSECAPP |
| 12| 34816| 67583| 32768|TZAPPS |
| 13| 67584| 68607| 1024|BACKUP_SBL1 |
| 14| 68608| 68671| 64|BACKUP_DBI |
| 15| 69632| 73727| 4096|BACKUP_UEFI |
| 16| 73728| 74727| 1000|BACKUP_RPM |
| 17| 74752| 75751| 1000|BACKUP_TZ |
| 18| 75776| 76799| 1024|BACKUP_WINSECAPP |
| 19| 76800| 109567| 32768|BACKUP_TZAPPS |
| 21| 117760| 131071| 13312|PADDING1 |
| 22| 131072| 134143| 3072|MODEM_FS1 |
| 23| 134144| 137215| 3072|MODEM_FS2 |
| 24| 137216| 137247| 32|MODEM_FSC |
| 25| 138240| 154623| 16384|PLAT |
| 26| 154624| 220159| 65536|EFIESP |
| 27| 220160| 262143| 41984|PADDING2 |
| 28| 262144| 265215| 3072|MODEM_FSG |
| 29| 265216| 491519| 226304|PADDING3 |
| 30| 491520| 524287| 32768|PERSIST |
+-----+-----------+-----------+--------+------------------------------------+
GUID Partition Table from data block #13603
Code:
+-----+-----------+-----------+--------+------------------------------------+
+ # | Start LBA | End LBA | Size | Name |
+-----+-----------+-----------+--------+------------------------------------+
| 0| 1024| 2047| 1024|SBL1 |
| 1| 2048| 2559| 512|UEFI_BS_NV |
| 2| 3072| 3583| 512|UEFI_RT_NV |
| 3| 4096| 8191| 4096|UEFI |
| 4| 8192| 10239| 2048|DDR |
| 5| 10240| 12287| 2048|SSD |
| 6| 12288| 14335| 2048|PADDING0 |
| 7| 14336| 30719| 16384|DPP |
| 8| 30720| 30783| 64|DBI |
| 9| 31744| 32743| 1000|RPM |
| 10| 32768| 33767| 1000|TZ |
| 11| 33792| 34815| 1024|WINSECAPP |
| 12| 34816| 67583| 32768|TZAPPS |
| 13| 67584| 68607| 1024|BACKUP_SBL1 |
| 14| 68608| 68671| 64|BACKUP_DBI |
| 15| 69632| 73727| 4096|BACKUP_UEFI |
| 16| 73728| 74727| 1000|BACKUP_RPM |
| 17| 74752| 75751| 1000|BACKUP_TZ |
| 18| 75776| 76799| 1024|BACKUP_WINSECAPP |
| 19| 76800| 109567| 32768|BACKUP_TZAPPS |
| 20| 109568| 117759| 8192|MMOS |
| 21| 117760| 131071| 13312|PADDING1 |
| 22| 131072| 134143| 3072|MODEM_FS1 |
| 23| 134144| 137215| 3072|MODEM_FS2 |
| 24| 137216| 137247| 32|MODEM_FSC |
| 25| 138240| 154623| 16384|PLAT |
| 26| 154624| 220159| 65536|EFIESP |
| 27| 220160| 262143| 41984|PADDING2 |
| 28| 262144| 265215| 3072|MODEM_FSG |
| 29| 265216| 491519| 226304|PADDING3 |
| 30| 491520| 524287| 32768|PERSIST |
| 31| 524288| 5537791| 5013504|MainOS |
| 32| 5537792| 20967423|15429632|Data |
+-----+-----------+-----------+--------+------------------------------------+
Data Blocks to Partitions
-------------------------
Data Block #0-0: -> GPT
Data Block #0-1: -> GPT
Data Block #1-0: -> SBL1
to
Data Block #4-0: -> SBL1
Data Block #5-0: -> UEFI_BS_NV
to
Data Block #8-0: -> UEFI_RT_NV
Data Block #9-0: -> UEFI
to
Data Block #24-0: -> UEFI
Data Block #25-0: -> PADDING0
to
Data Block #32-0: -> PADDING0
Data Block #33-0: -> DPP
Data Block #34-0: -> DBI
Data Block #35-0: -> RPM
to
Data Block #38-0: -> RPM
Data Block #39-0: -> TZ
to
Data Block #42-0: -> TZ
Data Block #43-0: -> WINSECAPP
to
Data Block #46-0: -> WINSECAPP
Data Block #47-0: -> TZAPPS
to
Data Block #48-0: -> TZAPPS
Data Block #49-0: -> BACKUP_TZAPPS
to
Data Block #60-0: -> BACKUP_TZAPPS
Data Block #61-0: -> MODEM_FS2
to
Data Block #68-0: -> MODEM_FS2
Data Block #69-0: -> MODEM_FSC
Data Block #70-0: -> PLAT
to
Data Block #127-0: -> PLAT
Data Block #128-0: -> EFIESP
to
Data Block #208-0: -> EFIESP
Data Block #209-0: -> GPT
Data Block #210-0: -> MMOS
to
Data Block #211-0: -> MMOS
Data Block #212-0: -> MainOS
to
Data Block #12925-0: -> MainOS
Data Block #12926-0: -> Data
to
Data Block #13602-0: -> Data
Data Block #13603-0: -> GPT
Data Block #13604-0: -> GPT
Regarding the Firehose flasher:
".\prog_emmc_firehose_8974.mbn" is a SBL (Secondary Boot Loader) file with a 80 bytes header
The file is not signed (no signature and no certificate chain).
Codeword[4]: d1dc4b84
Magic[4]: 3410d773
Image ID[4]: 0d000000
Reserved 1[4]: ffffffff
Reserved 2[4]: ffffffff
Image source[4]: 50000000
Image destination pointer[4]: 50c000f8 (4160798800)
Image size[4]: 90480100
Code size[4]: 90480100
Signature pointer[4]: e00802f8 (4160882912)
Signature size[4]: 00000000 (0)
Certificate chain pointer[4]: e00802f8 (4160882912)
Certificate chain size[4]: 00000000 (0)
OEM root certificate selelected[4]: 01000000
OEM number of root certificates[4]: 01000000
Booting image config[4]: ffffffff
Reserved 6[4]: ffffffff
Reserved 7[4]: ffffffff
Reserved 8[4]: ffffffff
Reserved 9[4]: ffffffff
Finally, the packages installed in this ROM:
Part of the Windows Mobile Adaptation Kit (AK):
C:\Program Files (x86)\Windows Kits\10\MSPackages\Merged\arm\fre
Probably untouched.
Microsoft.MS_RETAILDEMOCONTENT_NEUTRAL.Data.cab
Microsoft.MS_RETAILDEMOCONTENT_ZH-CN.Data.cab
Microsoft.EFIESP.Production.cab
Microsoft.MS_BOOTSEQUENCE_RETAIL.EFIESP.cab
Microsoft.RELEASE_PRODUCTION.EFIESP.cab
Microsoft.MainOS.Production.cab
Microsoft.MainOS.Production_Lang_en-US.cab
Microsoft.MainOS.Production_Lang_zh-CN.cab
Microsoft.MainOS.Production_Res_1080x1920.cab
Microsoft.MS_BOOTSEQUENCE_RETAIL.MainOS.cab
Microsoft.MS_COMMSENHANCEMENTCHINA.MainOS.cab
Microsoft.MS_COMMSMESSAGINGGLOBAL.MainOS.cab
Microsoft.MS_FACEBOOK.MainOS.cab
Microsoft.MS_OPTIMIZED_BOOT.MainOS.cab
Microsoft.MS_RETAILDEMOCONTENT_NEUTRAL.MainOS.cab
Microsoft.MS_RETAILDEMOCONTENT_ZH-CN.MainOS.cab
Microsoft.MS_SKYPE.MainOS.cab
Microsoft.MS_STANDARD_FEATURE_1.MainOS.cab
Microsoft.PhoneFM.cab
Microsoft.PRERELEASE_PROTECTED.MainOS.cab
Microsoft.PRERELEASE_PROTECTED.MainOS_Lang_en-US.cab
Microsoft.PRERELEASE_PROTECTED.MainOS_Lang_zh-CN.cab
Microsoft.PRERELEASE_PROTECTED.MainOS_Res_1080x1920.cab
Microsoft.RELEASE_PRODUCTION.MainOS.cab
Microsoft.RELEASE_PRODUCTION.UpdateOS.cab
Microsoft.UpdateOS.Production.cab
C:\Program Files (x86)\Windows Kits\10\MSPackages\mobilecore\ARM\fre
Probably untouched.
microsoft.mobilecore.prod.efiesp.cab
microsoft.mobilecore.prod.mainos.cab
microsoft.mobilecore.updateos.cab
C:\Program Files (x86)\Windows Kits\10\MSPackages\retail\ARM\fre
Probably untouched.
Microsoft.Input.mtf_Lang_en-US.cab
Microsoft.Input.mtf_Lang_zh-CN.cab
Microsoft.Speech.Data_Lang_en-US.cab
Microsoft.Speech.Data_Lang_zh-CN.cab
Part of the Qualcomm Board Support Package:
E:\MI4\BSP\prebuilt.3063.RTF\spkg
ODM-made packages:
Qualcomm.MI4.Customizations.MainOS.spkg
Qualcomm.MI4.Customizations.StartLayout.spkg
Qualcomm.MI4.Customizations.StaticApps.MainOS.spkg
Qualcomm.MI4.Customizations.EFIESP.spkg
Qualcomm.QC8974.OEMAutobrightness.spkg
Qualcomm.QC8974.OEMDevicePlatform.spkg
Qualcomm.Xiaomi.DeviceLayout.spkg
Qualcomm MSM8974 drivers:
Can ODM recompile these packages? Or are they untouched?
OEM.HalExtensions.UpdateOS.spkg
OEM.Service.ProvisionService.spkg
Qualcomm.QC8974.BattProv.spkg
Qualcomm.QC8974.FlightToken.spkg
Qualcomm.QC8974.startupnsh.spkg
Qualcomm.QC8974.ABD.spkg
Qualcomm.QC8974.AccLSM330.spkg
Qualcomm.QC8974.ADCM.spkg
Qualcomm.QC8974.adsprpc.spkg
Qualcomm.QC8974.AlsPrxTMD27723.spkg
Qualcomm.QC8974.AMSSPeriImage_8974DI4.spkg
Qualcomm.QC8974.AtmelTouch.spkg
Qualcomm.QC8974.AudioDeviceDriver.spkg
Qualcomm.QC8974.bam_dmux.spkg
Qualcomm.QC8974.BCryptCipher_KM.spkg
Qualcomm.QC8974.BT_MainOS.spkg
Qualcomm.QC8974.DataDaemon.spkg
Qualcomm.QC8974.DiagBridge.spkg
Qualcomm.QC8974.DiagCSI.spkg
Qualcomm.QC8974.DiagRouter.spkg
Qualcomm.QC8974.direct3dum11.spkg
Qualcomm.QC8974.DisableSaverF800Bugcheck.spkg
Qualcomm.QC8974.DSPPeriImage.spkg
Qualcomm.QC8974.FveEnable.HardwareCrypto.spkg
Qualcomm.QC8974.GyroLsm330.spkg
Qualcomm.QC8974.HalExtQCTimer.spkg
Qualcomm.QC8974.HalExtQCWdogTimer.spkg
Qualcomm.QC8974.hwnhaptics.spkg
Qualcomm.QC8974.hwnled.spkg
Qualcomm.QC8974.ipc_router.spkg
Qualcomm.QC8974.libadsprpc.spkg
Qualcomm.QC8974.linklocal.spkg
Qualcomm.QC8974.MagAKM8963.spkg
Qualcomm.QC8974.mbb.spkg
Qualcomm.QC8974.mbbuio.spkg
Qualcomm.QC8974.mbrg.spkg
Qualcomm.QC8974.ocmem.spkg
Qualcomm.QC8974.PageFile.UserData.256.spkg
Qualcomm.QC8974.Pep_ROT.spkg
Qualcomm.QC8974.PEPLED.spkg
Qualcomm.QC8974.PEPProxy.spkg
Qualcomm.QC8974.PhoneRadioRevision_8974DI4.spkg
Qualcomm.QC8974.pil.spkg
Qualcomm.QC8974.powerkeygpiodriver.spkg
Qualcomm.QC8974.PPMSettings.spkg
Qualcomm.QC8974.QC_PEP.spkg
Qualcomm.QC8974.qcadc.spkg
Qualcomm.QC8974.qcaud.spkg
Qualcomm.QC8974.QcBattMiniclass.spkg
Qualcomm.QC8974.QcBattMngr.spkg
Qualcomm.QC8974.qcbluetooth.spkg
Qualcomm.QC8974.QcBms.spkg
Qualcomm.QC8974.qccamavs.spkg
Qualcomm.QC8974.qccamflash.spkg
Qualcomm.QC8974.qccamfrontsensor_imx219_8m_bayer.spkg
Qualcomm.QC8974.qccamisp.spkg
Qualcomm.QC8974.QCCamJpegE.spkg
Qualcomm.QC8974.qccamplatform.spkg
Qualcomm.QC8974.qccamrearsensor_imx214_13m_bayer.spkg
Qualcomm.QC8974.qccamsettings.spkg
Qualcomm.QC8974.qccamtuningdata.spkg
Qualcomm.QC8974.qccdi.spkg
Qualcomm.QC8974.QCCI.spkg
Qualcomm.QC8974.qccomposite.spkg
Qualcomm.QC8974.QCDiagLogging.spkg
Qualcomm.QC8974.qcdx11compiler.spkg
Qualcomm.QC8974.qcdxdriver.spkg
Qualcomm.QC8974.qcepmadc.spkg
Qualcomm.QC8974.qcfmminiport.spkg
Qualcomm.QC8974.qcfmtransport.spkg
Qualcomm.QC8974.qcgnss.spkg
Qualcomm.QC8974.QcGnssSvc.spkg
Qualcomm.QC8974.qcgpio.spkg
Qualcomm.QC8974.QcGsiffSvc.spkg
Qualcomm.QC8974.qci2c.spkg
Qualcomm.QC8974.qcimssink.spkg
Qualcomm.QC8974.qcimssrc.spkg
Qualcomm.QC8974.QCJpegEncoderMFT.spkg
Qualcomm.QC8974.QcKmdBam.spkg
Qualcomm.QC8974.qclistensoundmodellib.spkg
Qualcomm.QC8974.QcLTECoexMgr.spkg
Qualcomm.QC8974.qcmchdcpuml.spkg
Qualcomm.QC8974.qcmcumd.spkg
Qualcomm.QC8974.QcMipiBif.spkg
Qualcomm.QC8974.QcPmic.spkg
Qualcomm.QC8974.QcPmicApps.spkg
Qualcomm.QC8974.QcPmicGpio.spkg
Qualcomm.QC8974.QCPowerLog.spkg
Qualcomm.QC8974.qcqdss.spkg
Qualcomm.QC8974.QcRCSPresSvc.spkg
Qualcomm.QC8974.qcSensor1UM.spkg
Qualcomm.QC8974.qcSensors.spkg
Qualcomm.QC8974.qcSensorsConfig.spkg
Qualcomm.QC8974.QcShutdownSvc.spkg
Qualcomm.QC8974.QCSI.spkg
Qualcomm.QC8974.qcslimbus.spkg
Qualcomm.QC8974.qcspi.spkg
Qualcomm.QC8974.qcspmi.spkg
Qualcomm.QC8974.QcUsbFnSsFilter.spkg
Qualcomm.QC8974.qcviddecmft.spkg
Qualcomm.QC8974.QcVidEncmftH263.spkg
Qualcomm.QC8974.QcVidEncmftH264.spkg
Qualcomm.QC8974.QcVidEncMftMPEG4.spkg
Qualcomm.QC8974.qcvidencum.spkg
Qualcomm.QC8974.qcvss.spkg
Qualcomm.QC8974.QcWicEncoder8974.spkg
Qualcomm.QC8974.QmiDaemon.spkg
Qualcomm.QC8974.qmux.spkg
Qualcomm.QC8974.QNFC.spkg
Qualcomm.QC8974.qualcomm_uart.spkg
Qualcomm.QC8974.RegCustomization.spkg
Qualcomm.QC8974.remoteat.spkg
Qualcomm.QC8974.RemoteAtSrvc.spkg
Qualcomm.QC8974.remotefs.spkg
Qualcomm.QC8974.revrmnet.spkg
Qualcomm.QC8974.rmnetbridge.spkg
Qualcomm.QC8974.RPEN.spkg
Qualcomm.QC8974.scm.spkg
Qualcomm.QC8974.ShowVideoCallingSwitch_8974DI4.spkg
Qualcomm.QC8974.smd.spkg
Qualcomm.QC8974.smmu.spkg
Qualcomm.QC8974.SOCProdTest.spkg
Qualcomm.QC8974.ssd.spkg
Qualcomm.QC8974.ssm.spkg
Qualcomm.QC8974.subsys.spkg
Qualcomm.QC8974.TouchDetectionDriver.spkg
Qualcomm.QC8974.UsbFnFilter.spkg
Qualcomm.QC8974.WCNSSPeriImage.spkg
Qualcomm.QC8974.WDFHelper.spkg
Qualcomm.QC8974.WifiNotifierSrvc.spkg
Qualcomm.QC8974.wlan.spkg
Qualcomm.QC8974.wlan_ihv.spkg
Qualcomm.QC8974.WMIms.spkg
Qualcomm.QC8974.WMRil.spkg
Qualcomm.QC8974_MTP.ACSP.spkg
Qualcomm.M8X74SOC_MTP.acpi.spkg
Qualcomm.QC8974.smbios_cfg.spkg
Partitions:
Qualcomm.QC8974.dbi.spkg
Qualcomm.QC8974.rpm.spkg
Qualcomm.QC8974.sbl1.spkg
Qualcomm.QC8974.tz.spkg
Qualcomm.QC8974.tzapps.spkg
Qualcomm.QC8974.uefi.spkg
Qualcomm.QC8974.winsecapp.spkg
Do not forget, you can still install android on it without digging
djtonka said:
Do not forget, you can still install android on it without digging
Click to expand...
Click to collapse
Yes, I know you can flip from Android and Windows Mobile as you wish
I shared these information to understand how they ported Windows Mobile to an Android phone: it seems you need to keep some partition.
TristanLeBoss said:
Yes, I know you can flip from Android and Windows Mobile as you wish
I shared these information to understand how they ported Windows Mobile to an Android phone: it seems you need to keep some partition.
Click to expand...
Click to collapse
Kept partitions must be related to flash mode .
I think if you remove them you will not be able to go back to android
Can it be ported to other phones.
@TristanLeBoss i just wanna know what's the magic that differentiates an ARM windows to an ARM Android? Basic instruction set is the same. So it can be ported to other ARM devices right?
@katsuga & @iamsubhranil
Windows Mobile 10 can theoretically work on all ARM phones. But that's the theory...
For example, Secure Boot will be a problem because if the bootloader of your phone is not signed by your manufacturer, your phone won't boot. Some phones like the Google Nexus offer a way to disable Secure Boot...
The next problem I see is with the drivers. I am unsure if they can be customized by manufacturers or if they are generic.
TristanLeBoss said:
For example, Secure Boot will be a problem because if the bootloader of your phone is not signed by your manufacturer, your phone won't boot. Some phones like the Google Nexus offer a way to disable Secure Boot...
The next problem I see is with the drivers. I am unsure if they can be customized by manufacturers or if they are generic.
Click to expand...
Click to collapse
SecureBoot can be disabled by OEM unlocking AFAIK. And regarding the .spkg drivers, I already made some searches and found that they are UWD(Universal Windows Drivers). VS15 itself provides some generic drivers for UWP. Any low level customisations have to be made by the devolper. This is an one time effort as only UWD will reside in any future version of Windows. Being Linux based OpenSource OS, we already have our device sources, bases and all low level components in the source code state. I don't think porting them in UWD won't be any problem. Will it?
With these discoveries, what could be considered the most optimal candidate phone to test a port on? Be it not all ducks will line up in a row, but if only 1 or 2 are standing out of line, then it seems there are workarounds that can be implemented...hence the disabling of secure boot. The other difficulty is how to flash, or what method can be used both ways...from Android to WM10 and vice versa. Something similar to the miflash tool looks ideal or possibly other qualcomm tools. Maybe I am thinking too far ahead here...
nate0 said:
With these discoveries, what could be considered the most optimal candidate phone to test a port on? Be it not all ducks will line up in a row, but if only 1 or 2 are standing out of line, then it seems there are workarounds that can be implemented...hence the disabling of secure boot. The other difficulty is how to flash, or what method can be used both ways...from Android to WM10 and vice versa. Something similar to the miflash tool looks ideal or possibly other qualcomm tools. Maybe I am thinking too far ahead here...
Click to expand...
Click to collapse
Well at first I think a 100% similar spec-ed Android device with a Windows one could be the target because there'll be much less chance of missing and/or conflicting drivers and other components.
nate0 said:
With these discoveries, what could be considered the most optimal candidate phone to test a port on? Be it not all ducks will line up in a row, but if only 1 or 2 are standing out of line, then it seems there are workarounds that can be implemented...hence the disabling of secure boot. The other difficulty is how to flash, or what method can be used both ways...from Android to WM10 and vice versa. Something similar to the miflash tool looks ideal or possibly other qualcomm tools. Maybe I am thinking too far ahead here...
Click to expand...
Click to collapse
You figured them
1) Ability to disable Secure Boot or to boot an untrusted boot loader
2) Ability to flash in 9008 mode
2a) A file to flash to restore the original OS
2b) Sahara programmer to restore GPT & need boot partitions (MPRGXXXX.hex & XXXX_msimage.mbn) in case we soft brick it
2b) Firehose programmer (prog_XXXX_firehose.mbn) to flash new partitions once fastboot is gone
3) A SoC supported by one of the Windows Mobile 10 FFU we have (Xiaomi Mi4, Lumia 950, Lumia 950XL...)
TristanLeBoss said:
You figured them
1) Ability to disable Secure Boot or to boot an untrusted boot loader
2) Ability to flash in 9008 mode
2a) A file to flash to restore the original OS
2b) Sahara programmer to restore GPT & need boot partitions (MPRGXXXX.hex & XXXX_msimage.mbn) in case we soft brick it
2b) Firehose programmer (prog_XXXX_firehose.mbn) to flash new partitions once fastboot is gone
3) A SoC supported by one of the Windows Mobile 10 FFU we have (Xiaomi Mi4, Lumia 950, Lumia 950XL...)
Click to expand...
Click to collapse
EDIT: Has anyone documented successfully disabling secure-boot on a Nexus or accomplished this? Is this the same as unlocking the boot loader? I have been thinking along the lines of UEFI/EFI secure boot. Similar to disabling secure boot on a surface so you can install Android... Wondering if there are any repercussions or if it can be reversed...
TristanLeBoss said:
Regarding the Firehose flasher:
".\prog_emmc_firehose_8974.mbn" is a SBL (Secondary Boot Loader) file with a 80 bytes header
The file is not signed (no signature and no certificate chain).
Codeword[4]: d1dc4b84
Magic[4]: 3410d773
Image ID[4]: 0d000000
Reserved 1[4]: ffffffff
Reserved 2[4]: ffffffff
Image source[4]: 50000000
Image destination pointer[4]: 50c000f8 (4160798800)
Image size[4]: 90480100
Code size[4]: 90480100
Signature pointer[4]: e00802f8 (4160882912)
Signature size[4]: 00000000 (0)
Certificate chain pointer[4]: e00802f8 (4160882912)
Certificate chain size[4]: 00000000 (0)
OEM root certificate selelected[4]: 01000000
OEM number of root certificates[4]: 01000000
Booting image config[4]: ffffffff
Reserved 6[4]: ffffffff
Reserved 7[4]: ffffffff
Reserved 8[4]: ffffffff
Reserved 9[4]: ffffffff
Click to expand...
Click to collapse
@TristanLeBoss
What else do you know about this programmer or others you may be able to analyze, was it supplied through the OEM to use with their tool? Can it be used on other ARM QC 8974 chip phones? Maybe it can be used on another phone with same partition layout/size? If not I am curious if there is a way to extract or build the mbn/programmer files needed from another phone via jtag setup or something.
I ask this since the OnePlus 2 (A2001 Chinese model) there are mbn/flash partitions/programmer files available for unbricking. Maybe those would come in handy...
This sounds like your theory would also work with an OTG cable and a thumb drive. But what do you mean get a uefi image file to pack in the boot image though. This would be a signed file?
feherneoh said:
If you tell me the exact device you are using (and optionally give me a boot.img for it) I can try to build one image for you (first LK, to make sure drivers are okay, if they work, then EFIDroid)
Click to expand...
Click to collapse
Only for same specs device's for now or for all android devices?
feherneoh said:
I should be able to build UEFI for almost any SnapDragon device, but in some cases LCD does not work with it
And you still have to mess around with W10M to make it work
Click to expand...
Click to collapse
Your method uses an SD card to build/boot the separate OS correct? Can this be done with a OTG connection as well? Would this work for the OnePlus3? I currently own one. If not I would be willing to purchase a cheap used OnePlus 2 device seeing how folks are trying to get rid of them now, but not sure how easily available that boot.img is.....
Actually it seems a OP2 device has no SD card slot either, if I am able to get a cheap used test device that will work then seems OnePlus X does have a slot. Have you successfully accomplished a boot of W10M off an SD card from an Android phone? What's your test device, and do you have separate thread on this as some this is off topic from the thread Subj... @TristanLeBoss apologies.
feherneoh said:
BTW, I know people who started porting it, but it is extremely hard
Click to expand...
Click to collapse
Yes from my small experience digging into it, it is not easy to get all things to line up the way they are needed.