I thought it was because I dirty flashed it, but then I tried clean-flash, very clean with wiping a lot except the internalSD.
I clean-flashed 3 times your unofficial LOS-13 2017oct30 with bootloop. But I believe very much in you and you are welcome to be my room-mate.
H815 EU.
Solved to enter Recovery by giving up and I was ready to delete the whole **** in my phone. Luckily, the LG factory reset question with white background took me to TWRP.
I succeed to enter TWRP 3.1.1.1 by accepting a total factory reset, luckily the factory-scripts opened recovery image TWRP for me, and that was the surprise. It didn't delete anything, not even the internal SD.
Of course, in my case, TWRP can reboot to bootloader-mode.
But recovery-mode was more than enough for me
I will try a newer weekly nightly. :highfive:
I'm glad I'm not the only one who met the same problem !
@datorprofessor*:
Since you'll be trying the next nightlies, could you post your results ? Thank you !*
- said:AF[-Death;74383200]Same thing with me. Land in the bootloop, too.
The last working one was the lineage-13.0-20171002-UNOFFICIAL-h815. zip, but the GPS didn't work.
Yea sorry guys.. I had no time yet to fix that. It's due to incompatible blobs..
EDIT: Found H815 firmware from Spain and England
https://lg-firmwares.com/lg-h815-firmwares/
Can you guys tell me which bootloader you flashed? The new blobs are based on 20p so you should try to flash 20p kdz first then the newest nightly. Would be a great help if someone is willing to try that..
Sent from my LG-H815 using XDA Labs
Fastboot getvar all
yes Sir!, I'll change my bootloader. I think mine bootloader is old.
gives back version 0.5 for my bootloader, but that maybe not exactly the correct return. Where can I find the 20p information on my phone?Code:Fastboot getvar all
Ultimately, the best would be if you have some bootloader & modem only zips, instead of whole stock-rom becuase I have limited internet right now. I go to a friend and do it
freedom rom 2nd post. tap and go find the firmware you want to flash
Thank You!
More precisely, it was this:
https://androidfilehost.com/?w=files&flid=194933
It was even flashable.zip for Recovery-mode :good:
The file.zip hadn't any md5 zip verification, for such fragile thing as a bootloader-partiton. :cyclops:
Update: Still bootlooping after 20p modem- & -bootloader-flashZipping; with LOS-13 2017oct30
Do your thing SteadfasterX! Do your thing at your tempo; I'll be back, Later! Alligator!
many thx for testing this! too bad it hasnt worked though.
I have send my device to repair so i cant test anything atm.. i could revert to the old blobs in the meanwhile maybe..
UPDATE:
ok reverted to the old blobs. next build will contain them and so should boot again..
Check the build status here: once finished you will find the download on my server in the OP.
UPDATE 2:
New build up! Lemme know guys if that works again for you now..
sfX
Hi steadfasterX! Thank you for all your work
I was on 0813 build, encryption and no gapps installed.
I updated to this last build (1103) and the phone doesn't boot, it doesn't bootloop on the boot animation, the phone doesn't pass from the LG screen.
I'm on v20D bootloader and modem, what can I do to help? Count on me for testing if you want
I hope you understand my english, have a nice day :good:
Update: I tried a clean flash and the same happens
Same here.
I updated to the last build and doesn´t pass the LG Screen.
What can i make ? I can't get into recovery mode anymore either
I can enter in recovery mode without problems, reflashed last working build and phone boots normalthx for testing.
could you guys try to do an adb connection when the LG logo is showing like:
adb devices
and
adb shell
The recovery mode is not affected by installing LOS. you may use the wrong key combo? Do you see even the factory reset screen? What happens exactly when you try to go into TWRP?
.
Whatever, but after I've left the cell phone a while off I'm coming back to recovery with the key combination.
Have then the last working version installed and running.
By the way, I've made a mistake, the last working version is the lineage-13.0-20170927-UNOFFICIAL-h815.zip
thanks for your reports. I will check it asap..I can enter in recovery mode without problems, reflashed last working build and phone boots normal
I'm installing it again and I will try to make the adb connection.
EDIT: no device is detected when I run adb devices while on the lg logo.
I tried with your FWUL and same
I also tried this https://xdaforums.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818 and same
I've got the dmesg from twrp maybe it's useful for you? I've sent you a PM, I'm not sure if it contains personal data
thanks for your reports. I will check it asap..
afaik 20170927 is working but without GPS?
sfX
thx for testing.
could you guys try to do an adb connection when the LG logo is showing like:
adb devices
and
adb shell
and
adb shell mount
and
adb shell dmesg
and
adb logcat
If you get any results posts them on paste.omnirom.org and provide the link to the paste.
.
If someone wanna help me ( my device is still not back from repair):
Watch until the job here has finished :
EDIT:
Build finished
once finished you will find a new LOS release on my download server. Download and flash.
It will still fail to boot but now the above adb commands should work so pls paste the results as mentioned above
thx
steadfasterX
.
If you can connect with adb in TWRP and not when you see the LG logo it is not an issue on your site..I tried with 1106 and 1107 and I can't get adb connection, I don't know what to do to make it work or if I'm doing something wrong, is any special driver needed?
In twrp or in a booted up android I get the adb connection, I'm not an expert but I use sometimes adb, so I'm not that newbie...
What can I do to help?
Thanks steadfasterX :good:
Those new builds have security updates? Is it possible to have this last security update of november? Or we have to forget all that in our loved old lineageos 13?
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
It's my daily driver, phone doesn't get hot, really stable, latest security patches from lineageos tree (Is this right?)
Everything but no GPS, but if you want GPS you can stay on 0813 build.
Thanks again steadfasterX for building this!!!!
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
I tried all of them (that let me install, most of them are +7.0 required)
Last official google cam for 6.0.1,
And the snapdragon one (attached on the aoscp #2 post of the thread)
Open camera and the WhatsApp camera
Need more logcats? Using the experimental build since then and it's smoother and a lot better. Just missing my camera.
Have a nice day steadfasterX!