NBH_WM7_AKU_6176_WWE_for_HTC_MONDRIAN
- Thread starter 911sniper
- Start date
This one might work...
http://www.tincantools.com/product.php?productid=16134&cat=0&page=1&featured
It definitely supports the Cortex-A8 as it seems to be one of the favorites of the beagleboard people (which is running a A8 based TI OMAP). Waayyyy cheaper than a lot of the other stuff out there. Some more good info here...http://elinux.org/BeagleBoardJTAG
http://www.tincantools.com/product.php?productid=16134&cat=0&page=1&featured
It definitely supports the Cortex-A8 as it seems to be one of the favorites of the beagleboard people (which is running a A8 based TI OMAP). Waayyyy cheaper than a lot of the other stuff out there. Some more good info here...http://elinux.org/BeagleBoardJTAG
Guys what about this one? It specifically mentions QSD8250 / QSD8650 and Scorpion in the supported chips list.
http://www.lauterbach.com/frames.html?bdmusb2.html
Sorry if this has been mentioned before
http://www.lauterbach.com/frames.html?bdmusb2.html
Sorry if this has been mentioned before
hoss_n2
Senior Member
MAP.txt from Kernel WP7:
Code:
87a00000 - ef930000 L67f30000 NUL
ef930000 - ef936000 L00006000 Virtual base address of htcpme.dll
ef936000 - ef940000 L0000a000 NUL
ef940000 - ef946000 L00006000 Virtual base address of htcoalcb.dll
ef946000 - ef950000 L0000a000 NUL
ef950000 - ef955000 L00005000 Virtual base address of HTCMFG.dll
ef955000 - ef960000 L0000b000 NUL
ef960000 - ef968000 L00008000 Virtual base address of htcfsfilter.dll
ef968000 - ef970000 L00008000 NUL
ef970000 - ef975000 L00005000 Virtual base address of HTCCeLog.dll
ef975000 - ef980000 L0000b000 NUL
ef980000 - ef98e000 L0000e000 Virtual base address of drhtc.dll
ef98e000 - ef990000 L00002000 NUL
ef990000 - ef995000 L00005000 Virtual base address of HTC_Flashlight.dll
ef995000 - ef9a0000 L0000b000 NUL
ef9a0000 - ef9a5000 L00005000 Virtual base address of TLMM_GPIO_config.dll
ef9a5000 - ef9b0000 L0000b000 NUL
ef9b0000 - ef9b6000 L00006000 Virtual base address of tlmm.dll
ef9b6000 - ef9c0000 L0000a000 NUL
ef9c0000 - ef9e9000 L00029000 Virtual base address of qualcomm_flashpdd.dll
ef9e9000 - ef9f0000 L00007000 NUL
ef9f0000 - efa04000 L00014000 Virtual base address of msm7x00_sdhc.dll
efa04000 - efa10000 L0000c000 NUL
efa10000 - efa1d000 L0000d000 Virtual base address of DALSYSDRIVERS.dll
efa1d000 - efa20000 L00003000 NUL
efa20000 - efa25000 L00005000 Virtual base address of DALConfig.dll
efa25000 - efa30000 L0000b000 NUL
efa30000 - efa35000 L00005000 Virtual base address of wce_pmem.dll
efa35000 - efa40000 L0000b000 NUL
efa40000 - efa45000 L00005000 Virtual base address of smem_drv.dll
efa45000 - efa50000 L0000b000 NUL
efa50000 - efa58000 L00008000 Virtual base address of smem.dll
efa58000 - efa60000 L00008000 NUL
efa60000 - efa85000 L00025000 Virtual base address of smd.dll
efa85000 - efa90000 L0000b000 NUL
efa90000 - efac0000 L00030000 Virtual base address of rpc_server.dll
efac0000 - efacd000 L0000d000 Virtual base address of rpc_router.dll
efacd000 - efad0000 L00003000 NUL
efad0000 - efad6000 L00006000 Virtual base address of rpc_daemon.dll
efad6000 - efae0000 L0000a000 NUL
efae0000 - efae5000 L00005000 Virtual base address of qsd8x50v1_msm_hw.dll
efae5000 - efaf0000 L0000b000 NUL
efaf0000 - efaf5000 L00005000 Virtual base address of qsd8x50v1_hwioreg_block.dll
efaf5000 - efb00000 L0000b000 NUL
efb00000 - efb05000 L00005000 Virtual base address of qcomv1_hw.dll
efb05000 - efb10000 L0000b000 NUL
efb10000 - efb1b000 L0000b000 Virtual base address of pmem_drv.dll
efb1b000 - efb20000 L00005000 NUL
efb20000 - efb87000 L00067000 Virtual base address of k.oncrpc.dll
efb87000 - efb90000 L00009000 NUL
efb90000 - efb9c000 L0000c000 Virtual base address of k.dsm.dll
efb9c000 - efba0000 L00004000 NUL
efba0000 - efba9000 L00009000 Virtual base address of k.Diag_LSM.dll
efba9000 - efbb0000 L00007000 NUL
efbb0000 - efbba000 L0000a000 Virtual base address of k.ceddk.dll
efbba000 - efbc0000 L00006000 NUL
efbc0000 - efbc7000 L00007000 Virtual base address of gpio.dll
efbc7000 - efbd0000 L00009000 NUL
efbd0000 - efbd6000 L00006000 Virtual base address of errorfatal.dll
efbd6000 - efbe0000 L0000a000 NUL
efbe0000 - efbf4000 L00014000 Virtual base address of datamover.dll
efbf4000 - efc00000 L0000c000 NUL
efc00000 - efc07000 L00007000 Virtual base address of DALSys.dll
efc07000 - efc10000 L00009000 NUL
efc10000 - efc19000 L00009000 Virtual base address of DALRemote.dll
efc19000 - efc20000 L00007000 NUL
efc20000 - efc29000 L00009000 Virtual base address of DALBUSES.dll
efc29000 - efc30000 L00007000 NUL
efc30000 - efc36000 L00006000 Virtual base address of DAL0DRIVER.dll
efc36000 - efc40000 L0000a000 NUL
efc40000 - efc47000 L00007000 Virtual base address of clk_pause.dll
efc47000 - efc50000 L00009000 NUL
efc50000 - efc66000 L00016000 Virtual base address of clkregim.dll
efc66000 - efc70000 L0000a000 NUL
efc70000 - efc75000 L00005000 Virtual base address of oalioctl.dll
efc75000 - efc80000 L0000b000 NUL
efc80000 - efc8c000 L0000c000 Virtual base address of relfsd.dll
efc8c000 - efc90000 L00004000 NUL
efc90000 - efca5000 L00015000 Virtual base address of ccfgsvc.dll
efca5000 - efcb0000 L0000b000 NUL
efcb0000 - efcc7000 L00017000 Virtual base address of osaxst0.dll
efcc7000 - efcd0000 L00009000 NUL
efcd0000 - efcdb000 L0000b000 Virtual base address of hd.dll
efcdb000 - efce0000 L00005000 NUL
efce0000 - efcf5000 L00015000 Virtual base address of k.fpcrt.dll
efcf5000 - efd00000 L0000b000 NUL
efd00000 - efd09000 L00009000 Virtual base address of sdmemory.dll
efd09000 - efd10000 L00007000 NUL
efd10000 - efd24000 L00014000 Virtual base address of sdbus.dll
efd24000 - efd30000 L0000c000 NUL
efd30000 - efd36000 L00006000 Virtual base address of regenum.dll
efd36000 - efd40000 L0000a000 NUL
efd40000 - efd53000 L00013000 Virtual base address of pm.dll
efd53000 - efd60000 L0000d000 NUL
efd60000 - efd66000 L00006000 Virtual base address of k.mmtimer.dll
efd66000 - efd70000 L0000a000 NUL
efd70000 - efd88000 L00018000 Virtual base address of devmgr.dll
efd88000 - efd90000 L00008000 NUL
efd90000 - efd95000 L00005000 Virtual base address of device.dll
efd95000 - efda0000 L0000b000 NUL
efda0000 - efda7000 L00007000 Virtual base address of busenum.dll
efda7000 - efdb0000 L00009000 NUL
efdb0000 - efdb9000 L00009000 Virtual base address of wmpart.dll
efdb9000 - efdc0000 L00007000 NUL
efdc0000 - efdcb000 L0000b000 Virtual base address of unifiedblock.dll
efdcb000 - efdd0000 L00005000 NUL
efdd0000 - efdd6000 L00006000 Virtual base address of romfsd.dll
efdd6000 - efde0000 L0000a000 NUL
efde0000 - efdec000 L0000c000 Virtual base address of rawfs.dll
efdec000 - efdf0000 L00004000 NUL
efdf0000 - efdf6000 L00006000 Virtual base address of ramdisk.dll
efdf6000 - efe00000 L0000a000 NUL
efe00000 - efe09000 L00009000 Virtual base address of mspart.dll
efe09000 - efe10000 L00007000 NUL
efe10000 - efe20000 L00010000 Virtual base address of k.fatutil.dll
efe20000 - efebd000 L0009d000 Virtual base address of k.coredll.dll
efebd000 - efec0000 L00003000 NUL
efec0000 - efecb000 L0000b000 Virtual base address of imgfs.dll
efecb000 - efed0000 L00005000 NUL
efed0000 - efef4000 L00024000 Virtual base address of fsdmgr.dll
efef4000 - eff00000 L0000c000 NUL
eff00000 - eff07000 L00007000 Virtual base address of flashpart.dll
eff07000 - eff10000 L00009000 NUL
eff10000 - eff25000 L00015000 Virtual base address of flashmdd.dll
eff25000 - eff30000 L0000b000 NUL
eff30000 - effa1000 L00071000 Virtual base address of filesys.dll
effa1000 - effb0000 L0000f000 NUL
effb0000 - effcb000 L0001b000 Virtual base address of exfat.dll
effcb000 - effd0000 L00005000 NUL
effd0000 - effd7000 L00007000 Virtual base address of diskcache.dll
effd7000 - effe0000 L00009000 NUL
effe0000 - effe8000 L00008000 Virtual base address of cecompr.dll
effe8000 - efff0000 L00008000 NUL
efff0000 - efffe000 L0000e000 Virtual base address of cachefilt.dll
Da_G
Inactive Senior RD / Moderator Emeritus
With CE6 MSFT totally changed the process VM model (now no longer do we have the 32 process slot x 32MB per slot limit)
Take a look here for some more info:
http://msdn.microsoft.com/en-us/library/aa914933.aspx
What needs to happen is we need to drop the concept of 32x32MB slots, with Slot 1 and Slot 0 being used by XIP modules, and slot 63, 61, 60, 1 being used by user modules. Now we need to adopt the new concept of XIP being alloced to a single 256MB "slot" and user modules being alloced to a single 512MB "slot"
(assuming that has not changed since CE6)
It will be easier to work with once some CE7 documentation comes out, as that will detail the VM layout etc. (but for now i'm pretty certain it's not changed majorly since CE6)
Take a look here for some more info:
http://msdn.microsoft.com/en-us/library/aa914933.aspx
What needs to happen is we need to drop the concept of 32x32MB slots, with Slot 1 and Slot 0 being used by XIP modules, and slot 63, 61, 60, 1 being used by user modules. Now we need to adopt the new concept of XIP being alloced to a single 256MB "slot" and user modules being alloced to a single 512MB "slot"
(assuming that has not changed since CE6)It will be easier to work with once some CE7 documentation comes out, as that will detail the VM layout etc. (but for now i'm pretty certain it's not changed majorly since CE6)
Last edited:
With CE6 MSFT totally changed the process VM model (now no longer do we have the 32 process slot x 32MB per slot limit)
Take a look here for some more info:
http://msdn.microsoft.com/en-us/library/aa914933.aspx
What needs to happen is we need to drop the concept of 32x32MB slots, with Slot 1 and Slot 0 being used by XIP modules, and slot 63, 61, 60, 1, 0 being used by user modules. Now we need to adopt the new concept of XIP being alloced to a single 256MB "slot" and user modules being alloced to a single 512MB "slot"
It will be easier to work with once some CE7 documentation comes out, as that will detail the VM layout etc. (but for now i'm pretty certain it's not changed majorly since CE6)
I understand that no tool does not reduce the system?
As for relocation ...
I found in nk.exe:
So.
We know where it was compiled (yes it is really useful, lol)
and timebomb is in nk.exe
enjoy
So.
We know where it was compiled (yes it is really useful, lol)
and timebomb is in nk.exe
enjoy
Da_G
Inactive Senior RD / Moderator Emeritus
Hi Nokser,
I think you mean to say "Do we have a new tool for relocing modules to this new memory boundary yet?"
If that's what you meant, the answer is no, not yet
Regarding the timebomb strings in nk.exe, I believe that is to artificially force the system clock back (workaround) during the initial loading stages, so that the AK (Adpatation Kit) built in timebomb does not trigger before the system completes booting.
I think you mean to say "Do we have a new tool for relocing modules to this new memory boundary yet?"
If that's what you meant, the answer is no, not yet
Regarding the timebomb strings in nk.exe, I believe that is to artificially force the system clock back (workaround) during the initial loading stages, so that the AK (Adpatation Kit) built in timebomb does not trigger before the system completes booting.
Top Liked Posts
-
There are no posts matching your filters.
-
1Model: HTC Mondrian (Cingular USA)
AKU: WindowsMobile_7_AKU_6176
Language: 0409_WWE
ROM_WP7_AKU_6176_WWE_for_HTC_MONDRIAN.7z
http://www.rayfile.com/files/c9670b54-5f82-11df-97af-0015c55db73d/
Happy cooking!
Thx for the mirrors!
http://forum.xda-developers.com/showpost.php?p=6484403&postcount=22
http://forum.xda-developers.com/showpost.php?p=6485142&postcount=43
**********************************************************
NB file of the Bootloader in an older version:
HTC SPL & Radio included.
NB_HTCSPL_&_Radio_for_Mondrian.7z
http://www.rayfile.com/files/48c42d87-604c-11df-ba8e-0015c55db7
** MOD EDIT 2**
Take a look here for a detailed explanation of what this file is, and what we need to do to work with it.
** MOD EDIT **
This is obviously big news. Keep in mind this "ROM" is NOT flashable to any of the current devices we know of. NONE. You also can't dump this with the current tools we have at our disposal so, NO, we can not make WP7 ROMs based on this. Some great minds are already working on decrypting the format of this ROM and I'm sure information to that effect will be posted in the thread when that happens.
Until then, please refrain from asking if this is compatible with your phone (it's not!) or when it's going to be ported to "X" device. Thank you for your anticipated cooperation1
New posts
-
[GSI][13] LineageOS 20 TrebleDroid-based- Latest: TheGhost_31
-
