I have the Fire 2015 on FireOS 5.1.1
Rooted and has google play services.
In order to gain write access to the external SD with TitaniumBackup I modified the platform.xml as follows:
Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Upon reboot, I have no access to the microSD card using ES File Explorer. The internal partition sdcard is also not accessible and shows no files or folders. I can only view the system partition.
Additionally, I cannot access the internet, although I can connect to my wifi network.
When I try to write to the internal sd "0" partition, I see "open failed: EACCES (Permission denied)"
I tried removing the changes in the platform.xml file but I could not save them, even with root explorer turned on in ES File Explorer.
I installed fx explorer and its root module using adb. I was then able to edit the xml file, taking out my change, making it original. I rebooted the device and the issues still persist. I figured this would happen because I have read other users' report issues even when replacing the modified platform.xml with the original.
(I cannot access root with it using "adb root" as it returns "adbd cannot run as root in production builds")
I tried a factory reset. The issues still persist.
At this point I might have to wait until there is a method for custom recoveries on 5.1.1 in order format /system and flash a custom rom. I was fine with being on fireOS with root...I just wanted to use TitaniumBackup with the extSDcard. I should have picked a different method!
Any ideas?
Start over. Reinstall FireOS 5.1.1 > root > block OTA > add google play.
See the thread on restoring stock FireOS.
No luck
blueberry.sky said:
Start over. Reinstall FireOS 5.1.1 > root > block OTA > add google play.
See the thread on restoring stock FireOS.
Click to expand...
Click to collapse
Thanks for the reply, bluberry.sky
So I successfully sideloaded my firmware version. It didn't work.
It restored all the stock fireos apps and everything, keeping a couple non amazon apps I had pushed to it earlier. Wifi settings were saved too. Issues with wifi and extSDcard remain.
I thought for sure your suggestion would work...
You can wipe with FlashFire
FlashFire worked for me. Since I saw it was possible to flash SlimLP with 5.1.1 I went ahead with that, rather than just wiping and restoring with a manual sideload.
1. I adb installed FlashFire
2. Used OTG-USB to copy the rom and gapps to root directory of device
3. Used FlashFire to wipe and install SlimLP
Man, it is so much snappier than FireOS.
Thanks for the replies.
Related
I want to back up system, recovery and boot so I can root and be able to go back to stock to take otas without having to go back to kitkat and factory reset and all. Otas won' t apply to previously rooted systems, so how to create one without rooting first? I tried twrp, it seems to create a backup but when looking in the folder nothing is there.
You can't
You can't. Because even with ADB commands the phone request for root privileges
It could be that TWRP is using the "legacy" path instead of the default "0" path for the SD card. I use FX file explorer to browse to it. It can be found at /storage/emulated/legacy/. The TWRP folder may be found there, and if so, it can either be copied to /storage/emulated/0/ or you can simply upload the entire folder to a cloud storage of some sort.
Additionally, you would have to restore stock recovery following a TWRP recovery for obvious reasons, so you have to make sure that the stock recovery image is available somewhere to fastboot flash it.
That said, with the new SuperSU, I don't think it modifies the kernel any longer, so a simple unroot from the app would restore /system back to default. The root method simply boots a permissive kernel instead of replacing your phone's kernel. And you wouldn't need to have a TWRP backup of your system partition. Also keep in mind that you would have to restore any other mod to /system such as ad removers which replace the hosts file or wakelock detector app helpers that need to write to /system.
Here is the scenario. I updated SuperSU v2.46 that came with the LG G4 root injection method with SuperSU v2.52 by running the Superuser.apk which basically installed /data/apps/<appname>/base.apk which worked as v2.52 except SuperSU will not install itself to /system even though I selected that option in SuperSU in which it said it will need to do a cleanup and reboot. So I manually renamed the base.apk to SuperSU.apk, changed the owner/group to root/root and kept the permissions as rw-r--r--, moved the file to /system/apps/SuperSU/SuperSU.apk, deleted the /data/apps/<appname> folder for SuperSU and restarted the phone. The only thing is SuperSU does not show up in the app launcher and the SuperSU.apk has the Android icon instead of the SuperSU app icon so I flashed the SuperSU v2.52 zip file with flashfire and it did restore /system/apps/SuperSU/SuperSU.apk with the correct icon except the problem is I noticed with Android 5.1 lollipop, you just can't replace a .apk in /system/app by moving it from /data/app as it will not even show up in the launcher. Not sure if this is a Lollipop thing or a LG thing as on previous Motorola phones running 4.4 Kitkat and below, replacing the .apk will usually work. I've cleared the app cache, deleted the files in /data/dalvik-cache/arm, /data/dalvik-cache/arm64 and /data/dalvik-cache/profiles without deleting the folders as I don't know if it's safe deleting the folders and also clearing the system /cache to see if it makes a difference. Didn't work. Does anyone know how I can fix this because it seems like once you updated to a newer version that installs in /data/apps, even if you delete the /data/apps version, it will not use the /system/apps version and simply ignore it. The only reason I still have root is probably because of the su binary still on the system.
Try:
- Make sure you've manually removed all SuperSU's APK files (/system, /data, etc)
- Reboot device
- From PC: adb uninstall eu.chainfire.supersu
- Or from root shell: pm uninstall eu.chainfire.supersu
- Reboot device
- Install SuperSU.apk (via adb, file explorer, Play Store, etc)
Chainfire said:
Try:
- Make sure you've manually removed all SuperSU's APK files (/system, /data, etc)
- Reboot device
- From PC: adb uninstall eu.chainfire.supersu
- Or from root shell: pm uninstall eu.chainfire.supersu
- Reboot device
- Install SuperSU.apk (via adb, file explorer, Play Store, etc)
Click to expand...
Click to collapse
My only concern is that on the LG G4, the original SuperSU was injected into the system image and as I have a locked bootloader still, it seems like if I did that, the only way I'll get root is if I reflash the system image again. It doesn't happen with just SuperSU but pretty much any apk in system that gets a newer version installed in data as it seems even if the data one was deleted, it will never use the one in system again.. Is there a way to use either adb or pm and install to system instead of data?
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
swaderade said:
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
Click to expand...
Click to collapse
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
TonikJDK said:
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
Click to expand...
Click to collapse
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
swaderade said:
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
Click to expand...
Click to collapse
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Since checking mount system does nothing, I went into Advanced > Terminal and did an `rm -rf GoogleHindiIME` and still can't edit the hosts file.
swaderade said:
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
Click to expand...
Click to collapse
I mount in twrp. Delete hindu and korean with the file manager in twrp. Reboot, install adaway and it works. I have never manually edited it.
No, the system mount in twrp does not stick on reboot. Mounting system with systemless root is tricky as I understand it. So I just avoid it.
You can't mount system as rw in a booted Android system unless you have a permissive kernel, and you should not have a permissive kernel.
Had the same problem and didn't want to remove things from /system. You can follow the steps here: http://forum.xda-developers.com/showthread.php?t=3266107
Systemless root on 6.0.1 - How to edit build.prop
Sent from my Nexus 6 using Tapatalk
I have rooted my phone, root checker said it was fine and supersu works fine.
But I can't edit system files through esFileExplorer (in root mode) and other way (by entering in twrp recovery).
I think it's not done the root, but idk what can I do. Should I root it again?
I wanted for disabling LPA in build.prop.
gregvp00 said:
I have rooted my phone, root checker said it was fine and supersu works fine.
But I can't edit system files through esFileExplorer (in root mode) and other way (by entering in twrp recovery).
I think it's not done the root, but idk what can I do. Should I root it again?
I wanted for disabling LPA in build.prop.
Click to expand...
Click to collapse
Which ROM are you on ?
Have you enabled Root Access>Apps & ADB in Developer Options ?
TryllZ said:
Which ROM are you on ?
Have you enabled Root Access>Apps & ADB in Developer Options ?
Click to expand...
Click to collapse
I had rooted with TWRP and Windroid Universal Android Toolkit.
And Apps & ADB is ~disabled~ (READ BELOW)
-----Update-----
Agh, wrong-
Apps & ADB option is not in my Developer Options,
I confused it with "Verifying Apps via USB" <---- (cause it said that it verify with ADB/ADT)
gregvp00 said:
I had rooted with TWRP and Windroid Universal Android Toolkit.
And Apps & ADB is ~disabled~ (READ BELOW)
-----Update-----
Agh, wrong-
Apps & ADB option is not in my Developer Options,
I confused it with "Verifying Apps via USB" <---- (cause it said that it verify with ADB/ADT)
Click to expand...
Click to collapse
If you are on CM or LOS this option will exists in Developer Options..
Do you have access to Developer Options in your current ROM ?
Which ROM are you on ?
TryllZ said:
If you are on CM or LOS this option will exists in Developer Options..
Do you have access to Developer Options in your current ROM ?
Which ROM are you on ?
Click to expand...
Click to collapse
Nope, I have developer options activated and doesn't exist ~
Stock Android 4.4.2
gregvp00 said:
Nope, I have developer options activated and doesn't exist ~
Stock Android 4.4.2
Click to expand...
Click to collapse
These options only exists in CM & LOS.
As I recall correctly, it's not possible to edit every file despite gaining root access in stock ROM, the work around to this is to copy the file to another location in your phone or into your PC, edit it, then copy the edited file into the phone to a different location, then rename the original file (as backup incase of failure) to anything else, then use TWRP to overwrite or copy the file into system directory using advanced feature, then restart device for changes to take place, if even after restart the changes did not take effect then you will have to use CMD to overwrite the file, the latter should work as I have tested it before.
tryllz said:
These options only exists in CM & LOS.
As I recall correctly, it's not possible to edit every file despite gaining root access in stock ROM, the work around to this is to copy the file to another location in your phone or into your PC, edit it, then copy the edited file into the phone to a different location, then rename the original file (as backup incase of failure) to anything else, then use TWRP to overwrite or copy the file into system directory using advanced feature, then restart device for changes to take place, if even after restart the changes did not take effect then you will have to use CMD to overwrite the file, the latter should work as I have tested it before.
Click to expand...
Click to collapse
https://puu.sh/A5hVB/08fef7d0ef.png
~~~~~~
I did it like you said but I still couldn't overwrite/copy the file into system through TWRP -> Advance
https://puu.sh/A5irV/5959e6aa53.png
By moving I had that error, but by copying it says successful although later I saw that It didn't overwrite anything
-----UPDATE-----
INFO::: ROOT ACCESS/ADB/SELINUX
http://puu.sh/A5joV/e136a8cb87.jpg
http://puu.sh/A5jpe/4cdb3e186c.jpg
..
gregvp00 said:
https://puu.sh/A5hVB/08fef7d0ef.png
~~~~~~
I did it like you said but I still couldn't overwrite/copy the file into system through TWRP -> Advance
https://puu.sh/A5irV/5959e6aa53.png
By moving I had that error, but by copying it says successful although later I saw that It didn't overwrite anything
-----UPDATE-----
INFO::: ROOT ACCESS/ADB/SELINUX
http://puu.sh/A5joV/e136a8cb87.jpg
http://puu.sh/A5jpe/4cdb3e186c.jpg
Click to expand...
Click to collapse
In that case the only option remains is to flash the file through CMD.
This should help https://stackoverflow.com/questions/22166770/permission-to-write-system-etc-on-android-4-3?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
You could also try to apply full permissions to edit to the folder and the file you are trying to access and edit..
What You'll Need:
The experimental firmware: https://androidfilehost.com/?fid=745425885120704448 (Thanks @NavSad !)
My updated G900A RootPack: https://drive.google.com/file/d/1U7vwyq4T4609SiUQz43zLXvYOu9Hqohb/view?usp=sharing
(Windows Defender may detect TowelRoot as an Android Malware Exploit, you may need to disable defender temporarily.)
If you want to downgrade to NCE/KitKat: The G900A_NCE.Zip file: https://drive.google.com/file/d/1ahpVGnG3bQ-mEoztN4XUvdbTOW64IdoT/view?usp=sharing
Get Ready:
You will need to extract the RootPack files and move the RootPack folder along with the G900A_Firmware.zip to an external SD and put it in your phone.
What To Do:
Step 1: Go back down!
Download the experimental firmware and extract the zip on your computer.
Open Odin3, select the AP slot, and specify the experimental firmware so you can flash it.
Under Options, Make sure only "AutoReboot" and "F. Time Reset" are selected.
FLASH
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, SuperSU, TowelRoot, BusyBox, and SafeStrap.
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (you don't have to reboot)
Step 3. Where to go?
You now need to determine where you want to go?
You can downgrade to NCE or upgrade to OF3
NCE DOWNGRADE/ROOT GUIDE
(KitKat) (Will downgrade you to KitKat and root it)
Now open BusyBox, dismiss the social prompt, and hit install
Now open SafeStrap Installer, grant SU Permissions, and Install recovery (DO NOT Reboot into it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Hit the '+' and hit 'Flash Firmware Package', navigate and select the G900A_NCE.Zip, and let it scan the archive.
Check Recovery, System, Cache, and Persist. Uncheck modem/Firmware
Hit the Check in the Top Right to confirm changes and Hit the '+' again
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package
Select EverRoot, Uncheck "Inject SuperSU" (If you don't, it will cause a kernel panic)
Select Reboot, Check Select "Preserve Recovery", and select the check in the top right to confirm changes (If you don't do this, you won't have recovery once you downgrade.)
HIT FLASH and OK (This will work, don't panic) It may take up to five minutes for the process to complete, if it fails, reflash combination.
After the OS is installed, go to the file manager and install TowelRoot, SuperSU, BusyBox, And SafeStrap
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Reboot to make SuperSU detect root.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (Yes, Reboot now)
Now open BusyBox, grant SU Permissions, dismiss the inital message and install busybox
Now open SafeStrap, grant SU Permissions, Install Recovery.
Your all set.
OF3 UP/DOWNGRADE/ROOT GUIDE
(Lollipop) (Will downgrade you to Lollipop and root it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Select "Flash Zip/OTA" and Select the G900A_OF3.zip
Mount /system read/write
Select "Flash Zip/OTA" and Select the G900A_OF3_Tether.zip
Mount /system read/write
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package (This will fix battery/heating/lag issues while your on OF3) (Trust Me)
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag below the G900A_OF3.zip (This will clean up the setup) (Trust me)
Hit "flash", let it flash, reboot, and load.
HIT FLASH and OK
After OS is installed, you will have root.
Copy G900A_OF3_Kernel.zip to the RootPack folder.
Install BusyBox, open and grant SU, Install BusyBox
Install SafeStrap, open and grant SU, Install to Recovery. (DO NOT Reboot into it)
Download the NCE_Flasher then install it, and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish or even ANOTHER ROM, just make sure you wipe everything but the external SD card if you are flashing a new ROM and you should be good.
Remember to ReFlash the G900A_OF3_Kernel.zip file in SafeStrap before you exit SafeStrap otherwise you will not be able to reboot.
If you forget and end up with an error, Just flash G900A_OF3_Kernel.zip with Odin3. (It won't wipe anything)
Marshmallow
---Working on a method---
(Won't stop until I have every update rooted.)
Marshmallow is currently unrootable on the G900A and G900V (CID 11). A method will likely appear in the future.
It is safe for you to flash to the latest Marshmallow, you will be able to restore the experimental combination to root again.
Notes: This guide is an updated version of AptLogic's Guide. ( Can a mod please sticky that thread )
I have created this thread as an "elimination of confusion"/"Catch All" and I will update the thread once I get root on Marshmallow , https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196.
Thank you to AptLogic and everyone involved in the development of root for this device.
Which File where?
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
CheeseMerchant said:
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
Click to expand...
Click to collapse
Guide Updated.
Works Great !
Justin1198 said:
Guide Updated.
Click to expand...
Click to collapse
Thank you !!! This worked great!
It has not worked for me or something I did wrong
please help me
Since I can downgrade my S5 to kitkat does that mean that I can use the CyanogenMod build for kitkat on the s5 or will it brick my phone ?
First off, thank you so much for this guide! I recently got an old Galaxy S5 from my Dad, and rolled it back to KitKat using these instructions.
I'm experiencing two rather strange issues, though.
1) KitKat doesn't seem to be remembering my Wi-Fi password. I'm having to re-enter it every time I reboot the phone.
2) I'm getting a message on booting that "Safestrap is disabled. System will start in 10 seconds." The system starts like it should, but this message pops up every time. Is this normal, or will something correct it?
Any assistance would be appreciated. Thanks!
The Google Drive links are dead. Could we get new ones please @Justin1198?
Thanks in advance!