Related
What is the best way to root G4, whilst keeping it "friendly" for warranty claims?!?
Hi, forgive me if this thread isn't in the appropriate section.
I have a bit of rooting experience, haven't done much in a few years though, (knowing that there are now several ways to root devices), and have just picked up the G4.
Now I'd like to root the G4, but keep the stock rom, (6.0) and mainly will be just running xposed to edit and muck around with LG's ugly skin. I'd still like to be able to receive OTA updates, (even if the OTA update may remove my root,) as well as hopefully still be fine if I needed to return the device under warren.
I've been reading around and apparently you must unlock the bootloader in order to root for Marshmallow? If i were to still do this, could I keep the stock recovery at least, or if not, would I be able to easily revert to stock with a stock recovery and relock the bootloader?
Apologies for my ignorance, just trying to figure out if I should really be rooting or just chuck on Nova launcher and be happy with LG's offerings. Cheers
Keep it on a stock rom and if yoi have a carrier varient then try to not change the boot logo lol idk just a guess.
Jared_Anderson said:
Hi, forgive me if this thread isn't in the appropriate section.
I have a bit of rooting experience, haven't done much in a few years though, (knowing that there are now several ways to root devices), and have just picked up the G4.
Now I'd like to root the G4, but keep the stock rom, (6.0) and mainly will be just running xposed to edit and muck around with LG's ugly skin. I'd still like to be able to receive OTA updates, (even if the OTA update may remove my root,) as well as hopefully still be fine if I needed to return the device under warren.
I've been reading around and apparently you must unlock the bootloader in order to root for Marshmallow? If i were to still do this, could I keep the stock recovery at least, or if not, would I be able to easily revert to stock with a stock recovery and relock the bootloader?
Apologies for my ignorance, just trying to figure out if I should really be rooting or just chuck on Nova launcher and be happy with LG's offerings. Cheers
Click to expand...
Click to collapse
Yes to reflashing stock rom
Yes to relocking the bootloader
So you are clear to make whatever modifications you want, you can always revert safely.
Vseprz said:
Yes to reflashing stock rom
Yes to relocking the bootloader
So you are clear to make whatever modifications you want, you can always revert safely.
Click to expand...
Click to collapse
Once your bootloader is unlocked, you cannot relock it. Your device will always show a message saying "Bootloader unlocked" after turned on. Warranty is likely to be declined then. BTW: You have to get your unlock.bin file from lg, agreeing to void your warranty. So, even if you smash your screen and they cannot see the message, lg knows it is out of warranty.
pen² said:
Once your bootloader is unlocked, you cannot relock it. Your device will always show a message saying "Bootloader unlocked" after turned on. Warranty is likely to be declined then. BTW: You have to get your unlock.bin file from lg, agreeing to void your warranty. So, even if you smash your screen and they cannot see the message, lg knows it is out of warranty.
Click to expand...
Click to collapse
Since when do you have to get the unlock.bin? We unlock from fastboot. Have you confirmed by trying to relock from fastboot? I read otherwise from another thread.
Furthermore, a quick search around indicates people who have unlocked and rooted have had their warranty honored despite software changes.
Vseprz said:
Since when do you have to get the unlock.bin? We unlock from fastboot. Have you confirmed by trying to relock from fastboot? I read otherwise from another thread.
Furthermore, a quick search around indicates people who have unlocked and rooted have had their warranty honored despite software changes.
Click to expand...
Click to collapse
Unlock from fastboot is only possible after flashing said unlock.bin file, which can only be obtained by lg and is unique for each device. Furthermore, I had an unlocked, bootlooping h815 and lg refused warranty to me (in Germany). Got my phone replaced by my vendor on eu law which only applies if the defect strikes in the first six months.
So, while some people are lucky to have their phone repaired despite an unlocked bootloader, I'm really happy for them, but lg is not bound to repair it on warranty
pen² said:
Unlock from fastboot is only possible after flashing said unlock.bin file, which can only be obtained by lg and is unique for each device. Furthermore, I had an unlocked, bootlooping h815 and lg refused warranty to me (in Germany). Got my phone replaced by my vendor on eu law which only applies if the defect strikes in the first six months.
So, while some people are lucky to have their phone repaired despite an unlocked bootloader, I'm really happy for them, but lg is not bound to repair it on warranty
Click to expand...
Click to collapse
Ah I see. You have a h815. I have a h811. Our process differs there.
Hmmm, thanks for the info guys. Its not from a carrier, i bought it outright. Seems like i might just have to keep it stock, its not too bad as is, guess ill just have to live with it. Thanks for the help though.
Jared_Anderson said:
Hmmm, thanks for the info guys. Its not from a carrier, i bought it outright. Seems like i might just have to keep it stock, its not too bad as is, guess ill just have to live with it. Thanks for the help though.
Click to expand...
Click to collapse
At least you can root with locked bootloader
Not under marshmallow
You can do none of things you listed keeping it stock. First of all google change policy and in marshmallow you need to flash modified boot.img in order to flash custom recovery and/or to root it. As you know the bootloader has to be unlocked but there is no way to relock it. So sorry, but impossible.
People need to understand a simple thing.
You either mod your device and lose warranty or you keep it stock.
It's that simple. People worried about warranties and ota updates are on the wrong site.
hello, good morning, this is my first topic, I do not know if I'm posting in the correct location, if not, please correct me.
I bought a moto z2 play and a camera error resulted in a big problem, first asked to restart and so I did, the second time came the problem, it just does not stay more than 3 seconds on the welcome screen, I already tried hard reset , I already installed another stock, already tried to start in safe mode and nothing, unlocking oem and debugging usb are disabled, I contacted the motorola to ask the unlock code oem for the code obtained by fastboot and they told me that it would not be possible give me such a code, and now, is there anything I can do?
This doesn't seem to be a modding problem, looks more like hardware... so I'd strongly reccomend you NOT to void your warranty by unlocking bootloader. Send it to an official repair center and hope they either fix or replace the phone...
hi, so I was trying to unlock the bootloader before attempting to use an AOSP pie rom using this guide on the official LG site http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Anyway when I come to step 9, I type "adb reboot bootloader" and the phone reboots in fastboot mode. Then when I type "fastboot oem device-id" the phone freezes and I have to press the power button to restart it, meanwhile in the powershell command page it says
Code:
C:\Users\chahi\AppData\Local\Android\Sdk\platform-tools>fastboot oem device-id
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
I checked my drivers and everything seems to work perfectly fine. I am at my fifth attempt and I'm beginning to feel pretty desperate. If anyone encountered the same problem or could help me solve this I will be very thankful !
Thanks in advance.
NB : I'm on windows 10 and my phone is running the korean pie rom.
Piatch said:
hi, so I was trying to unlock the bootloader before attempting to use an AOSP pie rom using this guide on the official LG site http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Anyway when I come to step 9, I type "adb reboot bootloader" and the phone reboots in fastboot mode. Then when I type "fastboot oem device-id" the phone freezes and I have to press the power button to restart it, meanwhile in the powershell command page it says
Code:
C:\Users\chahi\AppData\Local\Android\Sdk\platform-tools>fastboot oem device-id
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
I checked my drivers and everything seems to work perfectly fine. I am at my fifth attempt and I'm beginning to feel pretty desperate. If anyone encountered the same problem or could help me solve this I will be very thankful !
Thanks in advance.
NB : I'm on windows 10 and my phone is running the korean pie rom.
Click to expand...
Click to collapse
I cannot 100% say what the cause is with certainty (I have the Sprint version and I absolutely hate this piece of trash) but others have reported similar issues from actually having a different variant that was cross-flashed to the EM model and sold as EM when it's really a Sprint version (for example). What happens when you enter your IMEI number in LG site, does it return the EM variant or something else? That's where I would start (unless you have already done this and confirmed it's EM). Non EM versions lack the full ADB support so we can't unlock the bootloader. This is the same point I lockup as well but mine was not intended to be unlocked.
GROOVYJOSHCLARK said:
I cannot 100% say what the cause is with certainty (I have the Sprint version and I absolutely hate this piece of trash) but others have reported similar issues from actually having a different variant that was cross-flashed to the EM model and sold as EM when it's really a Sprint version (for example). What happens when you enter your IMEI number in LG site, does it return the EM variant or something else? That's where I would start (unless you have already done this and confirmed it's EM). Non EM versions lack the full ADB support so we can't unlock the bootloader. This is the same point I lockup as well but mine was not intended to be unlocked.
Click to expand...
Click to collapse
Thank you for the quick response !
Yes I actually typed my IMEI in the LG site and it gave me a gray OK so I guess I truly have the EM version ? (knowing that only the EM is supported idk) Are there other methods to make sure I have the EM version for sure ? Also worth noting that I bought the phone new from North Africa so it must be the european version and not a carrier one.
Thank you !
Piatch said:
Thank you for the quick response !
Yes I actually typed my IMEI in the LG site and it gave me a gray OK so I guess I truly have the EM version ? (knowing that only the EM is supported idk) Are there other methods to make sure I have the EM version for sure ? Also worth noting that I bought the phone new from North Africa so it must be the european version and not a carrier one.
Thank you !
Click to expand...
Click to collapse
Not that I'm aware of but if the LGdev site let you get the unlock code then I will assume it's real as they do validate it. Normally I would suggest to reach out to LG but that's a waste, they won't help. In fact they shutdown the dev recently because of unlock requests so they don't care about us so that won't help you. I'll do some research and see if there's any official way to help but hopefully others will chime in with the answers.
GROOVYJOSHCLARK said:
Not that I'm aware of but if the LGdev site let you get the unlock code then I will assume it's real as they do validate it. Normally I would suggest to reach out to LG but that's a waste, they won't help. In fact they shutdown the dev recently because of unlock requests so they don't care about us so that won't help you. I'll do some research and see if there's any official way to help but hopefully others will chime in with the answers.
Click to expand...
Click to collapse
That's what I actually did, I sent them an email but I'm still without any response. Thank you for your help tho ! Is there any unofficial way to unlock the bootloader on the LG G7 that I'm unaware of ?
Piatch said:
That's what I actually did, I sent them an email but I'm still without any response. Thank you for your help tho ! Is there any unofficial way to unlock the bootloader on the LG G7 that I'm unaware of ?
Click to expand...
Click to collapse
Good luck with LG, they most likely will do nothing to assist you. That's my biggest gripe with LG, they suck with customer care nor give 2 craps about us, the customers. My LGG7 sucks so bad, it's barely usable but they will not do anything to help me nor Sprint so I'm leaving both once my horrible lease is up. All I can say is to sign the bootloader petition and leave LG, it's the only way they will ever change and even then, they probably won't. They will soon be out of business just like Blackberry's downfall and for the same reasons. They don't listen to the customers and change, nor did RIM with activesync, now RIM is a mere fraction of what they used to be, LG mobile is next. I hear so many complaints about LG devices, not just LG mobile but the entire company. All the same type of complaints across all LG products, no customer support when the device stops working and they pass the buck every time, and locked bootloaders (for LG mobile).
There is no unofficial unlock yet, that's why I'm so unhappy with the piece of junk! If I could unlock and install my own flavor of AOSP then it would be an entirely different story and I would fix my own issues and have an awesome device. Instead the jackalope in charge of LG decided to keep the bootloaders locked with no support to unlock (except for EM) but even that barely works (your issue).
I don't know what else to say except LG SUCKS, LG is terrible. I so wish I hadn't let the Sprint rep bully me into this horrific device. I should have stood my ground and not accepted the deal which came with this expensive paperweight (LGG7).
GROOVYJOSHCLARK said:
Good luck with LG, they most likely will do nothing to assist you. That's my biggest gripe with LG, they suck with customer care nor give 2 craps about us, the customers. My LGG7 sucks so bad, it's barely usable but they will not do anything to help me nor Sprint so I'm leaving both once my horrible lease is up. All I can say is to sign the bootloader petition and leave LG, it's the only way they will ever change and even then, they probably won't. They will soon be out of business just like Blackberry's downfall and for the same reasons. They don't listen to the customers and change, nor did RIM with activesync, now RIM is a mere fraction of what they used to be, LG mobile is next. I hear so many complaints about LG devices, not just LG mobile but the entire company. All the same type of complaints across all LG products, no customer support when the device stops working and they pass the buck every time, and locked bootloaders (for LG mobile).
There is no unofficial unlock yet, that's why I'm so unhappy with the piece of junk! If I could unlock and install my own flavor of AOSP then it would be an entirely different story and I would fix my own issues and have an awesome device. Instead the jackalope in charge of LG decided to keep the bootloaders locked with no support to unlock (except for EM) but even that barely works (your issue).
I don't know what else to say except LG SUCKS, LG is terrible. I so wish I hadn't let the Sprint rep bully me into this horrific device. I should have stood my ground and not accepted the deal which came with this expensive paperweight (LGG7).
Click to expand...
Click to collapse
You can always pay to get your phone unlocked
LameMonster82 said:
You can always pay to get your phone unlocked
Click to expand...
Click to collapse
SIM unlocked, yes, bootloader unlocked, no (on Sprint and everything other than the European model, no, EM model, yes), the rest of us, no, huge difference. I would pay a small fortune if bootloader unlocks were possible and why I bought the LG octoplus, still no option yet unfortunately.
GROOVYJOSHCLARK said:
SIM unlocked, yes, bootloader unlocked, no (on Sprint and everything other than the European model, no, EM model, yes), the rest of us, no, huge difference. I would pay a small fortune if bootloader unlocks were possible and why I bought the LG octoplus, still no option yet unfortunately.
Click to expand...
Click to collapse
It's possible to pay for a hacker in china to unlock the phone (bootloader unlock)
LameMonster82 said:
It's possible to pay for a hacker in china to unlock the phone (bootloader unlock)
Click to expand...
Click to collapse
Send me the info please
GROOVYJOSHCLARK said:
Send me the info please
Click to expand...
Click to collapse
I don't know from where exactly. You have to find it yourself but eBay is a place to start.
LameMonster82 said:
I don't know from where exactly. You have to find it yourself but eBay is a place to start.
Click to expand...
Click to collapse
Are you 100% sure this is not SIM unlocked using a modified octoplus (I have already gone down this path) so I bought my own octoplus. I am pretty sure all these "unlock" are merely SIM unlocks and not bootloader unlocks. I've investigated this pretty deep and it was only SIM unlocks not bootloader. As far as I'm aware, there is no hacks or mods to unlock the bootloaders for any LG G7 as of yet. eBay results are all SIM (which is simply using oct to apply the US-unkocked m ok model unlocking the SIM).
If you can find a REAL bootloader unlock method that works and unlocks my bootloader, I will PayPal you 20-30 bucks (I'm not joking). There is no method yet that anyone I know, knows of.
GROOVYJOSHCLARK said:
Are you 100% sure this is not SIM unlocked using a modified octoplus (I have already gone down this path) so I bought my own octoplus. I am pretty sure all these "unlock" are merely SIM unlocks and not bootloader unlocks. I've investigated this pretty deep and it was only SIM unlocks not bootloader. As far as I'm aware, there is no hacks or mods to unlock the bootloaders for any LG G7 as of yet. eBay results are all SIM (which is simply using oct to apply the US-unkocked m ok model unlocking the SIM).
If you can find a REAL bootloader unlock method that works and unlocks my bootloader, I will PayPal you 20-30 bucks (I'm not joking). There is no method yet that anyone I know, knows of.
Click to expand...
Click to collapse
It's not sim unlock
It works by installing g710em bootloader and then flashing an unlock.bin .It's actual bootloader unlock. You can probably even do it yourself on a octopus box but I'm not sure what does it allow and not allow you to do.
LameMonster82 said:
It's not sim unlock
It works by installing g710em bootloader and then flashing an unlock.bin .It's actual bootloader unlock. You can probably even do it yourself on a octopus box but I'm not sure what does it allow and not allow you to do.
Click to expand...
Click to collapse
Fantastic then I will investigate this new theory and if it works, reply to everyone. I've been waiting for this since day 1 with this terrible G7, I HATE this device and OS.
---------- Post added at 12:16 PM ---------- Previous post was at 12:04 PM ----------
GROOVYJOSHCLARK said:
Fantastic then I will investigate this new theory and if it works, reply to everyone. I've been waiting for this since day 1 with this terrible G7, I HATE this device and OS.
Click to expand...
Click to collapse
If does exist, I can't find it on eBay or the internet, only SIM unlocks. I will keep checking but I don't see anything to unlock the G7 bootloaders.
GROOVYJOSHCLARK said:
Fantastic then I will investigate this new theory and if it works, reply to everyone. I've been waiting for this since day 1 with this terrible G7, I HATE this device and OS.
---------- Post added at 12:16 PM ---------- Previous post was at 12:04 PM ----------
If does exist, I can't find it on eBay or the internet, only SIM unlocks. I will keep checking but I don't see anything to unlock the G7 bootloaders.
Click to expand...
Click to collapse
I can try guiding you if you want to
LameMonster82 said:
I can try guiding you if you want to
Click to expand...
Click to collapse
Heck yes, if it's possible, I'm definitely in!
GROOVYJOSHCLARK said:
Heck yes, if it's possible, I'm definitely in!
Click to expand...
Click to collapse
I can send you abl_a and you just need to use my unlock.bin to unlock
Edit: can I send it to you privately so nothing personal leaks?
LameMonster82 said:
I can send you abl_a and you just need to use my unlock.bin to unlock
Edit: can I send it to you privately so nothing personal leaks?
Click to expand...
Click to collapse
please, PM me and I will respond, just let me know when you do so I know when to look (I dont normally watch PM's).
Piatch said:
hi, so I was trying to unlock the bootloader before attempting to use an AOSP pie rom using this guide on the official LG site http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Anyway when I come to step 9, I type "adb reboot bootloader" and the phone reboots in fastboot mode. Then when I type "fastboot oem device-id" the phone freezes and I have to press the power button to restart it, meanwhile in the powershell command page it says
Code:
C:\Users\chahi\AppData\Local\Android\Sdk\platform-tools>fastboot oem device-id
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
I checked my drivers and everything seems to work perfectly fine. I am at my fifth attempt and I'm beginning to feel pretty desperate. If anyone encountered the same problem or could help me solve this I will be very thankful !
Thanks in advance.
NB : I'm on windows 10 and my phone is running the korean pie rom.
Click to expand...
Click to collapse
Hey Piatch, i'm stuck on your same situation!
I have a new LMG710EM taken a month ago in a store, today with the Pie release (I'm in Italy) I found some time to unlock the bootloader, root, debrand (my G7 is TIM branded) and update to Pie.
I'm not new with LG, I come from G2, G5, G6 and now G7, never a problem (apart from the slowness in the updates I like them).
Well, just your situation, only the wording is a bit different, to me it says FAILED (Write to device failed (Too many links)) then the phone reboots and freezes in G7 logo and I have to press the power button to restart it, like yours.
I've tried everything, even reading online, different USB cables, different fastboot versions, but nothing worked.
Then I unbranded via lgup refurbish option to have a clean install and reinstalled all, thinking that maybe the new OS would solve but nothing, same message.
Can anyone help us?
It is the first time in several years that I have not found a solution.
Thank you in advance
f0ster52 said:
Hey Piatch, i'm stuck on your same situation!
I have a new LMG710EM taken a month ago in a store, today with the Pie release (I'm in Italy) I found some time to unlock the bootloader, root, debrand (my G7 is TIM branded) and update to Pie.
I'm not new with LG, I come from G2, G5, G6 and now G7, never a problem (apart from the slowness in the updates I like them).
Well, just your situation, only the wording is a bit different, to me it says FAILED (Write to device failed (Too many links)) then the phone reboots and freezes in G7 logo and I have to press the power button to restart it, like yours.
I've tried everything, even reading online, different USB cables, different fastboot versions, but nothing worked.
Then I unbranded via lgup refurbish option to have a clean install and reinstalled all, thinking that maybe the new OS would solve but nothing, same message.
Can anyone help us?
It is the first time in several years that I have not found a solution.
Thank you in advance
Click to expand...
Click to collapse
Hi f0ster, I did not find any solution because I was lacking the time and tbh the skill to do it. I think we can't unlock the bootloader while under Pie ? Maybe if we roll back to Oreo, then we can unlock it and then update to Pie again ? I don't have the skills nor the confidence to safely flash Oreo on the G7 (I had bad experiences with bootlooping on the G3 and G4). Maybe you could try this way and see if it works out for you ?
So, I must've flashed something wrong, cause now I get
{
"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 still have access to FASTBOOT and Download Mode but the Bootloader is locked!! The phone is Stock! No TWRP, no nothing
Is there any way to fix it? I guess sending it to the service is not an option since the phone had Lineage OS previously...
Lgup. Just flash a kdz
maydayind said:
Lgup. Just flash a kdz
Click to expand...
Click to collapse
This has no use, Lgup does not flash into kdz
maydayind said:
Lgup. Just flash a kdz
Click to expand...
Click to collapse
I did, nothing changes, even after LG UP says "COMPLETE" the phone reboots into that error again
Your phone is probably unlocked..
Make shure u use the right kdz
Make shure u flash everything
MihaiA7X said:
So, I must've flashed something wrong, cause now I get
I still have access to FASTBOOT and Download Mode but the Bootloader is locked!! The phone is Stock! No TWRP, no nothing
Is there any way to fix it? I guess sending it to the service is not an option since the phone had Lineage OS previously...
Click to expand...
Click to collapse
Unlock bootloader and flash a custom rom works if you have enabled oem unlock in developer option
Bricked mine too by going from a GSI to the stock euro kdz then relocking the bootloader. Tried using partition dl, refurbish, factory upgrade, etc every option besides the chip erase one.
I've run the dft option from lgup (it compares the partitions from the phone to the ones from the kdz) and it fails on the "ftm" partition, then I used the partition dl and selected only the ftm partition, ran dft again and it failed on the "PrimaryGPT" partition.
It may be unbricked via firehose/9008 I think but since there's no public firehose file for the G7 we're out of luck.
Welcome to the club!
I bricked mine 2 days ago... Same error message... Did the same steps as you...
I also had Fastboot and Download Mode in the beginning...
And no! Flashing a kdz with LGUP doesn't solve this! And it is LG to blame that this doesn't solve this because it should. Flashing stock should always set the phone back to initial state
Then something went wrong flashing with LGUP and I lost Download Mode - only with Fastboot mode left....
Maybe a last hope is using a guy with the right tools to flash from 9008 mode...
The good thing: You can't break 9008 mode if the hardware ins't broken
I am working on it - We got Download mode back already flashing the full kdz in 9008 mode...
Next try is to re-unlock the bootloader from 9008 mode...
I keep you informed...
MagicOJB said:
The good thing: You can't break 9008 mode if the hardware ins't broken
I am working on it - We got Download mode back already flashing the full kdz in 9008 mode...
Next try is to re-unlock the bootloader from 9008 mode...
I keep you informed...
Click to expand...
Click to collapse
Did you manage to bring it from a state where you were not able to use download mode to a functional download mode, if so, there's still hope.
If it would be possible to flash using QFIL but instead of using the laf partition from the stock kdz we use the v35 engineering laf instead, would it still check for the "Enable OEM Unlocking" tick for flashing partitions?
The partitions.xml file would need some adjustments since the laf partition sectors from the v35 eng laf will differ from the ones from the stock kdz.
I don't have my G7 atm, but I will try doing this once I get it back.
V35 engineering laf: https://androidfilehost.com/?fid=1395089523397937620
Using QFIL: https://www.youtube.com/watch?v=BmAuzbG9re4
waau said:
Did you manage to bring it from a state where you were not able to use download mode to a functional download mode, if so, there's still hope.
Click to expand...
Click to collapse
Yes (But some guy helped my from remote with a OctoPlus tool)
waau said:
If it would be possible to flash using QFIL but instead of using the laf partition from the stock kdz we use the v35 engineering laf instead, would it still check for the "Enable OEM Unlocking" tick for flashing partitions?
The partitions.xml file would need some adjustments since the laf partition sectors from the v35 eng laf will differ from the ones from the stock kdz.
I don't have my G7 atm, but I will try doing this once I get it back.
V35 engineering laf: https://androidfilehost.com/?fid=1395089523397937620
Using QFIL: https://www.youtube.com/watch?v=BmAuzbG9re4
Click to expand...
Click to collapse
I was thinking about using QualComm tools also, but for now I stick with the guy with OctoPlus tool - With the QualComm tools there are to many unknowns
Right now I wait for the guy and we try to unlock the bootloader again with the same tool, because flashing the kdz brought back the download mode, but still does not resolve the safety error message.
I hope with an unlocked bootloader I can boot up into system again - but I still don't know if we get the bootloader unlocked with this procedure
I have a suspicion ...
I think my phone wasn't "bricked" - or at least the cause was completely different from what I thought...
I also used the LineageOS image - which needed to install the Korean Pie first - and then I went back to European Oreo (TIM)
I think the safety error might be related to the bootloader downgrade from the "pie" to the "oreo" one again - so maybe everything went well with the flashing of the device
We try to bring back the "pie" bootloader to my phone ... let's see what happens... last hope...
Emm.. Problem is, i flashed Korean Pie from LG U+ and then flashed stock .kdz without relocking bootloader, and everything goes fine. My phone works like a charm, so i don't think downgrade is a problem... But i think there is a possibility, that downgrade is impossible when bootloader is locked.
ShadoV90 said:
Emm.. Problem is, i flashed Korean Pie from LG U+ and then flashed stock .kdz without relocking bootloader, and everything goes fine. My phone works like a charm, so i don't think downgrade is a problem... But i think there is a possibility, that downgrade is impossible when bootloader is locked.
Click to expand...
Click to collapse
with an unlocked bootloader the safety procedures are not in place
but sadly flashing the pie image did not fix it ...
Well, the store told me to send the phone to the service I sent them a picture of the problem beforehand...I hope they will fix it, fingers crossed
MihaiA7X said:
Well, the store told me to send the phone to the service I sent them a picture of the problem beforehand...I hope they will fix it, fingers crossed
Click to expand...
Click to collapse
When will you know?
Okay - If they really get this fixed it would be nice if they could share how they did it.
If you could provide a full backup of your phone (before setting up personal stuff) with the bootloader unlocked that would help others which are falling into this trap.
I don't count on my ebay "store".
I would also now think it is LG's fault. If you follow the link which is show with the error message it clearly states that you can get back to a safe state if you flash a stock image. That is how Google inteded it. I would say we did everthing right and because they implemented the safety feature not correctly we got stuck.
I try to connect to LG service and ask what the safety check is looking for and if the can build me a signed kdz with developer options set.
MagicOJB said:
When will you know?
Okay - If they really get this fixed it would be nice if they could share how they did it.
If you could provide a full backup of your phone (before setting up personal stuff) with the bootloader unlocked that would help others which are falling into this trap.
I don't count on my ebay "store".
I would also now think it is LG's fault. If you follow the link which is show with the error message it clearly states that you can get back to a safe state if you flash a stock image. That is how Google inteded it. I would say we did everthing right and because they implemented the safety feature not correctly we got stuck.
I try to connect to LG service and ask what the safety check is looking for and if the can build me a signed kdz with developer options set.
Click to expand...
Click to collapse
Well, since I'm residing in the European Union, we have a law that the European Council gave back in 1999 that states that any digital device doesn't lose it's statutory warranty if the owner alters the software on it. In fact back in 2011 and 2016 I used this law to get a Samsung Galaxy mini and an HTC Desire X fixed. In both cases the stores complied with the law and they replaced the devices free of charge.
So, even if they fix the device, they won't tell me how they've done it since I won't interact directly with the service. I've made an inquiry with LG Support and I expect an answer from them. There is a high probability that the service will replace the device entirely...and if they don't LG itself will take action, again in the EU the law puts the customer above anything else and usually the companies comply to avoid facing penalties and fines...
EDIT: I've just seen that you are from Germany so this applies to you as well
MihaiA7X said:
Well, since I'm residing in the European Union, we have a law that the European Council gave back in 1999 that states that any digital device doesn't lose it's statutory warranty if the owner alters the software on it. In fact back in 2011 and 2016 I used this law to get a Samsung Galaxy mini and an HTC Desire X fixed. In both cases the stores complied with the law and they replaced the devices free of charge.
So, even if they fix the device, they won't tell me how they've done it since I won't interact directly with the service. I've made an inquiry with LG Support and I expect an answer from them. There is a high probability that the service will replace the device entirely...and if they don't LG itself will take action, again in the EU the law puts the customer above anything else and usually the companies comply to avoid facing penalties and fines...
EDIT: I've just seen that you are from Germany so this applies to you as well
Click to expand...
Click to collapse
I also made an inquiry to the LG support. Thank you very much stating this European law ?
I really wasn't aware, but this should make discussions easier ?
And even without this law I'm looking forward voting next Sunday for a democratic united Europe ?
MagicOJB said:
I also made an inquiry to the LG support. Thank you very much stating this European law
I really wasn't aware, but this should make discussions easier
And even without this law I'm looking forward voting next Sunday for a democratic united Europe
Click to expand...
Click to collapse
[OFFTOPIC] Yes, I also hope for a democratic United Europe hopefully Sunday will mark the beginning of this.
Response from LG
LG already sent me a response in which they claim I lost warrenty by unlocking the bootloader.
It seems to be standard response, especially because in the salution is the surname of somebody else
In the meantime I found something about the kaw. A interpretation states that a good test if the defect belongs to my actions is flashing back to stock firmware, which I did. If the defect still persists it falls under warrenty.
Today I made an inquiry to the seller, but they don't have a good reputation for service. So let's see what happens here....
MagicOJB said:
LG already sent me a response in which they claim I lost warrenty by unlocking the bootloader.
It seems to be standard response, especially because in the salution is the surname of somebody else
In the meantime I found something about the kaw. A interpretation states that a good test if the defect belongs to my actions is flashing back to stock firmware, which I did. If the defect still persists it falls under warrenty.
Today I made an inquiry to the seller, but they don't have a good reputation for service. So let's see what happens here....
Click to expand...
Click to collapse
I really want them to prove this because right before sending it to service, i flashed 10b from my country code on the box "DEC", then I used LG Bridge, to the software recovery which updated my phone to 10s, and that completed successfully, meaning that my phone was full stock with locked bootloader when i sent it to them
At first i unlocked boot-loader and rooted the device, everything was working fine, later all of sudden touch stopped working
later i did wipe in recovery after that
Im getting no operating system found,
and now im trying to flash the original os via fastboot, but its saying flash permission denied
and in the fastboot mode display in screen, its saying FLASHING_LOCKED
and i tried to unlock the boot-loader again its saying enable in development options / but i cannot load the operating the system
thanks for the help
serialhacker said:
At first i unlocked boot-loader and rooted the device, everything was working fine, later all of sudden touch stopped working
later i did wipe in recovery after that
Im getting no operating system found,
and now im trying to flash the original os via fastboot, but its saying flash permission denied
and in the fastboot mode display in screen, its saying FLASHING_LOCKED
and i tried to unlock the boot-loader again its saying enable in development options / but i cannot load the operating the system
thanks for the help
Click to expand...
Click to collapse
I don't know exactly what causes it, but if the bootloader was unlocked and now says Flashing_locked, usually the only fix is to flash a blankflash.
You will need to find a blankflash for your device, and get it into EDL to flash.
If you have a hanoip (XT2135) this one should work.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to boot into EDL Mode
sd_shadow said:
If you have a hanoip (XT2135) this one should work.
Click to expand...
Click to collapse
its hanoip (xt2135-2) and i think it will work
right?
serialhacker said:
its hanoip (xt2135-2) and i think it will work
right?
Click to expand...
Click to collapse
It should
Same issue here brothers, on my Moto G60
Did the solution work here @serialhacker ?
sd_shadow said:
I don't know exactly what causes it, but if the bootloader was unlocked and now says Flashing_locked, usually the only fix is to flash a blankflash.
You will need to find a blankflash for your device, and get it into EDL to flash.
If you have a hanoip (XT2135) this one should work.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to boot into EDL Mode
Click to expand...
Click to collapse
Hello!
in your link on how to boot in EDL mode, it assumes that the OEM bootloader is unlocked.
How can we boot into EDL with a locked bootloader? I'm stuck here.. Could you please direct us if possible?
Digging into Google, I find no other method but using short-test points method.
[UPDATE]
I could not find any way to enter into EDL mode.
Also, I have asked 2 smartphone technicians and they say there's no way that this brick could be solved at the moment and the hardware is a bit new.
The authorized Motorola center's solution is to replace the whole motherboard!! Dumbest solution...
Anyone here has any ideas please?
KayaNN said:
[UPDATE]
I could not find any way to enter into EDL mode.
Also, I have asked 2 smartphone technicians and they say there's no way that this brick could be solved at the moment and the hardware is a bit new.
The authorized Motorola center's solution is to replace the whole motherboard!! Dumbest solution...
Anyone here has any ideas please?
Click to expand...
Click to collapse
Have you found any solutions yet? Same problem here, can´t flash firmware or blankflash with bootloader locked, also could not, enter into EDL mode.
Unicorn310 said:
Have you found any solutions yet? Same problem here, can´t flash firmware or blankflash with bootloader locked, also could not, enter into EDL mode.
Click to expand...
Click to collapse
[UPDATE, tool name is JTAG Boot tool]
A technician has assured me that a BOOT fix will resolve the issue and for that he needs a tool(JTAG Boot tool) that uses the phone's memory type and loads recovery software into it directly.
Below is MotoG60 memory type from website GSMArena i.e. UFS2.1.
Once I get my phone fixed, I'll definitely write down the solution here in complete detail.
Cheers.
MemoryCard slotmicroSDXC (uses shared SIM slot)Internal128GB 4GB RAM, 128GB 6GB RAMUFS 2.1
One fix a shop suggested is to replace the emmc altogether. Haven't found any other fix yet
KayaNN said:
[UPDATE, tool name is JTAG Boot tool]
A technician has assured me that a BOOT fix will resolve the issue and for that he needs a tool(JTAG Boot tool) that uses the phone's memory type and loads recovery software into it directly.
Below is MotoG60 memory type from website GSMArena i.e. UFS2.1.
Once I get my phone fixed, I'll definitely write down the solution here in complete detail.
Cheers.
MemoryCard slotmicroSDXC (uses shared SIM slot)Internal128GB 4GB RAM, 128GB 6GB RAMUFS 2.1
Click to expand...
Click to collapse
Good afternoon, did you manage to fix the device? same problem here.
KayaNN said:
[UPDATE, tool name is JTAG Boot tool]
A technician has assured me that a BOOT fix will resolve the issue and for that he needs a tool(JTAG Boot tool) that uses the phone's memory type and loads recovery software into it directly.
Below is MotoG60 memory type from website GSMArena i.e. UFS2.1.
Once I get my phone fixed, I'll definitely write down the solution here in complete detail.
Cheers.
MemoryCard slotmicroSDXC (uses shared SIM slot)Internal128GB 4GB RAM, 128GB 6GB RAMUFS 2.1
Click to expand...
Click to collapse
There's no solution to it that you can do in home. I got my device fixed at Next Level Repair in Bangalore. They replaced the UFS chip on my phone. That's the only solution
ankurpandeyvns said:
Não há solução para isso que você possa fazer em casa. Consertei meu dispositivo na Next Level Repair em Bangalore. Eles substituíram o chip UFS no meu telefone. Essa é a única solução
Click to expand...
Click to collapse
Unfortunately I'm from Brazil, I think the only way to solve this would be to really change the motherboard of the device, I've already contacted the motorola aurtorizada and the device is to be posted this Monday, I'll send it anyway and there for next week until at the most in the other I write if it really solved.
Patrick972 said:
Unfortunately I'm from Brazil, I think the only way to solve this would be to really change the motherboard of the device, I've already contacted the motorola aurtorizada and the device is to be posted this Monday, I'll send it anyway and there for next week until at the most in the other I write if it really solved.
Click to expand...
Click to collapse
There might be some repair shops in your locality that may do it.
ankurpandeyvns said:
Pode haver algumas oficinas em sua localidade que podem fazê-lo.
Click to expand...
Click to collapse
So far, the only one that gave me any feedback, tried to pass the jtag directly into memory and it ended up that the device did not start, as they tried to resolder the device's processor, and if that doesn't work they told me to send the device to another assistance to write the system directly to the device's processor.
ankurpandeyvns said:
Pode haver algumas oficinas em sua localidade que podem fazê-lo.
Click to expand...
Click to collapse
Here in Brazil I can't find any place that sells the moto g60 ufs, in addition, a solution I imagined would be to buy a broken one and use the parts for repair, but I can't find any broken only with the plate lol, in which a broken used one has the same price as the repair leaving me with no option of what to do.
I would think that you should be able to get to EDL mode.
If you can disable access to the UFS it has no other choice.
You want to ground some data/clock line to the UFS.
Since you don't know what the accessible test points or resistors are you don't want to short anything directly to ground.
The point might be a power supply or who knows what.
Use a low value resistor (like 100 ohms). Try all the accessible points near the UFS through the 100 ohm to ground.
Long press the power button and wait to hear the connect to USB 05c6/9008
Renate said:
I would think that you should be able to get to EDL mode.
If you can disable access to the UFS it has no other choice.
You want to ground some data/clock line to the UFS.
Since you don't know what the accessible test points or resistors are you don't want to short anything directly to ground.
The point might be a power supply or who knows what.
Use a low value resistor (like 100 ohms). Try all the accessible points near the UFS through the 100 ohm to ground.
Long press the power button and wait to hear the connect to USB 05c6/9008
Click to expand...
Click to collapse
Thank you for sharing such wisdom with us.
I've done that with other things with eMMC where the system was corrupt enough that it didn't work but not so corrupt that the ROM bootloader could recognize it as being a total failure.
That's where you get stuck. Halfway failure is bad. Total failure gets recognized as such and goes to ROM bootloader.
Any idea what causes this and how can someone avoid all of this to begin with?
I guess the safest way would be not to unlock your bootlaoder. ) But if you did, and now you want to lock it back, what would be the safest way to do that, so you can avoid bricking your phone?
Right now, for example, my phone is back to stock ROM, but with an unlocked bootloader, and OEM Unlocking option greyed out and OFF (meaning bootloader is not unlockable anymore). Also, it says "bootloader is already unlocked". Which it is. But also, that's not the point. Ideally (and, for as far as I could see, that IS what happens on other phones, including other Motorola phones), is for that option to be ON, even if it's greyed out (inactive).
Because, in case you lock the bootloader, and something goes south, you can still unlock the bootloader again. But if that option is OFF (meaning get_unlock_ability=0), you can't unlock the bootloader anymore. And if you can't boot, you also can't go into developer options to activate it (assuming it wouldn't be greyed out and inactive anyway).
But I'm more interested to know why does this happen to begin with.
Why is that option greyed out and turned OFF, instead of being ON? And why do people get into this unbootable state, even with previously working stock ROMs?
Does anyone know?