FORUMS

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

Windows Phone 7 - ROM Deployment and how it will affect us

3,305 posts
Thanks Meter: 1,541
 
By Da_G, Moderator Emeritus / Senior Recognized Developer on 21st March 2010, 09:37 AM
Post Reply Subscribe to Thread Email Thread
Windows Phone 7 has standardized the bootloader requirements for OEMs. No longer will an OEM be allowed to implement it's own design for ROM deployment (such as HTC with the .nbh/RUU system, .dz/LGMDP with LG, etc.)

The image format will be B000FF/.bin, which receives only minor changes from CE5, and so our current tools should work fine with this. The major change is in the way the bootloader handles image deployment. For Samsung and a handful of other manufacturers, this won't change too much, as they already utilize the B000FF system for deployment. The filesystem inside will be IMGFS - no longer will BinFS be used for NK/XIP section (now IMGFS will all partitions on device, NK and OS just being split by package rather than a seperate FS)

The physical flash layout will look as follows:
  • Reserved Regions, updateable only through a special oem-written driver to allow access to this area (size varies)
  • Partition Table (1KB)
  • BLDR (1MB)
  • DBSP (Device Boot State Partition, 256KB)
  • DPP (Device Provisioning Partition, 256KB)
  • USP (Update State Partition, 2MB)
  • ULDR1 (>=6MB)
  • ULDR2 (>=6MB)
  • NK (IMGFS, >=4.5MB) - At least 1MB free space for updates
  • OS (IMGFS, >=181MB) - At least 20% free space for updates
  • User Store (TexFAT)

Only the User Store (Which uses new Transaction-Safe ExFAT filesystem) will be user-writeable, all other areas will only be writable during an update operation. The Partition Table, DBSP, DPP, USP, and User Store are all not updateable during an update operation, only during a full-flash scenario. B00FF images are signed and checksummed, and passed through to the bootloader via ethernet over usb. The connection will most likely be encrypted, using the same flashing utility as Zune HD. (This is currently used to deploy images to the DevKits)

.ffu (Full Flash Update) file format (XML) will be used to pass information to the Zune software on which partitions are to be updated, etc. FFUs are signed just as .cabs are signed and only an .ffu which passes validation against the certificates on-device will be allowed to update a device.

Updates can also be done on a per-package basis, using the ImageUpdate process, which I have described in length @ the XDA WinMo Software Development forum. This process is largely unchanged from WinMo 6.x with the addition of a policy xml file containing security policy settings related to the .cab.pkg being deployed.

As such, I would recommend anyone interested in cracking the bootloader and creating a "HardSPL" take a good hard look at the Zune HD.

Similar to CE5/WinMo 6.x, There is a BLDR (Base Boot Loader) which makes the initial determination to boot up to the ULDR or to the WP7 OS. The OEM implements alternate boot parameters to trigger this and/or a button press combination. If ULDR is triggered, it checks the battery and power source to ensure that there is enough life remaining to successfully complete the flash, then awaits the flash download. There are redundant ULDR partitions (ULDR1/ULDR2) to facilitate failsafe recovery in the event of a failed ULDR flash (ULDR provides a basic level of functionality to enable a recovery flash even in the event of power failure during a flash)

MSFT is pushing it's Phone Update service much harder this time - it is intended to be used as the primary method for distributing phone updates. These can be deployed both over-the-air and through a USB connection with the Zune software.
Last edited by Noonski; 15th May 2010 at 03:19 AM.
The Following 3 Users Say Thank You to Da_G For This Useful Post: [ View ]
 
 
20th April 2010, 10:41 PM |#2  
af974's Avatar
Retired Recognized Developer / Retired Forum Moderator
Thanks Meter: 1,889
 
More
subscribe to this......need to learn before my next device.
21st April 2010, 03:36 AM |#3  
Senior Member
Flag Orlando
Thanks Meter: 75
 
More
Thanks. I didn't see these threads before. Any chance you could share or point to the docs this info came from? It seems tweakers.net acquired it and I wouldn't mind looking through.
23rd April 2010, 03:18 PM |#4  
mord4z's Avatar
Senior Member
Flag Umuarama
Thanks Meter: 3
 
More
saved for future use! Da_G is the master of the roms!
24th April 2010, 03:56 AM |#5  
Senior Member
Thanks Meter: 12
 
More
As Usual Da_G you are cool..
24th April 2010, 05:22 AM |#6  
Tribulattifather's Avatar
Retired Forum Moderator / Recognized Developer
╠▒╣New╬York╠▒╣
Thanks Meter: 1,834
 
Donate to Me
More
Will you make this thread a Sticky for us? Thanks again G.
25th April 2010, 02:18 AM |#7  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by da_g

bump for visibility

bump! Bump! Bump!
25th April 2010, 03:37 AM |#8  
jagan2's Avatar
Recognized Developer
Thanks Meter: 220
 
More
Da_G you always rock, now we got a huge info.
28th April 2010, 03:10 PM |#9  
Senior Member
Flag Nice
Thanks Meter: 0
 
More
thanks for your infos
28th April 2010, 06:05 PM |#10  
jdep1's Avatar
Senior Member
Flag El Paso
Thanks Meter: 15
 
More
that is some good news eventually have custom ROMs on wp7
5th May 2010, 08:10 PM |#11  
Junior Member
Thanks Meter: 0
 
More
thanks!!!!!

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes