Develop Bugs

| bml0!c | reset flash counter in bml15 . analyze bml0!c in oneNAND

we gingerbread guys need to get serious on this fricken flash counter, else we can't truely clone our SGYs.
reedit: by this time Doky has found it in bml15 and resets it in his galaxy tool app. ty !!
Kies knows about it and it has implications for asec stuff too.
manufacturing tried to keep the info on the flash counter's whereabouts a tightly guarded secret like some Bill Clinton sex affair, but now it is busted all out in the open ! <-- link
we gotta be able to reset that data to a fricken pristine state!
then we got a 100% CLONE !!
quote :
The flash counter and triangle state had to be stored somewhere. Everybody knew that ... You can dump and compare the entire /dev/block/mmcblk0 and you won't find a difference (you'll find a few unallocated and unused gaps, though).
on SGY mmcblk0 is the sd card, /dev/block/bml0!c = total internal NAND storage - which is what we are looking for. see: http://forum.xda-developers.com/showthread.php?t=1998471
however, the flash disk actually has two hidden boot partitions,
/dev/block/mmcblk0boot0 and
/dev/block/mmcblk0boot1
The MMC driver in the kernels used for Gingerbread did not present these partitions in the past, the MMC driver in the ICS kernel does.
Dump and compare the partitions and you'll have found them in no time.
Structure /dev/block/mmcblk0boot0 @ 0x00020000:
0x00020000 header magic: 32bit - 0x12340011
0x00020004 flash count: 16bit
0x00020006 future: 16bit - 0x0000
0x00020008 type: 16bit - 0x0000 unknown, 0x0001 custom (triangle), 0x0002 Samsung Official
0x0002000A name: max 16 chars
0x0002001A end: 16bit - 0x0000
The boot partitions are presented as readonly by default, but allowing modification is a simple matter of executing the following before writing the data:
### does not fullly apply to SGY ! other phones only !! ###
echo 0 > /sys/block/mmcblk0boot0/force_ro
A number of bytes trailing this structure also change between flashes and appear to be checksum related.
click Tags below for more related info !

neither I'm able to confirm nor negate, but I'm afraid the SGY have other storage areas.
and keep in mind, on SGSII this hidden device has appears only on the leaked beta ICS kernel. Moreover I don't see any good reason, why is it accessible under Android. Kies does not care about the bin counter. I was able to restore factory state with bin counter>0 and Kies recognized my devce as valid upgradeable. On the other hand, the bin counter is handled on the sbl runlevel, where kernel and android not yet loaded.
For further reference please see my research on the SGY partition system, decoded from the pit file:
Code:
[B]minor bml stl image[/B]
1 /bml1 /stl1 BcmBoot.img
2 /bml2 /stl2 sbl.bin
3 /bml3 /stl3 bl.bin
4 /bml4 /stl4 totoro.pit
5 /bml5 /stl5 BcmCP.img
6 /bml22 /stl6 param.lfs
7 /bml6 /stl7 boot.img
8 /bml7 /stl8 (boot backup)
9 /bml21 /stl9 system.img
10 /bml23 /stl10 csc.rfs
11 /bml24 /stl11 userdata.img
12 /bml8 /stl12 (efs)
13 /bml9 /stl13 sysparm_dep.img
14 /bml10 /stl14 HEDGE_NVRAM8_RF_LE.bin
15 /bml11 /stl15 (cal)
On much deeper details please see my spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0Arilp8uJromLdHdrdGpiZ2FSN3daRzRQMkIxR0pCZXc
Minor #12 and #15 is suspicious, might have some data, which not used by the OS, and not affected by ROM update packs.

This is good research, doky. I bookmarked your spreadsheet for future reference.

efs
Doky73 said:
12 /bml8 /stl12 (efs)
15 /bml11 /stl15 (cal)
Minor #12 and #15 is suspicious, might have some data, which not used by the OS, and not affected by ROM update packs.
Click to expand...
Click to collapse
efs is directly related to the SIM card file system, I take it.
"the /efs folder is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location."

<post deleted>

cal : calibration data
Doky73's SGY layout table: now, spot the flash counter
minor Start-offset --- End-offset ------ Size (hex) units ------- SIZE (bytes) -- BML --------- STL -- Internal name Image name ------ Description
01 0x00000000 0x00040000 0x00040000 001 000262144 /bml1 _/stl1 _bcm_boot BcmBoot.img Primitive boot loader
02 0x00040000 0x00240000 0x00200000 008 002097152 /bml2 _/stl2 _Loke sbl.bin Secondary boot loader
03 0x00240000 0x00440000 0x00200000 008 002097152 /bml3 _/stl3 _loke_bk bl.bin backup sbl
04 0x00440000 0x00480000 0x00040000 001 000262144 /bml4 _/stl4 _systemdata totoro.pit partition table
05 0x00480000 0x01100000 0x00c80000 050 013107200 /bml5 _/stl5 _Modem BcmCP.img modem/phone
06 0x01100000 0x01600000 0x00500000 020 005242880 /bml22 /stl6 _param_lfs param.lfs
07 0x01600000 0x01b00000 0x00500000 020 005242880 /bml6 _/stl7 _boot boot.img kernel & initramfs
08 0x01b00000 0x02000000 0x00500000 020 005242880 /bml7 _/stl8 _boot_backup - backup kernel & initramfs
09 0x02000000 0x10600000 0x0e600000 920 241172480 /bml21 /stl9 _System system.img ROM
10 0x10600000 0x12e00000 0x02800000 160 041943040 /bml23 /stl10 Cache csc.rfs CSC
11 0x12e00000 0x1f340000 0x0c540000 789 206831616 /bml24 /stl11 Userdata userdata.img data
12 0x1f340000 0x1f380000 0x00040000 001 000262144 /bml8 _/stl12 Efs - efs unique phone data
13 0x1f380000 0x1f3c0000 0x00040000 001 000262144 /bml9 _/stl13 sysparm_dep sysparm_dep.img
14 0x1f3c0000 0x1f400000 0x00040000 001 000262144 /bml10 /stl14 umts_cal HEDGE_NVRAM8_RF_LE.bin
15 0x1f400000 0x1f500000 0x00100000 004 001048576 /bml11 /stl15 cal - calibration data
note: not all /bml & /stl devices are visible, some of them not linked under the OS
------------------------------------------------------------
I guess, cloning all of minor 12 would be a mistake.
14 & 15 are sets of calibration data, probably for RF part (gsm radio)

mai77 said:
Darky's SGY layout table: now, spot the flash counter
Click to expand...
Click to collapse
Well, Darky is working on a custom rom for SGY???
Yep, we're saved!

Factory mode
also there is a difference between ODIN mode (via DOWN+HOME+POWER) and FACTORY MODE via USB jig 301KOhm.
makes a diff for displayed "official" vs. "custom" ROM

Any new ideas on this guys? I was wondering if this cant be hacked via the .pit file?
I wish I could find this damn partition and forcefully reset this

Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100

Princeomi said:
Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100
Click to expand...
Click to collapse
Are you sure?where did uou get that info??
Sent from my GT-S5360 using xda premium

Princeomi said:
Apparently the max count is 255 so if you flash it the 256th time you should be on zero. Take this info with a pinch of salt.
Sent from my GT-I9100
Click to expand...
Click to collapse
Very interesting bro
Hmmmm.... That actually does make sense to me, because due to screen size limitations, I can't see the numbers carrying on into infinity. As it is when it gets to the teens, it starts screwing up the text on screen, so an ultimate limit would make sense.
I guess besides the fact that it voids your warranty if anybody had to see it from Samsung, I guess it does nothing but just annoy you cause you cant reset it
Not sure if I will try your method Princeomi but I will keep that in mind
---------- Post added at 08:23 PM ---------- Previous post was at 08:09 PM ----------
What I don't understand though is why does the USB jig not reset it on our phones but it does on the SGS2? I just watched a vid on you tube and Odin mode looks exactly the same as it does on our phones.

I read it in the news section of XDA, never tried it though as I am on zero
Sent from my GT-S5360

NanoSurfer said:
[/COLOR]What I don't understand though is why does the USB jig not reset it on our phones but it does on the SGS2? I just watched a vid on you tube and Odin mode looks exactly the same as it does on our phones.
Click to expand...
Click to collapse
actually it does not resets neither on SGSII. Only on some old/initial ROMs. The SBL has been modified by Samsung, to prevent users resetting the counter simply by USB JIG. To reset my SGSII's counter, I have to downgrade the SBL. (or upgrade to ICS , there's an other method, based on a new feature of the 3.x kernel)
Sent from my SGSII using Tapatalk 2 & Swype

Doky73 said:
actually it does not resets neither on SGSII. Only on some old/initial ROMs. The SBL has been modified by Samsung, to prevent users resetting the counter simply by USB JIG. To reset my SGSII's counter, I have to downgrade the SBL. (or upgrade to ICS , there's an other method, based on a new feature of the 3.x kernel)
Sent from my SGSII using Tapatalk 2 & Swype
Click to expand...
Click to collapse
Interesting Sir Doky
I kinda figured that Samsung would wise up to that trick sooner or later. BTW what you think of the max count trick?

doky's SGY partn table from above attached
remember,
dd if=/dev/block/bml0!c
gives you the complete NAND storage 501 MB file on SGY:
so this shell cmds gave me a 501 MB file which is probably the NAND dump :
adb shell
su
stop
dd if=/dev/block/bml0!c of=/sdcard/bml0c.outfile
## wait 2 minutes to finish
start
## wait 30 sec
I believe, the last 1 MB of the file is junk data or duplicate

bml0!c dump
the dump says:
OneNAND boot rev. 0.2
+cboot_uart_speed_handshake(0x%x)
Set Baudrate to 115k.
Set Baudrate to 230k.
¼:”Set Baudrate to 460k.
Set Baudrate to 921k.
Set Baudrate to 3m.
Invalid Baudrate, try again.
cboot_uart.c
assert at line %d in %s -cboot_uart_speed_handshake

###################################
Secondary Bootloader v3.1 version. Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: %s %s / %s %s TOTORO REV 03 Jan 14 2012 07:01:28
%s: debug level 0x%x %s: debug level low! PUMR: %d FOTA_BOOT FOTA_UAUP PUMR: 0x40 (AP only boot mode) loadmodem loadCPDATA loadkernel
boot SBL> %s: parse command error! (%s)
Autoboot (%d seconds) in progress, press any key to stop
Autoboot aborted..
booting code=0x%x stl init failed.. %s: j4fs_open.. success failed %s: bye~ bye! %s: booting stop.
%s: booting stop and power off..
S5360 console=ttyS0,115200n8 mem=362M kmemleak=off root=/dev/ram0 rw
androidboot.console=ttyS0 /mnt/rsv SNBL main
#############
prob. kernel command line for UART FOTA boot or whatever
#############
loke_exit
loke_init
command_loop
boot_kernel
SERIAL_SPEED LOAD_RAMDISK BOOT_DELAY LCD_LEVEL SWITCH_SEL PHONE_DEBUG_ON LCD_DIM_LEVEL LCD_DIM_TIME MELODY_MODE REBOOT_MODE NATION_SEL LANGUAGE_SEL SET_DEFAULT_PARAM PARAM_INT_13 PARAM_INT_14 VERSION CMDLINE DELTA_LOCATION PARAM_STR_3 PARAM_STR_4
mtdparts=bcm_umi-nand: %[email protected]%dK(%s)ro, %[email protected]%dK(%s)rw, fota_reboot FOTA
Boot cause : %s FOTA_BOOT FOTA_UAUP LOKE3 : FOTA_UPDATE_FOTA_BOOT
BOOT_FOTA=1 BOOT_FOTA=0
ATAG_CORE: %x
ATAG_INITRD2: %x

Linux-based NAND Flash software solution, offering higher performance and cost effectiveness for next-generation mobile phones. Samsung's Linux NAND Flash memory software allows the NAND Flash memory to store code as well as data. By eliminating the need for NOR Flash memory and supporting the Linux operating system with a demand-paging function, Samsung can lower overall costs and reduce space requirements in mobile handhelds.
Samsung's Linux file system, Robust File System (RFS), also offers greater data preservation capabilities in case of power disruption as well as wear-leveling for higher reliability. To address the problem of data loss from corrupted file allocation tables (FAT), Samsung's Linux-based NAND Flash memory solution also supports Transactional FAT for external memory cards. Compared to the conventional JFFS2 and YAFFS open file systems, Samsung's Linux file system enhances the NAND Flash write-speed up ten and four times , respectively.
This Flash memory solution is also available with Samsung's OneNAND (tm) Flash memory, which boasts a faster read speed compared to the conventional NAND Flash. With its advanced multi-tasking function, Linux will further accelerate the adoption of NAND Flash in next-generation mobile phones.
Importantly, as Samsung's new Linux NAND Flash memory software, RFS has completed verification in the Linux kernel 2.4.20-based Montavista Linux environment, Samsung's NAND Flash solution addresses the diverse needs of system developers for advanced performance, high reliability, shortened development time, and reduced costs.

SGY heimdall
with UBI running on oneNAND and UBIfs we SGY users can have our own "mobile ODIN" and Heimdall.
UBI is open source and part of the Linux kernel.

[Q] Cyanogenmod on Samsung Note 2 (i605)

I'm running in to the following error when attempting to flash my Samsun Note 2 (i605). Can anyone provide some help on getting past this issue?
I've used adb to reboot the device into download and attempted to run the below.
Here is the resources I'm using
Instructions I'm using are here: Wiki CyanogenMod on Samsung Galaxy Note 2 LTE (Verizon) ("i605")
Using Heimdall Suite v1.4.0
Recovery: recovery-clockwork-6.0.4.3-i605.img
On MAC: OSx 10.9.5
Here is the output
#sudo heimdall flash --RECOVERY recovery-clockwork-6.0.4.3-i605.img --no-reboot --verbose
Heimdall v1.4.0
Copyright © 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 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...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
14%
28%
42%
56%
70%
84%
98%
100%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...

I'm not a big fan of clockworkmod recovery...
Install twrp http://teamw.in/project/twrp2/133

FUSIONdev said:
I'm not a big fan of clockworkmod recovery...
Install twrp teamw.in/project/ twrp2/133
Click to expand...
Click to collapse
Can you clarify one thing. I"m guessing the instructions on that page may be out of date? When I go there from my Samsung Galaxy Note 2 (verizion i605), it doesn't download goo manager. It brings up TWRP Manager (ROOT) by Jmz Software. Is this correct?

jjones312 said:
Can you clarify one thing. I"m guessing the instructions on that page may be out of date? When I go there from my Samsung Galaxy Note 2 (verizion i605), it doesn't download goo manager. It brings up TWRP Manager (ROOT) by Jmz Software. Is this correct?
Click to expand...
Click to collapse
You have to install this! https://play.google.com/store/apps/details?id=com.s0up.goomanager

FUSIONdev said:
You have to install this! (this link your posted goes here.. noobs can't post URLs yet./QUOTE]
I'd love to but that link returns "We're sorry, the requested URL was not found on this server.", when browsing to that URL on phone or laptop.
Do you have an alternate download? and if so, can I install using ADP?
I was able to download "openrecovery-twrp-2.3.1.1-t0ltevzw.img" from the direct download link.
Click to expand...
Click to collapse

jjones312 said:
FUSIONdev said:
You have to install this! (this link your posted goes here.. noobs can't post URLs yet./QUOTE]
I'd love to but that link returns "We're sorry, the requested URL was not found on this server.", when browsing to that URL on phone or laptop.
Do you have an alternate download? and if so, can I install using ADP?
I was able to download "openrecovery-twrp-2.3.1.1-t0ltevzw.img" from the direct download link.
Click to expand...
Click to collapse
Just search "GooManager" on play store... by Snipanet Apps
Click to expand...
Click to collapse

FUSIONdev said:
jjones312 said:
Just search "GooManager" on play store... by Snipanet Apps
Click to expand...
Click to collapse
Thanks.. But unfortunately when searching for "GooManager" it doesn't return anything w/ that name or by that company/dev. Searching for Snipanet Apps returns nothing.
Searching "GooManager" returns the following list in order (first 10)
TWRP Manager (ROOT) by Jmz Software
ROM Manager by ClockworkMOd
Flashify (for root users) by Christian Gollner
ROM Installer by JRummy Apps
Superuser by ClockworkMod
Recovery Manaer by joeykrim
[ROOT]Rashr - Flash Tool by DsLneXus
Goodev Download Manager by goodev
Gapps Manager by Weidi Zhang
Click to expand...
Click to collapse

jjones312 said:
... cut ...
Click to expand...
Click to collapse
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this https://goo.im/devs/OpenRecovery/t0ltevzw/openrecovery-twrp-2.7.2.1-t0ltevzw.img.tar
(flash using the "AP" button and selection on Odin v3.09 or newer version)
-If you prefere or use Linux, you can use the DD method described on the page I linked on my first reply (http://teamw.in/project/twrp2/133)
EDIT:
OK I'm an Idiot xD you are a mac user... so with heimdal flash this: https://goo.im/devs/OpenRecovery/t0ltevzw/openrecovery-twrp-2.7.2.1-t0ltevzw.img
I suggest you to flash 2.7.2.1 version (as I linked to you) because it's stable and I had some issues with 2.8.0 version... fixed on 2.8.1, but it's not available for your device...

FUSIONdev said:
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this site removed
(flash using the "AP" button and selection on Odin v3.09 or newer version)
-If you prefere or use Linux, you can use the DD method described on the page I linked on my first reply site removed)
EDIT:
OK I'm an Idiot xD you are a mac user... so with heimdal flash this: site removed
I suggest you to flash 2.7.2.1 version (as I linked to you) because it's stable and I had some issues with 2.8.0 version... fixed on 2.8.1, but it's not available for your device...
Click to expand...
Click to collapse
Thanks for the info and links..
So... The fun begins
I have Heimdall version 1.4.0 installed along with ADP. Here is the steps I did to attempt to flash TWRP.
1. Rebooted MAC
2. Connected Phone
3. ran ./ADP reboot download
4. ran heimdall detect (found device)
5. based on some issues I noted at Cyanogendmod with heimdall and Samsung drivers did the follow to unload drivers
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
6. sudo heimdall flash --RECOVERY openrecovery-twrp-2.7.2.1-t0ltevzw.img --no-reboot
Here is the output from the screen:
sudo heimdall flash --RECOVERY openrecovery-twrp-2.7.2.1-t0ltevzw.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
site removed
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:
site removed
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
air:Mac Jesse$

Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9

FUSIONdev said:
Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9
Click to expand...
Click to collapse
Here is what happens running that from download mode
jesses-air:Mac Jesse$ heimdall detect
Device detected
jesses-air:Mac Jesse$ sudo ./adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
error: device not found
jesses-air:Mac Jesse$
Also tried to ./adb kill-server and ./adb start-server

You have to make these steps with phone in normal mode, not download mode...

FUSIONdev said:
Did you try just the DD method ?
adb push openrecovery-twrp-2.7.2.1-t0ltevzw.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.7.2.1-t0ltevzw.img of=/dev/block/mmcblk0p9
Click to expand...
Click to collapse
By the way thanks for the help so far..
I'm not rooted so getting
/dev/block/mmcblk0p9: cannot open for write: Permission denied
gotta root first correct?
sorry if silly questions.. First time
Android v 4.4.2
i605VRUFND7
Kernel v 3.0.31

jjones312 said:
By the way thanks for the help so far..
I'm not rooted so getting
/dev/block/mmcblk0p9: cannot open for write: Permission denied
gotta root first correct?
sorry if silly questions.. First time
Android v 4.4.2
i605VRUFND7
Kernel v 3.0.31
Click to expand...
Click to collapse
You can try to root easily using https://towelroot.com/
(ps check that you enabled USB Debugging on developer settings)

I tried Towel Root. it said my device was not supported. I'm going to try to get a Windows PC today..
USB debugging is on

FUSIONdev said:
Ok... so you have two alternatives.
-If do you have a windows pc, flash with ODIN this (site link removed for allow noob topost)
(flash using the "AP" button and selection on Odin v3.09 or newer version).
Click to expand...
Click to collapse
Do you have a link to Odin.exe? Initially I tried just google searching and downloaded an Odin.exe that installed malware etc etc.. (i'm cleaning that PC now). From what I understanding Odin is a stand-alone app that doesn't install, just runs.
thanks!
ps: I have an Windows PC to attempt from

jjones312 said:
Do you have a link to Odin.exe? Initially I tried just google searching and downloaded an Odin.exe that installed malware etc etc.. (i'm cleaning that PC now). From what I understanding Odin is a stand-alone app that doesn't install, just runs.
thanks!
ps: I have an Windows PC to attempt from
Click to expand...
Click to collapse
I think I found it by searching here in the forum.
http://forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539

That link doesn't appear to have download links to Odin 3.09 anymore? Know where it can be found?

jjones312 said:
That link doesn't appear to have download links to Odin 3.09 anymore? Know where it can be found?
Click to expand...
Click to collapse
You have no luck with this root xD
I uploaded it for you: https://www.dropbox.com/s/up732djqp0ysmhv/Odin_v3.09.zip?dl=0
Maybe you will need to install drivers before: http://d-h.st/a7H
Remember to reboot the phone...
Odin must show the COM port with blu background... then you can flash the package (remember to select it on AP)
{
"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"
}

FUSIONdev said:
You have no luck with this root xD
I uploaded it for you: https://www.dropbox.com/s/up732djqp0ysmhv/Odin_v3.09.zip?dl=0
Maybe you will need to install drivers before: http://d-h.st/a7H
Remember to reboot the phone...
Odin must show the COM port with blu background... then you can flash the package (remember to select it on AP)
View attachment 2971173
Click to expand...
Click to collapse
Just tried and got the following. in the message windows:
<ID:0/003>Added!!
<ID:0/003>Odin v.3engine (IE:3)
<ID:0/003>File analysis...
<ID:0/003>SetupConnection..
<ID:0/003>Initialization..
<ID:0/003>Get PIT for mapping..
<ID:0/003>Firmware update start..
<ID:0/003>SingleDownload.
<ID:0/003>recovery.img
<ID:0/003>NAND Write Start!!
<ID:0/003>
<ID:0/003>Complete(Write) operation failed.
<OSM>All threads completed. (success 0 / failed 1)
Starting to research that error.

Error flashing bootloader with heimdall

I need to update the bootloader on a T705 in order to run the Marshmallow ROM. Got the correct sboot.bin file but attempting to flash with heimdall gives the error "Failed to confirm end of file transfer sequence!":
Code:
# heimdall flash --BOOTLOADER sboot.bin
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Can't use odin as I don't have a windows machine.
My pit shows the bootloader as read-only and zero bytes:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
Is that normal or does it mean the bootloader is locked? Sorry for my ignorance, don't have any experience flashing the bootloader.

Sorry I can't answer your questions but I'm also a non-windows user (Linux). To use the safer Odin I created a Windows VirtualBox VM with a Windows install iso I downloaded over the net. Subsequently it has been suggested by others that it would have been easier for my to have created a bootable usb. In any event you never have to activate the window license to use Odin just answer that pop-up by clicking later. I download the latest firmware (there is a firmware download tool thread in the general section), quickly and use Odin all in that VM.
I posted a how-to create such a VM in the general section but if doing it again I'd likely go the USB route but either way is likely safe than your current method.
Sent from my SM-T800 using XDA Premium HD app

You're lucky you even got Heimdall to connect on the tab s.
I've had zero success with it on either windows or Linux.
Stick with a VM as suggested. It takes literally a few minutes to set up.
https://dev.windows.com/en-us/microsoft-edge/tools/vms/linux/

Thanks for the advice. Heimdall on Linux previously worked well for me when I flashed TWRP on the same T705 a few months ago. This time though I'll try odin in a VM as you both suggest.

Got odin working. The VM was slightly problematic:
Couldn't get Virtualbox on Mac to work. VM couldn't see the tablet.
Under Linux, had to "modprobe -r cdc_acm" to get it to work, as described here
Even then, Odin was failing with a big red FAIL! message at the completion of the flash. Resorted to pirating Windows 7 and installing on a spare harddrive. Still got the Odin FAIL! So I think it was the files I was using. Would the slightly wrong version cause a flashing error? My tablet is an Australian T705Y and the images may have been for a different region.
Anyway, downloaded the complete official ROM from sammobile and that flashed fine using Odin. Then installed TWRP and now the Marshmallow ROM.

cr1key said:
Got odin working. The VM was slightly problematic:
Couldn't get Virtualbox on Mac to work. VM couldn't see the tablet.
Under Linux, had to "modprobe -r cdc_acm" to get it to work, as described here
Even then, Odin was failing with a big red FAIL! message at the completion of the flash. Resorted to pirating Windows 7 and installing on a spare harddrive. Still got the Odin FAIL! So I think it was the files I was using. Would the slightly wrong version cause a flashing error? My tablet is an Australian T705Y and the images may have been for a different region.
Anyway, downloaded the complete official ROM from sammobile and that flashed fine using Odin. Then installed TWRP and now the Marshmallow ROM.
Click to expand...
Click to collapse
yes I am curious how to flash only sboot.bin through odin (or any other means)

The heimdall command is at the top of the thread.
I never actually attempted the bootloader in odin. I tried flashing the modem (which I also had to update), but as that was failing I never progressed to the bootloader. For the modem I just used a tar file that contained modem.bin. Odin reads the PIT and figures out where which partition it should go in (in this case, RADIO). I expect it'd work for the bootloader too. The official ROM distributions are tar files containing *.bin files:
Code:
-rw-rw-r-- dpi/dpi 1148160 2015-10-23 00:29 sboot.bin
-rw-rw-r-- dpi/dpi 7592208 2015-10-23 00:29 boot.img
-rw-rw-r-- dpi/dpi 7803152 2015-10-23 00:29 recovery.img
-rw------- dpi/dpi 2313405472 2015-10-23 00:30 system.img
-rw-r--r-- dpi/dpi 40231200 2015-10-23 00:31 cache.img
-rw-r--r-- dpi/dpi 217281008 2015-10-23 00:31 hidden.img
-rw-rw-r-- dpi/dpi 28600832 2015-10-23 00:24 modem.bin
odin flashes each one in turn to the appropriate partition. Just use PDA to flash the tar file. Possibly you could use the BOOTLOADER (sometimes called just "BL") button, but I don't think it matters.

TWRP fails to boot on SM-P600 (aka Exynos Wi-Fi)

I have flashed TWRP 3.0.2 with heimdall to my SM-P600. According to the output everything went out fine:
Code:
$ heimdall flash --no-reboot --RECOVERY twrp-3.0.2-0-lt03wifiue.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
[Link removed to comply with xdadevelopers policy]
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:
[Link removed to comply with xdadevelopers policy]
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
However, when afterwards I boot the tablet in recovery mode I get the following error message:
Could not do normal boot. Invalid KERNEL LENGTH!
Click to expand...
Click to collapse
What could be the cause of this error? Thank you.

LG h815 HELP - Bootloop in Download Mode

Hi all,
I manage to (soft) brick my LG H815
It was working fine (using Nougat) until I decided it was time to poke with it (battery was draining way too fast)! Bad idea!
So I tried to upload a new ROM ... which happened to be a wrong variant (i suppose). After that, my device boots straight in to Download Mode all the time. However, I can put it in Fastboot mode (hold Vol + and connect USB cable).
But Fastboot mode doesn't seems to be of any use for me, as when I use ADB DEVICES it doesn't show my device (but it can reboot it, and even respond to a getvar command that shows that its bootloader is unlocked (printscreen attached)
I thought it could be a a driver problem (I use Win10 Pro - Build 16299), but LG Bridge seems to find my device ... but any attempt to fix/recover/update it always fail. Also, LGUP always give "error code = 0x2000, invalid command response" when I try to upload a new KDZ archive.
After 3 days reading all I could find and burning out my brain ... so, I'll be very gratefull if someone can give me a help :good::good:
PS: I added a few print screens from what i've got here. Pls let me know if there is any other useful info.

H815 soft bricked
anyone....?
I'm willing to try any suggestion (phone still bricked and useless)... even if it seems similar/identical to previews try... and I'm happy to donate some gold coins (ie: paypal :highfive for suggestions that leads to fix it.
LGUP = does not seems to work
ADB commands = does not see the device

You can't use *adb* commands in *fastboot* mode!
So when you boot into fastboot only fastboot commands will work. Example: fastboot flash boot twrp.img
So download the latest preview TWRP from my server and rename it to twrp.img then do the above command while in fastboot mode.
This should bring up TWRP temporarely. But that wouldn't help a lot.
The fix would require SALT. You would extract with SALT the correct kdz variant of your model and flash the bootloader stack while in fastboot.
Sent from my LG-H815 using XDA Labs

otavio_aon said:
Hi all,
I manage to (soft) brick my LG H815
It was working fine (using Nougat) until I decided it was time to poke with it (battery was draining way too fast)! Bad idea!
So I tried to upload a new ROM ... which happened to be a wrong variant (i suppose). After that, my device boots straight in to Download Mode all the time. However, I can put it in Fastboot mode (hold Vol + and connect USB cable).
But Fastboot mode doesn't seems to be of any use for me, as when I use ADB DEVICES it doesn't show my device (but it can reboot it, and even respond to a getvar command that shows that its bootloader is unlocked (printscreen attached)
I thought it could be a a driver problem (I use Win10 Pro - Build 16299), but LG Bridge seems to find my device ... but any attempt to fix/recover/update it always fail. Also, LGUP always give "error code = 0x2000, invalid command response" when I try to upload a new KDZ archive.
After 3 days reading all I could find and burning out my brain ... so, I'll be very gratefull if someone can give me a help :good::good:
PS: I added a few print screens from what i've got here. Pls let me know if there is any other useful info.
Click to expand...
Click to collapse
Try after read this: https://forum.xda-developers.com/showpost.php?p=76571471&postcount=23
And this: https://forum.xda-developers.com/showpost.php?p=76580594&postcount=17

steadfasterX said:
You can't use *adb* commands in *fastboot* mode!
So when you boot into fastboot only fastboot commands will work. Example: fastboot flash boot twrp.img
So download the latest preview TWRP from my server and rename it to twrp.img then do the above command while in fastboot mode.
This should bring up TWRP temporarily. But that wouldn't help a lot.
The fix would require SALT. You would extract with SALT the correct kdz variant of your model and flash the bootloader stack while in fastboot.
Click to expand...
Click to collapse
ALRIGHT ... after a few days I managed to install SALT (using a VirttualBox + FWUL 2.6 Forgetfull).
I did as instructed in the SALT tread
git clone https://github.com/steadfasterX/SALT.git
cd SALT
bash install-desktop.sh
...but not sudo pacman -Sy python-pyusb python-crypto as I installed FWUL 2.6
Click to expand...
Click to collapse
However, it failed to identify my device (attached print screen).
Any idea of what I should do? Am I skipping any crucial step? Could this problem be related to the "MODIFIED" mark that shows in red on my device Download Mode screen (photo attached)?

otavio_aon said:
ALRIGHT ... after a few days I managed to install SALT (using a VirttualBox + FWUL 2.6 Forgetfull).
I did as instructed in the SALT tread
However, it failed to identify my device (attached print screen).
Any idea of what I should do? Am I skipping any crucial step? Could this problem be related to the "MODIFIED" mark that shows in red on my device Download Mode screen (photo attached)?
Click to expand...
Click to collapse
if you use FWUL there is no need to install SALT. its already included (LG folder on the desktop) but anyways.
do you have attached the LG device in virtualbox settings after booted to download mode?
if yes: press the skip button when starting SALT and device is connected and open the advanced menu -> debug log -> upload button -> share the link
.

steadfasterX said:
if you use FWUL there is no need to install SALT. its already included (LG folder on the desktop) but anyways.
do you have attached the LG device in virtualbox settings after booted to download mode?
if yes: press the skip button when starting SALT and device is connected and open the advanced menu -> debug log -> upload button -> share the link
Click to expand...
Click to collapse
YEs ... i've attached the device on the VirtualBox setting (Settings -> USB -> Add New USB Filter -> LG Eletronic Inc.) but it doesn't look like it got detected by linux (even though LGE Android Phone appeared there... PHOTO ATTACHED)
The Log generated is HERE (I'll paste it below in case it expires).
Also, when I click Show Your Partitions it is empty (but I suppose that is expected as no_device_found is displayed everywhere)
Code:
2018-05-26 02:57:41: F_VCHK: newer SALT version found (316 / 3.16-0 vs. 38 / 3.8-2)
2018-05-26 02:57:41: F_MSGW: started
2018-05-26 02:57:53: New SALT version available!
You: <b>3.8-2</b>
Online: <b>3.16-0</b>
Do you want to update now?
2018-05-26 02:57:53: 0
2018-05-26 02:57:53: OS: Manjaro Linux
fwulversion=2.6
fwulbuild=1520439165
patchlevel=0
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=17.1.6
DISTRIB_CODENAME=Hakoila
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
ID=manjaro
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.manjaro.org/"
SUPPORT_URL="https://www.manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
2018-05-26 02:57:53: OS (lsb): LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 17.1.6
Codename: Hakoila
2018-05-26 02:57:53: yad: 0.40.0 (GTK+ 3.22.28)
2018-05-26 02:57:53: DEVCON before: 99
2018-05-26 02:57:53: F_CHKDEVCON: started
2018-05-26 02:57:58: F_MSG: started
2018-05-26 02:58:06: NO DEVICE CONNECTED?
If you have connected your device ensure that it is in DOWNLOAD mode
(<u>not</u> fastboot, <u>not</u> recovery, <u>not</u> booted Android)
2018-05-26 02:58:06: F_MSG: ended
2018-05-26 02:58:06: F_CHKDEVCON: msge result = 99
2018-05-26 02:58:06: F_CHKDEVCON: lsusb output = Bus 001 Device 006: ID 1004:633a LG Electronics, Inc. Ultimate 2 Android Phone L41C
2018-05-26 02:58:15: RET: 99
2018-05-26 02:58:15: DEVCON after: 99
2018-05-26 02:58:15: DEVCON before: 99
2018-05-26 02:58:15: F_CHKDEVCON: started
2018-05-26 02:58:20: F_MSG: started
2018-05-26 02:58:22: NO DEVICE CONNECTED?
If you have connected your device ensure that it is in DOWNLOAD mode
(<u>not</u> fastboot, <u>not</u> recovery, <u>not</u> booted Android)
2018-05-26 02:58:22: F_MSG: ended
2018-05-26 02:58:22: F_CHKDEVCON: msge result = 11
2018-05-26 02:58:22: F_CHKDEVCON: lsusb output = Bus 001 Device 006: ID 1004:633a LG Electronics, Inc. Ultimate 2 Android Phone L41C
2018-05-26 02:58:22: RET: 11
2018-05-26 02:58:22: DEVCON after: 11
2018-05-26 02:58:22: EXPERIMENTAL: 0
2018-05-26 02:58:22: F_MSGW: started
2018-05-26 02:58:53: Your device does <b>not</b> support direct flashing!
Flashing functionality <b>disabled</b>!
Activate flashing functionality by flashing a SALT compatible LAF partition.
Download it right here for <b>any</b> G4 model (requires unlocked device + TWRP):
<a href='https://www.androidfilehost.com/?fid=818070582850495147'>SALT-compatible-LAF_flash-in-twrp.zip</a>
You can still use many of the features SALT offering - just not the flashing part.
2018-05-26 02:58:53: 0
2018-05-26 02:58:53: Flashing functionality disabled bc: LAFVER = no_device_found and/or EXPERIMENTAL = 0
2018-05-26 02:59:18: F_ADVMENU: started
2018-05-26 02:59:23: F_LISTPARTS: started
2018-05-26 02:59:23: F_GETPARTS: started
2018-05-26 02:59:25: F_LISTPARTS: started
2018-05-26 02:59:25: F_GETPARTS: started
2018-05-26 02:59:25: (F_GETPARTS) created yad list:
2018-05-26 02:59:28: (F_GETPARTS) created yad list:
2018-05-26 02:59:47: getlog script started
2018-05-26 03:00:35: F_MSGOK: started
2018-05-26 03:00:51: Log uploaded successfully!
Please share this link:
http://bpaste.net/show/e883bf5d476c
2018-05-26 03:00:51: 0
2018-05-26 03:00:58: getlog script started
PS: Yes, I installed VirtualBox Extension Pack
PS2: I tried to connect my other mobile (an old Sony Xperia) using the same procedure, and I can access it in linux without a problem.

otavio_aon said:
YEs ... i've attached the device on the VirtualBox setting (Settings -> USB -> Add New USB Filter -> LG Eletronic Inc.) but it doesn't look like it got detected by linux (even though LGE Android Phone appeared there... PHOTO ATTACHED)
The Log generated is HERE (I'll paste it below in case it expires).
Also, when I click Show Your Partitions it is empty (but I suppose that is expected as no_device_found is displayed everywhere)
PS: Yes, I installed VirtualBox Extension Pack
PS2: I tried to connect my other mobile (an old Sony Xperia) using the same procedure, and I can access it in linux without a problem.
Click to expand...
Click to collapse
Try the same with USB 3 in VirtualBox settings
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Try the same with USB 3 in VirtualBox settings
Click to expand...
Click to collapse
:laugh:... it worked!
It's not fixed... but SALT has found my mobile (after I change it to USB3) 2 new things happened:
1) SALT identified all device's information (photo attached)
2) Download Mode screen changed (slightly) and does not display the "Modified" (in red) anymore. Not it shows: "633A 50.0 AS0.0 BB1 UHS || U U LG-H815TR 07.0 Hrev_10 CPU4 || H81529a" (but if I reboot the device, old message returns)
Debug log is HERE:
Code:
[INDENT] 2018-05-26 09:58:38: F_VCHK: newer SALT version found (316 / 3.16-0 vs. 38 / 3.8-2)
2018-05-26 09:58:38: F_MSGW: started
2018-05-26 09:58:46: New SALT version available!
You: <b>3.8-2</b>
Online: <b>3.16-0</b>
Do you want to update now?
2018-05-26 09:58:46: 0
2018-05-26 09:58:46: OS: Manjaro Linux
fwulversion=2.6
fwulbuild=1520439165
patchlevel=0
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=17.1.6
DISTRIB_CODENAME=Hakoila
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
ID=manjaro
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.manjaro.org/"
SUPPORT_URL="https://www.manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
2018-05-26 09:58:46: OS (lsb): LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 17.1.6
Codename: Hakoila
2018-05-26 09:58:46: yad: 0.40.0 (GTK+ 3.22.28)
2018-05-26 09:58:46: DEVCON before: 99
2018-05-26 09:58:46: F_CHKDEVCON: started
aarch64
2018-05-26 09:58:47: F_CHKDEVCON: Device seems to be connected!
2018-05-26 09:58:47: RET: 0
2018-05-26 09:58:47: DEVCON after: 0
2018-05-26 09:58:47: EXPERIMENTAL: 0
2018-05-26 09:58:47: F_GETINFO: started
2018-05-26 09:58:47: F_CDARB: started
2018-05-26 09:58:48,032 partitions: INFO: Wrote 1048576 bytes to -
2018-05-26 09:58:48: ARB valid and 0
2018-05-26 09:58:48: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2018-05-26 09:58:48: F_CDARB: ended
2018-05-26 09:58:48: F_GETINFO: ARB 0:0
2018-05-26 09:58:48: F_CKUSU: started
2018-05-26 09:58:48: F_DUMPPART: started with aboot
0:15:2048
1:31:2048
2:46:2048
3:62:2048
3:77:2048
4:93:2048
5:108:2048
6:124:2048
6:139:2048
7:155:2048
8:170:2048
9:186:2048
9:201:2048
10:217:2048
11:232:2048
12:248:2048
12:263:2048
13:279:2048
14:294:2048
15:310:2048
15:325:2048
16:341:2048
17:356:2048
18:372:2048
18:387:2048
19:403:2048
20:418:2048
21:434:2048
21:449:2048
22:465:2048
23:480:2048
24:496:2048
24:511:2048
25:527:2048
26:542:2048
27:558:2048
28:573:2048
28:589:2048
29:604:2048
30:620:2048
31:635:2048
31:651:2048
32:666:2048
33:682:2048
34:697:2048
34:713:2048
35:728:2048
36:744:2048
37:759:2048
37:775:2048
38:790:2048
39:806:2048
40:821:2048
40:837:2048
41:852:2048
42:868:2048
43:883:2048
43:899:2048
44:914:2048
45:930:2048
46:945:2048
46:961:2048
47:976:2048
48:992:2048
49:1007:2048
49:1023:2048
50:1038:2048
51:1054:2048
52:1069:2048
52:1085:2048
53:1100:2048
54:1116:2048
55:1131:2048
56:1147:2048
56:1162:2048
57:1178:2048
58:1193:2048
59:1209:2048
59:1224:2048
60:1240:2048
61:1255:2048
62:1271:2048
62:1286:2048
63:1302:2048
64:1317:2048
65:1333:2048
65:1348:2048
66:1364:2048
67:1379:2048
68:1395:2048
68:1410:2048
69:1426:2048
70:1441:2048
71:1457:2048
71:1472:2048
72:1488:2048
73:1503:2048
74:1519:2048
74:1534:2048
75:1550:2048
76:1565:2048
77:1581:2048
77:1596:2048
78:1612:2048
79:1627:2048
80:1643:2048
80:1658:2048
81:1674:2048
82:1689:2048
83:1705:2048
84:1720:2048
84:1736:2048
85:1751:2048
86:1767:2048
87:1782:2048
87:1798:2048
88:1813:2048
89:1829:2048
90:1844:2048
90:1860:2048
91:1875:2048
92:1891:2048
93:1906:2048
93:1922:2048
94:1937:2048
95:1953:2048
96:1968:2048
96:1984:2048
97:1999:2048
98:2015:2048
99:2030:2048
99:2046:2048
100:2048:2048
2018-05-26 09:58:49: F_CKUSU: USU=0 (1=yes, 0=no)
2018-05-26 09:58:49: F_CKUSU: ended
2018-05-26 09:58:49: F_GETINFO: USU 0:
2018-05-26 09:58:49: F_ROMCOMP: started
0
1
2018-05-26 09:58:50: UsU compatibility: 0 (0=h815, 1=h811)
2018-05-26 09:58:50: F_GETINFO: ROMCOMP H815
2018-05-26 09:58:50: F_CHKLAFV: started with this args:
2018-05-26 09:58:50: F_CHKLAFV: detected 1000006
2018-05-26 09:58:50: F_CHKLAFV: no comparison needed
2018-05-26 09:58:50: F_GETINFO: LAFVER 1000006
2018-05-26 09:58:51: F_GETINFO:
2018-05-26 09:58:51: F_GETINFO: ended
2018-05-26 09:58:51: parsing
2018-05-26 09:58:51: parsing H815
2018-05-26 09:58:51: parsing 0
2018-05-26 09:58:51: parsing 1000006
2018-05-26 09:58:51: parsing 85
2018-05-26 09:58:51: parsing H81529a
2018-05-26 09:58:51: parsing U
2018-05-26 09:58:51: parsing LGH815TRAT-00-V29a-OPT2-HQ-JUL-12-2017+0
2018-05-26 09:58:51: parsing imei:xxxxxxxxxxx
2018-05-26 09:58:51: parsing serial:xxxxxxxxxxx
2018-05-26 09:58:51: parsing LG-H815TR
2018-05-26 09:58:51: parsing GLOBAL
2018-05-26 09:58:51: parsing COM
2018-05-26 09:58:51: F_MSGW: started
2018-05-26 09:59:11: Your device does <b>not</b> support direct flashing!
Flashing functionality <b>disabled</b>!
Activate flashing functionality by flashing a SALT compatible LAF partition.
Download it right here for <b>any</b> G4 model (requires unlocked device + TWRP):
<a href='https://www.androidfilehost.com/?fid=818070582850495147'>SALT-compatible-LAF_flash-in-twrp.zip</a>
You can still use many of the features SALT offering - just not the flashing part.
2018-05-26 09:59:11: 0
2018-05-26 09:59:11: Flashing functionality disabled bc: LAFVER = 1000006 and/or EXPERIMENTAL = 0
2018-05-26 09:59:22: F_ADVMENU: started
2018-05-26 09:59:25: getlog script started
2018-05-26 10:00:10: F_MSGOK: started
2018-05-26 10:03:33: Log uploaded successfully!
Please share this link:
http://bpaste.net/show/1e10b2cccc7e
2018-05-26 10:03:33: 0
2018-05-26 10:03:37: F_LISTPARTS: started
2018-05-26 10:03:37: F_GETPARTS: started
2018-05-26 10:03:38: modem,1,32768,208895,812DD655-627C-0D0F-3FD2-815DCE5ABBC4
2018-05-26 10:03:38: pmic,2,229376,230399,DAF3727B-E6CE-D706-A1D0-56DA4D6215A3
2018-05-26 10:03:38: sbl1,3,230400,232447,1E04EB30-648D-3B3B-1AFE-374D798D8540
2018-05-26 10:03:38: tz,4,232448,234495,A1DB62E4-8B1D-79B6-9BBD-72E3067C629C
2018-05-26 10:03:38: sdi,5,234496,235519,91F2EC68-8B7A-48F9-E26D-738F3EDC27DE
2018-05-26 10:03:38: hyp,6,235520,236543,881AEE2F-4930-E620-D43E-6CF0BD5BBEAC
2018-05-26 10:03:38: rpm,7,236544,237567,13E54E57-3AC1-F5C8-EB08-058DE52AAC47
2018-05-26 10:03:38: aboot,8,237568,241663,666255B1-D974-5DBE-60A2-F8EBB81F7D2E
2018-05-26 10:03:38: sbl1bak,9,241664,243711,D146B23E-8F14-FE0F-8E63-CC1034FF3AD7
2018-05-26 10:03:38: pmicbak,10,243712,244735,78BFD764-AE7C-E491-D43B-D5D68FC7134E
2018-05-26 10:03:38: tzbak,11,244736,246783,C74DD66B-0C83-D518-BF9A-611675363680
2018-05-26 10:03:38: hypbak,12,246784,247807,F62B8FB5-CBDA-4056-EBBC-8F5ED7C3353F
2018-05-26 10:03:38: rpmbak,13,247808,248831,58579D64-17A6-89D0-1622-1397AA80A681
2018-05-26 10:03:38: abootbak,14,248832,252927,E6540864-B4B7-8698-0F1A-DEAF653DAAAA
2018-05-26 10:03:38: sdibak,15,252928,253951,79DD4B98-AD7D-470E-BDD9-CE9AA6E9246A
2018-05-26 10:03:38: limits,16,253952,254975,A22DAF2F-AB5C-9D30-2236-512209A6FAF2
2018-05-26 10:03:38: devinfo,17,254976,255999,72A30C09-12E8-C6FC-7423-949A8EBAAA82
2018-05-26 10:03:38: apdp,18,256000,257023,618ED72A-84A4-3214-9126-DA6BBB3CC4D1
2018-05-26 10:03:38: msadp,19,257024,258047,6E801307-7F0F-6724-D4B6-37031D5C21F7
2018-05-26 10:03:38: dpo,20,258048,259071,77476FA7-2D7F-AD3B-84CA-23BDC11EBCAC
2018-05-26 10:03:38: spare1,21,259072,262143,584CAAA9-BB9D-A018-D395-6DFDCC039918
2018-05-26 10:03:38: misc,22,262144,294911,882D6E37-322E-5861-C2A5-C612AA5DBE1B
2018-05-26 10:03:38: persist,23,294912,360447,977164A1-A02D-24E6-46D4-2419B28F4AF3
2018-05-26 10:03:38: modemst1,24,360448,363519,33A57E1C-8210-8A64-33F2-53421F06125D
2018-05-26 10:03:38: modemst2,25,363520,366591,E012A295-A5BA-0BA0-1A67-B7C75413A1FA
2018-05-26 10:03:38: fsg,26,366592,369663,623D5942-BC88-D653-C36D-0A6F5A5F7716
2018-05-26 10:03:38: fsc,27,369664,370687,0AE8652B-9C14-CC79-DD95-8B15609F0871
2018-05-26 10:03:39: ssd,28,370688,371711,FB4BCE9E-6095-FA8B-12E5-17057399E17F
2018-05-26 10:03:39: keystore,29,371712,372735,F8317C1D-2ABB-20BC-8C67-DBB39C650DB1
2018-05-26 10:03:39: DDR,30,372736,376831,3083DD35-923A-1FE5-791D-4D5DEB9586F3
2018-05-26 10:03:39: sec,31,376832,377855,7ADEF19D-27E6-B1A5-2BFD-3018BAF82F06
2018-05-26 10:03:39: encrypt,32,377856,378879,68A71FCC-004E-5596-E810-1B8006293C58
2018-05-26 10:03:39: eksst,33,378880,379903,A2E77524-2565-B443-9C2A-DD5EE575C1AF
2018-05-26 10:03:39: rct,34,379904,380927,FE2C06FE-D904-DE3A-4076-DA16207ACF17
2018-05-26 10:03:39: persistent,35,380928,385023,C4799A1F-49F9-C600-B2C6-1BD2C7D129C6
2018-05-26 10:03:39: spare2,36,385024,393215,4ECD70C8-B392-9B3A-7652-24148D00DF9D
2018-05-26 10:03:39: laf,37,393216,491519,855DCE51-2AEE-58FA-632F-BC315AE32250
2018-05-26 10:03:39: boot,38,491520,573439,BDBBAA7F-C1F8-65E6-5AD6-E18DDEBB3E44
2018-05-26 10:03:39: recovery,39,573440,655359,F12ADFD1-1B60-AEF0-6C81-67E7114D58ED
2018-05-26 10:03:39: drm,40,655360,671743,A0AA8F72-5649-8BA4-8B44-56F9E1615838
2018-05-26 10:03:39: sns,41,671744,688127,232664F5-B752-C025-3A48-9A7F059572ED
2018-05-26 10:03:39: mpt,42,688128,753663,CF573AF5-D1CB-0311-BC4B-7FA12852D52B
2018-05-26 10:03:39: factory,43,753664,847871,C09B2DD0-3A16-4C44-73C0-A56EF0DD92B6
2018-05-26 10:03:39: fota,44,847872,868351,B728E1E5-DCA5-11FA-B9A3-FA5344F5158A
2018-05-26 10:03:39: raw_resources,45,868352,876543,083A2C34-2EA0-0FA0-5AFD-0F0E80FDD16C
2018-05-26 10:03:39: raw_resourcesbak,46,876544,884735,8587FC90-5E3C-105D-B978-BC293D805FC5
2018-05-26 10:03:39: system,47,884736,9363455,B3364B13-EEB8-CBBA-2B8C-458B7FF5795A
2018-05-26 10:03:39: cust,48,9363456,9887743,030D4113-B0F9-5323-2268-9383055D0B80
2018-05-26 10:03:39: cache,49,9895936,12419071,9CE8E415-5EE6-28A1-DACB-E409CABF612B
2018-05-26 10:03:39: userdata,50,12419072,61046783,7F9EDF99-45E1-EFA5-4CE8-23A9EFE21C86
2018-05-26 10:03:39: grow,51,61046784,61071326,84DB071C-E681-B8AF-77CB-35FD426B4471
2018-05-26 10:03:39: (F_GETPARTS) created yad list: true
modem
1
32768
208895
812DD655-627C-0D0F-3FD2-815DCE5ABBC4
<span color='#558000'>system-partition</span>
2 true
pmic
2
229376
230399
DAF3727B-E6CE-D706-A1D0-56DA4D6215A3
bootloader
1 true
sbl1
3
230400
232447
1E04EB30-648D-3B3B-1AFE-374D798D8540
bootloader
1 true
tz
4
232448
234495
A1DB62E4-8B1D-79B6-9BBD-72E3067C629C
bootloader
1 true
sdi
5
234496
235519
91F2EC68-8B7A-48F9-E26D-738F3EDC27DE
bootloader
1 true
hyp
6
235520
236543
881AEE2F-4930-E620-D43E-6CF0BD5BBEAC
bootloader
1 true
rpm
7
236544
237567
13E54E57-3AC1-F5C8-EB08-058DE52AAC47
bootloader
1 true
aboot
8
237568
241663
666255B1-D974-5DBE-60A2-F8EBB81F7D2E
bootloader
1 true
sbl1bak
9
241664
243711
D146B23E-8F14-FE0F-8E63-CC1034FF3AD7
bootloader
1 true
pmicbak
10
243712
244735
78BFD764-AE7C-E491-D43B-D5D68FC7134E
bootloader
1 true
tzbak
11
244736
246783
C74DD66B-0C83-D518-BF9A-611675363680
bootloader
1 true
hypbak
12
246784
247807
F62B8FB5-CBDA-4056-EBBC-8F5ED7C3353F
bootloader
1 true
rpmbak
13
247808
248831
58579D64-17A6-89D0-1622-1397AA80A681
bootloader
1 true
abootbak
14
248832
252927
E6540864-B4B7-8698-0F1A-DEAF653DAAAA
bootloader
1 true
sdibak
15
252928
253951
79DD4B98-AD7D-470E-BDD9-CE9AA6E9246A
bootloader
1 true
limits
16
253952
254975
A22DAF2F-AB5C-9D30-2236-512209A6FAF2
<span color='#558000'>system-partition</span>
2 false
devinfo
17
254976
255999
72A30C09-12E8-C6FC-7423-949A8EBAAA82
<span color='#ff0000'>dangerous</span>
88 true
apdp
18
256000
257023
618ED72A-84A4-3214-9126-DA6BBB3CC4D1
<span color='#558000'>system-partition</span>
2 true
msadp
19
257024
258047
6E801307-7F0F-6724-D4B6-37031D5C21F7
<span color='#558000'>system-partition</span>
2 true
dpo
20
258048
259071
77476FA7-2D7F-AD3B-84CA-23BDC11EBCAC
<span color='#558000'>system-partition</span>
2 true
spare1
21
259072
262143
584CAAA9-BB9D-A018-D395-6DFDCC039918
unknown-type
2 false
misc
22
262144
294911
882D6E37-322E-5861-C2A5-C612AA5DBE1B
<span color='#ff0000'>dangerous</span>
88 false
persist
23
294912
360447
977164A1-A02D-24E6-46D4-2419B28F4AF3
<span color='#ff0000'>dangerous</span>
88 false
modemst1
24
360448
363519
33A57E1C-8210-8A64-33F2-53421F06125D
<span color='#ff0000'>dangerous</span>
88 false
modemst2
25
363520
366591
E012A295-A5BA-0BA0-1A67-B7C75413A1FA
<span color='#ff0000'>dangerous</span>
88 true
fsg
26
366592
369663
623D5942-BC88-D653-C36D-0A6F5A5F7716
<span color='#558000'>system-partition</span>
2 true
fsc
27
369664
370687
0AE8652B-9C14-CC79-DD95-8B15609F0871
<span color='#558000'>system-partition</span>
2 true
ssd
28
370688
371711
FB4BCE9E-6095-FA8B-12E5-17057399E17F
<span color='#558000'>system-partition</span>
2 true
keystore
29
371712
372735
F8317C1D-2ABB-20BC-8C67-DBB39C650DB1
<span color='#558000'>system-partition</span>
2 true
DDR
30
372736
376831
3083DD35-923A-1FE5-791D-4D5DEB9586F3
<span color='#558000'>system-partition</span>
2 true
sec
31
376832
377855
7ADEF19D-27E6-B1A5-2BFD-3018BAF82F06
<span color='#558000'>system-partition</span>
2 true
encrypt
32
377856
378879
68A71FCC-004E-5596-E810-1B8006293C58
<span color='#558000'>system-partition</span>
2 true
eksst
33
378880
379903
A2E77524-2565-B443-9C2A-DD5EE575C1AF
<span color='#558000'>system-partition</span>
2 true
rct
34
379904
380927
FE2C06FE-D904-DE3A-4076-DA16207ACF17
<span color='#558000'>system-partition</span>
2 false
persistent
35
380928
385023
C4799A1F-49F9-C600-B2C6-1BD2C7D129C6
<span color='#ff0000'>dangerous</span>
88 true
spare2
36
385024
393215
4ECD70C8-B392-9B3A-7652-24148D00DF9D
unknown-type
2 true
laf
37
393216
491519
855DCE51-2AEE-58FA-632F-BC315AE32250
bootloader
1 true
boot
38
491520
573439
BDBBAA7F-C1F8-65E6-5AD6-E18DDEBB3E44
<span color='#558000'>system-partition</span>
2 true
recovery
39
573440
655359
F12ADFD1-1B60-AEF0-6C81-67E7114D58ED
<span color='#558000'>system-partition</span>
2 false
drm
40
655360
671743
A0AA8F72-5649-8BA4-8B44-56F9E1615838
<span color='#ff0000'>dangerous</span>
88 false
sns
41
671744
688127
232664F5-B752-C025-3A48-9A7F059572ED
<span color='#ff0000'>dangerous</span>
88 true
mpt
42
688128
753663
CF573AF5-D1CB-0311-BC4B-7FA12852D52B
<span color='#558000'>system-partition</span>
2 true
factory
43
753664
847871
C09B2DD0-3A16-4C44-73C0-A56EF0DD92B6
<span color='#558000'>system-partition</span>
2 true
fota
44
847872
868351
B728E1E5-DCA5-11FA-B9A3-FA5344F5158A
<span color='#558000'>system-partition</span>
2 true
raw_resources
45
868352
876543
083A2C34-2EA0-0FA0-5AFD-0F0E80FDD16C
<span color='#558000'>system-partition</span>
2 true
raw_resourcesbak
46
876544
884735
8587FC90-5E3C-105D-B978-BC293D805FC5
<span color='#558000'>system-partition</span>
2 true
system
47
884736
9363455
B3364B13-EEB8-CBBA-2B8C-458B7FF5795A
<span color='#558000'>system-partition</span>
2 true
cust
48
9363456
9887743
030D4113-B0F9-5323-2268-9383055D0B80
<span color='#558000'>system-partition</span>
2 false
cache
49
9895936
12419071
9CE8E415-5EE6-28A1-DACB-E409CABF612B
unneeded
99 false
userdata
50
12419072
61046783
7F9EDF99-45E1-EFA5-4CE8-23A9EFE21C86
unneeded
99 false
grow
51
61046784
61071326
84DB071C-E681-B8AF-77CB-35FD426B4471
unneeded
99
2018-05-26 10:04:39: Reboot button script started
2018-05-26 10:04:43: REBOOT INITIATED by USER!
2018-05-26 10:04:44: Reboot button script ended
2018-05-26 10:08:50: F_ADVMENU: started
2018-05-26 10:09:42: F_ADVMENU: started
2018-05-26 10:10:49: F_ADVMENU: started
2018-05-26 10:15:45: getlog script started[/INDENT]
I need to admit that I'm a bit too excited to try to mess with it now (at least without some guidance ) as I cannot understand this log properly. For me there is no clear error/damage...and I'm already happy to know that the device still alive and it even list the partitions (Advanced Menu -> Show My Partitions).
What should I do now? Is just a matter of extract with SALT the correct kdz variant (that I suppose is the H815TR and not the H815) and flash it?
Thanks again for helping me

otavio_aon said:
:laugh:... it worked!
It's not fixed... but SALT has found my mobile (after I change it to USB3) 2 new things happened:
1) SALT identified all device's information (photo attached)
2) Download Mode screen changed (slightly) and does not display the "Modified" (in red) anymore. Not it shows: "633A 50.0 AS0.0 BB1 UHS || U U LG-H815TR 07.0 Hrev_10 CPU4 || H81529a" (but if I reboot the device, old message returns)
Debug log is HERE:
I need to admit that I'm a bit too excited to try to mess with it now (at least without some guidance ) as I cannot understand this log properly. For me there is no clear error/damage...and I'm already happy to know that the device still alive and it even list the partitions (Advanced Menu -> Show My Partitions).
What should I do now? Is just a matter of extract with SALT the correct kdz variant (that I suppose is the H815TR and not the H815) and flash it?
Thanks again for helping me
Click to expand...
Click to collapse
Great. On of the first things which happen when SALT is starting up is it checks for a new version. Please do not skip the update. It's really necessary to use the latest SALT version and you're using an outdated one. So just update first when ever asked.
Then do a backup in SALT before doing anything else. You can mount folders from your windows to VirtualBox and then access it from there which is the best way to backup in a VM. Check the FWUL thread ftp a howto.
When starting the backup you get asked about the type: choose "basic" or when you want to backup all your internal storage (will take hours and needs 33 GB free disk space) choose the full one. Basic will have all partitions which are important on your phone just without your personal stuff and the ROM itself as that can be easily recovered by extracting a kdz.
Now extract a kdz file of your model with SALT (the partitions you need are listed on the next step). Ensure you have the latest SALT version and ensure that no folder or the kdz file contains any spaces in its name (known bug atm).
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
sbl1
rpm
sdi
pmic
hyp
laf
aboot
tz
system
boot
modem
factory
like that:
fastboot flash sbl1 sbl1.bin
...
Then do this:
fastboot format userdata (will erase all your internal data)
fastboot format cache
fastboot reboot
Keep thumbs pressed. The first boot can take up to 15min!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Great. On of the first things which happen when SALT is starting up is it checks for a new version. Please do not skip the update. It's really necessary to use the latest SALT version and you're using an outdated one. So just update first when ever asked.
Then do a backup in SALT before doing anything else. You can mount folders from your windows to VirtualBox and then access it from there which is the best way to backup in a VM. Check the FWUL thread ftp a howto.
When starting the backup you get asked about the type: choose "basic" or when you want to backup all your internal storage (will take hours and needs 33 GB free disk space) choose the full one. Basic will have all partitions which are important on your phone just without your personal stuff and the ROM itself as that can be easily recovered by extracting a kdz.
Click to expand...
Click to collapse
SALT updated to 3.16.0 :good:
Basic (dont need my personal data) Backup DONE :good: (and verified)
(set a Virtual Box shared folder with Auto mount, Full access and Permanent)
... however, the next part It wasn't so clear for me:
steadfasterX said:
Now extract a kdz file of your model with SALT (the partitions you need are listed on the next step). Ensure you have the latest SALT version and ensure that no folder or the kdz file contains any spaces in its name (known bug atm).
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
...
Click to expand...
Click to collapse
1) Should I download a new KDZ file and get the partitions from there?
2) Or I should get the partitions that are currently on my device?
I tried both:
1) Tried to extract a random KDZ (downloaded a time ago), but it don't know what to expect in case of success. I got a <*.kd> file and a <*.params>
2) if that is the case, it isn't very clear how to do it

otavio_aon said:
SALT updated to 3.16.0 :good:
Basic (dont need my personal data) Backup DONE :good: (and verified)
(set a Virtual Box shared folder with Auto mount, Full access and Permanent)
... however, the next part It wasn't so clear for me:
1) Should I download a new KDZ file and get the partitions from there?
2) Or I should get the partitions that are currently on my device?
I tried both:
1) Tried to extract a random KDZ (downloaded a time ago), but it don't know what to expect in case of success. I got a <*.kd> file and a <*.params>
2) if that is the case, it isn't very clear how to do it
Click to expand...
Click to collapse
Good!
Download and extract the latest version of h815 MM.. so I guess 20... whatever. Iirc 20p was the latest.
The backup with SALT is just to have it if something goes completely wrong. Then you may need it..
But to unbrick you should use the h815 20p kdz, extract it and after extraction completed you will be promoted by SALT to open the folder. Do that. Right click in that folder and choose : "open a terminal here". Then you can go on with the fastboot flash commands.
As said there is a known bug in SALT when the folder where the kdz is in contains spaces in its name or when the target folder where you extract the kdz to contains spaces in its name. So ensure that and you should be able to extract without a problem. If you can't extract a kdz share the SALT debug log after trying.
Sent from my LG-H815 using XDA Labs
OT:
Consider to press thanks from time to time when you think you get help from someone

steadfasterX said:
Download and extract the latest version of h815 MM.. so I guess 20... whatever. Iirc 20p was the latest.
...
But to unbrick you should use the h815 20p kdz, extract it and after extraction completed you will be promoted by SALT to open the folder. Do that. Right click in that folder and choose : "open a terminal here". Then you can go on with the fastboot flash commands.
Click to expand...
Click to collapse
I jsut cannot find the H815_20p anywhere ... so I'm considering using H815v29a (this version has already worked in the past) .... is it going to be a risky? Might it cause a problem? (SALT shows a AntiRollBack = 0 (which I suppose is good) in red (which I understand as a warning)
I also found the H815_20G at AutoPrime archive that seems to be an option...but I guess v29a is newer.
Also: is now the stage were I should get a rooted firmware?
Or I must go for a stock (and unrooted) ROM first... and then, when everything is done and working, I go and try to root it?

otavio_aon said:
I jsut cannot find the H815_20p anywhere ... so I'm considering using H815v29a (this version has already worked in the past) .... is it going to be a risky? Might it cause a problem? (SALT shows a AntiRollBack = 0 (which I suppose is good) in red (which I understand as a warning)
I also found the H815_20G at AutoPrime archive that seems to be an option...but I guess v29a is newer.
Also: is now the stage were I should get a rooted firmware?
Or I must go for a stock (and unrooted) ROM first... and then, when everything is done and working, I go and try to root it?
Click to expand...
Click to collapse
H815 20p is on my server, extracted or as a zip:
http://leech.binbash.it:8008/stock/LG/h815/20p/
Antirollback is in red because it's important not in general good or bad. If you would flash an ARB of anything higher then 0 to a h815 you will never be able to fully recover it.
Don't do any special things like rooting. First thing is to get back to normal and that's just pure stock.
Every side path may lead to issues.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
H815 20p is on my server, extracted or as a zip: http://leech.binbash.it:8008/stock/LG/h815/20p/
[...]
Click to expand...
Click to collapse
So I've downloaded the H81520p_00 stock ROM from your server.
In topic #10 you said that I should get files as ".bin" but in your servers they are all ".image". Should I just rename it to change the file extension? Or do I need to convert it somehow?
steadfasterX said:
After you extracted the kdz boot your phone to fastboot mode instead of download mode and begin to flash the extracted partitions:
sbl1
rpm
sdi
pmic
hyp
laf
aboot
tz
system
boot
modem
factory
like that: fastboot flash sbl1 sbl1.bin
...
Click to expand...
Click to collapse
I also tried to flash the "sdb1.bin" (assuming I just needed to rename the .image file) file into it ... but it didn't worked.
FIRST try:
rebooted in Fastboot mode
using FWUL 2.6 (same setup on VirtualBox), I started a terminal and entered command "fastboot flash sbl1 sbl1.bin "
Got Message "< waiting for any device >" ... and it was only this, even after waiting 10min.
SECOND try:
rebooted in Fastboot mode
using Win10, I started a CMD (as Admin) and entered command "fastboot flash sbl1 sbl1.bin " (PS: fastboot.exe in system path)
Got error message: FAILED (remote: cannot flash this partition in unlocked state)
Code:
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.058s]
writing 'sbl1'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.080s
​
So I decided to perform a simple test.
At Win10 CMD window, entered "fastboot getvar unlocked" ... and got "unlocked: yes || finished. total time: 0.008s"
At FWUL 2.6 Terminal, entered "fastboot getvar unlocked" ... and got same msg "< waiting for any device >". So apparently linux is connecting to the device while it's in download mode but cannot do it in fastboot mode.
Code:
For the records: how to reboot LG G4 in Fastboot mode:
[LIST=1]
[*] Turn OFF device
[*]remove battery
[*]hold Volume DOWN key
[*]insert battery back
[*]connect USB cable
[/LIST]

otavio_aon said:
So I've downloaded the H81520p_00 stock ROM from your server.
In topic #10 you said that I should get files as ".bin" but in your servers they are all ".image". Should I just rename it to change the file extension? Or do I need to convert it somehow?
I also tried to flash the "sdb1.bin" (assuming I just needed to rename the .image file) file into it ... but it didn't worked.
FIRST try:
rebooted in Fastboot mode
using FWUL 2.6 (same setup on VirtualBox), I started a terminal and entered command "fastboot flash sbl1 sbl1.bin "
Got Message "< waiting for any device >" ... and it was only this, even after waiting 10min.
SECOND try:
rebooted in Fastboot mode
using Win10, I started a CMD (as Admin) and entered command "fastboot flash sbl1 sbl1.bin " (PS: fastboot.exe in system path)
Got error message: FAILED (remote: cannot flash this partition in unlocked state)
So I decided to perform a simple test.
At Win10 CMD window, entered "fastboot getvar unlocked" ... and got "unlocked: yes || finished. total time: 0.008s"
At FWUL 2.6 Terminal, entered "fastboot getvar unlocked" ... and got same msg "< waiting for any device >". So apparently linux is connecting to the device while it's in download mode but cannot do it in fastboot mode.
[/LIST]
Click to expand...
Click to collapse
For the bin/image question read FAQ #11 here: https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864/post74811095
FWUL detects fastboot mode without any problems but when entering fastboot the USB id changes. That means when using VirtualBox you need to add that new USB device to FWUL. normally named android phone or similar.
But anyways the error you get in fastboot mode indicates that you can't flash anything useful in that firmware version. FWUL or windows makes no difference here.
So the only option is to flash in download mode then. Either come to IRC ( http://webchat.freenode.net/?channels=Carbonfusion-user ) or write me a PM with subject "SALT flashing mode".
Sent from my LG-H815 using XDA Labs

I have the same problem "Got error message: FAILED (remote: cannot flash this partition in unlocked state)". Please help how to flash in downloaded mode.

I have also tried "[GUIDE] Proper H815 unbrick through QFIL (Files included) by inteLzzz". Flashed different roms by LGUP. All went well, but nothing changed. Pls help.