Motorola Droid Turbo 2 Google FRP Lock Bypass - Droid Turbo 2 General
Here is a Video on how to bypass the setup wizard and enable usb debugging.
https://www.youtube.com/watch?v=VYU-Fs_lJ1c
Bro my droid turbo doesn't have developer options enabled! build number is locked!
its April security patch level.. plzz help
skyrio said:
Bro my droid turbo doesn't have developer options enabled! build number is locked!
its April security patch level.. plzz help
Click to expand...
Click to collapse
this is as far as i have gotten on the Droid Turbo 2
Tomsgt said:
this is as far as i have gotten on the Droid Turbo 2
Click to expand...
Click to collapse
Thank you so much bro for video..
but i already know this method.. this is not a completely bypass and one more thing in this method calling not working at all. you can call someone easily but you cant receive call.. it says the operator is busy.. any way to bypass account completely?
Thank You
skyrio said:
Thank you so much bro for video..
but i already know this method.. this is not a completely bypass and one more thing in this method calling not working at all. you can call someone easily but you cant receive call.. it says the operator is busy.. any way to bypass account completely?
Thank You
Click to expand...
Click to collapse
ok i have a full FRP bypass for this device coming really soon editing the video now
Tomsgt said:
ok i have a full FRP bypass for this device coming really soon editing the video now
Click to expand...
Click to collapse
Thanks a bunch Sir <3 Thanks alot will try this on my phone..
skyrio said:
Thanks a bunch Sir <3 Thanks alot will try this on my phone..
Click to expand...
Click to collapse
let me know how it works for you
Tomsgt said:
let me know how it works for you
Click to expand...
Click to collapse
sir i tried this method on moto x 2nd generation.. but encrypt phone button is locked in test dpc. even battery is 80% charged. what should i do? Sorry for disturbing you!
{
"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"
}
Sir it doesnt showing device owners option..
Sent from my SM-G900T using XDA-Developers mobile app
potential clue?
1. enter bootloader/fastboot by holding vol down before and while inserting USB cable with data connection
2. boot in "factory mode"
3. only in factory mode will RSD lite show a phone when booted into the full system interface.
booting in other modes renders this grid empty usually
4. when I initiate an image flash while booted in factory mode, I see a bunch of processes terminate "app has stopped" errors quickly flash on the phone screen while RSD lite says "rebooting into flash mode" ....
5. so this is where I pass it on to everyone else. as far as I knew, the only way to send reboot commands to the phone was via ADB. RSD lite seems to have some kind of magical ADB-ish command that it is sending to the phone in order to reboot it. would it be possible to wireshark that data and look at it?
for me this is the main block ... no matter how many times I hit "build number" I do not get the familiar developer mode message when using the workarounds in the youtube videos
Hello, ive been reading about bootloader unlocking and rooting. I was able to enable developer settings and enable USB debugging. Is anyone else trying to get this phone unlocked with me? I hope not, so if u have any opinions or suggestions let them out!! ?
anyone have try this methode on new update firmware ?
Android Security Patch Level : May 1, 2016
System Version : 24.14.16. Kinzie_verzon.verizon.en.US
Build number : MCK24.78-13.16
henhida said:
anyone have try this methode on new update firmware ?
Android Security Patch Level : May 1, 2016
System Version : 24.14.16. Kinzie_verzon.verizon.en.US
Build number : MCK24.78-13.16
Click to expand...
Click to collapse
That Solution Not Working On New Secuirty Patch !
I have motorola droid turbo xt1254 with google id lock and when i am trying to tap on build number for unlocking developer option, nothing happens ((, can anyone halp me?
Thanks in advance
Hello all. I been seeing good deals on ebay for the turbo 2. Find one for $160 but it's Google locked. I have the factory Motorola cable. Will that help do anything in resetting to phone in RSS lite or do you need to boot in factory? Would like to pick this phone up and save $50 or more from buying one that is not.
umairabubakkar said:
pwrdbykyank said:
Here is a Video on how to bypass the setup wizard and enable usb debugging.
Here is new Method of Motorola Droid Turbo XT1254 FRP Solution
http://www.lahoremobile.net/motorola-droid-turbo-xt1254-frp.html
Click to expand...
Click to collapse
the web site it's showing the wrong command lines
INCORRECT: content insert -uri content://settings/secure -bind name:s:user_setup_complete -bind value:s:1
CORRECT: content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
it work for me with on
motorola droid turbo xt1254 (verizon)
android 5. 1 / su4tl-49 /version: 23.21.49 / f14.mot.xt1254.0
security pacht: 2016-04-01
Click to expand...
Click to collapse
Thank you so mouch for me help sir
Gurrumichi said:
umairabubakkar said:
the web site it's showing the wrong command lines
INCORRECT: content insert -uri content://settings/secure -bind name:s:user_setup_complete -bind value:s:1
CORRECT: content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
it work for me with on
motorola droid turbo xt1254 (verizon)
android 5. 1 / su4tl-49 /version: 23.21.49 / f14.mot.xt1254.0
security pacht: 2016-04-01
Click to expand...
Click to collapse
Yes he is absolutely right i have done and posted all detail how to root Motorola droid turbo with latest security and how to bypass google account on my blog post. I have also uploaded apps to my server and given direct links. i am unable to post link so please copy and paste give link to your browser.
pakfones.com/motorola-droid-turbo-google-account-bypass-new-security-2016/
Click to expand...
Click to collapse
Successed wipe FRP in hardstyle way. Pull off eMMC from PCB and soldered back. Logs here :
Code:
Z3X EasyJtag Software ver. 2.4.1.1
Loading eMMC Addon Firmware... IO: 1800 mV
Box S/N: 1414FD121D756485, ,FW Ver.: 01.56
CMD Pullup Level:1175 mV
CMD Active Level:1515 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
HiPower mode is off!
---------- eMMC Device Information ----------
EMMC CID : 11010030333247373200B36CDA6E924E
EMMC CSD : D02700320F5903FFFFFFFFE78640009A
EMMC Manufacturer ID: 0011 , OEM ID: 0100
EMMC Date: 09/2015 Rev.0x0
EMMC NAME: 032G72 , S/N: 3010255470
EMMC NAME (HEX): 30333247373200
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.7 (MMC 5.0)
Boot configuration [PARTITION_CONFIG: 0x00] No boot partition configured.
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x00.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: 032G72_3010255470_20161111_1758.extcsd
Searching for partition tables...
Detected GPT over MBR...
Medium UUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Warning: Entries Count = 48
MMCBLK0P0 (MODEM) Range: [0X20000,0X3FFFE00] ,Len: 3FE0000
MMCBLK0P1 (PMIC) Range: [0X4000000,0X400B200] ,Len: B400
MMCBLK0P2 (SBL1) Range: [0X4020000,0X40DB600] ,Len: BB800
MMCBLK0P3 (DDR) Range: [0X4120000,0X421FE00] ,Len: 100000
MMCBLK0P4 (ABOOT) Range: [0X4220000,0X434BE00] ,Len: 12C000
MMCBLK0P5 (RPM) Range: [0X4397000,0X43CCA00] ,Len: 35C00
MMCBLK0P6 (TZ) Range: [0X4414000,0X44A3A00] ,Len: 8FC00
MMCBLK0P7 (SDI) Range: [0X4514000,0X452BE00] ,Len: 18000
MMCBLK0P8 (HYP) Range: [0X452C000,0X453EA00] ,Len: 12C00
MMCBLK0P9 (UTAGS) Range: [0X45AC000,0X462BE00] ,Len: 80000
MMCBLK0P10 (PADA) Range: [0X462C000,0X47FFE00] ,Len: 1D4000
MMCBLK0P11 (ABOOTBACKUP) Range: [0X4800000,0X492BE00] ,Len: 12C000
MMCBLK0P12 (RPMBACKUP) Range: [0X4977000,0X49ACA00] ,Len: 35C00
MMCBLK0P13 (TZBACKUP) Range: [0X49F4000,0X4A83A00] ,Len: 8FC00
MMCBLK0P14 (HYPBACKUP) Range: [0X4AF4000,0X4B06A00] ,Len: 12C00
MMCBLK0P15 (UTAGSBACKUP) Range: [0X4B74000,0X4BF3E00] ,Len: 80000
MMCBLK0P16 (PMICBACKUP) Range: [0X4C00000,0X4C0B200] ,Len: B400
MMCBLK0P17 (BLUETOOTH) Range: [0X4C20000,0X4E1FE00] ,Len: 200000
MMCBLK0P18 (PADB) Range: [0X4E20000,0X4FFFE00] ,Len: 1E0000
MMCBLK0P19 (MODEMST1) Range: [0X5000000,0X517FE00] ,Len: 180000
MMCBLK0P20 (MODEMST2) Range: [0X5180000,0X52FFE00] ,Len: 180000
MMCBLK0P21 (HOB) Range: [0X5300000,0X5379E00] ,Len: 7A000
MMCBLK0P22 (DHOB) Range: [0X537A000,0X5381E00] ,Len: 8000
MMCBLK0P23 (FSG) Range: [0X53A0000,0X551FE00] ,Len: 180000
MMCBLK0P24 (FSC) Range: [0X5520000,0X5520200] ,Len: 400
MMCBLK0P25 (CID) Range: [0X5520400,0X5540200] ,Len: 20000
MMCBLK0P26 (MISC) Range: [0X5540400,0X55C0200] ,Len: 80000
MMCBLK0P27 (METADATA) Range: [0X55C0400,0X5640200] ,Len: 80000
MMCBLK0P28 (LOGS) Range: [0X5640400,0X5840200] ,Len: 200000
MMCBLK0P29 (LIMITS) Range: [0X5860000,0X5860200] ,Len: 400
MMCBLK0P30 (LOGO) Range: [0X5880000,0X607FE00] ,Len: 800000
MMCBLK0P31 (CLOGO) Range: [0X6080000,0X6B7FE00] ,Len: B00000
MMCBLK0P32 (FRP) Range: [0X6B80000,0X6BFFE00] ,Len: 80000
MMCBLK0P33 (PERSIST) Range: [0X6C00000,0X73FFE00] ,Len: 800000
MMCBLK0P34 (KPAN) Range: [0X7400000,0X7BFFE00] ,Len: 800000
MMCBLK0P35 (BOOT) Range: [0X7C00000,0XA3FFE00] ,Len: 2800000
MMCBLK0P36 (RECOVERY) Range: [0XA400000,0XCC13E00] ,Len: 2814000
MMCBLK0P37 (SSD) Range: [0XCC20000,0XCC21E00] ,Len: 2000
MMCBLK0P38 (LOGS-CHARGING) Range: [0XCC22000,0XCF21E00] ,Len: 300000
MMCBLK0P39 (PADC) Range: [0XCF22000,0XCFFFE00] ,Len: DE000
MMCBLK0P40 (SP) Range: [0XD000000,0XD7FFE00] ,Len: 800000
MMCBLK0P41 (KEYSTORE) Range: [0XD800000,0XDFFFE00] ,Len: 800000
MMCBLK0P42 (CUSTOMIZE) Range: [0XE000000,0XFFFFE00] ,Len: 2000000
MMCBLK0P43 (OEM) Range: [0X10000000,0X10FFFE00] ,Len: 1000000
MMCBLK0P44 (CARRIER) Range: [0X11000000,0X11FFFE00] ,Len: 1000000
MMCBLK0P45 (CACHE) Range: [0X12000000,0X41FFFE00] ,Len: 30000000
MMCBLK0P46 (SYSTEM) Range: [0X42000000,0X141FFFE00] ,Len: 100000000
MMCBLK0P47 (USERDATA) Range: [0X142000000,0X745BDFE00] ,Len: 603BE0000
Done...Presets has been updated...
Done.
Running:Format FRP Partition...
Z3X EasyJtag Software ver. 2.4.1.1
Loading eMMC Addon Firmware... IO: 1800 mV
Box S/N: 1414FD121D756485, ,FW Ver.: 01.56
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
HiPower mode is off!
---------- eMMC Device Information ----------
EMMC CID : 11010030333247373200B36CDA6E924E
EMMC CSD : D02700320F5903FFFFFFFFE78640009A
EMMC Manufacturer ID: 0011 , OEM ID: 0100
EMMC Date: 09/2015 Rev.0x0
EMMC NAME: 032G72 , S/N: 3010255470
EMMC NAME (HEX): 30333247373200
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Searching for partition tables...
Detected GPT over MBR...
Medium UUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
GPT Entries Count = 48
Searching for FRP Data...
Marker of 6b80000 is: 19901873
FRP/Persistent Storage Format Success!
Searching for KillSwitch Specific FRP Data...
LG Custom Data is not found!
Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 603BE0000 bytes from 142000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 30000000 bytes from 12000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 02000000 bytes from 0E000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 00B00000 bytes from 06080000 ...ROM1
Erase Done.
this is good news
any pics logs or docs hardware software that you can share would be awesome
vim1 said:
Successed wipe FRP in hardstyle way. Pull off eMMC from PCB and soldered back. Logs here :
Code:
Z3X EasyJtag Software ver. 2.4.1.1
Loading eMMC Addon Firmware... IO: 1800 mV
Box S/N: 1414FD121D756485, ,FW Ver.: 01.56
CMD Pullup Level:1175 mV
CMD Active Level:1515 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
HiPower mode is off!
---------- eMMC Device Information ----------
EMMC CID : 11010030333247373200B36CDA6E924E
EMMC CSD : D02700320F5903FFFFFFFFE78640009A
EMMC Manufacturer ID: 0011 , OEM ID: 0100
EMMC Date: 09/2015 Rev.0x0
EMMC NAME: 032G72 , S/N: 3010255470
EMMC NAME (HEX): 30333247373200
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.7 (MMC 5.0)
Boot configuration [PARTITION_CONFIG: 0x00] No boot partition configured.
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x00.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: 032G72_3010255470_20161111_1758.extcsd
Searching for partition tables...
Detected GPT over MBR...
Medium UUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Warning: Entries Count = 48
MMCBLK0P0 (MODEM) Range: [0X20000,0X3FFFE00] ,Len: 3FE0000
MMCBLK0P1 (PMIC) Range: [0X4000000,0X400B200] ,Len: B400
MMCBLK0P2 (SBL1) Range: [0X4020000,0X40DB600] ,Len: BB800
MMCBLK0P3 (DDR) Range: [0X4120000,0X421FE00] ,Len: 100000
MMCBLK0P4 (ABOOT) Range: [0X4220000,0X434BE00] ,Len: 12C000
MMCBLK0P5 (RPM) Range: [0X4397000,0X43CCA00] ,Len: 35C00
MMCBLK0P6 (TZ) Range: [0X4414000,0X44A3A00] ,Len: 8FC00
MMCBLK0P7 (SDI) Range: [0X4514000,0X452BE00] ,Len: 18000
MMCBLK0P8 (HYP) Range: [0X452C000,0X453EA00] ,Len: 12C00
MMCBLK0P9 (UTAGS) Range: [0X45AC000,0X462BE00] ,Len: 80000
MMCBLK0P10 (PADA) Range: [0X462C000,0X47FFE00] ,Len: 1D4000
MMCBLK0P11 (ABOOTBACKUP) Range: [0X4800000,0X492BE00] ,Len: 12C000
MMCBLK0P12 (RPMBACKUP) Range: [0X4977000,0X49ACA00] ,Len: 35C00
MMCBLK0P13 (TZBACKUP) Range: [0X49F4000,0X4A83A00] ,Len: 8FC00
MMCBLK0P14 (HYPBACKUP) Range: [0X4AF4000,0X4B06A00] ,Len: 12C00
MMCBLK0P15 (UTAGSBACKUP) Range: [0X4B74000,0X4BF3E00] ,Len: 80000
MMCBLK0P16 (PMICBACKUP) Range: [0X4C00000,0X4C0B200] ,Len: B400
MMCBLK0P17 (BLUETOOTH) Range: [0X4C20000,0X4E1FE00] ,Len: 200000
MMCBLK0P18 (PADB) Range: [0X4E20000,0X4FFFE00] ,Len: 1E0000
MMCBLK0P19 (MODEMST1) Range: [0X5000000,0X517FE00] ,Len: 180000
MMCBLK0P20 (MODEMST2) Range: [0X5180000,0X52FFE00] ,Len: 180000
MMCBLK0P21 (HOB) Range: [0X5300000,0X5379E00] ,Len: 7A000
MMCBLK0P22 (DHOB) Range: [0X537A000,0X5381E00] ,Len: 8000
MMCBLK0P23 (FSG) Range: [0X53A0000,0X551FE00] ,Len: 180000
MMCBLK0P24 (FSC) Range: [0X5520000,0X5520200] ,Len: 400
MMCBLK0P25 (CID) Range: [0X5520400,0X5540200] ,Len: 20000
MMCBLK0P26 (MISC) Range: [0X5540400,0X55C0200] ,Len: 80000
MMCBLK0P27 (METADATA) Range: [0X55C0400,0X5640200] ,Len: 80000
MMCBLK0P28 (LOGS) Range: [0X5640400,0X5840200] ,Len: 200000
MMCBLK0P29 (LIMITS) Range: [0X5860000,0X5860200] ,Len: 400
MMCBLK0P30 (LOGO) Range: [0X5880000,0X607FE00] ,Len: 800000
MMCBLK0P31 (CLOGO) Range: [0X6080000,0X6B7FE00] ,Len: B00000
MMCBLK0P32 (FRP) Range: [0X6B80000,0X6BFFE00] ,Len: 80000
MMCBLK0P33 (PERSIST) Range: [0X6C00000,0X73FFE00] ,Len: 800000
MMCBLK0P34 (KPAN) Range: [0X7400000,0X7BFFE00] ,Len: 800000
MMCBLK0P35 (BOOT) Range: [0X7C00000,0XA3FFE00] ,Len: 2800000
MMCBLK0P36 (RECOVERY) Range: [0XA400000,0XCC13E00] ,Len: 2814000
MMCBLK0P37 (SSD) Range: [0XCC20000,0XCC21E00] ,Len: 2000
MMCBLK0P38 (LOGS-CHARGING) Range: [0XCC22000,0XCF21E00] ,Len: 300000
MMCBLK0P39 (PADC) Range: [0XCF22000,0XCFFFE00] ,Len: DE000
MMCBLK0P40 (SP) Range: [0XD000000,0XD7FFE00] ,Len: 800000
MMCBLK0P41 (KEYSTORE) Range: [0XD800000,0XDFFFE00] ,Len: 800000
MMCBLK0P42 (CUSTOMIZE) Range: [0XE000000,0XFFFFE00] ,Len: 2000000
MMCBLK0P43 (OEM) Range: [0X10000000,0X10FFFE00] ,Len: 1000000
MMCBLK0P44 (CARRIER) Range: [0X11000000,0X11FFFE00] ,Len: 1000000
MMCBLK0P45 (CACHE) Range: [0X12000000,0X41FFFE00] ,Len: 30000000
MMCBLK0P46 (SYSTEM) Range: [0X42000000,0X141FFFE00] ,Len: 100000000
MMCBLK0P47 (USERDATA) Range: [0X142000000,0X745BDFE00] ,Len: 603BE0000
Done...Presets has been updated...
Done.
Running:Format FRP Partition...
Z3X EasyJtag Software ver. 2.4.1.1
Loading eMMC Addon Firmware... IO: 1800 mV
Box S/N: 1414FD121D756485, ,FW Ver.: 01.56
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
HiPower mode is off!
---------- eMMC Device Information ----------
EMMC CID : 11010030333247373200B36CDA6E924E
EMMC CSD : D02700320F5903FFFFFFFFE78640009A
EMMC Manufacturer ID: 0011 , OEM ID: 0100
EMMC Date: 09/2015 Rev.0x0
EMMC NAME: 032G72 , S/N: 3010255470
EMMC NAME (HEX): 30333247373200
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Searching for partition tables...
Detected GPT over MBR...
Medium UUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
GPT Entries Count = 48
Searching for FRP Data...
Marker of 6b80000 is: 19901873
FRP/Persistent Storage Format Success!
Searching for KillSwitch Specific FRP Data...
LG Custom Data is not found!
Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 603BE0000 bytes from 142000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 30000000 bytes from 12000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 02000000 bytes from 0E000000 ...ROM1
Erase Done.
Z3X EasyJtag Software ver. 2.4.1.1
Skip loading eMMC Addon Firmware
CMD Pullup Level:1691 mV
CMD Active Level:1763 mV
Box IO Level:1800 mV
CLK Rate:21000 khz
Erasing 00B00000 bytes from 06080000 ...ROM1
Erase Done.
Click to expand...
Click to collapse
Related
[dev][ref][q]ancora partition table
as the title said, here i will post partition table of our ancora Code: Number Start (sector) End (sector) Size Code Name 1 1 212991 104.0 MiB 0700 Microsoft basic data 2 212992 213991 500.0 KiB 8300 Linux filesystem 3 213992 221183 3.5 MiB 8300 Linux filesystem 5 229376 239615 5.0 MiB 8300 Linux filesystem 6 245760 285759 19.5 MiB 8300 Linux filesystem 7 286720 292863 3.0 MiB 8300 Linux filesystem 8 294912 306175 5.5 MiB 8300 Linux filesystem 9 311296 324271 6.3 MiB 8300 Linux filesystem 10 327680 333823 3.0 MiB 8300 Linux filesystem 11 335872 342015 3.0 MiB 8300 Linux filesystem 12 344064 360447 8.0 MiB 8300 Linux filesystem 13 360448 375807 7.5 MiB 8300 Linux filesystem 14 376832 387071 5.0 MiB 8300 Linux filesystem 15 393216 1488895 535.0 MiB 8300 Linux filesystem 16 1490944 1613823 60.0 MiB 8300 Linux filesystem 17 1613824 3887103 1.1 GiB 8300 Linux filesystem 18 3891200 3993599 50.0 MiB 8300 Linux filesystem 19 3997696 3998695 500.0 KiB 8300 Linux filesystem 20 4005888 4013079 3.5 MiB 8300 Linux filesystem 21 4014080 4024319 5.0 MiB 8300 Linux filesystem 22 4030464 4070463 19.5 MiB 8300 Linux filesystem 23 4071424 4081663 5.0 MiB 8300 Linux filesystem 24 4087808 4101807 6.8 MiB 8300 Linux filesystem 25 4104192 4114431 5.0 MiB 8300 Linux filesystem 26 4120576 4130815 5.0 MiB 8300 Linux filesystem 27 4136960 4147199 5.0 MiB 8300 Linux filesystem 28 4153344 7733247 1.7 GiB 8300 Linux filesystem well, my question regarding this data are 1. why i don't get the name of each partition ? 2. as we know, kernel block memory is mmcblk0p13, the block size is 7.5MB, is this available size only for the kernel or this size included kernel+ramdisk? 3. we got so many partition, any idea of having a hidden partition that is vacant or useable to mount other things? thanks
i hope pep would see this post and help me Sent from my GT-I8150
hadidjapri said: i hope pep would see this post and help me Sent from my GT-I8150 Click to expand... Click to collapse You're making me ashamed I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified: * bootloader partition * 2 (two) baseband partitions * ROM partition * recovery partition As to the others... they *are* still mysterious... -- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
pepoluan said: You're making me ashamed I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified: * bootloader partition * 2 (two) baseband partitions * ROM partition * recovery partition As to the others... they *are* still mysterious... -- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 -- Click to expand... Click to collapse i got efs from arco another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk? Sent from my GT-I8150
hadidjapri said: another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk? Click to expand... Click to collapse kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb. This is the information I've gathered about the partitions. Code: # cat /proc/partitions major minor #blocks name 179 0 3864576 mmcblk0 179 1 106495 mmcblk0p1 //secboot2 partition map 179 2 500 mmcblk0p2 //dbl (boot loader) 179 3 3596 mmcblk0p3 //osbl (boot loader) 179 4 1 mmcblk0p4 //mbr extended partition table 179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode) 179 6 20000 mmcblk0p6 //amss 179 7 3072 mmcblk0p7 //emmcparam 179 8 5632 mmcblk0p8 //boot 179 9 6488 mmcblk0p9 //adsp 179 10 3072 mmcblk0p10 //rmt 179 11 3072 mmcblk0p11 //rmt 179 12 8192 mmcblk0p12 //persist 179 13 7680 mmcblk0p13 //recovery 179 14 5120 mmcblk0p14 //param 179 15 547840 mmcblk0p15 //system 179 16 61440 mmcblk0p16 //cache 179 17 1136640 mmcblk0p17 //data 179 18 51200 mmcblk0p18 //preload 179 19 500 mmcblk0p19 179 20 3596 mmcblk0p20 179 21 5120 mmcblk0p21 179 22 20000 mmcblk0p22 179 23 5120 mmcblk0p23 179 24 7000 mmcblk0p24 179 25 5120 mmcblk0p25 179 26 5120 mmcblk0p26 179 27 5120 mmcblk0p27 //efs 179 28 1787904 mmcblk0p28 //internal sdcard
arco68 said: kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb. This is the information I've gathered about the partitions. Code: # cat /proc/partitions major minor #blocks name 179 0 3864576 mmcblk0 179 1 106495 mmcblk0p1 //secboot2 partition map 179 2 500 mmcblk0p2 //dbl (boot loader) 179 3 3596 mmcblk0p3 //osbl (boot loader) 179 4 1 mmcblk0p4 //mbr extended partition table 179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode) 179 6 20000 mmcblk0p6 //amss 179 7 3072 mmcblk0p7 //emmcparam 179 8 5632 mmcblk0p8 //boot 179 9 6488 mmcblk0p9 //adsp 179 10 3072 mmcblk0p10 //rmt 179 11 3072 mmcblk0p11 //rmt 179 12 8192 mmcblk0p12 //persist 179 13 7680 mmcblk0p13 //recovery 179 14 5120 mmcblk0p14 //param 179 15 547840 mmcblk0p15 //system 179 16 61440 mmcblk0p16 //cache 179 17 1136640 mmcblk0p17 //data 179 18 51200 mmcblk0p18 //preload 179 19 500 mmcblk0p19 179 20 3596 mmcblk0p20 179 21 5120 mmcblk0p21 179 22 20000 mmcblk0p22 179 23 5120 mmcblk0p23 179 24 7000 mmcblk0p24 179 25 5120 mmcblk0p25 179 26 5120 mmcblk0p26 179 27 5120 mmcblk0p27 //efs 179 28 1787904 mmcblk0p28 //internal sdcard Click to expand... Click to collapse hmm what does mmcblk10-26 store sir? Sent from my GT-I8150
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
arco68 said: You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros. Click to expand... Click to collapse I once dd-ed p22, it has similar strings to p6. A kind of backup baseband? -- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
sigprof said:
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
Click to expand...
Click to collapse
is it possible partition number 19-26 are intended to be backup partition?
Sent from my GT-I8150
Could phone operator lock code be stored in one of the (normally unmounted) partitions? Sent from my GT-I8150 using xda app-developers app
Help can't Reboot into recovery
Hi guys I got Xperia T3 D5102 few days back. I rooted it & deodexed rom & now making few mods. I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot. Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone. Also I tried to go the hardware way by trying key combinations in many ways Power + Volume up/down doesn't work Power + Volume both btns also didn't work. Also tried using ADB commands for Advance power menu . But no luck then too. I suspect there is no recovery partition and hence didn't boot. The below table shows the partition table Code: Number Start End Size File system Name F 1 131kB 2228kB 2097kB TA 2 2228kB 2753kB 524kB sbl1 3 2753kB 3015kB 262kB s1sbl 4 3015kB 3080kB 65.5kB dbi 5 3080kB 3604kB 524kB aboot 6 3604kB 4129kB 524kB rpm 7 4129kB 4653kB 524kB tz 8 4653kB 5177kB 524kB alt_sbl1 9 5177kB 5439kB 262kB alt_s1sbl 10 5439kB 5505kB 65.5kB alt_dbi 11 5505kB 6029kB 524kB alt_aboot 12 6029kB 6554kB 524kB alt_rpm 13 6554kB 7078kB 524kB alt_tz 14 8389kB 9961kB 1573kB fsg 15 12.6MB 14.2MB 1573kB modemst1 16 16.8MB 18.4MB 1573kB modemst2 17 21.0MB 37.7MB 16.8MB ext4 persist 18 37.7MB 105MB 67.1MB fat16 modem 19 105MB 126MB 21.0MB boot 20 126MB 136MB 10.5MB fat32 ramdump 21 136MB 153MB 16.8MB FOTAKernel 22 153MB 153MB 32.8kB DDR 23 153MB 170MB 16.8MB ext4 LTALabel 24 172MB 180MB 8389kB apps_log 25 180MB 2248MB 2068MB ext4 system 26 2248MB 2458MB 210MB ext4 cache 27 2458MB 7818MB 5360MB ext4 userdata (parted) [email protected]:/ $ cat /proc/partitions cat /proc/partitions Code: major minor #blocks name 179 0 7634944 mmcblk0 179 1 2048 mmcblk0p1 179 2 512 mmcblk0p2 179 3 256 mmcblk0p3 179 4 64 mmcblk0p4 179 5 512 mmcblk0p5 179 6 512 mmcblk0p6 179 7 512 mmcblk0p7 179 8 512 mmcblk0p8 179 9 256 mmcblk0p9 179 10 64 mmcblk0p10 179 11 512 mmcblk0p11 179 12 512 mmcblk0p12 179 13 512 mmcblk0p13 179 14 1536 mmcblk0p14 179 15 1536 mmcblk0p15 179 16 1536 mmcblk0p16 179 17 16384 mmcblk0p17 179 18 65536 mmcblk0p18 179 19 20480 mmcblk0p19 179 20 10240 mmcblk0p20 179 21 16384 mmcblk0p21 179 22 32 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 8192 mmcblk0p24 179 25 2019328 mmcblk0p25 179 26 204800 mmcblk0p26 179 27 5234671 mmcblk0p27 179 32 512 mmcblk0rpmb 179 64 7761920 mmcblk1 179 65 7760896 mmcblk1p1 [email protected]:/ $ Need help from developers /modders on how to proceed further and lemme know some hint to proceed. I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone. Request someone to throw light on this ! Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said: Hello, just a question : how did you root your T3 ? are you allways on .14 ? Click to expand... Click to collapse Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery. AJ
Abhinav2 said: Xperia devices don't have a recovery partition. Neither do they have any stock recovery. AJ Click to expand... Click to collapse You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said: You wrong, only a few xperia devices does NOT have a recovery partition, all others have it Click to expand... Click to collapse None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition AJ
Al parecer no existe recovery Xenon1978 said: Hi guys I got Xperia T3 D5102 few days back. I rooted it & deodexed rom & now making few mods. I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot. Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone. Also I tried to go the hardware way by trying key combinations in many ways Power + Volume up/down doesn't work Power + Volume both btns also didn't work. Also tried using ADB commands for Advance power menu . But no luck then too. I suspect there is no recovery partition and hence didn't boot. The below table shows the partition table Code: Number Start End Size File system Name F 1 131kB 2228kB 2097kB TA 2 2228kB 2753kB 524kB sbl1 3 2753kB 3015kB 262kB s1sbl 4 3015kB 3080kB 65.5kB dbi 5 3080kB 3604kB 524kB aboot 6 3604kB 4129kB 524kB rpm 7 4129kB 4653kB 524kB tz 8 4653kB 5177kB 524kB alt_sbl1 9 5177kB 5439kB 262kB alt_s1sbl 10 5439kB 5505kB 65.5kB alt_dbi 11 5505kB 6029kB 524kB alt_aboot 12 6029kB 6554kB 524kB alt_rpm 13 6554kB 7078kB 524kB alt_tz 14 8389kB 9961kB 1573kB fsg 15 12.6MB 14.2MB 1573kB modemst1 16 16.8MB 18.4MB 1573kB modemst2 17 21.0MB 37.7MB 16.8MB ext4 persist 18 37.7MB 105MB 67.1MB fat16 modem 19 105MB 126MB 21.0MB boot 20 126MB 136MB 10.5MB fat32 ramdump 21 136MB 153MB 16.8MB FOTAKernel 22 153MB 153MB 32.8kB DDR 23 153MB 170MB 16.8MB ext4 LTALabel 24 172MB 180MB 8389kB apps_log 25 180MB 2248MB 2068MB ext4 system 26 2248MB 2458MB 210MB ext4 cache 27 2458MB 7818MB 5360MB ext4 userdata (parted) [email protected]:/ $ cat /proc/partitions cat /proc/partitions Code: major minor #blocks name 179 0 7634944 mmcblk0 179 1 2048 mmcblk0p1 179 2 512 mmcblk0p2 179 3 256 mmcblk0p3 179 4 64 mmcblk0p4 179 5 512 mmcblk0p5 179 6 512 mmcblk0p6 179 7 512 mmcblk0p7 179 8 512 mmcblk0p8 179 9 256 mmcblk0p9 179 10 64 mmcblk0p10 179 11 512 mmcblk0p11 179 12 512 mmcblk0p12 179 13 512 mmcblk0p13 179 14 1536 mmcblk0p14 179 15 1536 mmcblk0p15 179 16 1536 mmcblk0p16 179 17 16384 mmcblk0p17 179 18 65536 mmcblk0p18 179 19 20480 mmcblk0p19 179 20 10240 mmcblk0p20 179 21 16384 mmcblk0p21 179 22 32 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 8192 mmcblk0p24 179 25 2019328 mmcblk0p25 179 26 204800 mmcblk0p26 179 27 5234671 mmcblk0p27 179 32 512 mmcblk0rpmb 179 64 7761920 mmcblk1 179 65 7760896 mmcblk1p1 [email protected]:/ $ Need help from developers /modders on how to proceed further and lemme know some hint to proceed. I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone. Request someone to throw light on this ! Thanks Click to expand... Click to collapse No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE Code: FAILED <remote: Recovery partición doesn't founded>
H815 System Dump Needed!
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available. After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said: Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it. Click to expand... Click to collapse Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045 If you need help pm me
macdaddie87 said: Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045 If you need help pm me Click to expand... Click to collapse I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said: After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available. After someone dumps and uploads the system.img we should just be able to flash via fastboot. Click to expand... Click to collapse Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728 Code: major minor #blocks name 253 0 721772 zram0 179 0 30535680 mmcblk0 179 1 88064 mmcblk0p1 179 2 512 mmcblk0p2 179 3 1024 mmcblk0p3 179 4 1024 mmcblk0p4 179 5 512 mmcblk0p5 179 6 512 mmcblk0p6 179 7 512 mmcblk0p7 179 8 2048 mmcblk0p8 179 9 1024 mmcblk0p9 179 10 512 mmcblk0p10 179 11 1024 mmcblk0p11 179 12 512 mmcblk0p12 179 13 512 mmcblk0p13 179 14 2048 mmcblk0p14 179 15 512 mmcblk0p15 179 16 512 mmcblk0p16 179 17 512 mmcblk0p17 179 18 512 mmcblk0p18 179 19 512 mmcblk0p19 179 20 512 mmcblk0p20 179 21 1536 mmcblk0p21 179 22 16384 mmcblk0p22 179 23 32768 mmcblk0p23 179 24 1536 mmcblk0p24 179 25 1536 mmcblk0p25 179 26 1536 mmcblk0p26 179 27 512 mmcblk0p27 179 28 512 mmcblk0p28 179 29 512 mmcblk0p29 179 30 2048 mmcblk0p30 179 31 512 mmcblk0p31 259 0 512 mmcblk0p32 259 1 512 mmcblk0p33 259 2 512 mmcblk0p34 259 3 2048 mmcblk0p35 259 4 4096 mmcblk0p36 259 5 49152 mmcblk0p37 259 6 40960 mmcblk0p38 259 7 40960 mmcblk0p39 259 8 8192 mmcblk0p40 259 9 8192 mmcblk0p41 259 10 32768 mmcblk0p42 259 11 47104 mmcblk0p43 259 12 10240 mmcblk0p44 259 13 4096 mmcblk0p45 259 14 4096 mmcblk0p46 259 15 4239360 mmcblk0p47 259 16 262144 mmcblk0p48 259 17 1261568 mmcblk0p49 259 18 24313856 mmcblk0p50 259 19 12271 mmcblk0p51 179 32 4096 mmcblk0rpmb DDR -> /dev/block/mmcblk0p30 aboot -> /dev/block/mmcblk0p8 abootbak -> /dev/block/mmcblk0p14 apdp -> /dev/block/mmcblk0p18 boot -> /dev/block/mmcblk0p38 cache -> /dev/block/mmcblk0p49 cust -> /dev/block/mmcblk0p48 devinfo -> /dev/block/mmcblk0p17 po -> /dev/block/mmcblk0p20 drm -> /dev/block/mmcblk0p40 eksst -> /dev/block/mmcblk0p33 encrypt -> /dev/block/mmcblk0p32 factory -> /dev/block/mmcblk0p43 fota -> /dev/block/mmcblk0p44 fsc -> /dev/block/mmcblk0p27 fsg -> /dev/block/mmcblk0p26 grow -> /dev/block/mmcblk0p51 hyp -> /dev/block/mmcblk0p6 hypbak -> /dev/block/mmcblk0p12 keystore -> /dev/block/mmcblk0p29 laf -> /dev/block/mmcblk0p37 limits -> /dev/block/mmcblk0p16 misc -> /dev/block/mmcblk0p22 modem -> /dev/block/mmcblk0p1 modemst1 -> /dev/block/mmcblk0p24 modemst2 -> /dev/block/mmcblk0p25 mpt -> /dev/block/mmcblk0p42 msadp -> /dev/block/mmcblk0p19 persist -> /dev/block/mmcblk0p23 pmic -> /dev/block/mmcblk0p2 pmicbak -> /dev/block/mmcblk0p10 raw_resources -> /dev/block/mmcblk0p45 raw_resourcesbak -> /dev/block/mmcblk0p46 rct -> /dev/block/mmcblk0p34 recovery -> /dev/block/mmcblk0p39 rpm -> /dev/block/mmcblk0p7 rpmbak -> /dev/block/mmcblk0p13 sbl1 -> /dev/block/mmcblk0p3 sbl1bak -> /dev/block/mmcblk0p9 sdi -> /dev/block/mmcblk0p5 sdibak -> /dev/block/mmcblk0p15 sec -> /dev/block/mmcblk0p31 sns -> /dev/block/mmcblk0p41 spare1 -> /dev/block/mmcblk0p21 spare2 -> /dev/block/mmcblk0p36 ssd -> /dev/block/mmcblk0p28 system -> /dev/block/mmcblk0p47 tz -> /dev/block/mmcblk0p4 tzbak -> /dev/block/mmcblk0p11 userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Partition Layout for P20 lite
Code: HWANE:/ $ cat /proc/partitions major minor #blocks name 1 0 8192 ram0 1 1 8192 ram1 1 2 8192 ram2 1 3 8192 ram3 254 0 2293760 zram0 179 0 61071360 mmcblk0 179 1 256 mmcblk0p1 179 2 256 mmcblk0p2 179 3 256 mmcblk0p3 179 4 768 mmcblk0p4 179 5 4096 mmcblk0p5 179 6 4096 mmcblk0p6 179 7 6144 mmcblk0p7 179 8 65536 mmcblk0p8 179 9 4096 mmcblk0p9 179 10 4096 mmcblk0p10 179 11 8192 mmcblk0p11 179 12 4096 mmcblk0p12 179 13 32768 mmcblk0p13 179 14 2048 mmcblk0p14 179 15 2048 mmcblk0p15 179 16 2048 mmcblk0p16 179 17 14336 mmcblk0p17 179 18 32768 mmcblk0p18 179 19 65536 mmcblk0p19 179 20 2048 mmcblk0p20 179 21 24576 mmcblk0p21 179 22 61440 mmcblk0p22 179 23 4096 mmcblk0p23 179 24 2048 mmcblk0p24 179 25 16384 mmcblk0p25 179 26 12288 mmcblk0p26 179 27 24576 mmcblk0p27 179 28 32768 mmcblk0p28 179 29 16384 mmcblk0p29 179 30 24576 mmcblk0p30 179 31 16384 mmcblk0p31 179 32 32768 mmcblk0p32 179 33 16384 mmcblk0p33 179 34 28672 mmcblk0p34 179 35 4096 mmcblk0p35 179 36 98304 mmcblk0p36 179 37 1024 mmcblk0p37 179 38 1024 mmcblk0p38 179 39 2048 mmcblk0p39 179 40 16384 mmcblk0p40 179 41 4096 mmcblk0p41 179 42 131072 mmcblk0p42 179 43 131072 mmcblk0p43 179 44 2048 mmcblk0p44 179 45 2048 mmcblk0p45 179 46 4096 mmcblk0p46 179 47 32768 mmcblk0p47 259 0 2048 mmcblk0p48 259 1 16384 mmcblk0p49 259 2 14336 mmcblk0p50 259 3 5767168 mmcblk0p51 259 4 196608 mmcblk0p52 259 5 32768 mmcblk0p53 259 6 802816 mmcblk0p54 259 7 196608 mmcblk0p55 259 8 53043200 mmcblk0p56 179 144 4096 mmcblk0rpmb 179 96 4096 mmcblk0boot1 179 48 4096 mmcblk0boot0 179 192 62367744 mmcblk1 179 193 62366720 mmcblk1p1 253 0 4724684 dm-0 253 1 790064 dm-1 253 2 128924 dm-2 253 3 32172 dm-3 253 4 193424 dm-4 253 5 193424 dm-5 Code: HWANE:/ $ ls -l /dev/block/platform/hi_mci.0/by-name/ [I][B]User friendly display[/B][/I] /dev/block/mmcblk0p48 -> bootfail_info /dev/block/mmcblk0p42 -> cache /dev/block/mmcblk0p52 -> cust /dev/block/mmcblk0p40 -> dfx /dev/block/mmcblk0p35 -> dto /dev/block/mmcblk0p34 -> dts /dev/block/mmcblk0p27 -> erecovery_kernel /dev/block/mmcblk0p28 -> erecovery_ramdisk /dev/block/mmcblk0p38 -> erecovery_vbmeta /dev/block/mmcblk0p29 -> erecovery_vendor /dev/block/mmcblk0p5 -> fastboot /dev/block/mmcblk0p4 -> frp /dev/block/mmcblk0p26 -> fw_hifi /dev/block/mmcblk0p3 -> fw_lpm3 /dev/block/mmcblk0p44 -> hisitest0 /dev/block/mmcblk0p45 -> hisitest1 /dev/block/mmcblk0p46 -> hisitest2 /dev/block/mmcblk0p30 -> kernel /dev/block/mmcblk0p20 -> misc /dev/block/mmcblk0p36 -> modem_fw /dev/block/mmcblk0p18 -> modem_om /dev/block/mmcblk0p17 -> modem_secure /dev/block/mmcblk0p10 -> modemnvm_backup /dev/block/mmcblk0p6 -> modemnvm_factory /dev/block/mmcblk0p11 -> modemnvm_img /dev/block/mmcblk0p12 -> modemnvm_system /dev/block/mmcblk0p21 -> modemnvm_update /dev/block/mmcblk0p7 -> nvme /dev/block/mmcblk0p43 -> odm /dev/block/mmcblk0p8 -> oeminfo /dev/block/mmcblk0p47 -> patch /dev/block/mmcblk0p16 -> persist /dev/block/mmcblk0p55 -> product /dev/block/mmcblk0p31 -> ramdisk /dev/block/mmcblk0p32 -> recovery_ramdisk /dev/block/mmcblk0p37 -> recovery_vbmeta /dev/block/mmcblk0p33 -> recovery_vendor /dev/block/mmcblk0p22 -> reserved2 /dev/block/mmcblk0p9 -> reserved3 /dev/block/mmcblk0p14 -> reserved4 /dev/block/mmcblk0p15 -> reserved5 /dev/block/mmcblk0p39 -> reserved8 /dev/block/mmcblk0p50 -> reserved9 /dev/block/mmcblk0p49 -> rrecord /dev/block/mmcblk0p13 -> secure_storage /dev/block/mmcblk0p25 -> sensorhub /dev/block/mmcblk0p19 -> splash2 /dev/block/mmcblk0p51 -> system /dev/block/mmcblk0p23 -> teeos /dev/block/mmcblk0p24 -> trustfirmware /dev/block/mmcblk0p56 -> userdata /dev/block/mmcblk0p41 -> vbmeta /dev/block/mmcblk0p54 -> vendor /dev/block/mmcblk0p53 -> version /dev/block/mmcblk0p1 -> vrl /dev/block/mmcblk0p2 -> vrl_backup
Hello, I want to flash a firmware for downgrade. How i can make it without a dload method? I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Yes me to dload not downgrade Gesendet von meinem ANE-LX1 mit Tapatalk
Manflack said: Hello, I want to flash a firmware for downgrade. How i can make it without a dload method? I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that... Click to expand... Click to collapse SirusX said: Yes me to dload not downgrade Gesendet von meinem ANE-LX1 mit Tapatalk Click to expand... Click to collapse This is a partition layout it can't help you with downgrade. To downgrade without brick the phone you have to find a roll back firmware. In the picture is an example for p20 pro.
LM-G710V Hard Bricked. Qualcom 9008
G710V My Phone got bricked. Showing as Qualcom 9008. I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead.
Talharshad said: G710V My Phone got bricked. Showing as Qualcom 9008. I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead. Click to expand... Click to collapse There's no way to fix the 9008 mode on these phones yet regardless of how it happened
Hey what variant is the g710v? Was it factory unlocked? Sent from my OnePlus 5 using the XDA Premium App
aaya888 said:
i can help you with your problem it's posible to repair LG G4 V10 G5 V20 V30 G6 online "online usbredirector customer module"
you can contact me on skype = Aaya888
https://www.facebook.com/18367302566...991780680/?t=5
Model Settings:
Interface : USB
Core : Qualcomm MSM8996 UFS
Loader : QLoader_v2_LG
Connecting...
Sending loader...OK.
Loader successfully initialized.
INFO: Device Total Logical Blocks: 0x75ec00
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x1ad
INFO: Device Serial Number: 0x796e6978
INFO: {"storage_info": {"total_blocks":7728128, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":429, "serial_num":2037279096, "fw_version":"003","mem_type":"UFS","prod_name":"H28U62301AMR"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x1ad
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x3b9e000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x20
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x8079
UFS dEnhanced1MaxNAllocU: 0x1dcf
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x1dcf
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x1dcf
UFS wEnhanced3CapAdjFac: 0x200
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: SKhynix H28U62301AMR D003
ACK
Device : SKhynix H28U62301AMR D003
Core : Qualcomm MSM8996 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 7803904
Size : 29.77 GB (30484.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.0; FW: 1.23.
Physical partition number: 0
Block count : 7728128 (0x75EC00)
Size : 29.48 GB (30188.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00002000) 32 MB
P07: factory (0000B006, 00004200) 66 MB
P08: encrypt (0000F206, 00000080) 512 KB
P09: eksst (0000F286, 00000080) 512 KB
P10: rct (0000F306, 00000080) 512 KB
P11: ssd (0000F386, 00000080) 512 KB
P12: keystore (0000F406, 00000080) 512 KB
P13: carrier (0000F486, 00002800) 40 MB
P14: persist (00011C86, 00002000) 32 MB
P15: system (00013C86, 00169800) 5.648 GB
P16: cache (0017D486, 00081800) 2072 MB
P17: userdata (001FEC86, 0055F800) 21.49 GB
P18: grow (0075E486, 00000775) 7.457 MB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000300) 3072 KB
P02: xblbak (00000306, 00000300) 3072 KB
P03: fota (00000606, 00000400) 4 MB
P04: fsg (00000A06, 00000200) 2048 KB
P05: dip (00000C06, 00000100) 1024 KB
P06: devinfo (00000D06, 00000100) 1024 KB
P07: grow2 (00000E06, 00000001) 4 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000300) 3072 KB
P02: xbl2bak (00000306, 00000300) 3072 KB
P03: grow3 (00000606, 00000001) 4 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: reserve (00000206, 00000008) 32 KB
P03: cdt (0000020E, 00000001) 4 KB
P04: grow4 (0000020F, 00000001) 4 KB
Physical partition number: 4
Block count : 59392 (0xE800)
Size : 232.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: aboot (00007D06, 00000200) 2048 KB
P07: abootbak (00007F06, 00000200) 2048 KB
P08: raw_resources (00008106, 00000400) 4 MB
P09: raw_resourcesbak (00008506, 00000400) 4 MB
P10: rpm (00008906, 00000080) 512 KB
P11: rpmbak (00008986, 00000080) 512 KB
P12: hyp (00008A06, 00000080) 512 KB
P13: hypbak (00008A86, 00000080) 512 KB
P14: pmic (00008B06, 00000080) 512 KB
P15: pmicbak (00008B86, 00000080) 512 KB
P16: devcfg (00008C06, 00000020) 128 KB
P17: devcfgbak (00008C26, 00000020) 128 KB
P18: modem (00008C46, 00005600) 86 MB
P19: sec (0000E246, 00000080) 512 KB
P20: keymaster (0000E2C6, 00000080) 512 KB
P21: keymasterbak (0000E346, 00000080) 512 KB
P22: cmnlib (0000E3C6, 00000080) 512 KB
P23: cmnlibbak (0000E446, 00000080) 512 KB
P24: cmnlib64 (0000E4C6, 00000080) 512 KB
P25: cmnlib64bak (0000E546, 00000080) 512 KB
P26: apdp (0000E5C6, 00000080) 512 KB
P27: msadp (0000E646, 00000080) 512 KB
P28: dpo (0000E6C6, 00000080) 512 KB
P29: grow5 (0000E746, 00000001) 4 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000001) 4 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: persistent (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000001) 4 KB
Click to expand...
Click to collapse
That's for the Snapdragon 820.
Josh McGrath said:
That's for the Snapdragon 820.
Click to expand...
Click to collapse
INFO: Device Total Logical Blocks: 0xece800
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x198
INFO: Device Serial Number: 0x48494241
INFO: {"storage_info": {"total_blocks":15525888, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":408, "serial_num":1212760641, "fw_version":"100","mem_type":"UFS","prod_name":"THGAF4G9N4LBAIRB0100"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x198
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x7734000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x40
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x801f
UFS dEnhanced1MaxNAllocU: 0x3b9a
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x20
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x0
UFS wEnhanced3CapAdjFac: 0x0
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: TOSHIBA THGAF4G9N4LBAIRB0100
ACK
Device : TOSHIBA THGAF4G9N4LBAIRB0100
Core : Qualcomm MSM8998 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 15613952
Size : 59.56 GB (60992.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.5.9; FW: 1.23.
Physical partition number: 0
Block count : 15525888 (0xECE800)
Size : 59.23 GB (60648.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00000100) 1024 KB
P07: ftm (00009106, 00002000) 32 MB
P08: factory (0000B106, 00004200) 66 MB
P09: encrypt (0000F306, 00000080) 512 KB
P10: eksst (0000F386, 00000080) 512 KB
P11: rct (0000F406, 00000080) 512 KB
P12: ssd (0000F486, 00000080) 512 KB
P13: keystore (0000F506, 00000080) 512 KB
P14: persist (0000F586, 00002000) 32 MB
P15: srtc (00011586, 00000800) 8 MB
P16: qni (00011D86, 00001800) 24 MB
P17: pstore (00013586, 00000200) 2048 KB
P18: system (00013786, 0019A200) 6.408 GB
P19: cache (001AD986, 00020000) 512 MB
P20: userdata (001CD986, 00D00E74) 52.01 GB
P21: grow (00ECE7FA, 00000001) 4 KB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000380) 3584 KB
P02: fota (00000386, 00000400) 4 MB
P03: fsg (00000786, 00000200) 2048 KB
P04: dip (00000986, 00000100) 1024 KB
P05: devinfo (00000A86, 00000100) 1024 KB
P06: grow2 (00000B86, 00000002) 8 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000380) 3584 KB
P02: grow3 (00000386, 00000002) 8 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: cdt (00000206, 00000001) 4 KB
P03: grow4 (00000207, 00000002) 8 KB
Physical partition number: 4
Block count : 71680 (0x11800)
Size : 280.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: raw_resources (00007D06, 00000400) 4 MB
P07: raw_resourcesbak (00008106, 00000400) 4 MB
P08: rpm (00008506, 00000080) 512 KB
P09: rpmbak (00008586, 00000080) 512 KB
P10: hyp (00008606, 00000080) 512 KB
P11: hypbak (00008686, 00000080) 512 KB
P12: pmic (00008706, 00000080) 512 KB
P13: pmicbak (00008786, 00000080) 512 KB
P14: devcfg (00008806, 00000020) 128 KB
P15: devcfgbak (00008826, 00000020) 128 KB
P16: modem (00008846, 00006E00) 110 MB
P17: sec (0000F646, 00000080) 512 KB
P18: keymaster (0000F6C6, 00000080) 512 KB
P19: keymasterbak (0000F746, 00000080) 512 KB
P20: cmnlib (0000F7C6, 00000080) 512 KB
P21: cmnlibbak (0000F846, 00000080) 512 KB
P22: cmnlib64 (0000F8C6, 00000080) 512 KB
P23: cmnlib64bak (0000F946, 00000080) 512 KB
P24: apdp (0000F9C6, 00000080) 512 KB
P25: msadp (0000FA46, 00000080) 512 KB
P26: dpo (0000FAC6, 00000080) 512 KB
P27: abl (0000FB46, 00000100) 1024 KB
P28: ablbak (0000FC46, 00000100) 1024 KB
P29: limits (0000FD46, 00000001) 4 KB
P30: toolsfv (0000FD47, 00000100) 1024 KB
P31: logfs (0000FE47, 00000800) 8 MB
P32: storsec (00010647, 00000020) 128 KB
P33: storsecbak (00010667, 00000020) 128 KB
P34: grow5 (00010687, 00000002) 8 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000002) 8 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: frp (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000002) 8 KB
Yet again, that is the wrong model. That is not the G7. (!!!). It's good you can do that particular chipset, but You're really taking a huge hit to your credibility here.
Hi, Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone
DonDie said: Hi, Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone Click to expand... Click to collapse You'd be very lucky to find d the Firehouse file. Last file that was leaked was for the G4! There are companies like spammy above that do this but it'd be quicker to just get a warranty replacement from T-Mobile or LG. F- LG I hope they get a million damaged units cause they won't release the files we need to fix them ourselves
I had the wrong person mentioned. Please ignore
Josh McGrath said: Wtf is wrong with you? That's for the g6. Yet again you have proved you're ignorance and taken yet another serious blow to your credibility. Maybe you missed it. The g7 has a different chipset than the 8996, 8998 chipset. Mods can you please delete this thread? Its this guy and his spam, and incorrect spam at that. Click to expand... Click to collapse Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file. @ aaya888 Would you mind sharing the file?
DonDie said: Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file. @ aaya888 Would you mind sharing the file? Click to expand... Click to collapse I did, and saw it was a g6 with v20 partition tables. And actually, I thought it was the same guy I was correcting over and over and it is not so I have corrected my earlier post. I think they other guy got banned ?
@aaya888 How is the state of H918 (TMO V20) firehose fixin now a days, still no go?
Josh McGrath said: There's no way to fix the 9008 mode on these phones yet regardless of how it happened Click to expand... Click to collapse contact me i can help you out
Tennolee said: contact me i can help you out Click to expand... Click to collapse It's not me that needs the help but I know a lot of people could use your help after a hard brick.
Tennolee said: contact me i can help you out Click to expand... Click to collapse Can you do it remotely and how much will it cost?
DonDie said: Can you do it remotely and how much will it cost? Click to expand... Click to collapse Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version
KennynGGG said: Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version Click to expand... Click to collapse The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well): G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you. Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation.
GROOVYJOSHCLARK said: The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well): G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you. Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation. Click to expand... Click to collapse THanks, that's the reason I think JTAG pro can't send the loader to mine because it's G710TM which is not listed. I swear somehow that I had that same issue before but was able to fix just not now. Only if I can find the real Test Point to connect to ground. Their picture is very hard to see because it's not the whole motherboard picture just the section where the Test Points are.
Hi, I just changed the firmware on my G710 and LGUP informed Completed, but the phone never turned back on. I just found out I am also on the Qualcomm 9008. Did you manage to fix your issue? tks!
i need stock FirmWare for g570v stock rom, if anyone have?