Hidden Tethering Usage, PDAnet Instability and recreating "Hide Tether Usage" - Android Q&A, Help & Troubleshooting

Hidden Tethering Usage, PDAnet Instability and recreating "Hide Tether Usage"
Two Questions.
1) What is going on inside PDAnet to cause it to be so unstable?
2) Can whatever magic pixie dust running inside PDAnet /FoxFix hiding the tethering usage, be recreated in a linux environment, without full-root?
Ive found a HackerNews post here about using adb to set the DUN configuration:
https://news.ycombinator.com/item?id=20461879
Code:
adb shell settings put global tether_dun_required 0
This coupled with the Tether package (https://github.com/bemehiser/Tether/) and cyanogenmod tether results in blazing fast, yet impressively sporadic bandwidth ( 50 or 1mbps ... nothing in between @ 90% time being spent in crawling )
Additionally I've run this line:
Code:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,,,,310,120,,default,mms,dun"
Yet it seems to have done nothing to change the misbehaving speed fluctuations.
Ive found a few other packages:
https://github.com/RiFi2k/unlimited-tethering
https://github.com/double-m/easy-usb-tethering
https://github.com/evdenis/tether_unblock
But havn't used them yet.
Endgame I want my phone to not snitch on my USB-based tethering.
Can this be done with just ADB or do I need to full root the phone?
Heres another possible workaround using SQLITE to define what seems to be able to be set using ADB
http://www.madore.org/~david/linux/android.html
I BELIEVE this substantiates that changing a routing table, once full-rooted, would fix any DUN-based carrier reporting:
https://danielpocock.com/android-betrays-tethering-data/

Found more information on how PDAnet might work its magic:
https://www.howardforums.com/showth...-tethering-look-like-on-device-data-use/page4
PDANet hides tethering by changing the user agent of every HTTP request passed through, and also blocking OS-specific ports and features (Windows Update, Mac App Store, etc).
This in turn has the smartphone route each request, and then replicate the data back to the device. Anything only a PC could truly do (like Mac App Store), is in turn blocked.
Since then you're getting the mobile-formatted versions of sites, and not doing anything that you couldn't also do on the smartphone... if Android Auto isn't counted tethering, PDANet's stealth mode certainly is doing the same thing - basically... especially under Block C rules.
Click to expand...
Click to collapse

crazycarl said:
Can this be done with just ADB or do I need to full root the phone?
Click to expand...
Click to collapse
To enter Android's Shell
Code:
adb shell
requires a rooted Android.

Wait running the command requires a rooted phone?
Ive been able to run the command and my phones not rooted.
Maybe its just not giving me an error explicitly saying I dont have auth to run the command?

jwoegerbauer said:
To enter Android's Shell
requires a rooted Android.
Click to expand...
Click to collapse
I dont think this true. Im fairly certain that i've not rooted my phone yet Im able to connect the USB and bring up the adb shell promp:
Code:
[email protected]:~$ adb shell
a50:/ $

@crazycarl
What you think means nothing to me.

jwoegerbauer said:
@crazycarl
What you think means nothing to me.
Click to expand...
Click to collapse
That's good to know.
So youre saying that the $ adb shell will run on a terminal, accept commands, and issue no notification of failures.
IDK just seems unlikely.
Typical linux envs will notify you if you're got insufficient permissions. So what youre suggesting is an anti-pattern to whats most common.
Now you see my skepticism.

For example:
$ adb shell dumpsys activity
gives appropriate output.
Code:
ACTIVITY MANAGER Freecess (dumpsys activity freecess)
mFreecessManagedPackages --- size 132
-Uid 10192(-)-Idle(-)-Pkg com.amazon.mShop.android.shopping
-Uid 10033(-)-Idle(-)-Pkg com.sec.android.widgetapp.samsungapps
-Uid 10168(-)-Idle(-)-Pkg com.google.android.youtube
-Uid 10032(-)-Idle(-)-Pkg com.samsung.android.app.galaxyfinder
-Uid 10101(-)-Idle(-)-Pkg com.samsung.android.themestore
-Uid 10177(-)-Idle(-)-Pkg com.sec.android.app.chromecustomizations
-Uid 10197(-)-Idle(-)-Pkg com.sprint.care
-Uid 10194(-)-Idle(-)-Pkg com.sprint.ecid
-Uid 10271(-)-Idle(-)-Pkg com.sprint.w.v8
-Uid 10112(-)-Idle(-)-Pkg com.sprint.zone
So what is it @ jwoegerbauer ?
Either I've got a rooted phone and I don't know about it. Or running commands with $ adb shell doesn't require a rooted phone.

@crazycarl
In order to bring it to an end: Yes, i was mistaken, I apologize.

crazycarl said:
I dont think this true. Im fairly certain that i've not rooted my phone yet Im able to connect the USB and bring up the adb shell promp:
Code:
[email protected]:~$ adb shell
a50:/ $
Click to expand...
Click to collapse
You will get limited shell action. I don't think you have SuperUser permission so you can't change anything significant.

Related

SU request issue, help please

ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help

[GUIDE] ADB - Usage, Tips, Tricks and More!

*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.

How to make adb listen to tcpip 5555 after reboot

I have to use adb over ssh. now, everything works fine but after a reboot i have to connect my device again over usb and set adb to listen to tcpip instead of usb.
is ther a way to save those settings?
This is how it works for now. After a reboot i have to use these commands again (over usb) in order to establish an adb connection over ssh.
# adb kill-server
# adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in TCP mode port: 5555
malufor said:
I have to use adb over ssh. now, everything works fine but after a reboot i have to connect my device again over usb and set adb to listen to tcpip instead of usb.
is ther a way to save those settings?
This is how it works for now. After a reboot i have to use these commands again (over usb) in order to establish an adb connection over ssh.
# adb kill-server
# adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in TCP mode port: 5555
Click to expand...
Click to collapse
You can set service.adb.tcp.port=5555 in /default.prop or maybe /system/build.prop. But this isn't such a great idea, since it leaves you phone open to everybody wanting to gain shell access to it over the net.
And you don't need "adb kill-server" above. It's the devices adb you are restarting, not the one on your computer.
kuisma said:
You can set service.adb.tcp.port=5555 in /default.prop or maybe /system/build.prop. But this isn't such a great idea, since it leaves you phone open to everybody wanting to gain shell access to it over the net.
And you don't need "adb kill-server" above. It's the devices adb you are restarting, not the one on your computer.
Click to expand...
Click to collapse
Great thx. I'll give it a try.
Update:
Works perfectly. I modified the buil.prop. Thank you.
kuisma said:
You can set service.adb.tcp.port=5555 in /default.prop or maybe /system/build.prop. But this isn't such a great idea, since it leaves you phone open to everybody wanting to gain shell access to it over the net.
Click to expand...
Click to collapse
For tinkering purposes - well aware of the security implications here - I wanted to get adb to also listen on the mobile interface, when not connected to a wifi. Basically public debugging on the bus ride
I did not succeed though. How can adb be brought to listen on the mobile data connection?
schaggo said:
For tinkering purposes - well aware of the security implications here - I wanted to get adb to also listen on the mobile interface, when not connected to a wifi. Basically public debugging on the bus ride
I did not succeed though. How can adb be brought to listen on the mobile data connection?
Click to expand...
Click to collapse
I am in search of a similer thing.
Is it possible with port forwarding in adb ?
[email protected] said:
I am in search of a similer thing.
Is it possible with port forwarding in adb ?
Click to expand...
Click to collapse
Yes, it is possible. But 1st you must make sure your mobile operator is not blocking your connections.
Most data only SIM cards will not block connection, but only few operators allow connection to any SIM cards ( voice + data).
If you can ping your phone IP address while it is on 3g or 4g then you should be able to connect, some operators even block pinging but still allow the ADB connection.
1. connect your phone to a pc with usb
2. make sure it is visible by typing "adb devices"
3. type "adb tcpip 5555" to set up forwarding
4. once your phone is connected to mobile data (3g or 4g) go to settings -> about phone -> status -> IP address
5. from laptop.type "adb connect ip_addres:5555"
Have you tested this method on any network?
[email protected] said:
Have you tested this method on any network?
Click to expand...
Click to collapse
In Croatia, on Tele2 it works on both (voice + data) and data only cards, you are able to ping them both.
On Vip-net it works only on data-only cards and your are not able to ping them.
Also, if you are working inside a company network, the company firewall might block the connection
kuisma said:
You can set service.adb.tcp.port=5555 in /default.prop or maybe /system/build.prop. But this isn't such a great idea, since it leaves you phone open to everybody wanting to gain shell access to it over the net.
And you don't need "adb kill-server" above. It's the devices adb you are restarting, not the one on your computer.
Click to expand...
Click to collapse
I know it is really late to be saying this, but...
What a lot of people do when they need to open a port that is well-known, much like the SSH default port 22, is set a different port. Instead of 5555, use 7777 or something entirely different. It is much like a 4 digit passcode.
twistedumbrella said:
I know it is really late to be saying this, but...
What a lot of people do when they need to open a port that is well-known, much like the SSH default port 22, is set a different port. Instead of 5555, use 7777 or something entirely different. It is much like a 4 digit passcode.
Click to expand...
Click to collapse
Why not using a five digit passcode like 51423? Afaik you may use any port > 4096 and < 65536. The first 4096 are privileged ports...
guest4711 said:
Why not using a five digit passcode like 51423? Afaik you may use any port > 4096 and < 65536. The first 4096 are privileged ports...
Click to expand...
Click to collapse
Who said you couldn't?
Use any port number not already in use, but any known default assignment will defeat the purpose of avoiding intrusion. The point was that you aren't limited to 5555 exclusively.
Is it possible to target device to listen to port over wifi, without first connecting via USB?
omg no. please do NOT think that using a random port changes anything about security. I assure you it does not.
Turning off USB Debugging when its not in use seems to shut down access to 5555 - wouldn't that suffice from a security perspective? (only have USB Debugging on when you want to do ADB)
kuisma said:
You can set service.adb.tcp.port=5555 in /default.prop or maybe /system/build.prop. But this isn't such a great idea, since it leaves you phone open to everybody wanting to gain shell access to it over the net.
And you don't need "adb kill-server" above. It's the devices adb you are restarting, not the one on your computer.
Click to expand...
Click to collapse
hello! newbie here, can you please explain what is this "/default.prop or maybe /system/build.prop" Thank you
If I set this up in either build.prop or default.prop in a custom ROM, it works fine.
If I set this up in a stock MIUI ROM, it results in a bootloop, every single time.
I'm trying to figure out how to run adb tcpip 5555 in either post-fs or service.d for Magisk. The .sh script is given the correct execute permission and seems to run fine, but it doesn't actually set adb tcpip 5555 to enabled....
I just want to thank everyone for writing this thread way back in 2012, as we're STILL making good use of this information now, in 2022, when Android 11 (and up) has adb Wireless debugging options inside of Developer options... (no USB needed!).
(PSA) Using the new Android 12 TILE for 'Developer options' 'Wireless debugging' to establish adb connection over Wi-Fi without USB
I know it's been a while, but I find myself in need of adding this
Code:
service.adb.tcp.port=5555
line to build.prop on my unrooted Pixel 7 Pro. Here are some wild thoughts, as I am not an expert in rooting/unrooting:
With the unrooted phone, say I download the latest Pixel 7 Pro factory image and tinker with it, namely make the requisite change in build.prop, repackage the whole thing as a modified image, and then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?
Root the phone, make the requisite change in build.prop, and then un-root it back. Will this work? Or does the un-rooting process mess everything up, and destroy all the changes I made? (Mind you, I have no idea how un-rooting works, so please bear with me.)

[Q] How to get Wi-Fi working

I read somewhere that in order to get Wi-Fi working you need to ssh in to the phone and then run some commands? anyone know specifically how this is done?
Plays2 said:
I read somewhere that in order to get Wi-Fi working you need to ssh in to the phone and then run some commands? anyone know specifically how this is done?
Click to expand...
Click to collapse
You're not going to be able to ssh into it until after you get wifi working. You can port ssh through adb but you may as well just use adb shell.
As root:
Code:
adb shell
adb ubuntu_chroot shell
You can then debbug the networking (hopefully you have more luck than I'm having.

[Q] proscan root

Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK​
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>​7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]​
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices​
12. At the command prompt, enter:
C:\Users\entropy> adb shell​
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #​
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>​
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.

Categories

Resources