Hi,
Originally I had opened this thread in LG 5 AT&T forum. But, after a request from @Nitro1max1, I understood that he is right and it should be reached for more useres.
Please find the link for requesting LG to open our bootloader - https://www.change.org/p/lg-electro...utm_source=share_petition&utm_medium=copylink
Hopefully, we could make a change together.
last thing, this is the origina thread - https://forum.xda-developers.com/at...se-kdz-tot-t3587926/post71887733#post71887733
I will switch updating here since it will be more convinent to update in one single place.
Cheers,
Mor
stop
What happens when we reach 100 people?
Hopefully, LG will pay attention to our request. This device is no longer a valuable asset for LG (the newly LG G6 is out), therefore I guess we will have a fair odds with getting an unlocking method.
H840 now officially can unlock bootloader
I signed even though I know they will give a sh...t
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand here.
About the H840, they are so lucky
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
ForMartha said:
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
Click to expand...
Click to collapse
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Honestly Annoying said:
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
ForMartha said:
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
Click to expand...
Click to collapse
You can find the full explanation if you dig around, but basically for the G5 (and most devices) the bootloader unlock is not located in aboot, it is an actual change in the whole bootchain. You can modify aboot to disable a sig check, but that is not the same as unlocking the bootloader and doing so will break the signature of the aboot.img and hard brick your device.
Question is, what is the real differance between H850 to H820. they are sharing the same physical parts, but the bootloader is diffarent. so, by using external tool that will flash the new bootloader, it could be done, right?
Signed.
Honestly Annoying said:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
ayaromenok said:
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
Click to expand...
Click to collapse
Yep, I agree. I tend to belive that it's LG's move. let's hope that they will do the same for the H820.
Meanwhile, I've spend sime time speaking with @autoprime (thanks for your time!) and the way he sees it is the following :
1. Finding some exploit in the H820 bootloader that will pretty much will effect all the other devices. Question is, if one will find it - will he share it on XDA or sell it to Qualcomm or LG. Time will tell.
2. Finding some leaked debug bootloader (one which the development team is using or the tech system) - That way we will be able to flash custom boot.img (AKA some open recovery).
Meanwhile, I'm doing some digging around for finding exploits.
Now, let's have our finger crossed for one to happen.
ForMartha said:
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand
Click to expand...
Click to collapse
You have to take into account that for carrier-specific models, the CARRIER is actually the customer of LG, not the end user.
Only if you buy an unlocked device you are LG's customer.
So I'd guess that LG cannot provide a bootloader unlock for carrier-specific devices, this goes against the contract. Of course things change when the carrier agrees to the unlocking. But do you really think your carrier will allow this?
T-Mobile USA doesn't seem to care, but Verizon and AT&T?
Here in Europe carriers sell the regular H850, they "just" add additional bloat, so you can flash stock KDZs and unlock the bootloader. But the American carriers seem to stick to a different approach. Customers need to vote with their wallets to change this, but I think most people just don't care.
Well said BabelHuber,
Still, I have wish that it will be released eventually.
LG needs to do this or it will be my last LG phone.
Signed
Signed
Related
Hello everyone,
Right now I have another thread for the root over ADB with DirtySanta, I've that far. I have a potential method but I need more information on it from somebody else so I am waiting on a response from him, once i have that I'll work on it. If you guys have any other potential ideas that'd be great.
Thanks,
Abine45
This is my link to the root on ADB. I will be updating it tonight or tomorrow for the convenience of others. Thanks for waiting.
http://forum.xda-developers.com/verizon-lg-v10/general/temporary-root-adb-t3523538
NEW INFORMATION FOUND! I GOT SIGNIFICANT ROOT ACCESS WITH DIRTYSANTA!!!
SO i used the DirtySanta fearing for my life I wouldn't ruin my device, well the v10 failed it. rebooted and it didn't do anything but reboot back into the normal bootloader and stuff. But what i found is that he go the dirty cow to just work under root, so maybe from there we could do something, anybody have any ideas?
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Haxcid said:
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Click to expand...
Click to collapse
How did Tungkick manage to repackage it then? The dirty cow exploit can exchange recovery though on an unlocked bootloader so shouldn't I be able to replace the boot image if done correctly wouldn't it work? I could possibly unpack everything and modify it all and test it but the issue comes back to repacking and flashing?
Ask him, but if you attempt to do this on a locked and encrypted boot loader then you will brick the phone. I mean think about it, if it was really just that simple every phone would be rooted and rom'd. Most phones running 6 or above have had the security vastly increased to make the phone secure so they can be used by government employees. Hence the introduction to SELINUX polices into the kernel which is why getting root is so unbelievably difficult. The locked boot loader resets everything at boot so getting root and maintaining is so hard combined with SELINUX does not allow standard root to perm. write anything to the system partition and then good old hboot kills anything you did mange to write on reboot... you can start to see how difficult this really is.
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
LG are just not popular devices for hacking due to they make if extremely difficult. LG is a Corp. friendly company it is why Verizon loves them where companies like HTC are a bit more user sympathetic.
Funny you say that
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
Funny you say that! Tungick said to me, and i quote "[email protected]#$g you" and blocked me from Facebook. He also told me that he wouldn't tell me because it's a secret. He didn't speak very great English, that's why there is an ing at the end of the F-bomb. I asked Jcase through XDA and he said he wouldn't and so i put it better explanation of help through an email and he said I was harassing him... In which case before hand he said he doesn't develop for LG because he says basically we are A-holes sadly and that we don't live up to our donation pledges.
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
beavis5706 said:
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
Click to expand...
Click to collapse
True, that's why I'm going to try to do it. If you know anything and want to help could use it.
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
qujuanmiller said:
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
Click to expand...
Click to collapse
For sure, message me on xda.
beavis5706 said:
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
Click to expand...
Click to collapse
Anybody can help! Do some research and send it and whatever you would like to do. Try different things, Try to modify bits of code and see what you can do! Always gotta start somewhere!
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
beavis5706 said:
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
Click to expand...
Click to collapse
The thing with that is the fact that even if I know how systemless root works, I still have no way to install it, so first I need to find a way to get in the system.
Think I might have a way though
From what I understand systemless root will modify the boot image to attain root. Super SU will decide how to flash based on firmware version. Will automatically root normal with Lollipop and down, will automatically modify boot image on Marshmallow and up. How you will be able to modify the boot image on a VS990 without bricking it I don't know.
In order to do system less root we need a unlocked bootloader... It says that everywhere I'm reading
Hi abine45,
Please read this post completely, the guys here are close to obtain the perma root on android 6, using dirty cow.
https://github.com/timwr/CVE-2016-5195/issues/9
Sent from my E2006 using Tapatalk
I looked at this thread... a bit more technical than I am able to do... did it end up working? Looks like no, but I might have missed something.
Thanks!
Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
Is there still no way to unlock the bootloader and get a custom recovery onto an AT&T SGH-i527 Mega 6.3 over six years later? These phones are still popular despite having frequent hardware failures.
I found a site claiming to have instructions for flashing LineageOS 17.1 to the AT&T i527, but I'm pretty sure it's just a bot-written ad site with articles that appear to make sense at first glance, while nevertheless being completely useless and existing solely to harvest traffic for ad views by appearing to have real-looking content.
Note that in the URL below, I replaced ".com/" with ".c/", just to avoid having Google see this post and raise that URL's ranking because it found a link to it from here.
https://tweakdroid.c/lineage/samsung-galaxy-mega-6-3-samsung-sgh-i527-meliuslteatt/
On one hand, it seems to superficially make sense... until you you get to steps 2 and 3...
Next, you need, unlock the bootloader. You can’t do this if you have a locked bootloader. If you haven’t heard about this, you can look at the guide of unlock bootloaders.
As you have done these, next install TWRP recovery in your phone. You can use our guide for the installation of the TWRP recovery process.
... then head over to XDA, and ultimately lose several hours of your life that you'll never be able to get back before discovering that as far as anyone here can tell, unlocking the i527's bootloader is literally impossible (at least, without paying more than the phone is actually worth to have someone do it with a JTAG... and based on a 28-page thread I spent 2 hours reading, it looks like that didn't even work when someone tried paying someone to do it).
For what it's worth, I actually have two of these phones:
One has 4.2.2 (I527UCUAMH1)
One has 4.4.2 (I527UCSBNJ4)
As far as I know, the second one is doomed to be a useless paperweight forever, because nobody has ever even manged to root 4.4.2, let alone unlock its bootloader.
I haven't completely given up hope that the first one might eventually be useful for something, but as far as I can tell after plowing through old and dead threads here, 4.2.2 is rootable, but not even it can be unlocked for reflashing... and TWRP has never been successfully made to work with it. I'd love to be wrong... but I'm not feeling very hopeful right now.
hello does anybody know a working method to how to find and download and flash a Stock Rom on my Nokia 7.2 all Tutorials i try so far but did not work well i stuck as well in security patch problem it will not install thats why i want try to find a Stock Rom to flash again with working update
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
singhnsk said:
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
Click to expand...
Click to collapse
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Lord-Xanthor said:
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Click to expand...
Click to collapse
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.ii
Click to expand...
Click to collapse
I don't mind paying.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
Click to expand...
Click to collapse
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Lord-Xanthor said:
I don't mind paying.
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Click to expand...
Click to collapse
I will edit this after, if this works so others can try as well. It's not free and is costing me $150 to do. Will update in a few weeks.
New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.