Related
Yes, I did read other posts before posting myself, and I still have no clue what to do.
I have CWM v5 something, along with an associated SuperSU I have installed onto my phone.
I have the newest CVM 6.0.3.1 version .img file installed from their website.
What do I do now?
ROM Manager doesn't work, as my device is not listed.
I don't know where my /sdcard/ folder is located so I can't drop the .img file into that folder, and can't use a line of code for the terminal emulator.
Help!!
Stefan_S said:
Yes, I did read other posts before posting myself, and I still have no clue what to do.
I have CWM v5 something, along with an associated SuperSU I have installed onto my phone.
I have the newest CVM 6.0.3.1 version .img file installed from their website.
What do I do now?
ROM Manager doesn't work, as my device is not listed.
Click to expand...
Click to collapse
You should be able to use the same method as you did when you first installed CWM, do you remember how you got the rom manager up originally? Did you flash it over usb (fastboot method)?
What phone btw?
Fixed it
Tried a bunch of methods,
Went into GS3 Toolkit and got a new-ish version of CWM (6.0.2 something, not the newest 6.0.3.1).
Regardless, this was an upgrade from my 5.x.x.x version, which allowed me to install the stable build of CM 10.
I have a Samsung Galaxy S3 SGH-I747m with Rogers.
People should really create tar files from the img files.. but anyways, i got it !
I downloaded the Beanstalk KitKat ROM today and planned to install it to replace Jellybean. I copied the ROM zip and gapps to the internal storage, unplugged the phone and rebooted into recovery. I wiped the cache and data, but when I went to install the ROM zip it wouldn't work; it returns an error of "set_metadata_recursive: some changes failed" with a status of 7. Before I rebooted into Android to re-copy the files over, assuming something went wrong in the copy process, CWM prompted me saying that I might have lost root and whether or not it should fix it. I hit yes. Now, I cannot reboot back into Android. The phone hits the HTC loading screen, reboots, and then ends up back at CWM.
Is there any way I can get a ROM zip on my phone so that I can fix this? Or is my phone essentially bricked?
Any help is appreciated.
If you have adb drivers installed on your computer, you can do this: adb push path/to/ROM.zip /sdcard/ROM.zip make sure you mount data first. See this thread: http://forum.xda-developers.com/showthread.php?p=37535001
Are you using the newest version of tour recovery? You need the latest cwm or twrp beta to flash kitkat ROMs.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
If you have adb drivers installed on your computer, you can do this: adb push path/to/ROM.zip /sdcard/ROM.zip make sure you mount data first. See this thread: http://forum.xda-developers.com/showthread.php?p=37535001
Are you using the newest version of tour recovery? You need the latest cwm or twrp beta to flash kitkat ROMs.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
I'm running CWM 6.0.3.1. I assume this is outdated now as I installed it a while ago. I'll find a download for the latest one and install that too.
Thanks for your help.
Klayderpus said:
I'm running CWM 6.0.3.1. I assume this is outdated now as I installed it a while ago. I'll find a download for the latest one and install that too.
Thanks for your help.
Click to expand...
Click to collapse
Use this one http://invisiblek.org/dlx/recovery/recovery-clockworkmod-6.0.4.5-dlx-UNOFFICIAL.img
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
I am currently on cm-10.1.3 galaxy s2 i9100 intl (International, NOT G). It has CM-based Recovery v6.0.3.6. How do I upgrade to new rom cm-11 nightly?
1. Can the above CM-based Recovery v6.0.3.6 be usd for the flashing? Any link to a detailed post would be appreciated? I have seen references to problems if the above used, or first one has to goto cm-10.2 etc. It looks like cm-10.2 has been pulled back, I do not see that among cm downloads area.
2. Using the built in 'CM Check for updates' I downloaded the latest cm-11 nightly, it went without any error. But I do not see that .zip file anywhere. Where is that supposed to be?
Any help is appreciated.
CqN said:
I am currently on cm-10.1.3 galaxy s2 i9100 intl (International, NOT G). It has CM-based Recovery v6.0.3.6. How do I upgrade to new rom cm-11 nightly?
1. Can the above CM-based Recovery v6.0.3.6 be usd for the flashing? Any link to a detailed post would be appreciated? I have seen references to problems if the above used, or first one has to goto cm-10.2 etc. It looks like cm-10.2 has been pulled back, I do not see that among cm downloads area.
2. Using the built in 'CM Check for updates' I downloaded the latest cm-11 nightly, it went without any error. But I do not see that .zip file anywhere. Where is that supposed to be?
Any help is appreciated.
Click to expand...
Click to collapse
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
noppy22 said:
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
Click to expand...
Click to collapse
Thank you very much for your very helpful reply. I have more to clarify now.
A. Well, I found out why I dont see the cm-11 zip file. (I did search in the *nix console with
'find / -name cm-*.zip'. Couple of the other older zips do show up.). To see the problem I had to watch during the full download; towards the end it has a very brief popup like 'MD5 check failed'. I have no idea why the latest cm-11-20150426-nightly md5 is failing at my end!! The previous 20150412 could not be downloaded either (though I was not there to catch the md5 error, but since there was no file, I assume it failed similarly.) So I tried the 20150406, and that did ask me if I wanted to flash, I cancelled that, and the zip is in the /storage/sdcard0/cmupdater/ . Good.
B. I had never used any philz recovery tool before. So to flash this new recovery, I use the current CM-based Recovery v6.0.3.6, just like I load the gapps zip?
B1. When you say philz, from third post, this one? 8th September 2012, 11:40 PM |#3 ?
It says it 'can be flashed in stock recovery 3e: No Yellow Triangle'. Mine is no longer the stock recovery, since I had updated to the v6.0.3.6. My phone has a Yellow Triangle on boot! Does this mean I cannot use this one? Kindly explain.
So philz recovery is different flavour from the CM-10.1.3 based I have? I had used the flashing only once before to come from the stock to the 10.1.3. Are these two recoveries fully compatible?
C. I had already downloaded the gapps zip for cm-11. The date of that is rather old; I assume there is only one gapps zip version for the cm-11?
D. Since there have been so many cm-11 NIGHTLYs out there, no stable, or monthly, how does one select one of the more stable among them. I really do not need the latest, the primary reason is the main version Andorid upgrade, and I want the ones after the battery drain problem, and the music stop problems were fixed. Is there any place where they give a relative 'goodness' grading to these NIGHTLYs?
Thank you for your continuing help.
noppy22 said:
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
Click to expand...
Click to collapse
This is a continuation of my last reply to you. Double checking: The latest zip file I see at the goo.im downloads site phiilz_touch->CWM_Advanced_Editiion->i9100 is
philz_touch_6.48.4-i9100.zip Sun, 06 Jul 2014 22:47:33 GMT
Should I flash this from my CM-based Recovey v6.0.36 ?. After this flash, i suppose I can do a regular phone booting also, before flashing the cm-11? Thank you.
CqN said:
This is a continuation of my last reply to you. Double checking: The latest zip file I see at the goo.im downloads site phiilz_touch->CWM_Advanced_Editiion->i9100 is
philz_touch_6.48.4-i9100.zip Sun, 06 Jul 2014 22:47:33 GMT
Should I flash this from my CM-based Recovey v6.0.36 ?. After this flash, i suppose I can do a regular phone booting also, before flashing the cm-11? Thank you.
Click to expand...
Click to collapse
The latest philz is correct - 6.48.4. Yes you can flash it from your recovery, it is just an updated version of the v6.0.3.6, something like 6.0.4.something with touch ui. It will work flashing later android versions where the earlier one may not. Just flash it and reboot straight back into recovery when you are ready to do your backups, wipes and installs.
The nightly cm11's are all very stable at this stage; I would download the latest, but the more important bug fixes were implemented from about mid january(eg. fpbug fix). Anything after that would be ok. The gapps, I would download the latest just before I flashed the rom, you are better off with the latest play services etc. As long as they are compatible to 4.4.4, you can choose whatever gapps you want. I like minimal gapps by @jajb for example, but it's up to you. HERE are most of the gapps available at the moment.
If you can I would download the rom by pc. You are recommended to check the md5 sum whenever you download roms/gapps to make sure the download was successful
noppy22, Thank you. That clears up many things. The link to the gapps is a big help. I had previously read somewhere that my phone needed a small foot print gapps, because the system (?) partition was ony about 500mb. That was what I had downloaded, but I can check the newer ones.
How do I check the md5 checksum after the download? I have access to the terminal, and I can use minimal *nix commands, once i know the utility name At philz, there were .zip and .zip.md5 of the same version date. Can I flash either one? I know, as I mentioned in two msgs ago, when I use the system download of nightly, it automatically checks the md5, and saves only if it is correct. But I simply downloaded the gapps, and the .zip of he philz, so I do not know how to check the md5. Info-zip versions of zip has their own integrity check with unzip -t, but the unzip in busybox of Android appears minimal without those features. Thank you agian, I am almost ready to upgrade, as soon as I hear back from you
CqN said:
noppy22, Thank you. That clears up many things. The link to the gapps is a big help. I had previously read somewhere that my phone needed a small foot print gapps, because the system (?) partition was ony about 500mb. That was what I had downloaded, but I can check the newer ones.
How do I check the md5 checksum after the download? I have access to the terminal, and I can use minimal *nix commands, once i know the utility name At philz, there were .zip and .zip.md5 of the same version date. Can I flash either one? I know, as I mentioned in two msgs ago, when I use the system download of nightly, it automatically checks the md5, and saves only if it is correct. But I simply downloaded the gapps, and the .zip of he philz, so I do not know how to check the md5. Info-zip versions of zip has their own integrity check with unzip -t, but the unzip in busybox of Android appears minimal without those features. Thank you agian, I am almost ready to upgrade, as soon as I hear back from you
Click to expand...
Click to collapse
Yes you are generally better off with a smaller gapps package due to the smaller /system in the s2, more so in the newer lollipop roms.
You can check the md5 in a variety of ways, google will tell you ways to if you want to search, and there are apps in the market that check for you. I personally use hashtab, which you download to your pc. It gives you a tab in "properties" that allows you to compare the md5 value against the download site
Thank you. I got my s2 running on 4.4.4, thanks to your help. Everything went fine; I will reload another newer 'small' gapps pkg soon.
As for the md5 check, I was wondering if there is a way to do that from the phone (after a download) or using philz recovery, after download of a .zip.
CqN said:
Thank you. I got my s2 running on 4.4.4, thanks to your help. Everything went fine; I will reload another newer 'small' gapps pkg soon.
As for the md5 check, I was wondering if there is a way to do that from the phone (after a download) or using philz recovery, after download of a .zip.
Click to expand...
Click to collapse
Just go to play store and search for "md5 checker". There are several there. Sorry I haven't used any, so can't recommend but they should be able to give you a reference point
I have run into a problem, and I am stuck. While playing with the setting of profiles, I lost wifi, and the cell connection permanently. It is possible there is bug in the new profile version. Anyway, I flashed again the same nightly (after wipe for loading a new rom), and then this time without the gapps re-flashing, booted the system up. Both the wifi and the cell connected this time. Of course there was no google apps. So, I reflashed the philz advanced (the cm flash always gets rid of the philz advanced), then added the same apps pkg as before. But then when I booted the system up, both the wifi and the cell were not connecting!!
Any suggestions? Thank you.
PS. A related question. Does philz provide a way to save all the installed up and their setting to the external sdcard, and then reboot it? I am particularly interested in the settings save and restore.
CqN said:
I have run into a problem, and I am stuck. While playing with the setting of profiles, I lost wifi, and the cell connection permanently. It is possible there is bug in the new profile version. Anyway, I flashed again the same nightly (after wipe for loading a new rom), and then this time without the gapps re-flashing, booted the system up. Both the wifi and the cell connected this time. Of course there was no google apps. So, I reflashed the philz advanced (the cm flash always gets rid of the philz advanced), then added the same apps pkg as before. But then when I booted the system up, both the wifi and the cell were not connecting!!
Any suggestions? Thank you.
PS. A related question. Does philz provide a way to save all the installed up and their setting to the external sdcard, and then reboot it? I am particularly interested in the settings save and restore.
Click to expand...
Click to collapse
I don't know about the connection problems, you could post the problem in the cm11 thread as it is more specific to that rom. I have heard problems in cm12 with using gapps not released by cm, so you could try cm gapps HERE
Other than using the backup feature of philz, there isn't really any option to save settings. You could check out titanium backup from the market. It has the most comprehensive features for backing up apps and settings, although I have had problems with re-installing stuff using it, but plenty of people swear by it....
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.