Hello everyone!
I'm facing an issue from a couple of days and would really appreciate some help.
I am running Dr.Ketan rom V3 on my N910G.
I'm rooted but unable to modify anything in the system folder.
The phone just freezes and reboots.
I'm posting this thread here because I have the same issue on stock NK3 firmware aswell. I use Xposed framework with greenify and waman xposed. Any app that accesses the system/app or any other system folder causes the phone to reboot (also the phone vibrates twice when that happens) I have given proper r/w permissions, tried a clean flash, wiped everything re-rooted and so on. Also any modifications in system folder from TWRP also fails.
I really appreciate some help/guidance on this.
Related
Loving my new GN3. I got it rooted successfully and made a Titanium Backup. I got around to installing Xposed (and Busybox, on my way to installing Wanam). Unfortunately, upon installing Xposed, I encountered a bootloop. I tried to disable Xposed from recovery, but I guess I can't install unsigned zips (locked bootloader?).
So I wiped data and reflashed Root de la Vega and restored from Titanium. I don't know enough about Xposed to avoid a bootloop. Has anyone with a Verizon GN3 had success installing Xposed? If so, what steps did you follow? Maybe I did something wrong. TIA.
jimbosi said:
Loving my new GN3. I got it rooted successfully and made a Titanium Backup. I got around to installing Xposed (and Busybox, on my way to installing Wanam). Unfortunately, upon installing Xposed, I encountered a bootloop. I tried to disable Xposed from recovery, but I guess I can't install unsigned zips (locked bootloader?).
So I wiped data and reflashed Root de la Vega and restored from Titanium. I don't know enough about Xposed to avoid a bootloop. Has anyone with a Verizon GN3 had success installing Xposed? If so, what steps did you follow? Maybe I did something wrong. TIA.
Click to expand...
Click to collapse
A lot of people, including myself, have successfully installed it without an issue. I just installed the app, hit the Framework button, then Install, rebooted, opened the app, downloaded some modules, installed them, rebooted, made changes in the modules, rebooted and enjoyed.
It was during the reboot after hitting the Framework button that I got the bootloop. I tried the adb script to intercept the bootloop, without success. I want to get Xposed installed, but now I'm concerned I'll get a bootloop every time. I wonder if it matters what Busybox I have.
You shouldn't have to install busybox for anything. Not sure if that is what caused your bootloop. Everything that I put on this phone that needs Busybox (Viper4Audio for example) installed just fine. Try Xposed again w/o Busybox.
Thanks for the advice. It took me a few hours to restore the phone and root. I wish we could do an update.zip via TiBu. I miss my unlocked GNex for that reason. Otherwise, the GN3 is a great handset. I'll have to think about trying Xposed again because I haven't found a successful way to recover from the bootloop without re-wiping the phone. Thanks again.
Fixed!
jimbosi said:
Thanks for the advice. It took me a few hours to restore the phone and root. I wish we could do an update.zip via TiBu. I miss my unlocked GNex for that reason. Otherwise, the GN3 is a great handset. I'll have to think about trying Xposed again because I haven't found a successful way to recover from the bootloop without re-wiping the phone. Thanks again.
Click to expand...
Click to collapse
For those that perhaps encountered the same problem, I got Xposed installed by uninstalling Busybox, then installing Xposed, then Wanam in the same boot, then rebooted. Plus, I was crossing my fingers. Probably the finger-crossing was the thing that made everything work. At any rate, I'm up and running.
Hey everyone,
After updating to 4.4.2 I had the SD Card Write problem that other people have been having, and I looked around and found two threads here with a guide to fixing it.
This one :
http://forum.xda-developers.com/showthread.php?t=2656627
and this one :
http://forum.xda-developers.com/showthread.php?t=2607215
I tried flashing both the files (Using Philz recovery) but it didn't help.
What's more confusing is that if I try to manually edit my platform.xml file, ES file explorer simply says "Task Failed" when I try to save the edited file or even replace it with a pre-edited one. This is despite granting it root permissions. I thought that maybe my phone didn't root properly, but root checker says it's rooted fine, and I've used Xposed, AdAway, Greenify, and Seeder successfully.
This is the method I used to root and install recovery :
http://forum.xda-developers.com/showthread.php?t=2655544
I'm not sure if this is related, but Titanium Backup's freeze feature isn't working for me anymore either. I have purchased the Pro version. It says freezing successful, but it simply doesn't do anything to the app I'm trying to freeze.
Any ideas what's happening here?
Did you try custom kernel? That's how I got it fixed
As far as I could tell, none of the custom kernels for the I9500 are stable. I need my phone to be rock solid (that's why I'm sticking to stock as well) so can't afford to flash a custom kernel.
Any alternate solutions anyone? And any idea what's causing this in the first place?
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Duncan1982 said:
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Click to expand...
Click to collapse
Maybe install busybox from Ericsson
Thanks I have busy box installed, this is very odd it is like there is a security file blocking everything despite root.
Xblast works as I have the clock centred and circle battery.
I am Experienced in root, and haven't stumbled upon this before.
Was thinking it was 4.4.4 but others are having success.
Hmmmm baffled.
Maybe has something to do with the security settings?
Install if you like the Wanam module and check if Disable Secure storage is disabled.
Thats all i can think about for now.
Nope nothing, even tried changing secure storage value to false and upon hitting save it reboots and nowt.
I give up can't think of anything oh it could be AEA Kernel that perhaps is causing the problem?
The only way to find out if its the kernel you flashed. Re-flash the stock-kernel
Thanks for getting back, Yeh back to stock and same problem. Maybe for some reason only have partial root, can't see that as supersu is there and functional and I have twrp custom recovery. Hmmmmm the mind boggles lol.
Reasonably experienced root user and for the life of me I can't sus what's up.
Tried refreshing the AEA Kernel and it won't even do that now.
Not that it's important, was just after a sound mod & changing the Dpi down to 560. Tried both it won't change.
Some security thing is preventing this but what could it be?
With some 4.4.4 ROMs on the note 2, there were problems with getting "full" root using twrp. I don't know if this is relatedn but the symptoms sound similar. Solution there was to use philz recovery (which isn't an option here), or for some Roms to flash an older version of supersu in twrp and then update after starting. Could be worth a shot.
Did you make sure to open the SuperSU app after rooting and update the binary? Are you SELinux permissive?
If you are having issues, download the recovery version of SuperSU, install it, then make sure to open the app so it updates.
You could also disable SELinux through the build.prop. Having a kernel that is SELinux permissive doesn't matter if you still have everything enabled in the build.prop
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
If none of that has helped, it is recommended you restore to stock and root again, making sure that reactivation lock is disabled before attempting to perform the root portion.
For some reason everything I flash through TWRP is being reverted after rebooting. I'm currently rooted with unlocked BL and disabled the write protection for system. This seem to have worked since I am able to modify the system through a file manager, Adaway on the other hand can't modify the system partition.
Furthermore, I added a file to the system partition through the TWRP file manager and this is persistant after boot
The zip file I tried to flash was the official xposed zip and from what I read in the forum it's working for other users withut problem.
Any ideas how to solve this?
Adaway,System partition.
Cyb3rzombi3 said:
For some reason everything I flash through TWRP is being reverted after rebooting. I'm currently rooted with unlocked BL and disabled the write protection for system. This seem to have worked since I am able to modify the system through a file manager, Adaway on the other hand can't modify the system partition.
Furthermore, I added a file to the system partition through the TWRP file manager and this is persistant after boot
The zip file I tried to flash was the official xposed zip and from what I read in the forum it's working for other users withut problem.
Any ideas how to solve this?
Click to expand...
Click to collapse
adaway doesnt work for me either with unofficial cm. the ZTE Axon 7 is not using official TWRP maybe the problem. Bugs
teeve said:
adaway doesnt work for me either with unofficial cm. the ZTE Axon 7 is not using official TWRP maybe the problem. Bugs
Click to expand...
Click to collapse
I got adaway working no but I don't know what exactly made it working since I tried a lot of things.
Could be indeed a bug, but why does it work for others?
Adaway,System partition.Android OS more sercure
Not sure,why. Granted adaway storage permission and still not working. Gonna try DrakenFX Rom,Z.A.D.Mix7,and see if adaway works there. Suspicion that android OS is locking down somewhat. The OS is making the user take more steps permission wise for sure.
Got it working now but I'm not sure what actually solved the problem.
I managed to screw up my system partition and had to use the repair Filesystem option in TWRP in order to be able to restore a backup of the system partition. After that everything I flashed in the recovery became persistent.
I restored backups before and it didn't solve my problem so it might be because of the repair Filesystem option?
Don't think so but who knows :laugh:
Hello. New here.
I rooted my S7 G930A running Nougat 7.0 following this guide: https://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
I actually found the guide somewhere else, but these are the files and instructions I used.
Rooting worked with no issues, and my phone works fine. Now I am interested in unrooting the device because of applications that won't work due to the safety net API knowing the phone is rooted.
I have already tried many things. There is an unroot.bat that comes with the files downloaded in the guide, but running that doesn't seem to actually unroot. SuperSU is still installed, and applications still don't work. I have also tried deleting the files using the ES File Manager, but I can only locate one "su" file which will not delete, and the superuser.apk or supersu.apk files are nowhere to be found. When trying to full unroot using SuperSU, I get the error "Uninstall failed!" I have also tried going back to the stock firmware using odin, but odin fails to install that as well.
Are there any current ways of unrooting that I'm missing?
Any help is appreciated, thank you.
Also, if this helps my baseband version is G930AUCS4BQC2
Okay, so I think I solved my own issue here. I was using the modified version of odin to install the stock firmware. Used the official odin and went back to G930AUCU4BQA6.
I have an additional question now. Since it reset the phone, any application that I made a system application is no longer a system app now right? But if I re-root the device, make the same apps system apps, and then use odin to upgrade to G930AUCS4BQC2 again it will unroot and my apps will still be system apps?
Thanks
Crossbows said:
Okay, so I think I solved my own issue here. I was using the modified version of odin to install the stock firmware. Used the official odin and went back to G930AUCU4BQA6.
I have an additional question now. Since it reset the phone, any application that I made a system application is no longer a system app now right? But if I re-root the device, make the same apps system apps, and then use odin to upgrade to G930AUCS4BQC2 again it will unroot and my apps will still be system apps?
Thanks
Click to expand...
Click to collapse
If you flash any ODIN file, it will wipe the system partition and then replace it with the one in the package. There's no way to get rooted system changes to persist through an ODIN.