Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
================================================== ====
Sending AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE AMSS CERTIFICATE SUCCESS
Sending AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : AMSS WRITE SUCCESS
Sending ADSP Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE ADSP CERTIFICATE SUCCESS
Sending ADSP Data Blocks
(Please Wait for 25 Seconds...)
Status : ADSP WRITE SUCCESS
Sending MDM AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM AMSS CERTIFICATE SUCCESS
Sending MDM AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM AMSS WRITE SUCCESS
Sending MDM DSP1 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP1 CERTIFICATE SUCCESS
Sending MDM DSP1 Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM DSP1 WRITE SUCCESS
Sending MDM DSP2 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP2 CERTIFICATE SUCCESS
Sending MDM DSP2 Data Blocks
(Please Wait for 100 Seconds...)
Status : MDM DSP2 WRITE SUCCESS
Sending WPOS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 1652 Bytes
Status : WRITE WPOS CERTIFICATE SUCCESS
Sending WPOS Data Blocks
[BLOCK 1 0x00000000~0x00FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8D9F6A1AF69045EC0339C2EFFC2527D
---------- : D1CAECCFCFC39F1F44C67A5AD3F6C050
Status : WPOS WRITE SUCCESS
[BLOCK 2 0x01000000~0x016573FF]
Data Size: 0x00657400 Bytes
SHA-256 : 98D712C48E828E9816D3F7E84CFDE5DB
---------- : 2C32011C24D4615234D0F613F4EF7B52
Status : WPOS WRITE SUCCESS
[BLOCK 3 0x01697400~0x01FFFFFF]
Data Size: 0x00968C00 Bytes
SHA-256 : 80EB94E3FB5AE03E9091361275A3138E
---------- : 2D0370E5C2A497C74BEA6BEAA43A9E21
Status : WPOS WRITE SUCCESS
[BLOCK 4 0x02000000~0x02FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 07BE87B2AF4D1386F4C6CA136F3E5A57
---------- : 71DC6DDB330A07AAB4493C8AA329BB58
Status : WPOS WRITE SUCCESS
[BLOCK 5 0x03000000~0x03FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2A3DE5C7CB693B00E257A4E7FB03E834
---------- : 11FAA597F94B220E69E25BD4653BE9B5
Status : WPOS WRITE SUCCESS
[BLOCK 6 0x04000000~0x04FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 16A3B764DD2CCBE5D144B504A919A847
---------- : 2F5DDCBBE2506ACEF6A39800E4DC5124
Status : WPOS WRITE SUCCESS
[BLOCK 7 0x05000000~0x05FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 4A508131A19FC499F19529C55D5D69B8
---------- : D85FA016F8CADE240FA88FA175159699
Status : WPOS WRITE SUCCESS
[BLOCK 8 0x06000000~0x06FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 9E494B017FB7E00D9245C8AEF0F01467
---------- : F3A10341E7441CBEBDE04399AFDD8C5E
Status : WPOS WRITE SUCCESS
[BLOCK 9 0x07000000~0x07FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2AA1C1C01BA5F8825796F134753C7651
---------- : ABAC4C024CF30CE60B624C4E6C8CD665
Status : WPOS WRITE SUCCESS
[BLOCK 10 0x08000000~0x08FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 6F6EA7A66C4AE1A05CF643378A07E1A8
---------- : 523B29D66201C2FBD4053B19E785DE14
Status : WPOS WRITE SUCCESS
[BLOCK 11 0x09000000~0x09FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 017C4DB9A69575E684BADB7515DBBF59
---------- : 67A6F0DA20F034470D6148B12A1013F4
Status : WPOS WRITE SUCCESS
[BLOCK 12 0x0A000000~0x0AFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 1EFE884A458C910A768D6A60FF74BA8B
---------- : 58F546EB92737ACD1A59169E583CD407
Status : WPOS WRITE SUCCESS
[BLOCK 13 0x0B000000~0x0BFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 713CF0944BA46C6820DCEB7A210C365A
---------- : 7F8A1B0C3E168DE07B46E14907F511FC
Status : WPOS WRITE SUCCESS
[BLOCK 14 0x0C000000~0x0CFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 425A9ED14D4A78F21CDD261AB87F2CF1
---------- : 37080DD8E63F6A9BBBC4E9181AF7B9D2
Status : WPOS WRITE SUCCESS
[BLOCK 15 0x0D000000~0x0DFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 0C09DA5584E22D2709C548F2E5CD05F5
---------- : CFB62CE93C7DAF202A4B92299072B4FB
Status : WPOS WRITE SUCCESS
[BLOCK 16 0x0E000000~0x0EFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CC14545EF5F62DA50EFADEC5E077FA15
---------- : FE6723E61D703468E0F2B88A3A77008E
Status : WPOS WRITE SUCCESS
[BLOCK 17 0x0F000000~0x0FFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 75D352196D46AC4FED27B84844D89D27
---------- : A8E6C4BD07D46537FA1D66BC533BF017
Status : WPOS WRITE SUCCESS
[BLOCK 18 0x10000000~0x10FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D6847541FEB0C828C7BE18F045FD2602
---------- : D31D627E75BAA24AD9EBE13E111DCD96
Status : WPOS WRITE SUCCESS
[BLOCK 19 0x11000000~0x11FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 3512321DD2C8349BF40BF6ACD45B82A8
---------- : 970E7902252853F1C75FD6DA3B07416C
Status : WPOS WRITE SUCCESS
[BLOCK 20 0x12000000~0x12FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 970B38B361801866AEB1F9D0E2A6E5FB
---------- : 28066FD1BCF0EF794B57E56439B29152
Status : WPOS WRITE SUCCESS
[BLOCK 21 0x13000000~0x13FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8E0BAEDBCFC0A13A125FF17A9DDDA0E
---------- : 91AC3DD74B6E738F3AD53D269F12CFFD
Status : WPOS WRITE SUCCESS
[BLOCK 22 0x14000000~0x14FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D786A1406E5AF5D0B5354003197BCE87
---------- : F34053A66DF8375001E2DB59D528B21D
Status : WPOS WRITE SUCCESS
[BLOCK 23 0x15000000~0x15FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 47A2B984B6D9C39AF4131C9ED8DB949A
---------- : 82CBC84E0019ECB0E1BABB61E0F47790
Status : WPOS WRITE SUCCESS
[BLOCK 24 0x16000000~0x16FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D4CEA61B44087F662387735C6AF3F626
---------- : D0A782BCFC893D7CD19A1895A2503AE8
Status : WPOS WRITE SUCCESS
[BLOCK 25 0x17000000~0x17FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 93D0DB4DA824CE4660B96A99A1F65989
---------- : CA45F500E83FC9A53D1D8330B150A80E
Status : WPOS WRITE SUCCESS
[BLOCK 26 0x18000000~0x184A17FF]
Data Size: 0x004A1800 Bytes
SHA-256 : 0CE0CCDE41E4E40B170207CABCE6AA18
---------- : 8FD44C00E21833E6B5926A1F0CDFA40A
Status : WPOS WRITE SUCCESS
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
otchere said:
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
Click to expand...
Click to collapse
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
thals1992 said:
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
Click to expand...
Click to collapse
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
otchere said:
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
Click to expand...
Click to collapse
Did you first try the hard reset method with the VolDown + Power first? The only other method I'd recommend is using the Nokia Care Suite instead of what you are using. Its much simpler. Just remember to download the latest edition with the CareSuite External cfg file.
One other thing: what phone are you flashing this *onto*? If you tried flashing a Lumia 900 ROM onto a Lumia 920, for example, there is no possible way it will work (although the flashing tool should detect the discrepancy).
By the way, to get to appropriate forums for the Lumia 900, you should go to the WP7 forums (not WP8, such as this) or possibly to a device-specific forum
Oh, and title your thread properly! Seriously, people... if somebody posts a thread with a title like "plz help me" my default response is "No. Go read the forum rules and come back when you can make posts distinguishable from spam."
Hello,
since 2 weeks i try to get root together with encryption (Settings > Security > encrypt Phone ) running.
But i allready get stuck at the encryption
While testing several CustomROMs (see below) , i was (somewhere in between) able to encrypt OmniROM. (I don't no why it worked neither why it doesnot works anymore.)
Recoverys it used * TWRP 2.8.7.0 from golden-guy
* TWRP 2.8.0.0 from Novafusion
* TWRP 2.8.7.3 from Android-andi
Custom ROMs I used * SlimKAT 4.4.4 from Android-Andi
* CM12.1 from Novafusion
* CM 11.0 from Novafusion
* RR1 5.1.1 from Novafusion
* OmniROM 5.1.1 from golden-guy
(erverything in the latest version. (Date today 21. May .2016)
ATM I am not able to encrypt any of the above ROMs
The last 2 days i followed the instructions from android-andis thread :
http://forum.xda-developers.com/showthread.php?t=2548257
android-andis Instructions (date: 22 May 2016)
Backup all important stuff! We need to format the device!
Make sure using latest TWRP
Wipe -> Advanced Wipe:
Cache
Dalvic
System
Data
Wipe -> Format Data -> Type yes to confirm
This is the most important step! It will keep some space for the footer! Without that encryption is not possible!
Flash Rom
Reboot
Set a Pin for Lockscreen
Encrypt your device
Point by Point severaly times. (Just to make clear: Yes, I did "Format Data" and typed yes to perform it.)
It just didn't work.
----------------------------------------------------------------------------------------
Here are some Infos from the last try with the combination of:
TWRP 2.7.8.3 from android-andi &
SlimKAT 4.4.4 from android-andi April 2016 release
just in case someone needs it. The heimdall print of the PIT.
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
...
Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 28519
Unknown 4: 25708
Unknown 5: 28261
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MBR,GPT
Flash Filename:
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 256
Partition Block Count: 768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MasterTOC
Flash Filename: STE_boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: goldenxx.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6144
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot1
Flash Filename: STE_boot1.img
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot2
Flash Filename: STE_boot2.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Dnt
Flash Filename: dnt.ssw
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: reserved
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS
Flash Filename: cspsa.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 18432
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS2
Flash Filename: cspsa2.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: EFS.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 53248
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS
Flash Filename: modemfs.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 86016
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS2
Flash Filename: modemfs2.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 118784
Partition Block Count: 102400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Fota
Flash Filename: ssgtest.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 380928
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IPL Modem
Flash Filename: ipl.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 385024
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Modem
Flash Filename: modem.bin
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 417792
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Loke4
Flash Filename: normal.bin
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 421888
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: 2ndLoke4
Flash Filename: normal2.bin
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 425984
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 458752
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel
Flash Filename: boot.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 491520
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel2
Flash Filename: recovery.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 524288
Partition Block Count: 2457600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2981888
Partition Block Count: 1720320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHEFS
Flash Filename: cache.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4702208
Partition Block Count: 655360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5357568
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: userdata.img
FOTA Filename: remained
And also the output of fdisk /dev/block/mmcblk0 (taken while adb into recovery)
# fdisk -ul /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 15269888 sectors, 3360M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15269854
Number Start (sector) End (sector) Size Code Name
2 256 1023 384K 0700 MasterTOC
3 1024 3071 1024K 0700 PIT
4 6144 8191 1024K 0700 MD5HDR
5 8192 9215 512K 0700 STEboot1
6 9216 10239 512K 0700 STEboot2
7 10240 11263 512K 0700 Dnt
8 11264 12287 512K 0700 reserved
9 16384 18431 1024K 0700 CSPSAFS
10 18432 20479 1024K 0700 CSPSAFS2
11 20480 53247 16.0M 0700 EFS
12 53248 86015 16.0M 0700 ModemFS
13 86016 118783 16.0M 0700 ModemFS2
14 118784 221183 50.0M 0700 Fota
15 380928 381055 65536 0700 IPL Modem
16 385024 413695 14.0M 0700 Modem
17 417792 421887 2048K 0700 Loke4
18 421888 425983 2048K 0700 2ndLoke4
19 425984 458751 16.0M 0700 PARAM
20 458752 491519 16.0M 0700 Kernel
21 491520 524287 16.0M 0700 Kernel2
22 524288 2981887 1200M 0700 SYSTEM
23 2981888 4702207 840M 0700 CACHEFS
24 4702208 5357567 320M 0700 HIDDEN
25 5357568 15269854 4839M 0700 DATAFS
cat fstab.samsunggolden from recovery:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p12 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache f2fs nodiratime,noatime,nosuid,nodev,discard,background_gc=off,inline_xattr,active_logs=2 wait
/dev/block/mmcblk0p11 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/mmcblk0p25 /data f2fs nodiratime,noatime,nosuid,nodev,discard,background_gc=off,inline_xattr,active_logs=2 wait,encryptable=footer
# Vold managed volumes (External SDCard)
/devices/sdi0/mmc_host/mmc1/mmc1* auto vfat defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
# Recovery
/dev/block/mmcblk0p20 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p21 /recovery emmc defaults recoveryonly
Trying encryption (Settings > Security > encrypt Phone) the adb logcat presented:
E/Cryptfs ( 1687): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------------------------------------------------------------------------------------
Here are some Infos from the last try with the combination of:
TWRP 2.7.8.0 from golden-guy &
OmniROM 5.1.1 from golden-guy (20160505 release)
cat fstab.samsunggolden from recovery:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p12 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p11 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
# Vold managed volumes (External SDCard)
/devices/sdi0/mmc_host/mmc1/mmc1* auto vfat defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
# Recovery
/dev/block/mmcblk0p20 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p21 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p22 /system ext4 defaults recoveryonly
/dev/block/mmcblk0p23 /cache ext4 defaults recoveryonly
/dev/block/mmcblk0p25 /data ext4 defaults recoveryonly
/dev/block/mmcblk0p11 /efs ext4 defaults recoveryonly
When trying encryption (Settings > Security > encrypt Phone) the adb logcat presented:
E/Cryptfs ( 1686): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1686): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
--------------------------------------------
I am willing to serve further Information if needed, or for example to:
* resize the /dev/block/mmcblk0p25 via adb or
* change the PIT via "PIT Magic" / "EFS Professional"
if someone is going to guide me.
If the adb solution needs the parted command, please direct me to a recovery which got it.
I couldn't find any
Just found some obscure Download-Links for parted to put it barehand into /system . But i an not willing to use this.
Any help is welcome.
Greeting
Follow http://andi34.github.io/faq_twrp.html
After that flash your rom and gapps.
Enjoy encryption (SlimLP and CM12.1 need a different kernel to use it because of CAF based vold, i don't think i have added needed changes to my latest SlimLP build).
Hello Android-Andi,
Android-Andi said:
Follow http://andi34.github.io/faq_twrp.html
After that flash your rom and gapps.
Enjoy encryption (SlimLP and CM12.1 need a different kernel to use it because of CAF based vold, i don't think i have added needed changes to my latest SlimLP build).
Click to expand...
Click to collapse
thanx for taking time to help. :good: Unfortunatly it didn't work.
First of all i Flashed your TWRP 2.8.7.3 build via recovery.
After a reboot into your recovery i followed exactly the steps from your URL.
Then i Installed your latest SlimKAT 4.4.4 (11042016) via Recovery . (NO gapps)
(I also checked the MD5 of the downloaded files)
After a direct boot into system & setting up a 8 digit PIN i tried to encrypt the phone.
The result of cat abd_logcat_of_encrypting_SlimKAT.txt | grep Cryptfs was still:
E/Cryptfs ( 1682): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Just to be sure i did it exactly the same way with the OmniROM 5.1.1. golden-guy (20160505 release) and golden-guy latest TWRP 2.8.7.0
the result of adb logcat was:
E/Cryptfs ( 1681): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1681): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
....
Just a thought:
I am kinda confused. About a week ago it worked to encrypt only with OmniROM. (I am not sure if i ever did a Format Data befor that time.) And after i tried several other ROMs it does not work anymore to encrypt any ROM.
....
I searched a lot around this problem.
As far as i understand the "encryptable=footer" in the fstab indicates that the filesystem should be able to be encyrpted
AND
the /data partition on /dev/block/mmcblk0p25 has to be at the end of /mmcblk0
AND
/mmcblk0 has to have some free sectors at the end.
As far as i manage to read the fdisk output from the first Post: There are some "unusable"/unused sectors at the end of mmcblk0 .
Is it possible that this sectors are not for the encryption ?
Do i just have to resize (shrink) /dev/block/mmcblk0p25 a little ?
Or do i have to resize (shrink) the ext4 filesystem (which contains /data and ist "lying" on /dev/block/mmcblk0p25?
Or are these both the same ? :silly:
Greetings
You could try the twrp somewhere on last pages of my twrp thread, It's attached as flashable zip.
Atm i don't own a golden and can't test myself.
Some roms need 2 kernel commits to have working encryption because some roms use CAF based vold source (cm12.1 and newer, SlimLP)
https://github.com/andi34/android_k...mmit/514595570f2f542f55576946d913a9b17e6664e7
https://github.com/andi34/android_k...mmit/6c80b864ff6458ed8643c9b2f9bca9f11c63fabd
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
You could try the twrp somewhere on last pages of my twrp thread, It's attached as flashable zip.
Atm i don't own a golden and can't test myself.
Some roms need 2 kernel commits to have working encryption because some roms use CAF based vold source (cm12.1 and newer, SlimLP)
Click to expand...
Click to collapse
Hallo Android-Andi,
thanks for your time !!
i wasn't sure which TWRP you meant exactly. So i did a couple of tests
I allways worked in the following order:
1. flashed the TWRP-Recovery via Recovery
2. rebooted into the "downgraded" Recovery
3. wiped the dalvic, system, cache
4. formated Data
5. rebooted into recovery
6. flashed the mentioned ROM
First try:
TWRP_test4 (?) from yourt TWRP Thread(wich turned out to be a TWRP 2.8.7.0) & Slim KAT 4.4.4
adb logcat
E/Cryptfs ( 1684): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
all following TWRPs are from "your" AFH site.(/I]
Second try:
TWRP 2.8.7.0 F2FS & SlimKAT 4.4.4
adb logcat
E/Cryptfs ( 1681): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
Third try:
TWRP 2.8.7.0 f2fs & SlimLP (from android-andi) because you mentioned several times that there has to be some fixes for SlimLP & Cm12.1
adb logcat
Far Up in the logcat...
I/Cryptfs ( 1668): Check if PFE is activated on Boot
E/Cryptfs ( 1668): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1668): Error getting crypt footer and key
and later on the typical (but now with "Bad magic ..." line
E/Cryptfs ( 1668): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1668): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
Forth try:
TWPR 2.8.6.4 & SlimKAT 4.4.4
adb logcat
E/Cryptfs ( 1682): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
I hope you have another idea for me......
Greetings
Hello Everybody !
I managed to encrypt from Settings :victory:
I "just" resized (shrinked) the /data partition a little bit.
To Perform this i used the TWRP 2.8.7.3 version from Android-Andi
because it was the one which got all the commands i needed for it.
@ android-andi (would it make sense to change the TWRP setup, so that his tweak is done automatically ?)
at least some people semmed to have similar Problems like me.
I did a adb root / adb shell into the Recovery and followed a Tipp from over Here:
http://android.stackexchange.com/questions/117405/how-do-you-encrypt-your-device-running-cyanogenmod-12-1
Just because the www is sometimes full of dead ends i post the Instructions here, as I used them on MY device.
So i changed them a little bit from the originalpost.
If you wanna try something similar you should NOT just copy & paste the Commands.
Make shure which "/dev/block/..." is your /data partition
In Linux i did: (don't know what do to in Windows, sorry)
$ adb root
$ adb shell
within the adb Shell YOU should
~ # mount | grep data
to find the actual block device of the data partition.
For ME it is /dev/block/mmcblk0p25
so i did the following:
~ # umount /data
& i had also to do
~ # umount /sdcard
~ # e2fsck -f /dev/block/mmcblk0p25
everything was fine otherwise i could do e2fsck -f -p /dev/block/mmcblk0p25 to repair the stuff
~ # tune2fs -l /dev/block/mmcblk0p25 to obtain the "Block count" from the output.
~ # tune2fs -l /dev/block/mmcblk0p25
tune2fs 1.42.9 (28-Dec-2013)
Filesystem volume name: <none>
Last mounted on: /data
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 310080
Block count: 1239035
Reserved block count: 0
Free blocks: 1174719
Free inodes: 309535
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 303
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8160
Inode blocks per group: 510
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Last mount time: Tue Jan 3 14:00:32 2012
Last write time: Tue Jan 3 14:05:19 2012
Mount count: 0
Maximum mount count: -1
Last checked: Tue Jan 3 14:05:19 2012
Check interval: 0 (<none>)
Lifetime writes: 213 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
For me it was : 1239035
~ # resize2fs /dev/block/mmcblk0p25 1239015 , i.e. substract a sufficient amount like 20 from the original block count. As far as i read 8 should be the exact amonunt. But I am not fighting for the last Byte.
~ # resize2fs /dev/block/mmcblk0p25 1239015
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /dev/block/mmcblk0p25 to 1239015 (4k) blocks.
The filesystem on /dev/block/mmcblk0p25 is now 1239015 blocks long.
to check if everything is okay:
~ # e2fsck -f -p /dev/block/mmcblk0p25 found a minor problem which got fixed
~ # e2fsck -f -p /dev/block/mmcblk0p25
/dev/block/mmcblk0p25: Inode 7, i_size is 1270947840, should be 1275146240. FIXED.
/dev/block/mmcblk0p25: 545/310080 files (8.3% non-contiguous), 64316/1239015 blocks
After that i just did a reboot into recovery.
I Just wiped dalvic, system, cache & DATA ( NO FORMAT TO MESS THINGS UP AGAIN !!!)
Then I flashed SlimKAT 4.4.4. from Android-Andi April 2016 build.
Rebooted into System.
In System in Settings > Interface > Lockscreen i set up PIN
Than in Settings > Security > encrypt Phone EVERYTHING went fine. Finally after a couple of weeks !!
adb Logcat "tells" now:
D/Cryptfs ( 1686): Just asked init to shut down class main
D/Cryptfs ( 1686): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 1686): unmounting /data/data succeeded
D/Cryptfs ( 1686): unmounting /data succeeded
D/Cryptfs ( 1686): Just triggered post_fs_data
D/Cryptfs ( 1686): post_fs_data done
D/Cryptfs ( 1686): Just triggered restart_min_framework
E/Cryptfs ( 1686): Crypt_ftr version doesn't support persistent data
I/Cryptfs ( 1686): Enabling support for allow_discards in dmcrypt.
E/Cryptfs ( 1686): Encrypting filesystem in place...
After first root app installation (root browser) the system did a crash.
Since thea i installed 3 more root apps. so far (about since an hour) the system is running stable.
Greetings
P.S.
I Suppose this trick should at least work with any KiTKat ROM.....
I gonna try Lollipop , but not tonight ....
Update
to anybody how may it concern.
I installed successfully OmniRom 5.1.1. on the device. encryption still working.
Recovery was still: TWRP 2.8.7.3 by Android-andi
OmniROM 5.1.1. by golden-guy (build 05052016)
I just booted into Recovery & entered the choosen encryption PIN & wiped:
system
cache
dalvic
data !!
I did NOT format data.
Next step was to flash the OmniROM image.
Booted back into System.
Everything worked fine. data was still encrypted !
-----
Next try was to flash CM12.1 by Novafusion (bulid 24 05 2016)
The same TWRP a above.
I had no errors flashing the same way as above.
But booting into system ended with a "corrupted" encrypted Filesystem.
A factory Reset didn't help.
----
Even flashing the promary SlimKAT 4.4.4 by Android-andi didn't changed the problem.
I don't know the reason why the corruption happend (perhaps because i didn't used the "novafusion TWRP Recovery" , perhaps for another reason.
So i did a "classic" Flash with "wipe of dalvic, system, cache" and a "format data".
after flashing SlimKAT again, i got the same old error from all the postings above.
----
Im not gonna dig deeper into this Stuff. I now gonna do the "/Data shrink" again and gonna be happy with what i managed to fullfill.
Greeting
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
{
"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"
}
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
sry for bad english
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
you're welcome
this also works with all Snapdragon devices
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2-QPST_2.7.422
3- QDLoader HS-USB Driver
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
download links for drivers not working.
jkenic said:
download links for drivers not working.
Click to expand...
Click to collapse
broken links updated
thx for informing me
jkenic said:
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
download links for drivers not working.
Click to expand...
Click to collapse
bro has install nokia care suite?
thinhx2 said:
bro has install nokia care suite?
Click to expand...
Click to collapse
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
Ramy3r said:
broken links updated
thx for informing me
Click to expand...
Click to collapse
u re welcome but number 2 download link still not working.......
jkenic said:
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
u re welcome but number 2 download link still not working.......
Click to expand...
Click to collapse
sry fixed and add links from google drive
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
jkenic said:
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
Click to expand...
Click to collapse
Do u have any problems with ur operating system maybe its not running very well or u have some program that interferes with the download/flashing process
Sent from my Nokia_X2 using XDA Labs
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
jkenic said:
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
Click to expand...
Click to collapse
Sry for late comment .. Win 10 has a lot of support issues like the error 0x000007 with some games and programs ... I recommend win 7 for best results
Sent from my Nokia_X2 using XDA Labs
Work with lumia devices?
thinhx2 said:
Work with lumia devices?
Click to expand...
Click to collapse
i tested this only on android devices i'm not sure about windows phone tbh
but if it has same files "firehose , rawprogram and label layout" included in firmware files then its possible
error
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Hoоdlum said:
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Click to expand...
Click to collapse
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Ramy3r said:
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Click to expand...
Click to collapse
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Hoоdlum said:
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Click to expand...
Click to collapse
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Ramy3r said:
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Click to expand...
Click to collapse
I downloaded from your site on the links firmware driver program. Error exact same stands in the middle.
That log
Code:
[FONT="Verdana"][B]Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
SEARCHPATH:C:\RM-1013
RAWPROGRAM:
rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH:
P12026702dpi600_label_layout.xml
ACKRAWDATAEVERYNUMPACKETS:True
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:True
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\RM-1013
RAWPROGRAM file path: C:\RM-1013\rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH file path:C:\RM-1013\P12026702dpi600_label_layout.xml
Programmer Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
Start Download
Program Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Enable Ack Raw Data Every 100Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:9
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Set TxBuffer 0xc000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x37226800
Download Image
PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x125c3
PROGRAM: Partition 0, Sector: 16384, Length: 75203 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_NON-HLOS.bin
FireHose Log: start 16384, num 75203
FireHose Log: Write failed Sector 16480, Errno 2
FireHose Log: Finished sector address 16480
PROGRAM: Written Bytes 0x24b8600 (64)
Program Size: 36.72 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 147456, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 147456, num 492
FireHose Log: Write failed Sector 147456, Errno 2
FireHose Log: Finished sector address 147456
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 148480, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 148480, num 492
FireHose Log: Write failed Sector 148480, Errno 2
FireHose Log: Finished sector address 148480
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x100 to file size in sector 0x2d
PROGRAM: Partition 0, Sector: 149504, Length: 45 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sdi.mbn
FireHose Log: start 149504, num 45
FireHose Log: Write failed Sector 149504, Errno 2
FireHose Log: Finished sector address 149504
PROGRAM: Written Bytes 0x5a00 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 180224, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 180224, num 938
FireHose Log: Write failed Sector 180224, Errno 2
FireHose Log: Finished sector address 180224
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 181248, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 181248, num 938
FireHose Log: Write failed Sector 181248, Errno 2
FireHose Log: Finished sector address 181248
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 182272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 182272, num 296
FireHose Log: Write failed Sector 182272, Errno 2
FireHose Log: Finished sector address 182272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 183272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 183272, num 296
FireHose Log: Write failed Sector 183272, Errno 2
FireHose Log: Finished sector address 183272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x38d5
PROGRAM: Partition 0, Sector: 196608, Length: 14549 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_boot.img
FireHose Log: start 196608, num 14549
FireHose Log: Write failed Sector 196608, Errno 2
FireHose Log: Finished sector address 196608
PROGRAM: Written Bytes 0x71aa00 (64)
Program Size: 7.10 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 229376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 229376, num 663
FireHose Log: Write failed Sector 229376, Errno 2
FireHose Log: Finished sector address 229376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 230376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 230376, num 663
FireHose Log: Write failed Sector 230376, Errno 2
FireHose Log: Finished sector address 230376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Partition 0, Sector: 344064, Length: 262160 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_1.img
FireHose Log: start 344064, num 262160
FireHose Log: Write failed Sector 344064, Errno 2
FireHose Log: Finished sector address 344064
PROGRAM: Written Bytes 0x8002000 (64)
Program Size: 128.01 MB
PROGRAM: Partition 0, Sector: 606600, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_2.img
FireHose Log: start 606600, num 16
FireHose Log: Write failed Sector 606600, Errno 29
FireHose Log: Finished sector address 606600
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 610352, Length: 257992 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_3.img
FireHose Log: start 610352, num 257992
FireHose Log: Write failed Sector 610352, Errno 2
FireHose Log: Finished sector address 610352
PROGRAM: Written Bytes 0x7df9000 (64)
Program Size: 125.97 MB
PROGRAM: Partition 0, Sector: 868352, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_4.img
FireHose Log: start 868352, num 16
FireHose Log: Write failed Sector 868352, Errno 2
FireHose Log: Finished sector address 868352
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 872104, Length: 258384 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_5.img
FireHose Log: start 872104, num 258384
FireHose Log: Write failed Sector 872104, Errno 2
FireHose Log: Finished sector address 872104
PROGRAM: Written Bytes 0x7e2a000 (64)
Program Size: 126.16 MB
PROGRAM: Partition 0, Sector: 1130496, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_6.img
FireHose Log: start 1130496, num 16
FireHose Log: Write failed Sector 1130496, Errno 2
FireHose Log: Finished sector address 1130496
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1130888, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_7.img
FireHose Log: start 1130888, num 16
FireHose Log: Write failed Sector 1130888, Errno 2
FireHose Log: Finished sector address 1130888
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1134640, Length: 95712 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_8.img
FireHose Log: start 1134640, num 95712
FireHose Log: Write failed Sector 1134640, Errno 2
FireHose Log: Finished sector address 1134640
PROGRAM: Written Bytes 0x2ebc000 (64)
Program Size: 46.73 MB
PROGRAM: Partition 0, Sector: 1392640, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_9.img
FireHose Log: start 1392640, num 16
FireHose Log: Write failed Sector 1392640, Errno 2
FireHose Log: Finished sector address 1392640
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1654784, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_10.img
FireHose Log: start 1654784, num 16
FireHose Log: Write failed Sector 1654784, Errno 29
FireHose Log: Finished sector address 1654784
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1655176, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_11.img
FireHose Log: start 1655176, num 16
FireHose Log: Write failed Sector 1655176, Errno 29
FireHose Log: Finished sector address 1655176
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1777664, Length: 11376 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_cache_1.img
FireHose Log: start 1777664, num 11376
FireHose Log: Write failed Sector 1777664, Errno 2
FireHose Log: Finished sector address 1777664
PROGRAM: Written Bytes 0x58e000 (64)
Program Size: 5.55 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x3ca9
PROGRAM: Partition 0, Sector: 1974272, Length: 15529 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_recovery.img
FireHose Log: start 1974272, num 15529
FireHose Log: Write failed Sector 1974272, Errno 2
FireHose Log: Finished sector address 1974272
PROGRAM: Written Bytes 0x795200 (64)
Program Size: 7.58 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x1
PROGRAM: Partition 0, Sector: 1998848, Length: 1 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_misc_erase.img
FireHose Log: start 1998848, num 1
ReadFile last error: 0
PROGRAM: Written Bytes 0x200 (64)
Program Size: 0.00 MB
PROGRAM: Partition 0, Sector: 2015232, Length: 262136 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img
WriteFile last error: 0
PROGRAM: Send XML command fail code: 9
Failed to write C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img to the device
Download Fail:FireHose Fail Failed to Upload the emmc images to the phone using Firehose.
Finish Download[/B][/FONT]
Hello. At some point, the phone turned off and then when you press the power button, the phone booted up to the moment with the logo prowered by android -> Asus and turned off.
If you put your phone on charge: battery logo -> powered by android -> Asus.
When using keyboard shortcuts, fastboot works.
There were attempts to flash through the fastboot to the v16 firmware and the factory one, but everything is useless, everything is going well through cmd, until the partition table is updated.
I hope for help in resuscitation.
Code:
==========================================
ZE620KL raw flashing program
Version 20180129
==========================================
erase cmd: -f
need_wipe_data: 1
Please connect device to host.
This is ZE620KL device!
This is FUSED device!
This is SDM636 CPU!
Device support check CID !!
Device's CID is ASUS!
RAW file found: OPEN_ZE620KL_15.0501.1711.46_M1.2.2.P8_Factory_Phone-userdebug.raw
file size is: 2236165676 bytes(2183755 Kbytes)
This is ZE620KL RAW file for ZE620KL device.
Folder is not exsit
Get return message:
aft_support: yes
finished. total time: 0.001s
Support AFT security.
fastboot device serial: J8AXB765A124HL4
fastboot device serial len: 15
target reported max download size of 536870912 bytes
sending 'aft' (0 KB)...
OKAY [ 0.008s]
writing 'aft'...
OKAY [ 0.003s]
finished. total time: 0.013s
Start process RAW file: OPEN_ZE620KL_15.0501.1711.46_M1.2.2.P8_Factory_Phone-userdebug.raw
file size is: 2236165676 bytes(2183755 Kbytes)
This is ZE620KL RAW file for ZE620KL device.
=================================================================================
Process File for partition label: partition, size: 262144bytes
#=================================================================================
Process File for partition label: xbl, size: 2883584bytes
#=================================================================================
Process File for partition label: abl, size: 262144bytes
#=================================================================================
Process File for partition label: pmic, size: 262144bytes
#=================================================================================
Process File for partition label: rpm, size: 262144bytes
#=================================================================================
Process File for partition label: tz, size: 2097152bytes
#=================================================================================
Process File for partition label: hyp, size: 524288bytes
#=================================================================================
Process File for partition label: devcfg, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib64, size: 524288bytes
#=================================================================================
Process File for partition label: keymaster, size: 524288bytes
#=================================================================================
Process File for partition label: xblbak, size: 2883584bytes
#=================================================================================
Process File for partition label: ablbak, size: 262144bytes
#=================================================================================
Process File for partition label: pmicbak, size: 262144bytes
#=================================================================================
Process File for partition label: rpmbak, size: 262144bytes
#=================================================================================
Process File for partition label: tzbak, size: 2097152bytes
#=================================================================================
Process File for partition label: hypbak, size: 524288bytes
#=================================================================================
Process File for partition label: devcfgbak, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlibbak, size: 262144bytes
#=================================================================================
Process File for partition label: cmnlib64bak, size: 524288bytes
#=================================================================================
Process File for partition label: keymasterbak, size: 524288bytes
#=================================================================================
Process File for partition label: dsp, size: 16777216bytes
#=================================================================================
Process File for partition label: modem, size: 106430464bytes
#=================================================================================
Process File for partition label: logfs, size: 16384bytes
#=================================================================================
Process File for partition label: bluetooth, size: 536576bytes
#=================================================================================
Process File for partition label: boot, size: 18087936bytes
#=================================================================================
Process File for partition label: recovery, size: 21495808bytes
#=================================================================================
Process File for partition label: asusfw, size: 67108864bytes
#=================================================================================
Process File for partition label: system, size: 1281728448bytes
###=================================================================================
Process File for partition label: vendor, size: 707982956bytes
##
========================================
Flashing gpt_both0.bin for partition begin
========================================
target reported max download size of 536870912 bytes
sending 'CRC' (0 KB)...
OKAY [ 0.009s]
writing 'CRC'...
OKAY [ 0.008s]
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'partition' (256 KB)...
OKAY [ 0.014s]
writing 'partition'...
FAILED (remote: Error Updating partition Table
)
finished. total time: 0.033s
!!!ERROR to flash!!!
ERROR: Flashing files!
errorlevel="1"