Hey everyone,
So far I already rooted two phones to be able to delete system apps, which isn't a big deal.
Otherwise I would consider myself a root-newbie.
Right now I have troubles with my phone using root acces and flashing a custom rom.
My Honor 3c has the following history:
-Rooted the phone to delete system apps --> worked
Months go by
-Reset phone to factory settings --> phone sais it's still rooted, deleting of system apps wouldn't work anymore
Few weeks ago
-Decided to go with cyanogen mod
Here is where I don't know how to proceed.
When I enter bootloader to flash twrp or anyhting else, the system tells my that I
"can not install any OTA updates, because the phone has been rooted". I can't do anyhting but reboot.
What I tried so far:
Unroot via SuperSu or deleting the su & akp via file explorer
Result: When I rebooted the phone, root was re-established.
What I would try:
Root the phone again - but: how to do this when I can not flash a thing via boatloader?
I don't want to stick to the custom rom and unnecessary system apps Please help if u can
Please excuse if this is not the right forum to post.
Related
(SOLVED)
Hey guys, first time root here. HTC One AT&T 32gb
I was succesfully through the process, used a guide on htconeroot.com to go through all of the steps. Everything went just as expected and I had root access through superSU (was able to install and use root apps, such as Titanium Backup and AdFree). I used Root Manager to flash Clockworkmod because I saw a ROM I'd like to use in the future that only supported that custom recovery. After succesfully flashing that, I then made a backup using Root Manager. Everything was successful and expected, but upon reboot into my stock ROM from the original unrooted phone I had apparently lost SU binaries and root access. Also, ROM Manager (v5.5.3.0) cannot find any backups.
I tried reflashing superSU from the original rooting guide (UPDATE-SuperSU-v1.65.zip), and while it was successfully rooted, I still did not gain root access. I had read through some forums that using the stock ROM that came with the phone might lose root because of the stock recovery, but not sure if that is what happened. I have not installed a custom ROM on this phone yet.
Any help would be appreciated.
UPDATE: Solved, had to select "No" when rebooting from CWM on stock recovery option
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.
Hello how are you ? Well, as everyone here I am another who needs help. I have a Xperia Z2 and today I finally managed to make the ROOT (yeah!) Only that my happiness was short-lived, because of a stupid my ...
After having the procedure done and all settled cute I saw that had a android update message to 5.1.1 (since to root I installed 5.0.4) then went all happy thinking that would get being a super user and with the updated device falls into the mistake of installing. At the time of restart phone me the message: "ERROR - Update Failed", and has no way to do anything. I've tried various methods but none worked. "Now Joseph," what do I do? haha
Please respond with the correct English because I am Brazilian and I use the Google translator to understand what they say.
gahnunees said:
Hello how are you ? Well, as everyone here I am another who needs help. I have a Xperia Z2 and today I finally managed to make the ROOT (yeah!) Only that my happiness was short-lived, because of a stupid my ...
After having the procedure done and all settled cute I saw that had a android update message to 5.1.1 (since to root I installed 5.0.4) then went all happy thinking that would get being a super user and with the updated device falls into the mistake of installing. At the time of restart phone me the message: "ERROR - Update Failed", and has no way to do anything. I've tried various methods but none worked. "Now Joseph," what do I do? haha
Please respond with the correct English because I am Brazilian and I use the Google translator to understand what they say.
Click to expand...
Click to collapse
First you need to remove root and make sure all root files from your /system are gone.
Root prevent the phone from doing OTA updates because you have modified your system.
If you can't update OTA try flashing using flashtool it will remove root obviously because it's a newer Frimware.
For your information 5.1.1 root isn't the same way as 5.0.2.
Quick tip if you want to keep your root access try installing a recovery and busybox and make a pre rooted Frimware and flash it in the recovery.
I hope this was helpful.
Shady_BlackSn0w said:
First you need to remove root and make sure all root files from your /system are gone.
Root prevent the phone from doing OTA updates because you have modified your system.
If you can't update OTA try flashing using flashtool it will remove root obviously because it's a newer Frimware.
For your information 5.1.1 root isn't the same way as 5.0.2.
Quick tip if you want to keep your root access try installing a recovery and busybox and make a pre rooted Frimware and flash it in the recovery.
I hope this was helpful.
Click to expand...
Click to collapse
Thank you for wanting to help, but have tried for FlashTool, PRF Creator and various manual methods in the mobile itself. Here's a video of how it is: "Z3 COMPACT AFTER ROOTING"
However, recalling that mine is the Z2. I found this video on youtube and that's exactly how is my mobile, but I can not post links forum.
If it's this https://youtu.be/VPrJthvqKfE
Flashtool will fix your issue. Install the drivers and flash a ftf file to fix the system partition.
Sent from my D6503 using Tapatalk
1.Download a pre-rooted firmware 5.1.1 (flashable zip)
2.Boot into Recovery (TWRP Recommend)
3.Install - Choose ROM direction - flash the ROM zip and wipe cache\dalvik cache
(don't worry this won't wipe your data)
# I highly recommend you to do a factory reset after flashing because if you didn't the phone will be laggy and battery will drain extremely fast
*And If you have xposed installed don't forget to remove it because it may causes problems
If I Helped, Leave A Thanks ?
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.
Dear All,
Sorry if am re-posting the same, and as am new here and need an urgent help, started this thread.
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.
Many Thanks,
BR,
Shiva
I belive you need to flash the stock 4.3 jellybean rom with odin, and root it afterwards.
Silviu_gs3 said:
I belive you need to flash the stock 4.3 jellybean rom with odin, and root it afterwards.
Click to expand...
Click to collapse
Many Thanks, seems to be a good option and I will try that.
You need a recent version of twrp recovery
rchtk said:
You need a recent version of twrp recovery
Click to expand...
Click to collapse
TWRP 3.0.0..???????????
First of all.. Update TWRP to 3.0.2, you are NOT supposed to see the message that tells you that root is gone, as (official) CM13 includes root from now on.
For root, inside Android go to Settings > Developer Options > Root > Only apps.
Do it via Odin as only 3.0.2 is available in a .tar file (latest version), should not be hard.
Not only that, but upgrading from CM11 to CM13 is not recommended, as it causes multiple compatibility issues with installed apps (afaik).
You are better off with wiping it all and install CM13 Clean, and if you decide to; you must also flash Gapps (optional) directly after CM13 (no reboot).
Read more on the official thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-13-nightlies-i9300-t3272811
SGS3 I9300: Root and Custom Recovery lost after CM13 - SOLVED
Dear All,
Thank you for your valuable advice and suggestions. I used ODIN to flash back to stock ROM and now everything works as it is like out of the box. I will root again perhaps in a few days and the flash the stable release of CyanogenMod. Will keep you posted. I wish the Android M snapshot is released by then.
Thanks again,
Cheers,
Shiva