[Q] Rerooting SuperNexus ROM - Galaxy S III Q&A, Help & Troubleshooting

Hey all, slightly worried atm. I've flashed various roms before so I know what I'm doing. However, I recently unrooted to use an app but now I want to change ROM again after using this one for so long I want more customization. Tried installing SuperSU from play store however the binaries aren't updating and I have no idea how to fix this. Will doing a factory reset restore the ROM to how it was before? Is there a way to manually install binaries via recovery? Any help would be greatly appreciated!

Yes, there it is. But if you are already using a custom recovery, you can install any ROM, as it does not matters if you are rooted or not.
If you still want to use your actual ROM
1.Download this: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/philz_touch_6.19.3-i9300.zip
2.Reboot to recovery
3.Flash this .zip
4.Go to Power options if you are using a CWM based recovery (like CWM, CWM Touch, Philz Touch or Devil Recovery) and choose "Reboot Recovery". If you are on TWRP, go to "Reboot" and choose "Recovery". This it will boot you into latest Philz Touch 6.19.3 recovery.
5. Now go to "Philz settings" and click "Re-root System (SuperSU)" and then "Yes - Apply SuperSu". The proccess takes like half of a second.
6. Click "+++++Go Back+++++" and then "Reboot System Now"
Now you are good to go You can instll SuperSu from the marjet and update the binaries, even if I think this install the latest binaries.

Also, in the future, if you have supersu pro you can disable supersu to use apps, versus totally unrooting.

wangdaning said:
Also, in the future, if you have supersu pro you can disable supersu to use apps, versus totally unrooting.
Click to expand...
Click to collapse
The option to hide root in surperSU is still not complete enough for some apps such as the Barclays Banking app. In this case it may be worth trying to use the exposed module designed for hiding root. Plus you can pre-set it on an app by app basis.

Hey guys, thanks for all your help. It was indeed the pingit app I had to unroot for. Well got my phone working again now so panic is over. Will definitely try the exposed way of trying it in the future!

Related

[Q] Xposed Framework

I have 2 questions. Does Xposed Framework work with LG P76921d? And 2, is it possible to install a recovery and back up your rom without an unlocked bootloader?
V1vatr0n said:
I have 2 questions. Does Xposed Framework work with LG P76921d? And 2, is it possible to install a recovery and back up your rom without an unlocked bootloader?
Click to expand...
Click to collapse
Xposed Framework works with P76920h. Using version 2.5 of the app now. (app_process:50, XposedBridge.jar:46)
GravityBox does not work. It will fill up ALL AVAILABLE internal space with an error log. Our ROM is unsupported anyway, so let it go.
Master Key multi-fix [2.0] DOES WORK.
(An aside: when did you update to 21d?)
It updated last year around august
Also, do you know any modules that might work? If not, there would be no point in installing xposed
V1vatr0n said:
It updated last year around august
Also, do you know any modules that might work? If not, there would be no point in installing xposed
Click to expand...
Click to collapse
I have the LGMS769 which is no different than the P769 and I have xposed framework, gravity box, battery themer, youtube adaway and have used multi window, xblast tools and some others without any issues.
Yes you can install cwm recovery for locked bootloaders with the L9 recovery installer from here -
http://forum.xda-developers.com/showthread.php?t=2095825
Download SuperSU and BusyBox by stericson from the play store. Install SuperSU then install BusyBox, open BusyBox and chose to install BusyBox v1.21.0 to system/xbin. Then install the L9 recovery installer, open the app and click on install ICS/JB stable recovery, once its installed it will tell you to reboot and when the device reboots the front keys will start flasing,(this means you have recovery access) press and hold down the volume (-) down button while the lights are flashing and the device will boot into the recovery. Once in recovery, immediately at this point make sure you perform a nandroid backup before exiting recovery.... this is just in case you get the "Encrypting Reset Phone" error when you exit recovery and boot to android OS, sometimes this will happen because of a BusyBox issue and rebooting back into recovery and flashing your nandroid backup will fix it.
Anyway that's it, you now have cwm recovery installed.
With the cwm for locked bootloaders you can perform and restore backups, flash zips and etc... But you cannot flash custom ROMs with it.
I'd recommend to now install xposed framework and whatever other modules that you want now that you have a nandroid backup. If you want to try a module then try it and see if it works... If it causes problems just uninstall it, if you still have problems or it causes a boot loop, boot to recovery and restore your nandroid backup and your fine.
xdrc45 said:
I have the LGMS769 which is no different than the P769 and I have xposed framework, gravity box, battery themer, youtube adaway and have used multi window, xblast tools and some others without any issues.
Yes you can install cwm recovery for locked bootloaders with the L9 recovery installer from here -
http://forum.xda-developers.com/showthread.php?t=2095825
Download SuperSU and BusyBox by stericson from the play store. Install SuperSU then install BusyBox, open BusyBox and chose to install BusyBox v1.21.0 to system/xbin. Then install the L9 recovery installer, open the app and click on install ICS/JB stable recovery, once its installed it will tell you to reboot and when the device reboots the front keys will start flasing,(this means you have recovery access) press and hold down the volume (-) down button while the lights are flashing and the device will boot into the recovery. Once in recovery, immediately at this point make sure you perform a nandroid backup before exiting recovery.... this is just in case you get the "Encrypting Reset Phone" error when you exit recovery and boot to android OS, sometimes this will happen because of a BusyBox issue and rebooting back into recovery and flashing your nandroid backup will fix it.
Anyway that's it, you now have cwm recovery installed.
With the cwm for locked bootloaders you can perform and restore backups, flash zips and etc... But you cannot flash custom ROMs with it.
I'd recommend to now install xposed framework and whatever other modules that you want now that you have a nandroid backup. If you want to try a module then try it and see if it works... If it causes problems just uninstall it, if you still have problems or it causes a boot loop, boot to recovery and restore your nandroid backup and your fine.
Click to expand...
Click to collapse
How much memory does this need? I tried to back up my phone but it said there was not enough room
V1vatr0n said:
How much memory does this need? I tried to back up my phone but it said there was not enough room
Click to expand...
Click to collapse
Really depends on what you have on the device as far as apps, user data and so forth, but can be around 1-2 gb.
When you make the nandroid backup select to backup to the SD card and not onto the device.
xdrc45 said:
Really depends on what you have on the device as far as apps, user data and so forth, but can be around 1-2 gb.
When you make the nandroid backup select to backup to the SD card and not onto the device.
Click to expand...
Click to collapse
I don't have that option. Do I just move the folder to the sd card?
EDIT: NVM I found it
After you get recovery in your phone... Go & Search this forum for @kuma82 's kumakan rom for locked bootloaders. Its the best I have found. I'm on cm9 for locked boot loader right now but I'm going to probably switch back to kumakan. He's already got the xposed framework & gravity box set up. Internal/external memory swap script too. Highly suggest it.
Sent from my LG Optimus L9 using Tapatalk

[Q] Rooting and Superuser

Hi! I've just rooted my device (Nexus 5) with Chainfire auto setup and I've downloaded Superuser by Clockworkmod. When I opened it up, it showed a message saying that I needed to update the SU binary, I went back to the Play Store, I read the description and I found a link, that allows me to install it from a recovery files. Once I downloaded it I opened the app again using the recovery files, Android crashed and rebooted itself, but during the boot it showed a dead android image (the one with the red triangle). I've turned off my device (Nexus 5) and then I've reboot it, now all works fine. I'm terribly scared, what the hell happened? It's my fault or Superuser just crashed?
SimoPiersi said:
Hi! I've just rooted my device (Nexus 5) with Chainfire auto setup and I've downloaded Superuser by Clockworkmod. When I opened it up, it showed a message saying that I needed to update the SU binary, I went back to the Play Store, I read the description and I found a link, that allows me to install it from a recovery files. Once I downloaded it I opened the app again using the recovery files, Android crashed and rebooted itself, but during the boot it showed a dead android image (the one with the red triangle). I've turned off my device (Nexus 5) and then I've reboot it, now all works fine. I'm terribly scared, what the hell happened? It's my fault or Superuser just crashed?
Click to expand...
Click to collapse
You didn't do any damage to your device. What it seems like is that you only have root access and not a custom recovery like ClockWorkMod or TWRP so when you went back to the app it went to boot you to recovery to install them and it rebooted you to the stock recovery which does not allow installation of files that aren't signed with a specific factory key. You should be able to update the binary with the normal install mode on the Nexus without issues. If you want a custom recovery, there are various ways to do it, but the easiest would be with the GooManager app (free in the Play Store) where you grant it SU access, hit Menu > Install OpenRecoveryScript and let it do it's thing. Then when you boot to recovery, you will have a version of TWRP. This is a great custom recovery. Touch based, Fast. Allows you to back up all the important parts of the phone so you have a system backup - called a nandroid (which you should do and save to a safe spot) as well as install custom versions of android, themes, kernels, and all types of other mods as well as a way to do a complete factory and /sdcard wipe if ever needed.
Thanks GOD!
es0tericcha0s said:
You didn't do any damage to your device. What it seems like is that you only have root access and not a custom recovery like ClockWorkMod or TWRP so when you went back to the app it went to boot you to recovery to install them and it rebooted you to the stock recovery which does not allow installation of files that aren't signed with a specific factory key. You should be able to update the binary with the normal install mode on the Nexus without issues. If you want a custom recovery, there are various ways to do it, but the easiest would be with the GooManager app (free in the Play Store) where you grant it SU access, hit Menu > Install OpenRecoveryScript and let it do it's thing. Then when you boot to recovery, you will have a version of TWRP. This is a great custom recovery. Touch based, Fast. Allows you to back up all the important parts of the phone so you have a system backup - called a nandroid (which you should do and save to a safe spot) as well as install custom versions of android, themes, kernels, and all types of other mods as well as a way to do a complete factory and /sdcard wipe if ever needed.
Click to expand...
Click to collapse
That's why I love XDA Developers, because there are people that knows what they are saying! Thank you so much. Now I'm wondering if I should install a recovery mod as you suggested. Do you think I have to install Tasker as well? My first idea was to install Xposed modules, after rooting my device, but when they say "be careful it could **** UP your device" I wonder "Why the hell you should say that when I want to install them?", so I still think about that. Thank you again!
SimoPiersi said:
That's why I love XDA Developers, because there are people that knows what they are saying! Thank you so much. Now I'm wondering if I should install a recovery mod as you suggested. Do you think I have to install Tasker as well? My first idea was to install Xposed modules, after rooting my device, but when they say "be careful it could **** UP your device" I wonder "Why the hell you should say that when I want to install them?", so I still think about that. Thank you again!
Click to expand...
Click to collapse
Tasker is not necessary for any of this. Tasker is for automating your phone to do certain tasks under specific conditions you set up. Such as setting your phone to turn on wifi based on location. You certainly don't NEED a custom recovery, but if you like to play with your phone, then it is a great way to be able to make a complete backup to restore in case of emergency. When you install and activate the Xposed framework, it will also create a zip file on your storage that will disable it while flashed through a custom recovery. If things go super wrong, you can also restore the phone via PC using fastboot tools and factory img files from Google. What I like to do is:
Download factory img files and set up adb and fastboot
Root
Recovery
Nandroid
Backup Nandroid and complete storage to PC
Flash whatever roms or mods
If it completely bricks and you lose access to storage then restore system from PC then redo recovery, copy files and nandroid back to storage and restore backup
bam - back in business.

Help with T769 Tmobile Recovery & Custom ROM on 4.0.4

Hey guys I'm trying to install the Themed ROM for P769 Locked bootloader. (http://forum.xda-developers.com/showthread.php?t=2468880) I have the phone rooted from awhile back, i cant recall what i used to root it, the phone is still on 4.0.4, I am trying to put a recovery on it to install this ROM, but I dont see any recoveries for 4.0.4, I've seen a few different ones for JB but I'm not sure if its compatible.
This is the recovery it said to install (http://forum.xda-developers.com/showthread.php?t=2095825) but the issue is that the link to the recovery was taken down, so I'm not sure what recovery I can install.
TLDR: I got a rooted T769 on 4.0.4 and i would like to install the themed ROM for T769 with Locked BL.
eric303 said:
Hey guys I'm trying to install the Themed ROM for P769 Locked bootloader. (http://forum.xda-developers.com/showthread.php?t=2468880) I have the phone rooted from awhile back, i cant recall what i used to root it, the phone is still on 4.0.4, I am trying to put a recovery on it to install this ROM, but I dont see any recoveries for 4.0.4, I've seen a few different ones for JB but I'm not sure if its compatible.
This is the recovery it said to install (http://forum.xda-developers.com/showthread.php?t=2095825) but the issue is that the link to the recovery was taken down, so I'm not sure what recovery I can install.
TLDR: I got a rooted T769 on 4.0.4 and i would like to install the themed ROM for T769 with Locked BL.
Click to expand...
Click to collapse
I'm guessing you mean that you have a P769 T-Mobile version.
Here is a link to the L9 Recovery Installer - https://www.dropbox.com/s/l8tegpmiyh8moa5/L9RecoveryInstaller_1.5.0.apk
Since your already rooted, just make sure that you download and install BusyBox by stericson from the playstore, before installing the L9 recovery installer. It needs BusyBox installed on your device for it to work properly.
Download the Kumakan themed ROM to your external sdcard.
Open the BusyBox app and click on and select the version of BusyBox to install to the device and select version 1.21.0 to install.
Then install the L9 recovery installer app. Open the app and select "Install recovery" then select "jb/ics stable version", then grant it root rights through SuperSU when asked for permission.
Once it says recovery is installed, select power down/reboot the device. After the phone starts to boot up you'll see your front keys blinking this means you have recovery success and to enter into recovery immediately press and hold volume(-) down button while lights are still blinking... You are now in recovery mode. I would highly recommend that you immediately preform a nandroid backup of your L9 right now before doing anything else. Select backup and restore, choose backup and choose backup to external sdcard.
Once the nandroid backup is done then you are free to flash the Kumakan themed ROM that you want to install. Just follow the directions from the ROM thread to install the ROM.
xdrc45 said:
I'm guessing you mean that you have a P769 T-Mobile version.
Here is a link to the L9 Recovery Installer - https://www.dropbox.com/s/l8tegpmiyh8moa5/L9RecoveryInstaller_1.5.0.apk
Since your already rooted, just make sure that you download and install BusyBox by stericson from the playstore, before installing the L9 recovery installer. It needs BusyBox installed on your device for it to work properly.
Download the Kumakan themed ROM to your external sdcard.
Open the BusyBox app and click on and select the version of BusyBox to install to the device and select version 1.21.0 to install.
Then install the L9 recovery installer app. Open the app and select "Install recovery" then select "jb/ics stable version", then grant it root rights through SuperSU when asked for permission.
Once it says recovery is installed, select power down/reboot the device. After the phone starts to boot up you'll see your front keys blinking this means you have recovery success and to enter into recovery immediately press and hold volume(-) down button while lights are still blinking... You are now in recovery mode. I would highly recommend that you immediately preform a nandroid backup of your L9 right now before doing anything else. Select backup and restore, choose backup and choose backup to external sdcard.
Once the nandroid backup is done then you are free to flash the Kumakan themed ROM that you want to install. Just follow the directions from the ROM thread to install the ROM.
Click to expand...
Click to collapse
I follow all of the above steps to a tee. The recovery installs fine but when I try to reboot back into my rom all I can get is the white screen that says " encrypting" and " reset phone"... I'm on software version, P76920h.... any help would be appreciated.
Mangani001 said:
I follow all of the above steps to a tee. The recovery installs fine but when I try to reboot back into my rom all I can get is the white screen that says " encrypting" and " reset phone"... I'm on software version, P76920h.... any help would be appreciated.
Click to expand...
Click to collapse
Sorry for the late reply!
Did you make a nandroid backup when you installed and booted recovery?
If so, all you have to do is just reboot to recovery and restore your nandroid backup and you'll be back in businesses.

Latest CWM SuperUser flashable zip

Hi, folks,
I have pretty much wasted the past 3-4 hours trying to get cwm superuser to work.
I installed .314 UK generic firmware using FlashTool & unticked wipe data, then used TowelRoot v12 to root then flashed NUT's dual recovery but no matter what cwm superuser flashable zip I use I cant get it to work right, it always prompts me to use recovery install when I open the SuperUser app, tried that but I just get error saying there was a error installing SuperUser. If I disable SuperUser then install SuperSU & SuperSU pro from market I get root access but SuperSU has always had issues with AdAway applying the hosts file so I switched to CWM SuperUser when I was on .402 firmware.
I did have the flashable CWM zip file but can no longer find it
Really need some help with this.
BanziBaby said:
Hi, folks,
I have pretty much wasted the past 3-4 hours trying to get cwm superuser to work.
I installed .314 UK generic firmware using FlashTool & unticked wipe data, then used TowelRoot v12 to root then flashed NUT's dual recovery but no matter what cwm superuser flashable zip I use I cant get it to work right, it always prompts me to use recovery install when I open the SuperUser app, tried that but I just get error saying there was a error installing SuperUser. If I disable SuperUser then install SuperSU & SuperSU pro from market I get root access but SuperSU has always had issues with AdAway applying the hosts file so I switched to CWM SuperUser when I was on .402 firmware.
I did have the flashable CWM zip file but can no longer find it
Really need some help with this.
Click to expand...
Click to collapse
If you're not on CWM, you can't use CWM SuperUser. Install SuperSU and use that. You can also switch to AdFree which is what I use. You'll also need to install XZDualRecovery to be able to write to /system.
Sent from my SGP311 using XDA Free mobile app
Thanks for the reply
I was using CWM superuser with no issues on .402 UK generic & Philz recovery, I have always had issues with SuperSU both on my old Galaxy S3 with custom roms & now on my Z2, most of the time with SuperSU any app that needs root access will freeze due to the delay in SuperSU showing the alert & as I mentioned above with AdAway not being able to apply the hosts file 90% of the time.
I also have Dual Recovery installed but keep losing it, seems that using the NDR tools app it installs causes the phone to forget that the recoveries are installed.
Just want some help with this issue & it would be great if someone could post a working kitkat CWM superuser flashable zip.
Can anyone else help me with this?
Have just done a full wipe & used Flashtool to install UK generic .314, have used EasyRoot 12.1 to root & it says I'm rooted. I then install CWM SuperUser from market & when opening it says the su binary needs to be updated & only gives recovery install or cancel options, I chose recovery & it reboots into Philz recovery & says it has installed but Philz says root is broken. When I boot the phone again I get a notification from SuperUser saying the binary needs to be updated again but when I tap recovery it just says there was a error.
Really would appreciate some help here as I need to get AdAway installed, change the DPI & use the nextapp kitkat SD fix app.
Cheers.
EDIT: forget it, got it fixed myself, now CWM superuser is working fine.

Xposed Installer Help

Hi guys
Apologies if this has been posted in the wrong section.
I have recently inherited a Galaxy S2 (GT-I9100) running the CyanogenMod 12.1, Android Version 5.1.1
I have spent the last two day trying to and failing miserably to install Xposed Installer V3.0 Alpha 2, I have searched Google and read through numerous forums on how to resolve this, but the more I read the more confusing it becomes. I would really appreciate any help/assistance in helping me fix the problem, so that I can run the app without any issues. When I access the app's log it states:
data/data/de.robv,android,xposed.installer/log/error.logpen failed. ENOENT (No such file or directory)
Also, when I try to run Titanium Backup 6.1.0, I get an error stating:
Sorry, I could not acquire root privileges. This application will *not* work! Please very that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
I have gone into Developer Options and set Root Access to Apps and ADB.
As I new to Android my understanding (please correct me if I am wrong) that the CyanogenMod 12.1 was actually a ROM and therefore Titanium Backup should work. FYI SD Maid not working.
Any help on both of these issues would be most appreciate, please bear in mind I am a noob where Android and Galaxy S2 are concerned.
Thanks in advance.
The forum for the i9100 is located here, but because it's so close to the i777 we can probably help a bit.
Sounds to me like your phone isn't rooted, as none of the apps you mention will work without root privileges. Install the latest SuperSU; you should be getting access prompts if you're correctly rooted.
If you are not prompted for root access when opening apps such as Titanium Backup, you'll need to install Framaroot and use the Aragorn exploit in order to easily root your device. Let us know if either of these work for you.
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
pops1368 said:
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
Click to expand...
Click to collapse
Strange. In that case have you tried doing a complete wipe in recovery, then reinstalling the ROM? In your case you would boot into recovery, wipe /system and dalvik cache, then install ROM and gapps. Just make absolutely certain you're running a custom recovery before doing this, such as CWM (ClockworkMOD) or TWRP (TeamWin), or you could damage your device if you're on stock recovery. And, of course, make sure you have the ROM/gapps already on your device before wiping everything!
Because you inherited the device the best method would normally be to flash back to stock and start all over - if for nothing else it's a good learning experience. Hope this helps.
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
pops1368 said:
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
Click to expand...
Click to collapse
As long as you have a custom recovery there's very little that can go wrong with a full wipe. I would suggest booting into recovery first (power button + both volume keys, then release at the Samsung logo) and make sure you're running either CWM or TWRP. While in recovery do a backup first, as a "just in case". You can always restore your device fully from a backup.
The next thing to remember is to make sure your ROM/gapps are compatible with one another. For instance, if you're installing a CM12 (Android 5.0+) ROM make sure your gapps are also 5.0+.
Best of luck!
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
pops1368 said:
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
Click to expand...
Click to collapse
Best option for you is to go to the i9100 forum and download a kernel for your phone that is compatible with the OS version you want to install (CM12, which is 5.1. in your case). With your device (as well as our i777), the kernel and recovery are fused together, so you cannot use ROM Manager to install a recovery to a separate partition.
Once you have an i9100 5.1 kernel downloaded on your phone you can flash it through the current recovery you have, then immediately reboot back into recovery. You'll then have the correct recovery and can proceed as normal with the ROM installation.
CWM absolutely has a backup/restore option, but it's hidden in a sub menu. My personal recommendation is to use TWRP recovery, as it's still being developed and is more robust/user friendly.
So as a general rule stay away from ROM Manager for system specific changes.
Thank you so much for the information/advice, I really do appreciate all of it.

Categories

Resources