(I apologize that this is in the wrong section, I don't have enough posts to post in the development section)
I'm interested in installing Safestrap on my 7in Kindle Fire HDX, but I had a quick question about the stipulation that "Rooted w/ SuperSU" be installed before installing Safestrap. Is "Rooted w/ SuperSU" a specific .apk, or does SuperSU do the rooting? I've had experience with TWRP with my old Kindle Fire, so I'm fairly familiar with what NOT to do, but I wanted to ask you this out of an abundance of caution.
Best,
James
marlowja said:
(I apologize that this is in the wrong section, I don't have enough posts to post in the development section)
I'm interested in installing Safestrap on my 7in Kindle Fire HDX, but I had a quick question about the stipulation that "Rooted w/ SuperSU" be installed before installing Safestrap. Is "Rooted w/ SuperSU" a specific .apk, or does SuperSU do the rooting? I've had experience with TWRP with my old Kindle Fire, so I'm fairly familiar with what NOT to do, but I wanted to ask you this out of an abundance of caution.
Best,
James
Click to expand...
Click to collapse
From What I gather, you install the required ADB drivers, then run the root script which includes the required files to root (somewhere on this forum). You can then install and sideload the supersu, busybox and the safestrap tool which will install the recovery portion allowing you to create custom rom slots.
Root first, install SuperSu later.
Then install SafeStrap recovery, THEN the rest should be obvious.
Related
Hello,
I wish to install (and use) the application DME Excitor (corporate emails) but it is detecting the root in some way.
I have a i9100 device with cm9.1 (latest stable one) & siyah kernel 5.0.1.
I've also made sure (using ExTweaks) that the kernel is not re-rooting the device every boot.
I've tried to remove the root using "Hide my root" / "ExTweaks" / "SuperSU" - and others that say they will hide the root - so far with no success!!!
Can you please suggest how to prevent DME from detecting my root?
I really don't mind unrooting the device - but please do not suggest me to return to stock!
Any help will be highly appreciated! :good::good::good:
bump
bump
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
florox said:
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
Click to expand...
Click to collapse
sorry - no success yet
In case you find any way, please let me know
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
bkraptor said:
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
Click to expand...
Click to collapse
Did you tried it with DME ?
By default, installing the SuperSU from the play store is in '/data' (you can later change that option in settings to be set on '/system')
Anyway, tried that, didn't worked.
Any help would be highly appreciated. :good:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
bkraptor said:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
Click to expand...
Click to collapse
Hi,
First of all thanks for trying to help.
There's no any Superuser.apk in /system/app/ (that's the first thing I've checked).
And I did made sure to uncheck the "Enable Superuser" option within SuperSU.
Still doesn't work.
If you don't mind me asking, could you please provide me with more details on your firmware?
Which rom are you using (is it Cyanogenmod)?
Special kernel?
CWM ?
Any details would help.
And once again, thanks!
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
bkraptor said:
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
Click to expand...
Click to collapse
Thanks for the info.
I was afraid that you would note you're using a rooted stock firmware.
The thing is that by going back to stock rom, there's no need to root it and then unroot it to use the DME (simply use the stock firmware unrooted).
The first post on this thread was a question on how to use the DME on different rom than the stock one (such as CM).
After that being said, I would like to thank you for trying, but this didn't help me, since I wish to use the Cyanogenmod rom and DME together.
If you still have any suggestions on how to use the DME with a non-stock rom, I would be more than happy to hear.
I don't see how running CM is any different than running official. You should check that after disabling Superuser from within SuperSU that there is no "su" binary anywhere within the directories in the PATH variable (i.e. /system/bin or /system/xbin).
Is dual booting a stock/cm setup possible, and would that serve as a "workaround"?
Edit...just thought....even if possible, the dual boot kernel would probably give the game away....
Sent from my CM10 powered S2 via XDA Developers App
is there any solution at this point? I have cm installed and i want to use dme on my rooted phone...
finally!!! fully functional nexus 7 ))
meaning stock browser AND DME running
rooted with this method (from stock 4.2.2):
http://forum.xda-developers.com/showthread.php?t=2233852
installed stock browser from here:
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
SuperSU settings (many thanks to bkraptor):
http://forum.xda-developers.com/showpost.php?p=42009031&postcount=6
Can someone please let me know how to install superSU in /data. As If I instal UPDATE-SuperSU-v1.51.zip by using PhilZ-cwm6. It is installed by default in /system.
If I install it using Playstore it does the same got installed in /system. and further conflicts with SU installed by PhilZ-cwm6.
Will appreciate any suitable advice
I know that portions of Busybox are necessary for root (at least that is my limited understanding). I am currently rooted with Kingoapp which I consider a "soft root" as there is not a custom recovery installed.
There are some android apps that require not only root access but also a full install of Busybox. When I try to install them they warn that the full install is required. This, of course, leads me to believe that this, and probably other "soft root" methods don't use or use a limited version of Busybox.
My question is, if I install a full version of Busybox, will it cause issues with my current set up? I've read on a couple reviews of Busybox that insalling it caused loss of root, or prevented one of the cpu cores from coming online, etc....
Thanks in advance for the education!
Hello! I want to install Safestrap Recovery v3.71 and i have the HDX8.9 WIFI.
"First Requirement: Rooted w/ SuperSU installed." (Hashcodes HowTo from here http://forum.xda-developers.com/showthread.php?t=2612772)
I have the stock rom, the only thing i have done ist root it and prevent OTA-Updates.
Before i make a backup/copy of the stock rom, i dont want to make much changes, like installing an alternate market.
Now my question:
How to secure install SuperSU ?
I found the APK can be downloaded from http://www.1mobile.com/supersu-358316.html.
But can i trust that download from 1mobile ?
Is a scan of the apk with https://www.virustotal.com/ usefull ?
THX for Help ...
I recently installed Hyperdrive RLS19 on a a I545 NC5 using Safestrap 3.75 KitKat A01. Everything works fine including wifi. I did have to restore the Android Device ID, which got changed somehow. I have rebooted several times into SS and used it to flash other stuff, etc. However, I decided to update the pre-installed version of SafeStrap, which was an older version. I first attempted to uninstall SS using System App Remover. The SS app appears to be gone; but then, when I tried to reinstall SafeStrap a message asked if I wanted to update this built-in app. The update then failed. I have two questions. If this has been explained elsewhere, please just point me in the right direction.
1. How can I reinstall SafeStrap 3.75, so that it matches the version of the installed recovery?
2. Is there any need to keep the SafeStrap app installed, after the recovery is installed and working? Does it do anything besides install and uninstall the recovery?
(I think I should be able to uninstall the recovery, if needed, by switching back to the stock ROM slot and uninstalling it from there.)
Thanks in advance for any help or explanations.
Also, kudos to the developers of Hyperdrive for an outstanding product.
VirtualX1 said:
I recently installed Hyperdrive RLS19 on a a I545 NC5 using Safestrap 3.75 KitKat A01. Everything works fine including wifi. I did have to restore the Android Device ID, which got changed somehow. I have rebooted several times into SS and used it to flash other stuff, etc. However, I decided to update the pre-installed version of SafeStrap, which was an older version. I first attempted to uninstall SS using System App Remover. The SS app appears to be gone; but then, when I tried to reinstall SafeStrap a message asked if I wanted to update this built-in app. The update then failed. I have two questions. If this has been explained elsewhere, please just point me in the right direction.
1. How can I reinstall SafeStrap 3.75, so that it matches the version of the installed recovery?
2. Is there any need to keep the SafeStrap app installed, after the recovery is installed and working? Does it do anything besides install and uninstall the recovery?
(I think I should be able to uninstall the recovery, if needed, by switching back to the stock ROM slot and uninstalling it from there.)
Thanks in advance for any help or explanations.
Also, kudos to the developers of Hyperdrive for an outstanding product.
Click to expand...
Click to collapse
Download the Safestrap 3.75 apk. Go into your old version of Safestrap and "uninstall recovery". Then from your app drawer, drag the Safestrap app to "uninstall app". Uninstall Busybox also. From the Play Store, download Selinux and Busybox. Reboot your phone. Go into Selinux and set Linux to "permissive". Go into the Busybox app and "install Busybox". Go to wherever the Safestrap 3.75 APK is and install it. Go into your Safestrap app and "install recovery" reboot. Profit.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
liljoe727 said:
Download the Safestrap 3.75 apk. Go into your old version of Safestrap and "uninstall recovery". Then from your app drawer, drag the Safestrap app to "uninstall app". Uninstall Busybox also. From the Play Store, download Selinux and Busybox. Reboot your phone. Go into Selinux and set Linux to "permissive". Go into the Busybox app and "install Busybox". Go to wherever the Safestrap 3.75 APK is and install it. Go into your Safestrap app and "install recovery" reboot. Profit.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
Click to expand...
Click to collapse
The Safestrap app was removed. Usually, System App Remover makes a backup of apps removed, but in this case it did not make the backup; not sure why.
If you reboot after removing the recovery, does it automatically go into the last used ROM slot? Or does it default back to the stock slot?
Thank you for the assistance.
VirtualX1 said:
The Safestrap app was removed. Usually, System App Remover makes a backup of apps removed, but in this case it did not make the backup; not sure why.
If you reboot after removing the recovery, does it automatically go into the last used ROM slot? Or does it default back to the stock slot?
Thank you for the assistance.
Click to expand...
Click to collapse
I reckon it should boot into whatever partition you were in before you removed Safestrap. You could just hotboot the phone and you wouldn't need to worry about that.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
What's the best way to unroot 4.5.2 and remove gapps? I'm not doing as much on the tablet as before and I'd like to just go back to stock. I do want to back up my APKs first so I can adb reinstall a few that Amazon doesn't have (Marvel Unlimited, up to date version of Trillian, etc) rather than having to dig around for them on apk sites.
Thanks.
You can unroot in SuperSU.
And for gapps and such, just manually remove all the files, or can I just uninstall the various apps using the native uninstall function?
You can't regularly uninstall system apps, so you'll need to do those things while you're still rooted.
Would it be cleaner to do a firmware rollback/upgrade? I don't mind wiping everything.
Still looking for the right way to remove gapps before I unroot... thanks.
No easy way to remove 'gapps' as there are multiple ways it can be installed each containing a different suite of components. Your best bet would be to disable anything having to do with google. You may need a 3rd party tool to accomplish this (not sure if FireOS shows all installed apps/services). This approach leaves the files behind but effectively negates their function.
You could also replace (overwrite) FireOS via temporary installation of SafeStrap v4 but that involves several hoops and accompanying risk.
Just use something like ES File Explorer or 'System app remover' to get rid of anything to do with Google.
"Just use something like ES File Explorer or 'System app remover' to get rid of anything to do with Google."
Be careful with this approach. If you trash a file that is referenced at boot your device may hang (FireOS is fussy stupid around startups).
Regardless of approach make sure USB debugging is enabled so you can use adb to fix stuff if necessary.
Could I reenable ota updates, remove Google play services, Google play store, supersu, towelroot, upgrade to 4.5.5 or whatever the current version is, and then safely do a factory reset? If so, how do I turn the updates back on first?
On FireOS v4 OTA updates are typically disabled by renaming DeviceSoftwareOTA.apk located under /system/priv-app/. Assuming you followed this process restore that file/filename to reenable updates. Before doing that remove whatever components were added while rooted as you may not be able to do so after it updates.
I would be hesitant to perform a native factory reset as others have reported boot hangs and other anomolies after rooting FireOS v4 and installing non-Amazon components (eg: gapps). Really depends how they were installed and whether system files/permissions/settings got twiddled. As you can not be 100% sure everything was removed/restored the risk remains.
To restore pure stock you'll need to install Safestrap v4, wipe system and data partitions, flash a custom SS compatible version of FireOS 4.5.2 (here) and then immediately remove Safestrap. Your device will update to v4.5.5 (or whatever the current version is) shortly after. Under this scenario a factory reset is not required as a full wipe was done within Safestrap.
While installing and working with Safestrap is relatively safe/easy it is not a brainless process and requires careful attention to detail. Important: Never perform a 'native' factory reset with Safestrap installed!
BTW - towelroot is irrelevant on FireOS v4 (remove the .apk if present).
Ah sorry I meant the cvexxxxx successor to towelroot, it's been quite a while.