Database Info

USB tethering Sprint Touch Pro 2 running the stock WM 6.5 Rom

Alrite fellas, I know there are a ton of threads on how to tether via USB using ICS. I think I finally got the proper way to stealth tether/connect using ICS. In my case, I wasn't able to find anybody who had all the exact correct steps. I followed a few of the steps that PPCGeeks forum member "Boo Boo" posted. However, several steps were missing. The following steps will work for TP2 users who are using the stock 6.5 Sprint Rom:
1) Install DotFred's TaskManager. After install, start the program and go to the "Services" tab. Find "CM Guardian", click and hold it and then press stop. Once again, click and hold "CMGuardian" and select "Set Manual". Exit out of the program.
Soft Reset
2) Install the ICS_and_WModem_Fix cab that is attatched below.
3) Using a Registry Editor, edit the following:
Delete the "isext.dll" entry located here:
[HKEY_LOCAL_MACHINE\Comm\InternetSharing]
Extension="isexy.dll"
Change ForceCellConnection to Sprint, if it is not already done so:
[HKEY_LOCAL_MACHINE\Comm\InternetSharing\settings]
ForceCellConnection="Sprint"
You may have to create this DWORD entry if it is not already there:
[HKEY_LOCAL_MACHINE\Comm\InternetSharing]
MaxCMCon=0
I didn't need to make any changes here as it was already done. But you might have to:
[HKLM\Services\CMGuaridan]
Flags = 4 (it's a DWORD Value. if it doesn't exist. you need to create it)
Change the following if needed. If you are missing some of these entries, don't worry. There is no need to create them:
[HKLM\Software\OEM\WModem]
CheckProfile = 0
Multi-NAI = 0
WModemDUN = 0
[HKCU\Software\Microsoft\InternetSharing]
LastCellConnection = Sprint
Soft Reset
4) Then go into the Windows directory on your phone using a File Explorer and make a backup copy of the IntShr.exe file and save it to another directory. This will be your backup to save just in case you have any problems in the future.
Then go back to the Windows directory and make a copy of IntShrUI.exe. Save it to another directory. Then rename the IntShrUI.exe copied file to IntShr.exe . Copy that file and place it back into the Windows directory. A prompt will pop up asking if you want to overwrite the existing file. Select "Overwrite." You will get a message stating that this is a ROM file and it is dangerous blah blah. Ignore that. The reason to do all of this is because the original IntShr.exe is not protected against tethering and doesn't offer the Sprint/Phone As Modem option. This is what I mean:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is also the same file that pops up when you select Internet Sharing whenever you connect your phone to your PC using USB. You don't want that. BY making these changes, now every time you connect your phone to your PC via USB, and you select Internet Sharing, it will start up the correct ICS file. This is the screen you want popping up:
Now, Reboot.
5) You should make sure to turn "Data Connection" on in the Comm Manager. Connect your phone via USB cable to your PC. When the selection screen pops up on your phone (ActiveSync, Disk Drive, Internet Sharing), make sure to select Internet Sharing.
Select Sprint under type of connection, if it is not already selected.
Hit Connect In the Internet Sharing application, although it may connect automatically.
6) You're done. I know that's quite a few steps, but this was the way that it fully worked for me. If you want Wi-Fi tethering, you can install one of the numerous Wi-Fi cabs that are floating around. But do so after you finish these steps. Hope this can help someone out and sorry for beating a dead horse.

Network connection only shows "None"
Hi ,
I executed all the steps mentioned in the thread in sequence. Now only option "none" is shown under network in the ICS screen. And the connect option is disabled.

Are you running the Sprint Touch Pro 2 WM 6.5 Stock ROM?

PapaPrem said:
Are you running the Sprint Touch Pro 2 WM 6.5 Stock ROM?
Click to expand...
Click to collapse
you need to learn how to properly give credit..
first, YOU didnt figure out anything.. everything you have up there has been posted and reposted 100s of times..
"your cab" is from Mighty Mikes essential cabs thread on PPCGEEKS..
when you quote other peoples work, you need to link threads to the original posts

crazychef said:
you need to learn how to properly give credit..
first, YOU didnt figure out anything.. everything you have up there has been posted and reposted 100s of times..
"your cab" is from Mighty Mikes essential cabs thread on PPCGEEKS..
when you quote other peoples work, you need to link threads to the original posts
Click to expand...
Click to collapse
Easy there Anger Boy... You might wanna get off your little pedestal there for a moment. If you took time to actually read my post, you would notice that I stated that there are a ton of threads on how to tether via USB using ICS, but none of them fully worked for me. I also gave credit to forum member Boo Boo, whos' post is also where I found the ICS_and_WModem_Fix cab. I didn't rename the cab or claim it was mine. And if you actually searched through the "Tether" posts, you would see many posters just post that cab as a way to "help others out." But you wouldn't understand that part now would you? Perhaps you haven't been on this site long enough? Next time, why don't you try contributing something positive instead of playing "Thread Police".

PapaPrem said:
Easy there Anger Boy... You might wanna get off your little pedestal there for a moment. If you took time to actually read my post, you would notice that I stated that there are a ton of threads on how to tether via USB using ICS, but none of them fully worked for me. I also gave credit to forum member Boo Boo, whos' post is also where I found the ICS_and_WModem_Fix cab. I didn't rename the cab or claim it was mine. And if you actually searched through the "Tether" posts, you would see many posters just post that cab as a way to "help others out." But you wouldn't understand that part now would you? Perhaps you haven't been on this site long enough? Next time, why don't you try contributing something positive instead of playing "Thread Police".
Click to expand...
Click to collapse
I just posted these same direction but a different cab i found on ppcgeeks in 08 that worked on the my old touch

sak211l said:
I just posted these same direction but a different cab i found on ppcgeeks in 08 that worked on the my old touch
Click to expand...
Click to collapse
Sounds good. But did you make sure to check the Windows folder to see if you needed to replace the stock IntShr.exe (42kb) file? You may not need to, but in my case, I did. Steps 1-3 (in my OP) has been originally stated in many other threads before. But I haven't come across any thread that mentioned Step 4. For me personally, I had to learn about it through trial and error. It saves the extra step of having to start the Internet Sharing program prior to connecting the USB cable.

PapaPrem said:
Sounds good. But did you make sure to check the Windows folder to see if you needed to replace the stock IntShr.exe (42kb) file? You may not need to, but in my case, I did. Steps 1-3 (in my OP) has been originally stated in many other threads before. But I haven't come across any thread that mentioned Step 4. For me personally, I had to learn about it through trial and error. It saves the extra step of having to start the Internet Sharing program prior to connecting the USB cable.
Click to expand...
Click to collapse
yes it does everything you need i also checked the registry after install because at first i was doing the registry edit then installing the program but i installed it first by mistake then checked the registry and everything was already set so all i do is run the cab and just make sure the registry is correct and never seen number 4 either as soon as i plug the usb in my phone goes to the menu usb connect menu

sak211l said:
yes it does everything you need i also checked the registry after install because at first i was doing the registry edit then installing the program but i installed it first by mistake then checked the registry and everything was already set so all i do is run the cab and just make sure the registry is correct and never seen number 4 either as soon as i plug the usb in my phone goes to the menu usb connect menu
Click to expand...
Click to collapse
When you plug the USB in your phone and the USB To PC menu pops up and you select Internet Sharing, does the menu give you the option to select either Sprint or Phone As Modem or does it only give you the option to select USB/Bluetooth?

PapaPrem said:
When you plug the USB in your phone and the USB To PC menu pops up and you select Internet Sharing, does the menu give you the option to select either Sprint or Phone As Modem or does it only give you the option to select USB/Bluetooth?
Click to expand...
Click to collapse
mines has PC connection USB at the top and Network connection Sprint PCS at the bottom

PapaPrem said:
Are you running the Sprint Touch Pro 2 WM 6.5 Stock ROM?
Click to expand...
Click to collapse
Yes, I have Touch Pro2 6.5 Sprint Stock rom

Should be As Easy As 1-2-3!
I have been using Sprint HTC Touch Pro for a very long time, only thing you actually need is ICSInstall.cab (IntShrUI), that's the only thing you need,for my HTC Touch Pro from Sprint (stock, non-modified) I do not need any additional program such as WModem etc., after install press "ok" to restart the device, then for the first time, open your Opera browser and make the connection alive.
Then open IntShrUI and click Bluetooth PAN and Network Connection as "Sprint". That's it. No need to edit ANY files. Same thing will work on HTC Touch Pro 2, I just tried, no need to do any additional steps, HOWEVER...
NOW, my question is, everything works EXCEPT the Bluetooth PAN, for the PC Connection on IntShrUI in HTC Touch Pro, it cave me an option for either Bluetooth PAN or USB, but in the new HTC Touch Pro 2 it only offer USB, I love the Bluetooth PAN because it's... simple... wireless!
Any idea foks?

Still can't side load on my Captivate even with rooting it.

hey guys, still new to the Android game. Had a friend at work root it for me. I got rid of all the ATT junk but still can't side load. Does anyone have any ideas on how to overcome that issue.

go to general, read wiki

shuratilt said:
hey guys, still new to the Android game. Had a friend at work root it for me. I got rid of all the ATT junk but still can't side load. Does anyone have any ideas on how to overcome that issue.
Click to expand...
Click to collapse
Specifics would be helpful but my guess is that all the issues you are having have already been mentioned in other threads.
Checkout the wiki in the general section, and the other Non-Market Apps threads in this section.

Read non market apps solved this will fix your issue.
Sent from my Samsung Captivate using Tapatalk Pro

actually, read the SECOND thread on the issue. It's not 16+ pages to read.
http://forum.xda-developers.com/showthread.php?t=738376

If you don't mind using your PC to sideload, do a Google search for "Sideload Wonder Machine."
It's the easiest way to do it and you don't even have to be rooted.

Double-post / Please disregard...

Everyone is telling you what to read but not why.
You still need to enable the ability to install non-market apps. You can read the above posts on how to do it!

max_warheads said:
actually, read the SECOND thread on the issue. It's not 16+ pages to read.
http://forum.xda-developers.com/showthread.php?t=738376
Click to expand...
Click to collapse
I agree you post is a lot more organized and detail. Going to stick your thread and replace the other one.

I rooted my Captivate and then followed a guide that I located via Google. Since I am a "noobie", I am not allowed to post the link due to anti-spam rules... So, here is how to locate the link:
1) go to Google, enter the keywords "sideload at&t captivate" without the quote marks.
2) when the search results appear, look down the page for one titled "How to Enable Sideloading of Apps on Captivate" on androidforums dot com. For me it was about the eighth result down on first page.
3) when you go to the link, you might wind up on the second or third page of comments, so click back to the first page to locate the solution...
The "big idea" behind the solution is that there is a SQLlite database containing settings which the Android OS uses to determine, among other things, if sideloading of apps is allowed. AT&T, being the kind-hearted benevolent protectors of us children to keep us from harming ourselves, has shipped their Android phones with this setting toggled to prevent sideloading. The guide above describes how to copy the database to your computer, toggle the setting "on" to allow sideloading and copy the modified settings database back to your phone.
Or at a bit more granular level, the guide describes how to:
1) at the location "/dbdata/databases/com.android.providers.settings/settings.db" on the phone is a SQLite database containing configuration settings for the android OS
2) you are copying that database to first your SD card and from there to your computer
3) on you computer you are using a tool to modify a particular setting within the database, the setting which AT&T toggles off to prevent sideloading. NOTE: The tool utilized by the guide is the Firefox browser with an add-on plugin which allows viewing / modification of SQLite databases, any tool that gives you access to view/modify a SQLite database will work fine.
4) finally, you copy the modified database back to the SD card on the phone and from there back to its "real" location where the Android OS will read it.
5) When you reboot the phone, Android reads in the modified setting and sideloading should "just work"
This is my first post, hope it is helpful...
BTW, I am a user of Linux, these days mostly Ubuntu and its derivatives. I was able to perform the entire rooting and enable sideloading operation from my Linux machine without having to use Windows!! Yippeeeee!!!

[Q] ATT ONE X Wi-Fi check

I have the att version of the one x. I just rooted the phone and have sqllite installed. i'm looking for where I would go do disable the check with ATT before enabling the hotspot. I did this with my Atrix so I'm sure there has to be a key one one x as well.

I'm interested in this too........there's a folder in data/data called com.htc.teatheringguard wonder if that's it??

this is the first thing I did upon acquiring root. I think AT&T wised up a bit and removed the exact way we did it on the Atrix. I looked up the directions for the Atrix and they go like this:
Open SQLite
Go to “Settings Storage (com.motorola.android.providers.settings)”
Click “settings.db”
Click “Settings”
Find the line labeled “entitlement_check” with a value of 1
Change the value from 1 to disabled
Hit Save
Reboot
But there are two issues... There is no Settings menu after settings.db...
also...in none of the menus does it list "entitlement_check"
there is in one of the menu's a line entitled "be polite" and I just find it curious that it's there, but i'm afraid to test out changing it to disabled, as I don't know much about this stuff besides reading directions.
I think the tetheringguard.apk is going to have to be altered to make the hotspot app always think that there is a tethering plan on the account.
when i use root expl. to get to the data/data/ and data/user/0 folders that hold com.htc.tetheringguard, there aren't any files that appear to be changeable.
to a novice like me these seem like deadends, but maybe someone more experienced can take a look?

Kingo Root (still) steals your IMEI

This is probably a hell of a way to make a first post, but whatever.
So, in preparation for the wall of text upcoming, a tl;dr: kingoroot for windows (and probably the android app as well) calls "dumpsys iphonesubinfo" over adb for no discernible reason, obtaining the IMEI of every phone one attempts to root with kingoroot. In addition, the application tries to obtain some other nasty things, like the phone's GSM baseband version number and battery information, all of which are entirely useless for something claiming to just root a phone.
Ok, so first for some backstory. I recently got a prepaid ZTE paragon from best buy for 5 dollars. The hardware is pretty good for the price:
-Qualcomm 410
-1 GB RAM
-sd card slot
- IPS screen
Unfortunately, the phone is running Android 4.4.4 out of the box. Because of this, every trustworthy rooting app I could find failed on the phone, as all of the relevant bugs have been patched. So, I turned to China to give me my su jollies, and indeed, Kingoroot managed to root my phone with little trouble. This got me curious: what exactly was that windows executable doing on the phone anyway? And that's where this all begins....
I first tried to sniff the adb traffic between the computer and the phone. Unfortunately, there is no way to do this: adb sessions are isolated from one another, and so there is no real way to see what the Kingo adb thread was doing from a different shell. So, I went one level deeper and scanned ALL of the USB packet traffic on the computer with USBPcap. After opening up the hex dump, this worked a treat: I could see plaintext in the packets corresponding to adb shell commands. After several hours of skimming through the several megabyte dump, I could see roughly what the Kingo app was doing on the phone: It determines some system information (the model number, whether or not the phone is already rooted, some more unsavory stuff I'll get onto later), then copies over the apk of the splash screen that you get on your phone. When you click the button to root the phone, the executable copies over a lot of files to /data/local/tmp (some root essentials like the su binary and busybox, the main exploit binary called "kingo", and some scripts to ensure root persistence after the main root), chmods busybox, the root exploit, and su to give execution rights, and runs "./kingo kingo", which after several seconds creates a temporary instance of the su binary which you can call over adb at that point. (Interestingly, this must be run as "./kingo kingo" to work; anything else causes a segfault. Some form of password protection, maybe?) It then runs some scripts and rearranges some files with this newfound root access to maintain persistence, deletes all the files it brought over, and quits.
My main interest here was determining the root exploit Kingo were using to root the phone, and so after factory resetting the phone, I rooted it again using the app and copied over any files I could see in /data/local/tmp from a second adb instance. This gave me the set of files Kingo was using to root the phone, and after another reset, running the magic exploit offline indeed gave me temporary root access to the device (I haven't fully figured out how to make persistence work, but that is not the main issue here). So, after some hunting around on the internet to see if anyone else had gotten any information on this magic executable, I found some threads here on XDA claiming that Kingo was stealing some information about your phone and sending it to the Chinese mafia or something. Naturally, I was somewhat upset by this: I was running this in my good Windows VM! Now I have to reset it! But this again piqued my interest, and so I went to see if Kingo really was doing anything malicious.
For those who are unfamiliar with the story, Kingo was caught obtaining the IMEIs of phones which were rooted with the app. This upset a lot of people, and so with version 1.2.2, the Kingo developers claimed to have removed the ability to capture phone IMEIs. (Of course now, I know this is a pile of ****, but let's keep going.) So, first things first, I pulled out my packet log of the rooting endeavor and searched for my ZTE's IMEI. And with this, I found in the packet log:
Code:
529 17.074812 5.2 host USB 58 URB_BULK in:
Device ID = 865895021744484
Oh dear....
(Note that I'm not planning on using this phone for any networking over the cellular modem. I don't really care if this phone's IMEI is stolen. That is actually the phone's IMEI, btw)
Looking a little higher into the packet log revealed that Kingoroot was calling "dumpsys iphonesubinfo" over adb shell to obtain this information, and looking around some more revealed the following gems:
Code:
535 17.102832 host 5.2 USB 56 URB_BULK out
getprop gsm.version.baseband
and
Code:
547 17.124868 host 5.2 USB 43 URB_BULK out
dumpsys battery
Now I don't know about you, but I can't for the life of me figure out why a rooting program needs access to my IMEI, my GSM baseband version (!) and my battery information just to root the phone. To add insult to injury, all of this is done after
Code:
388 13527122 5.2 host USB 108 URB_BULK in
Qdevice::ro.product.name=P821A21;ro.product.model=Z753G;ro.product.device=faerie;
was sent over by the phone, indicating that all of the identifying device information that should have been sent was already sent.
This is only the shady stuff kingo is doing before the root happens too! After root privileges have been obtained, there is an unsettling amount of time taken until the application claims to be done and when it appears to actually be done.
I haven't looked through the whole packet log yet, but just from a brief look at the post-root adb commands packet 15710 has the executable calling "getprop", and who knows what the Chinese mafia are going to do with all of that information!
So, in conclusion, I set out to figure out how KingoRoot for windows roots android phones, but also determined that Kingo never really stopped doing shady **** as they claimed. To anyone who wants to take a look at the files I found for themselves, here (www (dot) filedropper (dot) com (slash) kingo)(I still can't post urls) is a link to everything I found during my little experiment. In that zip is the USB packet log for others to find some interesting information in (just open in wireshark) , the files kingo uses to root my Android 4.4.4 phone (I humbly defer to people who know more about binary reversing than I do to figure out what the hell that binary does), and some instructions to rooting a ZTE paragon z753g with this binary should you happen to have such a phone yourself. I realize that disclosing a root executable is not a particularly good idea, but considering the process to obtain it is so straightforward, I don't think not providing it is stopping anyone who wants to do something nefarious. If someone tells me to take it down, I will, however.
In addendum, I have a couple requests of anyone reading this. If you have a phone you don't particularly care about, download USBPcap, ADB, and the kingoroot executable and get the USB packet log during the whole interaction and the contents of /data/local/tmp (just copy that directory to a known safe place, like /sdcard/Download). Im curious if
1) Kingo actually uses different exploits for different phones and
2) the IMEI and baseband firmware version are always sent over
Finally, if anyone out there is good at binary reversing, I am curious about what exploit the "kingo" file is using to root the phone. When I look again at this process, nothing particularly screams that this actually requires the debugging bridge to work; presumably a rogue .apk could do the same thing. (Or worse yet, an ACE exploit like Stagefright) Although the Kingoroot Android app did not root the phone I used for this experiment, I have reason to believe that the same or a similar exploit is being used there, as opening a simultaneous adb shell reveals su privileges being obtained at a certain point of the process, although presumably the process fails because the persistence creating scripts didn't work for some reason.
So, in actual conclusion, Kingoroot is untrustworthy, panic and run

Thanks for this thread.
Kingoroot didn't root the phone, but stole the IMEI. This is 100% theft.
---------- Post added at 05:56 PM ---------- Previous post was at 05:35 PM ----------
zzazzdsa said:
This is probably a hell of a way to make a first post, but whatever.
So, in preparation for the wall of text upcoming, a tl;dr: kingoroot for windows (and probably the android app as well) calls "dumpsys iphonesubinfo" over adb for no discernible reason, obtaining the IMEI of every phone one attempts to root with kingoroot. In addition, the application tries to obtain some other nasty things, like the phone's GSM baseband version number and battery information, all of which are entirely useless for something claiming to just root a phone.
Ok, so first for some backstory. I recently got a prepaid ZTE paragon from best buy for 5 dollars. The hardware is pretty good for the price:
-Qualcomm 410
-1 GB RAM
-sd card slot
- IPS screen
Unfortunately, the phone is running Android 4.4.4 out of the box. Because of this, every trustworthy rooting app I could find failed on the phone, as all of the relevant bugs have been patched. So, I turned to China to give me my su jollies, and indeed, Kingoroot managed to root my phone with little trouble. This got me curious: what exactly was that windows executable doing on the phone anyway? And that's where this all begins....
Click to expand...
Click to collapse
Does Helium Backup work on this phone? I also bought this phone for $5.
I don't really need to root this phone. I just need to disable some System apps for my privacy.

Some members want root at any cost. You're not posting anything that's not already known.
But as with anything, flash at your own risk. That is the bottom line in this hobby.
Read, research, decide. The responsibility is on members to flash what they want. So, use it or dont. Not much more to say. :good:

And SU ??
Sent from my SM-A700FD using Tapatalk

Awesome post. Thanks!
Two comments/questions:
1. I bought two of these phones for my girls (3 years old and 1 year old). I want to load some games and some videos. I need to root so that I can load apps onto the SD card, etc. Should I worry about using Kingoroot or just go for it? They aren't going to be doing email.. at most taking pictures probably. Maybe Dropbox access. Pandora. So some (of mostly my) credentials going over the air.
2. The link you didn't post (see what i did there?) doesn't work any more. Care to upload it elsewhere? Feel free to PM me if you want.
Edit: I should also say this.. these are the only android phones I've ever owned. But I do consider myself very tech savvy (few programming languages, very comfortable at a unix command line, etc). So if there's any newbie android advice for securing a phone for kid use I'm happy to hear it!). Thanks

I have only used KingRoot on a Blu device and then which, gave to my father.

Thanks for all the work, another vendor of my list.

couldn't get Kingo to work
So inspired by the above post I tried Kingo and it didn't work. After much screwing around with Windows in VirtualBox I got Kingoroot installed and it even said it rooted it - but I couldn't get anything (i.e. SuperUser) to work correctly. Mind sharing your method for getting it to work?

@zzazzdsa You gotta do some research on Kingroot
They claim on their website that they parented up with XDA....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Newyork! said:
@zzazzdsa You gotta do some research on Kingroot
They claim on their website that they parented up with XDA....
Click to expand...
Click to collapse
Nope. Lol
No affiliation. But anyone can put anything out there on the interwebz.

So i haven't had much time to play around with this some more, but I can post a rough guide to making a sniffing setup if you want to play along at home.
First, you're going to need a windows computer. It doesn't matter if it's virtualized, it just needs to have USB support enabled (via native support in VMware or the PUEL extension pack in VirtualBox)
Second, you will need to download adb for windows, USBPcap, and wireshark. All of those can be found with minimal googling. Once you have installed all three, you are ready to go.
Plug in your phone, enable adb on the phone, start USBPcap and an adb shell, and then start kingoroot.
Let kingoroot do its thing. While it is rooting the phone, pay close attention to the directory /data/local/tmp over adb. If anything interesting appears there, copy it over to a safe directory, like the emulated SD card.
Once the phone is rooted, close USBPcap, open wireshark, and comb through the packet log with a fine-toothed comb to find plaintext adb commands which will make the exploit work. A useful tip: the packet log will be extremely long, but almost all of the length will be due to the packet capture picking up file transfers as well. You can filter out these long file transfer sequences without losing any useful information.

zzazzdsa said:
So i haven't had much time to play around with this some more, but I can post a rough guide to making a sniffing setup if you want to play along at home.
First, you're going to need a windows computer. It doesn't matter if it's virtualized, it just needs to have USB support enabled (via native support in VMware or the PUEL extension pack in VirtualBox)
Second, you will need to download adb for windows, USBPcap, and wireshark. All of those can be found with minimal googling. Once you have installed all three, you are ready to go.
Plug in your phone, enable adb on the phone, start USBPcap and an adb shell, and then start kingoroot.
Let kingoroot do its thing. While it is rooting the phone, pay close attention to the directory /data/local/tmp over adb. If anything interesting appears there, copy it over to a safe directory, like the emulated SD card.
Once the phone is rooted, close USBPcap, open wireshark, and comb through the packet log with a fine-toothed comb to find plaintext adb commands which will make the exploit work. A useful tip: the packet log will be extremely long, but almost all of the length will be due to the packet capture picking up file transfers as well. You can filter out these long file transfer sequences without losing any useful information.
Click to expand...
Click to collapse
How did you get kingoroot to root your ZTE Paragon? I thought this phone cannot be rooted.

Get a virtual Windows machine running. Download the pc app at kingoapp com. Plug in, root. The problem is getting apps like super su to work given lack of /system write access. get that figured out and I'll give you a few gold stars. Because from what I can tell that's all that's holding me back from moving my apps to the sd card.

OMG LOL!
Then What? They are going to sell my imei number

With as much due respect for someone I've never met: so what? It's a $5 phone. If they get your imei and something bad happens I'll personally refund your $5.
If you're really nervous about that run your virtual machine thru a mitm proxy and filter out anything that looks like your imei.

Sounds like a very shady enterprise overall.
Wasn't planning on using it anytime soon but thank you for the heads up.
Just goes to show, when in doubt come here first.

Hi, my only concern is many novice use wifi at work is there a risk to hijacking a system via
Wifi, if the imei is the security password key used
By many phone services that allow access to towers.

Sweet i didnt know that thanks for the information.

Imei is not a security password.
It's used to identify the phone when programming a number to it (which then gets stored on your sim card)
Verizon won't even tell you the imei associated with a line unless your the account holder.
Curious what the mobile app installation of kingroot saves.
Sent from my unknown using XDA Free mobile app

wonderful article
iam the victim of the kingroot imei stealing

[ROOT][MOD][HOW TO] Disable Presidential Alert Text Messages EASY METHOD

DISABLE PRESIDENTIAL/ CMAS ALERTS-ALL COUNTRIES
I'd like to say the original post about how to do this is here: https://forum.xda-developers.com/showthread.php?t=1829681
This is an easier, alternative method that only takes a few minutes. Since September 20Th 2018 is closing upon us fast, here is a method to get rid of the emergency broadcasts.
DISCLAIMER:
Always have your phone backed up in TWRP and also for safety one should create a copy of the XML file being addressed. I am not responsible if you brick your phone. (Luckily with this method it is near impossible to do so).
NEEDED:
-Rooted Android
-Quick Edit Text Editor (https://play.google.com/store/apps/details?id=com.rhmsoft.edit)
GUIDE:
-download quick edit and open the application
-in the app, select internal storage
-go to the parent directory "/ "
-go to "data" then "user_de" then "0" then "com.android.cellbroadcastreceiver" then "shared_prefs"
-open the file "com.android.cellbroadcastreceiver_preferences.xml"
-change presidential value to "false" and whatever else you'd like to be changed
-press back button and save changes
-restart your phone
(Some phones may not have the file in that specific directory. If not refer to the original guide).
This method was tested on a Moto Z2 Play US Retail edition running 8.0.
Please keep the ethics of whether one should disable this feature or not out of this forum. Thanks
PICTURES:
https://ibb.co/fNQwqU
https://ibb.co/h16Ec9
https://ibb.co/iue0H9
Also this can be done with an unrooted phone but you'll need to edit the file on the computer and save it that way.

ihateverizon1 said:
DISABLE PRESIDENTIAL/ CMAS ALERTS-ALL COUNTRIES
I'd like to say the original post about how to do this is here: https://forum.xda-developers.com/showthread.php?t=1829681
This is an easier, alternative method that only takes a few minutes. Since September 20Th 2018 is closing upon us fast, here is a method to get rid of the emergency broadcasts.
DISCLAIMER:
Always have your phone backed up in TWRP and also for safety one should create a copy of the XML file being addressed. I am not responsible if you brick your phone. (Luckily with this method it is near impossible to do so).
NEEDED:
-Rooted Android
-Quick Edit Text Editor (https://play.google.com/store/apps/details?id=com.rhmsoft.edit)
GUIDE:
-download quick edit and open the application
-in the app, select internal storage
-go to the parent directory "/ "
-go to "data" then "user_de" then "0" then "com.android.cellbroadcastreceiver" then "shared_prefs"
-open the file "com.android.cellbroadcastreceiver_preferences.xml"
-change presidential value to "false" and whatever else you'd like to be changed
-press back button and save changes
-restart your phone
(Some phones may not have the file in that specific directory. If not refer to the original guide).
This method was tested on a Moto Z2 Play US Retail edition running 8.0.
Please keep the ethics of whether one should disable this feature or not out of this forum. Thanks
PICTURES:
https://ibb.co/fNQwqU
https://ibb.co/h16Ec9
https://ibb.co/iue0H9
Also this can be done with an unrooted phone but you'll need to edit the file on the computer and save it that way.
Click to expand...
Click to collapse
Trying this on my Nexus 5 (Hammerhead D821) and while I can find and edit the file, it looks like the line pertaining to presidential alerts is missing.
Should I edit it in and set it to false?
Also, when I rebooted and checked the Emergency Alerts config in the Settings app, the boxes were still checked/active.

The new values re-enable themselves upon rebooting.
Any thoughts on how to make them permanent?

Update from my previous post: I've used Titanium Backup to freeze Cell Broadcasts and then an su terminal to remove /system/system/priv-app/CellBroadcastReceiver/CellBroadcastReceiver.apk completely. Confirmed the .apk file did not come back after reboot.
Do the XML files still need to be edited? I couldn't find the files in the original path, I had to go elsewhere and unfortunately did not write down where I found them (there were 2 XML preference files.)
Also, fossils-n-dents definitely deserves an answer. I don't mean to try to draw attention away from his/her question.

What ELSE can they do with carrier authorisation for WEA?
We had the "Presidential" Wireless Emergency Alert go USA-wide on 03 October (I'm roaming from Europe so this was a big shock). I'm less concerned with how to disable alert messages than any back door that WEA compatibility might provide carriers to manipulate the phone beyond sending a 90-character text-only message.
Can anyone post evidence that com.android.cellbroadcastreceiver & other service apps don't provide an opportunity for the carrier to control, shut down, commandeer or enable surveillance on the phone? FYI I'm not an Android developer but can read code & comments, I just don't know where to look....

CelticWhisper said:
Update from my previous post: I've used Titanium Backup to freeze Cell Broadcasts and then an su terminal to remove /system/system/priv-app/CellBroadcastReceiver/CellBroadcastReceiver.apk completely. Confirmed the .apk file did not come back after reboot.
Do the XML files still need to be edited? I couldn't find the files in the original path, I had to go elsewhere and unfortunately did not write down where I found them (there were 2 XML preference files.)
Also, fossils-n-dents definitely deserves an answer. I don't mean to try to draw attention away from his/her question.
Click to expand...
Click to collapse
Since you are using titanium Backup, why don't you just backup and uninstall cell broadcasts 9 app?

rphair said:
We had the "Presidential" Wireless Emergency Alert go USA-wide on 03 October (I'm roaming from Europe so this was a big shock). I'm less concerned with how to disable alert messages than any back door that WEA compatibility might provide carriers to manipulate the phone beyond sending a 90-character text-only message.
Can anyone post evidence that com.android.cellbroadcastreceiver & other service apps don't provide an opportunity for the carrier to control, shut down, commandeer or enable surveillance on the phone? FYI I'm not an Android developer but can read code & comments, I just don't know where to look....
Click to expand...
Click to collapse
Cell broadcast receiver has no permission to use anything except (send and receive SMS messages).