Related
I have found a way to connect any modem to the tablet even if the tablet does not recognizes it. your device must be ROOTED to do so. I am not a developer, i just found out somewhere and modified the instructions to make it easy. i am not responsible to any thing that happens to your device (however this method isn't risky at all).
Just follow the instructions and enjoy. First download the attachment...
. First you need to move the modem to "modem only" for this you will need a terminal, you can use Hyper Terminal on windows.
Google search for AT commands for your modem to make it modem only mode and how to do that.
All right .... transferred the modem to the modem-only mode ....
Then note the vid and pid of your modem. one way to do this is to connect the modem to computer then go to device manager, expand modems, right click your modem >properties>details.
2. Next we need ES File Explorer
Install it on your tablet ... Open, go to settings -> Root rights, and tick all checkboxes.
3. Then go to /system/bin/preinstall.sh on your tablet and add a line to the file using es file explorer echo "19d2 1176" > /sys/bus/usb-serial/drivers/option1/new_id (see my preinstall.sh in the archive).
here 19d2 is my modem (vodafone K3370-z) vid and 1176 the pid. replace the vid and pid with your own.
REEBOT YOUR TABLET
4.There is a folder peers in the archive you downloaded. open conf-chat in the folder with es file explorer and replace your apn here with the apn of your service provider .
When the tablet does not recognize the modem it will not generate ttyUSB files which are needed to communicate with the modem. In Step 3 you made the tablet to recognize the modem and it now generates the ttyUSB files. You can check that in Terminal emulator(download from play store) by typing "dmesg" command(without qoutes). scroll the output down, you will see the generated ttyUSB ports as given in attached screenshot Pic1. It also gives the number of ports genetated. If you see these lines you can Connect your modem to Internet. But wait a minute you have additional things to do in order to get connected.
Now you need to find which port is pppd port because we need it to insert in the file Conf-pppd in peers folder of the archive you downloaded. (open the conf-pppd using wordpad you would see ttyUSB1 on the top because pppd port of my modem is 1, those modems who has pppd port at 1 would be able to connect without any modifications, if the pppd port of your modem is not 1 you would have to edit it e.g if the pppd port of your modem is 2, the top line in conf-pppd would look like ttyUSB2 and so on)
To determine which is pppd port follow the below steps...(see the attached screenshots)
Open 2 windows in terminal emulator. (you can copy paste the commands in terminal emulator)
(1) In first window type busybox tr -s "\n" < /dev/ttyUSBx (Pic2)
where x is the first port generated by your modem.(this command opens the port)
(2) Now in window 2 type echo -e "ATi\r" > /dev/ttyUSBx (pic3)
Here x is the same you typed in window 1.
You would see OK in WINDOW 1(Not in window 2). IF YOU DONT SEE ANY OUTPUT IN WINDOW 1(pic4), YOU HAVE TO UNPLUG YOUR MODEM AND PLUG IT AGAIN AND THEN USE NEXT PORT. yOU HAVE TO DO THIS EVERY TIME YOU DONT SEE ANY OUTPUT. IF YOU DO SEE AN OUTPUT PROCEED TO NEXT STEP.(pic 5, 6, and 7)
(3) Again type echo -e "AT+CGDCONT=1,\"IP\",\"www\"\r" > /dev/ttyUSBx in window 2. (Pic8)
Here replace www with your apn
You will see the OK again in window 1.(pic9)
(4) Again type echo -e "ATDT*99#\r" > /dev/ttyUSBx in WINDOW 2(pic10)
You will See the output in window 1. if you see ERROR in window 1, then it is your AT port not PPPD port. Unplug your modem and try next port untill you get CONNECT message in window 1(pic11). If you get Connect Message the at any port then it is your pppd port. IF you get these messages at port 2, then replace 1 in ttyUSB with 2, ehich then reads ttyUSB2 at the top of conf-pppd file.
Now copy the folder Peers in /etc/ppp/ in your sd card.
Install the application GScript_Mod.apk lies just in the archive .... open it and add the two scripts in the folder gscript of your sdcard : inet-ON.sh (Which brings up connection) and inet-OFF.sh (which disables the connection)
5. REBOOT TABLET. insert the modem. Start the application Gscript and run inet-ON.sh(pic12)
If you do everything on the instructions, your modem will connect to the Internet, although you will not see the 3G connection on the tablet...(pic13)
Thanks for reading..
Great Work..
A person who never made a mistake never tried anything new.
- Albert Einstein
Dear Bhaskar1109,
Kindly tell me how to use Hyper Terminal and make it a modem only mode. I have Micromax 310G modem with aircel connection and Micromax Funbook Infinity P275. I am unable to connect my modem as it says damaged sd card.
Thank You for your wonderful guide.
Micromax 310G..
manb7 said:
Dear Bhaskar1109,
Kindly tell me how to use Hyper Terminal and make it a modem only mode. I have Micromax 310G modem with aircel connection and Micromax Funbook Infinity P275. I am unable to connect my modem as it says damaged sd card.
Thank You for your wonderful guide.
Click to expand...
Click to collapse
Select COM port in HyperTerminal and try AT Commands.. i know AT commands to disable Emulated CDROM for few modems. Try it otherwise google commands for your modem
Huawei AT^U2DIAG=x command to control emulated CD-ROM and Micro-SD card
values of <x>:
0: disable CD-ROM and Micro-SD
1: enable CD-ROM only
255: enable CD-ROM and Micro-SD
256: enable Micro-SD only
ZTE AT+ZCDRUN=x command to control emulated CD-ROM and Micro-SD card
values of <x>:
8: disable autorun (modem appears when plugged in)
9: enable autorun (only CD-ROM appears when plugged in)
E: enable download mode (CD-ROM does not appear when plugged in)
F: disable download mode (CD-ROM appears when plugged in)
ZTE(ICERA chipsets) AT%USBMODEM?: to check the actual state
AT%USBMODEM=x command to control emulated CD-ROM and Micro-SD card
values of <x>
0: modem only mode
1: modem + CD-ROM + microSD
Great work.Usefull
Instructions added...
oops, i forgot some vital instructions earlier which i have added in bold letters now. Please view those if you were not able to connect to internet earlier and give your experiences.
great work, now i can connect any dongle to my tab. took some time though to make the dongle to modem only mode.
thanks.
Hi there,
I have checked the presence of ttyUSB into the /dev, but when I run the inet-ON I get.
Waiting ttyUSB1
Starting pppd
stderr: pppd: in file /etc/ppp/peers/conf-pppd unrecognized option TIMEOUT
Connecting....
Can anybody help me on this issue?
Thanks.
siraci said:
Hi there,
I have checked the presence of ttyUSB into the /dev, but when I run the inet-ON I get.
Waiting ttyUSB1
Starting pppd
stderr: pppd: in file /etc/ppp/peers/conf-pppd unrecognized option TIMEOUT
Connecting....
Can anybody help me on this issue?
Thanks.
Click to expand...
Click to collapse
which sim r u using? and what are the settings for the connection? these problems arise due to incorrect settings. check pm
Hi Bhaskar1109,
thanks for your reply. As you suggested, I have check all installation and I found the mistake, using the adb command I pushed the conf-pppd file but with the conf-chat's file contents .
So now "almost" it works fine. Almost because I have to give manually from adb shell or terninal:
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
in order to create the USBtty
and when the connection is on
setprop net.dns1 208.67.222.222
to set the dns server, because when I run the inet-ON.sh i get the error:
stderr: usage: setprop <key> <value>
This time I have checked the preinstall.sh and inet-ON.sh contents and permissions.
Any clues?
siraci said:
Hi Bhaskar1109,
thanks for your reply. As you suggested, I have check all installation and I found the mistake, using the adb command I pushed the conf-pppd file but with the conf-chat's file contents .
So now "almost" it works fine. Almost because I have to give manually from adb shell or terninal:
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
in order to create the USBtty
and when the connection is on
setprop net.dns1 208.67.222.222
to set the dns server, because when I run the inet-ON.sh i get the error:
stderr: usage: setprop <key> <value>
This time I have checked the preinstall.sh and inet-ON.sh contents and permissions.
Any clues?
Click to expand...
Click to collapse
Maybe that you have done some typing mistakes like extra spaces etc. and have you restarted your tablet?. you can set dns in inet-on.sh file. Are you able to browse internet normally after these commands?
p.s Google play and internal download manager may not work. You can browse play market but cannot install any apps(probably). UC browser download manager works fine. Use 1 mobile market instead of google play.
I have done other tests and now the only small issue is that I have to run the
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
into a separate sh file because seems that doesn't work into preinstall.sh file.
Anyway all works fine and let me say that you have done a great and clever job.
Thanks
it s cool
Hello Bhaskar1109,
I have the tablet N101 by Yuandao and I was successfully using PPPwidget with a Huawei E173 stick for 3G browsing.
Recently it stopped connecting, so after searching new alternatives, I found your very useful topic. I would appreciate your help, since I am trying now to find a way to make it work with your way.
I started using your guide, but I cant pass Step 4 with the terminal emulators.
First of all in Terminal Emulator, when I run dmesg command I get "converter now disconnected from ttyUSB0" and I get this for all USB (0,1,2)
Then when I run busybox tr -s "\n" < /dev/ttyUSBx ( I tried with USB0 till USB2), I am getting a message "cannot open /dev/ttyUSB0 (0,1,2)"
Any help?
RASTAVIPER said:
Hello Bhaskar1109,
I have the tablet N101 by Yuandao and I was successfully using PPPwidget with a Huawei E173 stick for 3G browsing.
Recently it stopped connecting, so after searching new alternatives, I found your very useful topic. I would appreciate your help, since I am trying now to find a way to make it work with your way.
I started using your guide, but I cant pass Step 4 with the terminal emulators.
First of all in Terminal Emulator, when I run dmesg command I get "converter now disconnected from ttyUSB0" and I get this for all USB (0,1,2)
Then when I run busybox tr -s "\n" < /dev/ttyUSBx ( I tried with USB0 till USB2), I am getting a message "cannot open /dev/ttyUSB0 (0,1,2)"
Any help?
Click to expand...
Click to collapse
the ports will be available only when the tab recognizes it as a modem. Following questions might help-
Is your tab Rooted?
Is your modem OK?
Is you modem vid pid correct?
Have You followed step 3 Correctly?Can You see the new line in preinstall.sh?
Have you restarted the tab?
Have You given su permissions to the scripts?
Bhaskar1109 said:
the ports will be available only when the tab recognizes it as a modem. Following questions might help-
Is your tab Rooted?
Is your modem OK?
Is you modem vid pid correct?
Have You followed step 3 Correctly?Can You see the new line in preinstall.sh?
Have you restarted the tab?
Have You given su permissions to the scripts?
Click to expand...
Click to collapse
Since I mentioned before that this dongle was working right for some time with PPP widget, I think most of your questions are already covered.
From your experience, could the Otg cable have started to fail and create these problems that never had before?
The command dmesg is showing that first these ports are available and after they are not.
Also, I think its important that I get this ""cannot open /dev/ttyUSB0 (0,1,2). No such file or directory"
Unleashed by my rooted Nexus 4
Gscript is not working .and from step 4 my confusion starts.
RASTAVIPER said:
Since I mentioned before that this dongle was working right for some time with PPP widget, I think most of your questions are already covered.
From your experience, could the Otg cable have started to fail and create these problems that never had before?
The command dmesg is showing that first these ports are available and after they are not.
Also, I think its important that I get this ""cannot open /dev/ttyUSB0 (0,1,2). No such file or directory"
Unleashed by my rooted Nexus 4
Click to expand...
Click to collapse
Sorry i didnt notice the ppp widget thing.
It may be otg problem, otherwise why would ppp widget failed suddenly at the first place. i suggest u to replace the cable and try again.
Devarishi said:
Gscript is not working .and from step 4 my confusion starts.
Click to expand...
Click to collapse
Can you tell what exactly is the problem/error with Gscript?
Error i faced...
I installed Gscript apk from your download link from your thread. I put that two script under sdcard/"another folder"/gscript. I opened gscript application and it says "process.android.com(alike this) stop working". What happened to my tablet. Im using micromax funbook p300. Is there is any way or the other to let it work ?
Hi guys,
I'm looking for a way to read the kernel output during the boot process. I've already tried recompiling the kernel with/without FIQ_DEBUGGER, KGDB_SERIAL and SERIAL_SAMSUNG (_DEBUG), as well as setting the kernel console in the cmdline to every possible /dev/tty* port without any success.
I also tried echoing in every available serial port and use a digital analyzer on a breakout-microusb board to monitor the output. But all of the tty devices seem to be disconnected from the USB port. There are a lot of hints on the internet for other devices, but the most of them use a dialer to get into the service menu (e.g. for smartphones: http://forum.xda-developers.com/showthread.php?t=1515570) or a jig-cable with a resistor between ID and GND (http://redmine.replicant.us/projects/replicant/wiki/SamsungSerial). Both approaches failed on my Nexus 10.
I got no clue what to do next, so I would be very appreciated for any hints or new ideas.
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
EniGmA1987 said:
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
Click to expand...
Click to collapse
Thanks for that, but as far as I know the ADB daemon is started only after the kernel initialization. I can read the dmesg after Android is booted, but it doesn't help me to debug problems if the kernel panics.
I think I need some kind of a correct serial cable to read the kernel (and bootloader) output, but I couldn't find any working method for N10.
Did you have any luck with your case?
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 ?
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
Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
abs0lutezer0 said:
Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi, where you able to solve this? I'm having the exact same problem
Hey! I was able to find the solution for this.
First you will need to root the phone with Android 7.1.1 Nougat (you can find the procedure in the forum or in youtube).
After phone is rooted, run the following ADB commands:
su
setprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
setprop sys.usb.state diag,serial_cdev,rmnet,adb
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Please note after entering "su" (super user) you'll need to grant superuser permissions (prompt shown on the phone).
After doing this, TEMS Investigation can detect and activate the phone, as you'll can see here. I assume other software (Nemo, XCAL, etc) should work as well.
Hope this helps!!