Related
Hello,
I new here, i'm from germay, and i only found a way for unlocking USA Phones.
Now my question is if anyone knows a way hot to unlock my phone which is from germany and also locked on german t-mobile.
Sorry if there was this question before but i havnt found it.
Merry Christmas! tollmar
Afaik the german g1 do not have a Netlock or Simlock, only the austrian have. I rooted my german g1 with a goldcard.
yes,yes,bastards is right, you need a goldcard and root our germany G1 canbe very easy , do it ,you can
My german G1 never had a Netlock. Are you sure that your one really have it?
And the first Android Devices released here in Austria also never had a Netlock, the G1 and the Magic (at least the Vodafone ones).
Well i mean the Austria one But t-mobile austria and german is the same
SO anyone got an idea?
I tried to unlock it with a code i get from a site. But it havnt worked..
Now there is not any longer the screen where i can enter the code..
Is it normal that after 1 fals entering i cant enter it anymore ?
When i Start the phone now, i just see the screen to log in google account, but cause the handy is not unlocked i dont get connection to it.
What shall i do?
Which release are you on? On 1.5 or 1.6 you could just skip it for now and use wifi later, after activating it in the settings. If it's older you have to search the forums, I've seen a few threads about that.
Well the its the fact, that the phone isnt UNLOCKED... I asked at HTC and they ment if the phone isnt Unlocked i cant logged in Google!
The best solution
I performed this procedure during rooting my G1 without a T-Mobile data plan. I don't remember who published this info so I can't give credit where it's due. I found a root kit along with specific instructions here: http://forums.t-mobile.com/t5/Opera...oot-G1-even-if-it-has-1-6-android/td-p/237395. Once you downgrade then upgrade to 1.5 or cupcake, you are within the 'security hole' to root you G1. In order to proceed from this point, you must have a data plan or follow this procedure to enable wifi and log into google. Also, this process works without a sims card. Here goes.
Activate Stock G1 over WiFi
I've seen a few guides around the internet in regards to activating a G1 over wifi without a data package, and decided to test it myself. Since it worked, I'm compiling the information that I've gathered into one easy-to-read thread.
Standard disclaimer:
Bricked phones, not my fault.
The Setup
1x Stock G1 running cupcake, this phone has no root modifications on it.
1x USB cable
1x SD card, at least 128MB
The image file to downgrade to version RC29 of Android, download here
ADB for your computer:
Linux Download
Mac Download
Windows Download
Windows Only:
Windows Drivers for Android (XP only)
--End Setup--
1. Ensure that your SD card is formated FAT32, and place the DREAIMG.nbh, that came out of the DREAIMG-RC29.zip file, in the root directory of the SD card. (No, DREAIMG is not a typo.)
2. With the phone off, insert the SD card into your G1.
3. While holding down the camera button, turn on the phone.
3a. You should see a rainbow screen, followed almost immediately by a gray screen. (mileage and colors may vary)
3b. One of the lines on the phone should read: "Press power button to start update image".
3c. Press the power button
3d. Wait for the entire process to complete, do not interrupt! It will tell you it is done updating.
4. Reboot phone.
Download the appropriate ADB file for your system, if you're on a Windurrs machine you'll need to download and install the Android drivers as well.
Ok, we're done rolling back to RC29; and we have access to the 'sploit which gives us terminal access without seeing the terminal.
Until I tell you to later on, do not touch the screen for any reason. During the rollback process the screen has turned into hot lava and will burn your hand if you touch it. If you can't resist, and touch the screen not only will you be sans one digit but you get to reboot your phone and start over.
You should now be at this screen:
<pic>
5. Hit <enter>, type "reboot"(no quotes), and hit enter again.
5a. If all went well your phone just rebooted, yay good thing!
6. We're back to the last screen.
7. Plug your phone into your computer using your USB cable.
8. If you mistype this step or it doesn't work(because you mistyped), you'll need to reboot your phone and try, try again.
9. Hit <enter>, type "setprop persist.service.adb.enable 1"(no quotes), hit <enter>
9b. If all went well you should get an error message saying something like "cannot dial 7387767 7377478.7378423.232.362253 1, it's not an emergency number. This is a good thing, we hope.
10. Set your phone down.
11. Open a terminal on your computer, and navigate to the folder containing the adb file you downloaded earlier.
edit: First cd 'drag and drop the folder Tools into the terminal window. I will copy the proper directory path.
12. If all is well, you should be able to type "adb" and get a big screen of options.
13. Type "adb devices".
13a. You should see the following: <pic>
13b. If all you see is "list of devices attached", and nothing below it, reboot your phone and move back to step 8.
13c. type "adb shell" (no quotes)
14. Copy and paste "am start -a android.intent.action.MAIN -n com.android.settings/.Settings" into your terminal.(no quotes)
15. If your copy+paste-fu is strong, you'll see this screen: <pic>
At this point you're in. You will see the 'Settings' window allowing you to set up wifi, and connect to google data and hence the internet.
Regards, davidrol
Obviously, my g1 was unlocked, after my first attempt.
After entering he APN data i got from my provider and reading further newbie hints on the modmygphone forum i could create a g-mail account and us the phone! with my own provider!! I didnt get it mate to root the phone but i always got a massage "not allow".
Very big thx for ur help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Greetings Marc!
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
knotabs loca
manyelski said:
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
Click to expand...
Click to collapse
I'm in a similar situation. I was asked to use latest CWM. I happened to use Tenfar's CWM that came with the boot loader unlock.
I haven't tried it yet. Will give a shot this weekend
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
I can't turn on my phone, or DO ANYTHING with it, the only thing is that I get "M" screnn taht's all, if i want to turn it down I hae to do a battery poll.
Excactly, that's what Early Enumeration is for Usually, USB is loaded when the OS is up, I suppose - at least you can't normally connect with ADB during boot. However, with Early Enumeration set, you can connect while the phone is still booting and access every capability ADB or the shell is able to provide. (Granted, uninstalling the .apk in question with adb uninstall did not work for me, that's why I posted the manual approach, but that may have been an error on my side.)
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
JeRrYFaR said:
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
Click to expand...
Click to collapse
Mine is tha same
Stuck in mortorola unlocked boot screen
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
How do you find the device's IP address?
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
Hi All,
I have Note 4 AT&T vwrsion and i am currently using beta version of MM.
When i jumoed to MM the spell check was working but after a while it just stoped working and i am trying to turn it back on but no luck so far.
I have found this article explaning the steps to turn on the "Auto Spell Check" but unfortunatily this button do not exist in my phone. http://inside-galaxy.blogspot.com/2016/03/samsung-galaxy-s6-edge-how-to-enable_22.html?m=1
Can any one plz help, Thanks in advance.
P.S: i tried at&t thread, no one seams to reply there
Attached is screenshot of my keyboard settings.
Got it fixed via adb command.
- turn on developer options
- turn on usb debugging
- on your PC downlolad and install minimal adb and fastboot ( http://forum.xda-developers.com/show....php?t=2317790 )
- connect your device via usb to your PC, wait 2 minutes until adb drivers have been installed
- run the installed adb link in your start menu, a cmd window opens op
- enter: adb shell
- enter: settings put secure spell_checker_enabled 1
- close cmd, disconnect phone, spell checking is enabled
See Post #2
This was not generated for thieves or hackers. I agree entirely that security is important but there are many of us in the world who just slip up and do dumb stuff on occasion. Locking oneself out of their own device is more common than you'd expect.
This write-up may seem a bit complex but is actually pretty easy. The only steps that were originated by myself are using the headphone jack and using menu code to enable debugging. Everything else was built on other people's work, in which the origins can be found all over youtube and other websites. No idea who came up with it first. I give credit where i can find it. As well, if you jack up your phone during any misadventures, I am not responsible.
What you need: PC, device USB drivers, USB cord, and of course the device to unlock.
This pertains to the LG G6 T-mobile model # with software version was H87210e_00_0322 (March 2017 patch).
Once on the startup screen (Google Setup Wizard) , sign into wifi, progress to the Google sign in screen, then page back to the wifi screen. Click onto whichever name you are not signed onto as if to fill out password, don’t. Once the keyboard is up, click on settings icon in keyboard. See below for a diagram of sorts.
Settings >General>Smart Settings>Earphone [set app to settings {phone}]
Plug into headphone jack and phone dialer pops up.
3. Dial *#546368#*872# (Field Test Mode). Go to SVC>LDB> Enable usb debugging
Back out to primary GUI phone screen and reboot. Once rebooted leave alone.
4. Plug phone into PC and start adb terminal. If you do not already have ADB, Google it.
Insure your usb drivers for your computer are up to date.
At terminal prompt type > ADB devices, make sure your device is recognized.
5. From the guide linked below enter the following command.
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind
value:s:1
This will clear the setup wizard.
6. REBOOT and send thanks!
Links
http://www.gsmplayer.com/frp-via-adb-command/
my crappy web page
https://raff1ut.wixsite.com/otgg
NOTE: *#546368#*872# 872 designates the T-Mobile device model number, if coming from another carrier be sure to enter your particular model number instead of 872.
lg g6
i get and error unsupported argument please help
Will this work for other devices like pixel xl
THANKS!!
Hey,
I just wanted to say thanks for helping me get back into my phone. One thing: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete -- * * * * * * *bind value:s:1"
Is what you have listed on your site as the command. This has a formatting error and should read: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete --bind value:s:1"
Was this intentional?
Thanks again!
rlang85 said:
Hey,
I just wanted to say thanks for helping me get back into my phone. One thing: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete -- * * * * * * *bind value:s:1"
Is what you have listed on your site as the command. This has a formatting error and should read: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete --bind value:s:1"
Was this intentional?
Thanks again!
Click to expand...
Click to collapse
First, sorry it took me this long to see this reply. Seems to be a thing with app notifications on my phone, didn't see any until I signed onto a computer. Anyway, you're referring to an external link within the OTGG site and what I see within it is as follows "adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1" Unless it was fixed prior to my revisit it appears to be the same as what you've posted.
* EDIT: On looking again, I see in fact that you are referring to the OTGG text. I do believe that would be considered a typo or furthermore a format issue ... ha. Thanks!
ksuhiyp said:
Will this work for other devices like pixel xl
Click to expand...
Click to collapse
Doubtful, but you can always tinker and try.
bracebg said:
i get and error unsupported argument please help
Click to expand...
Click to collapse
First, apologies for taking so long to see this. Hopefully you have it figured out by now. For future reference; it might help to be more descriptive into the steps or process you were at when the error message occurred as I, obviously didn't run into that issue. Also, it could be that this little hole was patched.
hi i have the lg g6 h872 and i id exactly as instructed but i cant get the phone dialer to come up please help
melie323 said:
hi i have the lg g6 h872 and i id exactly as instructed but i cant get the phone dialer to come up please help
Click to expand...
Click to collapse
Apologies for just seeing this, I'm not getting notifications for some reason. All I can recommend is to retry all the steps. Also, your phone may have been patched/updated since this write-up. I don't have the G6 anymore so I can't replicate the error you're getting. Not getting phone dialer up doesn't give me much to go on with just my memory.
Debugging shaded
Hello
I went through all the steps and the USB debugging is shaded grey??????? PLEASE HELP FAST!!!
The debugging option on my G6 is grayed out as well. Does anyone know of any other options that might currently be working?
rlang85 said:
Hey,
I just wanted to say thanks for helping me get back into my phone. One thing: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete -- * * * * * * *bind value:s:1"
Is what you have listed on your site as the command. This has a formatting error and should read: "adb shell content insert --uri *content://settings/secure --bind name:s:user_setup_complete --bind value:s:1"
Was this intentional?
Thanks again!
Click to expand...
Click to collapse
Better yet, use the command:
adb shell settings put secure user_setup_complete 1
Aimless Rambler said:
This was not generated for thieves or hackers. I agree entirely that security is important but there are many of us in the world who just slip up and do dumb stuff on occasion. Locking oneself out of their own device is more common than you'd expect.
This write-up may seem a bit complex but is actually pretty easy. The only steps that were originated by myself are using the headphone jack and using menu code to enable debugging. Everything else was built on other people's work, in which the origins can be found all over youtube and other websites. No idea who came up with it first. I give credit where i can find it. As well, if you jack up your phone during any misadventures, I am not responsible.
What you need: PC, device USB drivers, USB cord, and of course the device to unlock.
This pertains to the LG G6 T-mobile model # with software version was H87210e_00_0322 (March 2017 patch).
Once on the startup screen (Google Setup Wizard) , sign into wifi, progress to the Google sign in screen, then page back to the wifi screen. Click onto whichever name you are not signed onto as if to fill out password, don’t. Once the keyboard is up, click on settings icon in keyboard. See below for a diagram of sorts.
Settings >General>Smart Settings>Earphone [set app to settings {phone}]
Plug into headphone jack and phone dialer pops up.
3. Dial *#546368#*872# (Field Test Mode). Go to SVC>LDB> Enable usb debugging
Back out to primary GUI phone screen and reboot. Once rebooted leave alone.
4. Plug phone into PC and start adb terminal. If you do not already have ADB, Google it.
Insure your usb drivers for your computer are up to date.
At terminal prompt type > ADB devices, make sure your device is recognized.
5. From the guide linked below enter the following command.
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind
value:s:1
This will clear the setup wizard.
6. REBOOT and send thanks!
Links
http://www.gsmplayer.com/frp-via-adb-command/
my crappy web page
https://raff1ut.wixsite.com/otgg
NOTE: *#546368#*872# 872 designates the T-Mobile device model number, if coming from another carrier be sure to enter your particular model number instead of 872.
Click to expand...
Click to collapse
I am sorry but that partially worked for me. I just bypassed the frp on LG G4 | android version 6.0 | security patch 2016-09-01 and unfortunately none of the tutorials completely solved it. This is my method.
- First connect the phone to wifi.
- Select an other wifi or "add wifi" just so you can type some text. Select the text, press the tree dots for extra options and click on "Assist", if that does nothing at first click, click it one more time. That will open google. From here we can open any application we want.
- Type phone and at the very bottom of the results the "Phone" application will be listed, click it to open it. After that type on the dialer the following string: *#546368#*811# (Note: The last 3 numbers correspond to your lg model, you can find the model by removing the battery on the sticker. Mine was LG-H811 [T-Mobile]. That will open the "Hidden Menu".
- Navigate to SVC Menu > LDB where you will find an USB debugging option. Enable it.
- Restart device.
- Now you have adb access to your phone. Now you need a PC with any operating system but with adb installed. Also you need to download this 2 files, gam-6 and frp-login. Put them in a new folder. You can get adb from here. Connect the device to the computer and in the folder you created open an cmd prompt if in windows or a terminal if in linux or mac. Type the following commands on the terminal:
# adb devices (You will get a prompt on your phone to allow access. Allow it.)
# adb install -r gam-6.apk (Since we can not enable "Unknown Resources" we are going to use adb to install the apk we need.
The "-r" options is for overwriting the existing google account manager.)
# adb install frp-login.apk
- Now navigate to the wireless screen to once again open the google. Select an other wifi or "add wifi" just so you can type some text. Select the text, press the tree dots for extra options and click on "Assist", if that does nothing at first click, click it one more time. Type "FRP" and from the results select the application we installed "FRP Bypass". On the application click on the 3 dots located on the right top corner of the screen. Click on "Browser sign-in" and click on "OK". Now sign in with a valid google account.
- After you've signed in you will be brought back the the google screen. Restart your device and go through the steps as if your phone was never locked.
- Make an "Factory Reset" as a clean up.
- Done.
Note that this method is only tested on LG G4 android version 6.0. If you need help just reply.
KnownAsDon said:
I am sorry but that partially worked for me. I just bypassed the frp on LG G4 | android version 6.0 | security patch 2016-09-01 and unfortunately none of the tutorials completely solved it. This is my method.
- First connect the phone to wifi.
- Select an other wifi or "add wifi" just so you can type some text. Select the text, press the tree dots for extra options and click on "Assist", if that does nothing at first click, click it one more time. That will open google. From here we can open any application we want.
- Type phone and at the very bottom of the results the "Phone" application will be listed, click it to open it. After that type on the dialer the following string: *#546368#*811# (Note: The last 3 numbers correspond to your lg model, you can find the model by removing the battery on the sticker. Mine was LG-H811 [T-Mobile]. That will open the "Hidden Menu".
- Navigate to SVC Menu > LDB where you will find an USB debugging option. Enable it.
- Restart device.
- Now you have adb access to your phone. Now you need a PC with any operating system but with adb installed. Also you need to download this 2 files, gam-6 and frp-login. Put them in a new folder. You can get adb from here. Connect the device to the computer and in the folder you created open an cmd prompt if in windows or a terminal if in linux or mac. Type the following commands on the terminal:
# adb devices (You will get a prompt on your phone to allow access. Allow it.)
# adb install -r gam-6.apk (Since we can not enable "Unknown Resources" we are going to use adb to install the apk we need.
The "-r" options is for overwriting the existing google account manager.)
# adb install frp-login.apk
- Now navigate to the wireless screen to once again open the google. Select an other wifi or "add wifi" just so you can type some text. Select the text, press the tree dots for extra options and click on "Assist", if that does nothing at first click, click it one more time. Type "FRP" and from the results select the application we installed "FRP Bypass". On the application click on the 3 dots located on the right top corner of the screen. Click on "Browser sign-in" and click on "OK". Now sign in with a valid google account.
- After you've signed in you will be brought back the the google screen. Restart your device and go through the steps as if your phone was never locked.
- Make an "Factory Reset" as a clean up.
- Done.
Note that this method is only tested on LG G4 android version 6.0. If you need help just reply.
Click to expand...
Click to collapse
Nice, granted the post you're replying to was done for the G6 over 2 years ago (not G4) but information that might be handy nonetheless.
Aimless Rambler said:
Nice, granted the post you're replying to was done for the G6 over 2 years ago (not G4) but information that might be handy nonetheless.
Click to expand...
Click to collapse
Yeah, and granted that the phone was released 4 years ago you'd think there surely is a tutorial or post that will solve the problem but 2 hours of research didn't seem to be enough to find it. I think I could help someone and the reason I replied to this post it is the only one that kind of worked and was on the top results of G4 frp. Don't wanna be rude, just wanted to clarify some things.
KnownAsDon said:
Yeah, and granted that the phone was released 4 years ago you'd think there surely is a tutorial or post that will solve the problem but 2 hours of research didn't seem to be enough to find it. I think I could help someone and the reason I replied to this post it is the only one that kind of worked and was on the top results of G4 frp. Don't wanna be rude, just wanted to clarify some things.
Click to expand...
Click to collapse
No worries. I was sincere in saying handy information.
relock/unlock bootloader will erase frp. tested on stock 20g rom
I'm also facing the grayed USB debugging. Anyone found a solution ?