How can I recover the phone from this? (RED WARNING - NO BOOT) - LG G7 ThinQ Questions & Answers

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

Related

stuck at bootloader state : bootloader unlocked !

my lg g4 h815 is stuck on this msg at the boot screen :
stuck at bootloader state : bootloader unlocked !
i tried flashing it to many versions ; always end up and when i try to turn in it on i see nothing but this
delete the spaces plz
imagizer.imageshack. us/v2/1024x768q90/923/LKepyr. jpg
the only mode that i can access to is emergency mode
Are you definitely flashing the correct firmware? No Nandroid? Would LGUP possibly fix?
SavageRobot said:
Are you definitely flashing the correct firmware? No Nandroid? Would LGUP possibly fix?
Click to expand...
Click to collapse
yeah of course the correct firmware , many in tot and kdz format , using original flasher and boxes softwares .
i already said that i can only access to emergency mode , no custom recovery on my device
If your LED doesn't blink it means u just got a 'bootloop issue'. LG said its 'loose connection between the components', so high five cuz my G4 died as well, I mailed LG if I can get replacement. Since they replaced people's G4 after the warranty period they should replace it even if the bootloader is unlocked, when they reply I'll tell you whether you can get replacement or throw it away. (Theres no fix for it)
Adam Myczkowski said:
If your LED doesn't blink it means u just got a 'bootloop issue'. LG said its 'loose connection between the components', so high five cuz my G4 died as well, I mailed LG if I can get replacement. Since they replaced people's G4 after the warranty period they should replace it even if the bootloader is unlocked, when they reply I'll tell you whether you can get replacement or throw it away. (Theres no fix for it)
Click to expand...
Click to collapse
I am having this issue now as well. Please let me know what LG said to you in there reply back to you.
Thanks
dmxcrb said:
I am having this issue now as well. Please let me know what LG said to you in there reply back to you.
Thanks
Click to expand...
Click to collapse
LG simply sai that they will not repair it and they gave me the phone number to their 3rd party service that REFUSED to repair my phone, I'm done.

About all versions of LG G7 unlock the bootloader and ROOT discussion

I am from China, I don't know English, this article is translated by Google, but I hope you can read it.
In our place, there are technologies for all models of G7 to unlock bootloader and ROOT (T-MOBILE version of the phone needs to be replaced with a cup to become a general version to unlock the bootloader, because this version of the phone cpu is encrypted), but, frustrating Yes, this technology is only in the hands of a few people, they do not intend to share, and they use this technology to gain benefits.
They provide remote unlocking of the bootloader and ROOT services, but need to pay 150 yuan, which is expensive for me and is meaningless.
I bought a G7 from a second-hand merchant who replaced the RAM with 4G and changed it to 6G. He said that the machine replaced the T-MOBILE version of the CPU, but the IMEI code displayed on the machine is the Korean blue version, and my G7 is Red, I don't know if G7 has changed the IMEI code. If so, please let me know, thank you
My mobile phone, the merchant has helped me unlock the bootloader and ROOT. And, since someone on XDA has shared the cracked version of LGUP, I can use it to brush in any version of my G7. I brushed Korea, T-MOBILE, and KDZ in Europe, and in Europe and Korea. The version of the system ROOT, because now only the European version and the Korean version of ROOT BOOT, I brushed into the boot through FASTBOOT, but, very strangely, I brushed the three versions of KDZ, only T-MOBILE version KDZ can enter FASTBOOT via ADB commands or keystrokes (maybe this phone is T-MOBILE version), other versions will only restart. Therefore, I have to first brush into the T-MOBILE version of KDZ into FASTBOOT to brush into the version of ROOT BOOT I want, then brush into the corresponding version of KDZ, and then install magisk, you get ROOT. However, I am not satisfied with the current system version, I want a newer version, and make it ROOT BOOT, I brushed KDZ many times, when I entered FASTBOOT again into BOOT, I found that I can't brush BOOT again. And FASTBOOT prompts to open the OEM to unlock
So, I entered the system, clicked on the developer option, found that the OEM unlock option has become gray, and can not be opened, so my phone can not be brushed into BOOT, I am looking for ways online, unfortunately, I have not I found a way to succeed. Later, I saw the latest V30 unlocking Bootloader post. It seems that after unlocking the bootloader, the OEM unlock will turn gray. It will take a few days to open again. However, I didn’t see it. Before the V30 post, I have already entered my G7 into FASTBOOT and re-locked the bootloader via the adb command.
Now I can open the OEM to unlock it, but it is useless. Because the bootloader is locked, I still can't brush it into the BOOT through FASTBOOT. Because the bootloader has been locked back by me, I did this, I thought my G7. Is the T-MOBILE version of the replacement CPU machine, in our case, it is said that after the T-MOVILE version of the machine to replace the CPU, T-MOBILE G7 can unlock the bootloader, and will not lock
Now, I am trying to find a way to unlock the bootloader, but no, yes, no, I hope to get some clues to unlock the bootloader by contacting those who have remotely unlocked the bootloader and ROOT by paying. However, no one wants to do this, they I even told me to go away, maybe because they have already paid to unlock it, and telling me will damage their interests. Finally, I learned about the process of remotely unlocking the bootloader by one person. Those who master the technology to unlock the bootloader do not want to expose it. They help the remote unlocking of the bootloader and block the operation process, just through the chat software. Release the command to let you connect to the computer or switch the phone into LG's brush mode, etc. I want to get some information through the screen of the phone. Unfortunately, that person doesn't remember, I only asked some strange news, that person's The mobile phone is a Korean mobile phone that does not unlock the bootloader. The mobile phone version is Android 9.0 South Korea's 20c. The remote flashing machine does not know how to enter the Korean version of FASTBOOT on this mobile phone that does not unlock the bootloader and ROOT. As far as I know, the Korean version The FASTBOOT of the mobile phone is hidden and cannot be opened by the command. This thing has been said on XDA... This thing makes me wonder, I thought they used the tool to brush into the European version of the system and then enter FASTBOOT to unlock. (Unfortunately, my G7 can only enter fastboot by brushing into the T-MOBILE version, the European version cannot pass the adb Or in the form of platinum enter). Some time ago, someone discussed on xda how to unlock the bootloader by brushing into the European version of the system. Since the cracking tool did not come out at the time, they hoped to use the octopus box to brush into the European version of the system and then unlock it (how to unlock without explanation), now crack The tool came out, it can make our G7 brush into any version of the system, but the discussion is gone...
If you have any ideas, please let me know and send it to this mailbox at [email protected]. I am not very good at using xda, and I need vpn on xda. I also need to pay for using VPN. I am poor, this is for me. It’s too much trouble...
*I have a few questions that need your help, 1 how to change the IMEI of G7, I want to try to get a network upgrade by changing imei to the corresponding system version.
2 How to unlock KDZ of G7, I need to unlock KDZ of G7 to extract BOOT.IMG into ROOT BOOT, I tried new methods and some old methods that I can find in my country to unlock KDZ of G7. failed
If you have a method, please let me know (hopefully have a tutorial), I hope to get your reply, thank you...
thanks for your sharing。
Intresting things they do in China. This is why I never trust buying a chinese brand. I bought in 2015 3 xiaomi mi3 mediatek clones from official shenzhen mi store. Never trust chinese brands again. That applyes for software also.
What version of kdz do you want? I have most versions from European model and 2 versions form Korean pie.
Update instructions, I used my friend's Korean version G7 to brush into T-MOBILE version KDZ tiles, can not boot, now only into 9008 mode, now confirmed that the replacement of CPU G7 seems to have become a strange machine, it seems that it can be cracked version of LGUP into any version of KDZ will not tiles, but other machines can not, such as my friend's Korean version machine brush into T-MOBILE machine. It will change into bricks, but one thing is certain that KDZ of Korean and European machines can be brushed into each other, because the publisher of LGUP cracked version is using this tool to make European G7 brush into Korean G7 9.0 system, but it is possible to brush KDZ randomly into Korean G7 system. I do not recommend that you do so. I do not think you have the hope that your machine will become a brick. If it has happened, I'm sorry, I can only say that, but I hope you can share it and let those who have not happened avoid it. I need more communication and look forward to your reply.
It has entered 9008 mode. Can I change it to European IMEI and ID, then get the unlock file, brush it into European system, and turn it into a European machine, then unlock BL. In theory, the hardware of G7 is the same... I hope someone can share the IMEI and device ID of the European version G7 to me. It's better to have unlock.bin file. I want to test it. My mailbox is [email protected].
x593095611 said:
It has entered 9008 mode. Can I change it to European IMEI and ID, then get the unlock file, brush it into European system, and turn it into a European machine, then unlock BL. In theory, the hardware of G7 is the same... I hope someone can share the IMEI and device ID of the European version G7 to me. It's better to have unlock.bin file. I want to test it. My mailbox is [email protected].
Click to expand...
Click to collapse
That will be verry nice. Is it ok if I give you one from one g7em un retail mode but that has sim enabled?
Any update on this? Would be an interesting method, i would absolutely do this if it works
x593095611 said:
It has entered 9008 mode. Can I change it to European IMEI and ID
Click to expand...
Click to collapse
No you can't. Starting with SD845 - IMEI and ID stays in CHIP and regenerates on every boot.
So, the only way to achieve it is to contact this taobao seller and he will resolder EU chip, flash EM firmware and unlock it and then re-solder back your chip and you will have EM firmware but IMEI and SN will be 0.
N.B.:Regarding G7 it is build in 3 factories and has 4 different Hardware revisions so stop thinking HW is identical and simply cross-flashing will do the trick
So no way to sim unlock the lg g7 tmobile?
lmg710em unsupported country
Greetings everyone;
Since my lmg710em is registered in an "unsupported country"; I cannot unlock my bootloader with official way. I've looked for hours to find an unofficial way but there is nothing... I have tried to flash France's kdz, but nothing changes. Does someone have the european version's unlock.bin file? This is my only hope for now.
It's really bad to be forbidden to use the device, which you paid for, as you like.
I really need help guys,
thank you all,
cheers...
can unlock unofficial by flash abl LG V35
hsrose11 said:
can unlock unofficial by flash abl LG V35
Click to expand...
Click to collapse
Wow have ever you tried it? B'cause I really dont want to brick my phone :/
"Fastboot oem unlock" does not works :/ I have already tried it. The output was "unknown command" or sth like that as I remember. Was there any other step before cmd prompt section?
yes, flash bootloader LG V35
hsrose11 said:
yes, flash bootloader LG V35
Click to expand...
Click to collapse
Wow, makes sense man, thanks! But there is only one problem... I dont know how to do it

Root/Bootloader unlock

Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk
2390 said:
Hey guys, I'm super excited to get my new LG G8 tonight, with all of the incentives Sprint is offering me it'll cost just over $300!
However, the previous LG phones that I've had (G4 and G5) were absolute trainwrecks when it came to software, and the G8 doesn't seem to be too different. I'm hoping that eventually we will be able to root it, if not install a Project Treble AOSP build.
How likely is this? Can we get a bootloader bounty going? Heck, I'd be happy with just root and Magisk
Click to expand...
Click to collapse
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.
mr3p said:
Unless something like this will work on G8, there is no reason to believe your G8 will be able to be rooted anytime soon.
Click to expand...
Click to collapse
let me know when u can unlock bootloaders , happy to help out with twrp or so
Cheers
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Dumb question but did you try the adb reboot bootloader command?
BoredKender said:
Dumb question but did you try the adb reboot bootloader command?
Click to expand...
Click to collapse
Yes and it simply reboots the phone. Does not go to the bootloader at all. Not a dumb question by the way. Pretty good to ask.
AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
some variants doesnt have fastboot if im not wrong
J0SH1X said:
some variants doesnt have fastboot if im not wrong
Click to expand...
Click to collapse
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.
AngryManMLS said:
I suspect that's the case with the T-Mobile variant. I wouldn't be shocked if there's a backdoor method found to getting fastboot to work on such variants as I can still get into download mode easily along with recovery. So I'm sure there's a way to use either one of these to getting fastboot to work.
Click to expand...
Click to collapse
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp
J0SH1X said:
the problem is i think ur phones abl partition doesnt contain fastbootd , and since T-Mobile variant has different RSA keys then other variants you cant crossflash it with some variant that includes twrp
Click to expand...
Click to collapse
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.
AngryManMLS said:
Fudge... I figured that someone who knows way more than I do would prove my idea would not work.
No method to add fastboot to the abl partition I'm assuming? Just throwing ideas out there.
Click to expand...
Click to collapse
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys
J0SH1X said:
i have no idea just sharing what ive learnt from my g6 and g7, as on g7 the TMO is the only one not unlockable , bcs of its rsa keys
Click to expand...
Click to collapse
A shame really. :crying:
AngryManMLS said:
A shame really. :crying:
Click to expand...
Click to collapse
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom
J0SH1X said:
yeah if u buy lg always watch out , i always wait till i buy a new phone to see if it can be unlocked i probably buy g8 at some time and i need unlock bl i cant stand the lg rom
Click to expand...
Click to collapse
Someone has a engineering bootloader that allows you to unlock bootloader working on the g7 andv40 and v35 mabye works on g8 you need to use jtag from octoplus though.
Any other info yet?
Verizon
LM-G820UM
I'm pretty sure they'll update their Bootloader Unlock Key page in the next few weeks and add the G8(S) to the list of supported devices.
The unlocked G8S at least boots into Fastboot and also explicitly describes and explains how to unlock the bootloader. So there's that.
AngryManMLS said:
The good news on the T-Mobile variant is the "Enable OEM Unlock" is present and not greyed out. The bad news is I am unable to get into the bootloader either through command or even with the volume up+power while turning the phone on. It looks like the T-Mobile variant has the bootloader locked out unless if I'm missing something here.
Edit: Even holding down then plugging in my USB-C cable doesn't get the bootloader to kick in. Up then plugging in however does get me to download mode. I can get into recovery but can't get the dang thing to do anything other than display the broken Android logo and can't even get the typical recovery stuff to pop up. Says "no command" below the broke Android logo.
Click to expand...
Click to collapse
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8
Robin M said:
AngryMan, I have an unlocked G8 that I got from Amazon. I tried your "Up then plugging in" method and got to the download mode and a screen that said "Firmware Update" But from there, I couldn't get into anywhere else - no Recovery, and no broken Android logo. How did you get into the recovery mode. I would like to try that on my unlocked version of the G8
Click to expand...
Click to collapse
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
{
"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"
}
Frau Son said:
It's volume down and plugging in the cable. What @AngryManMLS edited in as well.
If your device is unlockable it should lead you to fastboot mode with (more or less) detailed instructions on how to unlock the bootloader.
I "only" own a G8s but it should be the same for the other variants.
Click to expand...
Click to collapse
Thanks. It didn't work on mine. I have a carrier unlocked version that I got from Amazon - $350 discount on Prime Day. (It's an LM-G820QM model with no digital assistant key and the Alexa apps added.) All I get when when using the volume down key (even with plugging in the cable afterwards) is the attached Factory Reset screen... I cannot get to the screens AngryMan saw.
I have an LM-G820QM unlocked I got from a bestbuy a couple weeks after launch. I can use adb reboot bootloader to get into fastboot. I followed the instructions on the LG bootloader unlock page. I got the device ID and IMEI put in and it told me my device doesn't support bootloader unlocking or some nonsense. I was pretty disappointed because I thought buying the unlocked variant it would be unlockable by LG. I seem to be the only person with this vairant here so if I can help the effort in any way, please let me know.

Question Error "No valid operating system could be found. The device will not boot."

Hello colleagues, I would like you to help me please, I recently unlocked my device's bootloader and in an attempt to lock it again to remove the bootloader locked message, I got the following error: "No valid operating system could be found. The device will not boot." when flashing the rom to the device again it refuses, stating that the bootloader is locked, and when I ask to unlock it returns me to go to the settings, in the developer options section and from there activate the oem unlock, but it is not possible because the device it doesn't turn on, it's just from the error screen to the cell phone off, or from the cell phone off to the bootloader.
I'm desperate because the device is for my own use and I need to fix it urgently.
I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside
ankurpandeyvns said:
I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside
Click to expand...
Click to collapse
Got it, it's not under warranty because I unlocked the bootloader, so the only way is to replace a motherboard?
If so where can I get support? Can it be at any technical assistance in the city or does it have to be an authorized motorola company?
Check in your area if someone can do it. Else getting a new motherboard is going to be very expensive
ankurpandeyvns said:
Check in your area if someone can do it. Else getting a new motherboard is going to be very expensive
Click to expand...
Click to collapse
If so, is there any other way without having to replace the motherboard?
Hy patrick......can your phone gets in fastboot mode
You made a cardinal mistake - NEVER lock the bootloader on custom software.
The error message means that the firmware you installed is not signed or cannot be verified by the bootloader.
It looks like Motorola has a rescue tool here that may help. Otherwise, you might try sideloading an OTA package (if available); there is a tool here that may be helpful.
If not, you're SOL.
Yes you can repair it by flashing the stock rom through platform tools by fastboot method but firstly install adb drivers and usb drivers for your phone on pc check whether your phone is detected by pc in fastboot mode or not connect your phone to pc through usb cable and put your phone in fastboot mode and type fastboot devices on Command prompt if it detect your device then you are good to go .....and it doesn't require a unlocked bootloader this can help you......
Devilme said:
Hy patrick......can your phone gets in fastboot mode
Click to expand...
Click to collapse
Hello, he is company on fastboot normally
V0latyle said:
You made a cardinal mistake - NEVER lock the bootloader on custom software.
The error message means that the firmware you installed is not signed or cannot be verified by the bootloader.
It looks like Motorola has a rescue tool here that may help. Otherwise, you might try sideloading an OTA package (if available); there is a tool here that may be helpful.
If not, you're SOL.
Click to expand...
Click to collapse
Thanks, I will try, but the software was not customized but the official one in case I was trying to downgrade from android 12 to 11 because I didn't like 12
Devilme said:
Yes you can repair it by flashing the stock rom through platform tools by fastboot method but firstly install adb drivers and usb drivers for your phone on pc check whether your phone is detected by pc in fastboot mode or not connect your phone to pc through usb cable and put your phone in fastboot mode and type fastboot devices on Command prompt if it detect your device then you are good to go .....and it doesn't require a unlocked bootloader this can help you......
Click to expand...
Click to collapse
I tried this method but it returned saying that the "bootloader flash permission denied" even with the device rom provided by motorola
ankurpandeyvns said:
I faced the same issue. You cannot do anything about it. If you're under warranty, get the motherboard replaced in service center. Or you'll have to get your emmc replaced outside
Click to expand...
Click to collapse
Was it under warranty in your case? if not how much on average was the repair?
Patrick972 said:
Thanks, I will try, but the software was not customized but the official one in case I was trying to downgrade from android 12 to 11 because I didn't like 12
Click to expand...
Click to collapse
Ah, I misunderstood.
Patrick972 said:
I tried this method but it returned saying that the "bootloader flash permission denied" even with the device rom provided by motorola
Click to expand...
Click to collapse
A locked bootloader will always refuse flash commands.
Patrick972 said:
Was it under warranty in your case? if not how much on average was the repair?
Click to expand...
Click to collapse
I was not under warranty and no one is able to fix yet with any tool.
A guy here in Bangalore had a tool named Easy JTAG, he was trying to write to the UFS but it's failing there too. Idk what motorola wants lol
ankurpandeyvns said:
I was not under warranty and no one is able to fix yet with any tool.
A guy here in Bangalore had a tool named Easy JTAG, he was trying to write to the UFS but it's failing there too. Idk what motorola wants lol
Click to expand...
Click to collapse
The issue is that it is so illogical that it seems that this error was made specifically to stop us developers and make us go to an authorized one to fix it, it makes no sense to re-lock the bootloader to return a bizarre error like this, and motorola doesn't to comment on this, I took it to an authorized one and they gave me the budget of 920 R$, about 181.23 Dollars, they said that to solve the problem, the device's motherboard should be replaced and the worst thing is that for being a recent device, I can't find the motherboard anywhere so I can change it myself and pay less.
Patrick972 said:
The issue is that it is so illogical that it seems that this error was made specifically to stop us developers and make us go to an authorized one to fix it, it makes no sense to re-lock the bootloader to return a bizarre error like this, and motorola doesn't to comment on this, I took it to an authorized one and they gave me the budget of 920 R$, about 181.23 Dollars, they said that to solve the problem, the device's motherboard should be replaced and the worst thing is that for being a recent device, I can't find the motherboard anywhere so I can change it myself and pay less.
Click to expand...
Click to collapse
Did you manage to fix it?
The error occurs due to locking the bootloader when phone is running on a custom boot image/ROM/rooted with magisk. It is really simple to fix, just boot your phone into fastboot mode and flash factory image/stock firmware.
The right way to lock the bootloader is to first factory reset the phone or install a stock firmware /factory image and you'll never experience this error again.
I recently fixed this error on a Google Pixel 7. You can watch the step-by-step tutorial here.
wrkadung said:
The error occurs due to locking the bootloader when phone is running on a custom boot image/ROM/rooted with magisk. It is really simple to fix, just boot your phone into fastboot mode and flash factory image/stock firmware.
The right way to lock the bootloader is to first factory reset the phone or install a stock firmware /factory image and you'll never experience this error again.
I recently fixed this error on a Google Pixel 7. You can watch the step-by-step tutorial here.
Click to expand...
Click to collapse
It is that simple on a Pixel. On Moto devices, LMSA won't flash with a locked bootloader, when the device is in this specific state. You can see the error below.
{
"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"
}
Also, it will not let you unlock the bootloader again, since the "OEM Unlocking" option is not checked anymore. And, obviously, you can't check it, since you can't boot.
So yes, the solution is to flash stock ROM. The problem is...you can't flash from fastboot (bootloader won't accept flash commands), and you can't use LMSA to flash either. So...you need to make sure everything is clean BEFORE attempting to lock the bootloader. In other words, do the cleanup with an unlocked bootloader, and make sure everything is back to stock before locking back the bootloader.
Patrick972 said:
Hello colleagues, I would like you to help me please, I recently unlocked my device's bootloader and in an attempt to lock it again to remove the bootloader locked message, I got the following error: "No valid operating system could be found. The device will not boot." when flashing the rom to the device again it refuses, stating that the bootloader is locked, and when I ask to unlock it returns me to go to the settings, in the developer options section and from there activate the oem unlock, but it is not possible because the device it doesn't turn on, it's just from the error screen to the cell phone off, or from the cell phone off to the bootloader.
I'm desperate because the device is for my own use and I need to fix it urgently.
Click to expand...
Click to collapse
Hello
I'm having the exact same issue, and yesterday I bumped across this:
now, this person has solved his cellphone problem over in his video, in my case - i am facing a connection issue in the usb redirector client/customer module tool
bengu_chengu said:
Hello
I'm having the exact same issue, and yesterday I bumped across this:
now, this person has solved his cellphone problem over in his video, in my case - i am facing a connection issue in the usb redirector client/customer module tool
View attachment 5832385
Click to expand...
Click to collapse
You all fixed now? I had same problem found a guy on telegram who fixed for a small fee, best money I ever spent

Question Convert LE2127 to Global LE2125

Hello,
There are currently cheap 9 Pros on Aliexpress, but they are Global versions LE2127.
I've searched the forum and found a thread to convert a LE2127 to LE2125 EU. Is there such a guide for converting to Global instead?
I intend to stay on Android 11 using the Jaguar rom.
Thanks
Phillis said:
Hello,
There are currently cheap 9 Pros on Aliexpress, but they are Global versions LE2127.
I've searched the forum and found a thread to convert a LE2127 to LE2125 EU. Is there such a guide for converting to Global instead?
I intend to stay on Android 11 using the Jaguar rom.
Thanks
Click to expand...
Click to collapse
Le2127 is not global this the t-mobil devices
Le2125 is usa
And le2123 is eu
Le2121 is india
And you can flash what ever you will
India build, global build eu build or us build
You can flash Other build over fastbootd
I think I found the solution after some digging:
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
If anyone can confirm, that would be great! Thanks!
ChrisFeiveel84 said:
Le2127 is not global this the t-mobil devices
Le2125 is usa
And le2123 is eu
Le2121 is india
And you can flash what ever you will
India build, global build eu build or us build
You can flash Other build over fastbootd
Click to expand...
Click to collapse
{
"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"
}
This is why I was asking. Just read some horror stories about flashing and somehow losing connectivity because of the modem.
Phillis said:
View attachment 5885177
View attachment 5885179
This is why I was asking. Just read some horror stories about flashing and somehow losing connectivity because of the modem.
Click to expand...
Click to collapse
You can use the conversion tool to go to Eu and flash the modem back in and stay connected fine. Or you can flash global.
They're not real horror stories because we have msm tool available and can (almost) always get back to working devices with that. I stay on oos11 EU and flashed the modem back in, everything works. I do have a modem crash issue when I get download speeds over 500mbps on 5G but I rarely use 5G anyway.
Since you're going custom rom, it may depend on what it was built on, whether or not you would need to flash modem back in. Regardless of that possibility, it is fixable and do-over-able
Appreciative said:
You can use the conversion tool to go to Eu and flash the modem back in and stay connected fine. Or you can flash global.
They're not real horror stories because we have msm tool available and can (almost) always get back to working devices with that. I stay on oos11 EU and flashed the modem back in, everything works. I do have a modem crash issue when I get download speeds over 500mbps on 5G but I rarely use 5G anyway.
Since you're going custom rom, it may depend on what it was built on, whether or not you would need to flash modem back in. Regardless of that possibility, it is fixable and do-over-able
Click to expand...
Click to collapse
Thanks for the reply!
Didn't the modem have unique information that if overwritten would render it useless?
From what I've read, I'll need to contact OnePlus to unlock the bootloader of that phone, even though it's coming direct from China with a Global (non TMO) rom.
Once I get clarification on that I shall jump ship and order it!
Reply from seller:
Thanks for your message. It is LE2127,hope you could understand. If there is any other question , feel free to contact us. Wish you have a sweet day. Best wishes, Inma
Dear customer, Thanks for your message. the phone comes with OxygenOS based on Android 11. and no need to contact oneplus to unlock bootloader any other question, feel free to contact us.
Is it possible an LE2127 not require contacting OnePlus for unlocking the bootloader?
Phillis said:
Thanks for the reply!
Didn't the modem have unique information that if overwritten would render it useless?
From what I've read, I'll need to contact OnePlus to unlock the bootloader of that phone, even though it's coming direct from China with a Global (non TMO) rom.
Once I get clarification on that I shall jump ship and order it!
Click to expand...
Click to collapse
Modemst1/2 do have unique information. Modem_a can be shared. Modem_a/b is different from modemst1/2 and modem_a/b is the one in question for this device.
However, you should back up modemst1/2 and efs/persist anyway because then you really have nothing to fear if something goes wrong.
As of right now, while in oos11, it's already possible to unlock the bootloader of the le2127 without contacting OnePlus or t-mobile. By converting to EU, while on oos11, you can bypass the OnePlus+Tmobile bootloader token requirement and unlock the bootloader.
It sounds like they are already on global anyway.
What I did may give you peace of mind also:
Rebooted my device into edl mode with msm tool open and took backups of partitions I wanted (modemst1/2 efs/persist and boot)
Used One+TooL to make OEM Unlock toggle available in developer settings. (This was needed because I was not sim unlocked at the time. The tool or adb can be used to bypass that and make the toggle visible)
Got my bootloader token in fastboot and submitted it to OnePlus website. I know it takes a week (I've since heard it is faster using support chat or email and the automatic tool is providing wrong unlock bins).
Knowing I will be waiting a week, I did the Tmo->EU conversion, unlocked my bootloader, rooted using the boot.img I made a backup of, flashed my modem_a (not modemst1/2) back in and set everything up. Staying on oos11, this is no problem. Updating to oos12/13 after the conversion, you will need the unlock token again. As I understand it, the unlock token bypass is only present in oos11 so it's advised to do it then.
This is the furthest you'd need to go most likely, you can go from Eu to global. The connectivity issues I've read, seem to come for those who upgrade Eu to the latest versions of oos13. They solve it by going to Global instead.
(A week later I received my unlock.bin from OnePlus. I used the regular Tmo msm tool to go back to stock Tmo. Verified my bootloader unlock token worked in stock form and it did. I unlocked it, rooted again, and set up https monitoring to see the exchange happening during sim unlock. Then I requested my sim unlock and eventually found someone not dumb to help me out. I logged the request I was interested in and went back to Eu again, rooted/unlocked bootloader again, flashed my modem_a again and have been here ever since)
I can't speak for custom roms or oos13 but I can say for sure that on OOS11, it is possible to bypass the sim unlock requirement for bootloader, possible to unlock the bootloader without the token, it is possible to have unlocked bootloader, root/magisk and retain L1 DRM for netflix/disney+, google pay works, android auto works and I'm showing up as device certified in play store. So long as you install the appropriate magisk modules of course.
The LE2127 is a lil bit different than the others but it's definitely not a nightmare or very risky if you take precautions. Take backups of your partitions, keep the msm tools handy and you'll be just fine. Every one of us who have done any flashing on xda, have had to redo or start over at some point on some device. Luckily, there are a lot of us in this section that have the le2127 to help ease your mind and assure you that it's gonna be ok. We have been blessed by a few guys who did the hard work before us and figured out the bypasses and fixes to various issues.
Since this phone is currently the last OnePlus device to have real MSM tool and custom rom development, it's looking real good to be a 9P owner. This phone has a lot of good hardware, specs, options and support. I think you've done good to research beforehand. I think you'll be happy with the device when you get it set up how you want it also.
For taking backups in the msm tool, you put your phone into edl mode and connect it with msm tool open, press F8. That will bring up a list of partitions you can backup. Select the ones you want (especially modemst1 and persist), type the password "oneplus" and press readback. It will save the partitions to C:\. I suggest making a backup of the backups but I'm extra cautious. Don't sweat it tho, you'll be fine with le2127
Appreciative said:
Modemst1/2 do have unique information. Modem_a can be shared. Modem_a/b is different from modemst1/2 and modem_a/b is the one in question for this device.
However, you should back up modemst1/2 and efs/persist anyway because then you really have nothing to fear if something goes wrong.
As of right now, while in oos11, it's already possible to unlock the bootloader of the le2127 without contacting OnePlus or t-mobile. By converting to EU, while on oos11, you can bypass the OnePlus+Tmobile bootloader token requirement and unlock the bootloader.
It sounds like they are already on global anyway.
What I did may give you peace of mind also:
Rebooted my device into edl mode with msm tool open and took backups of partitions I wanted (modemst1/2 efs/persist and boot)
Used One+TooL to make OEM Unlock toggle available in developer settings. (This was needed because I was not sim unlocked at the time. The tool or adb can be used to bypass that and make the toggle visible)
Got my bootloader token in fastboot and submitted it to OnePlus website. I know it takes a week (I've since heard it is faster using support chat or email and the automatic tool is providing wrong unlock bins).
Knowing I will be waiting a week, I did the Tmo->EU conversion, unlocked my bootloader, rooted using the boot.img I made a backup of, flashed my modem_a (not modemst1/2) back in and set everything up. Staying on oos11, this is no problem. Updating to oos12/13 after the conversion, you will need the unlock token again. As I understand it, the unlock token bypass is only present in oos11 so it's advised to do it then.
This is the furthest you'd need to go most likely, you can go from Eu to global. The connectivity issues I've read, seem to come for those who upgrade Eu to the latest versions of oos13. They solve it by going to Global instead.
(A week later I received my unlock.bin from OnePlus. I used the regular Tmo msm tool to go back to stock Tmo. Verified my bootloader unlock token worked in stock form and it did. I unlocked it, rooted again, and set up https monitoring to see the exchange happening during sim unlock. Then I requested my sim unlock and eventually found someone not dumb to help me out. I logged the request I was interested in and went back to Eu again, rooted/unlocked bootloader again, flashed my modem_a again and have been here ever since)
I can't speak for custom roms or oos13 but I can say for sure that on OOS11, it is possible to bypass the sim unlock requirement for bootloader, possible to unlock the bootloader without the token, it is possible to have unlocked bootloader, root/magisk and retain L1 DRM for netflix/disney+, google pay works, android auto works and I'm showing up as device certified in play store. So long as you install the appropriate magisk modules of course.
The LE2127 is a lil bit different than the others but it's definitely not a nightmare or very risky if you take precautions. Take backups of your partitions, keep the msm tools handy and you'll be just fine. Every one of us who have done any flashing on xda, have had to redo or start over at some point on some device. Luckily, there are a lot of us in this section that have the le2127 to help ease your mind and assure you that it's gonna be ok. We have been blessed by a few guys who did the hard work before us and figured out the bypasses and fixes to various issues.
Since this phone is currently the last OnePlus device to have real MSM tool and custom rom development, it's looking real good to be a 9P owner. This phone has a lot of good hardware, specs, options and support. I think you've done good to research beforehand. I think you'll be happy with the device when you get it set up how you want it also.
For taking backups in the msm tool, you put your phone into edl mode and connect it with msm tool open, press F8. That will bring up a list of partitions you can backup. Select the ones you want (especially modemst1 and persist), type the password "oneplus" and press readback. It will save the partitions to C:\. I suggest making a backup of the backups but I'm extra cautious. Don't sweat it tho, you'll be fine with le2127
Click to expand...
Click to collapse
Wow..thank you for the detailed response!
You are correct that they are already on Global!
I found a deal too good to be true yesterday on Ebay: 9 Pro brand new Global version US Version for 175$USD. I pulled the trigger without thinking. That one might be a LE2127. Seller has decent feedback so who knows:
OnePlus 9 Pro 5G Global Version Smartphone 12GB RAM 256GB ROM NFC Mobile Phone | eBay
Find many great new & used options and get the best deals for OnePlus 9 Pro 5G Global Version Smartphone 12GB RAM 256GB ROM NFC Mobile Phone at the best online prices at eBay! Free shipping for many products!
www.ebay.com
Before that happened, I also contacted the 3 sellers on Aliexpress that are selling some 9 Pros.: OPPO store, OnePlusStore and HWMall. The first 2 said they only have LE2127, which is why I had asked here.
The third one replied yesterday evening and confirmed he has LE2125s. Pulled the trigger on that one too (in case ebay is a scam).
Let's see what ends up in my hands!
Thanks again, I am now less worried about getting a LE2127 if that ends up being the case
Phillis said:
Hello,
There are currently cheap 9 Pros on Aliexpress, but they are Global versions LE2127.
I've searched the forum and found a thread to convert a LE2127 to LE2125 EU. Is there such a guide for converting to Global instead?
I intend to stay on Android 11 using the Jaguar rom.
Thanks
Click to expand...
Click to collapse
Keep searching it is there for the global.
As i know, you can convert LE2127 to Global Version (LE2123). You need to take your phone EDL mode and flash the image from this link using MSM Tool. After successfully flashed, connect to internet your device and update until see LE2123 model in the settings.
utilizedwill said:
As i know, you can convert LE2127 to Global Version (LE2123). You need to take your phone EDL mode and flash the image from this link using MSM Tool. After successfully flashed, connect to internet your device and update until see LE2123 model in the settings.
Click to expand...
Click to collapse
Global is LE2125 for pro model, LE2123 is EU model

Categories

Resources