{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Factory Reset Protection (FRP) is a security method that was designed to make sure someone can't just wipe and factory reset your phone if you've lost it or it was stolen. Starting with Android Lollipop, FRP is "standard" in vanilla Android, and most companies making our phones have implemented it in their own models. It's a good thing — it makes a stolen phone harder to use, which makes it less appealing to thieves, and anything that can protect our data on a phone we've lost is welcome.
The problem is that people are selling or trading or even giving away phones with FRP enabled and this makes things difficult for the next user.
I found myself in this predicament recently having purchased a used LG V10 and, being in a rush, I flashed a factory KDZ on the device. Needless to say, I could do nothing with the phone once I rebooted - I was stuck on the proverbial "Verify your account" prompt.
If you reset a phone with FRP enabled, you have to provide the user name and password for the last Google account that was registered with the device. There are tons of random work-arounds on the Internet, but they tend to get patched almost as soon as they are discovered. You'll pretty much need to know the login details for the last account to use the phone before you can do anything with it if FRP was enabled before you reset it.
A quick XDA search turns up some 13000+ hits pertaining to "frp v10 verify account" and it takes time to try them all. The truth is that most were exploits geared for Android versions prior to Nougat and, even those which claimed to fix the problem for Android 7 no longer worked due to changes LG likely made between the 30B and 30C updates.
To make a long story short I finally found one method that worked. I got the device back and fully functional. Although I have only tried this on the 901H (T-Mobile variant) it may well work on any V10 running LG's version of Nougat (30C). If you try it and it fails or works you should let people know which variant and how you made out.
The solution for the V10 devices is documented in this video.
The ADB command line used is in the comments of the video but for ease of use this is it:
Code:
adb shell content insert --uri co-ntent://settings/secure --bind name:s:user_setup_complete --bind value:s:1
If you have another method that you have tried and know works on this specific device, by all means, do tell.
It is nice to have the device I legitimately bought working again!
Help
My LG V10 is missing the USB port. Is there an alternative way?
Lrrrrr said:
My LG V10 is missing the USB port. Is there an alternative way?
Click to expand...
Click to collapse
If your V10 is running the 30C version of Nougat I have not found another working method. With other versions of Android there may be more choices.
Sent from my LG-H901 using XDA Labs
Mine is actually running version 30B
NYLimited said:
Factory Reset Protection (FRP) is a security method that was designed to make sure someone can't just wipe and factory reset your phone if you've lost it or it was stolen. Starting with Android Lollipop, FRP is "standard" in vanilla Android, and most companies making our phones have implemented it in their own models. It's a good thing — it makes a stolen phone harder to use, which makes it less appealing to thieves, and anything that can protect our data on a phone we've lost is welcome.
The problem is that people are selling or trading or even giving away phones with FRP enabled and this makes things difficult for the next user.
I found myself in this predicament recently having purchased a used LG V10 and, being in a rush, I flashed a factory KDZ on the device. Needless to say, I could do nothing with the phone once I rebooted - I was stuck on the proverbial "Verify your account" prompt.
If you reset a phone with FRP enabled, you have to provide the user name and password for the last Google account that was registered with the device. There are tons of random work-arounds on the Internet, but they tend to get patched almost as soon as they are discovered. You'll pretty much need to know the login details for the last account to use the phone before you can do anything with it if FRP was enabled before you reset it.
A quick XDA search turns up some 13000+ hits pertaining to "frp v10 verify account" and it takes time to try them all. The truth is that most were exploits geared for Android versions prior to Nougat and, even those which claimed to fix the problem for Android 7 no longer worked due to changes LG likely made between the 30B and 30C updates.
To make a long story short I finally found one method that worked. I got the device back and fully functional. Although I have only tried this on the 901H (T-Mobile variant) it may well work on any V10 running LG's version of Nougat (30C). If you try it and it fails or works you should let people know which variant and how you made out.
The solution for the V10 devices is documented in this video.
The ADB command line used is in the comments of the video but for ease of use this is it:
If you have another method that you have tried and know works on this specific device, by all means, do tell.
It is nice to have the device I legitimately bought working again!
Click to expand...
Click to collapse
I grp bypassed my verizon lg g7 thinq through an exploit using wifi with a dead sim card. I basically found a way through youtube and google settings and i never once used any kind of downloaded app. Im on 9.0 pie. This was acheived about 15 minutes ago. It took 5 days to get it. But if you get at me tomorrow I will share what I did through step bu step instructions.
GkHammer said:
I grp bypassed my verizon lg g7 thinq through an exploit using wifi with a dead sim card. I basically found a way through youtube and google settings and i never once used any kind of downloaded app. Im on 9.0 pie. This was acheived about 15 minutes ago. It took 5 days to get it. But if you get at me tomorrow I will share what I did through step bu step instructions.
Click to expand...
Click to collapse
tooo bad you wil likely never see this - as im VERY curious as to whats up with a dead sim somehow allowing a frp bypass!!
Related
it appears after the new APC5 update the Apn settings are greyed out EVEN with the MSL code
FYI
its also appeared to break many working features of the s7 edge . on he phone with sprint now returning the phone for a new one without the update. it literally breaks at least 5 things so far and ruins the signal also
Do NOT accept the update or your going to have constant problems and alot of features will be broken
samsung is in the process of pulling it.
I repeat DO NOT take the apc5 update. youve been warned
Read this Post also http://forum.xda-developers.com/showpost.php?p=66141237&postcount=20
Robalboa said:
it appears after the new APC5 update the Apn settings are greyed out EVEN with the MSL code
FYI
its also appeared to break many working features of the s7 edge . on he phone with sprint now returning the phone for a new one without the update. it literally breaks at least 5 things so far and ruins the signal also
Click to expand...
Click to collapse
Can anyone else confirm that this update breaks the MSL Hotspot mod?
Also, any changes to the bootloader in this update?
use your msl and try and go into apns . they are all greyed out sprint advanced tech cant even access them. it breaks smart lock. youll have to reset wifi and bluetooth settings every couple of reboots. sprint has had 1300 calls today about it.
Robalboa said:
use your msl and try and go into apns . they are all greyed out sprint advanced tech cant even access them. it breaks smart lock. youll have to reset wifi and bluetooth settings every couple of reboots. sprint has had 1300 calls today about it.
Click to expand...
Click to collapse
I mean, I appreciate the warning, but I turned off auto OTA updates for a reason. I don't want to possibly lose the ability to unlock my bootloader. Thanks for your unintentional research and I'm sorry for your loss of ability with your device. Good luck in getting a new one.
I can confirm this. Got a new phone for a second line on my account today. Update notification popped up, accepted it and went to modify the APN settings when it was finished and they are all greyed out now. Fortunately had not updated my phone yet, but this new one is going back.
I updated my phone yesterday my APN is greyed out but hotspot mod still works. The issue I'm having is my data is slower than before.
so does it or does it not break hotspot mod??? has this update actually been pulled? i have not received the update notification on any of my s7 edges.
I don't use the hotspot mod and installed the update. Haven't noticed any issues, but what else is it breaking for you guys?
My hotspot works, I did the whole add dun in the apn when I first got my phone on the 8th. I used it today at work with no problems.
Update is fine. Yes, the update will screw stuff up if you modded your phone off stock.
Sent from my SM-G935P using Tapatalk
After applying the update this morning, the battery drain rate has increased drastically. The phone has been rebooted a few times. Hopefully, it'll get better in the next couple days.
Sent from my SM-G935P using Tapatalk
I just got done downloading it but haven't installed it yet. I don't really care about the hot spot that much, can you be more specific on what other things it breaks? Did you run the update with having package disabler enabled? Patching the hot spot mod I'm sure was on the top of there list. I just checked for my update and it was still live. Usually my rule is to hard reset after system updates. If sprint wanted to pull it, I would have thought they would have done that by now.
I don't know how much credibility there is for anything that guy said aside from the hotspot issue. Haven't seen anyone else confirm it.
My battery seemed to drain faster after the update, but that could just be a result of the battery stats being reset as a part of the update - I will post back if things settle down after a while. I don't use smart lock, so can't confirm that.
Sent from my SM-G935P using Tapatalk
Similar to pitcherj above... battery *appears* to be draining quicker, but i've also now read 2 pages of placebo effect on that so we'll see as time moves on if that's real or imagined. never used the hotspot mod (got a work phone with that function already paid for) and also no smart lock usage.
So, other than possible battery concerns, no issues to report so far, and I can't see any apparent changes on the front end yet.
Both mine seem to have worse battery life after update
I performed a factory reset & set up the phone from scratch. Still getting ****ty battery life. What a friggin fail by Sprint & Samsung.
Sent from my SM-G935P using Tapatalk
optimummind said:
I performed a factory reset & set up the phone from scratch. Still getting ****ty battery life. What a friggin fail by Sprint & Samsung.
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
Have to agree. Beautiful phone but barely lasting to the day. Was so excited about the huge battery but can't even use it to listen to music at work or it will die. Bought it so i wouldn't have to worry about charging all the time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's what today looked like.
Couple of small topoffs but less than a day here.
Screen time 2h56m.
Will have to see how it does over time.
Sent from my SM-G935P using Tapatalk
LISTEN CLEARLY for you guys who took the update and still have a working hotspot. if or when your PRL or profile udpate it WILL ERASE YOUR APNS AND RESET THEM TO DEFAULT AAAANNNNDD LOCK THEM SO THEY ARE INACCESSIBLE.
its only a matter of time for you now at some point it will update and your hotspot will be gone. i can Confirm i did it myself .
i have a new one now i didnt connect to wifi when first turning it on so in the initial startup it wouldnt update
then i turned of the updates and all is well. if you already accepted ACP5 update your doomed sooner or later.
just DO NOT update prl or Profile or its gone for ever
Sorry if I posted this thread in the wrong place, but after searching here and there, the only place appropriate for my thread seems like in here. If I posted in the wrong place feel free to delete my thread or to move my thread to the right sub-forum. Sorry if this feels like I'm ranting or complaining, but this issue of mine just seems so cruel, evil, and unfair, especially done by such a big brand like Xiaomi.
So here's the deal, I bought a Xiaomi Redmi 5A (2GB RAM and 16GB's of storage) in mid of January. I bought the 5A because it had great specs even with it's low price and it's because my current daily driver can't handle the latest of what Android offers (I was using an ASUS Zenfone 5 with an Intel Chipset, very fast battery drainage, low compatibility with latest apps, and very poor signal reception plus dying support on XDA).
I bought my 5A online from a Official Store, but it was manufactured in my country (Indonesia) that was under a certain brand of smartphone warranties (TAM). I checked the device via Mi-Verify and the results showed up seeing my 5A is an official device supported by Xiaomi.
When the device was in my hands I proceeded to try to unlock it's bootloader, so I can gain root access and start restoring right away every Titanium Backup backup I had so I can use the 5A as my daily driver. I logged in to my Mi-Account and because my account had already been approved of Mi bootloader unlocking since 2016. I thought everything would turn out smooth, I expected that I had to wait for 72 hours or something (which I didn't mind about and was willing to patiently wait for). I proceeded to enable Developer Settings (in which is required to be able to bind my account to the device and unlock it using Mi-Unlock Status). I turned on USB debug & OEM unlock then I proceeded to get permission (bind Mi-Account) from Mi-Unlock status. This is were things went downhill.
First, it showed me an error code 10008 (in which could be fixed by using a Chinese based VPN server), then after using a VPN, it showed me another error code which is now my current nightmare: code 86023 hardwareId abnormal (<- originally Chinese fonts which I translated via google translate). I started searching for guides here and there to fix this issue with no luck at all. I tried every guide out there and even destroyed my warranty in process (I had to open the back case and use the test point methods) because I was followed a guide that said I had to flash via QFIL/Mi-Flash a China Developers ROM to be able to unlock my bootloader (which didn't change a thing, it still failed to unlock and still showed those 2 error codes: 10008 & 86023).
I even posted a thread in MIUI forums about error code 86023 in the complaints/advice sub-forum (in which now has the highest views and replies), and was surprised to see that I wasn't the only one with this UBL issue. It affected lots of Xiaomi devices that were manufactured or distributed in the near end of 2017 and early 2018 (especially Asia-Pacific devices). I faced a dead end and was hoping that it'll get fixed in a month.
After waiting for a month or more, it didn't get fixed at all. The only thing that was fixed was error code 10008 (Now it doesn't require a bypass via VPN) but the error code 86023 persisted. I got totally frustrated and tried contacting customer service via online chat and via email. First I tried online chat, and they suggested me to go to a local authorized service center to ask for bootloader unlocking. When I arrived to one of those shops, I was surprised that they said that they don't accept UBL pleas, they say that the user has to do it by their own consent (which pissed me off because I told them my situation and they still refused to help me). Then I emailed my country's customer service ([email protected]). I had 2 sessions of replies in which first they told me that UBL has been disabled by Xiaomi because they fear my device would be vulnerable to virus attacks (SERIOUSLY!?). I told them that I understand the risks of UBL and asked for a better and decent explanation on why UBL has been disabled. Then I received this reply:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Kami mohon maaf atas kendala dan ketidaknyamanan yang Bapak Ezra alami. Terkait kendala yang terjadi, perihal kebijakan bahwa Unlock Bootloader sudah ditiadakan merupakan wewenang dari pihak Xiaomi Pusat yang berada di Cina."
This translates to:
"We are sorry for these issues and inconveniences that Mr. Ezra has experienced. Regarding to the problems that have occurred, the Unlock Bootloader policy has been removed and it is under the authority of Xiaomi's central headquarters that is in China."
After reading this, I was dumbfounded, totally dumbfounded. I nearly went ballistic. I was super pissed off and disappointed.
So from what I read, it seems like devices for my country, or maybe all of Asia Pacific has been totally locked out of UBL. So now I have no idea on how to unlock my Redmi 5A.
I did read UA of Xiaomi and found that they have total rights on removing a feature of some sort (read Xiaomi's User Agreement):
"The user accepts that in relation to business development, we may change, suspend, restrict, terminate or revoke the rights of our services at any time without notice;"
I understand this very much, but why did they have to terminate UBL? I thought Xiaomi supported developement and modding. But how did it come to this?
Please give me your opinions about this absurdness that Xiaomi has thrown to me and many other users out there.
Thanks.
I recently bought a pixel 2 XL for cheap on ebay, turns out it is FRP locked. I was looking for a bypass and they all seem to be patched. E.g. Talkback, maps, magnification. While digging I was able to get to the internet in a limited capacity. The google keyboard allows you to search for gifs and I was able open a tenor gif which had the a link to see more gifs which led me to a website. Ill link pictures. I was able to navigate from there to facebook and then to youtube and the rest of the internet by logging into facebook and messaging myself or posting links privately on my wall. What I could not do was launch other apps or download anything. Anyways this is what I've manage so far, hopefully someone can finish what I have started.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pics link
https://imgur.com/a/hoLNPwN
code9523 said:
FRP is not a solution to protect stolen phone from use as it is bypassable. There should be an option in google account to full dissable phone to prevent it even turn on.
Click to expand...
Click to collapse
open an issue for this on google's issue tracker and lets see what response you get.
Moderator Information: Some posts are removed. Please remember our rules while posting. Thanks.
Any Luck
I am on the same boat. Talkback 7.0
i have successfully bypass frp on pixel 2 xl android 9.
adna said:
i have successfully bypass frp on pixel 2 xl android 9.
Click to expand...
Click to collapse
That's kinda not helpful at all. The way it works is you post your method and anyone who accidentally locked their own device can unlock it. Naturally, this is not useful for blacklisted IMEIs in the US.
so sad to see no updates on this thread, I've had this stupid pixel for months now while my gfs phone continues to detoriate, and I'm really hoping someone discovers a new method soon. I don't trust the guy who posted that and then disappeared when he was essentially asked to prove it lol
Search YouTube: Android 9 FRP bypass.
kelarys said:
so sad to see no updates on this thread, I've had this stupid pixel for months now while my gfs phone continues to detoriate, and I'm really hoping someone discovers a new method soon. I don't trust the guy who posted that and then disappeared when he was essentially asked to prove it lol
Click to expand...
Click to collapse
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.
computerslayer said:
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.
Click to expand...
Click to collapse
We have to give benefit of the doubt. But I agree with you entirely.
Sent from my [device_name] using XDA-Developers Legacy app
I’m not able to find a true working frp bypass. I don’t get a search icons to bypass like all the videos show for android P. And the helo&feedback button doesn’t take you anywhere. So I’m guessing Verizon blocked it in the last patch
The only way to fix this is to send it back to the seller. Ask for a refund.
No news?
try this new video youtu.be/WS1RFEiFMM8
hakkuba said:
try this new video youtu.be/WS1RFEiFMM8
Click to expand...
Click to collapse
Thanks a bunch! This worked.
computerslayer said:
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.
Click to expand...
Click to collapse
I just discovered a new way.I dont know if itll work but.....
https://forum.xda-developers.com/pixel-c/help/pixel-c-8-1-1-frp-bypass-t3879498
Factory Reset Protection is Annoying, Get Rid of it!!!
I purchased a Google Pixel 2 Certified Refurbished on Amazon and I have this issue as well. If anyone has a solution I suggest they post it...party to theft or not, **** happens and I hate when device vendors install crap like this claiming it's to prevent theft....it's to boost sales, period. Fortunately I can get a refund or replacement but its a bleeping waist of time having to mail in my phone and wait for another phone be sent to me.
IMO this factory reset protection hurts more legitimate users than it protects. It create brick/useless devices that is a waist of resources just so companies can make more $ . . . If you lose your phone, track it down, get insurance and/or consider it a loss. If I irreversibly lost my phone I would not harbor some BS attachment to it...Ideally I would like it returned but alternatively I'd prefer someone else make use of it than create more waist.
Please search Change dot org for my petition for Google to remove FRP
I got a Pixel 2 XL with Android 10. How can i bypass the FRP ?
Hello everyone,
I bought this phone on sale last year and it was advertised as follows...
Refurbished: LG G Flex2 H950 32GB Unlocked GSM 4G LTE Octa-Core Android Phone
In browsing the forums here I see the excitement around this phone has waned quite a bit since it's release, but I'm hoping there's still a few of you left who might be able to help me. I totally love this phone and want to be able to use its full potential.
It's branded as an AT&T phone when the boot-up screen appears. I doubt it was sold as unlocked by AT&T, but rather Newegg, or someone they're reselling for, unlocked it. I've never been an AT&T customer. I bought it knowing I could use any carrier willing to sell me a sim card. I'm currently using Mint.
It came with the 5.01 firmware. I've spent many days reading every thread I can about how to upgrade it, and possibly get Marshmellow as well. The issue is that I can't seem to find any drivers that function properly. Here are all the ones I've tried...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only one that's come close to fully functional is the top one for version 3.11.3.0 It's the only one that recognizes all of the sub-devices no matter how many times I unplug the USB cable and plug it back in. The only other one that came close was version 4.2.0
I use a program called USBDeview, which provides live monitoring of USB connections and shows a great deal of info about each one. In the images I'm going to share, I've shrunk away all of the columns except the ones I think are most relevant. The ones with Green dots mean it sees them as a working, connected device. The ones with Gray dots mean that there is a record of this device connecting, but that it does not see them as currently connected. And the Purple dots mean it sees the device as connected, but that there is some issue with its functionality.
Here's the result when I use the 3.11.3.0 driver...
All 5 devices show green and everything action I've tried to perform from studying guides here works perfectly. And, as I said, it keeps working no matter how often I reconnect it. The only weird thing is that USBDeview reports the version as 3.11.0.0, even as the filename and the file properties report it as 3.11.3.0 It reports correctly for all the other drivers I've tried, but I guess it's nothing to complain about at this point.
The problem is that whenever I put the phone in “Firmware Update/Download Mode” I get this result...
The LGE Mobile Sooner Single ADB Interface driver now shows as disconnected, and as such, I can't send any ADB commands and my device doesn't show up on the list when I type "ADB Devices". It doesn't indicate there is a problem, it just shows it as not there. This issue is thwarting all my efforts to upgrade the phone.
With the 4.2.0.0 driver, I get a similar, but slightly different result. Sometimes I got this when connecting the phone in normal mode...
And other times I got this...
I can't account for the different results because I was trying all kinds of tweaks and fixes between different attempts. But one thing was universal with this version: They would all show green for up to a minute or so and then all but one would start disconnecting until it looked something like this...
The other drivers I tried were similar. Some recognized more devices, some less, and some would look like the above on their first use. Some were consistent and some would look okay for a minute and then disconnect.
When it came to Download Mode, some would see the ADB driver and some would see the USB driver, but I still haven't found one that will see both. When I check the error logs, I most often see something like this...
So if anyone has a driver that they know works on this phone and has definitely used it to upgrade this model in Download mode, please let me know.
Also, if you know of a method to accomplish my goal without using Download mode, please point me to some steps to that method.
Just to avoid the obvious advice, I've tried a great many fixes...
Turned off Fast Startup.
Disabled ability to turn off device for power savings on all USB hubs.
Disabled USB Selective Suspend.
Disabled firewall and all other protection settings in Windows Defender.
Uninstalled my anti-virus.
Disabled Windows automatic device updates in Group Policy.
Made sure all my other devices have the latest drivers.
Update my BIOS to the latest version.
Windows 10 Pro is up to date.
As one person advised, tried to manually update the devices that wouldn't connect using lgx64bus.inf from the driver folder.
And various registry tweaks.
Thanks in advance for any help.
NOTE: In going through all the drivers again, I discovered that version 3.14.1, at least on the surface, is performing exactly as ver 3.11.3 has been. Works perfectly in normal mode, missing ADB device in Download mode. Guess I skipped it in my first few runs. Still doesn't solve my problem, but I strive to be accurate.
NOTE 2: I have found a method for flashing that does not require ABD to flash my phone. I can't find an option to delete this post, so the moderator has my permission to do so at their discretion.
I have an unlocked Fold 2 from Samsung. I love the idea of rooting and having full access/control over a device I own, but it has been years since I rooted a phone. Recently my needs have changed and I find I am thinking about rooting again. Just curious if the below reasons are worth rooting and if rooting will even help or would I need to root and load a a custom rom?
1st I need to disable the 5g radio on my phone. I live and work in an area with poor 5g coverage, but have just enough that the phone can see it and try's to default to it and ends up providing far worse connectivity than the LTE that is steller in my area. AT&T is who I use and they have disabled this feature in their portion of the firmware. I can plug in a buddies T mobile sim and after reboot have access to the menu that allows me to pick LTE and my preferred connection type but not on AT&T.
2nd This is less of a concern as I have work arounds, but I would like to remove any and all carrier control of my device. In particular their ability to monitor and dictate how I use my data, i.e. wifi/BT/usb tethering. Like I said I have a work around but its fiddly.
3rd I would like to be able to run full weight cellular diagnostic tools on my phone as well as have full access to the USSD dialer codes.
Can these things be done after rooting and or loading a custom rom, in particular on the Fold 2? I have been searching for a bit, but can't seem to target my search to just this thread as I end up having to sort through a dozen other threads. I can work my way through rooting my phone and loading a rom, just curious which apps and or roms to look for once I have rooted. Any feedback would be much appreciated.
Ok how about this. Can anybody point me to a location that can help me figure out how to removed carrier specific configurations once rooted? I want to disable my 5g radio on my fold 2. This is something that can be done when it has a T Mobile sim, but not an AT&T sim.
Redtick said:
Ok how about this. Can anybody point me to a location that can help me figure out how to removed carrier specific configurations once rooted? I want to disable my 5g radio on my fold 2. This is something that can be done when it has a T Mobile sim, but not an AT&T sim.
Click to expand...
Click to collapse
You should google harder dude
You could just Flash an international firmware of an un-carrier branded software, they can be found here - https://www.sammobile.com/samsung/galaxy-z-fold-2-5g/firmware/#SM-F916B
Try this app - ESET USSD Control : https://play.google.com/store/apps/details?id=com.eset.securedialer&hl=en&gl=US
Disable 5G radio :
Settings -> Connections -> Mobile Networks : Change the network mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry about the googling... Could only find and confirm that it was locked on att phones. As I have an unlocked variant I was not sure why I was having that problem. Thanks for the tip on F916B I did not know I could load that on the F916U1, I will look more into that. But again I thought the F916U1 from Samsung was unbranded.
Thanks for the software link.
Redtick said:
I have an unlocked Fold 2 from Samsung. I love the idea of rooting and having full access/control over a device I own, but it has been years since I rooted a phone. Recently my needs have changed and I find I am thinking about rooting again. Just curious if the below reasons are worth rooting and if rooting will even help or would I need to root and load a a custom rom?
Click to expand...
Click to collapse
I have been an XDA Forums member for about 10 years and have enjoyed countless custom ROM on dozens of devices ... here is my opinion ...
In 2020 there is ZERO point in rooting a phone. Full stop. The end.
Edit: no point whilst the manufacturer is still providing software updates & support
Fair point... Is there a means by which I can manual control the radios in my phone without rooting? For example sending custom crafted AT commands to the radio to do things like IMSI masking, band switching, and most importantly band aggregation commands.
dezborders said:
I have been an XDA Forums member for about 10 years and have enjoyed countless custom ROM on dozens of devices ... here is my opinion ...
In 2020 there is ZERO point in rooting a phone. Full stop. The end.
Edit: no point whilst the manufacturer is still providing software updates & support
Click to expand...
Click to collapse
i am sorry but as I upgraded OS I encounter more and more issues in termux most of good things require root now IMO its on the contrary more needed to root your device
BeRkCaN said:
i am sorry but as I upgraded OS I encounter more and more issues in termux most of good things require root now IMO its on the contrary more needed to root your device
Click to expand...
Click to collapse
Everyone's mileage may vary but I stand by what is said ... For me, I see ZERO need to root on Samsung android 10 or 11
If you had asked me a few years back, what I would do with a brand new android phone out of the box and I would have said "root". I think the last phone I rooted was note 8, out of habit and that voided my warranty and I didn't gain anything in return... almost everything I used to do, can be done without root. Ad blocking via disconnect pro and netguard, to disable apps, use ccswe (as long as knox licence isn't revoked), youtube vanced to fine tune adfree youtube, naptime for putting device to quick deep sleeps, side actions to configure power button behaviour etc... these were probably the things I could have only achieved with root earlier.
I personally rooted my Samsung Fold 2 just so I can degoogle it. I cant stand big tech so for me it was worth doing