Hello all,
As a frequent user to the XDA Forums but a first-time poster, please allow me, from the onset, to express my gratitude for the litany of assistance this forum has offered. The resources here and pure talent have proven invaluable; from assisting me in actually taking a Nokia Windows Phone and installing Android, bypassing Google's FRP on an LG Tablet to mirroring a broken display and thus saving my S5 Neo. Please accept my humble thanks and heartfelt gratitude. Perhaps one day, I will be able to offer something back to this amazing community. Kindly bear with me as I need to ask you all for some expertise and guidance one again — I have some specific questions — as a segue into the first inquiry, pardon me if this is the wrong subforum.
Question the first. And you have my permission to all point and laugh at me for asking this one: Is this subforum dedicated to a device with a specific label of LG G Pad X 8.0 or is X expressive of a variable employing categorization of many devices? I know how to research, but I still can't find a direct answer or mere suggestion; deduction implies the latter. Specifically, I am enquiring about the LG G Pad III 8.0 FHD (the LG-V522). I do hope X was a prelude to "insert Roman numeral here" or now I just sound like a verbose moron with too much time on his hands.
Background & Specifics:
- Google FRP was bypassed and a clean, stock installation of Andriod 7.0 Nougat was employed.
- While this tablet was originally sold with Marshmellow 6.0.1, support for OTA updates extended to upgrading to Nougat which became accessible upon the successful factory reset after bypassing Google's FRP.
- This tablet is not rooted.
- According to LG and LG's Developer Blog, the V522 bootloader is not unlockable.
- This tablet does employ a SIM card slot and I've been using an active cellphone SIM (and of course, WiFi where available), but apparently the tablet is only utilizing the data component of the Rogers Share Everything plan and when I dial my own number from a third-party phone, it goes straight to voicemail. Yet sending texts to my number will pop up as a notification just like any other smartphone.
- Tablet is "Canadian" and SIM-locked to the Rogers / Fido network.
Tablet Details:
- Android Version is 7.0 Nougat employing a security patch level dated December 1, 2016. Baseband version is MPSS.TA.1.0.c3.3-00015-8952_GEN_PACK-1.79167.2 and it's running a kernel v3.10.84-g22068de [email protected]@ ) #1 SMP PREEMPT Mon Dec 19 14:48:23 KST 2016. Its build number is NRD90U and it runs a software version V52220a. Firmware version is 7.0.
- Factory Version is specified as LGV522AT-01-V20a-302-720-DEC-19-2016-ARB00 with SW Original Version being specified as LGV522AT-00-V20a-RGS-CA-DEC-19-2016-ARB00.
- Apparently, this product is also categorized as "b3_rgs_ca". I have seen this label, almost to the point of a recurring motif, through my research, as simply referred to "B3".
- The LG "hidden menu" is accessible by dialling *#546368#*522# via the Google Hangouts "Contacts" app.
- "Download Mode" is accessible through ADB commands and respective key-combinations and I have been able to reload or "flash" V52220a more than I'd care to admit.
Questions:
- Since the bootloader is apparently "unlockable" by official standards, does this explain why even through ADB I cannot get the tablet to boot into the bootloader partition? I'm familiar with ADB, Fastboot and the Command Prompt and all respective drivers on my Windows 10 desktop are the most current and configured correctly and the step of enabling USB debugging, OEM unlock, et al has already been covered (unless you've got a completely random idea of some random setting I may have overlooked). Invoking the command "adb reboot recovery" triggers an entry into the stock recovery mode, but selecting from the menu "reboot into bootloader" merely restarts the device; as does invoking "adb reboot bootloader" from the command prompt.
- If "download mode" is supposed to be synonymous with fastboot or bootloader mode, why does the tablet not acknowledge any fastboot commands?
- Can or would anyone be kind enough to explain why there is such a diverse categorization of this tablet and what the specific nuances imply (i.e. model B3 vs. LG-V522 vs. LG G Pad X)? What is the meaning of V20a contained within the descriptors/identifier of SW Original or Factory version?
- Is it possible through an entirely unofficial method to root the tablet without unlocking the bootloader (some users have reported yes, but never when utilizing the "Canadian" version)?
- Employing "dirtycow" is no longer an option as the security patch installed precludes this possibility (unless there have been updates to the process of using a muddy heifer that I haven't found yet).
- If rooting is not possible at the moment (even through unofficial methods), is it still possible to establish and employ an "emulator" on the Stock OS to "trick" the tablet into thinking it has a built-in cellular modem? I've found several references that suggest this tablet does have a cellular modem because of the SIM card, but when I try and look at the tablet's hardware on the actual device, telephony information is lacking.
Trying to unlock or hack the bootloader or even just rooting this tablet seems more like a beautiful woman slapping you for simply asking if it'd be okay to buy her a drink — yes, you want her to give you full root access — but hey, you're being a gentleman and trying to wine and dine her first (I know I'm a nerd and it has been awhile, but I digress).
- Carvio
FRP reset on the LG-V522
Hi Carvio,
I haven't been able to perform an FRP reset on my LG Gpad3 LG-V522. I didn't want to use the device on the cellular network just as a tablet at home.
I ended up buying the Octoplus FRP reset dongle but it turns out to not have the correct model in the setup.
How did you manage to bypass the FRP rest or rest it on this tablet?
I think Chimera may have a tool to do the reset but that means another $100 to unlock the tablet...
Thanks in advance,
REDRONAN.
carvio said:
Hello all,
As a frequent user to the XDA Forums but a first-time poster, please allow me, from the onset, to express my gratitude for the litany of assistance this forum has offered. The resources here and pure talent have proven invaluable; from assisting me in actually taking a Nokia Windows Phone and installing Android, bypassing Google's FRP on an LG Tablet to mirroring a broken display and thus saving my S5 Neo. Please accept my humble thanks and heartfelt gratitude. Perhaps one day, I will be able to offer something back to this amazing community. Kindly bear with me as I need to ask you all for some expertise and guidance one again — I have some specific questions — as a segue into the first inquiry, pardon me if this is the wrong subforum.
Question the first. And you have my permission to all point and laugh at me for asking this one: Is this subforum dedicated to a device with a specific label of LG G Pad X 8.0 or is X expressive of a variable employing categorization of many devices? I know how to research, but I still can't find a direct answer or mere suggestion; deduction implies the latter. Specifically, I am enquiring about the LG G Pad III 8.0 FHD (the LG-V522). I do hope X was a prelude to "insert Roman numeral here" or now I just sound like a verbose moron with too much time on his hands.
Background & Specifics:
- Google FRP was bypassed and a clean, stock installation of Andriod 7.0 Nougat was employed.
- While this tablet was originally sold with Marshmellow 6.0.1, support for OTA updates extended to upgrading to Nougat which became accessible upon the successful factory reset after bypassing Google's FRP.
- This tablet is not rooted.
- According to LG and LG's Developer Blog, the V522 bootloader is not unlockable.
- This tablet does employ a SIM card slot and I've been using an active cellphone SIM (and of course, WiFi where available), but apparently the tablet is only utilizing the data component of the Rogers Share Everything plan and when I dial my own number from a third-party phone, it goes straight to voicemail. Yet sending texts to my number will pop up as a notification just like any other smartphone.
- Tablet is "Canadian" and SIM-locked to the Rogers / Fido network.
Tablet Details:
- Android Version is 7.0 Nougat employing a security patch level dated December 1, 2016. Baseband version is MPSS.TA.1.0.c3.3-00015-8952_GEN_PACK-1.79167.2 and it's running a kernel v3.10.84-g22068de [email protected]@ ) #1 SMP PREEMPT Mon Dec 19 14:48:23 KST 2016. Its build number is NRD90U and it runs a software version V52220a. Firmware version is 7.0.
- Factory Version is specified as LGV522AT-01-V20a-302-720-DEC-19-2016-ARB00 with SW Original Version being specified as LGV522AT-00-V20a-RGS-CA-DEC-19-2016-ARB00.
- Apparently, this product is also categorized as "b3_rgs_ca". I have seen this label, almost to the point of a recurring motif, through my research, as simply referred to "B3".
- The LG "hidden menu" is accessible by dialling *#546368#*522# via the Google Hangouts "Contacts" app.
- "Download Mode" is accessible through ADB commands and respective key-combinations and I have been able to reload or "flash" V52220a more than I'd care to admit.
Questions:
- Since the bootloader is apparently "unlockable" by official standards, does this explain why even through ADB I cannot get the tablet to boot into the bootloader partition? I'm familiar with ADB, Fastboot and the Command Prompt and all respective drivers on my Windows 10 desktop are the most current and configured correctly and the step of enabling USB debugging, OEM unlock, et al has already been covered (unless you've got a completely random idea of some random setting I may have overlooked). Invoking the command "adb reboot recovery" triggers an entry into the stock recovery mode, but selecting from the menu "reboot into bootloader" merely restarts the device; as does invoking "adb reboot bootloader" from the command prompt.
- If "download mode" is supposed to be synonymous with fastboot or bootloader mode, why does the tablet not acknowledge any fastboot commands?
- Can or would anyone be kind enough to explain why there is such a diverse categorization of this tablet and what the specific nuances imply (i.e. model B3 vs. LG-V522 vs. LG G Pad X)? What is the meaning of V20a contained within the descriptors/identifier of SW Original or Factory version?
- Is it possible through an entirely unofficial method to root the tablet without unlocking the bootloader (some users have reported yes, but never when utilizing the "Canadian" version)?
- Employing "dirtycow" is no longer an option as the security patch installed precludes this possibility (unless there have been updates to the process of using a muddy heifer that I haven't found yet).
- If rooting is not possible at the moment (even through unofficial methods), is it still possible to establish and employ an "emulator" on the Stock OS to "trick" the tablet into thinking it has a built-in cellular modem? I've found several references that suggest this tablet does have a cellular modem because of the SIM card, but when I try and look at the tablet's hardware on the actual device, telephony information is lacking.
Trying to unlock or hack the bootloader or even just rooting this tablet seems more like a beautiful woman slapping you for simply asking if it'd be okay to buy her a drink — yes, you want her to give you full root access — but hey, you're being a gentleman and trying to wine and dine her first (I know I'm a nerd and it has been awhile, but I digress).
- Carvio
Click to expand...
Click to collapse
REDRONAN said:
Hi Carvio,
I haven't been able to perform an FRP reset on my LG Gpad3 LG-V522. I didn't want to use the device on the cellular network just as a tablet at home.
I ended up buying the Octoplus FRP reset dongle but it turns out to not have the correct model in the setup.
How did you manage to bypass the FRP rest or rest it on this tablet?
I think Chimera may have a tool to do the reset but that means another $100 to unlock the tablet...
Thanks in advance,
REDRONAN.
Click to expand...
Click to collapse
i tried to frp myself and i got it in qualcomm 9008 mode. can you make a backup of your device?
Related
Hi all,
I've spent a rather frustrating week or so in the throes of searching Google and XDA to figure out how to get my brand new RS988 upgraded to the 21c software version on Nougat. Here's what I've done so far:
-Check for OTA updates using the OS. No dice...it went from 11a to 11c and will not find any further updates.
-Use LG Bridge to try to update the software. No dice. The software tries to get the current OS version and then says "cannot find operating system version" and won't contact home base to get the new files.
-Reboot into boot loader to install TWRP. No dice...the phone will not reboot into the boot loader for some reason. I've tried using both the ADB method of "adb reboot bootloader" and "adb reboot-bootloader", but both just have it reboot into the full OS. I've also tried powering on the phone while holding the volume down button, to no avail.
-All root and TWRP methods, and even getting the official bootloader unlock require booting into the boot loader
The one thing I *have* been able to get to work was re-flashing a KDZ of the RS98811c software from autoprime's linked repository.
As best as I can tell, I am stuck. Without being able to install TWRP via the boot loader I don't know how to update the software. Please help me figure this out!
Edit: additional device info added
Android version: 6.0.1, 2016-07-01 security patch
Baseband version: MPSS.TH.2.0.c1.4-00010-M8996FAAAANAZM-1.43591.5
Kernel: 3.18.20
Build: MMB29M
Configuration: F15.LGE.RS988.0
Software version: RS98811c
Security software: MDF v2.0 Release 1
Thanks!
Use lg up
It's possible that you have the RS988.BPT version (Brightpoint), which only got updated to 11h, I believe. I sent in a RS988.USA version, and they swapped for a new BPT motherboard. I've since sent it back yet again to get that resolved.
It appears to be a Tracfone Wireless version, according to the box, at least. It was supposed to be new, not refurb, so fingers crossed that's all good as well. Even if it was the Brightpoint version, wouldn't that have been fixed when I flashed the USA stock ROM?
I also don't see how to use LG UP to reboot into boot loader mode. It only shows me the phone, with nothing clickable, and a selection of 4 processes: refurbish, upgrade, phonesetting, and FOTA upgrade. Not wanting to mess up my phone, I am trying to be cautious about just trying either of the latter two options. Especially without a file there. Thoughts?
You did unlock the bootloader am I correct?
Matthew_Jay said:
You did unlock the bootloader am I correct?
Click to expand...
Click to collapse
Nope. I can't get into the bootloader (unless I've totally missed a method to do that). Even the instructions on LG's website pre-suppose that you can enter the bootloader. Step 9 on their bootloader unlock instructions say:
9. Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Click to expand...
Click to collapse
Unfortunately, issuing that command simply reboots the phone without a bootloader in sight. Any commands issued by fastboot after the "adb reboot bootloader" command just sit there saying "waiting for device". I think if I could get this far, the excellent instructions elsewhere on these forums would have me sorted the rest of the way, since then I could use TWRP to flash a more recent OS version. Thus far, it's only LG UP which works, which also requires a .KDZ file, but I can't find one for any version > 11c.
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
AdamDG said:
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
Click to expand...
Click to collapse
Simple answer is "You can't". I am in the same boat, stuck on 11c with no OTAs in sight. The ability to boot into the bootloader wasn't added until a later version (11h, I think?) So until/unless LG releases a KDZ of one of the later versions, you (and I) are out of luck.
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
AdamDG said:
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
Click to expand...
Click to collapse
Hey AdamDG, were you able to solve your issue? I am stuck with the same situation and asinine LG folks won't help me out because Total Wireless/Tracfone are supposed to take care of the matter. But the latter are not responsible for software updates because they are MVNOs and don't (need to) care.
Truly jokers, but more importantly, taking customers for a s(laughter) ride!
Hi all. I'm a complete newb and don't even know the correct terminology to use. If I should not be posting this here maybe someone could point to the right place for me to post. Here is my issue/question: I have a Moto E (the second generation model, aka Moto E 2015) and it is the LTE version - the XT1527. I bought it used and it had originally been an ATT phone. I went to the ATT website and got from them a code to unlock the phone so I could use it with my provider (Ultramobile, an MVNO that uses T-Mobile's infrastructure). It's a pretty basic phone and pretty slow. I have removed all the ATT-branded apps I can but there is still plenty left. What I am wondering is: Could I somehow load what I think is called firmware so that the phone was like the versions actually sold by Motorola? I figure the less branded crap on it, the more space I will have for my own apps and perhaps it may even be a little faster. I have read quite a lot of posts on this forum and it seems to be quite hard to do because ATT phones do not have unlockable bootloaders (and I don't even know really what that is yet). But when I go into developer options on the phone there is an option called "OEM unlocking" that has, as a subtitle, "Allow the bootloader to be unlocked". It is currently switched off, but it does allow me to turn it on if I want to. It gives me some sort of warning about "Device protection features will not work while this setting is turned on" but that doesn't sound too scary (although I am of course totally ignorant and could be totally wrong about that). But does this mean that on this phone if I unlock the bootloader, I could load the original Motorola firmware/ROM once I learn how to do it?
Thanks for any help.
Dan
P.s. this would sort of be a learning experience. I have another phone I would use while I try to play with the Moto E.
I actually didn't see the part where you said ATT can't have the boot loader unlocked my bad, you can still check using the Motorola site I guess but yeah you can't change the ROM unless you can unlock the bootloader
So the first thing you should do is unlock your boot loader
Note: this will wipe all the data on your phone so back it up before hand
https://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then I would actually suggest that you change to Lineage OS instead. The Motorola stock ROMs are no longer being updated with security updates AFAIK and you are stuck on marshmallow (android 6). Lineage OS has all the security updates and is on nougat (android 7)
To do that first you would flash a custom recovery (TWRP)
https://forum.xda-developers.com/mo.../twrp-squid-twrp-recovery-moto-e-lte-t3137649
Then you can find our official Lineage OS here https://forum.xda-developers.com/mo...ment/rom-cyanogenmod-14-1-moto-e-lte-t3516694
Thanks but you have not addressed the main point of my post, which was whether my phone's bootlocker is or is not unlocked. Also, I am not interested in anything other than stock ROMs and I prefer Marshmallow (or better yet Lollipop). Definitely don't want Nougat.
I have this phone to, I have a question, this device exists possibly to unlock bootloader and put any custom rom? I can't find tread with this info
I'm planning to use a low-cost tablet for a wall mounted home automation display. For this use I have bought an rather unkown but very affordable tablet from SPC (Smart Products Connection) (Model Heaven 10.1) running on Android 7.0 with kernel-version 3.10.65. To unlock features I need for a wall mounted display (e.g. always on, controlling the charging of the battery to enhance battery lifetime, adjusting the tablet time automatically through my local network timeserver etc. etc.) I need the device unlocked. I followed the nice description in the Forum Hovatec (<https://>forum.hovatek.com/thread-1405.html) to get into custom recovery mode and make a stock boot image but I got stuck at the step where the tablet should boot into recovery since fastboot is not able to connect to the tablet. Thus I assume that I cannot unlock the bootloader of the device. The applications like King Root, KingoRoot and the like do not seem to find a software exploit to help out here either (most probably of the uncommon model I use) and OneClickroot wants to have a premium for unlocking it (the app claims that it can do it but I'm very reluctant to pay 30-50$ to unlock a tablet which I already have bought, to a very shady company...
So I hope that someone here has already experience with my tablet model and may help out with a description how to:
1.) Get to unlock the bootloader
2.) Get a stock boot image
3.) Unlock the device
4.) Or have a software exploit to unlock the tablet online
?
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
TLDR; I am wondering if all U.S. phones with Snapdragon cannot be normally rooted by just enabling OEM unlock/unlocking bootloader and must be rooted in an expert/costly method. Or if accounts from people saying they enabled OEM unlock on their Moto G Powers I read were not just fictional or with non-U.S. phones.
Click to expand...
Click to collapse
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
jwoegerbauer said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked...
Click to expand...
Click to collapse
See the CID and OEM unlock posts
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
If you get the bootloader unlocked
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
Click to expand...
Click to collapse
Absolute nonsense.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, this there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
Click to expand...
Click to collapse
You must wait, I believe it was several days of the device being online (wifi at least) to get it to permit unlocking the bootloader. I know with mine (US Xfinity Wireless), out of the box, it was gray, but 2 or 3 days later it was able to be toggled and I unlocked and got Magisk installed easily, using the patch stock boot.img method, and flashing it via fastboot beyond that. So you can do it, just can't do it before you activate the thing properly I think is the main block there you're describing. So perhaps those outside the US (with US models they can't toggle) can connect to a VPN'd wifi network and have it look like it's in the US, maybe.
There's a lot that can be done on these with just tinkering to get it there is all. But make sure you have your stock firmware is all, so you can quickly get it back into bootloader and just a flash away to fix anything really.
jwoegerbauer said:
Absolute nonsense.
Click to expand...
Click to collapse
Okay. Legit question here... How does one go about injecting SU binary to the system on the moto g 2021 series with secured boot?
Why should SU binary get housed in /system/... ? It's irrelevant where it's located, the main thing is that it's available and executable. Even Magisk doesn't store it in /system/.. but in /data/..
Because folder /data/local/tmp by default is mounted as RW my recommendation is to store it there. Using this storage place isn't conflicting with SELinux and/or AVB.
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When you have to run a shell command what requires elevated rights, then you run
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Deleted member 1890170 said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
it needs to be unlock
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
According to this list
LineageOS 20 Supported Phones: All Models For 2023 [UPDATED]
Here's a quick breakdown of ALL the Android phones that can run LineageOS 20...
www.knowyourmobile.com
the popular Lineage OS isn't available for the Galaxy A14
Rottytops said:
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
Click to expand...
Click to collapse
You can't do anything because the bootloader lock is on.
I bypassed frp with sp flash tool but a14 has exynos processor so sp flash tool will not work.
There is no offical previous android, So downgrade will not work too.
Was able to bypass FRP unlock using one of those paid tools, but it may have been unnecessary to pay. (SamFW to be specific)
I'll explain for future googlers dealing with the same issue.
So I had the ATT model of the device. Specifically model SM-A146U. It comes with an Exynos or Mediatek SoC.
Mine was specifically the MT variant.
I used Odin3 to revert to the stock build. Build dated November 29/Dec 1 2022; despite the official release date of the device being Jan 2023.
The emergency code *#0*# does not work, but *#*#88#*#* does.
Obviously you needed Samsung USB, ADB, drivers installed. Additional troubleshooting has me download Microsoft Visual C++ 2015 ; and MT65XX Preload Drivers.
The SamFW tool claims it's free to remove the FRP lock on security patches pre-dating December 2022.
The SamFW tool only suggests you needed Samsung driver's and Visual C++. So I tried several times using the SamFW tool to push it's exploit, and it kept failing.
So in a moment of weakness, I bought the $15 credit pack because it promised "All models", ran the tool again, and still it failed. It required a credit card number for a service called coffee break or something, which is exactly the shady **** I have a cash app card for. I was not going to use my real bank account.
Because it runs a ADB exploit, I reboot into Recovery. Then in recovery menu, I select to Reboot into Bootloader, which puts the device into fastboot.
This is where I discover that I had no ADB drivers.
So I install ADB, and open Terminal/shell, whatever you call it. (Hold Shift and right click in ADB folder to shortcut ADB terminal)
I type:
Fastboot Devices
Didn't get a serial. I reboot Fastboot again, this time with Device Manager open on Windows, and notice for 5 seconds, a device called MT65xx preloader was lacking driver, and unloaded to reload ADB drivers. This is where I find out I'm using a MediaTek SoC
So I finally googled and install MT65xx Preload. Reboot to Fastboot 1 more time. I type
Fastboot Devices
I get a serial.
So not I reboot to system, then on phone in emergency dial type *#*#88#*#* then do another device check. Looks good.
Because I already paid $15 for the premium unlock, that's the first option I pick it finally unlocks. But because all this time I was missing critical mediatek drivers, the free option still could have worked. So I can't confirm if being free would have sufficed, or if I needed that paid service.
But what's done was done, and I was able to get into the phone.
So to recap I used:
SM-A146U ATT stock Rom (5.5GB), earliest build Nov-Dec 2022 (Google it)
Odin v3 Flash Tool (Hold Vol+ Vol- & Power to access)
Samsung USB Drivers (Latest and official)
Google ADB Drivers (Mini installer)
Microsoft Visual C++ 2015
MT65xx preloader Drivers (Google it)
And SamFW 4.6 FRP Tool
Emergency Dial code : *#*#88#*#*
To bypass FRP Lock on Galaxy A14 ATT version, Model SM-A146U ; MediaTek variant.
and to reiterate, Recovery and Fast Boot are not necessary in any part of the process.
I use Recovery to boot into Fastboot, and I only use FastBoot + ADB to personally confirm that my computer recognizes the device connected in several boot modes