Develop Bugs

[Q] Flash by apx

Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you

APX is a hardware defect, no solution for that at the moment....yes there is one ! Replace the mainboard

THe thing is I switched the tegra IC and now its stuck on APX but I can Use APX only need the files.
Nothing like the known problem...

Ow oke......good luck then

Thanks
Any one knows a way to full flash by apx ?"

Maybe you can look by posts from nitrous2 or TripnRaver......they know more about APX. At least in general so it might be helpful

Some one any ideas ?

Trip has released drivers for apx mode however you will need the sbk for the one x in order to flash anything which is something that nobody except HTC have
Sent from my HTC One X using xda app-developers app

deadwolf666 said:
Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you
Click to expand...
Click to collapse
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!

Bugz! said:
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!
Click to expand...
Click to collapse
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.

Thanks for the reply !
I have been able to communicate with the device from the second link you provided, but it gives errors when trying to repartition it.
I will post the errors first thing in the morning as I don't have the device with me now to regenerate it
I've read on so many forums that the mainboard may be fried as in it needs to be replaced, but then again I've proven forums wrong before when it comes to unknown errors and situations, so I'm hoping they're wrong again.
I'm curious, how far did you go with your device? where did you stop and give up on it?

deadwolf666 said:
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.
Click to expand...
Click to collapse
Ok here's my log:
Code:
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>nvflash -
-blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile fl
ash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d256462581c11
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>pause
Press any key to continue . . .
Did you get this far? I don't know what this error means as I don't have any experience with nvflash
I'll be looking into the error code, just wanted to share this in case someone is following the footsteps

[Q] Galaxy Nexus stopped working, trying to recover important data...

Hi Guys
I'm new to the Forum and start with asking a question - apologize for that, I know that it's impolite.
I'm pretty desperate at the moment. Tried to switch on my Galaxy Nexus some days ago and it did not start. If I try to switch it on (long button press), the google logo appears for about 72 seconds, then "something" happens on the screen (usually the logo becomes brighter and horizontal lines appear on the screen). And that's it.
There's no clear reason why the mobile is broken now.
The big problem is that I have lots of pictures of my little boy on that device, from his birth until now (it's his first birthday tomorrow). These pics are very very important to me, the only pictures I have from his birth. I did not backup those pictures - I'm stupid. So my goal is to rescue those images from the device somehow. Currently I'm spending every free second to read and learn how to recover those images...
Device info:
Galaxy Nexus, Tuna Maguro 16GB
HW Version: 9
Bootloader Version: PRIMEMD04
Baseband Version: I9250XXLJ1
Everything is stock version, Android 4.4.2 (I think), stock bootloader
What I've tried so far:
- Installed fastload / ADB on Ubuntu 14.04 from repo. Manually installed ADB 1.0.32 as well.
- I can boot the device into Fastboot / Rescue / Odin mode, that works.
- Tried to clear the cache. It hangs after "Formatting /cache". No "completed" message. If I go to the recovery menu now, I get a couple of messages which say
"E:failed to mount /cache (Invalid argument)"
and then lots of "Can't mount /cache/recovery/log" messages.
If I boot in Rescue Mode, select "apply update from ADB" and connect the mobile to the PC:
Code:
[ 502.524071] usb 1-5: new high-speed USB device number 3 using ehci-pci
[ 502.657321] usb 1-5: New USB device found, idVendor=18d1, idProduct=d001
[ 502.657330] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 502.657348] usb 1-5: Product: Galaxy Nexus
[ 502.657352] usb 1-5: Manufacturer: samsung
[ 502.657355] usb 1-5: SerialNumber: (redacted)
So it gets detected, at least.
Then:
Code:
$ ./adb get-state
sideload
$ ./adb devices -l
List of devices attached
(serial redacted) sideload usb:1-5
$ ./adb backup -all
adb: unable to connect for backup
$ ./adb bugreport
error: closed
$ ./adb shell pwd
error: closed
$ ./adb logcat
- waiting for device -
^C
I've downloaded the stock yakju ROM from the google dev website (can't post links, sorry).
There are a bunch of files in that archive:
Code:
$ ll
total 298996
drwxr-x--- 2 m m 4096 Aug 21 2013 ./
drwxr-xr-x 7 m m 4096 Aug 30 23:50 ../
-rw-r----- 1 m m 2363392 Aug 21 2013 bootloader-maguro-primemd04.img
-rw-r----- 1 m m 956 Aug 21 2013 flash-all.bat
-rwxr-x--x 1 m m 827 Aug 21 2013 flash-all.sh*
-rwxr-x--x 1 m m 785 Aug 21 2013 flash-base.sh*
-rw-r----- 1 m m 291192953 Aug 21 2013 image-yakju-jwr66y.zip
-rw-r----- 1 m m 12583168 Aug 21 2013 radio-maguro-i9250xxlj1.img
Code:
$ zipinfo image-yakju-jwr66y.zip
Archive: image-yakju-jwr66y.zip
Zip file size: 291192953 bytes, number of entries: 5
?rw-r--r-- 2.0 unx 4481024 b- defN 09-Jan-01 00:00 boot.img
?rw-r--r-- 2.0 unx 5042176 b- defN 09-Jan-01 00:00 recovery.img
?rw-r--r-- 2.0 unx 485561008 b- defN 09-Jan-01 00:00 system.img
-rw------- 2.0 unx 140860420 b- defN 13-Aug-13 22:56 userdata.img
-rw-r----- 2.0 unx 93 b- defN 13-Aug-13 16:00 android-info.txt
So my questions are:
Am I doing the right thing here? I Hope that this is a software problem and the hardware is ok.
If yes, which of those file(s) should I flash to the device, without risking the loss of data?
Can you think of any other possibility to recover the data? Clockwork mod or TWRP maybe? Or a custom sideload script (inside the uploaded zip file).
I've read that flashing a custom bootloader wipes the device - so maybe CW / TWRP is not a good idea...
Thank you very very much for your help.
Matt

It may have been a while, bit it might help anyways
Boot your phone to the Bootloader mode. Connect it to your PC via USB.
Use Terminal to cd into your adb/fastboot folder.
Grab the latest TWRP from here: https://dl.twrp.me/maguro/
Copy it into the same directory as fastboot and rename it to recovery.img
Then try to boot into recovery (assuming you haven't rooted your phone and you have a locked bootloader) with "./fastboot boot recovery recovery.img"
I am not sure if this will work with a locked bootloader, but it's worth a try.
If it boots to TWRP then "./adb pull /sdcard/ /backup/" this should create a folder with all the contents of the internal memory in the fastboot direcory. Just let it copy, its done when you are at a prompt again.

Lumia 950 XL Dual Sim having problem flashing need help.

Hello everyone I recently got a Lumia 950 XL from B&H not knowing that I ended up with one from Mexico no big deal but id like to have the Reset Protection on the phone since that's a US only feature. So I look up my phone on the back of it an such and so on. And I try this one code that suppose to change my product code which didn't work I try even my original code of my device and nothing happen just errors. this what ive done. Mine a RM-1116 and product number 059X5P5 I wanted to put on my device a US code of 059X505 since there both RM-116 then I put this code down as followed try both as a test.
"C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe" -mode uefiflash -ffufile C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu -skip_flash -productcodeupdate 059X5P5
"C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe" -mode uefiflash -ffufile C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu -skip_flash -productcodeupdate 059X505
But both didn't work. I ended up with a huge error. If I could get some help on this or more clarification of what im doing wrong please help im not a coder just ran into this code from a different forum I belong too. here the log off my error below.
Process started Mon Apr 25 08:58:17 2016
Logging to file C:\Users\Daniel\AppData\Local\Temp\thor2_win_20160425085817_ThreadId-232.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Normal mode detected
Rebooting to the normal mode...
Resp from NCSd {"id":7,"jsonrpc":"2.0","result":null}
[THOR2_flash_state] Switching to flash mode
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 69, charging current 71
Protocol version 2.6 Implementation version 2.48
Booting to FlashApp
Reboot to FlashApp command sent successfully.
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.41 Implementation version 2.75
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.41 Implementation version 2.75
Size of one transfer is 2363392
MMOS RAM support: 1
Size of buffer is 2359296
Number of eMMC sectors: 61071360
Platform ID of device: Microsoft.MSM8994.P6211.2.1
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0015
Subblock ID 32
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\ProgramData\Microsoft\Packages\Products\RM1116_1078.0038.10586.13080.15285.033372_retail_prod_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 2.41 Implementation Version 2.75
Unknown sub block detected. Skip...
DevicePlatformInfo: Microsoft.MSM8994.P6211.2.1
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 15
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU sync version 2 supported.
Secure FFU async version 2 supported.
CRC header v. 1
CRC align bytes. 4
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 61071360
CID: Hynix, Size 29820 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
ConnSpeedEcho: Elapsed= 0.221000, EchoSpeed= 30.54, Transferred= 7077918 bytes
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is 427D8FD5A7F227820D5B11BF8C6F7670C0A0622CC61BA95AAEE18F7517FC0B77
Get ISSW Version...
ISSW Version: 291
Thu Nov 19 16:02:20 EET 2015 ;ISSW v0291; rg0; OS; DNE; KCI 1318; ASIC 899x;
Get system memory size...
Size of system mem: 3145728 KB
Read antitheft status...
Reset Protection status: Disabled
Reset Protection version: 1.1
Send backup to RAM req...
Unable to parse FFU file. File open failed
programming operation failed!
Unable to parse FFU file. File open failed, Error code: 2
Operation took about 34.00 seconds.
FFU_PARSING_ERROR
THOR2 1.8.2.18 exited with error code 2228224 (0x220000)

same

maliksantika said:
same
Click to expand...
Click to collapse
you can ask for help in telegram group.its called "LumiaWOA" join it and ask there

can't flash twrp (no error - just not installed)

hello,
im trying to flash my S4 Mini with lineage os - first step installing twrp fails.
i tried using heimdall to to flash twrp with the gui and via cli, but fail the same way: they report no error at all! finish the flashing and reboot. when i then try to go into recovery the standard recovery is still there! everything is jsut as stock as it was before.
here is the cli output:
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-serranoltexx.img --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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
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: 82
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: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
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%
11%
22%
33%
45%
56%
67%
79%
90%
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
note that: i tried 2 different versions of the latest twrp (one compiled by someone from xda), and i tried the gui too - adding the path to the save pit -> same result.
my problem seems similar to this post:
https://forum.xda-developers.com/galaxy-s4-mini/help/heimdall-reboot-to-custom-recovery-t3474163
but there was no response
also, ive read that sudo can be problem for heimdall, but without sudo it cant access the usb....
if anyone has any idea, please dont be shy to attempt to help, or point to other places where i could get help thank you!
about me: this is literally the first time im having an android device (im a sailfish user), so forgive me the possible beginners mistakes. also, my host pc is runing mint19.

misc11 said:
hello,.
Click to expand...
Click to collapse
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
yes, the phone is still completely stock. not rooted, but apparently the bootloader comes unlocked with samsung phones...
the version is: GT-I9195. so, from your link, i understand that i HAVE to root it?

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!

misc11 said:
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!
Click to expand...
Click to collapse
Thanks no worries
HemanthJabalpuri

G4 not able to enter fastboot mode after Wipe

Hi,
since i wanted to install a custom Lineage OS ROM for my LG G4, i wanted to make a clean install of the OS according to https://forum.xda-developers.com/showpost.php?p=79502871&postcount=2 .
I used
Code:
fastboot boot ~/Downloads/twrp.img
to boot into TWRP from my phone. I didn't install TWRP.
I chose WIPE->Advanced and selected "System" and "Cache". After that, I also used the "Format Data" function.
I rebooted the phone, but since then, only the LG logo is shown with the message "Bootloader Mode: Bootloader unlocked!"
I tried to enter fastboot mode by following these instructions from https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451:
take out the battery
unplug the usb cable from the PC (not from the device)
Insert the battery again
wait 2 sec
press volume DOWN and while keeping it pressed: plug the USB cable to the device
keep volume DOWN pressed until you see the fastboot screen
Click to expand...
Click to collapse
However, it doesn't work. Right now, It looks I can't use the phone for anything anymore. Can anyone help me with this?
Edit: I found out that my phone manages to enter download mode.

benni_g4 said:
Hi,
since i wanted to install a custom Lineage OS ROM for my LG G4, i wanted to make a clean install of the OS according to https://forum.xda-developers.com/showpost.php?p=79502871&postcount=2 .
I used
to boot into TWRP from my phone. I didn't install TWRP.
I chose WIPE->Advanced and selected "System" and "Cache". After that, I also used the "Format Data" function.
I rebooted the phone, but since then, only the LG logo is shown with the message "Bootloader Mode: Bootloader unlocked!"
I tried to enter fastboot mode by following these instructions from https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451:
However, it doesn't work. Right now, It looks I can't use the phone for anything anymore. Can anyone help me with this?
Edit: I found out that my phone manages to enter download mode.
Click to expand...
Click to collapse
UsU'd or not? Sounds like an official unlocked so an advice for UsU devices will not help.
Which TWRP version do you had used?
And most importsnt what model (h815, h812..)?
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
UsU'd or not? Sounds like an official unlocked so an advice for UsU devices will not help.
Which TWRP version do you had used?
And most importsnt what model (h815, h812..)?
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
The model is is H815. You are right, I unlocked it the offical way. The TWRP version is 3.3.1-2.

Any chance to solve this? It would be sad to throw it away because of this reason...

benni_g4 said:
Any chance to solve this? It would be sad to throw it away because of this reason...
Click to expand...
Click to collapse
I think, I had the same problem a couple of years back, but I don't remember the solution. Might have been the USB cable that I used. You could try changing up the cable.
Are you able to detect the device with "adb devices"?

dat_benjie said:
I think, I had the same problem a couple of years back, but I don't remember the solution. Might have been the USB cable that I used. You could try changing up the cable.
Are you able to detect the device with "adb devices"?
Click to expand...
Click to collapse
I changed the cable, but the problem remains. As I said, the phone is also able to enter download mode when I press volume up and plug in the cable.
There is neither any output from
Code:
adb devices
nor from
Code:
fastboot devices
.
But I checked the output of
Code:
lsusb
. There is no usb entry for my phone after trying to enter fastboot mode.
BUT an entry appears after entering download mode:
Code:
Bus 002 Device 026: ID 1004:633a LG Electronics, Inc.
(but still no output from adb devices or fastboot devices)

benni_g4 said:
The model is is H815. You are right, I unlocked it the offical way. The TWRP version is 3.3.1-2.
Click to expand...
Click to collapse
The official TWRP is for oreo ROMs not pie. I don't believe that was the reason though , more likely because you didn't flashed TWRP and just fastboot boot'ed it.
You need to find the right combo for the h815. Just use the xda search to find it and also youtube could show good results.
The cable can be an issue as well and also the usb port ( try on usb 2 and usb 3 port).
Other then that it can differ between the bootloader stack version.
If you haven't flashed any bootloader TWRP zip then this is the last stock firmware version (the last one you had installed on your device).
Last but not least (depends on your bootloader stack version) you might be able to flash with SALT TWRP and boot it afterwards. Btw what was your reason not flashing TWRP ?
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
The official TWRP is for oreo ROMs not pie. I don't believe that was the reason though , more likely because you didn't flashed TWRP and just fastboot boot'ed it.
You need to find the right combo for the h815. Just use the xda search to find it and also youtube could show good results.
The cable can be an issue as well and also the usb port ( try on usb 2 and usb 3 port).
Other then that it can differ between the bootloader stack version.
If you haven't flashed any bootloader TWRP zip then this is the last stock firmware version (the last one you had installed on your device).
Last but not least (depends on your bootloader stack version) you might be able to flash with SALT TWRP and boot it afterwards. Btw what was your reason not flashing TWRP ?
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
To answer your question first: I didn't have a specific reason not to flash TWRP, I just read it somewhere that it was possible just to boot into TWRP. So I thought it wouldn't make a difference.
I didn't find any other key combination to enter fastboot mode.
I actually don't know what a bootloader stack is, my knowledge about android phones is limited .
Maybe the following information might be useful: before my attempts to install your custom ROM, I had a completely outdated ROM of the Official Lineage OS running on my LG G4. I once installed it also using TWRP. I think, back then I actually flashed TWRP, because I followed these instructions: https://wiki.lineageos.org/devices/h815/install .
I installed SALT and was able to connect with my phone. SALT seems to retrieve the correct device information. However, I don't understand how I can flash TWRP using SALT.

benni_g4 said:
To answer your question first: I didn't have a specific reason not to flash TWRP, I just read it somewhere that it was possible just to boot into TWRP. So I thought it wouldn't make a difference.
I didn't find any other key combination to enter fastboot mode.
I actually don't know what a bootloader stack is, my knowledge about android phones is limited .
Maybe the following information might be useful: before my attempts to install your custom ROM, I had a completely outdated ROM of the Official Lineage OS running on my LG G4. I once installed it also using TWRP. I think, back then I actually flashed TWRP, because I followed these instructions: https://wiki.lineageos.org/devices/h815/install .
I installed SALT and was able to connect with my phone. SALT seems to retrieve the correct device information. However, I don't understand how I can flash TWRP using SALT.
Click to expand...
Click to collapse
Share the debug log of SALT, latest version (advanced menu -> debug log -> upload button -> copy & share the link)
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
Share the debug log of SALT, latest version (advanced menu -> debug log -> upload button -> copy & share the link)
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Here you go: https://hastebin.com/yafukeyisu

Hi,
sorry if I ask again. Is the debug information i posted above helpful in this case?
Thanks for your help btw!

benni_g4 said:
Hi,
sorry if I ask again. Is the debug information i posted above helpful in this case?
Thanks for your help btw!
Click to expand...
Click to collapse
Yes because you can use the flashing part of SALT which makes things easier.
Just start a terminal in mAid and type:
sudo ~/programs/SALT/salt --experimental
This will allow flashing.
Download latest TWRP preview(!) for P.
Choose flash folder and browse to TWRP and choose BOOT as your target partition. Let it flash . Then either choose reboot in SALT or reboot manually .
If all went fine TWRP will boot without any interaction. While in TWRP push the TWRP image to the device and then flash TWRP to the RECOVERY partition (you must use the button to show IMG files). Then choose reboot and there recovery. TWRP will show up again this time from the recovery partition. Now flash the ROM of your choice and you should be back in business.
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
Yes because you can use the flashing part of SALT which makes things easier.
Just start a terminal in mAid and type:
sudo ~/programs/SALT/salt --experimental
This will allow flashing.
Download latest TWRP preview(!) for P.
Choose flash folder and browse to TWRP and choose BOOT as your target partition. Let it flash . Then either choose reboot in SALT or reboot manually .
If all went fine TWRP will boot without any interaction. While in TWRP push the TWRP image to the device and then flash TWRP to the RECOVERY partition (you must use the button to show IMG files). Then choose reboot and there recovery. TWRP will show up again this time from the recovery partition. Now flash the ROM of your choice and you should be back in business.
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
I followed your instructions and selected the flash folder containing the TWRP preview image file. Then, I need to choose the partitions I want to flash. My TWRP preview image is displayed there, as shown in the picture.
{
"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"
}
I don't understand, how I can choose the BOOT partition here. I thought, I could simply type in the string "BOOT" in the "Target Partition" column. But after pressing FLASH, two error dialogs appear.
This is the according log output:
Code:
2020-06-10 17:25:06: F_FLASHPART: started
2020-06-10 17:25:17: F_FLASHPART: IMGDIR=/home/benjamin/Downloads/twrp_flash
2020-06-10 17:25:17: F_CHKDEVCON: started
LGLAF.py: DEBUG: product id in CR list: >LG_new<
LGLAF.py: DEBUG: Device is: 633a, LG_new. Enabling Challenge/Response!
LGLAF.py: DEBUG: Final CR detection: None / 1
LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
LGLAF.py: DEBUG: Using Protocol version: 0x1000001
LGLAF.py: DEBUG: CR detection: 1
LGLAF.py: DEBUG: Hello done, proceeding with commands
LGLAF.py: DEBUG: Challenge: b'1a63780b'
LGLAF.py: DEBUG: Response: b'764940f602e3805cb7098e6d602cbaed'
LGLAF.py: DEBUG: KILO METR Response -> Header: b'4b494c4f4d455452000000000200000000000000000000002f5d0000b4b6b3b0', Body: b''
LGLAF.py: DEBUG: Header: b'EXEC' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\x1fW\0\0' b'\xba\xa7\xba\xbc'
2020-06-10 17:25:17: F_CHKDEVCON: Device seems to be connected!
2020-06-10 17:25:17: RET: 0
2020-06-10 17:25:17: F_USUVARVALID: started
2020-06-10 17:25:17: F_FLASHPART: will display all files (USUOVERRIDE=FALSE)
2020-06-10 17:25:17: F_FLASHPART: image files: twrp-3.3.1-PREVIEW-213_g4_P.img
2020-06-10 17:25:17: F_FLASHPART: created yad list: true
twrp-3.3.1-PREVIEW-213_g4_P.img
twrp-3.3.1-PREVIEW-213_g4_P
unknown-type
2
2020-06-10 17:25:30: F_FLASHPART BTNRET: 0
2020-06-10 17:25:30: choosen partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:BOOT:unknown-type:2 -> 1
2020-06-10 17:25:30: sorted partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:BOOT -> 1
2020-06-10 17:25:30: F_VERIFYDARB: started with /home/benjamin/Downloads/twrp_flash
2020-06-10 17:25:30: F_CDARB: started
2020-06-10 17:25:31: F_CDARB: ARB partition seems to be: sbl1
2020-06-10 17:25:32: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2020-06-10 17:25:32: F_CDARB: ended
2020-06-10 17:25:32: F_VERIFYDARB: KARB: , DARB: 0:0,
CHKMRES: unknown VS. unknown
2020-06-10 17:25:32: F_ERR: started
2020-06-10 17:25:32: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
2020-06-10 17:25:32: F_MSGE: started
2020-06-10 17:25:34: ERROR:
ERROR!
Device ARB or file-based ARB cannot be checked! ABORTED!!
2020-06-10 17:25:34: 0
2020-06-10 17:25:34: F_EXIT: started
2020-06-10 17:25:34: EXIT: F_VERIFYDARB->F_ERR with code 4
2020-06-10 17:25:34: F_ERR: started
2020-06-10 17:25:34: ERROR: 3 occurred in F_FLASHPART (expected 0, got 3)
2020-06-10 17:25:34: F_MSGE: started
2020-06-10 17:25:35: ERROR: Aborted on user check verification (2020-06-10 17:25:32: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
0
2020-06-10 17:25:34: EXIT: F_VERIFYDARB->F_ERR with code 4)
2020-06-10 17:25:35: 0
2020-06-10 17:25:35: F_EXIT: started
2020-06-10 17:25:35: EXIT: F_FLASHPART->F_ERR with code 4
2020-06-10 17:25:37: F_ADVMENU: started with LG-H815
2020-06-10 17:25:37: F_ADVMENU: main YAD_PID is 7508
2020-06-10 17:25:38: CR setting: Auto =
2020-06-10 17:25:38: getlog script started
Am I doing something wrong, or is this related to something else?

benni_g4 said:
I followed your instructions and selected the flash folder containing the TWRP preview image file. Then, I need to choose the partitions I want to flash. My TWRP preview image is displayed there, as shown in the picture.
I don't understand, how I can choose the BOOT partition here. I thought, I could simply type in the string "BOOT" in the "Target Partition" column. But after pressing FLASH, two error dialogs appear.
This is the according log output:
Code:
2020-06-10 17:25:06: F_FLASHPART: started
2020-06-10 17:25:17: F_FLASHPART: IMGDIR=/home/benjamin/Downloads/twrp_flash
2020-06-10 17:25:17: F_CHKDEVCON: started
LGLAF.py: DEBUG: product id in CR list: >LG_new<
LGLAF.py: DEBUG: Device is: 633a, LG_new. Enabling Challenge/Response!
LGLAF.py: DEBUG: Final CR detection: None / 1
LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
LGLAF.py: DEBUG: Using Protocol version: 0x1000001
LGLAF.py: DEBUG: CR detection: 1
LGLAF.py: DEBUG: Hello done, proceeding with commands
LGLAF.py: DEBUG: Challenge: b'1a63780b'
LGLAF.py: DEBUG: Response: b'764940f602e3805cb7098e6d602cbaed'
LGLAF.py: DEBUG: KILO METR Response -> Header: b'4b494c4f4d455452000000000200000000000000000000002f5d0000b4b6b3b0', Body: b''
LGLAF.py: DEBUG: Header: b'EXEC' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\x1fW\0\0' b'\xba\xa7\xba\xbc'
2020-06-10 17:25:17: F_CHKDEVCON: Device seems to be connected!
2020-06-10 17:25:17: RET: 0
2020-06-10 17:25:17: F_USUVARVALID: started
2020-06-10 17:25:17: F_FLASHPART: will display all files (USUOVERRIDE=FALSE)
2020-06-10 17:25:17: F_FLASHPART: image files: twrp-3.3.1-PREVIEW-213_g4_P.img
2020-06-10 17:25:17: F_FLASHPART: created yad list: true
twrp-3.3.1-PREVIEW-213_g4_P.img
twrp-3.3.1-PREVIEW-213_g4_P
unknown-type
2
2020-06-10 17:25:30: F_FLASHPART BTNRET: 0
2020-06-10 17:25:30: choosen partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:BOOT:unknown-type:2 -> 1
2020-06-10 17:25:30: sorted partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:BOOT -> 1
2020-06-10 17:25:30: F_VERIFYDARB: started with /home/benjamin/Downloads/twrp_flash
2020-06-10 17:25:30: F_CDARB: started
2020-06-10 17:25:31: F_CDARB: ARB partition seems to be: sbl1
2020-06-10 17:25:32: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2020-06-10 17:25:32: F_CDARB: ended
2020-06-10 17:25:32: F_VERIFYDARB: KARB: , DARB: 0:0,
CHKMRES: unknown VS. unknown
2020-06-10 17:25:32: F_ERR: started
2020-06-10 17:25:32: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
2020-06-10 17:25:32: F_MSGE: started
2020-06-10 17:25:34: ERROR:
ERROR!
Device ARB or file-based ARB cannot be checked! ABORTED!!
2020-06-10 17:25:34: 0
2020-06-10 17:25:34: F_EXIT: started
2020-06-10 17:25:34: EXIT: F_VERIFYDARB->F_ERR with code 4
2020-06-10 17:25:34: F_ERR: started
2020-06-10 17:25:34: ERROR: 3 occurred in F_FLASHPART (expected 0, got 3)
2020-06-10 17:25:34: F_MSGE: started
2020-06-10 17:25:35: ERROR: Aborted on user check verification (2020-06-10 17:25:32: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
0
2020-06-10 17:25:34: EXIT: F_VERIFYDARB->F_ERR with code 4)
2020-06-10 17:25:35: 0
2020-06-10 17:25:35: F_EXIT: started
2020-06-10 17:25:35: EXIT: F_FLASHPART->F_ERR with code 4
2020-06-10 17:25:37: F_ADVMENU: started with LG-H815
2020-06-10 17:25:37: F_ADVMENU: main YAD_PID is 7508
2020-06-10 17:25:38: CR setting: Auto =
2020-06-10 17:25:38: getlog script started
Am I doing something wrong, or is this related to something else?
Click to expand...
Click to collapse
sorry the BOOT was just in uppercase to highlight it (because it is unusual to flash a recover to the boot partition).
so simply type "boot" there (lower case) and it should work.
.-

steadfasterX said:
sorry the BOOT was just in uppercase to highlight it (because it is unusual to flash a recover to the boot partition).
so simply type "boot" there (lower case) and it should work.
.-
Click to expand...
Click to collapse
I tried it again with lower case, but the error message remains the same. Also the log output didn't really change, except that "boot" is now lower case, of course.
Code:
2020-06-11 13:44:41: F_FLASHPART: started
2020-06-11 13:44:54: F_FLASHPART: IMGDIR=/home/benjamin/Downloads/twrp_flash
2020-06-11 13:44:54: F_CHKDEVCON: started
LGLAF.py: DEBUG: product id in CR list: >LG_new<
LGLAF.py: DEBUG: Device is: 633a, LG_new. Enabling Challenge/Response!
LGLAF.py: DEBUG: Final CR detection: None / 1
LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
LGLAF.py: DEBUG: Using Protocol version: 0x1000001
LGLAF.py: DEBUG: CR detection: 1
LGLAF.py: DEBUG: Hello done, proceeding with commands
LGLAF.py: DEBUG: Challenge: b'6ac5a97c'
LGLAF.py: DEBUG: Response: b'5cc04d128e07296b63574a3034bc7435'
LGLAF.py: DEBUG: KILO METR Response -> Header: b'4b494c4f4d455452000000000200000000000000000000002f5d0000b4b6b3b0', Body: b''
LGLAF.py: DEBUG: Header: b'EXEC' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\x1fW\0\0' b'\xba\xa7\xba\xbc'
2020-06-11 13:44:54: F_CHKDEVCON: Device seems to be connected!
2020-06-11 13:44:54: RET: 0
2020-06-11 13:44:54: F_USUVARVALID: started
2020-06-11 13:44:54: F_FLASHPART: will display all files (USUOVERRIDE=FALSE)
2020-06-11 13:44:54: F_FLASHPART: image files: twrp-3.3.1-PREVIEW-213_g4_P.img
2020-06-11 13:44:54: F_FLASHPART: created yad list: true
twrp-3.3.1-PREVIEW-213_g4_P.img
twrp-3.3.1-PREVIEW-213_g4_P
unknown-type
2
2020-06-11 13:45:12: F_FLASHPART BTNRET: 0
2020-06-11 13:45:12: choosen partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot:unknown-type:2 -> 1
2020-06-11 13:45:12: sorted partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot -> 1
2020-06-11 13:45:12: F_VERIFYDARB: started with /home/benjamin/Downloads/twrp_flash
2020-06-11 13:45:12: F_CDARB: started
2020-06-11 13:45:12: F_CDARB: ARB partition seems to be: sbl1
2020-06-11 13:45:13: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2020-06-11 13:45:13: F_CDARB: ended
2020-06-11 13:45:13: F_VERIFYDARB: KARB: , DARB: 0:0,
CHKMRES: unknown VS. unknown
2020-06-11 13:45:13: F_ERR: started
2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
2020-06-11 13:45:13: F_MSGE: started
2020-06-11 13:45:20: ERROR:
ERROR!
Device ARB or file-based ARB cannot be checked! ABORTED!!
2020-06-11 13:45:20: 0
2020-06-11 13:45:20: F_EXIT: started
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4
2020-06-11 13:45:20: F_ERR: started
2020-06-11 13:45:20: ERROR: 3 occurred in F_FLASHPART (expected 0, got 3)
2020-06-11 13:45:20: F_MSGE: started
2020-06-11 13:45:28: ERROR: Aborted on user check verification (2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
0
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4)
2020-06-11 13:45:28: 0
2020-06-11 13:45:28: F_EXIT: started
2020-06-11 13:45:28: EXIT: F_FLASHPART->F_ERR with code 4
2020-06-11 13:47:05: F_ADVMENU: started with LG-H815
2020-06-11 13:47:05: F_ADVMENU: main YAD_PID is 5304
2020-06-11 13:47:07: CR setting: Auto =
2020-06-11 13:47:07: getlog script started

benni_g4 said:
I tried it again with lower case, but the error message remains the same. Also the log output didn't really change, except that "boot" is now lower case, of course.
Code:
2020-06-11 13:44:41: F_FLASHPART: started
2020-06-11 13:44:54: F_FLASHPART: IMGDIR=/home/benjamin/Downloads/twrp_flash
2020-06-11 13:44:54: F_CHKDEVCON: started
LGLAF.py: DEBUG: product id in CR list: >LG_new<
LGLAF.py: DEBUG: Device is: 633a, LG_new. Enabling Challenge/Response!
LGLAF.py: DEBUG: Final CR detection: None / 1
LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
LGLAF.py: DEBUG: Using Protocol version: 0x1000001
LGLAF.py: DEBUG: CR detection: 1
LGLAF.py: DEBUG: Hello done, proceeding with commands
LGLAF.py: DEBUG: Challenge: b'6ac5a97c'
LGLAF.py: DEBUG: Response: b'5cc04d128e07296b63574a3034bc7435'
LGLAF.py: DEBUG: KILO METR Response -> Header: b'4b494c4f4d455452000000000200000000000000000000002f5d0000b4b6b3b0', Body: b''
LGLAF.py: DEBUG: Header: b'EXEC' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\x1fW\0\0' b'\xba\xa7\xba\xbc'
2020-06-11 13:44:54: F_CHKDEVCON: Device seems to be connected!
2020-06-11 13:44:54: RET: 0
2020-06-11 13:44:54: F_USUVARVALID: started
2020-06-11 13:44:54: F_FLASHPART: will display all files (USUOVERRIDE=FALSE)
2020-06-11 13:44:54: F_FLASHPART: image files: twrp-3.3.1-PREVIEW-213_g4_P.img
2020-06-11 13:44:54: F_FLASHPART: created yad list: true
twrp-3.3.1-PREVIEW-213_g4_P.img
twrp-3.3.1-PREVIEW-213_g4_P
unknown-type
2
2020-06-11 13:45:12: F_FLASHPART BTNRET: 0
2020-06-11 13:45:12: choosen partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot:unknown-type:2 -> 1
2020-06-11 13:45:12: sorted partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot -> 1
2020-06-11 13:45:12: F_VERIFYDARB: started with /home/benjamin/Downloads/twrp_flash
2020-06-11 13:45:12: F_CDARB: started
2020-06-11 13:45:12: F_CDARB: ARB partition seems to be: sbl1
2020-06-11 13:45:13: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2020-06-11 13:45:13: F_CDARB: ended
2020-06-11 13:45:13: F_VERIFYDARB: KARB: , DARB: 0:0,
CHKMRES: unknown VS. unknown
2020-06-11 13:45:13: F_ERR: started
2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
2020-06-11 13:45:13: F_MSGE: started
2020-06-11 13:45:20: ERROR:
ERROR!
Device ARB or file-based ARB cannot be checked! ABORTED!!
2020-06-11 13:45:20: 0
2020-06-11 13:45:20: F_EXIT: started
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4
2020-06-11 13:45:20: F_ERR: started
2020-06-11 13:45:20: ERROR: 3 occurred in F_FLASHPART (expected 0, got 3)
2020-06-11 13:45:20: F_MSGE: started
2020-06-11 13:45:28: ERROR: Aborted on user check verification (2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
0
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4)
2020-06-11 13:45:28: 0
2020-06-11 13:45:28: F_EXIT: started
2020-06-11 13:45:28: EXIT: F_FLASHPART->F_ERR with code 4
2020-06-11 13:47:05: F_ADVMENU: started with LG-H815
2020-06-11 13:47:05: F_ADVMENU: main YAD_PID is 5304
2020-06-11 13:47:07: CR setting: Auto =
2020-06-11 13:47:07: getlog script started
Click to expand...
Click to collapse
ah ok. just do a backup in SALT and choose custom. There select aboot and sbl1 and after the backup copy them in the same dir as the twrp image and try again.
.-

steadfasterX said:
ah ok. just do a backup in SALT and choose custom. There select aboot and sbl1 and after the backup copy them in the same dir as the twrp image and try again.
.-
Click to expand...
Click to collapse
Awesome!
Just installed your newest LineageOS build and everything is working again. Thanks for your help, I would never have succeeded without you!
I donated to your Account to support your work.