Hello everyone.
This is my first time doing any flashing on an android device, so I want to do this as step-by-step as possible. My end goal is to install a cyanogenmod custom ROM. Before that, I have read around the internet (this forum included) that it's best done via CWM recovery. So I went to read up on the process. I found an all-in-one tutorial on the cyanogen wiki that has both the custom recovery install procedure, as well as the ROM installation itself, located here:
wiki.cyanogenmod.org/w/Install_CM_for_i9100
Which brings me to the reason I'm posting here.
I'm stuck.
On Step 2, "Unstable Apps Recovery Downloader" link is down. So I went to the first link in that sentence that got me here:
clockworkmod.com/rommanager
From where I downloaded the recovery for my specific device version, namely, CWM Recovery 4.0.1.5
Now, besides being not completely sure that's what the tutorial calls for, the step I'm stuck at is Step 7.
I extracted the recovery zip as instructed, but it just has a few folders in it, and I am at a loss what to write in the command line, since neither of those folders contain files called "kernel" or "zImage" or anything similar.
I would appreciate help with this very much as my phone is just sitting in download mode now.
I'm a noob in regards to this, and I apologize in advance if I'm asking a stupid question, or the solution is glaringly obvious
Assuming you want to install CyanogenMod 13, ditch every method you see out there and follow the steps on the guide which I've linked below.
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Kevin3014 said:
Assuming you want to install CyanogenMod 13, ditch every method you see out there and follow the steps on the guide which I've linked below.
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Click to expand...
Click to collapse
I've since managed to successfully install CyanogenMod 11. I originally wanted 12.1, but for the life of me, I could not get it to work. 11 works fine, but 12.1 just refuses to work. It either hangs at the robot icon or boots up fine, but then just starts spamming an "Unfortunately Settings has stopped working". I've tried everything I could find over cca 6 hours of searching, including trying both CWM 6.0.4.5 and 6.0.5.7, DARKSIDE superwipe/cache wipe, doing a factory restart in cm 11 then data wipe in cwm then flashing cm 12.1 and gapps pico 5.1. It just refuses to work. Really frustrating.
Do you know how to fix this issue, or do you have any guides like that one but for 12.1 for Galaxy S2 International?
Also, how stable is cm 13 compared to 12.1? From what I've read, it's still in very early stages of development with a lot of bugs and issues. If it works well, I'd be fine with giving the guide you linked a try.
Edit: Nevermind, the link you provided held the solution to my problem, and I've finally got cm 12.1 to boot up, and everything's working smooth as butter! Turns out all I had to format /system in CWM. Thank you so much, you've no idea how much you've helped me out
Though my question about CM 13 still stands... what's it like in terms of stability and bugs and issues nowadays and is it worth upgrading yet?
Warrick21 said:
Though my question about CM 13 still stands... what's it like in terms of stability and bugs and issues nowadays and is it worth upgrading yet?
Click to expand...
Click to collapse
CM 13 is smooth for daily use. It's stable as well, I've been using it for weeks with no problem whatsoever. I heard there's some problem with YouTube and Netflix app, but since I don't use these apps, I have no problem whatsoever. The battery isn't that great, but what can you expect from such an old device?
hello guys. .
I have 3 problems regarding my Samsung galaxy s5 SM G900H . .
1)I have recently rooted with cf auto root via ODIN. . BT by default I got super su version 2.68 which it beta app. . .even play store have version2.65 as latest version. . .super su keeps on asking for binary update. .when I try to update it normally,it always gets failed. .
2)I thought if I could install cwm/twrp recovery I could install super su version 2.65 and fix the binary issue. . I got the cwm recovery and flashes it via ODIN. . .cwm was installed. .BT it shows mount issues and seems to have reading SD card issues. . I can't backup to my SD card or so. . .
this is the text which I see when open cwm recovery. . .even when I installed Phil's recovery from rashr recovery tools. . ven Phil's recovery showed same issues. .
3)I have installed flashfire in my Samsung galaxy s5. . it shows the following warning. . .
I just want to backup my current stock ROM and move to s6 ROM for my Samsung galaxy s5 SM G900H. . .if you have any working alternatives feel free to suggest. . .
please help. .
Sent from my Venue7 3740 LTE using XDA Free mobile app
venkatsiddhartha said:
hello guys. .
I have 3 problems regarding my Samsung galaxy s5 SM G900H . .
1)I have recently rooted with cf auto root via ODIN. . BT by default I got super su version 2.68 which it beta app. . .even play store have version2.65 as latest version. . .super su keeps on asking for binary update. .when I try to update it normally,it always gets failed. .
2)I thought if I could install cwm/twrp recovery I could install super su version 2.65 and fix the binary issue. . I got the cwm recovery and flashes it via ODIN. . .cwm was installed. .BT it shows mount issues and seems to have reading SD card issues. . I can't backup to my SD card or so. . .
this is the text which I see when open cwm recovery. . .even when I installed Phil's recovery from rashr recovery tools. . ven Phil's recovery showed same issues. .
3)I have installed flashfire in my Samsung galaxy s5. . it shows the following warning. . .
I just want to backup my current stock ROM and move to s6 ROM for my Samsung galaxy s5 SM G900H. . .if you have any working alternatives feel free to suggest. . .
please help. .
Sent from my Venue7 3740 LTE using XDA Free mobile app
Click to expand...
Click to collapse
This is S2's section. You'll get help in S5's section.
Sent from my GT-I9100 using Tapatalk
Related
I know it's been adressed many times in different ways, but the info I found yet is not clear so I need a little help! I am trying to install the latest stable Cyanogen mod, using Gingerbread 2.3.7.
I have a Galaxy SII from Bell that I rooted and unlocked when I got it last november. It came on 2.3.3 and I flashed an official 2.3.4 on it, mainly to improve the battery life (and it worked). I did that using Odin and it went well.
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
I was having doubts if my phone was even rooted, but since it is still unlocked and software like Titanium backup runs fine, I guess that confirms it!! I am not sure what route to take from here...
Right now here are the phone details...
GT-i9100 on 2.3.4, FW I9100XXKG2, Kernet 2.6.35.7-I9100XXKG2-CL375027 [email protected] #2
I'll appreciate any help!!!!!!
JFChamp said:
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
|Question = Q&A
Looks like you are yet another that has not followed the instructions and flashed a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
OR are not following the instructions posted .
First time flashing CyanogenMod 7 to the Samsung Galaxy S II, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Clockwork mod recovery see
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
The instructions work as i have just installed by following the instructions in reply to an exact same post .
jje
Click to expand...
Click to collapse
Thanks jje... The instructions did work! Tough I tought I had bricked my phone at one point, on the final restart it would get stuck at the Samsung logon screen, but I forced it back in recovery, re-flashed from the zip and then it booted in CyanogenMod!!!
I really appreciate your reply
Greetings fellow Earthicans!
I've been roaming these forums for several years now and have been able to fulfill all my custom rom needs by searching, trial and error. I've bricked all my phones at least once but have always managed to make the phone work better than when i first stardet modding it. This time i managed to do something i've never been able to do before and i'm therefor writing my first post here.
Yesterday i did a full wipe/format of everything available in CWM because the internal phone memory was close to full. In the process i managed to erase all my backups, which i thought was fine since i loaded my external sd with most of the custom roms and gapps available on this amazing forum.
However, when i tried to flash either one of the .zip files i get the same message "this package is for "m3", m3xxm i9305, gt - i9305 device; this is a "m0"." Even though i've had both avatar and miui ROM installed a few hour earlier. I was stuck on the boot screen, as so many other times with this and other devices.
So i searched around this forum and google and found out that m0 is the i9300 and my initial thought was "nice, perhaps i can install the custom roms of the i9300 by copying them to my ext sd and install through CWM" Which of course did not work and i realized i had to go back to stock through the download screen
So i downloaded my firmware (4.1.2 and 4.3) from sammobile.com to do a stock reset through odin 3.07. Both firmwares works fine and all of the phones functions work as intended, as far as i know.
I'm currently running 4.3 I9305XXUEMKC_I9305TLAEML1_I9305XXUEMK1_HOME.tar.md5 without any problem, but would love to be able to run custom ROMs again, but have no clue how to proceed.
I would be eternally thankful if someone know the solution to this problem i've encountered through my irresponsible actions.
/an open-source and android enthusiast
This is not i9305 q&a .
in recovery format system sdcard data and cache then boot to download mode and flash the correct stock rom for your phone via Odin .
JJEgan said:
This is not i9305 q&a .
in recovery format system sdcard data and cache then boot to download mode and flash the correct stock rom for your phone via Odin .
Click to expand...
Click to collapse
Thank you for your reply.
I've checked which of the stock rom to use and have done as you described, i can run the stock rom and currently am.
iIve rooted the phone and installed CWM through odin. When booting into CWM, and clearing as described in all guides, i still get the same error message given in my post above.
are you sure you do have the right recovery and that this is up to date?
Hello to everyone
I am the proud owner of a galaxy S3 - i9300 since couple of days (got s2 before) and I would like to install a custom rom. Right now it is official JB. So first I tried to follow the guide from here the galaxys3root.com - galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-jelly-bean-or-ics
I finished installing, everything said ok but SuperSU said "“There is no SU binary installed, and SuperSU cannot install it. This is a problem!”. However I was able to enter recovery mode and see that cwm was installed. I repeated the procedure - same result. I tried using the CF-Auto-Root-m0-m0xx-gti9300.tar.md5, it said ok, finished, all green but again i had no root access (cwm still there, root checker said no root and supersu dissappeared).
The ultimate goal for me is to install CM11 rom with kitkat. So please clear some things for me (almost beginner level):
1. do i really need root from now on?
2. can i just reboot into recovery, wipe data/factory reset and install ROM? (all from the device, no odin)
3. is it a better solution to flash stock firmware through odin and start rooting all over again ?
4. Why don't I have root access since I followed all the indicated steps?
One detail that might matter is that now my cwm is version 5.5.0.4 CF v.1.5
Thank you for any help (and again, beginner+1 language please)
Visit CM and CF autoroot site you will find the answer to your questions.
All you need to install CM is recovery, so if you can get into that you are golden and don't need root on your current rom because its going to be over written with CM anyway
Thank you for your replies!
IOU-1, I did some research over the internet and I still do but I'm looking for some straight-on answers right now.
Darke5tShad0w, thanks for your help - right now I have cwm 5.5.0.4 - can you point me towards how to update to newer one? (I cannot do it through play store since I don't have root access).
Ok, I've found the cwm update: http://forum.xda-developers.com/showthread.php?t=2052091 I think this should work.
tt34t34 said:
Thank you for your replies!
IOU-1, I did some research over the internet and I still do but I'm looking for some straight-on answers right now.
Darke5tShad0w, thanks for your help - right now I have cwm 5.5.0.4 - can you point me towards how to update to newer one? (I cannot do it through play store since I don't have root access).
Ok, I've found the cwm update: http://forum.xda-developers.com/showthread.php?t=2052091 I think this should work.
Click to expand...
Click to collapse
Try this since your goal is to install CM-ROM http://wiki.cyanogenmod.org/w/CyanogenMod_Installer
Sorry I dont have alot of time today to be able to find you a link for the updated version.
Few things you can do here,
Use the link IOU-1 posted, I forgot about this yesterday then update CWM with rom manager
Try to flash cm with current CWM, if it works update it with rom manager
Search the forums and find the correct cwm post and update manually
Ok, thanks to everyone for their answers.
I fixed it and I'll say how so anyone in my position will do the same.
As a reminder, I tried to root but all I succeded to do is get cwm installed but no root (so no rom manager or any other root app installed).
What i did was to update cwm manually from within it, with zip install from this thread: http://forum.xda-developers.com/showthread.php?t=2052091
After that I simply installed CM11 - zip install - and now I have root and everything is running smoothly.
Again thanks - and good luck to all.
So first of all, hello
I'm pretty new to this whole universe of custom roms, rooting etc.
My main problem is that I tried to install a custom rom (2 to be exact,
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
and http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864)
So, the whole rooting process was on this side:
http://www.techverse.net/root-samsung-galaxy-s3-android-4-3-jellybean/
I did everything and it worked like a charm
now I wasn't really sure about the crossfire recovery so I wanted to get cwm (because I had that one on my s2)
I downloaded it here:
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
flashed it via odin 3.07 and everything worked fine
now I just wanted to install a custom rom:
Trying to install the cyanogenmod 12 resulted in a status 7 installation aborted error. I figured that this may have something to do with my
cwm version so I left it alone. The bootloop started on this try. I wiped Dalvik, Cache and Data
I thought that the bootloop resulted because I didn't have a single firmware installed so I tried to install a second rom. This time it was Archidroid. The Aroma launcher started, everything started, I chose my stuff etc. The installation began and I thought it would work. I was dead wrong. Some things failed on the installation but it still resulted in a finished message. This didn't help the bootloop tho. I made a factory reset, wiped dalvik, wiped cache and data, but nothing helped so far.
The only options I haven't tried are restoring my stock firmware and flashing another recovery (most like CF auto root).
Can somebody help me? I should mention that my phone is a samsung galaxy s III gt-I9300
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
TheRuan said:
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
Click to expand...
Click to collapse
I'm about 90% sure that my s3 is the international version (I'm not really sure how to check that)
as for the recovery update option in Archidroid. I'm actually really afraid that the update could somehow damage the recovery. Is it a safe process?
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.