Related
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 am wondering around the internet to learn any method to disable MTP/PTP/all usb stuff except charging.
So, why i want this?
Because i want my device to be secure.
I don't anyone to sneak around and try to go into bootloader or recovery/connection to a pc etc to set my device to make a fresh start/copying data and end my privacy up.
So is there a way to disable those functions?
And if it is possible then what? Will it be secured?
And the big question is that can i enable it through recovery (from adb or moving mobile files) as you know if one has a messed up rom then he/she should have those functions workable.
.
@LGaljo?
@nik60?
@MAXSIMUS96?
@adityaupreti?
@Ciro?
@Renix63?
@sev3n1985?
delete mtpApplication.apk in syste/priv-app and in dev options..deflag debug usb
anyway ...not tried because i don't use pin in LS--but in S6 when phone is locked with pin is not recognized with PC
So will it disable the mobile to connect to a pc through bootloader?
I found this on a web:
.
The most device-compatible way to disable everything is to run this command at startup or set this in your build.prop:
Code:
setprop persist.sys.usb.config none
which is equivalent to charge-only on all Android devices.
That also disables adb. If you use adb regularly, then:
Code:
setprop persist.sys.usb.config adb
will allow adb when developer options are turned on/checked. If you don't use ADB often, I would not recommend it, because setting adb causes my S5 to still recognize in device manager, even when it is locked.
To restore original functionality,
Code:
setprop persist.sys.usb.config mtp,ptp,adb
allows all USB protocols.
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 ?
Phone is rooted, TWRP installed, (almost) everything is OK.
What is not OK is that now I cannt ADB connect. The "Allow USB debugging" window with the RSA key does not open at all.
Another thing I've noted - the "Revoke USB debugging authorizations" option in the Developer options - does not exist.
Any ideas as to how to solve this ?
I'm using linux (Arch, 64 bit). Another phone (an older, stock Moto G2) connect with ADB without any problem - so this is not a problem on the computer side, nor a USB cable problem.
Thanks.
Ben
Solved (almost).
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
ben-moto said:
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
Click to expand...
Click to collapse
+1 to this solution. I have a very similar problem on my HTC One M8. No prompt, also missing the "Revoke USB debugging authorizations" option.
Between this thread, a few others, and that same stackoverflow answer, I was able to come up with a couple of solutions:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
I'm experiencing this now, except I still have my "revoke USB auth" option under Dev Options.
I'll try the adb push method now...
I flashed both the latest 7.1.2 and 8.0 (Dp6) images on Nexus6p, but when system boot up there is no option for "jump the setup wizard" or "setup without wifi connection" something like that.
I also searched and there are some possible solution e.g. pushing a command line via adb as:
adb shell echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
but it doesn't help, are there any other solutions