Related
Hi All,
i have an issue - i installed custom ROM, custom kernel, all is working except root.
I have two root apps - superuser (standard) and one from ROM supersu. One came with ROM, and i flashed another (standard) just after flash (not sure why really)
So - I have two supersusers - bot don't have root... irony
Any suggestion how to fix that? Also, how should i delete superuser (standard) from system/app folder (without root apparently)?
Thanks all!
"This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me. It is impossible for an app to be installed in /system/app by the Play store. In fact, the entire /system partition is read only at runtime. The only way for an app to be placed in /system/app is via a rooting process (which usually installs Superuser), or by remounting the system partition as read/write and manually putting it there."
this is from the play store page. I guess you could try using root explorer to delete it but don't know if it will work
The more important question is why don't you have root? You have two root apps installed on a custom ROM. You should be able to run SuperSU and let it update the su binary. Then you can use ROM Toolbox or TB to remove Superuser.
Posted using Tapatalk 2
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Jsparta26 said:
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Click to expand...
Click to collapse
That's already been suggested in the ROM thread on another site, but he seems to be trying to get around it without reinstalling the ROM. He said over there that he doesn't know why he installed SuperUser since the ROM came with another su app and neither do I. He should just go ahead and reflash the ROM.
For some reason this guy seems to want to do things differently from standard practices and then ask for help when it doesn't work. His latest post in the other thread was asking if he could flash the ROM after removing the kernel (boot.img)!
I'm not sure where he comes up with these ideas but he seems to be off doing his own thing even though he is new at this stuff. I'm not suggesting that you don't help him, but wanted you to be aware that he may be creating problems for himself.
ramjet73
Thanks for the heads up. Your right, it don't make sense to try something different if what we suggest to somebody has been a better and usually a full proof way of fixing a problem. But like you said if he wants to add to his own problems that's on him. Let's make this clear to him too since he is new. Nobody on this site or other sites are responsible if you blow up your device, your gf leaves you, or you burn down your house and get fired. :highfive:
I just installed the 2.1 update on my child's Nabi 2. I would like to root it so that she could have some of the apps in the Google Play Store. Can I use Nabi Lab 2 to root it, or has there been an update since then? I download Nabi Lab 2, and it said in the instructions that I needed to be on version 1.9.37 so I was afraid to use it. Any information on how to root my Nabi 2 with the latest update on it would be greatly appreciated.
nabimom said:
I just installed the 2.1 update on my child's Nabi 2. I would like to root it so that she could have some of the apps in the Google Play Store. Can I use Nabi Lab 2 to root it, or has there been an update since then? I download Nabi Lab 2, and it said in the instructions that I needed to be on version 1.9.37 so I was afraid to use it. Any information on how to root my Nabi 2 with the latest update on it would be greatly appreciated.
Click to expand...
Click to collapse
I guess the short answer is no you cannot use Nabi Lab, or any other program right now, to take a stock Nabi at 2.1.27 and install root and gapps.
The more descriptive version is: There is ~504MB of space where the ROM, root, and gapps(with Google Play) need to go. The 2.1.27 install takes I think around 497MB, root is small but uses ~1M, Gapps uses maybe ~40M. That puts ~538MB into what can only hold ~504MB. Basically it doesn't all fit.
There hasn't really been a consensus on what is the best method to work around this. The easiest is to delete some kids applications and use that space for Gapps. For example the Wings software(apks) is close to 100MB. Deleting that gives more then enough space, but it's not optimal for those that have kids that want Wings. It is by far the best bang for the buck. 2 huge files. A lot of the other kids software is 3-5MB, and you have to delete 8 or 9 of them.
The general premise would be:
Stock tablet on 2.1.27
Use NabiLab/or whatever to Install TWRP and then MAKE A BACKUP!
Install Root
In Android use a Root file explorer such as ES File Explorer(I think it's still downloadable on the Nabi store/Amazon) and delete some apps in /system/vendor/apps
Use TWRP/Nabilab to install Gapps.
OR
Stock tablet on 2.1.27
Use NabiLab/or whatever to Install TWRP and then MAKE A BACKUP!
Use TWRP file manager to delete some apps in /system/vendor/apps
Use TWRP/Nabilab to install Root and Gapps.
If that sounds like something you want to try but need more detail on exactly how let us know.
mehtuus just made a beta version of ROOT installer for Nabi that should remove Wings automatically. Easier then the by hand method, it's beta but he does good work.
http://forum.xda-developers.com/showthread.php?t=2172843&highlight=nabi
Thanks
Thanks so much for the quick reply. You gave me some great information. Do you think I should go ahead and root it or would it be better to wait a little while until more info is known about this issue?
nabimom said:
Thanks so much for the quick reply. You gave me some great information. Do you think I should go ahead and root it or would it be better to wait a little while until more info is known about this issue?
Click to expand...
Click to collapse
Really depends on how much you would miss Wings. I think we will make a way to keep Wings. Just haven't got it there yet. It's not so much an issue, as it is: will you miss Wings app?
Can't get TWRP to work
I'm endlessly frustrated, and I'm hoping there is just some stupid little thing I'm overlooking.
Have an older Nabi 2. Rooted fine, Gapps working fine, great.
Have a newer Nabi 2 for my older child. I CANNOT cannot cannot get TWRP to install or work. I have the ADB drivers installed. It's recognized in the device manager. Nabi is connected. PDAnet is installed properly. ADB debugging is on. This is a brand new stock Nabi 2, version 2.1. I just keep getting the stupid dead red exclamation point android dude. I've used every method I have found on this site. NabiLab is what I used for the older Nabi with no problems. Example:
I run NabiLab. Device is detected, plugged in. Go to install recovery and root. It gets to the "Press enter when you see text on the screen after Nabi logo" and then the Nabi just gets stuck on the logo screen, indicating the drivers aren't installed. But they ARE installed. I'm about to throw this against the wall. I can reboot the device with the power and up keys and the "text on the screen" does appear, but it just goes to the dead android afterward. Can anyone help?
I'd be also interested in figuring out the definitive way to root and stick on gapps on this with the latest update.
Archon810 said:
I'd be also interested in figuring out the definitive way to root and stick on gapps on this with the latest update.
Click to expand...
Click to collapse
It's pretty messy. Everyone seems to be rolling with the "delete Wings" way, but it haphazard and confusing to almost everyone. I'm still up in the air for a way to make an automated script for those that aren't technical and would like a one click solution.
Funny timing I just finished writing a post on my blog about it.
http://nabtabhacks.com/
I am really confused about rooting my son's Nabi 2. Everyone says remove wings and it should be able to root, but I did that and still can't root it. Just curios if it is possible because I read a report that said there was software in the 2.1 update to stop people from rooting it. I've been going at this since noon and tried everyway I could find and it still doesn't work.
I'm not able to remove wings for some reason it cannot find it :/
Anyone have any suggestions?
"
Code:
rm: can't remove '/system/vendor/app/fuhu_WingsChallenge.apk': No such file or directory
rm: can't remove '/system/vendor/app/fuhu_WingsUniversity.apk': No such file or directory
zyphex said:
I'm not able to remove wings for some reason it cannot find it :/
Anyone have any suggestions?
"
Code:
rm: can't remove '/system/vendor/app/fuhu_WingsChallenge.apk': No such file or directory
rm: can't remove '/system/vendor/app/fuhu_WingsUniversity.apk': No such file or directory
Click to expand...
Click to collapse
look in
data/addon_res/vendor/app
hth
If your only wanting a few gapps, and not full root there is a simple method.
Using your google chrome browser on your PC, download and install apk downloader extension for browser. Use any google account info from any rooted device to register with apk downloader. Then go to play store on browser, search for app u need, then instead of hitting install, click the apk downloader extension button in toolbar. It will download the apk to your PC. Then simply transfer the apk file to your nabi.
Hope this helps.
I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
bump
Double44 said:
I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
Click to expand...
Click to collapse
To answer your questions:
Samsung Galaxy S
ROM Manager
ROM Manger has been buggy for a while now and can cause a lot of problems on certain devices, I would personally avoid it for the time being. That being said the best way to manage your ROM's (And any other Kernel, or MOD's you may want to flash) is too boot your device into recovery mode by using the key combination described in this post, or by running the following command from ADB on your computer:
Code:
adb reboot recovery
Once in recovery, you can flash any ROM that you pushed to your phones sdcard. Make sure to always perform a NANDROID backup of your current setup in recovery mode, before installing a new ROM, Kernel, or other MOD (Such as editing your build.prop file). Also before flashing anything in recovery make sure it is intended for your device and that you read and re-read, and re-read again the instructions on how to properly flash the file.
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
It is always assumed that any OTA update you apply will break root and that you will have to re-gain root access by re-rooting your device. You can disable OTA updates a couple of different ways. One method is to use an app such as FOTAkill to prevent OTA updates from happening. Another method is to use an app such as Titanium Backup to freeze and disable certain system apps that control OTA updates from being sent and received. Lastly, you can install a custom ROM to prevent OTA updates from being pushed to your device.
Internal Storage
This is a great question. The way the Nexus 7 and other devices that don't have an actual physical sdcard slot handle this is the sdcard folder you see in the file explorer acts as an emulated sdcard. So this way when you go to install a custom ROM in recovery mode when the ROM installation requires you to wipe everything the contents of the emulated sdcard will be untouched and remain as if it were a actual physical sdcard.
General
Busybox
Busybox is a series of stripped down GNU utilities and command line applets, you can find more about Busybox and what it is here. As far as needing it in the beginning you might not need it but as you get more familiar with modifying devices is comes in very handy for performing certain operations and tasks and is worth installing just to have for it's functionality. A lot of root programs push the su binary, a Superuser.apk, and often times the busybox binary. Not all ROM's choose to include busybox but it's handy to have like I mentioned for it's functionality.
Cyanogenmod
Cyanogenmod is an aftermarket firmware distribution you can find more about it here. As for why is it famous it was one of the first well know custom ROM's and soon grew to include support for a vast amount of devices you can find more about the history of Cyanogenmod here. AOKP is another well know ROM that stands for Android Open Kang Project, it first came about when Android 4.0 Ice Cream Sandwich was released you can learn more about AOKP here.
SuperUser
If your current ROM is missing a Superuser app you may install one from the Play Store, it does not matter which one you choose it is personnel preference but I would use either Chainfire's SuperSU app or Koush's Superuser app. Updating a pre-installed Superuser app to the latest Play Store version is fine. There are no consequences to installing one Superuser app and uninstalling another one it's a matter of personnel preference which one you want to use. Keep in mind if you uninstall one Superuser app and then install a different one it may ask you to update the su binary (Which it should ask you if you want to do that once you launch the app for the first time) before it will function properly.
If you have any other questions let me know I'll be happy to answer them or elaborate on anything that may still be unclear to you.
Long story short, this is a zip to debloat your S8 and probably other Samsung devices. Please modify it to suit your firmware. *As long as your rom is from Samsung, regardless of nougat or oreo, most of the package names should be the same thus this zip should still remove quite a lot of them by default, you will need some minor edits to match your rom perfectly though.
The attached zip is what I'm currently using, there's something that I had commented out because I use that feature and never tried disabling it. Please feel free to experiment with it and modify the script as per your need. However, do pay close attention to some of the lines as activating them will cause your phone fail to boot.
If you had any error or knowledge about what certain file does, please provide feedback so that we can improve this script. The ultimate goal is to know what we can stripe off from TouchWiz ROM until close AOSP state without breaking features that we use, that includes .apk files, files of any format and even related lines in build.prop.
Also, for anyone who wishes to use this script in any way, please feel free to do so. No need to inform or give credit.
Since I do not backup my file before testing, I'm using Github to do this for me. The most updated version will be on Github.
For more information please visit Github.
Credit
SoLdieR9312 for his OREO BETA6 Debloat zip as template.
foobar66 for his debloat shell script as a reference.
Google as well as several posts in XDA Developers forum
Hall of fame
1. Debloating Samsung Experience Service might lead to Samsung Account FC / bootloop. By: Saibot.XI
After this zip your phone will be left with:
Stock Samsung Audio (Adapt sound, SoudAlive, etc)
Stock Samsung AOD
Stock Samsung Calculator
Stock Samsung Calendar
Stock Samsung Camera & all plugin
Stock Samsung Clock
Stock Samsung Contacts
Stock Samsung Device maintenance w/ McAfee removed
Stock Samsung Gallery & related editor
Stock Samsung Game Launcher & services
Stock Samsung Live wallpaper picker
Stock Samsung Messages
Stock Samsung Music
Stock Samsung Phone
Stock Samsung Smart capture (Screenshot w/ crop, drawing features)
Stock Samsung Launcher
Stock Samsung Video Player
Samsung Desktop Smart Switch support .apk file
Google play etc among some preloads
And some files that IDK what they do/what will happen after removal
Over hundred of apk files will be removed.
Theme center and Samsung account will also be removed, if you want to use theme, please comment them out before flashing.
They can be removed after you applied your theme and will stick after reboot. This is what I did too.
How do i add themestore and remove it after applying theme? Also, flash in twrp?
Got it working nvm. Awesome work!
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
kleen3r said:
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
Click to expand...
Click to collapse
used the updated script from github and works perfectly!
is this working on 955N or 950N variant?
Very good ! VERY SMOOTH AND FAST!
Box3D said:
is this working on 955N or 950N variant?
Click to expand...
Click to collapse
I do expect people here to experiment with it, as I said in Github this is not (completely) noob-friendly.
You can cross check the script with your ROM, majority of the Samsung preloaded app will be the same, the difference usually is carrier apps. Maybe I shouldn't mention that I'm using AQL5.
XDA developer yeah, not XDA noobs.
kleen3r said:
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
Click to expand...
Click to collapse
I've no idea what is flashfire, sorry about that.
ImbaWind said:
I've no idea what is flashfire, sorry about that.
Click to expand...
Click to collapse
It's an app that flashes zip files similar to TWRP. I have the snapdragon 955u variant so cant use twrp since the bootloader is locked. I do have root though.
kleen3r said:
It's an app that flashes zip files similar to TWRP. I have the snapdragon 955u variant so cant use twrp since the bootloader is locked. I do have root though.
Click to expand...
Click to collapse
I see, good to know. Im using an exynos version so cant really figure that out.
You can even delete folder/file one by one by using terminal/root explorer according to my updater-script, that shouldn't make much of a difference.
Will this work on oreo zra5? Actually tried flashing this but it didnt remove anything at all
I personally use the Package Disabler because I'm not that worried about space but the script helped me extremely on what to disable. Very helpful. (also on aql5 btw)
dr460nf1r3 said:
Will this work on oreo zra5? Actually tried flashing this but it didnt remove anything at all
Click to expand...
Click to collapse
That's weird, it should be able to delete what nougat and oreo have in common and there's quite a few.
porkslapchop90 said:
I personally use the Package Disabler because I'm not that worried about space but the script helped me extremely on what to disable. Very helpful. (also on aql5 btw)
Click to expand...
Click to collapse
System space is quite useless, but it makes people like me feel better when useless stuff is actually gotten rid of.
Plus it is able to remove files, that's beyond the ability of package disabler.
Work on 7.0 aql5? Renovate 7.5
Hey after flashing this tool i have problem : screen write is ereased and when i want to use root file to open system/app my device suddenly reboot what could be the problem?
Nathan5900 said:
Work on 7.0 aql5? Renovate 7.5
Click to expand...
Click to collapse
Im using stock aql5, how do you define 'work' tho?
EDIT: This zip basically removes stuff, so if your ROM contains the stuff that match the updater-script, it gets removed. Nothing magic happening here.
torhect said:
Hey after flashing this tool i have problem : screen write is ereased and when i want to use root file to open system/app my device suddenly reboot what could be the problem?
Click to expand...
Click to collapse
This script doesn't remove the function that allows you to draw on your screenshot cause I'm using that too, one of the actually handy feature added by Samsung...
The reboot part, I'm not sure. Somehow when I try to add back apks directly to system via explorer, my /data partition gets corrupted with
Code:
persist.security.tlc.otp structure needs cleaning
in TWRP, only format data fixes this, and this happened to me twice so I'd recommend you to flash them in instead using the rescue zip template I provided in Github.
The script is really good, I just read it line by line but since I see some issues reported for some people I prefer to try it out later
Edit: i was thinking on replace all Samsung needed apps with Google ones like phone and dialer, anyone knows a port from those?
I have a TCL Flip 2, flip phone, which runs AOSP Android 11, and blocks APK installation. It has a package installer, but blocks APKs from being installed, and sends an error message through ADB when I try to install like that. There is no option to enable apps from unknown sources, and running settings put (global/secure) install_unknown_apps 1 doesn't do the trick. Anyway, how can I go about rooting the phone?
Android 11
Kernel version 4.14.186
I appreciate your help, thanks!
Maybe you have found it already, but for everyone else you can install apks and root with this guide https://github.com/neutronscott/flip2/wiki
I couldn't find this anywhere on Google, so hopefully this helps!
Also TCL Flip Go and Flip 2 are the same phone but with different carriers.
ZeroTheSavior said:
Maybe you have found it already, but for everyone else you can install apks and root with this guide https://github.com/neutronscott/flip2/wiki
I couldn't find this anywhere on Google, so hopefully this helps!
Also TCL Flip Go and Flip 2 are the same phone but with different carriers.
Click to expand...
Click to collapse
Yes, I already found it thanks. Also cricket flip classic is the same.
Neutonscott is the dev who did anything and everything to help root the phone. He made a custom magisk boot img with a script running to reset the prop which blocks app installation.
you can find a ton of info about that phone on forums.apps4flip.com. I am also available here if you have any other question about it.