Database Users

Remove autoupdate Market

How i can remove autoupdate of market?
I open market and have new version. Then i go on application, uninstall update and have old Market. After some time i have new market again.
New market on my wildfire is very slow and FC, and if i have luck to find something, get error to insufficient disl space or app is not compatible.....
With old Market don't have problems. And i want remove autoupdate of Market..
Please someone...

The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
what if I don't have donate version?

dengseng said:
what if I don't have donate version?
Click to expand...
Click to collapse
Simply put.......... get it, or find a different app with root access to freeze it.
We suggest titanium because its the best at what it does, and is worth every penny to a serial flasher.
That sounds a bit wrong!
Sent from my HTC Wildfire using xda premium

Titanium don't help me
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market

mozvatic said:
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market
Click to expand...
Click to collapse
How to put market back in system using titanium backup???

Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.

Yeh but not everyone is as fluent as you in adb, damn took me 4 days just to get it setup correctly and now a month later I'm still learning the basics. With TB its a simple long press on the app and freeze but if you don't have adb its a long process installing for first time and then learning the commands.
Sent from my HTC Wildfire using xda premium

4 days to download the SDK and run it? Did you order a new PC in the process?
EDIT: Consider installing ConnectBot or Android Terminal Emulator. That way you don't need adb and the soft keyboard is good enough for the occasional tweak.

Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.

You're probably completely right about that, sorry for being a "smartass".

henkdv said:
Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.
Click to expand...
Click to collapse
I tried that but I couldn't update any app from the market when disabled.
EDIT: it is not because of that but after removing market udpates it behaves strange, seems that I am able to install 1 or 2 updates but any successive update fails. I will try to get the log to see what is the problem.
EDIT2: seem to be caused by low memory

That's odd, mine still auto-updates applications (but not the market itself).

antish said:
How to put market back in system using titanium backup???
Click to expand...
Click to collapse
Yes, please explain me someone!
Thanks!

Scratch0805 said:
Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.
Click to expand...
Click to collapse
Totally agree. I to this day still have no idea how to use adb or fastboot!!! When I have tried I have failed miserabley lol.
On topic, I personally just deleted market updater from the rom zip before I flash the rom and have no problems with AP updates.
Lol I must be a smarter arse to get away without using sdk, adb or fastboot for so long.
sent from my wilderbeast:buzz

you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.

cceerrtt said:
you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.
Click to expand...
Click to collapse
worked for me thanks a lot bud

cedriccc said:
worked for me thanks a lot bud
Click to expand...
Click to collapse
I just repeated what henkdv wrote before. ;-)

And I got the idea from The_Complete_Noob
{
"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"
}

Root kindle fire hd 7.2.2/7.2.3 success!!

After several hours i have finally been able to root my brand new kindle fire hd which came preloaded with 7.2.2. While setting up it updated to 7.2.3 on its own. Anyways here are the steps i took:
Prereq:
1. Download the ADB Drivers and QemuRoot method files. http://forum.xda-developers.com/showthread.php?t=1893838
2. Download Binary v17 Method http://forum.xda-developers.com/showthread.php?t=1886460
3. Download and install the latest java. http://www.java.com/en/ This is a very important step in which allowed me to succesfully root my device.
Steps:
I recommend uninstalling all drivers in order to start fresh and do a factory reset on your kindle.
1. Install ADB drivers. Extract Qemu Root and Binaryv17 files.
2. Open cmd run as admin and execute runme.bat from binaryv17.
3. Select Method 1 and your kindle should have a screen pop up requesting a restore.
4. Simply tap on Restore on your kindle and it should reboot after that. Kindle will be slow and sluggish. Thats ok.
5. After Binaryv17 is done run qemuroot.bat from Qemuroot method.
6. Choose option 1 to root.
7. Executable should go through different steps in order to root your kindle.
I saw people posting about not being able to root 7.2.2/7.2.3 devices which have not been rooted before. I can confirm it does work if you follow the above steps. The trick that it for me was the installation of JAVA. I kept getting multiple errors when i did not have it installed on my computer. Hope it works for you all.

Thank you very much vida69!
I used Windows 7 Ultimate 64 sp1
installed the lastest Java
Kindle Fire ADB drivers.exe --- 8,96 MB (9.402.392 bytes)
Kindle factory reset ***
Binary v17 Method
QemuRoot method
I bought my Kindle Fire 7 HD 32g last week, my Kindle was version 7.2.2 from factory, and updated to 7.2.3 (have not been rooted before)
I did a factory reset, *** and then without registered my Kindle with my Amazon account, and the device Language >English (USA), I followed the vida69's instructions step by step.
and my Kindle is rooted

Results of Updating MY KF HD 7" to 7.2.3
vida69 said:
...I saw people posting about not being able to root 7.2.2/7.2.3 devices which have not been rooted before. I can confirm it does work if you follow the above steps. The trick that it for me was the installation of JAVA. I kept getting multiple errors when i did not have it installed on my computer. Hope it works for you all.
Click to expand...
Click to collapse
Thank you for this information --although my case is a bit different. I rooted my Kindle Fire HD 7" when I first got it and it had &.7.1.?/3. Put Google play on it, Titanium BU, Screenshot Es, and Root Explorer. Disabled the OTA updates (I did not get affected by either 7.2 or 7.2.3!). However I was interested in trying the 7.2.3. So I downloaded it and did the upgrade.
The update was smooth and provided me with the latest including Swype Keyboard (especially for the Swype Keyboard).
Much to my surprise, however, every single app that I had sideloaded or purchased and loaded from Play after I first rooted was still there! And all of them were functional. Except that all of the "Root-requiring" apps won't work now (Tintanium, Screenshot ES and Root Explorer in the RW mode).
The rest are there, and I can still access the Play store . . . So I will try the root process using your tips, but have no hurry since I have my apps and market too --not bad. Only thing is I will have to get root eventually so as to turn off the future OTA updates!
Really surprised since on my original Kindle Fire, whenever I updated it basically wiped the machine clean. This update was like flashing a rom and not clearing the cache or the dalvik or (especially) not doing a factory reset! I am surprised it worked!

Kindle Fire HD 7" 7.2.3
So i didn't even know my KF updated from 7.2.2 to 7.2.3. I previously rooted 7.2.1. so I already had a pretty good idea of what needed to happen. One thing that I will note is that when I plugged my kfhd in I opened a cmd prompt and typed in "adb devices" when my serial number showed up I knew that I could proceed with the scripts.
Hope it helps.
ded

Glad to hear you we able to re-root. We've got some discussions going as to how to can disable future updates.
Sent from my KFTT using xda premium

Thanks a lot for putting together a step-by-step guide!
Please keep it updated.

hi everybody!
i'm on windows 7 professional 64 bit and i have a kindle fire hd 7.2.3. i'm trying to root my device but i've got always the same problems: when i plugin my kindle and run "Runme.bat" it can't find the device. in fact when i run the command "stuff\adb devices" the list is empty. I've followed all the steps in the guide! i'm lost
ps sorry for my english

After running "runme.bat" its still stopping at *daemon started successfully*.......
Still does not show anything when I run "adb devices". But does show up under Device Manager.

fireslayer26 said:
After running "runme.bat" its still stopping at *daemon started successfully*.......
Still does not show anything when I run "adb devices". But does show up under Device Manager.
Click to expand...
Click to collapse
I have the same problem. The program just doesn't recognize the device even if the adb drivers are installed. Have Widows 7 x64 and normal ADB Drivers 29.08.2012.. Hope, that CM10 will be published soon..

root useless
i follow you steps, gets rooted but can't able to install file exper app. still have superuser app. runs smooth. any help how to install apps now because I can't use amazon due to geographical restrictions in Australia.
if i can't install any app root is useless.

fireslayer26 said:
After running "runme.bat" its still stopping at *daemon started successfully*.......
Still does not show anything when I run "adb devices". But does show up under Device Manager.
Click to expand...
Click to collapse
I have the same problem. I´ve tried all step that mentions above. :S

Work like a charm for me; no need to do de qemu root, just the root many android did it for me, i did have root access before 7.2.3
Thanks a lot!

hector333 said:
Work like a charm for me; no need to do de qemu root, just the root many android did it for me, i did have root access before 7.2.3
Thanks a lot!
Click to expand...
Click to collapse
Works for me too. No need for qemu. I have not rooted this before and it auto updated to 7.2.3.
First I got permission errors, but after I restored to factory settings I was able to root it. I used a separate computer to do it though so I'm not really sure if it really is the reset to factory settings that did it.
Also, I had to download Android SDK to get the new adb because adb packaged with the root tools can't detect the device.

Success (!)
Hello all, I am a noob to THIS forum. I have successfully rooted according to the above mentioned guideline, but not without one issue.
For all those doing this for the first time, just remember at the "Restore" screen mentioned on step 4 of vida69's post, it would be best that you use a simple password for the restore point, as just pressing "Restore My Device" does not allow the exploit to continue. :good:
Found this out the hard way.
Happy rooting!:good:

engwan said:
Works for me too. No need for qemu. I have not rooted this before and it auto updated to 7.2.3.
First I got permission errors, but after I restored to factory settings I was able to root it. I used a separate computer to do it though so I'm not really sure if it really is the reset to factory settings that did it.
Also, I had to download Android SDK to get the new adb because adb packaged with the root tools can't detect the device.
Click to expand...
Click to collapse
The adb.exe replace from SDK solved the issue from me too.

Duplicate Thread?
OP: It seems like this thread duplicates http://forum.xda-developers.com/showthread.php?t=2035334 Particularly if you believe Java is key why not post it there?

RustedRoot said:
OP: It seems like this thread duplicates http://forum.xda-developers.com/showthread.php?t=2035334 Particularly if you believe Java is key why not post it there?
Click to expand...
Click to collapse
I was having some difficulties doing this last night and I found a solution. Here's some proof that I'm rooted:
{
"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"
}
All I did was enter my SDK Manager and installed the following driver: Google USB Driver
Then ADB DRIVERS showed my Kindle Fire HD 7".
Note: I was never rooted before, so people saying that it only works if you were rooted before, that's a lie!

yadavshyam said:
i follow you steps, gets rooted but can't able to install file exper app. still have superuser app. runs smooth. any help how to install apps now because I can't use amazon due to geographical restrictions in Australia.
if i can't install any app root is useless.
Click to expand...
Click to collapse
Just download a file explorer from any other store >google search> es file explorer apk> download and send to your email as attachment, open the email in the Kindle, install the attachment

got KFHD rooted in WIndows 8
I use windows 8 and got problem with connecting to kindle fire hd 7" to root.
The adb.exe from Binary v18 does not see my kindle fire ( i installed driver from this http://forum.xda-developers.com/showthread.php?t=1893838)
I decided to uninstall the the Amazon adb driver, and installed google usb driver from android sdk.
The adb.exe from Binary v18 still does not see my kindle fire, but the adb from android sdk see it.
At last i have changed something in RunMe.bat from Binary v18, put them all in one folder.
Run the RunMe.bat first then the rootQemu.bat.
here is the file:
http://www.4shared.com/zip/57kOoY4Z/tool_root_KFHD_723_windows_8.html
Sorry for my bad english

Success Rooted again one more time !!!
Follow the steps above, as superuser CMD prompt. Install Java and run Runme.bat then menu.
after that I side loaded Fileexpert to give root permission to move Vending apk and google services.
Due to Geographical Restrication I was unable to use Amazon Appstore. That why I have to use this method.
Now I am rooted with version 7.2.3 user.....and Google market 3.8.17 installed.
For user Outside US use these steps.... even you had new kindle fire HD with preinstalled version 7.2.3.
Anyway thanks to all who make this happens.:laugh:

[SOLVED] Win7/8 ADB Driver - VZW G2

FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
{
"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"
}

Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425

Huskehn said:
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Click to expand...
Click to collapse
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.

Yea i've tried the drivers from LG's site and the drivers that come on the phone itself. Definitely no luck so far.

Darkestred said:
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Click to expand...
Click to collapse
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.

drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
Software update would probably break current root method though sadly.

bose301s said:
Software update would probably break current root method though sadly.
Click to expand...
Click to collapse
ADB > root! ADB is usually essential to achieve root anyway.

It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319

emplox said:
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
Click to expand...
Click to collapse
This sucks, now we wait for a software update... without the ability to use ADB or any way to fix it. Oh well, worse things have happened.

I just got off the phone with LG. They specifically told me that there are no drivers that currently work on the VZW G2 and they should have the released 'in less than a week' and it should solve all ADB issues. Not sure I believe it...but I guess we'll see.

emplox said:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)

chrisexv6 said:
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
Click to expand...
Click to collapse
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version

ok i'm having issues with getting adb to find my device and this is an old thread and the chinese root wasn't working right. anyway to get the phone to list in adb yet, not using the chinese method?
Edit: could drivers from my previous phone have anything to do with this?
Edit2: Still could use an answer just in case, but i just realized that i haven't had to use adb on a device since before 4.2.2 so i possibly need to update my abd from pdanet, so i'll give that a go later tonight. but any other help would be appreciated. thanks in advance

drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app

bigox said:
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
We figured out how to enable ADB a while ago. You need to plug in your phone to PC, select Internet then Ethernet (or something similar) instead of Media Sync or Charge Only. Also ADB must be enabled in Settings. Then, it should show in PC devices, you can install the Google ADB driver, and use ADB. First time using it, your phone should pop up with an RSA key window to allow ADB.

1. Install drivers can be found here: http://d-h.st/fBw
downloaded this file but i dont see how to install it. no .exe or anything
how do i install drivers? http://i.imgur.com/J5dax87.png
thanks
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Click to expand...
Click to collapse

Having the same problem
I have the Verizon phone and tried using the 3.1.1 driver on Windows 7 (latest driver linked on the rooting post). When I went to the LG website and downloaded the 2.11.1 driver there, everything worked perfectly and I can see the phone on the PC using ADB devices command.

question:
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
will this work for d800 d80010o?

does this ( VZW LG G2 Drivers) work for at&t g2 also?

It will works for Sprint LS980?

Root method likely possible via modified Binary method...

sa·yo·na·ra
ˌsīəˈnärə/

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
{
"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"
}
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Just wanted to say thanks for helping the cause.

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Well at least things are moving here. It's been so sad seeing no development on this thread. I have the KF HDX 7" and willing to offer mine for testing. I've been itching to see at a least root. I also did run the Bin4ry method and the restore reboots but doesn't do anything else.

Really? Unless that's new with the hdx, any backup/restore should work fine. Even if its files are corrupt.
Sent from my KFTT using xda app-developers app

Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app

GSLEON3 said:
Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app

r3pwn said:
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.

You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

good to hear this, hope the rooting method coming out soon!

stunts513 said:
You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah, I've tried just about everything I've ever seen or done to resolve abd issues since 2007. Still a no go. Going to give usb otg a try. Otherwise it's RMA & start over. While the SU binary is in place, I still cannot access it. Calls to SU or trying to open the SU app cause an instantaneous FC & reboot.
I'll tell you though, I really like the tablet. Awesome display & the SD800 w/Adreno 330 flat out rocks. This is totally what the Nexus 10 should have been.
I've also been able to determine that Motorola is the OEM. There are Motorola backup files native to the device at least. I am also going to run this weekend & pick up a 1k transistor, to make a Motorola factory fastboot cable, since I gave mine away with an Xperia tablet. With the factory cable, I should be able to issue fastboot commands. That may enable me to devise a BL unlock.

GSLEON3 said:
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.
Click to expand...
Click to collapse
How are you sure that you got it into xbin?
Sent from my iPod touch using Tapatalk

Guide: How to use OnePlus dialer with call recording in OnePlus 8T/Nord

Hey everyone!!
Greetings from my side. We were trying hard to get 100% working oneplus dialer and messaging app in oneplus 8t. and Yes, We have successfully done it.
I am very happy to share the guide with you all
WITHOUT ANY ROOT METHOD: (Thanks to some anonymous help for non-rooted )
- oos11 required
-Please download this OnePlus Dialer: Link
-Install it and open it, set as default.
-Give all required permissions only.
-Enjoy guys, this dialer app has no bugs at all.
-If you want to use OnePlus contacts and message app please download them from old method below, these two has 1 minor bug which is not noticeable in daily life, So enjoy them at fullest without rooting your device.
Root methods below:
Requirements:
- oos11
-Root
-Magisk
- OnePlus Apps v1.0 Module
-Your own responsibility before following the all steps
To root your device with magisk please follow this amazing guide by @DroidFreak32 :
- https://forum.xda-developers.com/oneplus-8t/how-to/guide-how-to-root-oneplus8t-kb2001-t4178675
NEW METHOD(Recommended): Big thanks to @shadowstep for your contribution and providing us this amazing module.
1. Download OnePlus Apps v1.0 Module from the above link.
2. Open Magisk App and select it to flash.
3. You will get Option which app you want to install from all three apps(Contacts, Dialer, and Messaging).
Because few users do not want to install all of them together and only want to install a particular app.
4. You can select them using volume keys: Volume Up for Yes, Volume Down for No. (Refer Screenshot for better understanding).
{
"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"
}
5. Reboot and voila, Apps has been installed successfully.
6. Please make them default apps and give all required permissions.
7. Clear Catch for dialer/messages/contact app before using them.
8. You are ready to go. Thank you.
Points to be noted:
-These apps are not permanently stored in the system storage because we cannot write in the android 11 system, So do not remove/disable magisk. Wait for TWRP to come up.
- No need to disable Module while doing OTA.
-You will not face any issues while using these apps. Reboot will not remove these apps unless you remove/disable the magisk module manually.
- If OnePlus dialer comes with your 8T and call recording is locked in your country, please download this app and enable it without even rooting your device. (This point is not for google dialer users).
- Same as other OnePlus phones, you can see the recording files in the dialer settings itself (Find out screenshots below) OR
Path: android/data/com.oneplus.communication.data/files/Record/PhoneRecord
OLD METHOD:
Please download the required dialer apk from this link:
https://drive.google.com/drive/folders/1814cAPa4y1yP2lJfvIQwkZTmoajxuEXi?usp=sharing
If you need messaging and contact app as well. I have shared it in the above link.
- Download the Busybox Module in magisk
Open the hamburger menu again like before, then head to "Downloads." In the search bar, do a search for the term "busybox" to locate the next module for this guide. Tap the download arrow once, then go to "Install" to start the install process. Once finished, tap the back arrow to return to the previous screen.
-Download the App Systemizer Module
In the search bar for the "Downloads" section, do another search for the term "app systemizer," then repeat the process like before to get the module installed. Once this one finishes installing, you can go ahead and hit the "Reboot" button at the bottom to restart your device.
-Install the Terminal App
To use the App Systemizer module you downloaded in Step 3, you'll first need to access a terminal. The module is entirely command-line based, which is why you also needed the Busybox module — it allows you to use more advanced commands with superuser permissions.
Play Store Link: Termux
-Store the dialer in some of your specific location which is provided in the above google drive link.
-Systemize the OnePlus Phone App
Open the Termux app, then type in the command below, followed by: (Please do not use " in all steps below commands)
1. "su"
When you're prompted to do so, tap the "Grant" option to give Termux full superuser privileges to your system.
2. Now that your superuser permissions have been granted, type in the next command followed by enter.
"systemize"
This command will immediately launch the App Systemizer module interface for the first time. This is easily the best way you can turn any user-installed app into a system app with minimal effort.
3. Choose option 3 only which is via .apk (Choice 1 & 2 not working in our 8T). Choice 3 was the best way to make the dialer work in 8T.
4. Now give the apk location. For me, I have placed the apk directly into storage. Enter the following line.
"/storage/emulated/0/Phone_Dialer.apk"
5. Now type 2 to install to /system/priv-app and then reboot the device.
6. Please make oneplus dialer as default phone dialer. It is very important step.
7. Now app has installed successfully. Please disable google dialer for now.
8. Please give all permissions to oneplus dialer from phone settings(calls logs,contacts,files and media,microphone, phone,SMS)
If you are facing any issue in using systemizer app, please prefer this link . This link also contains screenshots for first few steps.
If you have followed all the steps carefully, You will have a working oneplus dialer with call recording. You can enable call recording from dialer settings.
I am attaching the screenshots for your reference and I will keep updating the guide for better understanding, so please do not create multiple guides with the same steps.
It is 100% tested and working fine. If you will face any bug, Please let everyone know in the comments below.
Telegram: t.me/OnePlus8T5G
Special thanks to: @sansanc , Abhay Singh Gill, KunalShah and @Bewildered Wolf

It works folks! No way i would keep using google dialer. Everything works, even recording. Great stuff!

All working here

App systemize is working for you? Mine wasn't showing apps

I successfully enabled call recording using jOnePlus Tools. No root required, no steps. Just hit the enable switch. Is this different somehow?
Also, shouldn't this guide be in the ONEPLUS 8T GUIDES, NEWS, & DISCUSSION section?

Not working on my KB2007 TMO version

zeusofyork said:
App systemize is working for you? Mine wasn't showing apps
Click to expand...
Click to collapse
Yes, that's why you need to install via .apk. Very easy, you don't even need to start systemize interactively, just do: stemize -d /storage/emulated/0/contacts.apk
Substitute contacts.apk for another name/apk.
BTW, this magisk module has been discontinued. So the app list bug won't be fixed, unless soneone picks the development up.
---------- Post added at 01:56 ---------- Previous post was at 01:54 ----------
jwarrior319 said:
Not working on my KB2007 TMO version
Click to expand...
Click to collapse
What steps did you do? What happens?

sansanc said:
Yes, that's why you need to install via .apk. Very easy, you don't even need to start systemize interactively, just do: stemize -d /storage/emulated/0/contacts.apk
Substitute contacts.apk for another name/apk.
BTW, this magisk module has been discontinued. So the app list bug won't be fixed, unless soneone picks the development up.
---------- Post added at 01:56 ---------- Previous post was at 01:54 ----------
What steps did you do? What happens?
Click to expand...
Click to collapse
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod

Was waiting for this. Will try and report back ?
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
jwarrior319 said:
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod
Click to expand...
Click to collapse
It's a region thing as far as i know. Even global models might not have it.

Thanks for trying. We have tested it and it's working fine. If anyone have want to add some points please share your feedback. I will add it in the guide.

AlwaysLucky said:
I successfully enabled call recording using jOnePlus Tools. No root required, no steps. Just hit the enable switch. Is this different somehow?
Also, shouldn't this guide be in the ONEPLUS 8T GUIDES, NEWS, & DISCUSSION section?
Click to expand...
Click to collapse
Did you have OnePlus dialer or Google dialer ?

zeusofyork said:
App systemize is working for you? Mine wasn't showing apps
Click to expand...
Click to collapse
as sansanc said. You have to choose .apk choice 3. First two options will not work to show app list in 8T.

jwarrior319 said:
I just dont ever get the call recording option. My tmo one came preinstalled with the oneplus dialer as well. I haven't found any combination of things to make it work. I even tried the google dialer mod
Click to expand...
Click to collapse
Download joneplustools from the playstore! It allows you to enable call recording in the oneplus dialer

zeusofyork said:
Download joneplustools from the playstore! It allows you to enable call recording in the oneplus dialer
Click to expand...
Click to collapse
This only works if you already have OnePlus dialer installed.

Shavi_Suri said:
This only works if you already have OnePlus dialer installed.
Click to expand...
Click to collapse
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.

zeusofyork said:
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.
Click to expand...
Click to collapse
Yes...

zeusofyork said:
He said in his post that his phone, like mine, came with the oneplus dialer... We're both on T-Mobile and that is why we have it. Sooooooo yes.... It will.
Click to expand...
Click to collapse
Sweet it works.

For call recording, i use the apk from here:
https://forum.xda-developers.com/oneplus-5/themes/app-enable-call-recording-boot-t3634292
Now, i couldn't find an alternative for systemize. Android 11 comes with /system read only. Remounting it read-write doesn't work. That means that you just can't manually copy the .apk to /system/priv-app like before. That's why apps like Link2SD don't work anymore. So i think we are stuck with systemize.
If you disable systemize on magisk, the apps you installed with it, will disappear. But will appear again if re-enabling it. Reboot needed. If you delete the module, the apps will be gone for good.
Not sure about this, but i think magisk modules need to be disabled when udating the ROM. Otherwise, it boot loops/freezes. So, don't forget about that.
Messages with a dark background also works. Including blocking settings, but it needs to be a system app for that.
Contacts also works, But importing/exporting don't. Call logs permision can't be set. And permissions can't be edited manually because /system is read only.
Maybe a custom kernel can override this read only limitation?
We need for Oneplus to put these apps on play store!

sansanc said:
For call recording, i use the apk from here:
https://forum.xda-developers.com/oneplus-5/themes/app-enable-call-recording-boot-t3634292
Now, i couldn't find an alternative for systemize. Android 11 comes with /system read only. Remounting it read-write doesn't work. That means that you just can't manually copy the .apk to /system/priv-app like before. That's why apps like Link2SD don't work anymore. So i think we are stuck with systemize.
If you disable systemize on magisk, the apps you installed with it, will disappear. But will appear again if re-enabling it. Reboot needed. If you delete the module, the apps will be gone for good.
Not sure about this, but i think magisk modules need to be disabled when udating the ROM. Otherwise, it boot loops/freezes. So, don't forget about that.
Messages with a dark background also works. Including blocking settings, but it needs to be a system app for that.
Contacts also works, But importing/exporting don't. Call logs permision can't be set. And permissions can't be edited manually because /system is read only.
Maybe a custom kernel can override this read only limitation?
We need for Oneplus to put these apps on play store!
Click to expand...
Click to collapse
Thanks for the valuable feedback on this. Will pin this comment and will update the guide.

Thanks for this! I gave up after seeing that Terminal systemizer App list wasn't showing up, didn't think on trying to install an apk directly
Sent from my KB2005 using Tapatalk