So I dug up my old LG V10 VS990 (verizon) and was trying to root it and turn it into a dedicated speedometer. After 18 hours of trying every thing I could possibly find on the internet, I'm totally at a loss. So I'm coming to you guys for help.
I've seemingly tried everything. The one thing I have noticed is, OEM Lock is no longer an option in Developer options. I have the android SDK and LGUP and have tried all the "one click" apps I could find and still can't find anything.
Here are the phone specs that may help
Hardware version : Rev 1.0
Android security patch level : 2017-12-01
Build Number : MRA58K
Configuration Version : B15.LGE.VS990.0
Software Version : VS9902BA
Software Status : Modified
Security Software version : MDF v2.0 Release 2
I'd greatly appreciate any info you can give me on rooting this phone, or at the very least how to turn off OEM Lock.
Also, I promise, I spent a lot of time on this already. I read page after page after page of google searches and tried everything. My guess is the information I'm gathering is all as old as this phone.
Related
I get message on Motorola site that says no to getting unlock key.
MOTO E, bought from Walmart
US Retail Phone;
Android version 4.4.4;
Baseband version MSM8610BP_1803.346.31.00R, TRAC_CDMA_CUST;
Kernel version 3.4.42-g6bc7ff3;
System version 21.12.40.confor_tacfone.trac_cdma.en.US tracfone;
Build number DXC21.5-40.
I have spent many days trying to get some java apps to run on my phone and discovered this whole world of phone development. I am in the computer industry myself and am a Linux Administrator besides having a number of Microsoft and Cisco certifications. I have followed many steps so far in this process but seem to be stuck at the point of getting the bootloader unlocked. I thought that I caught wind of maybe flashing the memory with a different image to get around this. Is this most likely the path I will have to take now. I did try to get the Moto key on two different computers.
What is the next step if Motorola doesn't give unlock key. THANKS
rhcrco
Really...No Replies
This is sad
In motorola development site are the instructions for unlock bootloader
Same issue here. Is there no hope?
If you can't unlock your bootloader, then either you have to wait until someone finds a way around it or leave your phone the way it is.
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?
Hi everyone! my friend has his LG Stylo 4 that has a version 7.2.0 of Android Accessibility Suite or TalkBack version 7.2.0. It is currently in a state of lockdown because it has been registered with a Google account and was reset and its now in FRP protection that requires a Google account to make the phone usable. We've tried all of my friend's accounts and we can't seem to find the one he used.
There are several videos and tutorials that explain how bypass the FRP by activating Talkback and accessing the internet via loopholes in the system. Most of these videos show a TalkBack version of 6.2.0 or 6.1 and they demonstrate different methods of achieving the same goal which it does with ease. But I have managed to figure out that this phone has a different version 7.2.0 and has apparently been designed as a way to close all the loopholes the system had in order to bypass the FRP.
Anyone has had this issue? any workarounds?
Can i downgrade to 6.2?
Can I root in order to downgrade while the phone is in lockdown?
Thanks!
Try this
I was in the same position. I have the same version of talkback ad your friend. There is a video that has steps that I was able to use to get in.
Start by googling "stylo 5 frp bypass". I used 5 expecting that it will have the same version.
Then find the video starting with "all LG September 2019" by Mohammed Ali. I can't link cause I only joined to respond to you.
Hello, guys, I have a galaxy A10 in which it does not appear oem unlock, I've tried all the tutorials on the internet but none of them work, I have this device since the launch in Brazil, at the time it was android 9, and this oem unlock option always appeared, but as at the time it didn't have a custom rom yet (or I haven't found any) I left it disabled, now in 2021 I saw several custom rom for my device, but after upgrading to android 10, I was no longer able to have the option of oem unlock, I will pass the current configuration of my device.
Galaxy A10 (105M/DS)
Android 10
security patch March 1, 2021
build number A105MUBS6BUC2
is there any way to still be able to root and unlock the bootloader?
I don't care if I have to install rom from other countries, I just want to be able to root and install custom roms.
About the tutorials I saw on the internet, they were just the most common ones like delaying the date and looking for an update, I saw a tutorial in which the person left and entered the developer settings until it appears, I already did a hard reset and tried to make oem unlock appear with all the tutorials.
lTheuSl said:
Hello, guys, I have a galaxy A10 in which it does not appear oem unlock, I've tried all the tutorials on the internet but none of them work, I have this device since the launch in Brazil, at the time it was android 9, and this oem unlock option always appeared, but as at the time it didn't have a custom rom yet (or I haven't found any) I left it disabled, now in 2021 I saw several custom rom for my device, but after upgrading to android 10, I was no longer able to have the option of oem unlock, I will pass the current configuration of my device.
Galaxy A10 (105M/DS)
Android 10
security patch March 1, 2021
build number A105MUBS6BUC2
is there any way to still be able to root and unlock the bootloader?
I don't care if I have to install rom from other countries, I just want to be able to root and install custom roms.
About the tutorials I saw on the internet, they were just the most common ones like delaying the date and looking for an update, I saw a tutorial in which the person left and entered the developer settings until it appears, I already did a hard reset and tried to make oem unlock appear with all the tutorials.
Click to expand...
Click to collapse
I forgot to mention, when I go into download mode, instead of being in the prenormal, mine is in normal.
lTheuSl said:
I forgot to mention, when I go into download mode, instead of being in the prenormal, mine is in normal.
Click to expand...
Click to collapse
Same issue, A107m (a10s) mtk doesn't show the oem unlock after a11 update and i can't find a solution (it is on kg state normal)
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