Related
hi, when I tried to flash my motorola defy with sbf_flash I get error:verifying CG31 Checksum error (Expected 0x9a68, Got 0xc5a4)
===JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 8BAC AP
04: CG34 0xB0700000-0xB07047FF AB80 AP
05: CG35 0xB1000000-0xB17FFFFF 100C AP
06: CG39 0xB3300000-0xC79C07FF C7E6 AP
07: CG42 0xB0800000-0xB0842FFF 4BB7 AP
08: CG45 0xB0C00000-0xB0F007FF 738D AP
09: CG47 0xB1800000-0xB1FFFFFF 45F0 AP
10: CG53 0xB2F00000-0xB2F007FF FDFF AP
11: CG61 0xB0B00000-0xB0B7FFFF 4A7C AP
12: CG64 0xB0000000-0xB00047FF 85D0 AP
13: CG65 0xB0180000-0xB01847FF 2409 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG32: 100.0%
-- OK
>> uploading CG33: 100.0%
-- OK
>> uploading CG34: 100.0%
-- OK
>> uploading CG35: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG45: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG53: 100.0%
-- OK
>> uploading CG61: 100.0%
-- OK
>> uploading CG64: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> verifying CG31
Checksum error (Expected 0x9a68, Got 0xc5a4)
!! failed
>> verifying CG32
Checksum error (Expected 0x4805, Got 0x4a05)
!! failed
>> verifying CG33
usb_bulk_read -110
!! failed
>> verifying CG34
usb_bulk_read -110
!! failed
>> verifying CG35
usb_bulk_write -110
!! failed
>> verifying CG39
usb_bulk_write -110
!! failed
>> verifying CG42
usb_bulk_write -110
!! failed
>> verifying CG45
usb_bulk_write -110
!! failed
>> verifying CG47
usb_bulk_write -110
!! failed
>> verifying CG53
usb_bulk_write -110
!! failed
>> verifying CG61
usb_bulk_write -110
!! failed
>> verifying CG64
usb_bulk_write -110
!! failed
>> verifying CG65
usb_bulk_write -110
!! failed
>> rebooting
usb_bulk_write -110
Click to expand...
Click to collapse
Now, it does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
What I can doing to unbrick my defy?
Thank's!
Were you trying to downgrade? What rom were you on earlier?
Sent from my MB525 using Tapatalk
ryan8r said:
Were you trying to downgrade? What rom were you on earlier?
Click to expand...
Click to collapse
I don't know what rom version was before, maybe I can somehow check it?
Were you on Eclair, Froyo or Gingerbread?
Sent from my MB525 using Tapatalk
I am having the same issues here, my defy wont load, been stuck in the bootloader for a couple of hours. Any help will be greatly aprecciated
I'm having the same error's. Somebody solved the problem or know, what is the problem?
Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
scamex said:
Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
Click to expand...
Click to collapse
Thank you for posting these links, it's sometime impossible to figure out "what to google" if you know what I mean.
Was wondering if you had found any MTP drivers that work, as the ones LG provides does not work for windows 8 64bit.
tidaboy9 said:
Thank you for posting these links, it's sometime impossible to figure out "what to google" if you know what I mean.
Was wondering if you had found any MTP drivers that work, as the ones LG provides does not work for windows 8 64bit.
Click to expand...
Click to collapse
Just install Media Sync Manager i belive from microsoft and you`ll be fine.
problem with my lg g3 help!!
i have a problem with my lg g3 d855, not write in emmc
elite124 said:
i have a problem with my lg g3 d855, not write in emmc
Click to expand...
Click to collapse
Once it happened me too. I just factory resetted the device and after that flashing was ok.
scamex said:
Once it happened me too. I just factory resetted the device and after that flashing was ok.
Click to expand...
Click to collapse
and I do, so now I'm losing esperansas that attempt everything and get errors
elite124 said:
and I do, so now I'm losing esperansas that attempt everything and get errors
Click to expand...
Click to collapse
Please use google translate.
How fixed
elite124 said:
and I do, so now I'm losing esperansas that attempt everything and get errors
Click to expand...
Click to collapse
Dis you fix this issue????? i have the same error
same error
error flashing or erasing
if you solve this problem, please email me [email protected]
where to place AP-CHIP dll and ATT archive to choose in smart boot diagnostic tool ?
nickamania said:
where to place AP-CHIP dll and ATT archive to choose in smart boot diagnostic tool ?
Click to expand...
Click to collapse
I want to know too.
--------------------------------------------------------
I take this opportunity to present my case, I have the green screen (Appz Whatchdog bark) screen when I try to enter download mode with the usual method (Volume Up and push USB cable) tries to enter but ends up turning off the display and is recognized immediately in admisnistrador device as "Qualcomm HS-USB QDLoader 9008" all with the battery connected. My question now is this, do I still should remove the battery and make the bridge between the 2nd. and ground contact on the motherboard of the device? And thenceforth to follow the repair with SmartBootDiag v1.3.1
Lg g3 d 850 att smart boot bin missing in recovery folder .if any one have plz upload
hello, i have bought g4 with same problem, i have lg flash tool and qualcomm drivers but i dont have required files for it, its h818n dual sim, any idea ?
thanks
At & t lg g3 d850
cdmababa said:
Lg g3 d 850 att smart boot bin missing in recovery folder .if any one have plz upload
Click to expand...
Click to collapse
Please send mesage from me [email protected]. Using LG smart boot Diag Tool to unbrick LG G3 models that stuck in qualcomm 9008 mode.I got the link:good:
ertas71 said:
Please send mesage from me [email protected]. Using LG smart boot Diag Tool to unbrick LG G3 models that stuck in qualcomm 9008 mode.I got the link:good:
Click to expand...
Click to collapse
Plz explain ,
Sent from my HTC_One_max using Tapatalk
G3
Hi.D850 D851 Ap_chip https://mega.nz/#!h0JExLwb!rDBMrSbj5nuUhyVN5EzoeHO6d3apl1EPjU4ugLcgYFI
http://www.gsmkolik.com/lg-g3/21619-lg-smart-boot-diag-tool-unbrick-lg-g3.html
Ap-Chip for D850,D851,All EU Global,LGLS990_ASPR_Sprint,LGVS985_AVRZ_VRZ
LG G3 D858HK hard Bricked Need Help
After Boot diagnostic still my phone is on same bricked state only qualcomm 9008 no emmc detected the log file of boot diagnostic is as
>> ---------------------------- Start Logging ----------------------------
>> USB Status : Qualcomm HS-USB QDLoader 9008 (COM41)
>> Ready to access the target board...
>> BootLoader File : LGD858HK_AHKG_HKG.mbn
>> 1. Model : LGD858HK , 2. Suffix : AHKG , 3. Operator : HKG
>> Bootloader : LGD858HK_AHKG_HKG.mbn
>> AP Chip : MSM8974_G3 , BootLoader : LGD858HK_AHKG_HKG.mbn
>> Trying Connection To Device with sahara protocol for AP Chip.
>> Successfully Connection To Device with sahara protocol for AP Chip.
>> connected with Sahara Protocol successfully.
>> Loading flash to SYS_IMEM.
>> Loading 0 Kbytes to SYS_IMEM.
>> Loading 4 Kbytes to SYS_IMEM.
>> Loading 8 Kbytes to SYS_IMEM.
>> Loading 12 Kbytes to SYS_IMEM.
>> Loading 16 Kbytes to SYS_IMEM.
>> Loading 20 Kbytes to SYS_IMEM.
>> Loading 24 Kbytes to SYS_IMEM.
>> Loading 28 Kbytes to SYS_IMEM.
>> Loading 32 Kbytes to SYS_IMEM.
>> Loading 36 Kbytes to SYS_IMEM.
>> Loading 40 Kbytes to SYS_IMEM.
>> Loading 44 Kbytes to SYS_IMEM.
>> Loading 45 Kbytes to SYS_IMEM.
>> Successfully Loaded to SYS_IMEM.(Total 45 Kbytes)
>> Flash Image was normally loaded to SYS_IMEM.
>> Checking for device status.
>> [Verifying Hello Protocol]
>> Sending Hello request 0 time(s).
>> SendSync EHOST_HELLO_RSP OK.
>> Hello Response OK.
>> Got Hello response for Hello request.
>> [Verifying Security Protocol]
>> Security Response OK.
>> Connected to flash bootloader.
1> ----------------------------------------------------------------------
>> PBL SOFTWARE HISTORY
1> ----------------------------------------------------------------------
>> 1.Smart Boot Diagnosis Tool v1.3.1 <analysis tool="" for="" booting="" failure="">
>> 2.PBL_VERSION_NUMBER [fc021834] = 1c6c6162
1> ----------------------------------------------------------------------
1> ----------------------------------------------------------------------
>> SECURE_BOOT_INFORMATION
1> ----------------------------------------------------------------------
>> [QFPROM - AP Anti-rollback Region of OEM Region ]
>> QFPROM_AP_ANTIROLLBACK_1 [0xFC4B80B8] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_2 [0xFC4B80BC] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_3 [0xFC4B80C0] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_4 [0xFC4B80C4] = 0x00000000
1> ----------------------------------------------------------------------
>> QFPROM_DEVICE_SN_1 [0xFC4B81F0] = 0x1256AFAE
>> QFPROM_DEVICE_SN_2 [0xFC4B81F4] = 0x8800000B
1> ----------------------------------------------------------------------
>> QFPROM_MSA_ANTIROLLBACK_1 [0xFC4B80C8] = 0x00000000
>> QFPROM_MSA_ANTIROLLBACK_2 [0xFC4B80CC] = 0x00000000
1> ----------------------------------------------------------------------
>> [QFPROM QFuse INFO]
>> QFPROM_OEM_ID_LSB [0xFC4B80F0] = 0x00310000
>> QFPROM_OEM_ID_MSB [0xFC4B80F4] = 0x00000000
>> QFPROM_SECURE_BOOT_ENABLE_LSB [0xFC4B83F8] = 0x00202020
>> QFPROM_SECURE_BOOT_ENABLE_MSB [0xFC4B83FC] = 0x00000000
>> QFPROM_JTAG_DISABLE_LSB [0xFC4B80E8] = 0x3FC000C0
>> QFPROM_JTAG_DISABLE_MSB [0xFC4B80EC] = 0x040001FE
1> ----------------------------------------------------------------------
>> JTAG_ID [0xFC4BE0E0] = 0x107B40E1
>> OEM_ID [0xFC4BE0E4] = 0x00310000
>> SERIAL_NUM_MSB [0xFC4B81F4] = 0x8800000B
>> SERIAL_NUM_LSB [0xFC4B81F0] = 0x1256AFAE
>> [SECURITY INFO]
>> OEM_CONFIG_ROW0_LSB_ADDR [0xFC4B80E8] = 0x3FC000C0
>> OEM_CONFIG_ROW0_MSB_ADDR [0xFC4B80EC] = 0x040001FE
>> OEM_CONFIG_ROW1_LSB_ADDR [0xFC4B80F0] = 0x00310000
>> OEM_CONFIG_ROW1_MSB_ADDR [0xFC4B80F4] = 0x00000000
>> FEAT_CONFIG_ROW0_LSB_ADDR [0xFC4B80F8] = 0x00B08010
>> FEAT_CONFIG_ROW0_MSB_ADDR [0xFC4B80FC] = 0x00000000
>> FEAT_CONFIG_ROW1_LSB_ADDR [0xFC4B8100] = 0x00000001
>> FEAT_CONFIG_ROW1_MSB_ADDR [0xFC4B8104] = 0x0004785F
1> ----------------------------------------------------------------------
>> Start Address : 0xfc102140
>> End Address : 0xfc102c80
1> ----------------------------------------------------------------------
>> PBL_APPS LOG
1> ----------------------------------------------------------------------
>> PBL_LOG_COUNT=15
>> LOG_CODE :: 0xef010800 [ DECODED : 0x00010800 ]
>> TIMESTAMP :: 0x0002f50c
>> LOG_CODE :: 0xef0f0203 [ DECODED : 0x000f0203 ]
>> TIMESTAMP :: 0x0002fb8e
>> LOG_CODE :: 0xef010802 [ DECODED : 0x00010802 ]
>> TIMESTAMP :: 0x000330c9
>> LOG_CODE :: 0xef010804 [ DECODED : 0x00010804 ]
>> TIMESTAMP :: 0x0003471e
>> LOG_CODE :: 0xef010806 [ DECODED : 0x00010806 ]
>> TIMESTAMP :: 0x00034a84
>> LOG_CODE :: 0xef010808 [ DECODED : 0x00010808 ]
>> TIMESTAMP :: 0x00034b25
>> LOG_CODE :: 0xef01080a [ DECODED : 0x0001080a ]
>> TIMESTAMP :: 0x00034bae
>> LOG_CODE :: 0xef0f0300 [ DECODED : 0x000f0300 ]
>> TIMESTAMP :: 0x00034c11
>> LOG_CODE :: 0xef01080c [ DECODED : 0x0001080c ]
>> TIMESTAMP :: 0x00034c48
>> LOG_CODE :: 0xef5d0200 [ DECODED : 0x005d0200 ]
>> TIMESTAMP :: 0x00034d17
>> LOG_CODE :: 0xef5d0400 [ DECODED : 0x005d0400 ]
>> TIMESTAMP :: 0x0006f367
>> LOG_CODE :: 0xef5d0201 [ DECODED : 0x005d0201 ]
>> TIMESTAMP :: 0x0006f3bc
>> LOG_CODE :: 0xef0f0600 [ DECODED : 0x000f0600 ]
>> TIMESTAMP :: 0x0009bad1
>> LOG_CODE :: 0xef0f0500 [ DECODED : 0x000f0500 ]
>> TIMESTAMP :: 0x0714aad1
>> LOG_CODE :: 0xefa00502 [ DECODED : 0x00a00502 ]
>> TIMESTAMP :: 0x071766a9
1> ----------------------------------------------------------------------
>> < PBL DUMP LOG >
1> ----------------------------------------------------------------------
>> 1> PBL_GENERAL_LOG_FUNC_EXEC
1> PBL_FUSE_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_FUSE_FAST_BOOT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_SDCC_LOG_DETECT_PORT_ACCESS_ERR
1> PBL_SDCC_LOG_CARD_TYPE_ERR
1> PBL_SDC_LOG_DEFAULT
1> PBL_FUSE_USB_ENUM_TIMEOUT
1> PBL_FUSE_AP_SW_REV
1> PBL_AUTHENTICATION_LOG_DEFAULT
>> Logged Time : 2016-09-02 15:47:33...successfully Completed.
>> Saved Log File(LOG_LGD858HK_AHKG_HKG_20160902_154733.txt) successfully.
scamex said:
Hi, after some time searching for tools and info i have gathered a few working tools and service manuals for our belloved G3.
Here is the Service Manual Link
Here is the Smart Boot Diagnostic Tool Link
Here is the QDLoader HS-USB driver for 64bit windows pc Link
Here is the QDLoader HS-USB driver for 32bit windows pc Link
Here is the AP-CHIP dll and ATT achive for Flash Tool for use without LG B2B connection Link
Here is the LG FlashTool 1.5.10.1120 Link
Here is the Megalock .dll file to overwrite in flash tool folder for B2B nologin Link
Here is the How To Calibrate document Link
Here is a document that shows how to Flash a "dead boot" LG phone Link
Hope this will help someone or teaching others. Excuse my english and if i posted in a wrong section. Thanks !
Click to expand...
Click to collapse
Thanks. Was very usefull
this post save me multiple times;
everityme i use autoreck on a stock LG i got bulk error ecc and smartboot is the only tool that instantaneously unbrick the phone
:good:
Galaxy S6 G920F pit and branded firmwares
warning : pit can brick your dévice,so use it only if you need and with modération
please NO REDISTRIBUTION
do not copy in other forums (only XDA link)
pit files are signed so don't change the name and the download link
original pit for a G920F dévice open firmware:
ZEROFLTE_EUR_OPEN.pit :
partition--------------- ZEROFLTE.pit --- open firmware----- ILO firmware
p01: BOTA0 :--------------- 1 024
p02: BOTA1 : ---------------1 024
p03: efs.img :-------------- 5 120
p04: param.bin :-----------2 048
p05: boot.img :-------------7 168-------- 27 141ko
p06: recovery.img :-------8 704-------- 29 939ko
p07: OTA:------------------2 048
p08: modem.bin----------10 752-------- 39 065ko
p09: tombstones.img :----- 256
p10: dtn.ssw :--------------- 256
p11: PERSISTENT :------------192
p12: STEADY :----------------64
p13: persdata.img---------2 304
p14: SBFS :----------------3 840
p15: system.img :------ 947 200-------- 3 415 466ko
p16: cache.img :---------51 200---------- 27 645Ko--------- 40 869Ko
p17: hidden.img : -------- 2 560----------- 7 637Ko--------- 86 805Ko
p18: userdata.img :
by according @Hero, thread (thanks to him )
http://forum.xda-developers.com/galaxy-s6/development/dev-galaxy-s6-partition-table-t3081510
we must multiply by 4 , block count to converte in KB(b) .this new résult is lower than nine but don't change the partition (hidden and cache )
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
8 0 31240192 sda
8 1 4096 sda1
8 2 4096 sda2
8 3 20480 sda3
8 4 8192 sda4
8 5 28672 sda5
8 6 34816 sda6
8 7 8192 sda7
8 8 43008 sda8
8 9 1024 sda9
8 10 1024 sda10
8 11 768 sda11
8 12 256 sda12
8 13 9216 sda13
8 14 15360 sda14
8 15 3788800 sda15
259 0 204800 sda16
259 1 66560 sda17
259 2 26992640 sda18
8 16 4096 sdb
8 32 4096 sdc
253 0 1048576 vnswap0
for SM-G920F
ZEROFLTE_EUR_OPEN.pit : hidden (2560) 10 240KB cache: (51200) 204 800KB
https://1fichier.com/?olsab05qni
https://drive.google.com/file/d/0BzyeAt2hy6XeZHQ4bUpvbUtCLVk/view?usp=sharing
for branded or some open firmwares we need a higher hidden partition
ZEROFLTE-HIDDEN50.pit: hidden 51 200KB cache: 204 800KB
https://1fichier.com/?q88fz08nvy
https://drive.google.com/file/d/0BzyeAt2hy6XeVFdkdEFzdTBZOE0/view?usp=sharing
ZEROFLTE-HIDDEN100.pit: hidden 102 400KB cache: 204 800KB
https://1fichier.com/?ts1f3nb3nr
this pit size have been test bymrij (thank to him) with OJK firmware
http://www.sammobile.com/forum/showthread.php?t=26998
ZEROFLTE-HIDDEN150m.pit hidden 153 600KB cache: 204 800KB
https://1fichier.com/?c7wwmuqzc6
https://drive.google.com/file/d/0BzyeAt2hy6XeUWlaaTJjek1kOEk/view?usp=sharing
" magic pit " is:
ZEROFLTE_EUR_OPEN-HIDDEN250.pit:
https://1fichier.com/?4f8y7tvinm
https://drive.google.com/file/d/0BzyeAt2hy6XeVS1oZmdEbXkxMVE/view?usp=sharing
SM-G920F TEF multi CSC (O2U VIA XEC ) pit file
ZEROFLTE_EUR_OPEN_HIDDEN300M
https://drive.google.com/file/d/0BzyeAt2hy6XeUElrOFo0Tm15cHc/view?usp=sharing
other SM-G920
SM-G920A ATT
ZEROFLTE_USA_ATT.pit
https://drive.google.com/file/d/0BzyeAt2hy6XebTRUZERQODVpUGs/view?usp=sharing
SM-G920AZ AIO
ZEROFLTE_USA_ATT.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeSTY1VTJEbDY0NUU/view?usp=sharing
SM-G920F EVR
ZEROFLTE_EUR_OPEN_HIDDEN150M
https://drive.google.com/file/d/0BzyeAt2hy6XebWpHX0Vxb2phOWc/view?usp=sharing
SM-G920F TEF
ZEROFLTE_EUR_OPEN_HIDDEN300M
https://drive.google.com/file/d/0BzyeAt2hy6XeUElrOFo0Tm15cHc/view?usp=sharing
SM-G920F TIM
ZEROFLTE_EUR_OPEN_HIDDEN200M
https://drive.google.com/file/d/0BzyeAt2hy6XeT3ZCeDB0R0p0UWc/view?usp=sharing
SM-G920I ODD multi CSC ( BNG INS INU NPL SLK )
ZEROFLTE_AUS_XSA.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeZHZBYUtXYlc1NXM/view?usp=sharing
SM-G920P SPR
ZEROFLTE_USA_SPR.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeY3pDNXBhVUZodFk/view?usp=sharing
SM-G920R4 USC
ZEROFLTE_USA_USC.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeeFVmSjc3RVgtOEE/view?usp=sharing
SM-G920T TMO
ZEROFLTE_USA_TMO.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeRmRyd0Zqd0IyUVk/view?usp=sharing
SM-G920T1 TMO
ZEROFLTE_USA_TMO.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeaTZqejZVUEVudWs/view?usp=sharing
SM-G920V pit:
ZEROFLTE_USA_VZW
https://drive.google.com/file/d/0BzyeAt2hy6XeQlJ0a1BRSWxzckE/view?usp=sharing
SM-G920W8 OYA multi CSC ( BMC BWA ESK FMC GLW KDO MTA RWC TLS VMC VTR )
ZEROFLTE_CAN_BMC.pit
https://drive.google.com/file/d/0BzyeAt2hy6XebncxRl9MTGw4eTg/view?usp=sharing
SM- G9200 CHC pit:
ZEROFLTE_CHN_OPEN (G9200).pit
https://drive.google.com/file/d/0BzyeAt2hy6XeRVZFZGZxaGZuc1U/view?usp=sharing
SM-G9200 TGY pit:
ZEROFLTE_CHN_HK.pit
https://drive.google.com/file/d/0BzyeAt2hy6XeZ3pVMHRJWG5IdHM/view?usp=sharing
SM-G9208 BRI
ZEROFLTE_CHN_TW.pit
https://drive.google.com/file/d/0BzyeAt2hy6Xed0dLR21ucWd1Vmc/view?usp=sharing
SM-G9208 CHC
ZEROFLTE_CHN_CMCC (G9208).pit
https://drive.google.com/file/d/0BzyeAt2hy6XeZFlDQUliaVRaUWs/view?usp=sharing
regards , and don't forget the thanks button , it's free .
galaxy S6 G920F hidden and cache size list for pit:
OXA OE3 : hidden.img:___7 637Ko cache:_27 645Ko__ZEROFLTE_EUR_OPEN.pit
AMO OD9 : hidden.img:___9 409Ko cache:_11 353Ko__hidden250 OK
ATO OE3 : hidden.img:__19 989Ko cache:_10 681Ko__hidden100 ok
AUT OE3 : hidden.img:__22 653Ko cache:_14 925Ko__hidden100 ok
BOG OD9 : hidden.img:__30 337Ko cache:_10 981Ko__hidden250 OK
COS OCV : hidden.img:_182 461Ko cache:_10 093Ko__hidden250 OK
CYO OE3 ; hidden.img:___7 553Ko cache:_35 901Ko__hidden250 OK
DBT OE3 : hidden.img:__31 533Ko cache:_10 817Ko__hidden100 ok
DPL OFD : hidden.img:_134 669Ko cache:_20 865Ko__hidden250 OK
DHR OFD : hidden.img:_155 037Ko cache:_11 841Ko__hidden240 original
DNL OCV : hidden.img:_113 201Ko cache:_11 685Ko__hidden250 OK
DRE OCV : hidden.img:__21 877Ko cache:_35 733Ko__hidden60 original
DTM OCV : hidden.img:_176 637Ko cache:_22 313Ko__hidden250 OK
EVR OCY : hidden.img:__27 309Ko cache:_20 565Ko__hidden250 ok
FTM OCV : hidden.img:__63 385Ko cache:_18 085Ko__hidden250 ok
GLB ODI : hidden.img:__71 765Ko cache:_68 197Ko__hidden100 ok
H3G OCV : hidden.img:__31 405Ko cache:_14 069Ko__hidden100 ok
HTS OCV : hidden.img:__40 321Ko cache:_19 473Ko__hidden60 original
HUI OCV : hidden.img:__39 689Ko cache:_13 221Ko__hidden100 ok
IDE OD9 : hidden.img:__52 969Ko cache:_16 061Ko__hidden250 original
ILO OD4 : hidden.img:__86 805Ko cache:_40 869Ko__hidden100 ok tanks to omrij
LUX OCV : hidden.img:___7 553Ko cache:_14 837Ko
MAX OCV : hidden.img:_142 713Ko cache:_23 693Ko__hidden240 original
MEO OCV : hidden.img:__26 021Ko cache:_15 077Ko__hidden50 original
MOT OE3 : hidden.img:__57 573Ko cache:_19 593Ko__hidden100 ok
NEE : hidden.img:__16 745Ko cache:_17 772Ko__hidden50 original
OJV OD4 : hidden.img:__93 750Ko cache:_50 121Ko__hidden150 ok
O2C OE3 : hidden.img:__23 845Ko cache:_14 877Ko__hidden100 ok
PAN OE3 : hidden.img:__71 105Ko cache:_10 603Ko__hidden100 original
PHE OE3 : hidden.img:__48 845Ko cache:_10 413Ko__hidden100 ok
PHN OE3 : hidden.img:__15 329Ko cache:_10 581Ko__hidden50 ok
SEK OD5 : hidden.img:__19 157Ko cache:_29 557Ko__hidden100 ok
SER ODE : hidden.img:__19 157Ko cache:_29 747Ko__hidden100 ok
SFR OCV : hidden.img:___7 753Ko cache:_16 681Ko__hidden100 ok
TEN OE3 : hidden.img:__38 197Ko cache:_16 905Ko__hidden100 ok
TIM OCV : hidden.img:_119 341Ko cache:_11 021Ko__hidden250 ok
TMT : hidden.img;_126 409Ko cache:_11 201Ko__hidden240 original
TMZ : hidden.img:__59 425Ko cache:_11 381Ko__hidden240 original
TPD OE3 : hidden.img:__15 329Ko cache:_10 581Ko__hidden100 ok
SWC OCZ : hidden.img:_148 726Ko cache:_56 977Ko__hidden250 ok
VDS OE3 : didden.img:__27 809Ko cache:_16 905Ko__hidden100 ok
VIA OCV : hidden.img:_197 885Ko cache:_50 153Ko__hidden300 ok
XEG OCV : hidden.img:__44 469Ko cache:_11 725Ko__hidden60 original
VVT OE3 : hidden.img:__11 245Ko cache;_10 473Ko__hidden100 ok
WIN OCV : hidden.img:__49 457Ko cache:_10 669Ko__hidden100 ok
3IE OCV : hidden.img:__20 929Ko cache;_11 721Ko__hidden100 ok
ZEROFLTE_EUR_OPEN.pit :___________hidden 10 240KB cache: 204 800KB
ZEROFLTE_EUR_OPEN-HIDDEN100.pit:__hidden 102 400KB cache: 204 800KB
ZEROFLTE_EUR_OPEN-HIDDEN150.pit:__hidden 153 600KB cache: 204 800KB
ZEROFLTE_EUR_OPEN-HIDDEN250.pit:__hidden 256 000KB cache: 204 800KB
ZEROFLTE_EUR_OPEN-HIDDEN300.pit:__hidden 307 200KB cache: 204 800KB
-CYO same firmware for BGL CYO ETL MET MSR ORX ROM SEB SEE SIO TEB TOP TPH TSR TWO XEH XEO
-DAX same firmware for MAX TRG TTR
-DHX same firmware for CRO DHR
-DNL same firmware for DNL TNL
-DPL same firmware for DPL TPL
-DTM same firmware for DTM DDE
-GLB same firmware for CAM GLB SMA THL XID XME XSE XTC XTE XXV
-ILO same firmware for CEL ILO PCL PTR
-OJV same firmware for ACR AFG AFR BTC ECT EGY FWD KEN KSA LEB LYS MAT MID MRU MTZ MWD PAK THR TMC TRC TUN TUR WTL XFA XFE XFM XFN XFU XSG
-OXA same firmware for BTU CPW DBT ITV KOR NEE XEF XEO
-SER same firmware for CAC CAU SEK SER SKZ
-SWC same firmware for ATL AVF CNX CYV MOB MTL OMN MTL OMN SIM SWC TCL VD2 VDC VDF VDH VDI VGR VIP VOD
-VIA same firmware for O2U VIA XEC
regards
S6 G920F ODIN V3.10.6
don't forget to save all your data
with a stock or branded firmware , flash the one file ( md5 ) firmware in AP case
{
"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"
}
with a 4 files firmware:
the répartition is automatic with the pit file (in the CSC ) so you will loose all your data
you can flash the pit file alone :
select pit case (1)
ok(2)
click pit case (3) choose your pit file
click start (4)
you also will loose all your data
downgrading firmware ( only from 5.0.2 to 5.0.2 and never from 5.1 to 5.0.2 )
you can downgrade but after the keyboard will not work .
1-power off the device ,
2- power on in recovery mode for wiping cache partition and data/factory reset
http://wgnszoz9s1.1fichier.com/
3- reboot your device
with the ZEROFLTE_EUR_OPEN-HIDDEN100.pit you will have this repartition:
if you want to see your partition like this image (with rooted or unrooted device)
install an explorer app ( https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=fr )
and open: proc/partitions (open as: text file / RB Text Editor )
regards
Im sorry but what is the benefit of this?
i own the sprint version g920p
by according @Hero, thread (thanks to him )
http://forum.xda-developers.com/galaxy-s6/development/dev-galaxy-s6-partition-table-t3081510
i've change post1
@ Ntress:
if your original dévice was sold with an open firmware you can't change and download a branded firmware without changing pit file
(ODIN failed at hidden.img )
http://www.sammobile.com/forum/showthread.php?t=27055&p=118525#post118525
for G920P don't use these pit files they are only for G920F and maybe you need another table partition
exemple with G920V
partition name : ZEROFLTE_USA_VZW.pit
p01: BOTA0 :--------------- 1 024
p02: BOTA1 : ---------------1 024
p03: efs.img :-------------- 5 120
p04: m9kefs1.bin :---------1*024
p05: m9kefs2.bin :---------1*024
p06: m9kefs3.bin :---------1*024
p07: param.bin:------------2 048
p08: boot.bin--------------7*168
p09 :recovery.img---------8*704
p10: OTA-------------------2*048
p11: modem.bin-----------19*456
p12: tombstones.img :----- 256
p13: dtn.ssw :--------------- 256
p14: PERSISTENT :------------192
p15: STEADY :----------------64
p16: persdata.img---------2 304
p17: SBFS :----------------3 840
p18: system.img :------ 1*121*280
p19: cache.img :---------262*144
p20: carrier.img : -------- 3*840
p21: userdata.img :
regards
@ Ntress:
for G920P ZEROFLTE_USA_SPR.pit https://1fichier.com/?ns0zyi2rdi
partition name : ZEROFLTE_USA_SPR.pit
p01: BOTA0 :--------------- 1 024
p02: BOTA1 : ---------------1 024
p03: efs.img :-------------- 5 120
p04: m9kefs1.bin :---------1 024
p05: m9kefs2.bin :---------1 024
p06: m9kefs3.bin :---------1 024
p07: param.bin:------------2 048
p08: boot.bin--------------7 168
p09: recovery.img---------8 704
p10: OTA-------------------2 048
p11: modem.bin-----------19 456
p12: tombstones.img :----- 256
p13: dtn.ssw :--------------- 256
p14: PERSISTENT :------------192
p15: STEADY :----------------64
p16: persdata.img---------2 304
p17: SBFS :----------------3 840
p18: system.img :------ 957 440
p19: cache.img :---------76 800
p20: carrier.img : -------- 11 520
p21: userdata.img :
HIDDEN partition only contains the carrier bloatware anyway so none of it's contents is needed at all if you don't want the crappy preloaded stuff.
Downloads not work!
@jonchliu
branded firmwares : you can find carrier app and games in hidden partition
@dajumper
after control ,downloads are working :
regards
Re-Partition operation failed
Failed tried to partition with ZEROFLTE_EUR_OPEN-sb.pit to prepare for EVR ROM
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
@inkstripe
have you try with ODIN V3.10.6
in first flash only pit file and do not tick auto reboot
and after flash full firmware and pit file with auto reboot select
regards
Yes, I'm trying pit file on it's own and with 3.10.6
yakapa40 said:
@inkstripe
have you try with ODIN V3.10.6
in first flash only pit file and do not tick auto reboot
and after flash full firmware and pit file with auto reboot select
regards
Click to expand...
Click to collapse
Hi.
My rom is : OJV OD4 : hidden.img:__93 750Ko cache:_50 121Ko
Could you help me which pit file should i download?
I really need this. @yakapa40
@inkstripe
Pit file worked fine, however the G920FXXU1AOCY_G920FEVR1AOC1_G920FXXU1AOCW_HOME.tar .md5 didn't succeed with hidden.img fail
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so i don't understand why hidden failed
@amirkard
My rom is : OJV OD4 : hidden.img:__93 750Ko cache:_50 121Ko
you can try with:
ZEROFLTE_EUR_OPEN-sb225.pit:______hidden 204 800KB cache: 82 400KB
regards
yakapa40 said:
@inkstripe
Pit file worked fine, however the G920FXXU1AOCY_G920FEVR1AOC1_G920FXXU1AOCW_HOME.tar .md5 didn't succeed with hidden.img fail
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so i don't understand why hidden failed
Click to expand...
Click to collapse
How can I confirm if the pit file worked?
@inkstripe
http://forum.xda-developers.com/galaxy-s6/help/firmware-pit-file-t3116540
and
http://www.sammobile.com/forum/showthread.php?t=26998&p=118348#post118348
regards
@yakapa40
Pit didn't work for me
Odin 3.10.6 failed at pit
amirkard said:
@yakapa40
Pit didn't work for me
Odin 3.10.6 failed at pit
Click to expand...
Click to collapse
hello
please if you want help i need more infos:
which firmware do you try to download ?
whitch pit file ?
where have you put the pit file in ODIN ?
i think with ODIN 3.10.6 and G920 you need to flash the pit file with the 4 files firmware (pit file in the CSC)
regards
Still no joy with EVR hidden.img
Hi,
I'm struggling to put EVR ROM failing at hidden.img. Have tried all the pit files in this thread but no luck. Some of the pit files actually fails in odin. I have tried putting pit inside CSC with no luck.
ZEROFLTE_EUR_OPEN-sb.pit file fails in ODIN
however
ZEROFLTE_EUR_OPEN_HIDDEN100M.pit does NOT fail in Odin. But either way I can't put EVR hidden.img.
I am now trying to find out why ZEROFLTE_EUR_OPEN-sb.pit fails in odin. I compared the two pit files and noticed a difference in block size
Entry Memory Address: 0xA6C
ZEROFLTE_EUR_OPEN-sb.pit
Block Size: 1,024,224
Block Count: 22,560
ZEROFLTE_EUR_OPEN_HIDDEN100M.pit
Block Size: 1,044,224
Block Count: 25,600
Does anyone know
1. Why ZEROFLTE_EUR_OPEN-sb.pit fails in Odin? Has anyone been able to use this file?
2. Block sizes are different between the two? I can understand block count should be different.
3. Why ZEROFLTE_EUR_OPEN_HIDDEN100M.pit says successful in Odin however it still fails with hidden.img (27k)
4. Anyway of checking partition layout on my S6? I don't have root unfortunately.
Any help appreciated
i've worked on G920F for helping omrij
the new pit size have been test by: omrij (thank to him)
http://www.sammobile.com/forum/showthread.php?t=26998
i've post this thread in first in development section and at this time i don't know why not working for all the G920F
i'm working on this problem to see what Samsung have changed with S6 device but if you only post don't work it's very hard for me to find a solution
i need more infos
regards
How to backup stockRom S5 before starting to follow any instructions to root + flash + LineageOS ...
What I want:
* backup my brand new stock ROM Galaxy S5 SM-G900F
* before I even start with TWRP, root, etc.
* with an apk, via USB on a PC ... any way that would work
* or if total backup does not exist, then at least the EFS partitions?
because:
* I might want to sell it later
* I might have to send it back
* flashing TWRP & LineageOS might fail
* I have lost mobileInternet on an LG-V20 already because something went strange when flashing
* I am careful
Is there any way to backup a Samsung S5 before I even start with following any instructions here?
Am I asking for something impossible?
Was I on the right way already (see below), but have done something wrong?
Is it perhaps only possible after rooting? If so, then which tool do you recommend then?
Thanks a lot!
What I have tried:
* xda developer galaxy-s5/general every thread title until page 5 https://forum.xda-developers.com/galaxy-s5/general/page5
* xda developer search for "S5 backup", "S5 EFS", and a few other searches. Sorry for being dumb, please help me search, thanks.
* Heimdall PIT, but "ERROR: Failed to send request to end PIT file transfer!"
* Odin PIT, but "Can't open the specified file. (Line: 1892)"
* Samsung Tool 5.0 com.sec.ricky310711.samsungtool.apk https://forum.xda-developers.com/showthread.php?t=2696153 but the app-->Backup-EFS hangs at "Please Wait..." <-- probably because I could not install busybox because no root yet.
* manual EFS backup with dd https://forum.xda-developers.com/showthread.php?t=2737448 but I get a "su: not found", obviously, because unrooted
Code:
Heimdall v1.4.0
...
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 0 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone?
ankade said:
Anyone?
Click to expand...
Click to collapse
Though, I don't have your specific variant, the typical "just in case" files (that I personally always begin with) to obtain are the following:
1) Stock Firmware File (I just go with the latest and sometimes the 1 previously released).
2) Latest Odin PC Software.
3) Latest Samsung USB Drivers for the PC.
4) PIT file (PIT = Partition Information Table).
Those are usually the bare essentials that I begin with.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
Great, thanks a lot. That is a helpful list.
Ibuprophen said:
2) Latest Odin PC Software.
Click to expand...
Click to collapse
Which is the latest you are using? The version "Odin3-v3.13.1" does NOT work, see above.
How exactly do I extract the current state of my (still unrooted) SM-G900F ?
Thanks.
I have now tried again manually:
Code:
heimdall download-pit --output s5.pit
Is that the right command?
It only worked after overwriting the MSM8960 driver with zadig.exe
Then it looks like this:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
then after a while:
Code:
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
heimdall 1.4.2
Hooray, big progress. It was a version problem, older versions of heimdall seem faulty. And grrrmpf: the "heimdall" website which comes up at the top on search engines ... provides an outdated 1.4.0 version. Which seems broken. But hooray, the 1.4.2 version of heimdall works:
this looks good, no?
Code:
cd heimdall_1.4.2_win64
heimdall print-pit --no-reboot
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is encouraged.
If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Code:
Entry Count: 30
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
Unknown 7: 0
Unknown 8: 0
now there are 30 such entries:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 30720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:
I got the new heimdall 1.4.2 version from here:
https://github.com/Benjamin-Dobell/Heimdall/issues/295#issuecomment-364729538
and because he only provides the source, the binary from here
https://github.com/tothphu/heimdall_build/
this worked too:
Code:
heimdall download-pit --no-reboot --output S5-download-pit.pit
It resulted in a non-human-readable binary file of 8192 bytes.
But:
How to backup partitions?
with
Code:
heimdall --help
I can see that there I can flash ONTO the device with e.g.
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-klte.img --no-reboot
but there does not seem to be a
Code:
heimdall read --RECOVERY --file recovery.img --no-reboot
?
how to READ a partition FROM the device?
?
Now I have tried it via USB debugging, with "minimal_adb_fastboot_1.4.3_portable.zip"
but
Code:
adb shell
ls -al /dev/block/platform/msm_sdcc.1/by-name/efs
lrwxrwxrwx root root 2014-05-24 16:36 efs -> /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/storage/3164-3234/S5/efs.img
results in
Code:
dd: /dev/block/mmcblk0p12: Permission denied
and
Code:
su -
/system/bin/sh: su: not found
so it looks as if my first hope has to be declared dead ...
No system backup without root, right?
?
But what I don't understand ... How did people extract these here then: https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/ ???
I have found instructions how to get back to stock rom, but I would like to use my own original stockROM for that. But I don't know how to back it up. Please help. Thanks.
how to root?
The phone is this one:
Samsung S5
SM-G900F
Android version 6.0.1
Android security patch level: 1 January 2017
I have tried these root tools:
Kingroot (NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk) --> "Generating adaptation strategy, please come back later"
Towelroot v1.0 (tr.apk) --> "This phone isn't currently supported"
I did not want to try CF-Auto-Root because it says "If you have a Samsung-KNOX-enabled device, this package will trip the KNOX warranty flag. This flag cannot be reset, and will prevent some applications from working."
Is there really no way to get root without first installing TWRP ?
?
Hello Xda Experts,
I own LG D855. on fulmics MM rom. it started freezing and hanging so in TWRP i cleard cache and dalvik cache. after boot it freeze on boot logo.
so i decided to flash rom again by twrp. but i unable to do so. because its giving error failed to mout internal storage system etc...
download mode was showing but after 10 secs blank screen.
After that i decided to do hard brick method by board diag. after 9008 mode. i got AP: passed Emmc: failed
Failed to open partition from EMMC.
now i cant boot in twrp nothing. totally dead. no logo.
here is lg smart boot log:
>> ---------------------------- Start Logging ----------------------------
>> USB Status : Qualcomm HS-USB QDLoader 9008 (COM14)
>> Ready to access the target board...
>> BootLoader File : All EU Global_XXXX_XXXX.mbn
>> 1. Model : All EU Global , 2. Suffix : XXXX , 3. Operator : XXXX
>> Bootloader : All EU Global_XXXX_XXXX.mbn
>> AP Chip : MSM8974_G3 , BootLoader : All EU Global_XXXX_XXXX.mbn
>> Trying Connection To Device with sahara protocol for AP Chip.
>> Successfully Connection To Device with sahara protocol for AP Chip.
>> connected with Sahara Protocol successfully.
>> Loading flash to SYS_IMEM.
>> Loading 0 Kbytes to SYS_IMEM.
>> Loading 4 Kbytes to SYS_IMEM.
>> Loading 8 Kbytes to SYS_IMEM.
>> Loading 12 Kbytes to SYS_IMEM.
>> Loading 16 Kbytes to SYS_IMEM.
>> Loading 20 Kbytes to SYS_IMEM.
>> Loading 24 Kbytes to SYS_IMEM.
>> Loading 28 Kbytes to SYS_IMEM.
>> Loading 32 Kbytes to SYS_IMEM.
>> Loading 36 Kbytes to SYS_IMEM.
>> Loading 40 Kbytes to SYS_IMEM.
>> Loading 44 Kbytes to SYS_IMEM.
>> Loading 45 Kbytes to SYS_IMEM.
>> Successfully Loaded to SYS_IMEM.(Total 45 Kbytes)
>> Flash Image was normally loaded to SYS_IMEM.
>> Checking for device status.
>> [Verifying Hello Protocol]
>> Sending Hello request 0 time(s).
>> SendSync EHOST_HELLO_RSP OK.
>> Hello Response OK.
>> Got Hello response for Hello request.
>> [Verifying Security Protocol]
>> Security Response OK.
>> Connected to flash bootloader.
1> ----------------------------------------------------------------------
>> PBL SOFTWARE HISTORY
1> ----------------------------------------------------------------------
>> 1.Smart Boot Diagnosis Tool v1.3.1 <Analysis Tool for Booting failure>
>> 2.PBL_VERSION_NUMBER [fc021834] = 1c6c6162
1> ----------------------------------------------------------------------
1> ----------------------------------------------------------------------
>> SECURE_BOOT_INFORMATION
1> ----------------------------------------------------------------------
>> [QFPROM - AP Anti-rollback Region of OEM Region ]
>> QFPROM_AP_ANTIROLLBACK_1 [0xFC4B80B8] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_2 [0xFC4B80BC] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_3 [0xFC4B80C0] = 0x00000000
>> QFPROM_AP_ANTIROLLBACK_4 [0xFC4B80C4] = 0x00000000
1> ----------------------------------------------------------------------
>> QFPROM_DEVICE_SN_1 [0xFC4B81F0] = 0x0FF90131
>> QFPROM_DEVICE_SN_2 [0xFC4B81F4] = 0x8800000B
1> ----------------------------------------------------------------------
>> QFPROM_MSA_ANTIROLLBACK_1 [0xFC4B80C8] = 0x00000000
>> QFPROM_MSA_ANTIROLLBACK_2 [0xFC4B80CC] = 0x00000000
1> ----------------------------------------------------------------------
>> [QFPROM QFuse INFO]
>> QFPROM_OEM_ID_LSB [0xFC4B80F0] = 0x00310000
>> QFPROM_OEM_ID_MSB [0xFC4B80F4] = 0x00000000
>> QFPROM_SECURE_BOOT_ENABLE_LSB [0xFC4B83F8] = 0x00202020
>> QFPROM_SECURE_BOOT_ENABLE_MSB [0xFC4B83FC] = 0x00000000
>> QFPROM_JTAG_DISABLE_LSB [0xFC4B80E8] = 0x3FC000C0
>> QFPROM_JTAG_DISABLE_MSB [0xFC4B80EC] = 0x040001FE
1> ----------------------------------------------------------------------
>> JTAG_ID [0xFC4BE0E0] = 0x107B40E1
>> OEM_ID [0xFC4BE0E4] = 0x00310000
>> SERIAL_NUM_MSB [0xFC4B81F4] = 0x8800000B
>> SERIAL_NUM_LSB [0xFC4B81F0] = 0x0FF90131
>> [SECURITY INFO]
>> OEM_CONFIG_ROW0_LSB_ADDR [0xFC4B80E8] = 0x3FC000C0
>> OEM_CONFIG_ROW0_MSB_ADDR [0xFC4B80EC] = 0x040001FE
>> OEM_CONFIG_ROW1_LSB_ADDR [0xFC4B80F0] = 0x00310000
>> OEM_CONFIG_ROW1_MSB_ADDR [0xFC4B80F4] = 0x00000000
>> FEAT_CONFIG_ROW0_LSB_ADDR [0xFC4B80F8] = 0x00B08010
>> FEAT_CONFIG_ROW0_MSB_ADDR [0xFC4B80FC] = 0x00000000
>> FEAT_CONFIG_ROW1_LSB_ADDR [0xFC4B8100] = 0x00000001
>> FEAT_CONFIG_ROW1_MSB_ADDR [0xFC4B8104] = 0x0004785F
1> ----------------------------------------------------------------------
>> Start Address : 0xfc102140
>> End Address : 0xfc102c80
1> ----------------------------------------------------------------------
>> PBL_APPS LOG
1> ----------------------------------------------------------------------
>> PBL_LOG_COUNT=11
>> LOG_CODE :: 0xef010800 [ DECODED : 0x00010800 ]
>> TIMESTAMP :: 0x0002bea8
>> LOG_CODE :: 0xef0f0203 [ DECODED : 0x000f0203 ]
>> TIMESTAMP :: 0x0002c53e
>> LOG_CODE :: 0xef010802 [ DECODED : 0x00010802 ]
>> TIMESTAMP :: 0x0002fa67
>> LOG_CODE :: 0xef010804 [ DECODED : 0x00010804 ]
>> TIMESTAMP :: 0x000310b6
>> LOG_CODE :: 0xef010806 [ DECODED : 0x00010806 ]
>> TIMESTAMP :: 0x000313ff
>> LOG_CODE :: 0xef010808 [ DECODED : 0x00010808 ]
>> TIMESTAMP :: 0x000314a0
>> LOG_CODE :: 0xef01080a [ DECODED : 0x0001080a ]
>> TIMESTAMP :: 0x00031515
>> LOG_CODE :: 0xef01080c [ DECODED : 0x0001080c ]
>> TIMESTAMP :: 0x0003155c
>> LOG_CODE :: 0xef0f0600 [ DECODED : 0x000f0600 ]
>> TIMESTAMP :: 0x00044c53
>> LOG_CODE :: 0xef0f0500 [ DECODED : 0x000f0500 ]
>> TIMESTAMP :: 0x08084edd
>> LOG_CODE :: 0xefa00502 [ DECODED : 0x00a00502 ]
>> TIMESTAMP :: 0x080b0add
1> ----------------------------------------------------------------------
>> < PBL DUMP LOG >
1> ----------------------------------------------------------------------
>> 1> PBL_GENERAL_LOG_FUNC_EXEC
1> PBL_FUSE_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_GENERAL_LOG_DEFAULT
1> PBL_FUSE_USB_ENUM_TIMEOUT
1> PBL_FUSE_AP_SW_REV
1> PBL_AUTHENTICATION_LOG_DEFAULT
>> Logged Time : 2020-08-03 01:47:06...successfully Completed.
>> Saved Log File(LOG_All EU Global_XXXX_XXXX_20200803_014706.txt) successfully.
Please HELP ME Properly in this. what i do now?