LG G3 D850 unlock Mobile Hotspot tethering noroot

LG G3 D850 unlock Mobile Hotspot tethering noroot - AT&T LG G3

Hello fellow LG G3 owners,
After much frustration, I am pleased to announce that I figured out how to unlock wifi "Mobile Hotspot" tethering without root.
1) enable debugging in developer options on your phone
2) set up android SDK and ADB on your computer
3) run this command in adb"
Code:
adb shell settings put system tether_entitlement_check_state 0
4) confirm it worked:
Code:
adb shell content query --uri content://settings/system | grep tether
5) go to "Tethering & Networks" in your phones settings and enable Mobile Hotspot :good:
Enable developer mode:
http://www.androidcentral.com/android-50-lollipop-basics-how-turn-developer-settings
Linux users may need to read this:
http://forum.xda-developers.com/lg-g3/general/guide-connecting-lg-g3-to-linux-adb-aka-t2821673

I'm on D850 4.4.2 custom stock rom. my build.prop is edited to show T-Mobile network icons, which disables the wifi hotspot feature. I'll try this in 5 minutes.
Edit: unsuccessful with my setup. I want to keep my TMO network icons because it increases my bars and adds the HD voice calling feature. but I can't use wifi hotspot -_-
Sent from my LG G3

Followed the steps. Running abd on windows cmd. USB debugging is enabled.
When I enter: "adb shell settings put system tether_entitlement_check_state 0"
I get an error saying "/system/bin/sh: not found"
Note: I'm on stock lollipop OTA (no root)

Thank you, worked for me, I'm on Lollipop, rooted, with twrp installed, I couldn't edit the settings.db, said it was locked, so I followed your instructions, and worked great.

Update: After root...this method works for me. On AT&T G3 Lollipop 5.0.1 ROOTED. (As previously stated, this method didn't work for me without root)
Thanks for the post for getting it working

How do you run the command in terminal emulator?

UMGixxer said:
How do you run the command in terminal emulator?
Click to expand...
Click to collapse
Just type eveything after shell:
Code:
settings put system tether_entitlement_check_state 0

Thank you, its working on my device as of now. Does anyone know how AT&T can tell if you are tethering? I assume if they notice a large increase in data usage but idk.

UMGixxer said:
Thank you, its working on my device as of now. Does anyone know how AT&T can tell if you are tethering? I assume if they notice a large increase in data usage but idk.
Click to expand...
Click to collapse
I've used tethering via tethering hacks or custom roms on AT&T without a tethering plan for four or five years now -- One time I even managed to rack up a 100GB ($900 some odd dollars worth....seriously) of overages (CM9 tethering WiFi to PC, cat unplugged WiFi router) and didn't even have to pay for it (I played stupid....learned to disable data when I do that). I even TOLD them I was tethering and they didn't care.
Your mileage may vary, but from my experiences, they don't check nor do they even care.
I mean, if I can rack up $900 in overages, tell them I did it by doing something I shouldn't even have, and then have them wipe away the charges and not have to pay for it.....they clearly just don't care and obviously don't check....or their checking method is crap....

nhusby said:
Hello fellow LG G3 owners,
After much frustration, I am pleased to announce that I figured out how to unlock wifi "Mobile Hotspot" tethering without root.
1) enable debugging in developer options on your phone
2) set up android SDK and ADB on your computer
3) run this command in adb"
Code:
adb shell settings put system tether_entitlement_check_state 0
4) confirm it worked:
Code:
adb shell content query --uri content://settings/system | grep tether
5) go to "Tethering & Networks" in your phones settings and enable Mobile Hotspot :good:
Enable developer mode:
http://www.androidcentral.com/android-50-lollipop-basics-how-turn-developer-settings
Linux users may need to read this:
http://forum.xda-developers.com/lg-g3/general/guide-connecting-lg-g3-to-linux-adb-aka-t2821673
Click to expand...
Click to collapse
If you have root, you can also add the following line to the build.prop....
Code:
wifi.lge.common_hotspot=true
You might need to do a full wipe for it to activate the change, but your phone will no longer check for authorization.

Yeah I have used this method to get my Hotspot working and no luck. But when I install any custom rom I have no problem with my Hotspot and have used it solely for all data running through my house over 100 gigs one month. I'm on the $80 unlimited T-Mobile plan but that only allows for 5gb Hotspot.

Thanks, I was about to go full root/rom just to get tethering, but I'm quite happy with the stock experience, so this is the bees knees for me. Here's my experience from fully stock, non-rooted, AT&T LG G3 running Android 5.0.1-
After Step 2, When you first plug your phone in, you'll get a notification for USB options... Choose Media sync (MTP). You will also have to authorize the PC.
Now you can run the first command in ADB, then second command stated grep wasn't recognized, but upon checking the phone Mobile Hotspot functioned as desired.
As for the cell provider recognizing your activity, they can, but usually don't care unless you are abusing it. One simple way they can tell you are tethering is by seeing what browser you are using..... for example, if you watch several hours of Netflix on your PC while tethered, they can go in and see you have been using the desktop version of Chrome. You could always use a VPN/Tunneling service to encrypt your data, but those usually cost a little and are slower due to the extra hop and encryption overhead.

Awesome. Works like a charm. I used to install cyanogenmod to "stick it to the man", but discovered with the new phone that it seems my company has bundled in tethering with their AT&T contracts, so I had not bothered.
Then I found this thread and enabled it in one easy command. Now I no longer see a message about checking authorization for tethering. Stickin' to the man still has some satisfaction
BTW, if anyone wants to restore, "4" was the default for my 5.0.1 D85020f Build LRX21Y:
[email protected]:/ # content query --uri content://settings/system | grep tether
Row: 216 _id=263, name=tethering_time, value=600000
Row: 314 _id=3525, name=tether_entitlement_check_state, value=4

Will this work with Sprint LG G3 Lollipop version?

winn75 said:
Will this work with Sprint LG G3 Lollipop version?
Click to expand...
Click to collapse
it does work I just did it and worked like a charm.

Thank you for sharing. I tried 3 times, worked the third. I think typing error was the reason.

joe-45 said:
it does work I just did it and worked like a charm.
Click to expand...
Click to collapse
It didn't work for me.
did you have to first type "adb shell" then press enter?
[email protected]:/ $ settings put system tether_entitlement_check_state 0
do i have to put a # sign?
could someone make a video of how to?

Worked perfectly for me, just used Terminal Emulator from the phone. Only worked after I entered 'su' command and entered the lines as root.
Thanks!

Worked on my LG G4, thanks everyone.
Sent from my LG-H810 using XDA Free mobile app

Worked on my Stock 5.0.1 (lollipop)
:good:
Thanks! Works on my LG G3 android version 5.0.1, software version D85021q, kernal version 3.4.0, build number LRX21Y - pure stock with ota updates. No root.
I tried the second command first :
adb shell content query --uri content://settings/system
the "grep" won't work on windows if you don't have "grep" installed. Regardless, this would be good to see if you can connect to the phone properly. At first I got some error about server being outdated/old. But after trying a couple of time, it showed the contents.
The first time I tried adb shell settings put system tether_entitlement_check_state 0,
I got an error message as well. I just tried it a couple of times and it went through.
Tested at my gym and just now at work, and all's well.

Related

How to register the G1 without a sim or data plan

I've found a way to register the G1 in the initial registration screen that comes up the first time you boot the phone (or after you wipe the phone). It will allow you to register if you don't have a sim card at all, or if you have a sim card but no data plan.
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
------------
A few tips and tricks:
- If you have an official RC29 or lower phone, type the following command on the phone keyboard to enable adb:
<enter>setprop persist.service.adb.enable 1<enter>
- If you need to get root access on an official RC29 or lower phone, while it's at the registration screen, or the "no sim card" screen, enable adb (see first tip), and then type the following command on the phone keyboard:
<enter>telnetd<enter>
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together.
But beware, the phone seems a bit glitchy if you don't have it registered. For example, the home button doesn't seem to work. And you can't access the market or any of the google apps of course.
(Note: the following was the previous way to skip registration. I'll keep it here for informational purposes, but its easier to use the app.setupwizard.disable method instead of this)
- If you don't want to register the phone at all, you can edit /data/system/packages.xml and disable the registration screen. Add the following to the end of the <package> section for com.android.setupwizard, and then reboot:
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
so the full <package> would look something like below after the modification:
<package name="com.android.setupwizard" codePath="/system/app/SetupWizard.apk" system="true" ts="1217592000000" userId="10010">
<sigs count="1">
<cert index="0" />
</sigs>
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
</package>

He worked on this for a very long time with me and walked me through all the steps when testing this out. Great person.

Really nice...
I'll try to do it.
I have to study though...
I'll be in touch.
Thanks

thanks JF you are good in this thing.
My case i have sim card without data plan, when turn on phone show me screen for register email account with google.
c:\adb shell
show me # simbol
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
and in the phone show me the menu for connect to my wireless
conected, registered, go ahead.
thanks

satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.

Ok, my device was recognised and "installed" but no driver was requested.
I have read I need to do some settings from within the g1, but I can't, since it's not activated! (http://forum.xda-developers.com/showthread.php?t=443797&highlight=info)
When I issue the "adb devices" command, I get no recognised devices...

To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.

cmavr8 said:
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Click to expand...
Click to collapse
A quick way to check if you have RC30 is to reboot the phone, and then once it starts up and it shows the "click the android to begin" screen, type
<enter>reboot<enter> on the phone keyboard.
If it reboots, you have RC29 or lower. Otherwise you have RC30.
If you do have RC29 or lower, then you can use the first tip I posted to enable adb. Once adb is enabled it should ask you to install the drivers when you plug it in.

satru said:
conected, registered, go ahead.
thanks
Click to expand...
Click to collapse
Great! Glad it worked for you

Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)

cmavr8 said:
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
Click to expand...
Click to collapse
Did you try my first tip to enable adb?

johnny13oi said:
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
Click to expand...
Click to collapse
Thanks for your reply.
SD mounting works fine.
In recovery mode nothing is better... (tried recovery without sd only)
Is there anything else I should try?

JesusFreke said:
Did you try my first tip to enable adb?
Click to expand...
Click to collapse
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?

cmavr8 said:
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
Click to expand...
Click to collapse
A couple of things:
- Look further down the post, there's a "tips and tricks" section. The first tip is how to enable adb.
- second, I don't think you need to go through the first step (the sqlite3 command). The first step is to get past the "no sim card" screen. You said you have a sim card, just no data plan, right? So you don't need to get past the "no sim card" screen . You can skip to the second step (once you get adb working, of course)

DID IT!
Thanks so much!!
I now have to wait for the unlock code so that I can also use my sim card...
Thanks both of you!
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...

Great! Glad you got it working

cmavr8 said:
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Click to expand...
Click to collapse
how?
thanks

xaxis said:
how?
thanks
Click to expand...
Click to collapse
Probably by getting lucky and getting a nice CSR

JesusFreke said:
Probably by getting lucky and getting a nice CSR
Click to expand...
Click to collapse
man thank god you are here,
do i need the SDK installed to get the adb?
thank you

Yes, adb is included in the sdk

adb from smartphone to android wear with just bluetooth (no cables needed)

Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.

This isnt working for me on my OPO running CM12 unofficial... Running the commands gives me a blank adb devices window, any advice?

Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps

gusano38 said:
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
Click to expand...
Click to collapse
Works like a charm thanks for the help

Where is the adb binary? Adb isn't a recognized command

My binary is in /system/bin/adb

Sideloading...
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse

AJWizkid said:
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
Click to expand...
Click to collapse
Adb -s localhost:4444 install my.apk

Where can I download the script?
¯\_(ツ)_/¯

thegrim11 said:
Where can I download the script?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Here's the script.
Using Root Explorer:
Create a folder under /system and copy adbgwrbt.sh there
Set permissions to 100 (execute for owner)
Tap script and hit execute
Profit
No credit. Just copied and pasted from OP. Thank you so much for this gusano!! Always find myself needing this . Now if you could just figure out fastboot [emoji57]

Oh my, thank you very much, I've been trying to do this ever since I got my watch but just didn't have the skills (still managed to fins an other way to send files from the phone to the watch and even install apk's), you're great man!

hatefuel19 said:
Now if you could just figure out fastboot [emoji57]
Click to expand...
Click to collapse
I'm pretty sure that in fastboot mode (bootloader) the bluetooth driver is not loaded, so I guess having fastboot with bluetooth is not possible. Furthermore, I would not trust a bluetooth connection to do things that could brick your watch... of course, the pogo pins is not what I call a super trustable connection either

The sarcasm was lost apparently ?

Grr. Got a replacement phone from insurance and the binary isn't there. Can someone please pm me the adb from system/bin?
Sent from my XT1060 using Tapatalk

gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
Loved your post!
Thing is I get an error each time I try the script.
I own a rooted LG G3 ChupaChups 4.2 ROM and a LG G Watch R
Thanx in advance to your help.

setprop service.adb.tcp.port 5555
Sent from my HTC One_M8 using Tapatalk

Unauthorized
ADB tells me that my device has not authorized itself as an adb connection. The problem is since it's not actually a standard USB debugging connection I don't get a popup to mark my device as trusted. Is there anyway to work around this?

I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
J0SH1X said:
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
And yes I did enable all debugging setting in companion app on phone on wear
Gesendet von meinem Nexus 4 mit Tapatalk

i have this problem not connect to localhost 4444. i have cm13

adb commands won't work for me.

Samsung Luna StraightTalk S120VL FRP Bypass

Samsung Luna StraightTalk S120VL FRP Bypass
In Model Number usually..
BL = Tracfone
VL = Straight Talk
(Both the same company but there are differences in ways used to do FRP removal depending on certain devices so I always list accordingly)
Tested on U2 firmware APJ2 so not sure if this works on U1. If the U2 firmware is wanted I will host and post it here.. It can be found by searching google too.)
Security Patch: (October 1, 2016) and.. should work fine on any other.
I had a stack of these phones gave to me for FRP Removal and these days I usually use Uni Android Tools, OctoPlus, or Z3X boxes for SamSung work. I tried while knowing this would most likely not be possible with this handset model. Success = 0. Tried a multitude of other operations and still nothing. Upgraded Firmware to the latest U2 because i had it, couldn't find a (free) combo in the time i looked and thought maybe it would allow something different.. I might be right. This is the first one in the stack I have done this on. So I will edit / post about U1 (Binary 1) models once this one is finished off. I know the methods work below just getting this write up done first. Anywho..
Whats needed? (each will depend on method taken below)
1) Bluetooth EarPiece
2) Old sim card (Verizon best for this way)
3) ADB Installed (Install this anyway as it's handy to have!) - Here is a link to a super quick and easy installer that will do it and while making ADB systemwide. Thanks to XDA user @Snoop05
Link for basic info - https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Link to Thread for dicussion - https://forum.xda-developers.com/showthread.php?t=2588979
DIRECT DOWNLOAD LINK - https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
4) ADB FRP Removal Application
Lots of ways past this initial point.. Here are 3 i know of that will work for this $20 old pocket buddy.
1) Preperation - First start off by hard resetting your Samsung Luna S120VL
Next find a sim card. I used an older used Verizon sim card. No longer in service. Put it in.
Boot phone. Goto Emergency Dialer. Dial 112 and instead of taking you to 911 (good yeh?) you'll get a voice greeting by Verizon. While this happens pair your bluetooth. (best if you have it in pair mode before dialing)
2) Removal - Three ways to do this. 2 more possibilities to do at the bottom of this post.
a. Connect to WiFi with Bluetooth. -> [Will do this when i get time]
b. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+ Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup. Stay on the very first page of the setup wizard.
-
Now open CMD prompt type
Code:
adb devices
and make sure your device shows something like this -
List of devices attached
8e60d4bf device
Yeah? Ok now copy the following code and paste it into the CMD window and press enter.
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Follow through the Setup Wizard which will quickly drop you onto your home screen and now you are done!
If the above command does not work in your case you can try the following command below. This will take you to login screen and then you can enter you Google account.
Code:
adb shell am start -n com.google.android.gsf.login/
If both previous commands do not work then try this.
Code:
adb shell am start -n com.google.android.gsf.login.LoginActivity
c. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+. Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup.
-
Now use one of the many apps out there to remove FRP now that ADB is enabled. I will ask the moderators about posting but not sure it is allowed. Also the one that is easiest to use and that I recommend will trigger a false positive on Anti Virus. IF ok to post I will update this thread with a download.
----
Other Methods?
Accessibility Mode Method - When i get time (if it's possible.. as a quick check on U2 APJ2 didn't allow much)
ADB enabled boot IMG - Found one and these can be made as well but the one i have found (free) is from the Factory Engineering Firmware I believe. I just don't have much more time to fool with these luna phones. You'd just need to flash this then no need for bluetooth.. Again when i get a minute and remember I will put it up here.
Enjoy!
-noidodroid

Thanks

100+ Phone model extraction + others.

Hi.
First time making a post here, but have been using stuff here for quite a while. Thanks so much to the community for all the amazing stuff being developed, ect, here.
To the question:
My father's girlfriend recently came into 100's of phones. All various sources, mostly OBF's (Out of box failures) from the stores under their management.
I need a way to retrieve the models of each phone as quickly as possible. Other things aren't necessarily a necessity, but things like IMEI numbers, ect, would be a big bonus.
I then need to sort this data in a spreadsheet, but I can do that manually if exporting the data from the phones is possible.
These are obviously not rooted, as they were maybe turned on, or used once or twice if that much, and rooting them definitely would be longer than just doing the first time setup and then looking in settings.
Thanks to everyone for reading!
Greetings from South Africa.

You can retrieve a phone's brand / model and IMEI by means of ADB:
Get brand
Code:
adb shell "getprop 'ro.product.brand'"
Get model
Code:
adb shell "getprop 'ro.product.model'"
Get IMEI
Code:
adb shell "service call iphonesubinfo 4 | cut -c 52-66 | tr -d '.[:space:]'"

jwoegerbauer said:
You can retrieve a phone's brand / model and IMEI by means of ADB:
Get brand
Code:
adb shell "getprop 'ro.product.brand'"
Get model
Code:
adb shell "getprop 'ro.product.model'"
Get IMEI
Code:
adb shell "service call iphonesubinfo 4 | cut -c 52-66 | tr -d '.[:space:]'"
Click to expand...
Click to collapse
Is USB debugging not necessary for Adb? Or is fastboot all that you require? Do all android devices have a fastboot or similar? As I said, it's a lot of phones and they aren't all the same, all kinds of brands from Samsung to techno sparks.

Think I clearly spoke of ADB and not of Fastboot.
Yes, USB-debugging must be enabled on a phone to run ADB commands.

jwoegerbauer said:
Think I clearly spoke of ADB and not of Fastboot.
Yes, USB-debugging must be enabled on a phone to run ADB commands.
Click to expand...
Click to collapse
My apologies. I’m a computer technician. Don’t usually play with phones, except for the normal rooting devices from time to time (following guides ect.) So I’m not all that clued up yet.
Enabling usb debugging still means turning the device on, first time setup, enable usb debugging, use adb to get data.
Might as well just write down the model from “about” at that point and leaving the other less necessary data completely.
Any other ideas or is that the best we can do? In which case, thank you for the suggestion.
Is there perhaps a faster way to enable usb debugging?

AFAIK to access a phone's "About" screen it's not required that USB-debugging is got enabled on phone.

Resetting Verizon Orbic Speed RC400L firmware flash Kajeet

I purchased a used Kajeet branded Orbic Speed RC400L hotspot off eBay which came with a charger, carrying case and Verizon SIM. I went though the Verizon prepaid activate website and it says the device is compatible and the Verizon sim card in it will work, however I noticed when I powered on the hotspot many menu settings were locked out.
I then connected to the hotspot and navigated to 192.168.1.1 and following Verizon's manual for this device I entered in admin as the username and the wifi password as the password and nope, wasn't able to log in. To make matters worse I decided to swap a Verizon prepaid SIM from another device and everything appeared to work, it showed signal however it had no internet, and when I looked into this further I realized this device is programmed with a different APN than the Verizon default for Kajeet's services, and I can't log in to change this.
I then attempted to hold down the reset button on the device for 5 seconds following Verizon's manual for this device while it was powered on and it did not reset, nothing I did would let me factory reset the device.
I then started to look into other options.
If I connect the device powered off to a laptop via USB, press and hold both the power and reset buttons I hear the device connect sound on Windows. I checked Device Manager and see the device as a Qualcomm device on COM10. I opened up QPST which confirms this device is on COM10 and in download mode.
This is good news as this appears to be how I can flash new firmware onto this device, but sadly there is no instructions on how to do this nor the stock Verizon firmware to download for this device.
When connecting the device powered up normally QPST detects it on COM10 but isn't able to read any info about the device at all.
I am stuck now on what to do, part of me wants to activate it on Verizon prepaid and then call Verizon when it has no internet and see if they can remotely reset it or program the right APN settings into the device to see if it'll work, however I don't know if they'll be able to do this.

I’m looking into acquiring a second Orbic Speed hotspot new from Verizon and making a backup of that firmware and then flashing it to this other hotspot using the Qualcomm download mode to recover it as well as uploading it and making instructions here for anyone else who runs into this issue.
That seems to be the only way to do a complete hard reset since the firmware on the one I have is locked and the reset button doesn’t do anything in its regular powered up state.
There are various tutorials for Qualcomm based devices on how to make an entire firmware backup or dump of the device so I’m hoping those will work with this device as well.
I’d like to see if anyone can root this hotspot given it reportedly runs Linux and install a modified OS on it as well as do band unlocking and allow it to work on any carrier too, I’ll see if I can get more info about the hardware and which Qualcomm chipset it uses.
You can obtain one of these hotspots new for a significant discount by purchasing a used Ellipsis MHS900L and exchanging it under the recall that exists for these devices.

TheTechDude48 said:
I’m looking into acquiring a second Orbic Speed hotspot new from Verizon and making a backup of that firmware and then flashing it to this other hotspot using the Qualcomm download mode to recover it as well as uploading it and making instructions here for anyone else who runs into this issue. Omegle app
That seems to be the only way to do a complete hard reset since the firmware on the one I have is locked and the reset button doesn’t do anything in its regular powered up state.
There are various tutorials for Qualcomm based devices on how to make an entire firmware backup or dump of the device so I’m hoping those will work with this device as well.
I’d like to see if anyone can root this hotspot given it reportedly runs Linux and install a modified OS on it as well as do band unlocking and allow it to work on any carrier too, I’ll see if I can get more info about the hardware and which Qualcomm chipset it uses.
You can obtain one of these hotspots new for a significant discount by purchasing a used Ellipsis MHS900L and exchanging it under the recall that exists for these devices.
Click to expand...
Click to collapse
Xposed is incompatible with the ART runtime. That means it won't work on Lollipop.

How can i
Make an backup of a normal orbic hotspot

I have an Orbic Speed that I got in exchange for an Ellipse with the battery problem.
I had already wasted more money on the 8800L so I really didn't need the Orbic.
I was playing around trying to get it into EDL mode.
The normal connect is RNDIS.
I tried to find EDL test points, but nothing seemed to work.
I tried beating on it and actually got it into 11f6/900e QHSUSB__BULK, which is certainly strange. (Should be 05c6/9008).
I haven't been able to get there again, it may have just been really corrupted. Also, it didn't respond correctly to Sahara and got wedged.
But... I did find a test point to reliably put it into Fastboot mode! I was surprised. I can getvar and reboot but no reboot-edl or oem edl.
The test point is under the top left corner of the LCD, the first point in the corner. Just ground it during reset.
You have to ease the LCD display up a bit.
Does anyone know any good Orbic OEM commands?
Edit: Lol! That was quick. I just discovered that if you connect the "Fastboot" test point to the test point immediately to the right it goes into EDL.
I haven't got a loader for it, but Sahara gives me HWID: 000480e100000000, MSM: 000480e1, OEM: 0000, Model: 0000, Hash: cc3153a80293939b.
I haven't found a loader yet because my internet is so crappy. Yeah, Verizon.
For Fastboot: Connect Sense to Gnd
For EDL: Connect Sense to 1.8V
If you're timid, use a resistor (I used a 1k).
The loader that you want is:
https://github.com/bkerler/Loaders/qualcomm/patched/mdm9x07/prog_nand_firehose_9x07.mbn
This uses NAND storage.
The partioning is not GPT, it's something else.
Partitions are: sbl, mibib, efs2, dynamic_nv, efs2_bak, tz, rpm, aboot, boot, scrub, modem, misc, recovery, usrdata, recoveryfs, sec, system
The boot image is Red Hat UBI.
Edit: I got tired of this thing sitting around disassembled, so I soldered in a tiny magnetic reed switch and buttoned it up.
Now if I want to get to EDL I just park a magnet in the top of the case and hit reset.
I did this before to my ereader (Onyx Poke3) too.

@Renate
Are you still fooling with this device?
I told you I got one a couple weeks ago, I have my workup done for it. I also go the factory for it and patched it so it actually works now lol, it would only work before if you were on I think it was v1.5.1 now I have it set to force load everytime and patched the version check, I have full reloadable firmware made up for it now and can erase the device to 0 and then recover it to fully working.
I never could get that loader to work, i have to find a diff one for this model
here is a few screenshots
imei repair was different for this one than on other similar devices
We were talking about its comports in that 8800 thread, I baked enabled ports into the first firmware build I made for this one but then later found a way to enable them without needing to load firmware, if you need your ports enabled on yours hit me up.
Someone sent me a moxee device a few days ago and while they are basically the same looking device it is a deceiving similarity, cannot use the same firmware or loader and the board layouts are much different, the Verizon orbic model is much better than the moxee device at first glance the only notable diff is the micro USB port but looks can be deceiving lol.
the dumbed-down kernel with almost none of the needed modules makes it live up to its entry-level status.

Mmm, I don't need dumber Verizon hot spots, I need a smarter one!
It's too bad that the NetGear NightHawk M1 and M6 don't have the Verizon bands.

I have put hundreds of M1's on vzw, it only lacks b13 but most markets have 2, 4 & 66, they work fine on vzw and M6 I have put many on vzw also

Figured out a few things about my RC400L. First, to enable ADB, send a USB control message of type LIBUSB_REQUEST_TYPE_VENDOR, request 0xa0, a value of 0, and no data. The device will now reboot. adb is now enabled, but rndis has been disabled (regardless of what you set USB tethering to). However, it's also exposed the DIAG and AT endpoints, so if you have drivers installed for that you can just connect to the AT port and send AT+SER=9,1 which will switch to a mode that exposes adb, diag, at, and rndis. adb is running as an unprivileged user, but if you connect over the AT interface you can also run AT+SYSCMD= with a Linux command after the equals sign, and it'll run that as root. I was hoping to find a way to reboot into fastboot via software but haven't had any luck on that so far, so I guess I'll have to crack the case open.

Unfortunately it's not possible to configure the Orbic to just boot when plugged into USB - it's actually booting Linux, but simply displaying a charging screen instead of enabling USB or starting the modem stack. This is controlled by the "androidboot.poweronreason=" parameter that's passed on the kernel command line, and several different components parse this. The easiest solution I've found is to dump the bootloader (it's /dev/mtdblock7) and search for the byte sequence "03 02 00 0a 20" and replace the 20 with ff. 20 is the value read from the power management controller that indicates the device powered up because it was plugged into USB - replacing that with ff means the bootloader no longer understands that, and falls back to describing it as a hard reset. This value is interpreted as a legitimate bootup and everything works.

mjg59 said:
Unfortunately it's not possible to configure the Orbic to just boot when plugged into USB - it's actually booting Linux, but simply displaying a charging screen instead of enabling USB or starting the modem stack. This is controlled by the "androidboot.poweronreason=" parameter that's passed on the kernel command line, and several different components parse this. The easiest solution I've found is to dump the bootloader (it's /dev/mtdblock7) and search for the byte sequence "03 02 00 0a 20" and replace the 20 with ff. 20 is the value read from the power management controller that indicates the device powered up because it was plugged into USB - replacing that with ff means the bootloader no longer understands that, and falls back to describing it as a hard reset. This value is interpreted as a legitimate bootup and everything works.
Click to expand...
Click to collapse
Any chance at getting some 5000 foot guide/direction on how to do this? I haven't messed with ADB in the last 10 or so years . I would love to get my RC400L setup to auto start from a powered off state when the USB power is connected. My use case is a rpi running a remote weather station and camera that posts to twitter every 5 minutes. I have access to the setup, but it's a 15 minute drive each way!

Renate said:
I have an Orbic Speed that I got in exchange for an Ellipse with the battery problem.
I had already wasted more money on the 8800L so I really didn't need the Orbic.
I was playing around trying to get it into EDL mode.
The normal connect is RNDIS.
I tried to find EDL test points, but nothing seemed to work.
I tried beating on it and actually got it into 11f6/900e QHSUSB__BULK, which is certainly strange. (Should be 05c6/9008).
I haven't been able to get there again, it may have just been really corrupted. Also, it didn't respond correctly to Sahara and got wedged.
But... I did find a test point to reliably put it into Fastboot mode! I was surprised. I can getvar and reboot but no reboot-edl or oem edl.
The test point is under the top left corner of the LCD, the first point in the corner. Just ground it during reset.
You have to ease the LCD display up a bit.
Does anyone know any good Orbic OEM commands?
Edit: Lol! That was quick. I just discovered that if you connect the "Fastboot" test point to the test point immediately to the right it goes into EDL.
I haven't got a loader for it, but Sahara gives me HWID: 000480e100000000, MSM: 000480e1, OEM: 0000, Model: 0000, Hash: cc3153a80293939b.
I haven't found a loader yet because my internet is so crappy. Yeah, Verizon.
For Fastboot: Connect Sense to Gnd
For EDL: Connect Sense to 1.8V
If you're timid, use a resistor (I used a 1k).
The loader that you want is:
https://github.com/bkerler/Loaders/qualcomm/patched/mdm9x07/prog_nand_firehose_9x07.mbn
This uses NAND storage.
The partioning is not GPT, it's something else.
Partitions are: sbl, mibib, efs2, dynamic_nv, efs2_bak, tz, rpm, aboot, boot, scrub, modem, misc, recovery, usrdata, recoveryfs, sec, system
The boot image is Red Hat UBI.
Edit: I got tired of this thing sitting around disassembled, so I soldered in a tiny magnetic reed switch and buttoned it up.
Now if I want to get to EDL I just park a magnet in the top of the case and hit reset.
I did this before to my ereader (Onyx Poke3) too.
Click to expand...
Click to collapse
magnetic reed switch is so ****ing clever so it doesnt have to be disassembled to use testpoints for edl

chimchim54321 said:
Any chance at getting some 5000 foot guide/direction on how to do this? I haven't messed with ADB in the last 10 or so years . I would love to get my RC400L setup to auto start from a powered off state when the USB power is connected. My use case is a rpi running a remote weather station and camera that posts to twitter every 5 minutes. I have access to the setup, but it's a 15 minute drive each way!
Click to expand...
Click to collapse
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.

mjg59 said:
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.
Click to expand...
Click to collapse
Some of the steps are just a touch off on syntax, but it all worked successfully with my edit of aboot locally on my Windows machine via the HxD app.
Does the battery bypass file work to allow the RC400L to boot without the battery installed? If so, is the file specific to the RC400L?

chimchim54321 said:
Some of the steps are just a touch off on syntax, but it all worked successfully with my edit of aboot locally on my Windows machine via the HxD app.
Does the battery bypass file work to allow the RC400L to boot without the battery installed? If so, is the file specific to the RC400L?
Click to expand...
Click to collapse
Oh, please let me know what I screwed up and I'll fix it in case anyone else follows this! But no, as far as I can tell if the battery is missing the code changes behaviour at an earlier point, and I haven't looked into that (or whether it's even possible for it - some devices insist on the battery because they may instantaneously draw more power than is provided over USB and rely on the battery to make up for it). But this specific patch is very specific to the RC400L bootloader, and the entire process would probably need to be modified for other devices.

rich hathaway said:
I have put hundreds of M1's on vzw, it only lacks b13 but most markets have 2, 4 & 66, they work fine on vzw and M6 I have put many on vzw also
Click to expand...
Click to collapse
B13 at 750 MHz is very important when you're in the sticks.
In contrast, 5G is something that will never make any difference to me.
(A bit off-topic)
I'm currently running PtMP (microwave) internet off a Ubiquiti LTU Mini and a separate router/WiFi.
I'd like to be able to seasonally switch over to a 4G LTE modem with only wired ethernet.
So I don't want a modem with anything (no NAT, no WiFi), only a RJ45.
I see the NetGear LM1200. Is this any good? That 5G is useful to at least discount the 4G equipment.
Also, this is a battery-less device.
I never liked the MiFi 8800L. I found that when the LTE reception was flailing it would disrupt the regular connection between local devices on the WiFi.

mjg59 said:
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Click to expand...
Click to collapse
step 7 - my win10 PC didn't care for the orbic/* portion. Either use just "orbic" or use orbic/sshell (unteseted but would likely work)
mjg59 said:
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Click to expand...
Click to collapse
second half of step 9, the path is wrong and strangely the terminal responds back with OK. The path should be /tmp/orbic/sshell
mjg59 said:
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.
Click to expand...
Click to collapse
I think that was it for the issues I had. At least with the directions The adb pull put the file in a weird AppData path location, and perhaps a fully qualified path for the target of the pull would be advisable.
My old modem would often sort of flip out and require a power cycle to get back to normal. I built a relay module that could be operated by one of the gpio pins on the Rpi, and it would cut the external power as well as the internal battery. Was much easier as the internal battery had wires and a plug that I could splice into. For this modem I think I'm going to have to design and print a battery adapter that will allow me to put a set of relay contacts between the battery tabs and the modem battery buttons.

Renate said:
B13 at 750 MHz is very important when you're in the sticks.
In contrast, 5G is something that will never make any difference to me.
Click to expand...
Click to collapse
Yes the lower end of the spectrum is better for penetrating buidings and such, but if you have a tower (line-of-site) or maybe not to far and not to obstructed b13 is not needed to get good service, I have a tower at about 8miles not line of site and b66 works fine for me here on an m1
Renate said:
I'd like to be able to seasonally switch over to a 4G LTE modem with only wired ethernet.
So I don't want a modem with anything (no NAT, no WiFi), only a RJ45.
I see the NetGear LM1200. Is this any good? That 5G is useful to at least discount the 4G equipment.
Also, this is a battery-less device.
Click to expand...
Click to collapse
I have not had that device before so I am not familiar with it and not sure what it costs but the m2000 is a fine device and can run without a battery with a simple mod, no rj45 coming out but the usb-C can be cheaply adapted over to rj45, and this device can be bought for cheap (35 bucks) on ebay if you look around there are many for 50 bucks out there.
if you need help pulling in signal in your location the FW2000 is an excellent device, its expensive but I can tell you I am using one now and it is a beast with built in high power antennas it really pulls the signal in and is battery - less

Database Info

welcome