Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
only the EU bootloader has been unlocked, something to do with TMO releasing some keys or something for the secuity, I believe. I know on HTCs I used to have TMO had certain encryption on wifi calling and a few signatures that were broken by touching the security partition needed to gain root and install custom OSs. Once LG updates their bootloader unlock page to include TMO version G7 (I have one, too) then we'll see a KDZ thread and then root
cohan1219 said:
Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
Click to expand...
Click to collapse
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Joe199799 said:
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Click to expand...
Click to collapse
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
sharpknight said:
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
Click to expand...
Click to collapse
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
that one guy is checking the bootloader again and trying to help us ive been taking to him hope he's right about them locking it the same way give it a little time he thought bootloader was unlocked he doesn't have the device there's others we can't give up man adb root is possible prob hacking laf maybe possible and there's a way someone will get it anyone trying to I'll also help to
Joe199799 said:
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
Click to expand...
Click to collapse
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Honestly I just want it for viper4android literally that's it and maybe greenify and adaway other than that I'm good.
Honestly I probably won't switch over I'll just deal with it
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Greenify was the biggie to me particularly with the Xposed module. Titanium Backup. Disabling system apps that the UI wouldn't let me disable. (Maybe that can be done via adb w/o root. I should try.) BootManager. MinMinGuard. Worthwhile system-wide font replacement w/o bloat. (No apps, no junk, no "apps that don't support <thing> or <favorite font>", just replacing files in /system/fonts.)
Lots of other little things that -- added together -- made my phone just that much nicer to me.
I'm really happy with my G7 all around (except for the WiFi stability, that still sucks). I just wish I had all those little tweaks back.
I made a post about a week ago but never got any replies. Has anyone else ran the "fastboot flash unlock_critical" command? My phone restarts and shows the erasing screen but no actual bootloader unlock.
Any updates?
I'll try out when I make it back home sorry was flooded here we either need to mod kernel or laf aand github has a repo on some I'm checking on I'll be able to check more sorry and package disable pro will freeze apps or use autoprimes way on rooted you can use twrp file manager to delete system apps on moto z2 oem can't be touched but there's ways
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
ecompton59 said:
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
Click to expand...
Click to collapse
What are the different commands?
Okay I've tried the fastboot critical command same went to erase screen with the circle but fastboot flashing get_unlock_ability comes back 1 I've extracted kdz to dz still playing around trying
sign the petition to LG
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
There is an option for the T-Mobile version. Can someone actually try continuing with the progress?
I can't since I don't have the T-Mobile version.
LGM710TM is LG G7 from Italian provider TIM.
It has nothing to do with T-Mobile.
awww
umminkug said:
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
Click to expand...
Click to collapse
There's been petitions for like every locked-down LG device since the beginning of time. Never has it been effective, never will it be. LG doesn't reverse its bootloader locking policy.
Related
Looked at some threads and still wondering if they still works on unlocking bootloader. Seems like it tooks so much time for Devs, have anyone knows whats happening? Is it seems unlockable or not? :/
bdogan1912 said:
Looked at some threads and still wondering if they still works on unlocking bootloader. Seems like it tooks so much time for Devs, have anyone knows whats happening? Is it seems unlockable or not? :/
Click to expand...
Click to collapse
The T-Mobile US version comes unlocked. No one knows yet whether the other G3 versions will be able to be unlocked. The G2 was never unlocked but a work around where you could install custom Roms and kernels was eventually found. Its very much wait and see.
Batfink33 said:
The T-Mobile US version comes unlocked. No one knows yet whether the other G3 versions will be able to be unlocked. The G2 was never unlocked but a work around where you could install custom Roms and kernels was eventually found. Its very much wait and see.
Click to expand...
Click to collapse
Looked at many forums that people opened about 1-2 months ago. It seems like very very difficult to unlock it. I have much respect developers whichones tries to unlock it. Hope they can be successful on this. I'm glad to have stock rom this is very smooth i can admit it not like laggy touchwiz. But want to give a try to CM or PA or any AOSP ROM's like this, because back in time i was used AOSP based rom on my S III I9300 and loved it. Only reason that i want AOSP ROM is i think im loving pure Android it gives me ultra-smooth performance and simple UI.
The Verizon and AT&T threads have a bounty over $5700 and it looks like a few devs are close to having a solution.
what about the sprint ls990
Any word for Tge sprint ls990 at all I know it might be wrong section but might as well post somewhere
i can try
If someone can point me into the direction required to do bootloader unlocking i will give it a shot. Am a developer but have never attempted to do a bootloader unlock.
crqzyvonzipper said:
If someone can point me into the direction required to do bootloader unlocking i will give it a shot. Am a developer but have never attempted to do a bootloader unlock.
Click to expand...
Click to collapse
Well we have to ask it to developers whichones pro. on this.
bdogan1912 said:
Well we have to ask it to developers whichones pro. on this.
Click to expand...
Click to collapse
If only someone could tell me how to get to debug the software then ill be able to go from there because google isnt your friend when trying to find out.
[email protected] said:
Any word for Tge sprint ls990 at all I know it might be wrong section but might as well post somewhere
Click to expand...
Click to collapse
Devs in the AT&T bounty thread are working on an unlock for ALL variants besides the T-Mobile one.
sent from my LG G3
Yes. I know about that but it seems ike they are tking quite some time and I am not sure if they have given up?
Sent from my LG-D855 using XDA Free mobile app
joeyhdownsouth said:
Devs in the AT&T bounty thread are working on an unlock for ALL variants besides the T-Mobile one.
sent from my LG G3
Click to expand...
Click to collapse
Hope they can unlock soon. Phone was out on May and we're on September. Almost 4 months since released. And i know its hard but we have to wait. I wish i have money to donate/bounty 20 more dollars :/
crqzyvonzipper said:
Yes. I know about that but it seems ike they are tking quite some time and I am not sure if they have given up?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3
joeyhdownsouth said:
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3
Click to expand...
Click to collapse
Locked bootloader is like hot beer. Seems and tastes awfully. I wish companies sends their flagships with unlocked bootloader like T-Mobile did. Without custom recovery we're not able to even do a simple tweak (The tweaks who requires recovery such as modified frameworks and SystemUI's) Otherwise there is another option G3 Tweaksbox. But it shows very limited options if you're poor to buy it.
joeyhdownsouth said:
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3
Click to expand...
Click to collapse
HMMMM well ill have a look at what i can do tomorrow. Maybe i can find a small window here. I almost want to say that the abswer would be to adjust the bootloader to simply allow multi boot possibilities with partitions (at least in my mind that would be pretty cute).
I dont even really want the money. I just want to be able to do what i need to do. Multi OS's on one device.
bdogan1912 said:
Locked bootloader is like hot beer. Seems and tastes awfully. I wish companies sends their flagships with unlocked bootloader like T-Mobile did. Without custom recovery we're not able to even do a simple tweak (The tweaks who requires recovery such as modified frameworks and SystemUI's) Otherwise there is another option G3 Tweaksbox. But it shows very limited options if you're poor to buy it.
Click to expand...
Click to collapse
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3
crqzyvonzipper said:
If only someone could tell me how to get to debug the software then ill be able to go from there because google isnt your friend when trying to find out.
Click to expand...
Click to collapse
Also it's good to someone has interest about it. But it's ultimately hard job that they cannot solved in past 4 months. I appreciate all the tries/works on this job. Developers, you da real MVP! Well, other than that small joke we're still waiting. Not only international model D855 other models such as AT&T is waiting to unlock bootloader. T-Mobile users lucky that they got unlocked G3. I hope they will find a cure about it. If you can afford http://forum.xda-developers.com/att-lg-g3/general/bounty-att-lg-g3-bootloader-unlock-t2820785 go this thread and give some bounty (You're not have to do that its only suggest and saying thanks to hardwork)
yeeeeeepppp
joeyhdownsouth said:
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3
Click to expand...
Click to collapse
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.
joeyhdownsouth said:
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3
Click to expand...
Click to collapse
So you can say, i tried to modifiying build prop and ended with softbricking but so i got nandroid which is nice to me. Me neither. On my Note 3 i was tweaking build prop without any problem i've even enabled softkeys (I wondered a bit about how it will look etc.) But not gonna touch until this thing unlocks fully. Using stock rom & root with bloatware removed. With helper programs such as Greenify+Coolify. It's like science it's all about develop, try, fail, develop (or fix/debug),try, fail, develop try, success. It's alla about to hardwork and i appreciate all the efforts that developers given on this topic.
crqzyvonzipper said:
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.
Click to expand...
Click to collapse
Variants have different bootloaders. So we cannot do a copy/paste on it. If it works like this the devices will be unlocked in 10 min. I almost softbricked too but won against my wonder and didn't touched anything. It now works good. I love G3 even its bootloader locked lol
crqzyvonzipper said:
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.
Click to expand...
Click to collapse
Why don't you go to the irc chat room where all the devs hang out and do their work? You can talk to them there and see what they've tried or what they haven't. Believe the channel is: #lg-g3
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...
Would it be possible to inject something into a kdz and root that way? I know JOSH1X posted that pie kdz for all variants regardless of locked or unlocked bootloader.
I apologise if I'm completely wrong just trying to get some insight on this
Joe199799 said:
Would it be possible to inject something into a kdz and root that way? I know JOSH1X posted that pie kdz for all variants regardless of locked or unlocked bootloader.
I apologise if I'm completely wrong just trying to get some insight on this
Click to expand...
Click to collapse
The problem is that every kdz has an RSA Certificate witch will break if the kdz was edited. I do have a plan that can work but I'm still not sure and it's possible to completely lock the phone because it detected an edited boot (where magisk goes). It's possible to get system root too actually but I'm not sure if it's even going to get flashed.
LameMonster82 said:
The problem is that every kdz has an RSA Certificate witch will break if the kdz was edited. I do have a plan that can work but I'm still not sure and it's possible to completely lock the phone because it detected an edited boot (where magisk goes). It's possible to get system root too actually but I'm not sure if it's even going to get flashed.
Click to expand...
Click to collapse
If you can figure it out I'll throw you some cash I'm almost about to ditch this phone for a 6T because I'm carrying around 2 phones at the moment, this and a rooted ZTE Zmax.
thanks for the insight I appreciate it
Joe199799 said:
If you can figure it out I'll throw you some cash I'm almost about to ditch this phone for a 6T because I'm carrying around 2 phones at the moment, this and a rooted ZTE Zmax.
thanks for the insight I appreciate it
Click to expand...
Click to collapse
I just need someone to test it since my bootloader is unlocked and it has disabled security. If you want I can tell you how to do it but again. I'm not sure if it will trigger security but even if it does you should (not 100% sure) be able to go back with LG Up.
Again if it fails I'm not completely sure if it's possible to go back without LG service. (I'm saying that because I don't want to brick someone's main phone)
LameMonster82 said:
I just need someone to test it since my bootloader is unlocked and it has disabled security. If you want I can tell you how to do it but again. I'm not sure if it will trigger security but even if it does you should (not 100% sure) be able to go back with LG Up.
Again if it fails I'm not completely sure if it's possible to go back without LG service. (I'm saying that because I don't want to brick someone's main phone)
Click to expand...
Click to collapse
This is my main phone or I would try it out I can't brick it because I lease it with T-Mobile I'm sorry homie
Joe199799 said:
If you can figure it out I'll throw you some cash I'm almost about to ditch this phone for a 6T because I'm carrying around 2 phones at the moment, this and a rooted ZTE Zmax.
thanks for the insight I appreciate it
Click to expand...
Click to collapse
WOW, I'm in the same boat. I'm carrying around two phones too.
This and a rooted G5. and samee, i'll throw some money to whoever can get this rooted, I'm about to ditch the G7 for a OnePlus7 at this point.
Good bye LG!
Has anyone tried this method with success? I need to know.
Sent from my LM-G710 using Tapatalk
Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.