{
"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"
}
Official LineageOS 14.1 for Lenovo Vibe Z2 Pro
(kingdom_row/kingdomt)
Update to latest OTA-update (S288 or CN equivalent) before flashing this!
Lin·e·age /ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Known issues
Exporting contacts from phone to SIM is broken due to the changes in Android 7.1 SIM (batch) operations. Import from SIM works fine.
What is unlikely to be added
VoLTE support (impossible without proper support in modem firmware)
Touchscreen gestures (impossible without proper support in touchscreen firmware)
Overclocking (prohibited in official distributions)
What you need to know
Report device specific bugs to me, for the rest use the LineageOS Bug Tracker.
If you're coming from an older or unofficial CM/Lineage (14.0/13.0/...) do a wipe of ART Cache, Cache & Data.
I'm not responsible for anything that happens to you or your property.
Nobody is forcing you to flash this.
No ETAs.
OFFICIAL Builds (weekly):
LineageOS Downloads: https://download.lineageos.org/kingdom
Changelog: https://download.lineageos.org/kingdom/changes/
UNOFFICIAL Builds (outdated):
dd/mm/yyyy (SU/root included in all builds)
25/01/2017: https://mega.nz/#!UIw3xL5a!zdSJvdKUrYdxsqOVeL-Nu1nG5okeRsWScRgQKJpXHZc
04/01/2017: https://mega.nz/#!pEgVRAZB!2qCGtXgLMSrJ__gp3r7Z7XXfJVIE6unJFNrbfC2qaSw
25/12/2016: https://mega.nz/#!kd4lzJgZ!TPNE_tp22p_G62hlRHnSraqR5PN9xahvAIiENurMZ5s
23/11/2016: https://mega.nz/#!wNwUmRaT!ZNk_aNbWq-dgHYlOym9MkTYhVLWFv_h3eLVPyaSXerU
20/11/2016: https://mega.nz/#!UdwXUCTT!AQ-PPPHp-7lhgIAvyyJ_Tp3W7KQlcLB7nTAim4m-1u0
13/11/2016: https://mega.nz/#!lRhRQAYb!adanU8xZTjZerGbtzBk8jaBNT585zb73Su0mHQdBt-w
12/11/2016: https://mega.nz/#!JQhwRA6R!AE53FeuqFxKSS2ktpmbJ5MjW1dTACicbaY0rBhQgKIU
04/11/2016: https://mega.nz/#!sZp1zQyJ!EM4mn9cgbqoRCChmQj2AVzwBAclljRjZvOoJ3cYUbck (Disable signature verification)
30/10/2016: https://mega.nz/#!8BACFBqD!sBALhCbu2Sg4-VIkGzZEzVMt30wHxhZIC0-O7Wa2sV8
28/10/2016: https://mega.nz/#!BdgkXQrY!2_mjk_n4dDRUyHZCE7NDup3oO40TferTCclCEsUFqEQ
27/10/2016: https://mega.nz/#!tBRF2QLb!DLi_DHsUVfgKofg2-x7-VamEkdpcfcdpIbyciC2ffUQ
Builds by frantisheq: https://basketbuild.com/devs/frantisheq/kingdom_row/cyanogenmod
Useful links:
Google Apps: http://opengapps.org/ (use ARM 7.1)
TWRP: http://forum.xda-developers.com/android/development/recovery-team-win-recovery-project-3-0-t3454739
SU (root) addon: https://download.lineageos.org/extras (use ARM)
Official sub-reddit: https://www.reddit.com/r/LineageOS/
Special thanks for help and support
lockhrt999
cyprien T
mittar
northmantif
AntoSVK
leecs
iabanji1402
(if I forgot about you or you don't want to be here, send me a PM)
XDA:DevDB Information
LineageOS 14.1, ROM for the Lenovo Vibe Z2 Pro
Contributors
Electry, frantisheq
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-10-27
Last Updated 2017-05-09
Electry, thank you and frantisheq for your work! But could you please change the location of a build becase mega does not allow to download it due to the absence of an account?
Torch quick-tile works for me, NFC doesn't.
I noticed fishku.na 7.0 and 7.1 of the flashlight shutter does not work. .... But if the voice of google inc. Then everything works ....
Заметил фишку.на 7.0 и 7.1 фонарик из шторки не работает. ....но если голосовым из гугла вкл. Потом всё работает....
I guess the thing that won´t make me flash it right away is missing the OTA.
GREAT WORK from you guys, thank you!!!
new build up
You're awesome! It looks really great. Thank you
There´s something wrong with Wifi... can see the networks, but can´t connect. On Settings > Wifi I can turn on/off the wifi, on drag-down top bar I can´t, stays always on.
Maybe it´s just me.
time to retire i guess i have to ask everybody who wants to donate to send $ to Electry if it's possible and he agrees, not to me. as i wrote before this is mostly his work and i'm not really helping anymore, this ROM becomes "pixel perfect" thanks to him and he really deserves it
Sent from my K920 using Tapatalk
Hi electry, thank you for develop this rom for our K920! Ive tried to install it and I have the same issue that I had with CM14 a month ago, when I install it everything works except mobile network, when I enable it on the status bar it disable it automatically. I have a CN K920, could be modem compatibility problems?
Thank you
My experiences
- Speed is very good, smooth AF, no lags etc.
- Notificaion light: I can change the color and add aps, but cant set the brigthness
- Double tap to wake dont work. When i go to settings and i can turn it on, but dont work and when i go back to settings the switch is off.
- Torch tile works, NFC too
Question: It is possible that the notification light has higher priority than charging ligth? In stock rom when I was charging the phone and received a notification the ligh was pulse, as when the phone doesnt charge. (Sorry for bad einglish)
Thanks your hard work, have a good day
Do you help me to instal this amazing ROM on my k920 CN? Thanks for your help and your job.
Drug_Store said:
There´s something wrong with Wifi... can see the networks, but can´t connect
Click to expand...
Click to collapse
can confirm, is there a quick fix for wifi?
I have a problem after apply this unlock bootloader on my K920?* CN kitkat.
?*
Now I don't any partition. Specially "Preload" . It's strange all is ok with QFIL but the status bar is very quick to update the partition (roughly 10 seconds...). How can I rebuild all partion on my K920? Thanks!!!!
?*
LOG QFILE :
?*
Process Index:0
Programmer Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
Image Search Path:C:\UnlockBootloader_KK_CN
Please select the XML file
Start Download
Program Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
?*
?*?* ?* QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
?*
?*?* ?* QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:4
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xA5EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4ec
PROGRAM: Partition 0, Sector: 264232, Length: 1260 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\emmc_appsboot.mbn
PROGRAM: Written Bytes 0x9d800 (64)
Program Size: 0.62 MB
Total Size: 0.65 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6479492MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Download Fail:FireHose Fail Fail to find QDLoader port after switch
Finish Download
[ROM][7.1] CyanogenMod 14.1
Wifi dont work
Enviado desde mi iPad con Tapatalk and LTE
flashlite, double tap and wi-fi working fine, without any fixes
Krasimir said:
flashlite, double tap and wi-fi working fine, without any fixes
Click to expand...
Click to collapse
right? It's also working fine for me.
I have no idea why wifi doesn't work for some of you.
I'll try to revert the old wifi driver back, to see if that might be the problem.
Electry said:
right? It's also working fine for me.
I have no idea why wifi doesn't work for some of you.
I'll try to revert the old wifi driver back, to see if that might be the problem.
Click to expand...
Click to collapse
Updated 10. 30. and flashlight doesnt work :S. Wiped cache and dalvik but same. Wifi fine, double tap too. The battery parcentage show in status bar, but cant change the battery icon.
With latest 30/10 build can't connect wifi
NETWORK_SELECTION_DISABLED_ASSOCIATION_REJECTION=4 NETWORK_SELECTION_DISABLED_AUTENTICATION_FAILURE=4
Display goes crazy flashing red.
EDIT: As I assumed, wifi mac address is being read from NV in a reversed order, it should start with AC:38:70 (which is Lenovo's vendor tag). Some routers reject bad mac adresses, and therefore you aren't able to connect to any of them.
This should be fixed in next build.
Related
I'm the creator of Heimdall the cross platform Galaxy S flashing tool. I was wondering if any one has attempted to flash a Galaxy Tab using my tool?
I suspect that the protocol for flashing the Galaxy Tab is identical. However, I don't have access to a Galaxy Tab so I'm unable to test myself. I would love to add the Galaxy Tab to the list of officially supported devices if someone can confirm it works.
EDIT: Just realised I never updated this post. Heimdall has officially supported the Galaxy Tab for a while now.
I might be able to do it if I find some better firmware to flash. Not sure yet.
Sent from my SCH-I800 using XDA App
I'll give it a try later today. I'm a Linux zealot.
Install notes for Linux + a question
sorry -- wrong thread. No clue how to delete, but I don't want to cross-post so just ignore this.
I compiled and tried using it to flash a modem.bin, but got an error. Heres the console output:
Code:
$ heimdall flash --pit P1_20100909.pit --modem modem.bin
Heimdall, Copyright (c) 2010, 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/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Unexpected device info response!
Expected: 180 or 0
Received:3
Ending session...
Rebooting device...
Re-attaching kernel driver...
rotohammer, thanks for that. It seems as the initialisation process might be slightly different for the Galaxy Tab. Unfortunately the spot where it failed is the exact spot in the protocol that I have basically no clue about. The Galaxy S sends either 180 or 0, which is perhaps some sort of flags indicating the state of the device. Technically the flash could continue past there regardless of the value received but it's a bit of a safety net feature to stop right away.
I'll see if I can get my hands on a Galaxy Tab so I can get Heimdall working for Galaxy Tab users as well.
Works great
For those of you interested, I've modified the Heimdall source on Linux to accept the device info value of 3 and I have successfully flashed 2 different full firmwares on my T-Mobile Tab, as well as many individual files. It works much faster than Odin, and a lot less flaky. I let Benjamin know so he can include support in an upcoming release.
Thanks for the good work, Ben and Roto
Can Heimdall dump partititions from flash for backup?
Technomancer said:
Can Heimdall dump partititions from flash for backup?
Click to expand...
Click to collapse
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
I suppose the partitions are not mounted in the "downloading" mode, so any dumps from Heimdall should be better than dumps made using dd from the shell?
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
Hi Rotohammer!
Great work again
What did you use as chip-type and chip-id for dumping? I.e.
Code:
heimdall dump --chip-type ??? --chip-id ??? --output <filename>
Volker1 said:
What did you use as chip-type and chip-id for dumping?
Click to expand...
Click to collapse
Code:
heimdall dump --chip-type NAND --chip-id 0 --output hdump.img
I wrote a simple too to display information about PIT files (attached). The factory-installed PIT (/dev/block/bml2) on my T-Mobile US tab is identical to the one known as P1_20100909.pit and reads:
Code:
$ ./PITinfo bml2.dump
Contents of PIT file:bml2.dump
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x135d800 0x1 0 0x1331e17 0x2cf560
Number of partitions = 14 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [MOVINAND..)...*...p.i.t.........]
file name = [movinand.mst........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
I want to flash the Euro firmware (I'm back in Europe right now) by flashing P1000XWJJ4 (and then flash P1000XXJK5 on top). The P1_add_hidden.pit reads:
Code:
$ ./PITinfo P1_add_hidden.pit
Contents of PIT file:P1_add_hidden.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x1 0 0x411e17 0x12fae0 0x43d800
Number of partitions = 15 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [HIDDEN.D..)...*...p.i.t.........]
file name = [hidden.rfs.t........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
Partition #15
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file. So I guess I'm better off going the VirtualBox->Win32->Odin route?
Compile on Mac OS X
I've just successfully compiled libusb and Heimdall on Mac OS X.
I needed to set an environment variable by hand so that the "configure" of Heimdall detected libusb:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
Oh, and of course this source code modification is necessary for the Galaxy Tab to be supported:
main.cpp line 252:
if (unknown != 180 && unknown != 0 && unknown != 3)
Disclaimer: I haven't had time to try flashing anything yet.
I finally found the courage to flash my T-Mo US tab to Euro version. I made my own Franken-rom by combining P1000XWJJ4 with P1000XXJK5. Specifically, I
1. decompressed P1000XWJJ4.rar
2. took boot.bin, Sbl.bin, and dbdata.rfs from P1000XWJJ4/P1000XWJJ4_SERJJ2_XXJID/P1000XWJJ4-REV03-ALL-CL639474.tar.md5 (a tar archive despite the wrong ending)
3. decompressed P1000XXJK5.rar
4. took zImage, cache.rfs, factoryfs.rfs, modem.bin, and param.lfs from P1000XXJK5/P1000OXAJK5.tar
5. P1_20100909.pit
Then I rebooted my tab in download mode, plugged it into my PC's USB, and then flashed
Code:
$ ./heimdall flash --pit P1_20100909.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --boot boot.bin --secondary Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
Heimdall, Copyright (c) 2010, 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/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Downloading device's PIT file...
PIT file download sucessful
Uploading factory filesytem
Factory filesytem upload successful
Uploading cache
Cache upload successful
Uploading data database
Data database upload successful
Uploading primary bootloader
Primary bootloader upload successful
Uploading secondary bootloader
Secondary bootloader upload successful
Uploading param.lfs
param.lfs upload successful
Uploading kernel
Kernel upload successful
Uploading modem
Modem upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
I had my German SIM card in and after some booting I ended up with a perfectly working German-localized Euro tab. Switching the language back to US Englisch works fine, too.
Volker1 said:
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file.
Click to expand...
Click to collapse
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
daniel.weck said:
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
Click to expand...
Click to collapse
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
It's zero, if we trust the output of the PIT reader utility:
http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
Benjamin Dobell said:
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
Click to expand...
Click to collapse
Well 0 is the primary bootloader, so right now I'm not trusting it.
Does anyone have any idea what the contents of movinand.mst is? Because I just figured out how to flash the recovery partition directly.
EDIT: And the EFS.
NOTE: the log below pertains to KB5...I haven't had time yet to look into KB6.
http://www.samfirmware.com/WEBPROTECT-p1010.htm
ro.build.display.id=FROYO.XWKB5
ro.build.version.sdk=8
ro.build.version.release=2.2.1
ro.build.date=Thu Feb 17 19:34:43 KST 2011
I'm going to unpack the various RFS archives, to see what's new. I've got a GT-P1000 Galaxy Tab (wifi+3G), so I'm not going to flash with Heimdall (let alone Odin ).
I made backups for factoryfs.rfs / dbdata.rfs etc. using the usual bit-by-bit "dd" -based method, and I've got a trusty TitaniumBackup archive ready, just in case
I notice that TV-out seems to be gone, and FM radio appears to be available. Hardware DSP support seems more present too. (read content logs below for more information)
TAR contents:
Code:
p1wifi_20110128_r10_00.pit (4 KB) (see PIT-info dumped below)
GT-P1010-CSC-SERKB3/
cache.rfs (10.9 MB) (see content listing below)
movinand.mst (51MB) (can be extracted with [URL="http://movitool.ntd.homelinux.org/trac/movitool/"]MoviTool[/URL], based on [URL="http://forum.xda-developers.com/showpost.php?p=9481702&postcount=30"]Volker1's method[/URL])
P1010XWKB5-REV03-ALL-low-CL913814/
boot.bin (256 KB)
cache.rfs (672 KB)
normalboot.img (4.3 MB)
param.lfs (612 KB)
recovery.img (4.3 MB)
Sbl.bin (1.2 MB)
system.rfs (331 MB)
userdata.rfs (1.2 MB)
Output from Volker1's PIT-info utility:
Code:
Contents of PIT file: p1wifi_20110128_r10_00.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0 0 0 0 0
Number of partitions = 13 (usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [p1wifi.pit......................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x5; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [NORMALBOOT......................]
file name = [normalboot.img..................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [recovery.img....................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1430 blocks of 256 * 512 bytes = 187432960 B = 183040 kB = 178 MB
unknown string: [........]
partition name = [SYSTEM..........................]
file name = [system.rfs......................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 302 blocks of 256 * 512 bytes = 39583744 B = 38656 kB = 37 MB
unknown string: [........]
partition name = [USERDATA........................]
file name = [userdata.rfs....................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [HIDDEN.D........................]
file name = [hidden.rfs.t....................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
The usual CSC cache.rfs content:
Code:
/dbdata/svox/de-DE_gl0_sg.bin
/dbdata/svox/de-DE_ta.bin
/dbdata/svox/en-GB_kh0_sg.bin
/dbdata/svox/en-GB_ta.bin
/dbdata/svox/en-US_lh0_sg.bin
/dbdata/svox/en-US_ta.bin
/dbdata/svox/es-ES_ta.bin
/dbdata/svox/es-ES_zl0_sg.bin
/dbdata/svox/fr-FR_nk0_sg.bin
/dbdata/svox/fr-FR_ta.bin
/dbdata/svox/it-IT_cm0_sg.bin
/dbdata/svox/it-IT_ta.bin
/system/csc/feature.xml
/system/csc/contents.db
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/customer.xml
/system/app/MusicODC.apk
/system/T9DB/qwerty_fi.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_da.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/phonepad_lt.kdb
/system/T9DB/Samsung_400_TRlsUN_xt9.ldb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/Samsung_400_ETlsUN_xt9.ldb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/qwerty_sv.kdb
/system/T9DB/Samsung_400_DAlsUN.ldb
/system/T9DB/phonepad_uk.kdb
/system/T9DB/phonepad_it.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_UKlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_et.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/phonepad_no.kdb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/qwerty_lt.kdb
/system/T9DB/Samsung_400_LVlsUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/phonepad_da.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/phonepad_et.kdb
/system/T9DB/Samsung_400_KKlsUN_xt9.ldb
/system/T9DB/phonepad_es.kdb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/phonepad_ru.kdb
/system/T9DB/phonepad_tr.kdb
/system/T9DB/qwerty_tr.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_FIlsUN_xt9.ldb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_fi.kdb
/system/T9DB/qwerty_ru.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/qwerty_en.kdb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_NOlsUN.ldb
/system/T9DB/Samsung_400_RUlsUN_xt9.ldb
/system/T9DB/qwerty_kk.kdb
/system/T9DB/qwerty_no.kdb
/system/T9DB/qwerty_uk.kdb
/system/T9DB/phonepad_lv.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_LTlsUN_xt9.ldb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/qwerty_lv.kdb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/qwerty_it.kdb
/system/T9DB/phonepad_hu.kdb
/system/CSCFiles.txt
/system/SW_Configuration.xml
Changes in /system/app/ :
Removed DailyBriefing, Ebook, Mms, MobileTrackerEngineTwo, MobileTrackerUI, OtaProvisioningService, SamsungWidget_WeatherClock, SoundRecorder, signin, syncmldm, wipereceiver, wssomacp
Added PhoneCrashNotifier, PopupuiReceiverf, qik, qikhelp, skype
Changes in /system/bin/ :
Too many to list, but here are some notable ones:
Removed BCM4329B1_002.002.023.0534.0590.hcd (the driver for the multi-function Broadcom BCM-4329 chipset, also removed in /etc/wifi/ etc.), akmd2 (the multi-sensor driver, now split into several sub-daemons: geomagnetic, gyroscope, temperature, light, orientation, pressure, proximity, etc.)
Notable changes in /system/etc/ :
Added audio/codec/FMRadioEar.ini, audio/codec/FMRadioSpk.ini, and FM-radio stuff in /etc/firmware/ and /lib/libfmradio_jni.so (the Texas Intruments BRF6350 chip supports FM radio...but I don't think that /system/app/ contains an FM tuner application).
Notable addition: /lib/dsp/ + /lib/libOMX*.so + /lib/libVendor_ti_OMX*.so + lib/libaomx_*.so (Texas Intruments OMX/DSP, hardware encoding/decoding of 720p AMR, WB-AMR, AAC, h264, WMA, WMV, MP3, MPEG4, Flac, AC3, S263, etc.)
Code:
720p_h264vdec_sn.dll64P
720p_mp4vdec_sn.dll64P
720p_mp4venc_sn.dll64P
baseimage.dof
baseimage.map
chromasuppress.l64p
conversions.dll64P
dctn_dyn.dll64P
ddspbase_tiomap3430.dof64P
dfgm.dll64P
dynbase_tiomap3430.dof64P
eenf_ti.l64P
h264vdec_sn.dll64P
h264venc_sn.dll64P
ipp_sn.dll64P
jpegdec_sn.dll64P
jpegenc_sn.dll64P
m4venc_sn.dll64P
monitor_tiomap3430.dof64P
mp3dec_sn.dll64P
mp4v720parcdec_sn.dll64P
mp4varcdec_sn.dll64P
mp4vdec_sn.dll64P
mpeg4aacdec_sn.dll64P
mpeg4aacenc_sn.dll64P
mpeg4aridec_sn.dll64P
nbamrdec_sn.dll64P
nbamrenc_sn.dll64P
postprocessor_dualout.dll64P
qosdyn_3430.dll64P
ringio.dll64P
star.l64P
usn.dll64P
vpp_sn.dll64P
wbamrdec_sn.dll64P
wbamrenc_sn.dll64P
wmadec_sn.dll64P
wmv9dec_sn.dll64P
yuvconvert.l64p
Wifi access point doesn't seem very well protected (/etc/wifi/softap/hostapd.conf):
SSID = AndroidAP (not broadcast)
IP = 192.168.43.1
PASS = "password" (WPA)
By the way, the Wifi interface is different than on the fully-featured Tab: tiwlan0 (the access point is tiap0)
Nice let us know what's new and how you make out
This is great news and I am looking forward to your project, thanks!!!
Heads-up: original post updated with PIT partition structure and TAR contents.
Original post updated with further information (FM radio, DSP, etc.). None of this is authoritative, obviously. I am just making plain observations. I haven't even seen the manufacturer's specifications yet for this device.
Splice/combine the ROM with a P1000 ROM?
Cool. Does this mean that your aim to splice/combine the ROM with a P1000 ROM to create a custom Android 2.2.1 ROM WITH 3G capabilities, that is compatible with P1000?
And in that case, it sure would be nice to keep most of what has been removed from /system/* in the P1010 ROM, of course.
Very interesting, thanks for posting the analysis.
I wonder whether GL drivers are any newer than from P1000 ROMs.
And GPS daemon?
Also, interesting about these split sensor drivers.
edit
hmm, interesting, the GL drivers are for SGX530 not 540 like in normal tab.
And the CPU in 1010 is OMAP3 not Hummingbird.
KB6 now online @ Samfirmware.
I'm too busy to look into it though.
Hi,
I just got the Wifi version. How can I check the ROM version?
does the P1010 still have a gps radio?
jackfrostn said:
does the P1010 still have a gps radio?
Click to expand...
Click to collapse
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
could someone try getting the skype and qik files working
any update on the ROMs progress?
bthoven said:
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
Click to expand...
Click to collapse
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
himmelhauk said:
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
Click to expand...
Click to collapse
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
bthoven said:
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
Click to expand...
Click to collapse
Actually it is worth making a correction here as well, it plays 1080 just fine as well, at least for me.
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
chrisliphart said:
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
Click to expand...
Click to collapse
In all the TI OMAP libraries and kernel in the ROM?
skype for p1010 wifi
Skype will work with regular rom.i used it all day today
Yes, it does have gps radio on there. Well mine does anyway (in the uk)
plz.. help me.. my smartphon Not started...I tried everything but ROM- No Entry
Cmd>task 32
task 32
Level = 0
Cmd>lnbs mymac.bin 75108000
lnbs mymac.bin 75108000
Format by TrueFFS ver.: 7.1.0
:F=mymac.bin
:A=75108000
:O=00000000
:L=FFFFFFFF
start NB image download
SH
Load ADDR: 75108000 Length: 13
Programming DOC flash blocks by serial port...
Buffer=4M,0x400000
DOCInfoTableinitHW+
Binary0 Size: 0x200000
FAT0 Size: 0x5000000
FAT1 Size: 0xB00000
FAT2 Size: 0x9080000
All Size: 0xED80000
FAT0_ADDR=0x200000,FAT1_ADDR=0x5200000,FAT2_ADDR=0 x5D00000
ERROR: NO header matched
Transfer CERT error
Flash Programing Error
Please help me
Hello,
I'm french guy sorry for my english writting.
I'm searching about a pit file for my note 10.1 2014 edition. I have a memory use probleme, she use almost 14Go for systeme memory. I'v had the same probleme with my Gt-N5110 and flashing with pit file and repartition fixed it.
Thanks a lot for your helping.
See you soon
slovik1024 said:
Hello,
I'm french guy sorry for my english writting.
I'm searching about a pit file for my note 10.1 2014 edition. I have a memory use probleme, she use almost 14Go for systeme memory. I'v had the same probleme with my Gt-N5110 and flashing with pit file and repartition fixed it.
Thanks a lot for your helping.
See you soon
Click to expand...
Click to collapse
I'v tryed to extract .PIT from my Note with EFS professional. It's doesn't work.
Anybody knows another program to do the same think?
Thanks
up
anyone?
tdunks said:
anyone?
Click to expand...
Click to collapse
trying to do that with heimdall, it doesn't work.
Code:
heimdall download-pit --output sm-p600.pit --verbose
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...
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface...
lightman33 said:
trying to do that with heimdall, it doesn't work.
Code:
heimdall download-pit --output sm-p600.pit --verbose
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...
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface...
Click to expand...
Click to collapse
well this is above my level but my tablet is as good as bricked without it,
See here:
http://forum.xda-developers.com/showthread.php?p=48910857#post48910857
thanks...but pit file doesn't work on my 32Gb SM-P600.
what pit file you used to solve the problem with the gt-n5110?
I'm trying but I receive the message "Get pit for mapping..."
Where my I get the pit file you used?
jpbbarros said:
what pit file you used to solve the problem with the gt-n5110?
I'm trying but I receive the message "Get pit for mapping..."
Where my I get the pit file you used?
Click to expand...
Click to collapse
i'm uploading it on dropbox. I'll MP the link when i'ts done
This is a link:
https://www.dropbox.com/s/dpipmb45xfof0et/kona_wifi.pit
Thank you.
Well, I applied the partitions of this file but still the same!
At startup rom's logo appears but then the does not advance!
This started when I tried to install a new rom!
What can I do?
jpbbarros said:
Well, I applied the partitions of this file but still the same!
At startup rom's logo appears but then the does not advance!
This started when I tried to install a new rom!
What can I do?
Click to expand...
Click to collapse
Did you trie o wipe in recovery?
Yes, at the end, I reboot and did a wipe.
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?