Database Users

Rooting My TMo Vibrant Using Super Oneclick (A Full Guide)

And every other step you need to transform and gain control of your stock ROM!
Given the fact that T-Mobile and Samsung have made it clear that the Galaxy S Vibrant will not receive Gingerbread, Honeycomb, ICS, or any other functionality update, I made the decision that it was finally time to root my beloved phone.
I didn't want to root for the purpose of trying a ROM for any of the above OS's. I merely figured that since there are not going to be any future updates to my phone, I'm basically on my own. And if I'm on my own then I can and should get rid of the TMo crap software that came pre-installed on my phone (and which can't be uninstalled by any normal means).
Hopefully this process might also help make my phone operate a little faster and cleaner. And in general, the rooting process would give me full control over my own phone. But if you have ever rooted a device the experience can sometimes be challenging, even for tech-savvy folks like me.
There are lots of sites for advice and how-to’s on rooting your Android device, but most of these sites run you through the process in a way that assumes all will work perfectly the first time. There aren't a lot that take you through the root process with at-hand solutions to many of the commonly reported errors.
I've just finished rooting my stock TMo Vibrant, fixing signature/Multi-CSC issues from the root process, installing and using Titanium Backup (TB) PRO to handle bloatware, and finally installing ROM Manager for the purpose of installing ClockworkMod Recovery (for creating and restoring backups of my current ROM). WHEW! And while it's all fresh in my mind, I'm writing it all down to share the process with you so that it's all in one convenient place.
Let’s Start With Rooting The Phone By Using Super Oneclick
After doing some reading in the XDA forums and a few other places, I wanted to try rooting with a one click option. There are many out there that are available for use. But the very first issue that plagued my rooting process was the incompatibility of many of these root installers with my home Win7 64bit pc.
I tried downloading and extracting various recommended solutions that use the "one click" functionality (Super Oneclick--various versions with and without drivers, Galaxy S One Click Root, and Vibrant One Click Root). I also downloaded and installed AIO Vibrant Toolbox, a program which also features a “one click” method for rooting a Vibrant once it has been installed on your pc.
What many posts on rooting never really mention with these methodologies is that you might have issues running the programs on a Win7 machine, which was my issue. Not all Win7 machines, but some. I downloaded the zip file for each with generally with no issue. * But once I tried to run the exe (best done via "Run As Administrator"), I got the following error message on virtually all of them:
"CLR Error: 80004005 The program will now terminate"
AIO Vibrant Toolbox wasn’t any better even though it was an installed program. It terminated as well.
(*NOTE: Anti-virus programs will mistake parts of the root zip files for Trojans, usually quarantining them after download. You are then left with the uncomfortable choice of turning off your anti-virus and taking that chance, or looking for another zip solution. I opted for the latter. Never take a chance with a Trojan!)
These errors messages did not show up on my work pc which is also Win7 64-bit. But that was no comfort as most of my root work was going to be done at home. After much searching on the internet, I read a random post that mentioned two helpful suggestions:
Use a rear or powered USB port, not a front port (because they often can’t power the root install sufficiently)
Use Super Oneclick v1.7 as opposed to any newer versions. The newer versions can cause problems with this particular Galaxy S root.
Two simple suggestions that made a world of difference! The root process worked smoothly afterward, and was finally a "success".
Reminder - Remember to put your phone into USB Debugging mode for the root process, and don’t mount the external SD card when attached.
Along the way to “rooting” you might be confronted with messages about your Samsung drivers for your phone. You may see messages like these:
Device drivers not found
Samsung android USB composite device failed
A quick search on these forums will yield updated drivers for your phone. The successful install of these drivers can also be a function of using the proper USB ports, as in the situation above. The installation of Samsung drivers failed on the front USB ports of my Dell. Success was again found using the rear ports. The main point here: use the rear ports (or powered USB ports) no matter how much of a pain it is maneuvering under your desk and behind your pc!
You’re Almost There…Kinda!
You can check to see if you are successfully rooted by checking to see if Superuser is installed in your apps. It was there… whew. The next step was to install Titanium Backup so that I could have root control over my apps, allowing me to delete bloatware that was slowing my phone. I downloaded TB from the Market, opened it, tried to give it Superuser permissions, and was notified with an error message that permissions were unsuccessful because the phone was not rooted. WHAT???
More online research revealed that I had achieved a “soft root”, whereby you have successfully rooted your phone but you don’t have all root permissions because the install wasn’t complete. The solution? Basically you just have to keep doing it more than once. All steps of this process seem like they will take the first time if you do what you are supposed to do. But more often than not, you have to repeat your steps over and over to make sure that it takes. After two more Super Oneclick rooting attempts, TB finally gave me the thumbs up for root.
Some may say it’s not necessary, but I upgraded to TB PRO. It allows for more options and better functionality with the apps and system data on the phone. And really, at about 6 dollars it is more than worth the price. Heck, two Starbucks lattes will run you more than 8 or 9 bucks. So if I can get piece of mind with respect to app management on my newly-rooted phone, 6 bucks is more than worth it.
I immediately wanted to learn how to remove bloatware -- and it’s amazingly difficult to find clear directions on doing so. After my backup of all apps and data, I went to the backup/restore tab and found the programs I wanted to get rid of. Many online users recommend “freezing” an app first to make sure that removing it won’t make your phone all wonky. So after “freezing” the offending apps (by pressing the menu button, selection batch, and then scrolling down to the appropriate section on freezing apps), I long-pressed the desired app and only saw one option for uninstalling via an exploit. I selected it and long story short, it failed. As the phone boots to stock recovery, this message popped up:
E:failed to verify whole-file signature
E:signature verification failed
Applying Multi-CSC Installing
Multi-CSC Installation Aborted​
In simple terms, the rooting tool (Super Oneclick) doesn’t contain all of the necessary items for a complete root. A fix is needed for the invalid signature problem that will help you get to a full root state. Fortunately there are fixes out there you can find for this particular fix.
Here are some helpful links:
http://androidforums.com/galaxy-s-a...iled-installation-aborted-one-click-root.html
http://forum.xda-developers.com/showthread.php?t=1052991
Read the instructions for the fix on the first page, but get the correct file from the second page as the link for the fix from Dropbox is a little messed up in the first URL. The second URL has the correct link. Use the automatic method so that you don’t have to use the terminal emulator. If you are like me, this process has already given you more gray hairs than you would really like to admit. So take the easy route.
Run the install.bat file and you will be fine. When you reach stock recovery again remember to reinstall all packages. This will make sure that the fix is installed properly. I didn’t know that was needed and was wondering why the fix wasn’t taking initially. So I’m sharing this with you to head off your frustrations at the pass. ;-)
Getting Rid Of The Bloat
Check to make sure that you are fully rooted by opening TB. It will automatically take Superuser permissions from the first time you allowed it IF you are rooted. If not, it will tell you. And by now you should be rooted. Heading back to the bloatware, I was able to figure out that the “long press method” was not the correct one for uninstalling apps.
Once again, press the menu button (bottom left) and select batch. Scroll down and you will see a section for uninstalling apps. Select uninstall user and system apps, and make sure to DESELECT ALL before you do anything else. From there you can pick and choose the apps to uninstall, then “run the batch operation” to complete the task. Bye bye bloatware!
The last crucial step to complete now that your phone is rooted is to make sure that you have a backup of your current ROM and configuration. The backup you created using TB is only for apps and data. It is not a backup of your current stock ROM.
Nandroid backup works best for the purpose of backing up and restoring ROMs. And if you have done any previous rooting on an Android device, you will recognize that Nandroid is a function of ClockworkMod Recovery. Sigh. I know... frustration starts to set in as you realize that there is yet another necessary install needed for a totally successful root process ON TOP OF and AFTER everything else you have had to do. So what is the next step?
ROM Manager To The Rescue
Install the free ROM Manager from the Market and you will be good to go. This app allows you to flash CWM Recovery as well as mount various ROMs on your phone. After installing the app (and declining the various offers that pop up), press “Flash ClockworkMod Recovery” at the top of the menu. It will cause the phone to reboot. And CWM will be downloaded…but not installed. To install after reboot, open ROM Manager and now select Reboot into Recovery. It will challenge you with a question on whether you really want to do this or not. Say Yes.
Important: This is another one of those places where it’s not intuitively obvious what to do for CWM Recovery.
When I first rebooted into recovery I didn’t see any changes from my stock recovery menu…because there were none. What I needed to do (which I found in yet another forum posting) was again to select Reinstall all packages. CWM had been downloaded and was ready to install… this would do so.
Happily, the phone went into Clockwork recovery*immediately after "Reinstall all packages" . If it wasn't clear earlier, use the volume buttons toggle up (or down) to select backup/restore. *You can then implement your selection by pressing the power button on the right side of the phone. On the next screen select backup, and then let it do its’ thing. It may take a while to complete, but will be well worth the time and effort if you have any future problems.
The Entire Process Is Finally Complete
So there you have it. In a nutshell, here were my steps:
1. Samsung drivers
2. Super Oneclick v 1.7
3. E. Signature fix
4. Titanium Backup PRO
5. ROM Manager (free version)​
Use the rear USB ports or powered USB ports for the phone connection. Phone should be in USB debugging mode, and external SD card should not be mounted. For each process, it may take up to 2 or 3 attempts for successful completion. So keep trying after the first FAIL message. When applicable, “Reinstall All Packages” to make sure that downloaded files are actually installed.
And lastly, if absolutely nothing works correctly for you, PLEASE PLEASE PLEASE use Google for help. Many others have successfully worked through all of the problems you might encounter that aren’t listed here. Actively use Google to help find solutions to any problems, using the exact error messages shown and adding in your phone type. You will be amazed by the depth of experience out there that can help you.
Above all else, keep up a good attitude. Rooting might be a pain in the ass while you are doing it, but it’s for a greater purpose. My four days of rooting have now given me a phone that is FREE from all the bloatware that bugged me for the past two years. And soon I’m sure I will experiment with a different ROM. But for now I’m just happy that I have my phone, my way. After all, if they (TMo and Samsung) aren’t going to make our phones better, we can do so for ourselves.
Good luck, and I hope this complete set of instructions from my own past 4 days of experience will help someone else!

A good read. A few things though with the Titanium part.
First I whole-heartedly agree to kick down the $ for the Pro. It really ups the functionality of the app and what all it can do.
The part about "freezing". This part is tricky b/c you need to make sure he apps that you are freezing are indeed bloat and not something that is needed for something else (i.e. did you know that GTalk directly effects the market on some ROMS). I don't use Gtalk but I still have it installed and frozen so I can defrost at will. This is the reason for Freeze. It lets you know of any adverse effects on your ROM, other apps,...then you have the option to defrost if need be. I also always avoid doing anything in "Batches" on TBPro, as it can sometimes be a little wonky, especially when restoring batches, causes reboot and freezes resulting in batterty pull.
I freeze for at least a week on new ROMs so that I get the full experience with daily life to make my determination on uninstall, defrost or wait longer.
Another way to do it is once you know the apps that are frozen do not effect any other parts of your ROM, you can back them up with TBpro for later use and uninstall or you can do it this way. Since you have root, go into /system/app or and pull the APK out and put it in a folder or something like that on your SD card. You would do this to some of the /system apps that TB shows as only haveing a checkmark next to and not the yellow/orange circle with the M in it. If you uninstall these with the checkmark you will not be able to restore them b/c part of the executable portion of the APK is not able to be backed up. This is the reason to pull the app out of /system/app and put it on your SD card. Hit menu, more, Clean up Dalvik cache and viola!! you have some free space on /system and the offending APK's dex will be deleted too.
Sidenote: I have never been able to get SuperOneClick to work on any phone I have ever tried. Maybe I'll unroot and try again but the SU exploit is a flashable zip located here. Option A. Put it on your SD card, boot into recovery and Bam!!! you are rooted
Nice work though.

Where can we still get Super Oneclick v 1.7?

http://forum.xda-developers.com/showthread.php?t=739300 make sure you have ADB turned on and use the USB ports from the back not front

too lengthy.

Just got vibrant
Sent from my SGH-T769 using xda app-developers app

Sent from my SAMSUNG-SGH-I317 using Tapatalk
Delete..

Where are the game save files located on Android?

Got a galaxy note 3 and a note 10.1 2014 edition. both are not rooted.
I would like to transfer my progress in Injustice - Gods among us from my tablet to the phone.
Been looking online and in other threads here and the only option I saw is TI backup, which is for rooted devices.
I've checked the iOS setup, and they have a save file *.bin that they can use iFunbox to extract.
Is there no save file on Android? where is it?
Thanks in advance

sprunknwn said:
Got a galaxy note 3 and a note 10.1 2014 edition. both are not rooted.
I would like to transfer my progress in Injustice - Gods among us from my tablet to the phone.
Been looking online and in other threads here and the only option I saw is TI backup, which is for rooted devices.
I've checked the iOS setup, and they have a save file *.bin that they can use iFunbox to extract.
Is there no save file on Android? where is it?
Thanks in advance
Click to expand...
Click to collapse
Most of them in root/data/data. So you need root access as well. Maybe using adb you can pull it

Rosli59564 said:
Most of them in root/data/data. So you need root access as well. Maybe using adb you can pull it
Click to expand...
Click to collapse
ADB doesn't require ROOT?

sprunknwn said:
ADB doesn't require ROOT?
Click to expand...
Click to collapse
Basically root not needed but some people say it depends on what you're doing. Perhaps if you're to copy a root file no root is needed but if you're trying to delete maybe root is needed(even so with correct permission still no root required)
But i don't know adb so not sure.

Try Helium, but you will need Helium (carbon) for pc also. You need to connect ur phone to pc, start carbon on pc and phone to enable it for backup or restore. Copy the backup file over Will do.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Ok, tried Helium but it didn't work.
In addition I have something to say about the Samsung service as a whole.
I tried to find the Samsung android USB drivers on the Samsung website but it's impossible to get anything useful out of it.
Eventually I found the most updated drivers on these forums.
After that I contacted Samsung online chat support to receive assistance on backing up in-app data.
Turns out, there's no way to do it with anything Samsung offers (WHICH IS ABSURD).
Such a basic functionality and it's not available through any Samsung app or feature.
The only thing the support did was to comfort me regarding this issue and telling me there's no way to do it unless I use a 3rd party app, which they cannot recommend.
I have never had such ****ty service from such a big company. It started with the update and it's just going downhill ever since.
Unbelievable.

TL DNR: Helium worked perfectly for me with my Galaxy S4 and my new Galaxy S7, both of these devices are non-rooted and I used the free version of Helium. Continue reading for a walkthrough of what worked for me and will hopefully work for you.
I just got a Galaxy S7 (I upgraded from a Galaxy S4) and I wanted to keep my progress from all of my games so I wouldn't have to start from square one. All I had to do was download Helium on both of my phones and the desktop program. Then I connected my S4 to my desktop using a usb cable, opened Helium and followed the on screen instructions to backup whichever apps I chose. After that I set my S4 to connect via MTP and opened my phone on my desktop. The file path should look like this My Computer\Your_Phones_Name\Phone\carbon (carbon is the folder where Helium saves the app data that you chose to backup). Copy all the app folders you want, then follow pretty much the same steps for connecting your new device to your desktop and paste the folders from your old device in your new device's carbon folder. Once you've done that, on your new device open Helium and go to Restore And Sync, Internal Storage, select your apps to restore, and then finally enjoy your progress that you deserve!

A much much easier solution is to make use of the cloud backup feature in the game.
Just make a WBID account in-game and all your progress will be backed up. If you reinstall the game on the same device or another, just make sure you sign in with your WBID and a prompt with Superman will appear giving you the option to restore your progress.
DO NOT RESTORE USING THE CLOUD BUTTON AT THE TOP RIGHT CORNER IN THE MAIN MENU as Google Play Games cloud restore is broken in Injustice and you'll lose your progress!!!
I find this method alot easier than fiddling with system files =)

Rosli59564 said:
Basically root not needed but some people say it depends on what you're doing. Perhaps if you're to copy a root file no root is needed but if you're trying to delete maybe root is needed(even so with correct permission still no root required)
But i don't know adb so not sure.
Click to expand...
Click to collapse
How to get adb to do that please? I'm new to this stuff. I tried adb root but it says "adbd cannot run as root in production builds" I'm using linux if that helps. Device I'm trying to extract from is non-rooted OnePlus 3T.

So in the internal storage (NOT ROOT), you first need to know the first company maker of the app & then the first name of the app (example : tiktok would be somthing.musically) because of the package name & how it updates & stuff.
Now when you go to the Android Folder, you see data, this is where (most) files are saved for progress & is usually in here where data gets wiped by settings for apps, scroll down for your app, click on it & then...
find a way to put all those files into your other device.
(this is also how some people cheat their way through games like subway surfers unless they're a bit complicated for most users lol)

[SM-P905][SM-P907A] Debloating bloatware after rooting + Power On sound removal

** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** These scripts are written for Kitkat. Do not use on Lollipop. **​ What is new (9/7/2014)
Version 4 provides more Samsung bloat removal, Google bloat removal, and as a bonus it can disable the power on sound.
Background
Samsung has a program running on most of its devices that pushes "Security Updates" onto the device. If you make the mistake of accepting this security update, even after you root your tablet, it will patch the hole and you will never be able to use towelroot or any other know exploit as of June 2014 to root your it again. So this must be immediately disabled after a successful rooting.
Your tablet is also equipped with Knox. One component of Knox is in the bootloader and checks the integrity of the recovery and kernel. If it sees anything has changed at that level it trips the knox flag immediately, which is irreversible. That component can almost never be touched. The second component runs when the OS is up and running and its main task is to monitor the activities of the apps in your system and shut them down if they act "suspiciously". When you are rooted and install SuperSU, this element of Knox keeps detecting the background root activities and shuts them down and gives you warnings. There is therefore a high level of risk there if you let root and knox exist concurrently. So after rooting, this second component of Knox should normally be disabled.
Finally, there are useless junk apps that most of us agree Samsung should have never shipped with the tablet, or even if they are useful we want them gone to get a better battery life.
I will call all of the above (updaters, Knox, and useles junk) bloatware. The scripts attached here can disable or enable the bloatware on your tablet, which comes in handy if you do not have Titanium Backup Pro to freeze or remove bloatware. And since someone will ask at some point, no, it won't trip your Knox!
Please read below and understand what this script disables before you use it. There may be an app on the list that you may actually want to keep.
Requirements:
Rooted Samsung Note Pro 12.2, SM-P905 international model.
Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
The international version (P905) is tested with baseband P905XXUANA7, build P905XXUANC3 .
The ATT version (P907A) is tested with build KOT49H.P907AUCU1AND7 (thanks to @gerard0986 for testing the script)
Makes sure you download the version that is suitable for your tablet. It may work to varying extents for other models and firmwares.You try and tell me
If you are using models other than P905 or P907A, I can make a new script for you if you provide me with a "ls -R -l" dump of your /system, or even better, if you post your firmware somewhere online.
Download link:
Attached below
Instructions:
Generally speaking, you should always have a Nandroid backup before trying anything new. Also have a flashable ROM handy. I am not responsible if you brick your device while using these scripts.
To debloat:
1- Unzip the attachment and copy debloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh debloat.sh​3- Choose what you want to disable, or exit.
4- If you choose not to exit, the code does its thing and reboots your tablet. The bloat is gone now
To restore the bloatware:
1- Unzip the attachment and copy enbloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh enbloat.sh​3- The code will warn you:
Are you sure you want to restore the security/firmware/software updaters, and Knox?
They may immediately patch your system and make the existing root methods impossible to apply.
Then you can choose what to enable, or just exit.
4- If you choose not to exit, the code does its thing and reboots your tablet. The bloat is back now
Note that while running the debloat script you may get force-closing popups. This is normal; after all you are disabling these applications!
Limitations:
If you have previously removed bloat using other means this script CANNOT recover it for you. enbloat.sh can only restore what debloat.sh has disabled.
If you have debloated using an older version of this code and you want to try a newer version of it, first use enbloat from the older version to return everything to the original configuration and then use the newer version.
When you are restoring the bloat, it is best to enable "airplane mode" so that your tablet does not try to patch your system with a security update without your knowledge. You can disable the airplane mode after you debloat again.

Change log
V5:
Typos fixed.
=============
V4:
Option to disable all Google services except Youtube, search, map, and TTS
Option to disable/enable Power on sound
=============
V3:
The scripts give separate options to enable/disable these groups of bloatware:
1- Updater/knox
Firmware Upgrader, Local FOTA, Security Manager, FOTA Client, Security Update Client, Samsung Push Client, Samsung Software Update, Knox and its related apps
2- Samsung bloat
ANT, Blurb, ELM Agent, Samsung Apps apk and widget, Job Manager, Samsung cloud backup files, Context Provider, S Finder, S Voice, Samsung Account Service, aaIgnite_1.5.15_singtel, weplay_1.3.162, PCWClientS18
3- Other bloatware
Accuweather, Bloomberg, Dropbox, Evernote, Flipboard, NY Times, Remote PC, ,Travel Service, Twitter, WebEx, Line, Pinboard Scratch book, SNS, eMeeting
=============
V2:
The scripts give options to enable/disable updater/knox and other bloatware separately.
Added these to the disable list of V1:
SecurityManagerService, aaIgnite_1.5.15_singtel, weplay_1.3.162
=============
V1:
The script disables the following:
Firmware Upgrader, Local FOTA, FOTA Client, Security Update Client, Samsung Push Client, Samsung Software Update, Knox and related apps, ANT, Blurb, ELM Agent, Remote PC, Samsung Apps apk and widget,Travel Service, Twitter, WebEx, Line, Samsung cloud backup files
PCWClientS18, Scratch book, S Finder, SNS, Samsung Account, eMeeting

Would this work for the T-900 version too?

What do I need to get the info required to get a script made for the sm-p907a model? I read above post but the list of things required were above my head lol.
Sent from my SAMSUNG-SM-P907A using XDA Free mobile app

iNiREALiZED said:
What do I need to get the info required to get a script made for the sm-p907a model? I read above post but the list of things required were above my head lol.
Sent from my SAMSUNG-SM-P907A using XDA Free mobile app
Click to expand...
Click to collapse
1- What is your firmware version?
2- Open the terminal emulator and type the following commands in there:
su
cd /system
ls -R -l > /sdcard/sysdump.txt
Then pm the file sysdump.txt which is saved on your sdcard to me.

thank you
Thank you najoor for the neat script, it executed successfully on my sm-p905 (UANE1 rom) & removed the useless software, it saves a lot of time removing them manually.
Nice work

Hope to see a version for the SM-P907 soon.

Rockytop00 said:
Would this work for the T-900 version too?
Click to expand...
Click to collapse
I think the only existing models are SM-P900, SM-P905, SM-P907A and SM-P905V. I don't know what T-900 is.
If you are referring to model P900 (wifi only) this code may partially work but a lot of files are different between the two models so the outcome is a partial debloat. If you want, you can make a system dump file as I suggested in this post http://forum.xda-developers.com/showpost.php?p=55029414&postcount=5 and send it to me so I can make a custom code for you.
Edit: It appears that T900 is the Tab pro model which is a different device. This thread is for Note pro 12.2 and since I do not own a Tab Pro I cannot answer this question. Perhaps help can be found in the XDA's Tab Pro forum at http://forum.xda-developers.com/galaxy-tab-pro-12-10-8. or try these scripts as they are and see if it works for you.

Hey najoor, Im hoping that you can help me debloat my galaxy tab pro 12.2 sm-t900. I just bought it today and am shocked at the amount of bloatware thats included lol.
Basically I want everything removing that I can install through googleplay, leave the default browser.
Here is the log that you mentioned to the other guy also:-
View attachment sysdump.txt
Ill try to pm it also, really hope you can help out.
Pixel

Debloat method
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?

stockerrodney said:
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?
Click to expand...
Click to collapse
Yes, that is part of bloat removal. To get Google bloat back run the enbloat.sh script and hit y when it prompts you about restoring Google bloat.

stockerrodney said:
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?
Click to expand...
Click to collapse
najoor said:
Yes, that is part of bloat removal. To get Google bloat back run the enbloat.sh script and hit y when it prompts you about restoring Google bloat.
Click to expand...
Click to collapse
If i do the enbloat method will i have to reinstall knox ? Or will i still be able to keep it off?

When you use the enbloat.sh you only restore the stuff you choose. You don't have to restore everything. In your case you leave knox and other things out and only answer yes when it asks you if you want Google bloat to be restored.
The script is very user friendly. Just run it and follow the instruction. And just to give you peace of mind, these scripts do not delete anything from your system permanently so don't worry about breaking your system.

Any chance you could add the option to remove individual items?

http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294

Debloat v5.0 removed Scrapbook from Air Command
The debloat worked fine but the Scrapbook app in Air Command is now showing error "no application found to handle this actions".
Please advise.

mojoe said:
The debloat worked fine but the Scrapbook app in Air Command is now showing error "no application found to handle this actions".
Please advise.
Click to expand...
Click to collapse
Removing apps is what a debloating script does. If you want your app back just run the enbloat script. All the instruction you need is provided in the original post.

najoor said:
Removing apps is what a debloating script does. If you want your app back just run the enbloat script. All the instruction you need is provided in the original post.
Click to expand...
Click to collapse
Appreciated. I wanted to debloat but did not expect the scrapbook app to be debloated. Is there any way that I can retrieve this one app, without the rest of the garbage that will return if I "enbloat".
I recall finding the app the last time and renaming from .bak to .apk and it worked.
Can you tell me where to find the apk.

mojoe said:
Appreciated. I wanted to debloat but did not expect the scrapbook app to be debloated. Is there any way that I can retrieve this one app, without the rest of the garbage that will return if I "enbloat".
I recall finding the app the last time and renaming from .bak to .apk and it worked.
Can you tell me where to find the apk.
Click to expand...
Click to collapse
The app is either in /system/app or /system/priv-app. Rename app.apk.bac and app.odex.bac if it exists to app.apk and app.odex and reboot. I don't remember exactly which app is the one you need.

najoor said:
The app is either in /system/app or /system/priv-app. Rename app.apk.bac and app.odex.bac if it exists to app.apk and app.odex and reboot. I don't remember exactly which app is the one you need.
Click to expand...
Click to collapse
Thank you. I will return with the name once I find it.

Inaccessible Note 4 [BROKEN DIGITIZER] - How to recover data?

Need some help, got a broken note 4 here and I want to access my files that are still stored inside it. I tried the Vysor Application to see the display but the problem is I forgot the passcode of my phone because i haven't touched that phone for over a month now.
My phone is running custom Note 7 port rom (Ditto Note 7) and I have TWRP installed as a recovery option for my phone. I tried using the adb shell comand su to my phone to remove the gesture.key but it seems that I haven't accept permissions for the adb on my device.
How do I clear the passcode of my phone? or can I clear the settings and data (without internal storage) using TWRP?
Need replies ASAP please

There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings

stylemessiah said:
There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings
Click to expand...
Click to collapse
Okay thanks for the reply I'll try the link above

How To Properly Backup Fire TV Stick 4K in TWRP with no issues

As I did more testings on my Fire TV Stick 4K within TWRP, most of the issues usually occur while backing up the system and vendor. In the past, I thought I was doomed because of a bricked Fire TV Stick 4K for backing those two partitions. Yesterday, I finally discovered the true fix with backing up and restoring. You need to only backup the system image, vendor image, data, and boot to get your Fire TV Stick 4K working again WITHOUT flashing a prerooted or stock image. Let me know if this works for you and I'll be glad to respond back. I also have my version of a debloated rom for the Fire TV Stick 4K which may be available in the near future and is safely able to factory reset successfully along with the setup wizard going through without issues.

Skel40 said:
As I did more testings on my Fire TV Stick 4K within TWRP, most of the issues usually occur while backing up the system and vendor. In the past, I thought I was doomed because of a bricked Fire TV Stick 4K for backing those two partitions. Yesterday, I finally discovered the true fix with backing up and restoring. You need to only backup the system image, vendor image, data, and boot to get your Fire TV Stick 4K working again WITHOUT flashing a prerooted or stock image. Let me know if this works for you and I'll be glad to respond back. I also have my version of a debloated rom for the Fire TV Stick 4K which may be available in the near future and is safely able to factory reset successfully along with the setup wizard going through without issues.
Click to expand...
Click to collapse
EDIT: Version 1.0 of my debloated rom will be posted here shortly! Its a backup without my account obviously, and has a few tweaks done so far. ONLY works for Fire TV Stick 4K.

Looking forward it Skel40!
Keep up the good work....

Awesome can't wait to try it

Question
Hello. Any update on this? Ive been trying to find a way to do this but have had no luck on my 4k sticks. Please share

Headstrongrc said:
Hello. Any update on this? Ive been trying to find a way to do this but have had no luck on my 4k sticks. Please share
Click to expand...
Click to collapse
There's no new update on this. It still works. What did you backup? Backing up the system, and vendor only bricks the device. Its always important to backup only the system image, vendor image, data and boot.

Thank you for the reply
I understand that appdata is stored in the root folders. Im just looking for a simple way to copy that data from one stick to another. I guess i didnt understand exactly what you meant. Im really just wanting to save my atv launcher setup and if possible my logins and passwords to my premium app subscriptions. Any help will be much appreciated. Thanks

You can do this with
Busybox and
https://f-droid.org/en/packages/dk.jens.backup/
I also use this for ATV and Youtube without Problems.

And...
I am not familiar with TWRP or know how a debloated rom works. Im not a total noob or anything but im not anywhere on your level. Please leave some details.
I currently use es to backup all apps. Ftp & filezilla and use adb commands to install apps. I move over my custom codecs and kodi data etc. I do not know how to copy the appdata on 4k stick.
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
Big thanks to 0815hoffi. That looks like a winner. Im cant wait to try it. Im way excited! I will let you know how it goes.

So i move my backup to the other stick.
adb shell mkdir /sdcard/oandbackups
adb push oandbackups /sdcard/oandbackups/
adb install dk.jens.backup_305.apk
And make a reboot after restore to Apply the changes.

Sweet
Got it. Suprisingly I havent been able to find this info anywhere else. Thank You!!!

Question
0815hoffi said:
So i move my backup to the other stick.
adb shell mkdir /sdcard/oandbackups
adb push oandbackups /sdcard/oandbackups/
adb install dk.jens.backup_305.apk
And make a reboot after restore to Apply the changes.
Click to expand...
Click to collapse
Does this method work only on a rooted device? I have busybox installed and oandbackup. The app wont let me backup app data without SU permissions. Is there a command I need to enter in terminal or something? Also regarding twrp, is that able to backup the whole device? (Testing this on my android phone btw)

Yes you need root for this.

What root method do you reccomend for firestick? Also just wanting to know if there is any downside to rooting? Ive never rooted one just because ive never really needed to.

just catching up stick 4k root, have 4 tv sticks, rooted the first one using kamakiri and mantis 6.2.6.8_r1, in process of setting up stick 1 with apps. Once finished want to copy the same configuration over to the other sticks. Once i use kamakiri to unlock the other sticks, do i need to bother with installing mantis pre-rooted image or i can use use this backup method :
Skel40 said:
As I did more testings on my Fire TV Stick 4K within TWRP, most of the issues usually occur while backing up the system and vendor. In the past, I thought I was doomed because of a bricked Fire TV Stick 4K for backing those two partitions. Yesterday, I finally discovered the true fix with backing up and restoring. You need to only backup the system image, vendor image, data, and boot to get your Fire TV Stick 4K working again WITHOUT flashing a prerooted or stock image. Let me know if this works for you and I'll be glad to respond back. I also have my version of a debloated rom for the Fire TV Stick 4K which may be available in the near future and is safely able to factory reset successfully along with the setup wizard going through without issues.
Click to expand...
Click to collapse
from stick 1 and apply it to the other 4k sticks, and i shouldnt have enter the logins into the apps again ?

Headstrongrc said:
What root method do you reccomend for firestick? Also just wanting to know if there is any downside to rooting? Ive never rooted one just because ive never really needed to.
Click to expand...
Click to collapse
See these guides for rooting the 4k firestick.
https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459
https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273
The downside is you can destroy the firestick if you break any components trying to short the DAT0 or CLK points.

Thanks for all the great info. Idk if im ready to take the stick apart. Im going to watch a couple videos and see how comfortable i feel about doing this. Im sure its probably not that hard but a little unnerving for me not having done it before. I was really hoping there was an adb trick to backup this data.
---------- Post added at 05:22 PM ---------- Previous post was at 04:51 PM ----------
Can anyone tell me if something like this (please see link below) that can work on the firestick 4k? Everything else ive found without root requires plugging the device into a computer via usb like helium backup. https://android.stackexchange.com/questions/28296/how-to-fully-backup-non-rooted-devices

Headstrongrc said:
What root method do you reccomend for firestick? Also just wanting to know if there is any downside to rooting? Ive never rooted one just because ive never really needed to.
Click to expand...
Click to collapse
Without root.
adb backup -f myapp.ab -apk com.myapp
# backup on one device
adb restore myapp.ab
adb shell pm list packages -f
# to get the appname com.******

Having Trouble
0815hoffi said:
Without root.
adb backup -f myapp.ab -apk com.myapp
# backup on one device
adb restore myapp.ab
adb shell pm list packages -f
# to get the appname com.******
Click to expand...
Click to collapse
So I tried this command adb backup -f myapp.ab -apk com.myapp
CMD says: unlock your device and confirm the backup operation. Any ideas?
also once i get this to work am i supposed to just input # or # backup on one device?
I also tried the command with adding " " & ' ' around the command and got the same message both times.

Headstrongrc said:
So I tried this command adb backup -f myapp.ab -apk com.myapp
CMD says: unlock your device and confirm the backup operation. Any ideas?
also once i get this to work am i supposed to just input # or # backup on one device?
I also tried the command with adding " " & ' ' around the command and got the same message both times.
Click to expand...
Click to collapse
The "unlock your device" means you have to accept the adb connection on your firestick. There should be a message displayed on your TV screen. Use the remote to accept the connection.
# means that line is a comment. It is for your information, not to be executed.