My TWRP suddenly went to "that state". And now System is ReadOnly. What I did - I used Super SU-app to take root temporarily "away" because I needed to use bank app. Then I enabled root again. Worked just great. But I think after that recovery is "dirty" I cannot find any other reason. Before root off / root on it TWRP was OK. Any idea how to fix? I have tried to flash same and previous version from Bootloader, cannot do - fastboot flash it OK but when I boot to recovery, nothing has changed. My root is working OK while on OS (I am still rooted).
I also tried to fix it flashing Asgard kernel. Kernel flash was OK and now I am on Asgard but TWRP is still the same even after flashing it again after Kernel.
I am on stock (Android 7.0) which I have debloated (everything worked just great before that switch root on / off)
File System is ext4.
Any ideas or do I just have to go back to original stock and then TWRP and root again? (Just do not want to do that too much work)
Thank You
Related
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
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.
Troubles started when trying to upgrade to 23.5.A.0.575 shown here. The ROM simply got itself unrooted and ate my recovery. So I downgrade to 17.1.2.A.0.314 in order to root, successfully root, and then try every goddamn way to install a recovery but it just does not work. I've used the Nut's dual recovery here, the install script reports everything's peachy, it installs NDRUtils, but when I ask to reboot to recovery it just reboots normally. Also uring one of my attempts, the final ROM stayed rooted but /system became readonly, rendering it useless.
What do I do? If I flash the older firmware, shouldn't it wipe everything and make it possible to install the recovery normally - a recovery claimed to work with locked bootloaders? (I'm not unlocking my bootloader).
I lost my root (when updating to 575 from 570)three four days back, I installed lollipop ftf,rooted and installed recovery.
Didnt have any issues.
I installed .28 lp
http://www.ibtimes.co.uk/how-root-xperia-z3-z2-android-5-0-2-firmware-build-23-1-28-1509398
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!