Database Users

EF02.rdf

http://device.sprintpcs.com/Samsung/SPH-D700/EF02.rdf
Found this just now. I'm surprised nobody else broke this before me.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl"
href="http://device.sprintpcs.com/uaprof.xsl"?>
<!--
*********************************************************************
* Sprint UA Prof template
*
* Version: 2.0
* Created: 1/3/2002
* Organization: Customer Equipment
* Modified: 01/03/2008
*
* Copyright 2008 Sprint PCS
*
* Note
* Elements that are not required by Sprint PCS have been omitted
* from this template.
*
* Revision History
* 0.1 Initial Release
*
* 1.2 Updated for Multimedia (J Gilborne)
*
* 1.3 Updated for FOTA Components (K Hunter) 10/21/2004
* Updated for OTA Diagnostics Components (K Hunter) 10/21/2004
* Updated Multimedia Component to include MultimediaEncoderDisplaySize
* Updated WapDeviceClass with documentation
*
* 1.4 Added for Browser Portal Version in the Sprint Extensions(K Hunter) 06/29/2005
* Added for IOTA Protocol Version in the Sprint Extensions(K Hunter) 06/29/2005
* Added DateNetworkType in the Sprint Extensions (K Hunter) 06/29/2005
*
* 1.5 Deleted CcppAccept-Encoding from SoftwarePlatform section (K Hunter) 09/08/2005
* Note: If the CcppAccept-Encoding is include in the rdf with a Multimedia device, then
* this will prohibit the device from streaming multimedia content.
*
* 1.5.1 Updated profie to validate with MAG ( D Durig ) 10/27/2005
* 1.5.2 Changed units of measure on the Multimedia Maximum Bit Rate for Streaming and for
* Encoding from fps to kbps ( J Bryan ) 11/10/2005
*
* 1.6 Added for Sprint On Demand, Capable and Version in the Sprint Extensions ( J Bryan ) 01/06/2006
* Added for Sprint MI-UI, Capable and Version in the Sprint Extensions ( J Bryan ) 01/10/2006
* Added x-pcs/od.content and x-pcs/theme to CcppAccept ( J Bryan ) 01/18/2006
*
* 1.7 Added # to the xpcs namespace URL. ( J Bryan ) 12/05/2006
* 1.8 Added GLMS attributes. ( J Bryan ) 02/28/2007
* 2.0 Added WiMAX attributes. ( J Bryan ) 01/21/2008
*
* Known issues
*
* Push characteristics are not defined yet
* Have not yet defined schema for Sprint Specific enhancements
*
*********************************************************************
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:prf="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#"
xmlns:xpcs="http://device.sprintpcs.com/namespace/xpcs#"
xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:ID="MyDeviceProfile">
<!--********************** Hardware Platform Description
***************************************-->
<prf:component>
<rdf:Description rdf:ID="HardwarePlatform">
<rdf:type
rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#HardwarePlatform"/>
<!-- ******** Vendor/model *******-->
<!-- Enter the vendor name here. This must
match the vendor name in the EDF -->
<prf:Vendor>
SAMSUNG
</prf:Vendor>
<!-- Enter the device model name here. This
must match the model name in the EDF -->
<prf:Model>
SPH-D700
</prf:Model>
<!-- Change if different -->
<prf:CPU>
ARM11
</prf:CPU>
<!--****** Display ******-->
<!-- Enter screen size in pixels here - width x height -->
<prf:ScreenSize>
480x800
</prf:ScreenSize>
<!-- "Yes" if device supports color -->
<prf:ColorCapable>
Yes
</prf:ColorCapable>
<!-- Enter the color or grayscale depth here -->
<prf:BitsPerPixel>
16
</prf:BitsPerPixel>
<!-- Change if not 1:1 -->
<prf:PixelAspectRatio>
1x1
</prf:PixelAspectRatio>
<!-- This should always be "Yes" -->
<prf:ImageCapable>
Yes
</prf:ImageCapable>
<!-- Enter the screen size in characters here. Use the default font. -->
<prf:ScreenSizeChar>
25x21
</prf:ScreenSizeChar>
<!-- Change the to "No" only if the default font on the device is not proportional -->
<prf:StandardFontProportional>
Yes
</prf:StandardFontProportional>
<!-- List the supported output character sets here. -->
<prf:OutputCharSet>
<rdf:Bag>
<rdf:li>ISO-10646-UCS-2</rdf:li>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>UTF-8</rdf:li>
</rdf:Bag>
</prf:OutputCharSet>
<!-- ******** Input capabilities ******-->
<!-- List the supported Input character sets here -->
<prf:InputCharSet>
<rdf:Bag>
<rdf:li>ISO-10646-UCS-2</rdf:li>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>UTF-8</rdf:li>
</rdf:Bag>
</prf:InputCharSet>
<!-- This should always be "Yes" -->
<prf:TextInputCapable>
Yes
</prf:TextInputCapable>
<!-- This value should only be changed if the device does not use a standard DTMF keypad -->
<prf:Keyboard>
Qwerty
</prf:Keyboard>
<!-- Enter the number of softkeys supported by the device -->
<prf:NumberOfSoftKeys>
0
</prf:NumberOfSoftKeys>
<!-- ********* Audio **********-->
<!-- This should always be "Yes" -->
<prf:SoundOutputCapable>
Yes
</prf:SoundOutputCapable>
<!-- This should be "Yes" for all voice capable devices -->
<prf:VoiceInputCapable>
Yes
</prf:VoiceInputCapable>
<!--******************************-->
</rdf:Description>
</prf:component>
<!--********************** Software Platform Description ***************************************-->
<prf:component>
<rdf:Description rdf:ID="SoftwarePlatform">
<rdf:type rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#SoftwarePlatform"/>
<!-- ***** Basic ******-->
<!-- Should be "Yes" for all Java capable devices -->
<prf:AcceptDownloadableSoftware>
No
</prf:AcceptDownloadableSoftware>
<!-- Use this for J2ME app support -->
<prf:DownloadableSoftwareSupport>
<rdf:Bag><rdf:li>application/java-archive</rdf:li></rdf:Bag>
</prf:DownloadableSoftwareSupport>
<!-- Enter the software version number here.
This must match the version reported via IOTA-->
<prf:SoftwareNumber>
EF02
</prf:SoftwareNumber>
<!-- Should not change if using Qualcomm software-->
<prf:OSName>
Google Android, L4
</prf:OSName>
<!-- Should not change if using Qualcomm software-->
<prf:OSVendor>
Google, Qualcomm
</prf:OSVendor>
<!-- Fill in version of DMSS Software base -->
<prf:OSVersion>
Android 2.3, SBAQ6085BSNACAZ4390
</prf:OSVersion>
<!-- ********** Java ***********-->
<!-- Should be yes for all Java capable products -->
<prf:JavaEnabled>
Yes
</prf:JavaEnabled>
<!-- Indicate MIDP + Sprint Extension profile support -->
<prf:JavaPlatform>
<rdf:Bag>
<rdf:li>Dalvik</rdf:li>
</rdf:Bag>
</prf:JavaPlatform>
<!-- Indicate the VM vendor/version here -->
<prf:JVMVersion>
<rdf:Bag><rdf:li>Dalvik</rdf:li></rdf:Bag>
</prf:JVMVersion>
<!-- ********* CCPP accept **********-->
<!-- List all accepted MIME types here -->
<prf:CcppAccept>
<rdf:Bag>
<!-- Markup languages -->
<rdf:li>text/html</rdf:li>
<rdf:li>text/plain</rdf:li>
<!-- Images -->
<rdf:li>image/gif</rdf:li>
<rdf:li>image/jpeg</rdf:li>
<rdf:li>image/jpg</rdf:li>
<rdf:li>image/gif</rdf:li>
<rdf:li>image/png</rdf:li>
<rdf:li>image/bmp</rdf:li>
<rdf:li>image/x-ms-bmp</rdf:li>
<rdf:li>image/vnd.wap.wbmp</rdf:li>
<!-- Audio / Multimedia -->
<rdf:li>audio/aac</rdf:li>
<rdf:li>audio/amr</rdf:li>
<rdf:li>audio/imelody</rdf:li>
<rdf:li>audio/mid</rdf:li>
<rdf:li>audio/midi</rdf:li>
<rdf:li>audio/mp3</rdf:li>
<rdf:li>audio/mpeg3</rdf:li>
<rdf:li>audio/mpeg</rdf:li>
<rdf:li>audio/mpg</rdf:li>
<rdf:li>audio/x-mid</rdf:li>
<rdf:li>audio/x-midi</rdf:li>
<rdf:li>audio/x-mp3</rdf:li>
<rdf:li>audio/x-mpeg3</rdf:li>
<rdf:li>audio/x-mpeg</rdf:li>
<rdf:li>audio/x-mpg</rdf:li>
<!-- Video / Multimedia -->
<rdf:li>video/mpeg4</rdf:li>
<rdf:li>video/mp4</rdf:li>
<rdf:li>video/3gp</rdf:li>
<rdf:li>video/3gpp</rdf:li>
<rdf:li>video/3gpp2</rdf:li>
<!-- Applications -->
<rdf:li>application/java-archive</rdf:li>
<rdf:li>application/ogg</rdf:li>
<rdf:li>application/vnd.oma.dd+xml</rdf:li>
<rdf:li>application/vnd.oma.drm.message</rdf:li>
<rdf:li>application/vnd.wap.sic</rdf:li>
<rdf:li>application/vnd.wap.xhtml+xml</rdf:li>
<rdf:li>application/xhtml+xml</rdf:li>
<rdf:li>application/x-pcs-mcd+xml</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</prf:CcppAccept>
<!-- List all accepted character sets here -->
<prf:CcppAccept-Charset>
<rdf:Bag>
<rdf:li>ISO-10646-UCS-2</rdf:li>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>UTF-8</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</prf:CcppAccept-Charset>
<!-- List all accepted languages here in order of preference -->
<prf:CcppAccept-Language>
<rdf:Seq>
<rdf:li>en-us</rdf:li>
<!-- Enter other items... -->
</rdf:Seq>
</prf:CcppAccept-Language>
<!-- List all accepted transfer encodings here -->
<!-- Deleted CcppAccept-Encoding K.Hunter in 1.5-->
<!-- ******** Input Encoders ******-->
<prf:AudioInputEncoder>
<rdf:Bag><rdf:li> </rdf:li></rdf:Bag>
</prf:AudioInputEncoder>
<!--******************************-->
</rdf:Description>
</prf:component>
<!--********************** Network Characteristics Description ***************************************-->
<prf:component>
<rdf:Description rdf:ID="NetworkCharacteristics">
<rdf:type rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#NetworkCharacteristics"/>
<!-- Indicate support for SSL 3.0 and TLS 1.0 -->
<prf:SecuritySupport>
<rdf:Bag>
<rdf:li>SSL3.0</rdf:li>
<rdf:li>TLS</rdf:li>
</rdf:Bag>
</prf:SecuritySupport>
<!-- Indicate support for IS-2000 release 0 packet data bearer -->
<!-- May add more detail here in a later rev. -->
<prf:SupportedBearers>
<rdf:Bag>
<rdf:li>IPv4</rdf:li>
<rdf:li>IPv6</rdf:li>
<rdf:li>HTTP 1.1 (http, https)</rdf:li>
<rdf:li>FTP</rdf:li>
<rdf:li>file://</rdf:li>
<rdf:li>TLS</rdf:li>
<rdf:li>SMS</rdf:li>
</rdf:Bag>
</prf:SupportedBearers>
</rdf:Description>
</prf:component>
<!--********************** Browser UA Description ***************************************-->
<prf:component>
<rdf:Description rdf:ID="BrowserUA">
<rdf:type rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#BrowserUA"/>
<!-- ********* Browser Identification ********** -->
<!-- Enter the browser vendor/product name here -->
<prf:BrowserName>
Android Browser
</prf:BrowserName>
<!-- Enter the browser version here -->
<prf:BrowserVersion>
0.6
</prf:BrowserVersion>
<!-- ********** Capabilities *********** -->
<!-- Frames are not supported -->
<prf:FramesCapable>
Yes
</prf:FramesCapable>
<!-- Basic tables are supported in xhtml-basic -->
<prf:TablesCapable>
Yes
</prf:TablesCapable>
<!-- Frames are not supported -->
<prf:PreferenceForFrames>
No
</prf:PreferenceForFrames>
<!-- *********** Applet / Script support is not required ********** -->
<prf:DownloadableBrowserApps>
<rdf:Bag><rdf:li>No</rdf:li></rdf:Bag>
</prf:DownloadableBrowserApps>
<prf:JavaAppletEnabled>
No
</prf:JavaAppletEnabled>
<prf:JavaScriptEnabled>
Yes
</prf:JavaScriptEnabled>
<prf:JavaScriptVersion>
1.5
</prf:JavaScriptVersion>
<!-- ************* XHTML support - indicate XHTML-Basic 1.0 ************ -->
<prf:XhtmlVersion>
XHTML-Basic/1.1
</prf:XhtmlVersion>
<prf:XhtmlModules>
<rdf:Bag><rdf:li> </rdf:li></rdf:Bag>
</prf:XhtmlModules>
<!--******************************-->
</rdf:Description>
</prf:component>
<!--********************** WAP Characteristics Description ***************************************-->
<prf:component>
<rdf:Description rdf:ID="WapCharacteristics">
<rdf:type rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#WapCharacteristics"/>
<!--******** General ***********-->
<!-- WAP Device Class defined in http://www1.wapforum.org/tech/documents/PROP-ClassConform-20000211.pdf -->
<prf:WapDeviceClass>C</prf:WapDeviceClass>
<prf:WapVersion>
"1.2.1 (WML, WSP/WTLS)", "2.0 (limited supports for HTML-MP and wCSS)"
</prf:WapVersion>
<!--*********** WML ************-->
<!-- If full wml 2.0 is supported, it should be added here -->
<prf:WmlVersion>
<rdf:Bag>
<rdf:li>2.0</rdf:li>
</rdf:Bag>
</prf:WmlVersion>
<!-- Enter the maximum deck size for wml -->
<prf:WmlDeckSize>
8000000
</prf:WmlDeckSize>
<!--******************************-->
</rdf:Description>
</prf:component>
<!--********************** Push Characteristics Description ***************************************-->
<!-- Note: This entire section is TBD in this revision -->
<prf:component>
<rdf:Description rdf:ID="PushCharacteristics">
<rdf:type rdf:resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#PushCharacteristics"/>
<prf:Push-Accept>
<rdf:Bag>
<rdf:li>text/plain</rdf:li>
</rdf:Bag>
</prf:Push-Accept>
<prf:Push-Accept-Encoding>
<rdf:Bag>
<rdf:li>base64</rdf:li>
</rdf:Bag>
</prf:Push-Accept-Encoding>
<prf:Push-Accept-AppID>
<rdf:Bag>
<rdf:li></rdf:li>
</rdf:Bag>
</prf:Push-Accept-AppID>
<prf:Push-MsgSize>
<rdf:Bag>
<rdf:li>4096</rdf:li>
</rdf:Bag>
</prf:Push-MsgSize>
<!-- ********************************-->
</rdf:Description>
</prf:component>
<!-- ****************** Sprint UA Prof Extensions ******************************-->
<prf:component>
<rdf:Description rdf:ID="SprintExtensions">
<rdf:type rdf:resource="http://device.sprintpcs.com/uaprof/sprint-uaprof-extensions.xml"/>
<!-- MultimediaPlayback support -->
<xpcs:MultimediaPlaybackSupport>
<!-- example -->
Yes
</xpcs:MultimediaPlaybackSupport>
<!-- Multimedia Streaming Support -->
<xpcs:MultimediaStreamingSupport>
<!-- example -->
Yes
</xpcs:MultimediaStreamingSupport>
<!-- Multimedia Encoding Support -->
<xpcs:MultimediaEncodingSupport>
<!-- example -->
Yes
</xpcs:MultimediaEncodingSupport>
<!-- Type and version of MM player supported -->
<xpcs:MultimediaPlayer>
<!-- example -->
CORE/6.506.4.1 OpenCORE/2.02 (Linux;Android 2.3.3)
</xpcs:MultimediaPlayer>
<!-- Type and version of MM encoder supported -->
<xpcs:MultimediaEncoder>
<!-- example -->
CORE/6.506.4.1 OpenCORE/2.02 (Linux;Android 2.3.3)
</xpcs:MultimediaEncoder>
<!-- Multimedia Encoder Supported Display Size(s) -->
<xpcs:MultimediaEncoderDisplaySize>
<!-- example -->
800x480
<rdf:Bag>
<rdf:li>
</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:MultimediaEncoderDisplaySize>
<!-- File Format the decoder supports -->
<xpcs:MultimediaFileFormatForDecoder>
<rdf:Bag>
<rdf:li>MP4</rdf:li>
<rdf:li>3GP</rdf:li>
<rdf:li>3G2</rdf:li>
<rdf:li>WMV</rdf:li>
<rdf:li>AVI</rdf:li>
<rdf:li>FLV</rdf:li>
<rdf:li>MKV</rdf:li>
<rdf:li>M4A</rdf:li>
<rdf:li>AMR</rdf:li>
<rdf:li>AAC</rdf:li>
<rdf:li>MP3</rdf:li>
<rdf:li>WMA</rdf:li>
<rdf:li>AC3</rdf:li>
<rdf:li>OGG</rdf:li>
<rdf:li>WAV</rdf:li>
<rdf:li>FLAC</rdf:li>
<rdf:li>EVC</rdf:li>
<rdf:li>QCP</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:MultimediaFileFormatForDecoder>
<!-- File Format the encoder supports -->
<xpcs:MultimediaFileFormatForEncoder>
<rdf:Bag>
<rdf:li>3GP</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:MultimediaFileFormatForEncoder>
<!-- Display size the Multimedia player supports -->
<xpcs:MultimediaVideoDisplaySize>
<rdf:Bag>
<rdf:li>
800x480
</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:MultimediaVideoDisplaySize>
<!-- Maximum frame rate the device supports when playing local files -->
<xpcs:MultimediaMaximumFrameRateForPlayback>
<!-- example -->
30fps
</xpcs:MultimediaMaximumFrameRateForPlayback>
<!-- Maximum frame rate the device supports when streaming content -->
<xpcs:MultimediaMaximumFrameRateForStreaming>
<!-- example -->
30fps
</xpcs:MultimediaMaximumFrameRateForStreaming>
<!-- Maximum frame rate the device supports when encoding content -->
<xpcs:MultimediaMaximumFrameRateForEncoding>
<!-- example -->
30fps
</xpcs:MultimediaMaximumFrameRateForEncoding>
<!-- Maximum bit rate the Multimedia player supports when playing local files -->
<xpcs:MultimediaMaximumBitRateForPlayback>
<!-- example -->
12Mbps
</xpcs:MultimediaMaximumBitRateForPlayback>
<!-- Maximum bit rate the device supports when streaming content -->
<xpcs:MultimediaMaximumBitRateForStreaming>
<!-- example -->
10Mbps
</xpcs:MultimediaMaximumBitRateForStreaming>
<!-- Maximum bit rate the device supports when encoding content -->
<xpcs:MultimediaMaximumBitRateForEncoding>
<!-- example -->
12Mbps
</xpcs:MultimediaMaximumBitRateForEncoding>
<!-- List all supported video codecs for decoding here -->
<xpcs:VideoCodecsForDecoding>
<rdf:Bag>
<rdf:li>H.264 BP,MP,HP</rdf:li>
<rdf:li>MPEG4 SP,ASP</rdf:li>
<rdf:li>XviD</rdf:li>
<rdf:li>H.263 P3</rdf:li>
<rdf:li>Sorenson Spark</rdf:li>
<rdf:li>VC-1 MP</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:VideoCodecsForDecoding>
<!-- List all supported video codecs for encoding here -->
<xpcs:VideoCodecsForEncoding>
<rdf:Bag>
<rdf:li>H.264 SP,MP</rdf:li>
<rdf:li>H.263 P0</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:VideoCodecsForEncoding>
<!-- List all supported audio codecs here -->
<xpcs:AudioCodecsForDecoding>
<rdf:Bag>
<rdf:li>M4A</rdf:li>
<rdf:li>AMR-NB</rdf:li>
<rdf:li>AMR-WB</rdf:li>
<rdf:li>AAC</rdf:li>
<rdf:li>AAC+</rdf:li>
<rdf:li>eAAC+</rdf:li>
<rdf:li>MP3</rdf:li>
<rdf:li>WMA</rdf:li>
<rdf:li>AC3</rdf:li>
<rdf:li>OGG</rdf:li>
<rdf:li>WAV</rdf:li>
<rdf:li>FLAC</rdf:li>
<rdf:li>EVRC</rdf:li>
<rdf:li>QCELP</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:AudioCodecsForDecoding>
<!-- List all supported audio codecs here -->
<xpcs:AudioCodecsForEncoding>
<rdf:Bag>
<rdf:li>AAC</rdf:li>
<rdf:li>AMR-NB</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:AudioCodecsForEncoding>
<!-- MCD version -->
<xpcs:SprintMcdVersion>
3.5.4
</xpcs:SprintMcdVersion>
<!-- PictureMailSupport -->
<xpcs:PictureMailSupport>
<!-- example -->
No
</xpcs:PictureMailSupport>
<!-- VideoMailSupport -->
<xpcs:VideoMailSupport>
<!-- example -->
Yes
</xpcs:VideoMailSupport>
<xpcs:MobileOriginatedSmsSupport>
<!-- example -->
Yes
</xpcs:MobileOriginatedSmsSupport>
<!-- *************** IOTA/FOTA Components *****************-->
<xpcs:IOTAProtocolVersion>
<!--example -->
N/A
</xpcs:IOTAProtocolVersion>
<xpcs:FotaProtocolVersion>
<!-- example -->
N/A
</xpcs:FotaProtocolVersion>
<xpcs:FotaClientVersion>
<!-- example -->
N/A
</xpcs:FotaClientVersion>
<xpcs:FotaClientVendor>
<!-- example -->
N/A
</xpcs:FotaClientVendor>
<!-- *************** OTA Diagnostics Components *****************-->
<xpcs:DiagnosticsProtocolVersion>
<!-- example -->
1.1.0
</xpcs:DiagnosticsProtocolVersion>
<xpcs:DiagnosticsClientVersion>
<!-- example -->
3.2.13
</xpcs:DiagnosticsClientVersion>
<xpcs:DiagnosticsClientVendor>
<!-- example -->
CIQ
</xpcs:DiagnosticsClientVendor>
<!-- *************** Sprint Browser Components *****************-->
<xpcs:BrowserPortalVersion>
<!--
**Values for devices**
1.0 for 1x
2.0 for DO
-->
2.0
</xpcs:BrowserPortalVersion>
<!-- *************** Sprint Device Data Network Types*****************-->
<xpcs:DataNetworkTypes>
<rdf:Bag>
<rdf:li>IS2000</rdf:li>
<rdf:li>EVDO</rdf:li>
<rdf:li>DOrA</rdf:li>
<rdf:li>WiFi</rdf:li>
<rdf:li>WiMax</rdf:li>
</rdf:Bag>
</xpcs:DataNetworkTypes>
<!-- *************** Sprint On Demand *****************-->
<xpcs:OnDemandCapable>
<!-- example -->
No
</xpcs:OnDemandCapable>
<xpcs:OnDemandVersion>
<!-- example -->
N/A
</xpcs:OnDemandVersion>
<!-- *************** Sprint MI-UI *****************-->
<xpcs:MI-UICapable>
<!-- example -->
No
</xpcs:MI-UICapable>
<xpcs:MI-UIVersion>
<!-- example -->
N/A
</xpcs:MI-UIVersion>
<!-- *************** Sprint GLMS *****************-->
<xpcs:GLMSClientVendor>
<!-- example -->
N/A
</xpcs:GLMSClientVendor>
<xpcs:GLMSProtocolVersion>
<!--example -->
N/A
</xpcs:GLMSProtocolVersion>
<xpcs:GLMSClientVersion>
<!-- example -->
N/A
</xpcs:GLMSClientVersion>
<!-- ********************************-->
<!-- ****************** Sprint WiMAX Extensions ******************************-->
<xpcs:AdvertisingCapable>
<!-- example -->
No
</xpcs:AdvertisingCapable>
<xpcs:CommerceCapable>
<!-- example -->
No
</xpcs:CommerceCapable>
<xpcs:EmailCapable>
<!-- example -->
No
</xpcs:EmailCapable>
<xpcs:FixedVoIPCapable>
<!-- example -->
No
</xpcs:FixedVoIPCapable>
<xpcs:GamingCapable>
<!-- example -->
No
</xpcs:GamingCapable>
<xpcs:IMVideoCallingCapable>
<!-- example -->
No
</xpcs:IMVideoCallingCapable>
<xpcs:VoiceChatCapable>
<!-- example -->
No
</xpcs:VoiceChatCapable>
<xpcs:IntelligentSearchCapable>
<!-- example -->
No
</xpcs:IntelligentSearchCapable>
<xpcs:LBSCapable>
<!-- example -->
Yes
</xpcs:LBSCapable>
<xpcs:MobileTVORVODCapable>
<!-- example -->
No
</xpcs:MobileTVORVODCapable>
<xpcs:RadioCapable>
<!-- example -->
No
</xpcs:RadioCapable>
<xpcs:DeviceType>
<!-- example -->
</xpcs:DeviceType>
<xpcs:HardwareVersion>
<!-- example -->
</xpcs:HardwareVersion>
<xpcs:ManufacturerWiMAXRadioModule>
<!-- example -->
SAMSUNG
</xpcs:ManufacturerWiMAXRadioModule>
<xpcs:FirmwareVersionWiMAXRadioModule>
<!-- example -->
DH24
</xpcs:FirmwareVersionWiMAXRadioModule>
<xpcs:ModelWiMAXRadioModule>
<!-- example -->
CMC730S
</xpcs:ModelWiMAXRadioModule>
<xpcs:GPSChipsetVendor>
<!-- example -->
QUALCOMM
</xpcs:GPSChipsetVendor>
<xpcs:GPSChipsetModel>
<!-- example -->
QSC6085
</xpcs:GPSChipsetModel>
<xpcs:OMADMCapable >
<!-- example -->
Yes
</xpcs:OMADMCapable>
<xpcs:OMADMVendor >
<!-- example -->
SAMSUNG
</xpcs:OMADMVendor>
<xpcs:OMADMVersion>
<!-- example -->
1.2
</xpcs:OMADMVersion>
<xpcs:ConnectionManagerVendor >
<!-- example -->
</xpcs:ConnectionManagerVendor>
<xpcs:ConnectionManagerVersion>
<!-- example -->
</xpcs:ConnectionManagerVersion>
<xpcs:NavigationSupport>
<!-- example -->
Yes
<rdf:Bag>
<rdf:li></rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:NavigationSupport>
<xpcs:EmbeddedApplicationsCapable>
<!-- example -->
No
</xpcs:EmbeddedApplicationsCapable>
<xpcs:DownStreamBufferSize>
<!-- example -->
0
</xpcs:DownStreamBufferSize>
<xpcs:UpStreamBufferSize>
<!-- example -->
0
</xpcs:UpStreamBufferSize>
<xpcs:TotalDeviceMemory>
<!-- example -->
0
</xpcs:TotalDeviceMemory>
<xpcs:TotalDeviceFlash>
<!-- example -->
0
</xpcs:TotalDeviceFlash>
<xpcs:ExternalMemorySlot>
<!-- example -->
Yes
</xpcs:ExternalMemorySlot>
<xpcs:ExternalMemoryMaxSize>
<!-- example -->
32GB
</xpcs:ExternalMemoryMaxSize>
<xpcs:AudioJack>
<!-- example -->
3.5mm
</xpcs:AudioJack>
<xpcs:SupportedApplications>
<!-- example -->
<rdf:Bag>
<rdf:li></rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:SupportedApplications>
<xpcs:VOIPAnalogJacks>
<!-- example -->
0
</xpcs:VOIPAnalogJacks>
<xpcs:AntiVirus>
<!-- example -->
No
</xpcs:AntiVirus>
<xpcs:AntiVirusVendor>
<!-- example -->
N/A
</xpcs:AntiVirusVendor>
<xpcs:AntiSpam>
<!-- example -->
No
</xpcs:AntiSpam>
<xpcs:AntiSpamVendor>
<!-- example -->
N/A
</xpcs:AntiSpamVendor>
<xpcs:CameraMegaPixels>
<!-- example -->
5
</xpcs:CameraMegaPixels>
<xpcs:CameraHighestImageResolution>
<!-- example -->
2560x1920
</xpcs:CameraHighestImageResolution>
<xpcs:CameraZoomCapable>
<!-- example -->
Yes
</xpcs:CameraZoomCapable>
<xpcs:CameraBuiltInFlash>
<!-- example -->
Yes
</xpcs:CameraBuiltInFlash>
<xpcs:CamcorderResolution>
<!-- example -->
1280x720
</xpcs:CamcorderResolution>
<xpcs:CamcorderZoomCapable>
<!-- example -->
Yes
</xpcs:CamcorderZoomCapable>
<xpcs:DeviceIdentifierType>
<!-- example -->
<rdf:Bag>
<rdf:li>ESN</rdf:li>
<rdf:li>MEID</rdf:li>
<!-- Enter other items... -->
</rdf:Bag>
</xpcs:DeviceIdentifierType>
</rdf:Description>
</prf:component>
</rdf:Description>
</rdf:RDF>

beat me to it lol!!! just was posting now

Hah, I figured I wouldn't be the only one.

still says 2.3.3 tho .... bummer

Dont mind the versions posted until its officially released. It was mentioned that some versions of 2.2 still had 2.1 listed in the RDF.

Darkshneider said:
Dont mind the versions posted until its officially released. It was mentioned that some versions of 2.2 still had 2.1 listed in the RDF.
Click to expand...
Click to collapse
I think this is what they're workin on to release after we already get gingerbread. I'm pretty sure we will get EE19, and we'll get bug/security fixes with this after they finish this. And I bet this'll be 2.3.4
Sent from my perfect epic

Really, there are a lot of phones being built with 2.3.3; right now there are very few phones out there (that I know of) that are using 2.3.4. In fact, I think only the Nexus and Gx phones have 2.3.4. Anybody know of others?

AtomicPlayboy said:
Really, there are a lot of phones being built with 2.3.3; right now there are very few phones out there (that I know of) that are using 2.3.4. In fact, I think only the Nexus and Gx phones have 2.3.4. Anybody know of others?
Click to expand...
Click to collapse
i thought that 2.3.4 was for phones with nfc support only.

Okay, that would definitely rule out the Epic then. That probably limits it to the Nexus S, even.

FYI: FileMerge shows 1 difference between the RDFs, in the build number (EE19 -> EF02). No new info here, it's just a bugfix test build. Wonder if it will leak into the wild.

AtomicPlayboy said:
FYI: FileMerge shows 1 difference between the RDFs, in the build number (EE19 -> EF02). No new info here, it's just a bugfix test build. Wonder if it will leak into the wild.
Click to expand...
Click to collapse
I highly doubt it. Otherwise, we might already seen a leaked EE19.

southpark-droid said:
i thought that 2.3.4 was for phones with nfc support only.
Click to expand...
Click to collapse
It's out for the Nexus One so nope.

ccnd8 said:
I highly doubt it. Otherwise, we might already seen a leaked EE19.
Click to expand...
Click to collapse
As stated before by many sources, if EE19 is indeed the final build we probably won't see a leak. They said the final builds have never been "leaked".

So what is EF02 then? Patch build for a later update?

Yes
AtomicPlayboy said:
So what is EF02 then? Patch build for a later update?
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Transparent App

AtomicPlayboy said:
So what is EF02 then? Patch build for a later update?
Click to expand...
Click to collapse
Could very well be... I guess were going to find out as time rolls on by.... Between now and the rumored June 20th possible release date is going to seem like forever.... Until then I guess I'll keep bouncing back and forth between Bonsai v4.1.1 and EE03...

Updated! http://isgingerbreadoutforepic4g.com/

We need Whosdaman before we make assumptions on what this build means.

http://forum.xda-developers.com/showthread.php?t=1106858
|| Acer || said:
We need Whosdaman before we make assumptions on what this build means.
Click to expand...
Click to collapse

noobnl said:
http://forum.xda-developers.com/showthread.php?t=1106858
Click to expand...
Click to collapse
I saw that after I posted here lol

[DEV][DISCUSS]Nokia 1520 Partition Info .. From FFU

Code:
<?xml version="1.0" encoding="UTF-8"?>
-<DeviceLayout xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<Partitions>
<!-- QC 8974 PRODUCTION DEVICE LAYOUT -->
<!-- PROVISIONED DATA SECTION START - WARNING DO NOT ALTER BELOW OR FFU WILL REMOVE DEVICE SETTINGS -->
<!-- Device Provisioning Partition -->
-<Partition>
<Name>DPP</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<TotalSectors>16384</TotalSectors>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- QUALCOMM 8974 SPECIFIC PROVISIONING PARTITIONS -->
<!-- Modem golden file system -->
-<Partition>
<Name>MODEM_FSG</Name>
<TotalSectors>3072</TotalSectors>
<Type>{638FF8E2-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Modem live file systems -->
-<Partition>
<Name>MODEM_FS1</Name>
<TotalSectors>3072</TotalSectors>
<Type>{EBBEADAF-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>MODEM_FS2</Name>
<TotalSectors>3072</TotalSectors>
<Type>{0A288B1F-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Modem File System Cookie partition -->
-<Partition>
<Name>MODEM_FSC</Name>
<TotalSectors>16</TotalSectors>
<Type>{57B90A16-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- DDR training partition -->
-<Partition>
<Name>DDR</Name>
<TotalSectors>16</TotalSectors>
<Type>{20A0C19C-286A-42FA-9CE7-F64C3226A794}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Secure Software Download -->
-<Partition>
<Name>SSD</Name>
<TotalSectors>16</TotalSectors>
<Type>{2C86E742-745E-4FDD-BFD8-B6A7AC638772}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- UEFI Variable Services Partitions -->
-<Partition>
<Name>UEFI_BS_NV</Name>
<TotalSectors>512</TotalSectors>
<Type>{F0B4F48B-AEBA-4ECF-9142-5DC30CDC3E77}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>UEFI_RT_NV</Name>
<TotalSectors>512</TotalSectors>
<Type>{6BB94537-7D1C-44D0-9DFE-6D77C011DBFC}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- PROVISIONED DATA SECTION END - WARNING DO NOT ALTER ABOVE OR FFU WILL REMOVE DEVICE SETTINGS -->
<!-- START QUALCOMM 8974 BOOT PARTITIONS -->
<!-- Bootloaders -->
-<Partition>
<Name>SBL1</Name>
<TotalSectors>1024</TotalSectors>
<!-- Qualcomm defined for SBL1 -->
<Type>{DEA0BA2C-CBDD-4805-B4F9-F428251C3E98}</Type>
<Bootable>true</Bootable>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Debug Image Bootloader for Crash dump collection -->
-<Partition>
<Name>DBI</Name>
<TotalSectors>64</TotalSectors>
<Type>{D4E0D938-B7FA-48C1-9D21-BC5ED5C4B203}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>UEFI</Name>
<TotalSectors>4096</TotalSectors>
<Type>{400FFDCD-22E0-47E7-9A23-F16ED9382388}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>RPM</Name>
<TotalSectors>1000</TotalSectors>
<Type>{098DF793-D712-413D-9D4E-89D711772228}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>TZ</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- TrustZone Applets -->
-<Partition>
<Name>WINSECAPP</Name>
<TotalSectors>1024</TotalSectors>
<Type>{69B4201F-A5AD-45EB-9F49-45B38CCDAEF5}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>TZAPPS</Name>
<TotalSectors>32768</TotalSectors>
<Type>{14D11C40-2A3D-4F97-882D-103A1EC09333}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Bootloaders Backup Section (Sizes must match) -->
-<Partition>
<Name>BACKUP_SBL1</Name>
<TotalSectors>1024</TotalSectors>
<!-- Qualcomm defined for SBL1 -->
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<Bootable>true</Bootable>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>BACKUP_DBI</Name>
<TotalSectors>64</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>BACKUP_UEFI</Name>
<TotalSectors>4096</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>BACKUP_RPM</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>BACKUP_TZ</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- TrustZone Applet Backup Sections (Sizes must match) -->
-<Partition>
<Name>BACKUP_WINSECAPP</Name>
<TotalSectors>1024</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>BACKUP_TZAPPS</Name>
<TotalSectors>32768</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- ACPI table storage -->
-<Partition>
<Name>PLAT</Name>
<TotalSectors>16384</TotalSectors>
<FileSystem>FAT</FileSystem>
<Type>{543C031A-4CB6-4897-BFFE-4B485768A8AD}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- END QUALCOMM 8974 BOOT PARTITIONS -->
<!-- START MICROSOFT PARTITIONS -->
<!-- EFI System Partition -->
-<Partition>
<Name>EFIESP</Name>
<FileSystem>FAT</FileSystem>
<TotalSectors>65536</TotalSectors>
<!-- PARTITION_SYSTEM_GUID <Type>{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}</Type> -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
-<Partition>
<Name>MMOS</Name>
<FileSystem>FAT</FileSystem>
<MinFreeSectors>8192</MinFreeSectors>
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
</Partition>
-<Partition>
<Name>MainOS</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<!-- Accounts for 400MB free sectors and 256MB page file as defined in registry by package src\baseos\prod\packages\arm\armmemory -->
<MinFreeSectors>1343488</MinFreeSectors>
<ByteAlignment>0x800000</ByteAlignment>
<ClusterSize>0x4000</ClusterSize>
<FileSystem>NTFS</FileSystem>
<AttachDriveLetter>false</AttachDriveLetter>
</Partition>
-<Partition>
<Name>Data</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<UseAllSpace>true</UseAllSpace>
<ByteAlignment>0x800000</ByteAlignment>
<ClusterSize>0x4000</ClusterSize>
<FileSystem>NTFS</FileSystem>
</Partition>
</Partitions>
<!-- END MICROSOFT PARTITIONS -->
<SectorSize>512</SectorSize>
<ChunkSize>128</ChunkSize>
<DefaultPartitionByteAlignment>0x200000</DefaultPartitionByteAlignment>
</DeviceLayout>

Also Interesting is a package named " MicrosoftEmployeesApp.spkg" anyone noticed that when extracting FFU. ??
Code:
<PackageFile Path="$(mspackageroot)\pos\$(cputype)\$(buildtype)" Name="Microsoft.EmployeeApps.spkg" NoBasePackage="false" Resolution="*" Language="*">
sOME Qualcomm Diag Packages found :
Code:
Qualcomm.QC8974.DiagRouter.spkg
Qualcomm.QC8974.qccomposite.spkg
Qualcomm.QC8974.DiagBridge.spkg

Registry files .. attached.
Hackers/Moders please check the Qualcomm Registry files.
Can we manipulate those .inf files and add custom content to interact directly with the processor.
I wish Bepe and dcordes could help with these.

tids2k said:
Code:
<?xml version="1.0" encoding="UTF-8"?>
-<DeviceLayout xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
...
Click to expand...
Click to collapse
that is not a secret anyway
MicrosoftEmployeesApp.spkg
Click to expand...
Click to collapse
the best thing you can do is uploading whole \Windows\Packages content.
I have yet to get my hands on 1520 ROM, though, I am almost sure this package is useless.
Registry files .. attached.
Hackers/Moders please check the Qualcomm Registry files.
Can we manipulate those .inf files and add custom content to interact directly with the processor.
Click to expand...
Click to collapse
What for? You still can't edit these files anyhow. Neither you can flash edited ROM.
I wish Bepe and dcordes could help with these.
Click to expand...
Click to collapse
oh lol...

ultrashot said:
that is not a secret anyway
the best thing you can do is uploading whole \Windows\Packages content.
I have yet to get my hands on 1520 ROM, though, I am almost sure this package is useless.
What for? You still can't edit these files anyhow. Neither you can flash edited ROM.
oh lol...
Click to expand...
Click to collapse
Thanks for your feedback ultra, I am new to the WP8 as I just thought extracting the Rom and providing some info on the partition layout of the device might help in knowing the partitions and bootloader mount points that might help in future unlocks.
If you need anything from the rom please do ask.
Thanks.

tids2k said:
Thanks for your feedback ultra, I am new to the WP8 as I just thought extracting the Rom and providing some info on the partition layout of the device might help in knowing the partitions and bootloader mount points that might help in future unlocks.
If you need anything from the rom please do ask.
Thanks.
Click to expand...
Click to collapse
ultrashot said:
the best thing you can do is uploading whole \Windows\Packages content.
Click to expand...
Click to collapse
10char10char

ultrashot said:
10char10char
Click to expand...
Click to collapse
Here is the packages folder ...

This is the latest registry details from the latest FFU from Nokia.
Might be useful for some.
{
"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"
}

Sd card access fails for many apps

Hi,
I rooted my device and used a sd fix app but some apps cannot access the sd card (tapatalk, whatsapp,and many more)
Has someone an Idea?
It seems that there is a problem with the correct path
Could someone post a correctly working platform.xml?
And a mount listing?
Here is mine.
?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Copyright (C) 2013 Broadcom Corporation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.BLUETOOTH_STACK" >
<group gid="net_bt_stack" />
</permission>
<permission name="android.permission.NET_TUNNELING" >
<group gid="vpn" />
</permission>
<permission name="android.permission.SYSTEM_GROUP_INTERNAL" >
<group gid="system" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="com.sec.android.permission.CAMERA" >
<group gid="camera" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>
<permission name="android.permission.NET_ADMIN" >
<group gid="net_admin" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
<!-- Group that can read detailed network usage statistics -->
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY">
<group gid="net_bw_stats" />
</permission>
<!-- Group that can modify how network statistics are accounted -->
<permission name="android.permission.MODIFY_NETWORK_ACCOUNTING">
<group gid="net_bw_acct" />
</permission>
<permission name="android.permission.LOOP_RADIO" >
<group gid="loop_radio" />
</permission>
<!-- The group that releated with VPN -->
<permission name="android.permission.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>
<permission name="android.permission.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>
<permission name="android.permission.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>
<!-- The group that releated with VPN -->
<permission name="com.sec.android.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>
<permission name="com.sec.android.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>
<permission name="com.sec.android.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>
<!-- The group that releated with URL -->
<permission name="com.sec.android.SAMSUNG_GET_URL" >
<group gid="secnetfilter" />
</permission>
<!-- Group that can use gscaler -->
<permission name="com.sec.android.permission.USE_GSCALER" >
<group gid="graphics" />
</permission>
<!-- Except for SysScope, DO NOT USE this permission. -->
<permission name="com.sec.android.app.sysscope.permission.ACCESS_SYSTEM_INFO_SYSSCOPE_ONLY" >
<group gid="radio" />
</permission>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.WAKE_LOCK" uid="media" />
<assign-permission name="android.permission.UPDATE_DEVICE_STATS" uid="media" />
<assign-permission name="android.permission.UPDATE_APP_OPS_STATS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
<!-- This is a list of all the libraries available for application
code to link against. -->
<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
<!--
<library name="javax.btobex"
file="/system/framework/javax.btobex.jar"/>
-->
</permissions>
Click to expand...
Click to collapse
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=697168k,nr_inodes=130216,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware-modem vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/hidden /preload ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/179:65 /mnt/media_rw/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
/dev/block/dm-0 /mnt/asec/com.google.android.apps.docs.editors.docs-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue
Click to expand...
Click to collapse

Finally... unbrick your Lumia device QHSUSB_DLOAD without JTAG

04/30/2015​And THE WAIT IS OVER ... after almost two months without telephone, as this has happened to me in February, with the help of you... have achieved UNBRICK LUMIA DEVICES WITHOUT JTAG ONLY WITH USB. Thank you, thank infinitely.
Warning: use this tutorial at your own risk, I do not responsible of anything. To me it worked.​
05/25/2015
Simple method:
Yesterday update to WPRT 2.10 was released, which is able to fix DLOAD scenarios for lumias.
Here is the link.​
--------------------------------------
If this does not work, try the advanced method:
Let's to the steps:
Attachment files in the same thread.
1) Install Thor2 (incluiding on WPRT): http://go.microsoft.com/fwlink/?LinkID=525569
2) Download your firmware lumia with NaviFirm
3) Install Drivers
4) Go to the folder where it is thor 2 from cmd (run administrator)
cd C:...
Use this command line to extract gtp0.bin from ffu image
Code:
thor2 -mode ffureader -ffufile "C:\rm-914\XXX.ffu" -dump_gpt -filedir C:\dump
this command will create gpt0.bin and rename it as msimage.mbn
mine was F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD so my hex file in binary format was F771E62AF89994064F77CD3BC16829503BDF9A3D.bin
convert this binary file to hex using bin2hex.exe
Code:
bin2hex F771E62AF89994064F77CD3BC16829503BDF9A3D.bin HEX.hex
open .hex file in notepad
insert :020000042A00D0 in first line
and :040000052A000000CD before the last line
or
Hex files already created starting in the bin, use RESPONSIBLY depending on your Lumia device
https://mega.co.nz/#!A4903TYT!YeAiCZSrRVrKhOp8CAOF5z0ULtcfyvxuXqhZA1SA5iQ
Now you have HEX.hex and msimage.mbn
the use this command line
Code:
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
Ready, disconnect the battery and reconnect. Now connect your phone to the PC
Yeah, his phone started life with red screen!
Charge the battery
5) Flash rom: Now, in the case of Lumia 520/521
Code:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Nokia\Packages\Products\rm-915\XXX.vpl
.VPL remember it is not ffu. After the process 100%, your device turn with green screen, and:
Code:
thor2 -mode rnd -bootnormalmode
:highfive:
Some versions of Lumia, especially Lumia 820, 920, 920T, 925, 1020 (several models) have different .HEX, attached in the correct thread files ''CorrectedHexFiles.zip''
thanks @Heathcliff74
thanks @zapirkon and others users participated
thanks @ TheBITLINK aka BIT of Windows Insider.
Special thanks to Rathina Balan and AnnanZubair of Windows Insider Program
Thanks all... :fingers-crossed: they are the best

there is mbn file in the ffu
issw_ape_MSM_v1.mbn
Click to expand...
Click to collapse
but I don't know if it is the same

zapirkon said:
there is mbn file in the ffu
but I don't know if it is the same
Click to expand...
Click to collapse
you have extracted ffu using 7-Zip ? is that right ?

ngame said:
you have extracted ffu using 7-Zip ? is that right ?
Click to expand...
Click to collapse
either with thor2 or with imgmount
---------- Post added at 02:05 PM ---------- Previous post was at 01:44 PM ----------
from thor2 manual I see that it can flash the bin or mbn files
I tried that once, but later today I will try it again and post here
as for the mbn file i mentioned, I think it is too small to be the one.

still no luck... now looking at
http://forum.xda-developers.com/showthread.php?t=1705324

zapirkon said:
still no luck... now looking at
http://forum.xda-developers.com/showthread.php?t=1705324
Click to expand...
Click to collapse
this is for windows phone7 lumia devices... work on lumia X20 ?? wp8...
need the files partition.xml etc, to blink

johntheredimid said:
this is for windows phone7 lumia devices... work on lumia X20 ?? wp8...
need the files partition.xml etc, to blink
Click to expand...
Click to collapse
I can see that also, but the hope to find something is still present :fingers-crossed:

in the ffu there is MMOS.WIM file
inside it i found xml file with some partitioning info
Code:
<?xml version="1.0" encoding="utf-8"?>
<DeviceLayout xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
<Partitions>
<!-- READ-ONLY SECTION START -->
<!-- Device Provisioning Partition (FIRST READ-ONLY) -->
<Partition>
<Name>DPP</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<TotalSectors>16384</TotalSectors>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- QUALCOMM 8960 SPECIFIC READ-ONLY PARTITIONS -->
<!-- Modem golden file system - MUST FOLLOW DPP -->
<Partition>
<Name>MODEM_FSG</Name>
<TotalSectors>6144</TotalSectors>
<Type>{638FF8E2-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Secure Software Download -->
<Partition>
<Name>SSD</Name>
<TotalSectors>16</TotalSectors>
<Type>{2C86E742-745E-4FDD-BFD8-B6A7AC638772}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Bootloaders -->
<Partition>
<Name>SBL1</Name>
<TotalSectors>3000</TotalSectors>
<!-- Qualcomm defined for SBL1 -->
<Type>{DEA0BA2C-CBDD-4805-B4F9-F428251C3E98}</Type>
<Bootable>true</Bootable>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>SBL2</Name>
<TotalSectors>3000</TotalSectors>
<Type>{8C6B52AD-8A9E-4398-AD09-AE916E53AE2D}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>SBL3</Name>
<TotalSectors>4096</TotalSectors>
<Type>{05E044DF-92F1-4325-B69E-374A82E97D6E}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>UEFI</Name>
<TotalSectors>5000</TotalSectors>
<Type>{400FFDCD-22E0-47E7-9A23-F16ED9382388}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>RPM</Name>
<TotalSectors>1000</TotalSectors>
<Type>{098DF793-D712-413D-9D4E-89D711772228}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>TZ</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- fTPM Application -->
<Partition>
<Name>WINSECAPP</Name>
<TotalSectors>1024</TotalSectors>
<Type>{69B4201F-A5AD-45EB-9F49-45B38CCDAEF5}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- Bootloaders Backup Section (Sizes must match) -->
<Partition>
<Name>BACKUP_SBL1</Name>
<TotalSectors>3000</TotalSectors>
<!-- Qualcomm defined for SBL1 -->
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<Bootable>true</Bootable>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>BACKUP_SBL2</Name>
<TotalSectors>3000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>BACKUP_SBL3</Name>
<TotalSectors>4096</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>BACKUP_UEFI</Name>
<TotalSectors>5000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>BACKUP_RPM</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>BACKUP_TZ</Name>
<TotalSectors>1000</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- fTPM Application Backup Section (Sizes must match) -->
<Partition>
<Name>BACKUP_WINSECAPP</Name>
<TotalSectors>1024</TotalSectors>
<Type>{A3381699-350C-465E-BD5D-FA3AB901A39A}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- UEFI Variable Services Partitions - Read-Only -->
<Partition>
<Name>UEFI_BS_NV</Name>
<TotalSectors>512</TotalSectors>
<Type>{F0B4F48B-AEBA-4ECF-9142-5DC30CDC3E77}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>UEFI_NV</Name>
<TotalSectors>512</TotalSectors>
<Type>{74DA3EE7-D422-487C-A573-CE03C261362F}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- ACPI table storage -->
<Partition>
<Name>PLAT</Name>
<TotalSectors>16384</TotalSectors>
<FileSystem>FAT</FileSystem>
<Type>{543C031A-4CB6-4897-BFFE-4B485768A8AD}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- EFI System Partition (LAST READ-ONLY) -->
<Partition>
<Name>EFIESP</Name>
<FileSystem>FAT</FileSystem>
<TotalSectors>131072</TotalSectors>
<ByteAlignment>0x4000000</ByteAlignment>
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- READ-ONLY SECTION END -->
<!-- START QUALCOMM 8960 SPECIFIC READ-WRITE PARTITIONS -->
<!-- Modem live file systems -->
<Partition>
<Name>MODEM_FS1</Name>
<TotalSectors>6144</TotalSectors>
<Type>{EBBEADAF-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
<ByteAlignment>0x4000000</ByteAlignment>
</Partition>
<Partition>
<Name>MODEM_FS2</Name>
<TotalSectors>6144</TotalSectors>
<Type>{0A288B1F-22C9-E33B-8F5D-0E81686A68CB}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- UEFI Variable Services Partitions - Read-Write -->
<Partition>
<Name>UEFI_RT_NV</Name>
<TotalSectors>512</TotalSectors>
<Type>{6BB94537-7D1C-44D0-9DFE-6D77C011DBFC}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<Partition>
<Name>UEFI_RT_NV_RPMB</Name>
<TotalSectors>256</TotalSectors>
<Type>{E35F99CF-0025-4252-A608-CAAA1289CAF4}</Type>
<RequiredToFlash>true</RequiredToFlash>
</Partition>
<!-- END QUALCOMM 8960 SPECIFIC READ-WRITE PARTITIONS -->
<!-- START MICROSOFT READ-WRITE PARTITIONS -->
<Partition>
<Name>MMOS</Name>
<FileSystem>FAT</FileSystem>
<MinFreeSectors>8192</MinFreeSectors>
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
</Partition>
<Partition>
<Name>MainOS</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<!-- Accounts for 400MB free sectors and 256MB page file as defined in registry by package src\baseos\prod\packages\arm\armmemory -->
<MinFreeSectors>1343488</MinFreeSectors>
<ByteAlignment>0x800000</ByteAlignment>
<ClusterSize>0x4000</ClusterSize>
<FileSystem>NTFS</FileSystem>
<AttachDriveLetter>false</AttachDriveLetter>
</Partition>
<Partition>
<Name>Data</Name>
<!-- PARTITION_BASIC_DATA_GUID -->
<Type>{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}</Type>
<UseAllSpace>true</UseAllSpace>
<ByteAlignment>0x800000</ByteAlignment>
<ClusterSize>0x4000</ClusterSize>
<FileSystem>NTFS</FileSystem>
</Partition>
</Partitions>
<!-- END MICROSOFT READ-WRITE PARTITIONS -->
<SectorSize>512</SectorSize>
<ChunkSize>128</ChunkSize>
<DefaultPartitionByteAlignment>0x200000</DefaultPartitionByteAlignment>
</DeviceLayout>
also, i found
qcadsp8930.mbn
qcdsp1v18930.mbn
qcdsp1v28930.mbn
qcdsp28930.mbn
qcwcnss8930.mbn
but, I notice that when thor2 is started in emergency mode, and I provide any mbn file, the error is
Code:
QUATTRO EMERGENCY FLASH START
Quattro Emergency Programmer version 2014.11.25.001
ED download selected
Failed to load XML configuration file
Quattro emergency flash exited with error code 85000
QUATTRO EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 6.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_XML_PARSING_FAILED
THOR2 1.8.2.15 exited with error code 85000 (0x14C08)
also from the WMI file I see buld info:
Code:
collins_engine_8227/PRx_engine_integration
which indicates to me that emergency programming should be done with
Code:
-protocol streaming
but I always get error THOR2_ERROR_NO_SAHARA_HANDSHAKE
how to change the emergency protocol?

Read This
http://answers.microsoft.com/en-us/...-windows/c5d072d5-c26e-4a02-907d-fde2ca5e34c7

did you read it?
Please do try to recover and share your results.
Click to expand...
Click to collapse
---------- Post added at 12:00 PM ---------- Previous post was at 11:43 AM ----------
comparing
8960_msimage.mbn
to
GPT.bin
(extracted with thor2 -mode ffureader -ffufile "...ffu" -dump_partitions -filedir c:\temp)
they seem similar in contents
is this the mbn file? I still can't find hex file

Nokia uses own Sahara implementation, called "FireHose" , which will NOT work with QPST. And not open mass storage mode. And MSM image is also not usable for repair. Funny, isn't it?

WojtasXda said:
Nokia uses own Sahara implementation, called "FireHose" , which will NOT work with QPST. And not open mass storage mode. And MSM image is also not usable for repair. Funny, isn't it?
Click to expand...
Click to collapse
and is that mean we can run MStorage mode on samsung and HTC ?

ngame said:
and is that mean we can run MStorage mode on samsung and HTC ?
Click to expand...
Click to collapse
UEFI loader can run phone in MassStorage mode, engineering ROMs have unlocked this option

WojtasXda said:
Nokia uses own Sahara implementation, called "FireHose" , which will NOT work with QPST. And not open mass storage mode. And MSM image is also not usable for repair. Funny, isn't it?
Click to expand...
Click to collapse
And why the application makes mention thor2 files used in QPST?
------------------------------------------------------------------------
PD: I updated the theard to current information, thanks.

I don't know if it's me, but the fact that the phone seems to be in download mode indicates that we should be able to flash any kind of thing on it, surpassing the signature checks. Am I right?

whoadood said:
I don't know if it's me, but the fact that the phone seems to be in download mode indicates that we should be able to flash any kind of thing on it, surpassing the signature checks. Am I right?
Click to expand...
Click to collapse
if your phone is locked on the red screen yes it's download mode .
but if you mean you can bypass sign check in this mode ? I think no.
It's nothing else than one NOKIA Care Suite loads .
If you try to flash your phone using NCS you see this screen but it starts flashing phone in a little while .

ngame said:
if your phone is locked on the red screen yes it's download mode .
but if you mean you can bypass sign check in this mode ? I think no.
It's nothing else than one NOKIA Care Suite loads .
If you try to flash your phone using NCS you see this screen but it starts flashing phone in a little while .
Click to expand...
Click to collapse
No. I mean the black screen. It looks like it's some Qualcomm's (very low level) flashing mode. I would say it will swallow everything you feed it.

whoadood said:
No. I mean the black screen. It looks like it's some Qualcomm's (very low level) flashing mode. I would say it will swallow everything you feed it.
Click to expand...
Click to collapse
Everything you need is a Qualcomm MSM device ?
OK lets hold vol up key and turn your phone on and don't release vol up while you see a gear + a thunder .

ngame said:
Everything you need is a Qualcomm MSM device ?
OK lets hold vol up key and turn your phone on and don't release vol up while you see a gear + a thunder .
Click to expand...
Click to collapse
I'm telling you the phone is completely and absolutely dead. All I see is a QHSUSB_DLOAD device when I plug it into a computer. But the screen never shows anything.

whoadood said:
I'm telling you the phone is completely and absolutely dead. All I see is a QHSUSB_DLOAD device when I plug it into a computer. But the screen never shows anything.
Click to expand...
Click to collapse
ah I really forget it , sorry .
QHSUSB_DLOAD is different . I don't know about that .

[H815EU _ONLY_] Relock BL cust/misc/persistent.img preemptive dump

---
DISCLAIMER: Everything mentioned in this thread is not for personal use and will destroy your device.
{
"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"
}
---
I know (seriously) I should wait for xVANKO to finish his guide but, I really want to unlock the bootloader and/but before I do that even more so take the precautions to be able to relock it again (ILAPO, warranty, you know the deal).
Back in the days I used http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586 and http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 to root, so I am familiar with "dd" etc.
The following information is collected from across these forums, therefore I neither take any credit nor any responsibility!
Trying to execute those commands on my H815EU (DO NOT TRY THIS AT HOME, especially with anything other than H815EU. It will destroy your device and your house will catch on fire!)
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=585216 count=32768 of=/data/media/0/cust.img
dd if=/dev/block/mmcblk0 bs=8192 skip=16384 count=2048 of=/data/media/0/misc.img
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
In addition to that - to my understanding these then would be the commands to flash the dumped data back to the unlocked device?
(You have been warned!)
Code:
dd if=/data/media/0/cust.img bs=8192 seek=585216 count=32768 of=/dev/block/mmcblk0
dd if=/data/media/0/misc.img bs=8192 seek=16384 count=2048 of=/dev/block/mmcblk0
dd if=/data/media/0/persistent.img bs=8192 seek=23808 count=256 of=/dev/block/mmcblk0
Anyhow,
TLDR; and this is basically the problem here - it simply sais "FAIL".
Is this because of Marshmallow? Do I have to downgrade to Lollipop first?
I am able to use Send_Command.exe and I have set the right COM port, proper drivers installed (autoprime), connected via USB 2.0 on Win10x64.
THANKS SO MUCH FOR YOUR HELP, IT REALLY IS MUCH APPRECIATED!
PS: Obviously I would ask this in the dedicated thread, but it is locked atm. Sorry for the inconvenience!
Honorable mention aka 'Credits' not including any responsibility for aforementioned potential damages!
xVANKO (for: http://forum.xda-developers.com/g4/general/h815-relock-bootloader-t3506634)
^ btw, please please continue your awesome work for this community! <3

Mislick, my bad.. If a kind moderator would please move this to http://forum.xda-developers.com/g4/help, thanks!

blake_spector said:
---
DISCLAIMER: Everything mentioned in this thread is not for personal use and will destroy your device.
---
I know (seriously) I should wait for xVANKO to finish his guide but, I really want to unlock the bootloader and/but before I do that even more so take the precautions to be able to relock it again (ILAPO, warranty, you know the deal).
Back in the days I used http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586 and http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 to root, so I am familiar with "dd" etc.
The following information is collected from across these forums, therefore I neither take any credit nor any responsibility!
Trying to execute those commands on my H815EU (DO NOT TRY THIS AT HOME, especially with anything other than H815EU. It will destroy your device and your house will catch on fire!)
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=585216 count=32768 of=/data/media/0/cust.img
dd if=/dev/block/mmcblk0 bs=8192 skip=16384 count=2048 of=/data/media/0/misc.img
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
In addition to that - to my understanding these then would be the commands to flash the dumped data back to the unlocked device?
(You have been warned!)
Code:
dd if=/data/media/0/cust.img bs=8192 seek=585216 count=32768 of=/dev/block/mmcblk0
dd if=/data/media/0/misc.img bs=8192 seek=16384 count=2048 of=/dev/block/mmcblk0
dd if=/data/media/0/persistent.img bs=8192 seek=23808 count=256 of=/dev/block/mmcblk0
Anyhow,
TLDR; and this is basically the problem here - it simply sais "FAIL".
Is this because of Marshmallow? Do I have to downgrade to Lollipop first?
I am able to use Send_Command.exe and I have set the right COM port, proper drivers installed (autoprime), connected via USB 2.0 on Win10x64.
THANKS SO MUCH FOR YOUR HELP, IT REALLY IS MUCH APPRECIATED!
PS: Obviously I would ask this in the dedicated thread, but it is locked atm. Sorry for the inconvenience!
Honorable mention aka 'Credits' not including any responsibility for aforementioned potential damages!
xVANKO (for: http://forum.xda-developers.com/g4/general/h815-relock-bootloader-t3506634)
^ btw, please please continue your awesome work for this community! <3
Click to expand...
Click to collapse
If you wanna use Send_Command.exe with MM, please visit this thread and examine Method 2. :fingers-crossed:

jskasia said:
If you wanna use Send_Command.exe with MM, please visit this thread and examine Method 2. :fingers-crossed:
Click to expand...
Click to collapse
Ah, I see! Thanks.
Seems a bit troublesome, I guess I'll just flash a Lollipop KDZ for the Send_Command.exe tasks.
Then unlock, TWRP, Root, and "back" to MM . . . :angel:
. . . and eventually, flash Lollipop KDZ again, and "relock" Bootloader for warranty round#2.

blake_spector said:
Ah, I see! Thanks.
Seems a bit troublesome, I guess I'll just flash a Lollipop KDZ for the Send_Command.exe tasks.
Then unlock, TWRP, Root, and "back" to MM . . . :angel:
. . . and eventually, flash Lollipop KDZ again, and "relock" Bootloader for warranty round#2.
Click to expand...
Click to collapse
No, it is really simple. After few times you can do this with eyes closed(ok only one eye ). It's the Marshmallow's bootloader "security".
So after all it's as simple as dumping few partitions to SD and uploading them back again? No HEX editing or other stuff?
Or is it dumping before bootloader unlock and to relock just flash them back?

You don't have to downgrade to be able to use the send_command.exe
There is only an extra trick: you have to use LGUP to enable the com port in download mode.
Here is how to do it:
- Backup your data first
- launch LGUP, select a kdz (preferably the one you currently have),
- Make sure you select upgrade, not refurbish. I missed it once, it will do a factory reset right away!
- start flashing.
- Your device will go in download mode. Few seconds later (around 5% I believe), it will display a com port.
- As soon as you see the COM port displayed on the G4 screen, unplug the usb cable.
- Close LGUP
- Replug the usb cable, send_commands is now working.
If you still want to go ahead before having xVANKO information, I would suggest to also dump the drm partition. And if you want to be extra cautious, dump the whole mmc until userdata. It's a bit big, around 5 GB, but it would allow to extract any other partition if needed.

How do you find out you got a H815EU model?
I'm based in germany and bought a local one. The package simply says LG-H815 as well as the hardware informations inside the settings menu.
Edit: I know there are different types out there, but haven't read about a 'H815EU' model. Do you mean a european device or the unique 'H815EU' type?
Edit 2: Running the commands to backup the partitions shouldn't brick your device. The 'dd' command only reads bytes between skip and count. Executing without those parameter would simply clone your flash drive. Since it seems that there are different partition sizes per model, it could only happen that you read invalid data from the storage. Flashing those backups are the main reason for hard-bricks.

dnkncht said:
How do you find out you got a H815EU model?
I'm based in germany and bought a local one. The package simply says LG-H815 as well as the hardware informations inside the settings menu.
Edit: I know there are different types out there, but haven't read about a 'H815EU' model. Do you mean a european device or the unique 'H815EU' type?
Edit 2: Running the commands to backup the partitions shouldn't brick your device. The 'dd' command only reads bytes between skip and count. Executing without those parameter would simply clone your flash drive. Since it seems that there are different partition sizes per model, it could only happen that you read invalid data from the storage. Flashing those backups are the main reason for hard-bricks.
Click to expand...
Click to collapse
H815EU or H815 EUR is another name for unkockable H815 variant(keep in mind that not every H815 variant can be unlocked, that's why we call it like that). To determine if you have H815EU just download LG phone info check provider. There should be 3 letter long text. There is a list of unkockable H815s so check your letters and find yours on the list. Fortunately, my G4 is H815EU/H815 EUR
Wysłane z mojego LG-H815 przy użyciu Tapatalka

letama said:
- Backup your data first
- launch LGUP, select a kdz (preferably the one you currently have),
- Make sure you select upgrade, not refurbish. I missed it once, it will do a factory reset right away!
- start flashing.
- Your device will go in download mode. Few seconds later (around 5% I believe), it will display a com port.
- As soon as you see the COM port displayed on the G4 screen, unplug the usb cable.
- Close LGUP
- Replug the usb cable, send_commands is now working.
If you still want to go ahead before having xVANKO information, I would suggest to also dump the drm partition. And if you want to be extra cautious, dump the whole mmc until userdata. It's a bit big, around 5 GB, but it would allow to extract any other partition if needed.
Click to expand...
Click to collapse
Thanks a lot for the clear instructions!
In regard to dumping drm partition, or whole mmc . . . I found this, but I don't know how those values translate to the "skip" and "count" parts of the dd command. Do you know the appropriate values?
dnkncht said:
I'm based in germany and bought a local one. The package simply says LG-H815 [ . . . ]
Edit 2: Running the commands to backup the partitions shouldn't brick your device. The 'dd' command only reads bytes between skip and count. Executing without those parameter would simply clone your flash drive. Since it seems that there are different partition sizes per model, it could only happen that you read invalid data from the storage. Flashing those backups are the main reason for hard-bricks.
Click to expand...
Click to collapse
A german H815 does apply to the shenanigans discussed here. My device is the same.
To 'edit 2', you're right! The "reading" part isn't the problem . . . still, better safe than sorry.

blake_spector said:
Thanks a lot for the clear instructions!
In regard to dumping drm partition, or whole mmc . . . I found this, but I don't know how those values translate to the "skip" and "count" parts of the dd command. Do you know the appropriate values?
skip declares the start point, where dd should start to read. count names the amount ob bytes to read.
For example take a look at the cust partition:
48 4794089472B 5062524927B 268435456B ext4 cust
The command would be:
dd if=/dev/block/mmcblk0 bs=8192 skip=585216 count=32768 of=/data/media/0/cust.img
bs equals the block size -> 8192
skip equals = 4794089472 / 8192 -> 585216
count equals = 268435456 / 8192 -> 32768
Now you can calculate your values yourself
Click to expand...
Click to collapse

dnkncht said:
skip declares the start point, where dd should start to read. count names the amount ob bytes to read.
For example take a look at the cust partition:
48 4794089472B 5062524927B 268435456B ext4 cust
The command would be:
dd if=/dev/block/mmcblk0 bs=8192 skip=585216 count=32768 of=/data/media/0/cust.img
bs equals the block size -> 8192
skip equals = 4794089472 / 8192 -> 585216
count equals = 268435456 / 8192 -> 32768
Now you can calculate your values yourself
Click to expand...
Click to collapse
Marvellous piece of information, vielen vielen Dank!

blake_spector said:
Thanks a lot for the clear instructions!
In regard to dumping drm partition, or whole mmc . . . I found this, but I don't know how those values translate to the "skip" and "count" parts of the dd command. Do you know the appropriate values?
Click to expand...
Click to collapse
You're welcome.
To get the exact offsets for dd commands, I took a dump of the gpt partition table and then used a tool that gave me this (FRA/EUR model):
Code:
[+] Primary GPT header
[-] Signature: b'EFI PART'
[-] Revision: 65536
[-] Header Size: 92
[-] CRC32 of header: F1E68634 (VALID) => Real: F1E68634
[-] Current LBA: 0x00000001
[-] Backup LBA: 0x03A3DFFF
[-] First usable LBA for partitions: 0x00000022
[-] Last usable LBA for partitions: 0x03A3DFDE
[-] Disk GUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
[-] Partition entries starting LBA: 0x00000002
[-] Number of partition entries: 52
[-] Size of partition entry: 0x00000080
[-] CRC32 of partition array: 0x7330FD5F
[+] Primary GPT header md5: a22b35048e8f33a3df50a3bf2cc6c1b2
[+] Partition table
[-] WARNING!! CRC32 Check : E177F4F2 (INVALID)
[-] Partition 1
[-] First LBA: 32768
[-] Last LBA: 208895
=> First Offset: 0x01000000
=> Last Offset: 0x065FFE00
[-] Partition Name: modem
[-] Partition 2
[-] First LBA: 229376
[-] Last LBA: 230399
=> First Offset: 0x07000000
=> Last Offset: 0x0707FE00
[-] Partition Name: pmic
[-] Partition 3
[-] First LBA: 230400
[-] Last LBA: 232447
=> First Offset: 0x07080000
=> Last Offset: 0x0717FE00
[-] Partition Name: sbl1
[-] Partition 4
[-] First LBA: 232448
[-] Last LBA: 234495
=> First Offset: 0x07180000
=> Last Offset: 0x0727FE00
[-] Partition Name: tz
[-] Partition 5
[-] First LBA: 234496
[-] Last LBA: 235519
=> First Offset: 0x07280000
=> Last Offset: 0x072FFE00
[-] Partition Name: sdi
[-] Partition 6
[-] First LBA: 235520
[-] Last LBA: 236543
=> First Offset: 0x07300000
=> Last Offset: 0x0737FE00
[-] Partition Name: hyp
[-] Partition 7
[-] First LBA: 236544
[-] Last LBA: 237567
=> First Offset: 0x07380000
=> Last Offset: 0x073FFE00
[-] Partition Name: rpm
[-] Partition 8
[-] First LBA: 237568
[-] Last LBA: 241663
=> First Offset: 0x07400000
=> Last Offset: 0x075FFE00
[-] Partition Name: aboot
[-] Partition 9
[-] First LBA: 241664
[-] Last LBA: 243711
=> First Offset: 0x07600000
=> Last Offset: 0x076FFE00
[-] Partition Name: sbl1bak
[-] Partition 10
[-] First LBA: 243712
[-] Last LBA: 244735
=> First Offset: 0x07700000
=> Last Offset: 0x0777FE00
[-] Partition Name: pmicbak
[-] Partition 11
[-] First LBA: 244736
[-] Last LBA: 246783
=> First Offset: 0x07780000
=> Last Offset: 0x0787FE00
[-] Partition Name: tzbak
[-] Partition 12
[-] First LBA: 246784
[-] Last LBA: 247807
=> First Offset: 0x07880000
=> Last Offset: 0x078FFE00
[-] Partition Name: hypbak
[-] Partition 13
[-] First LBA: 247808
[-] Last LBA: 248831
=> First Offset: 0x07900000
=> Last Offset: 0x0797FE00
[-] Partition Name: rpmbak
[-] Partition 14
[-] First LBA: 248832
[-] Last LBA: 252927
=> First Offset: 0x07980000
=> Last Offset: 0x07B7FE00
[-] Partition Name: abootbak
[-] Partition 15
[-] First LBA: 252928
[-] Last LBA: 253951
=> First Offset: 0x07B80000
=> Last Offset: 0x07BFFE00
[-] Partition Name: sdibak
[-] Partition 16
[-] First LBA: 253952
[-] Last LBA: 254975
=> First Offset: 0x07C00000
=> Last Offset: 0x07C7FE00
[-] Partition Name: limits
[-] Partition 17
[-] First LBA: 254976
[-] Last LBA: 255999
=> First Offset: 0x07C80000
=> Last Offset: 0x07CFFE00
[-] Partition Name: devinfo
[-] Partition 18
[-] First LBA: 256000
[-] Last LBA: 257023
=> First Offset: 0x07D00000
=> Last Offset: 0x07D7FE00
[-] Partition Name: apdp
[-] Partition 19
[-] First LBA: 257024
[-] Last LBA: 258047
=> First Offset: 0x07D80000
=> Last Offset: 0x07DFFE00
[-] Partition Name: msadp
[-] Partition 20
[-] First LBA: 258048
[-] Last LBA: 259071
=> First Offset: 0x07E00000
=> Last Offset: 0x07E7FE00
[-] Partition Name: dpo
[-] Partition 21
[-] First LBA: 259072
[-] Last LBA: 262143
=> First Offset: 0x07E80000
=> Last Offset: 0x07FFFE00
[-] Partition Name: spare1
[-] Partition 22
[-] First LBA: 262144
[-] Last LBA: 294911
=> First Offset: 0x08000000
=> Last Offset: 0x08FFFE00
[-] Partition Name: misc
[-] Partition 23
[-] First LBA: 294912
[-] Last LBA: 360447
=> First Offset: 0x09000000
=> Last Offset: 0x0AFFFE00
[-] Partition Name: persist
[-] Partition 24
[-] First LBA: 360448
[-] Last LBA: 363519
=> First Offset: 0x0B000000
=> Last Offset: 0x0B17FE00
[-] Partition Name: modemst1
[-] Partition 25
[-] First LBA: 363520
[-] Last LBA: 366591
=> First Offset: 0x0B180000
=> Last Offset: 0x0B2FFE00
[-] Partition Name: modemst2
[-] Partition 26
[-] First LBA: 366592
[-] Last LBA: 369663
=> First Offset: 0x0B300000
=> Last Offset: 0x0B47FE00
[-] Partition Name: fsg
[-] Partition 27
[-] First LBA: 369664
[-] Last LBA: 370687
=> First Offset: 0x0B480000
=> Last Offset: 0x0B4FFE00
[-] Partition Name: fsc
[-] Partition 28
[-] First LBA: 370688
[-] Last LBA: 371711
=> First Offset: 0x0B500000
=> Last Offset: 0x0B57FE00
[-] Partition Name: ssd
[-] Partition 29
[-] First LBA: 371712
[-] Last LBA: 372735
=> First Offset: 0x0B580000
=> Last Offset: 0x0B5FFE00
[-] Partition Name: keystore
[-] Partition 30
[-] First LBA: 372736
[-] Last LBA: 376831
=> First Offset: 0x0B600000
=> Last Offset: 0x0B7FFE00
[-] Partition Name: DDR
[-] Partition 31
[-] First LBA: 376832
[-] Last LBA: 377855
=> First Offset: 0x0B800000
=> Last Offset: 0x0B87FE00
[-] Partition Name: sec
[-] Partition 32
[-] First LBA: 377856
[-] Last LBA: 378879
=> First Offset: 0x0B880000
=> Last Offset: 0x0B8FFE00
[-] Partition Name: encrypt
[-] Partition 33
[-] First LBA: 378880
[-] Last LBA: 379903
=> First Offset: 0x0B900000
=> Last Offset: 0x0B97FE00
[-] Partition Name: eksst
[-] Partition 34
[-] First LBA: 379904
[-] Last LBA: 380927
=> First Offset: 0x0B980000
=> Last Offset: 0x0B9FFE00
[-] Partition Name: rct
[-] Partition 35
[-] First LBA: 380928
[-] Last LBA: 385023
=> First Offset: 0x0BA00000
=> Last Offset: 0x0BBFFE00
[-] Partition Name: persistent
[-] Partition 36
[-] First LBA: 385024
[-] Last LBA: 393215
=> First Offset: 0x0BC00000
=> Last Offset: 0x0BFFFE00
[-] Partition Name: spare2
[-] Partition 37
[-] First LBA: 393216
[-] Last LBA: 491519
=> First Offset: 0x0C000000
=> Last Offset: 0x0EFFFE00
[-] Partition Name: laf
[-] Partition 38
[-] First LBA: 491520
[-] Last LBA: 573439
=> First Offset: 0x0F000000
=> Last Offset: 0x117FFE00
[-] Partition Name: boot
[-] Partition 39
[-] First LBA: 573440
[-] Last LBA: 655359
=> First Offset: 0x11800000
=> Last Offset: 0x13FFFE00
[-] Partition Name: recovery
[-] Partition 40
[-] First LBA: [B]655360[/B]
[-] Last LBA: [B]671743[/B]
=> First Offset: 0x14000000
=> Last Offset: 0x147FFE00
[-] Partition Name: drm
[-] Partition 41
[-] First LBA: 671744
[-] Last LBA: 688127
=> First Offset: 0x14800000
=> Last Offset: 0x14FFFE00
[-] Partition Name: sns
[-] Partition 42
[-] First LBA: 688128
[-] Last LBA: 753663
=> First Offset: 0x15000000
=> Last Offset: 0x16FFFE00
[-] Partition Name: mpt
[-] Partition 43
[-] First LBA: 753664
[-] Last LBA: 847871
=> First Offset: 0x17000000
=> Last Offset: 0x19DFFE00
[-] Partition Name: factory
[-] Partition 44
[-] First LBA: 847872
[-] Last LBA: 868351
=> First Offset: 0x19E00000
=> Last Offset: 0x1A7FFE00
[-] Partition Name: fota
[-] Partition 45
[-] First LBA: 868352
[-] Last LBA: 876543
=> First Offset: 0x1A800000
=> Last Offset: 0x1ABFFE00
[-] Partition Name: raw_resources
[-] Partition 46
[-] First LBA: 876544
[-] Last LBA: 884735
=> First Offset: 0x1AC00000
=> Last Offset: 0x1AFFFE00
[-] Partition Name: raw_resourcesbak
[-] Partition 47
[-] First LBA: 884736
[-] Last LBA: 9363455
=> First Offset: 0x1B000000
=> Last Offset: 0x11DBFFE00
[-] Partition Name: system
[-] Partition 48
[-] First LBA: 9363456
[-] Last LBA: 9887743
=> First Offset: 0x11DC00000
=> Last Offset: 0x12DBFFE00
[-] Partition Name: cust
[-] Partition 49
[-] First LBA: 9895936
[-] Last LBA: 12419071
=> First Offset: 0x12E000000
=> Last Offset: 0x17AFFFE00
[-] Partition Name: cache
[-] Partition 50
[-] First LBA: 12419072
[-] Last LBA: 61046783
=> First Offset: 0x17B000000
=> Last Offset: 0x746FFFE00
[-] Partition Name: userdata
[-] Partition 51
[-] First LBA: 61046784
[-] Last LBA: 61071326
=> First Offset: 0x747000000
=> Last Offset: 0x747BFBC00
[-] Partition Name: grow
[+] Partition table md5: ea0c8acec7957b09de3d317ab378824a
LBA is the index ofa 512 bytes block, so for instance to dump drm partition, dd looks like this:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/drm.img bs=[COLOR="Red"][B]512[/B][/COLOR] skip=[COLOR="Red"][B]655360[/B][/COLOR] count=[COLOR="red"][B]16384[/B][/COLOR]
skip value is exactly First LBA in table (=> 655360),
count value is (Last LBA - first LBA +1) (=> 671743 - 655360 +1 => 16384)
You can also retrieve the indexes and size in download mode if you know what partition number is the one you're looking for.
To find partition number do:
Code:
ls -l /dev/block/bootdevice/by-name
It will give you this:
Code:
lrwxrwxrwx root root 2015-01-15 01:12 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-15 01:12 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-15 01:12 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-15 01:12 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-15 01:12 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-15 01:12 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-15 01:12 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-15 01:12 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-15 01:12 dpo -> /dev/block/mmcblk0p20
[B]lrwxrwxrwx root root 2015-01-15 01:12 drm -> /dev/block/mmcblk0p40[/B]
lrwxrwxrwx root root 2015-01-15 01:12 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-15 01:12 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-15 01:12 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-15 01:12 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-15 01:12 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-15 01:12 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-15 01:12 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-15 01:12 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-15 01:12 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-15 01:12 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-15 01:12 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-15 01:12 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-15 01:12 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-15 01:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-15 01:12 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-15 01:12 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-15 01:12 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-15 01:12 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-15 01:12 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-15 01:12 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-15 01:12 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-15 01:12 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-15 01:12 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-15 01:12 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-15 01:12 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-15 01:12 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-15 01:12 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-15 01:12 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-15 01:12 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-15 01:12 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-15 01:12 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-15 01:12 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-15 01:12 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-15 01:12 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-15 01:12 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-15 01:12 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-15 01:12 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-15 01:12 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-15 01:12 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-15 01:12 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-15 01:12 userdata -> /dev/block/mmcblk0p50
So, in our case, drm is partition 40, commands to retrieve index and size are:
Code:
cat /sys/devices/soc.0/f9824900.sdhci/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p[COLOR="Red"]40[/COLOR]/start
cat /sys/devices/soc.0/f9824900.sdhci/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p[COLOR="red"]40[/COLOR]/size
giving you 655360 and 16384 directly.
Last, to dump full MMC until userdata, I just did dd until userdata LBA:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/full_dump.img bs=512 count=12419072
It's, a big file, around 6 GB. If you want to speed up things a bit, read with a block size of 4096 and divide by 8 the count:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/full_dump.img bs=4096 count=1552384
I didn't test relocking yet though, not enough free time. Hope it helps, don't hesitate to ask if you need more details.

blake_spector
Read private message?

letama said:
You're welcome.
To get the exact offsets for dd commands, I took a dump of the gpt partition table and then used a tool that gave me this (FRA/EUR model):
Code:
[+] Primary GPT header
[-] Signature: b'EFI PART'
[-] Revision: 65536
[-] Header Size: 92
[-] CRC32 of header: F1E68634 (VALID) => Real: F1E68634
[-] Current LBA: 0x00000001
[-] Backup LBA: 0x03A3DFFF
[-] First usable LBA for partitions: 0x00000022
[-] Last usable LBA for partitions: 0x03A3DFDE
[-] Disk GUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
[-] Partition entries starting LBA: 0x00000002
[-] Number of partition entries: 52
[-] Size of partition entry: 0x00000080
[-] CRC32 of partition array: 0x7330FD5F
[+] Primary GPT header md5: a22b35048e8f33a3df50a3bf2cc6c1b2
[+] Partition table
[-] WARNING!! CRC32 Check : E177F4F2 (INVALID)
[-] Partition 1
[-] First LBA: 32768
[-] Last LBA: 208895
=> First Offset: 0x01000000
=> Last Offset: 0x065FFE00
[-] Partition Name: modem
[-] Partition 2
[-] First LBA: 229376
[-] Last LBA: 230399
=> First Offset: 0x07000000
=> Last Offset: 0x0707FE00
[-] Partition Name: pmic
[-] Partition 3
[-] First LBA: 230400
[-] Last LBA: 232447
=> First Offset: 0x07080000
=> Last Offset: 0x0717FE00
[-] Partition Name: sbl1
[-] Partition 4
[-] First LBA: 232448
[-] Last LBA: 234495
=> First Offset: 0x07180000
=> Last Offset: 0x0727FE00
[-] Partition Name: tz
[-] Partition 5
[-] First LBA: 234496
[-] Last LBA: 235519
=> First Offset: 0x07280000
=> Last Offset: 0x072FFE00
[-] Partition Name: sdi
[-] Partition 6
[-] First LBA: 235520
[-] Last LBA: 236543
=> First Offset: 0x07300000
=> Last Offset: 0x0737FE00
[-] Partition Name: hyp
[-] Partition 7
[-] First LBA: 236544
[-] Last LBA: 237567
=> First Offset: 0x07380000
=> Last Offset: 0x073FFE00
[-] Partition Name: rpm
[-] Partition 8
[-] First LBA: 237568
[-] Last LBA: 241663
=> First Offset: 0x07400000
=> Last Offset: 0x075FFE00
[-] Partition Name: aboot
[-] Partition 9
[-] First LBA: 241664
[-] Last LBA: 243711
=> First Offset: 0x07600000
=> Last Offset: 0x076FFE00
[-] Partition Name: sbl1bak
[-] Partition 10
[-] First LBA: 243712
[-] Last LBA: 244735
=> First Offset: 0x07700000
=> Last Offset: 0x0777FE00
[-] Partition Name: pmicbak
[-] Partition 11
[-] First LBA: 244736
[-] Last LBA: 246783
=> First Offset: 0x07780000
=> Last Offset: 0x0787FE00
[-] Partition Name: tzbak
[-] Partition 12
[-] First LBA: 246784
[-] Last LBA: 247807
=> First Offset: 0x07880000
=> Last Offset: 0x078FFE00
[-] Partition Name: hypbak
[-] Partition 13
[-] First LBA: 247808
[-] Last LBA: 248831
=> First Offset: 0x07900000
=> Last Offset: 0x0797FE00
[-] Partition Name: rpmbak
[-] Partition 14
[-] First LBA: 248832
[-] Last LBA: 252927
=> First Offset: 0x07980000
=> Last Offset: 0x07B7FE00
[-] Partition Name: abootbak
[-] Partition 15
[-] First LBA: 252928
[-] Last LBA: 253951
=> First Offset: 0x07B80000
=> Last Offset: 0x07BFFE00
[-] Partition Name: sdibak
[-] Partition 16
[-] First LBA: 253952
[-] Last LBA: 254975
=> First Offset: 0x07C00000
=> Last Offset: 0x07C7FE00
[-] Partition Name: limits
[-] Partition 17
[-] First LBA: 254976
[-] Last LBA: 255999
=> First Offset: 0x07C80000
=> Last Offset: 0x07CFFE00
[-] Partition Name: devinfo
[-] Partition 18
[-] First LBA: 256000
[-] Last LBA: 257023
=> First Offset: 0x07D00000
=> Last Offset: 0x07D7FE00
[-] Partition Name: apdp
[-] Partition 19
[-] First LBA: 257024
[-] Last LBA: 258047
=> First Offset: 0x07D80000
=> Last Offset: 0x07DFFE00
[-] Partition Name: msadp
[-] Partition 20
[-] First LBA: 258048
[-] Last LBA: 259071
=> First Offset: 0x07E00000
=> Last Offset: 0x07E7FE00
[-] Partition Name: dpo
[-] Partition 21
[-] First LBA: 259072
[-] Last LBA: 262143
=> First Offset: 0x07E80000
=> Last Offset: 0x07FFFE00
[-] Partition Name: spare1
[-] Partition 22
[-] First LBA: 262144
[-] Last LBA: 294911
=> First Offset: 0x08000000
=> Last Offset: 0x08FFFE00
[-] Partition Name: misc
[-] Partition 23
[-] First LBA: 294912
[-] Last LBA: 360447
=> First Offset: 0x09000000
=> Last Offset: 0x0AFFFE00
[-] Partition Name: persist
[-] Partition 24
[-] First LBA: 360448
[-] Last LBA: 363519
=> First Offset: 0x0B000000
=> Last Offset: 0x0B17FE00
[-] Partition Name: modemst1
[-] Partition 25
[-] First LBA: 363520
[-] Last LBA: 366591
=> First Offset: 0x0B180000
=> Last Offset: 0x0B2FFE00
[-] Partition Name: modemst2
[-] Partition 26
[-] First LBA: 366592
[-] Last LBA: 369663
=> First Offset: 0x0B300000
=> Last Offset: 0x0B47FE00
[-] Partition Name: fsg
[-] Partition 27
[-] First LBA: 369664
[-] Last LBA: 370687
=> First Offset: 0x0B480000
=> Last Offset: 0x0B4FFE00
[-] Partition Name: fsc
[-] Partition 28
[-] First LBA: 370688
[-] Last LBA: 371711
=> First Offset: 0x0B500000
=> Last Offset: 0x0B57FE00
[-] Partition Name: ssd
[-] Partition 29
[-] First LBA: 371712
[-] Last LBA: 372735
=> First Offset: 0x0B580000
=> Last Offset: 0x0B5FFE00
[-] Partition Name: keystore
[-] Partition 30
[-] First LBA: 372736
[-] Last LBA: 376831
=> First Offset: 0x0B600000
=> Last Offset: 0x0B7FFE00
[-] Partition Name: DDR
[-] Partition 31
[-] First LBA: 376832
[-] Last LBA: 377855
=> First Offset: 0x0B800000
=> Last Offset: 0x0B87FE00
[-] Partition Name: sec
[-] Partition 32
[-] First LBA: 377856
[-] Last LBA: 378879
=> First Offset: 0x0B880000
=> Last Offset: 0x0B8FFE00
[-] Partition Name: encrypt
[-] Partition 33
[-] First LBA: 378880
[-] Last LBA: 379903
=> First Offset: 0x0B900000
=> Last Offset: 0x0B97FE00
[-] Partition Name: eksst
[-] Partition 34
[-] First LBA: 379904
[-] Last LBA: 380927
=> First Offset: 0x0B980000
=> Last Offset: 0x0B9FFE00
[-] Partition Name: rct
[-] Partition 35
[-] First LBA: 380928
[-] Last LBA: 385023
=> First Offset: 0x0BA00000
=> Last Offset: 0x0BBFFE00
[-] Partition Name: persistent
[-] Partition 36
[-] First LBA: 385024
[-] Last LBA: 393215
=> First Offset: 0x0BC00000
=> Last Offset: 0x0BFFFE00
[-] Partition Name: spare2
[-] Partition 37
[-] First LBA: 393216
[-] Last LBA: 491519
=> First Offset: 0x0C000000
=> Last Offset: 0x0EFFFE00
[-] Partition Name: laf
[-] Partition 38
[-] First LBA: 491520
[-] Last LBA: 573439
=> First Offset: 0x0F000000
=> Last Offset: 0x117FFE00
[-] Partition Name: boot
[-] Partition 39
[-] First LBA: 573440
[-] Last LBA: 655359
=> First Offset: 0x11800000
=> Last Offset: 0x13FFFE00
[-] Partition Name: recovery
[-] Partition 40
[-] First LBA: [B]655360[/B]
[-] Last LBA: [B]671743[/B]
=> First Offset: 0x14000000
=> Last Offset: 0x147FFE00
[-] Partition Name: drm
[-] Partition 41
[-] First LBA: 671744
[-] Last LBA: 688127
=> First Offset: 0x14800000
=> Last Offset: 0x14FFFE00
[-] Partition Name: sns
[-] Partition 42
[-] First LBA: 688128
[-] Last LBA: 753663
=> First Offset: 0x15000000
=> Last Offset: 0x16FFFE00
[-] Partition Name: mpt
[-] Partition 43
[-] First LBA: 753664
[-] Last LBA: 847871
=> First Offset: 0x17000000
=> Last Offset: 0x19DFFE00
[-] Partition Name: factory
[-] Partition 44
[-] First LBA: 847872
[-] Last LBA: 868351
=> First Offset: 0x19E00000
=> Last Offset: 0x1A7FFE00
[-] Partition Name: fota
[-] Partition 45
[-] First LBA: 868352
[-] Last LBA: 876543
=> First Offset: 0x1A800000
=> Last Offset: 0x1ABFFE00
[-] Partition Name: raw_resources
[-] Partition 46
[-] First LBA: 876544
[-] Last LBA: 884735
=> First Offset: 0x1AC00000
=> Last Offset: 0x1AFFFE00
[-] Partition Name: raw_resourcesbak
[-] Partition 47
[-] First LBA: 884736
[-] Last LBA: 9363455
=> First Offset: 0x1B000000
=> Last Offset: 0x11DBFFE00
[-] Partition Name: system
[-] Partition 48
[-] First LBA: 9363456
[-] Last LBA: 9887743
=> First Offset: 0x11DC00000
=> Last Offset: 0x12DBFFE00
[-] Partition Name: cust
[-] Partition 49
[-] First LBA: 9895936
[-] Last LBA: 12419071
=> First Offset: 0x12E000000
=> Last Offset: 0x17AFFFE00
[-] Partition Name: cache
[-] Partition 50
[-] First LBA: 12419072
[-] Last LBA: 61046783
=> First Offset: 0x17B000000
=> Last Offset: 0x746FFFE00
[-] Partition Name: userdata
[-] Partition 51
[-] First LBA: 61046784
[-] Last LBA: 61071326
=> First Offset: 0x747000000
=> Last Offset: 0x747BFBC00
[-] Partition Name: grow
[+] Partition table md5: ea0c8acec7957b09de3d317ab378824a
LBA is the index ofa 512 bytes block, so for instance to dump drm partition, dd looks like this:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/drm.img bs=[COLOR="Red"][B]512[/B][/COLOR] skip=[COLOR="Red"][B]655360[/B][/COLOR] count=[COLOR="red"][B]16384[/B][/COLOR]
skip value is exactly First LBA in table (=> 655360),
count value is (Last LBA - first LBA +1) (=> 671743 - 655360 +1 => 16384)
You can also retrieve the indexes and size in download mode if you know what partition number is the one you're looking for.
To find partition number do:
Code:
ls -l /dev/block/bootdevice/by-name
It will give you this:
Code:
lrwxrwxrwx root root 2015-01-15 01:12 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-15 01:12 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-15 01:12 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-15 01:12 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-15 01:12 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-15 01:12 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-15 01:12 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-15 01:12 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-15 01:12 dpo -> /dev/block/mmcblk0p20
[B]lrwxrwxrwx root root 2015-01-15 01:12 drm -> /dev/block/mmcblk0p40[/B]
lrwxrwxrwx root root 2015-01-15 01:12 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-15 01:12 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-15 01:12 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-15 01:12 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-15 01:12 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-15 01:12 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-15 01:12 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-15 01:12 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-15 01:12 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-15 01:12 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-15 01:12 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-15 01:12 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-15 01:12 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-15 01:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-15 01:12 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-15 01:12 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-15 01:12 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-15 01:12 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-15 01:12 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-15 01:12 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-15 01:12 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-15 01:12 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-15 01:12 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-15 01:12 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-15 01:12 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-15 01:12 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-15 01:12 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-15 01:12 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-15 01:12 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-15 01:12 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-15 01:12 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-15 01:12 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-15 01:12 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-15 01:12 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-15 01:12 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-15 01:12 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-15 01:12 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-15 01:12 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-15 01:12 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-15 01:12 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-15 01:12 userdata -> /dev/block/mmcblk0p50
So, in our case, drm is partition 40, commands to retrieve index and size are:
Code:
cat /sys/devices/soc.0/f9824900.sdhci/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p[COLOR="Red"]40[/COLOR]/start
cat /sys/devices/soc.0/f9824900.sdhci/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p[COLOR="red"]40[/COLOR]/size
giving you 655360 and 16384 directly.
Last, to dump full MMC until userdata, I just did dd until userdata LBA:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/full_dump.img bs=512 count=12419072
It's, a big file, around 6 GB. If you want to speed up things a bit, read with a block size of 4096 and divide by 8 the count:
Code:
dd if=/dev/block/mmcblk0 of=/data/media/0/full_dump.img bs=4096 count=1552384
I didn't test relocking yet though, not enough free time. Hope it helps, don't hesitate to ask if you need more details.
Click to expand...
Click to collapse
Wow, great post!! Thank you so much for that! :good:

Relocking works if you have cust and misc partitions saved before unlock, tested myself on H815!
Sent from my LG-H815

petro_ionut said:
Relocking works if you have cust and misc partitions saved before unlock, tested myself on H815!
Sent from my LG-H815
Click to expand...
Click to collapse
Interesting because it did not work for me.

I made a lil "thing" to help with the calculations . . .
http://codepen.io/blake_spector/pen/yVrNxg?editors=0010
(feel free to fork, expand, what not . . .)
Again, thanks to letama for the data!

OllieD said:
Interesting because it did not work for me.
Click to expand...
Click to collapse
I read your post in xVANKOs thread. I wonder what the issue was . . . other ppl confirmed it worked.
^ that is basically why i started this thread, to make sure to take all possible precautions.
petro_ionut said:
Relocking works if you have cust and misc partitions saved before unlock, tested myself on H815!
Click to expand...
Click to collapse
:good:
As of yet, my phone is still untouched/locked from when I got back the few days after LG warranty.
But I will, as soon as possible, backup all the partitions and see how it turns out.

blake_spector said:
I read your post in xVANKOs thread. I wonder what the issue was . . . other ppl confirmed it worked.
^ that is basically why i started this thread, to make sure to take all possible precautions.
:good:
As of yet, my phone is still untouched/locked from when I got back the few days after LG warranty.
But I will, as soon as possible, backup all the partitions and see how it turns out.
Click to expand...
Click to collapse
I reverted to lollipop, Dumped my partitions. Unlocked my Bootloader and restored the partitions and my bootloader remained unlocked.
I do have some other dumps and cannot remember the exact commands i used to dump the partitions.
I believe i just reversed the DD commands he issued in his video (swapping the if= and of= )
I also took some partition backups with flashfire before unlocking but havent tried to restore those.
My initial test however proved unsucessful.
I was waiting for him to release his method but he has since locked the thread.
His account was created just before he made his claims which is mildly suspicious.
If it were me, in the true spirit of the XDA Developers community, i would have just released all the information i had regardless of it not working on certain devices. the community could have helped fill the gaps in my work.
I think he is holding off with the aim of claiming the full unofficial unlock bounty, however i feel he will be lucky to recieve much of that given that most people dont pay and most of those who would have long since moved on to other devices.
Time will tell if this is just another hoax.
I'm hoping its not since i'm probably not the only one to unlock my device due to his claims.

OllieD said:
I reverted to lollipop, Dumped my partitions. Unlocked my Bootloader and restored the partitions and my bootloader remained unlocked.
I do have some other dumps and cannot remember the exact commands i used to dump the partitions.
I believe i just reversed the DD commands he issued in his video (swapping the if= and of= )
I also took some partition backups with flashfire before unlocking but havent tried to restore those.
My initial test however proved unsucessful.
I was waiting for him to release his method but he has since locked the thread.
His account was created just before he made his claims which is mildly suspicious.
If it were me, in the true spirit of the XDA Developers community, i would have just released all the information i had regardless of it not working on certain devices. the community could have helped fill the gaps in my work.
I think he is holding off with the aim of claiming the full unofficial unlock bounty, however i feel he will be lucky to recieve much of that given that most people dont pay and most of those who would have long since moved on to other devices.
Time will tell if this is just another hoax.
I'm hoping its not since i'm probably not the only one to unlock my device due to his claims.
Click to expand...
Click to collapse
I am not quite sure that it's a bland hoax (the RElocking part, unlocking all devices . . . another story)
petro_ionut confirmed in this thread it was working for him (as in the original thread) as well as polfrank in the original thread.
Suspisions aside, why would anyone registered a couple of years ago suddenly claim some hoax bs?!
I still have to come up with my own results obviously, but still I trust those guys?! I see no reason not to.
Anyhow, I take your feedback/results very seriously! In the end, I want this to work for me (and others), right?
Also I'm 100% with you on the community part! That's how it should be done . . . I try my best to do it that way.
PS: Did you only swap of= and if= . . . ? or also the seek and skip? I made extra sure to include this tiny detail in my harmful tool http://codepen.io/blake_spector/pen/yVrNxg?editors=0010