I'm very interested in how the Desire kernel works in comparison to other devices. The kernel source, which HTC is obliged to provide under the GPL, is not currently listed at http://developer.htc.com/. I e-mailed them yesterday and this was their response:
Thank you for contacting us concerning your request fro the Kernal for the HTC Legend and the HTC Desire, My name is Chris and I will be helping you today.
I do understand how important it is to be able to use your device to the best of its capabilities. We are not withholding the kernel; we are currently working through the legal channels that we must go through to make the kernel available to you. Each product is individually under review. When the kernel is available, you will be able to find it on developer.htc.com. I apologize for any inconvenience you may have experienced, and thank you for your patience in this matter.
Click to expand...
Click to collapse
Kernel source will also help developers find root exploits (it seems as though fastboot oem unlock does not work on the Desire, or perhaps the majority of Desires). HTC has not been prompt in providing the kernel source before, while competitors like Motorola have provided it the day of launch or before, and Google has always provided kernel source of AOSP-based devices at android.git.kernel.org.
Thus, I will encourage everyone here to pester HTC about the Desire/Legend kernel source. This may help expedite the process. There is absolutely no reason HTC must go through "legal channels" in order to release the kernel source, unless they have plans to withhold the source if said legal channels deny them the privilege of releasing the source.
Also, I'm curious about the Desire's hardware. Can someone run a "cat /proc/meminfo" to see that extra 64MB of RAM? Also, run a multitouch test to see if the Desire uses a "fixed" panel.
To begin root speculation, can anyone confirm that there are OEM unlockable Desires in the wild? If so, could we downgrade production Desires to this older SPL and then unlock? HTC's latest kernels seem rock-solid, and are probably incredibly difficult to exploit: just look at the Eris.
coolbho3000 said:
I'm very interested in how the Desire kernel works in comparison to other devices. The kernel source, which HTC is obliged to provide under the GPL, is not currently listed at http://developer.htc.com/. I e-mailed them yesterday and this was their response:
Kernel source will also help developers find root exploits (it seems as though fastboot oem unlock does not work on the Desire, or perhaps the majority of Desires). HTC has not been prompt in providing the kernel source before.
Thus, I will encourage everyone here to pester HTC about the Desire/Legend kernel source. This may help expedite the process. There is absolutely no reason HTC must go through "legal channels" in order to release the kernel source, unless they have plans to withhold the source if said legal channels deny them the privilege of releasing the source.
Also, I'm curious about the Desire's hardware. Can someone run a "cat /proc/meminfo" to see that extra 64MB of RAM?
Click to expand...
Click to collapse
I think Mr. Chris does not have a clue what the hell are you talking about
those customer care guys are just there to make you feel better, in most cases they know nothing about what you really want, they just have a template that they can fill in the blanks from your request.
in the mean time, i will fire them an email too and see how they will fill in the blanks
Here's the output from meminfo below:
$ cat /proc/meminfo
MemTotal: 407900 kB
MemFree: 58380 kB
Buffers: 1224 kB
Cached: 122968 kB
SwapCached: 0 kB
Active: 242228 kB
Inactive: 80004 kB
Active(anon): 202488 kB
Inactive(anon): 0 kB
Active(file): 39740 kB
Inactive(file): 80004 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 198052 kB
Mapped: 69508 kB
Slab: 8648 kB
SReclaimable: 2556 kB
SUnreclaim: 6092 kB
PageTables: 12284 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 203948 kB
Committed_AS: 4838304 kB
VmallocTotal: 466944 kB
VmallocUsed: 130264 kB
VmallocChunk: 305156 kB
s1977 said:
Here's the output from meminfo below:
$ cat /proc/meminfo
MemTotal: 407900 kB
MemFree: 58380 kB
Buffers: 1224 kB
Cached: 122968 kB
SwapCached: 0 kB
Active: 242228 kB
Inactive: 80004 kB
Active(anon): 202488 kB
Inactive(anon): 0 kB
Active(file): 39740 kB
Inactive(file): 80004 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 198052 kB
Mapped: 69508 kB
Slab: 8648 kB
SReclaimable: 2556 kB
SUnreclaim: 6092 kB
PageTables: 12284 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 203948 kB
Committed_AS: 4838304 kB
VmallocTotal: 466944 kB
VmallocUsed: 130264 kB
VmallocChunk: 305156 kB
Click to expand...
Click to collapse
Thanks Looks pretty similar to the N1 after highmem, give or take 12MB or so. That 64MB is probably baseband-only after all...
Bump: Now that the HTC Desire has been rooted, it is more imperative than ever that we have the kernel source. Kernel source will allow low-level tweaks that is not possible without it!
Please bug HTC about this issue so that the Desire kernel can be modified.
Title says it all. Recently upgraded ti a new kernel, got SetCPU. If you need any specific details, please ask.
Sent from a Time Lord, using his TARDIS.
Bad-Wolf said:
Title says it all. Recently upgraded ti a new kernel, got SetCPU. If you need any specific details, please ask.
Sent from a Time Lord, using his TARDIS.
Click to expand...
Click to collapse
what kernel did you apply and whats your devices specs i.e gsm or cdma etc
I'm GSM, using my own C and C ROM. Here's some info.
Kernel
Linux version 2.6.35.10-ga66971c ([email protected]) (gcc version 4.4.0 (GCC) ) #2 PREEMPT Fri Jan 6 12:42:25 PHT 2012
Battery
Battery Temp: 34.3° C (93.7° F)
Battery Level: 97%
CPU
Frequency: 768000 kHz
Load Average: 4.99 5.50 4.96 1/882 2160
Processor : ARMv6-compatible processor rev 5 (v6l)
BogoMIPS : 767.55
Features : swp half thumb fastmult vfp edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 5
Hardware : marvel
Revision : 0080
Serial : 0000000000000000
Time in State
120000 | 17185 | 11.92%
122880 | 0 | 0%
200000 | 1254 | 0.87%
245760 | 25510 | 17.7%
320000 | 5436 | 3.77%
400000 | 4896 | 3.4%
480000 | 4218 | 2.93%
600000 | 51630 | 35.82%
768000 | 14311 | 9.93%
787200 | 0 | 0%
806400 | 19695 | 13.66%
Memory
MemTotal: 428112 kB
MemFree: 17124 kB
Buffers: 1832 kB
Cached: 99156 kB
SwapCached: 0 kB
Active: 170404 kB
Inactive: 181640 kB
Active(anon): 125932 kB
Inactive(anon): 136504 kB
Active(file): 44472 kB
Inactive(file): 45136 kB
Unevictable: 10736 kB
Mlocked: 10428 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 261832 kB
Mapped: 58248 kB
Shmem: 644 kB
Slab: 14832 kB
SReclaimable: 3236 kB
SUnreclaim: 11596 kB
KernelStack: 7056 kB
PageTables: 20124 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 214056 kB
Committed_AS: 4057152 kB
VmallocTotal: 475136 kB
VmallocUsed: 161968 kB
VmallocChunk: 270340 kB
Sent from a Time Lord, using his TARDIS.
Please help as soon as possible.
Sent from a Time Lord, using his TARDIS.
Could be your new kernel pal
sent from my android powered beast!
Oh. It was working before. I'll try out a wipe. See where it gets me.
OK so I've done a factory reset, didn't work. Tried different kernels (bricked my phone cos I got the wrong one, lol), didn't help. Reflashed my kernel. No help. Please help me! I've got 2.3.5. Using Euro kernel. Maybe hardware issue. Recently switched to new network.
Bad-Wolf said:
Recently switched to new network.
Click to expand...
Click to collapse
No wonder it doesn't work
clean the sim card slot and make sure sim card is properly fitted in, if you do it correctly it will work.
Thanks, I'll try this layer today.
Sent from my HTC Wildfire S A510e using XDA
einstein.frat said:
clean the sim card slot and make sure sim card is properly fitted in, if you do it correctly it will work.
Click to expand...
Click to collapse
Took your advice, didn't work. I'll try some other stuff.
Please fix up the sig. It's nasty. It's worst than mine. No offence, but pretty much everyone I know would call it........ perverted............
I tried it in another phone, looks like the sim is faulty. Ill order a new one from orange.
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?