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.
Related
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
Hello, I had some general questions about the recoveries and how they work.
I have recently unlocked my bootloader and did the "recoveryinstallerfornoobs" process and then flashed the superuser zip file to gain root, which all worked, which is great.
So just for my understanding I had some questions:
-I guess I got some after market recovery program from the install process I did above?
-Can you only have 1 recovery program on your phone at a time
-I see in the app market there is a clockwork mod app there called "rom manager", is the same recovery app that some of this programs like Xboarder and such offer you the ability to flash (e.g. flash ClockworkMod 5.0.2.7) or is it different? With the app in the market place you can can make back ups of your current ROM but it is also the recovery app?
-The recovery app if my understanding is right is the app you boot into when you want to flash a new rom, wipe data, dalvik cache, battery stats, factory reset ...?
-Once you have root access why would you use a program to flash the clockwork recovery vs just installing it via the marketplace if they are the same?
-I just powered up in bootloader mode and then booted into recovery and notice that it says cwm based recovery v5.0.2.7 so I think I have the newest version from CWM, even newer than what is available in the market?
-I see and "X" watermarked in the back though so i believe this is "xboarder" I am surprised to see that if this app is from CWM
-How do I update this recovery in the future?
-I also don't see the app in my list of apps for ROM manager so I am starting to think the recovery and the clockwork app in the market place are different and do different things
Sorry for the long email and nood questions, however, any answers anyone can provide would be greatly appreciated.
windcan said:
Hello, I had some general questions about the recoveries and how they work.
I have recently unlocked my bootloader and did the "recoveryinstallerfornoobs" process and then flashed the superuser zip file to gain root, which all worked, which is great.
So just for my understanding I had some questions:
-I guess I got some after market recovery program from the install process I did above?
-Can you only have 1 recovery program on your phone at a time
-I see in the app market there is a clockwork mod app there called "rom manager", is the same recovery app that some of this programs like Xboarder and such offer you the ability to flash (e.g. flash ClockworkMod 5.0.2.7) or is it different? With the app in the market place you can can make back ups of your current ROM but it is also the recovery app?
-The recovery app if my understanding is right is the app you boot into when you want to flash a new rom, wipe data, dalvik cache, battery stats, factory reset ...?
-Once you have root access why would you use a program to flash the clockwork recovery vs just installing it via the marketplace if they are the same?
-I just powered up in bootloader mode and then booted into recovery and notice that it says cwm based recovery v5.0.2.7 so I think I have the newest version from CWM, even newer than what is available in the market?
-I see and "X" watermarked in the back though so i believe this is "xboarder" I am surprised to see that if this app is from CWM
-How do I update this recovery in the future?
-I also don't see the app in my list of apps for ROM manager so I am starting to think the recovery and the clockwork app in the market place are different and do different things
Sorry for the long email and nood questions, however, any answers anyone can provide would be greatly appreciated.
Click to expand...
Click to collapse
I got a headache reading so many questions. Felt like I was taking a final lol.
Long story short.
ROM Manager - Lets you make a backup on the entire phone. Allows you to flash ROMS.
CWM - The actual recovery. ROM Manager will go into CWM to flash the ROM or create a Nandroid backup.
Backing up Apps - I recommend using MyBackupPro.
"flash a new rom, wipe data, dalvik cache, battery stats, factory reset" - That's all done in CWM.
If you wanna update CWM, there will be a thread with the update. Usually you can flash it through ADB or flashing a zip file in CWM (same way as flashing a ROM
5.0.2.7 is the latest version of CWM
windcan said:
Hello, I had some general questions about the recoveries and how they work.
I have recently unlocked my bootloader and did the "recoveryinstallerfornoobs" process and then flashed the superuser zip file to gain root, which all worked, which is great.
So just for my understanding I had some questions:
-I guess I got some after market recovery program from the install process I did above?
-Can you only have 1 recovery program on your phone at a time
yes only 1
-I see in the app market there is a clockwork mod app there called "rom manager", is the same recovery app that some of this programs like Xboarder and such offer you the ability to flash (e.g. flash ClockworkMod 5.0.2.7) or is it different? With the app in the market place you can can make back ups of your current ROM but it is also the recovery app?
rom manager is the name of the program for android, clockwork recovery is the name of the recovery provided by rom manager. clockworkmod 5.0.2.7 is a recovery based on clockwork i believe (was made by xboarder)
-The recovery app if my understanding is right is the app you boot into when you want to flash a new rom, wipe data, dalvik cache, battery stats, factory reset ...?
yes correct. usually you can also flash kernels, but only if you have s-off...only some phones come with s-off by the luck of draw and there is no way at this moment to make s-on into s-off..you must flash kernels seperately and cannot be flashed through recovery.
-Once you have root access why would you use a program to flash the clockwork recovery vs just installing it via the marketplace if they are the same?
because the latest rom manager recovery does not have the 5.0.2.7 version from xboarder right now.
-I just powered up in bootloader mode and then booted into recovery and notice that it says cwm based recovery v5.0.2.7 so I think I have the newest version from CWM, even newer than what is available in the market?
like i said this version is based on clockwork recovery made by xboarder I believe. actually clockwork recovery is at 4.0.0.4 or something like that. do not use that recovery
-I see and "X" watermarked in the back though so i believe this is "xboarder" I am surprised to see that if this app is from CWM
like i said again it is made by xboarder and it is BASED ON clockwork Recovery
-How do I update this recovery in the future?
Same way you did now.
-I also don't see the app in my list of apps for ROM manager so I am starting to think the recovery and the clockwork app in the market place are different and do different things
I believed I have answered these questions above.
Sorry for the long email and nood questions, however, any answers anyone can provide would be greatly appreciated.
Click to expand...
Click to collapse
I think I passed my final
Thanks very much for both replies
To confirm, the app in the market place, ROM Manager, does not work with the clockworkMod 5.0.2.7 as they are developed by different individuals?
right now it is a bit of a pain as I have to take out the battery, and of course the back cover, in order to boot into recovery (I guess the phone just goes into a sleep mode when I power down and not a fulls shut down?)
I suppose with a matching app and recovery you can use the app to boot into recovery without needing to take the battery out?
Thanks very much and I hope I can return the favor to other noobs at some point
Here's a better answer...
Make backups of anything and everything.
Do anything and everything to get some experience for yourself.
If you break something, restore and try again.
Try different recoveries, try different roms, try different methods!
Nobody needs to ask for permission before doing anything. Just do it and learn from it! Don't be afraid of damaging your phone because with the exception of physical modification, I haven't heard of a way to break it yet. But... there's always a first.
windcan said:
Thanks very much for both replies
To confirm, the app in the market place, ROM Manager, does not work with the clockworkMod 5.0.2.7 as they are developed by different individuals?
right now it is a bit of a pain as I have to take out the battery, and of course the back cover, in order to boot into recovery (I guess the phone just goes into a sleep mode when I power down and not a fulls shut down?)
I suppose with a matching app and recovery you can use the app to boot into recovery without needing to take the battery out?
Thanks very much and I hope I can return the favor to other noobs at some point
Click to expand...
Click to collapse
your phone goes into sleep mode because you probably have it set on fastboot. Go under power settings and check fastboot off, this way you don't have to take out the battery. Also there are other ways of getting into recovery mode...read binary's first thread in the general section about how to root your phone.
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
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.
So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.