H815 UK version ....unlocked boot loader and got the dreaded bootloop soft brick ........is it worth waiting for flash tool to get updated or should I just send back to repair ....anyone guess on a time span for LG flash tool to get updated or if it ever will
Gone back to LG g2 for time being
flashtool update ... not really . is not possible to know that . just wait
I recently successfully unlocked bootloader on my H815 EUR version, v20a. I then proceeded to flash TWRP after booting into it from fastboot. I let the phone restart to make sure everything is ok. Then I went back into TWRP to flash SU. After that, I got a bootloop stuck at LG logo. Luckily I was able to use LG Bridge to flash back to stock and get rid of bootloop.
My question is, how come I got a bootloop? Is it worth it to try to root my phone again? I want to be able to use titanium backup to transfer stuff from my old phone. I also want to use xposed.
Hello,
Today my Phone suddenly started to reboot at first it just did a reboot normaly but afterwards it started to reboot again but now I am stcuk in the screen with the lg logo and the bootloader unlocked message I tried to boot into recovery but after I choose to do factory reset so i can boot into twrp, again it only boots to the screen with lg logo and bootloader unlocked message.
I am on Genesys Rom and did not install any Mods
is there anyway for me to fix this?
Please help me
jizang said:
Hello,
Today my Phone suddenly started to reboot at first it just did a reboot normaly but afterwards it started to reboot again but now I am stcuk in the screen with the lg logo and the bootloader unlocked message I tried to boot into recovery but after I choose to do factory reset so i can boot into twrp, again it only boots to the screen with lg logo and bootloader unlocked message.
I am on Genesys Rom and did not install any Mods
is there anyway for me to fix this?
Please help me
Click to expand...
Click to collapse
unlocking the bootloade voids your warranty.. only way is to send it to LG... or used the modded KDZ to disable big cores... in case you ncaat fix it. or get new motherboard..
raptorddd said:
unlocking the bootloade voids your warranty.. only way is to send it to LG... or used the modded KDZ to disable big cores... in case you ncaat fix it. or get new motherboard..
Click to expand...
Click to collapse
So its not software related? Is there anyway to disable the bootloader unlocked message?
jizang said:
So its not software related? Is there anyway to disable the bootloader unlocked message?
Click to expand...
Click to collapse
bootloop not software but hardware... but you could try flashing KDZ using LGUP. ive seen some claim theirs worked after flashinf stock firmware if it continues then hardware but most likely its hardware..
mines is unlockable.. and trying to keep it that way for the same reason... ive seen a post that says it can be relocked...
heres is the post.. i would like to ask you a favor if you try it.. make video of it .. to prove it works..
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
This is the reason why i swap my G4 H818P to Korean Variant G4. The Bootloop problem. Korean Variant is perfect for me. Strong 4G signal and no more SMS Limits in Marshmallow official update.
Sent from my LG-F500S using Tapatalk
I have the 2016 Motorola Z Play, running 7.1.1. I was able to find instructions for replacing the recovery for this model (Addison) via adb, It appeared to work successfully, but I cannot boot into the recovery (Baseband Version M8953_10229.50.04.65R Addison_VZW_CUST. I am not eligible to have my Verizon model be bootloader unlocked via Motorola. Is there any way at all I can get TWRP on this model, a custom rom, and root? My phone is able to boot into the standard rom without issue. Thanks in advance.
As far as I know, there is no way to get TWRP/anything custom on a Verizon locked device without exploits. I'm not aware of any exploits for the Z Play that may allow you to do so, and with a locked bootloader, if you did try to flash anything non-stock, you may either experience it failing to flash/work or have a bootloop. The bootloop could require a stock ROM reflash (of the Verizon 7.1.1 variant). What happens when you boot to the recovery now, do you still see the 'no command' and the Android laying on its back?
I'm not sure if you can flash OTA updates if you've replaced your recovery, it might be that the Verizon and retail variants are similar enough that OTA updates may flash without issue, but only trying to update would answer that question.
I should clarify this restriction seems to be for devices bought through Verizon (i.e. have a vzw software channel), whereas retail devices on Verizon may not have the same bootloader restriction.
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Amitie10g said:
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Click to expand...
Click to collapse
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Spaceminer said:
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Click to expand...
Click to collapse
1.- Maybe, depending the country. So, the agent who attended me told me the warranty is void just when unlocking the Bootloader. Motorola's technical service will give the last word about that, as I have re-installed the stock rom.
2.- As I told, the phone don't seems to power on and no charging light. I've connected to the computer and it never identifies as anything than a brick.
3.- Per above, Fastboot won't recognize the device and unable to send commands to the device in any way. In other words, the device seems to be completely dead.
The vendor where I purchased the device just told me they will replace the device under the warranty.
So, I'll apply the updates via OTA and tell you the results, but I'll not unlock the bootloader, but backup upload the ROM via Fastboot and TWRP, and upload it.
I've finally gone to the vendor to retire the replacement device.
However, they don't have the Moto G6 Play available anymore. Instead, they gave me the Moto G6 (better device except for the battery) for free, as the failure has been covered under the warranty.
Advices:
Ask your vendor the repair costs for failures caused by failed firmware updates. I assume Motorola didn't checked even if the bootloader is unlocked (as the device seems to be completely dead), they just decided to replace the device.
Don't send the device to the technical service if it powers on and Fastboot is working unless you're prepared to pay the repairs.
Don't try to install the Android Pie update with the bootloader unlocked and firmware altered.
acutally, updating with unlocked bootloader causes nothing. that might have been a hardware problem of some source, idk...
---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------
but unlocking the bootloader does void your warranty tho
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Amitie10g said:
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Click to expand...
Click to collapse
Not true. My bootloader is unlocked, and Motorola is well aware of that since I had to ask them for the key. Unlocking it by itself doesn't void it. It's what you do afterwards that might void it. Like running an over volted kernel and frying something. Check the screen shot. My warranty is still good until Aug of this year. And if I really wanted to I could just relock the bootloader before sending it in, which blows that theory out of the water.
i replaced one under warranty with no issue. with an unlocked boot loader. twice.