**New** Root Access is Now Required!
Download:
- G900T_OF6_Batch_Debloater_&_App_Freezer
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater & App Freezer folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click DeBloater.bat to launch the program.
4. Select "Light," "Medium," "Extreme", or "Freeze Apps"**and press "Enter."
5. Grant Root Access if prompted by your device and press "Enter" to begin.
6. Once complete press "Enter" to return to the Main Menu and select ***"Reboot Device."
7. Last, select "Exit" from the Main Menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use notepad++ or other text editor to view/edit the lists of affected apps in the debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
Download:
- G900T_OF6_Batch_DeBloater
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater folder onto your desktop.
2. Boot into *TWRP, Press "Mount" and make certain that "system" is checked.
3. Connect your phone to your **PC while still in TWRP and double click on the DeBloater.bat file.
4. Select "Light," "Medium," or "Extreme" debloating (see DeBloater.bat file for list of removed apps).
*I used TWRP 2.8.6.0 (could not get TWRP 2.8.7.0 to connect to PC).
** Make certain that you have Samsung Drivers installed.
Click to expand...
Click to collapse
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Its likely under a different name. I used the extreme option and its no longer installed.
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Not deodexed.
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
poncespr said:
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
Click to expand...
Click to collapse
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
muniz_ri said:
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
Click to expand...
Click to collapse
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
poncespr said:
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
Click to expand...
Click to collapse
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
muniz_ri said:
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
Click to expand...
Click to collapse
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
poncespr said:
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
Click to expand...
Click to collapse
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
muniz_ri said:
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
Click to expand...
Click to collapse
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
poncespr said:
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
Click to expand...
Click to collapse
I suspected that was the case so I have modified the tool to not run unless the device is recognized by the PC.
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Master619 said:
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Click to expand...
Click to collapse
Only thing that comes to mind are samsung drivers, try install or reinstall.
Edit: played around with it....connect your phone while in recovery to your PC and run Windows Update. It should give you the option of installing Android ADB Driver.
MortTheBeast said:
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Click to expand...
Click to collapse
What I did is I disabled MTP in TWRP.
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
MortTheBeast said:
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
Click to expand...
Click to collapse
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
poncespr said:
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
Click to expand...
Click to collapse
I got nothing... here's crossing my fingers that someone is working on a root method, or else I will have to dump 5.1.1 and go with 5.0. :good:
Related
Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Manual instructions:
All you need to do is use adb install appname.apk
Indirect said:
Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Click to expand...
Click to collapse
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
so the android central sideload wonder machine should work.
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
~Leko
gameman733 said:
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
Click to expand...
Click to collapse
They would have to maintain two versions of their software if they blocked adb install. How are they going to test the apps going into their market.
Sent from my BNTV250 using xda premium
xdahgary said:
so the android central sideload wonder machine should work.
Click to expand...
Click to collapse
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Hey all, I cannot get his to work because I no longer have usb debugging. I should say I am on a Nook Color not tab. I just thought it would be nice to try non-rooted for a while. I guess I will just re root.
~Leko
lekofraggle said:
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
Click to expand...
Click to collapse
I have AnyCut installed and created a shortcut to app settings. I reset the "Install from unknown sources" to be checked and then tried installing an app from the Amazon Market. When the package manager ran I got the new will not install dialog. Dang! So I launched the app settings again and noticed that the unknown sources box was unchecked. I checked it again, closed, and relaunched the settings window. The option is unchecked again. Grr....
Installing apps from the Android Market works just fine though, as it does not require the package installer to install an app.
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
I have been unable to clear and reset my drivers for the NOOK Tablet.
I've uninstalled and reinstalled but I must not have the right drivers.\
I'm running Win 7 64bit.
Any link would be appreciated.
GreenFuzzer said:
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
Click to expand...
Click to collapse
BUMP, as I was wondering this myself.
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Ugh, my Nook just updated to the dreaded 1.4.1 version. I tried the script from XDA and ran it with the command prompt, but it says "error no decide found", even though my Nook Tablet is plugged into my Windows XP Machine. Any ideas why this is happening?
I'd greatly appreciate it. Thanks!
Also, I got the script from here: http://forum.xda-developers.com/showthread.php?t=1407023 . I run the Sideload.bat file which usually doesn't run until an Android device has been found, and in MS Dos it says: C:\Sideload>adb wait-for-device . And yet when if I were to install an apk residing in the Sideload folder via Command Prompt, it says no device found.
szumlanski said:
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Click to expand...
Click to collapse
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Indirect said:
Script download:
Click to expand...
Click to collapse
Is there something available for Mac users? I don't have access to any Windows system for over a week.
Also, I was wondering if anyone out there has had success access the Android Market after using this new script? Hopefully some of the root teams/specialists out there can find use a better answer that going by to sideloading.
szumlanski said:
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Click to expand...
Click to collapse
Ok, so how DID you get it into debugging mode?
geonjay said:
Ok, so how DID you get it into debugging mode?
Click to expand...
Click to collapse
If you rooted 1.4.0, you would have used tgps launcher downloaded over the air. Once you run (install) the tgps launcher, it remains in your android apps installed on the Nook tablet after the 1.4.1 is installed by B&N. Just unplug your USB cable, run tgps launcher, go into te development settings, enable two debugging options, disable auto mount. Then when you plug in USB it should pop up a notification that you are in debugging mode.
Do "adb devices" from a command prompt. If your device is found, you can adb install apps.
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
jayochs said:
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
Click to expand...
Click to collapse
Looks like your only option will be to manually downgrade to 1.4.0 and load all the apps you want. You can also prevent OTA update to 1.4.1. Search the forums for the instructions. That sucks.
Alternatively, wait and see if a 1.4.1 root comes out.
xdahgary said:
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Click to expand...
Click to collapse
Thanks, this works great. I know there is a way to root and install google apps on 1.4.1 now, but I'm fine with this since I don't have to go through the process of losing and then restoring all the apps and books I have loaded.
Just like another person mentioned, all one has to do is have NT Hidden Settings or tgps_launcher installed prior to the upgrade to be able to enable USB debugging.
I managed to accidentally flash the BLADE boot.img for CM10.1 to my phone before I transferred the ROM across to my SD card.
Didn't think this was a problem.. went into recovery to Mount USB Storage. Didn't work, so I flashed TWRP to see if it worked on there. No luck.
Tried performing a restore of the full working stock sense and wiped caches so I could try to transfer it over the OS. again no luck.
I've even tried pushing the .zip file to the sdcard using adb (run cmd as admin and use 'adb push ROM.zip /sdcard/ROM/') with no luck. It just tells me the device isn't connected. The drivers are definitely installed (fastboot is working).
I'm all out of ideas. If anyone could point me in the right direction, I'd be grateful. Thank you!
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Is there another way of accessing the SD Card through recovery?
No except adb, but that only works with twrp. Why not flash a stock rom, and copy the rom to the SD Card while booted into android.
Sent from my HTC One X+ using Tapatalk 2
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
NasaGeek said:
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
petedavison93 said:
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
Click to expand...
Click to collapse
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Kraizk said:
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Click to expand...
Click to collapse
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
petedavison93 said:
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
Click to expand...
Click to collapse
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type "adb kill-server" and then type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Kraizk said:
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Click to expand...
Click to collapse
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
petedavison93 said:
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
Click to expand...
Click to collapse
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Kraizk said:
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Click to expand...
Click to collapse
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
petedavison93 said:
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
Click to expand...
Click to collapse
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Kraizk said:
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Click to expand...
Click to collapse
Trying the sideload now
petedavison93 said:
Trying the sideload now
Click to expand...
Click to collapse
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Kraizk said:
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Click to expand...
Click to collapse
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
petedavison93 said:
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
Click to expand...
Click to collapse
You could flash the stock recovery and run the RUU
Kraizk said:
You could flash the stock recovery and run the RUU
Click to expand...
Click to collapse
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Although this still doesn't solve my problems with adb
petedavison93 said:
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Click to expand...
Click to collapse
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Kraizk said:
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Click to expand...
Click to collapse
Can't relock the bootloader without working drivers.. this is beyond annoying now ¬.¬
EDIT: Relocked but not enough battery to flash RUU. Do I just run the RUU from the computer while the phone is at the home menu in the bootloader?
I'm using a batch file to charge the device over night. Will try again tomorrow.
Hello;
This was my first time installing a Rom. I was fed up with my phone responding slowly and in time jams.
1-The first thing I did was install cwm recovery v6.0.2.7.
2-Then use the S3 tool kit available in xda to make a backup of all except system apps and internal storage data and it was stored in a .bak file. So that games and other apps keep their info as it is a hassle to start from the beginning.
3-Installed CM 10.1 nightly used in the instructions provided here.
All is okay up to here.
4-Tried to restore apps and app data through S3 tool kit but it won't display the data in the phone. I did enable the usb debugging on the cm10.1 (by pressing 7 times on the build name to enable the developers option and enabling usb debugging). I had the same problem when trying to do the backup in step 2, but it connected through the adb mode. This problem is that when ever I connect a device via usb windows installs the driver so every time I connect my phone windows installs the drivers.
5- When step 4 did not work I tried to restore using Holo Backup but no use no able to connect through to adb mode.
I can access the phone storage but I believe the appropriate drivers are not running when using the restore programs even though they are installed.
So the questions are:
1- Is there a way to fix the connection to be able to use S3 unified tool kit or if any one has dealt with the same problem?
2- Is there a way to restore the .bak file via cwm recovery?
3-For future use; An app or program that can be stored in the phone to avoid the use of a PC. The app or program would back-up contacts, sms text, apps and app data into the virtual sd or cloud to avoid deletion when "wipe data/ factory reset" after installing a rom.
I look forward to your replies.
Thank you.
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
wststreet said:
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
Click to expand...
Click to collapse
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
sub-80 said:
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
Click to expand...
Click to collapse
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
sub-80 said:
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
Click to expand...
Click to collapse
Tried ADB wifi but no success the pc says that there are no adb devices.
Also tried PDANet+ to install the drivers but software does not see the s3.
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
JJEgan said:
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
Click to expand...
Click to collapse
removed the .bak extension and placed it in the download folder of my virtual sd folder and pressed restore on cwm but nothing happened.
Could be because the backup is password protected?
Also tried to restore the file via titanium backup through the extract simple adb with and without the extension but only says analyzing file and remains that way for hours.
So I have a Samsung Vibrant(just got it recently) and I'm having problems when i connect it to the computer. It gives me an USB device not recognized on my windows 8 computer. I have spent all morning searching and reinstalling drivers and trying my old pc and new cables and i found out that my old windows 7 computer with 4GB of ram and an overloaded hard drive will detect my device the problem there is it not my main computer and i dont want to have to connect all the vga cables boot it up connect mouse and ect to use this computer just to be able to copy files, and do other things from my computer to my phone I dont know why my main computer dell inspiron windows 8 will not work when it was a couple of days ago when i had a problem with conectivity and had to flash back to stock but now it wont connect. could someone help me? Here's a list of things i've tried
installing kies
installing adb again
aoi tool and then drivers
a bunch of diffrent drivers found on the fourms
diffrent usb cable
i would like to be able to do it on my main computer but its not working if someone could help that would be great
also please dont hate on me for having windows 8 jk i dont care :good:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Vono123 said:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Click to expand...
Click to collapse
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
apples723 said:
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
Click to expand...
Click to collapse
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Vono123 said:
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Click to expand...
Click to collapse
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
apples723 said:
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
Click to expand...
Click to collapse
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Vono123 said:
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Click to expand...
Click to collapse
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
apples723 said:
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
Click to expand...
Click to collapse
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Vono123 said:
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Click to expand...
Click to collapse
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
apples723 said:
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
Click to expand...
Click to collapse
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Vono123 said:
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Click to expand...
Click to collapse
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
apples723 said:
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
Click to expand...
Click to collapse
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Vono123 said:
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Click to expand...
Click to collapse
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
apples723 said:
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
Click to expand...
Click to collapse
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
binaryfalcon said:
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
Click to expand...
Click to collapse
didnt make a difrence still getting error i think its something with my system so i guess without a full diagonostic it wont work
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.