So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
I think so
LGG2 LS980 said:
So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
Click to expand...
Click to collapse
I think u also losses the root permission re-root ur phone install cwm and flash gapps
and
slogger001 said:
I think u also losses the root permission re-root ur phone install cwm and flash gapps
Click to expand...
Click to collapse
So I'm screwed?
NA
LGG2 LS980 said:
So I'm screwed?
Click to expand...
Click to collapse
not so just re-root ur phone from software which u used earlier and install cwm
Just because you can't get to recovery does not necessarily mean you lost root access. They are not one and the same. LGs are kind of finicky about recovery, If the built in reboot to recovery option from the Power menu is not working, you can try an app like QuickBoot or via adb commands from the computer, or via the hardware buttons like so: http://itechtriad.com/articles/2014/2/27/how-to-reboot-lg-g2-into-recovery-mode#.U14kH_ldWSo
If you actually have lost your recovery (which is unlikely because CM would not change that), and still have root access when booted up with CM - you should - then grab Flashify from the Play Store, put your favorite recovery img file on your storage of the phone, and use Flashify to install the recovery for you. Very easy.
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.
Hi guys,
I need to run Pokemon Go on two Samsung S3 i9300. Anyone who actually is running it on his/her S3 can suggest me the easiest way to do that on a custom rom? I saw about Magisk but while I am running it without any problems on RRemix on my Redmi Note 3 Pro, I cannot run it on my nephews' s3 phones
Anyone can help?
I did it using SuperSU and SUHide on RRemix on I9300.
https://www.reddit.com/r/pokemongod...mple_and_easy_magisk_on_cm13_tutorial/d88ip96
I used this tutorial just without Xposed cause I don't need it
KaSkA3eR said:
I did it using SuperSU and SUHide on RRemix on I9300.
https://www.reddit.com/r/pokemongod...mple_and_easy_magisk_on_cm13_tutorial/d88ip96
I used this tutorial just without Xposed cause I don't need it
Click to expand...
Click to collapse
Thanks, I'll give it a try! BTW, did you install SuperSU the 'normal' way or via recovery, when it asks you at first launch?
fparri said:
Thanks, I'll give it a try! BTW, did you install SuperSU the 'normal' way or via recovery, when it asks you at first launch?
Click to expand...
Click to collapse
First after installing rr with gapps i installed supersu from play store and did full unroot. Then i made a file in sdcard1 named .supersu with "systemless=true" if i remember good. After that i rebooted to recovery and moved file .supersu to /data/ using aroma file manager and flashed supersu. Now it doesnt work so im trying new method because safetynet has got fail payload when you try to run it on i9300.
SuperSU + suhide + removing /system/bin/su and /system/xbin/su will make pokemon go work on RR and any rom with built in SU. You can avoid the last additions if you're running AOSP.
Hey, I have that trouble. I was using CyanogenMod 14.1 and now I tried to update for LineageOS 7.1 and after boot the device it don't initialize. Stay on the loader screen and nothing happens. What could be the problem? One thing I've notice is that I can't click on Do Not Install when it says to me install the SuperSu. I use TeamWin . Sorry if I've make some mistake or make a question which was already done, I look for but don't found it.
roscfi said:
Hey, I have that trouble. I was using CyanogenMod 14.1 and now I tried to update for LineageOS 7.1 and after boot the device it don't initialize. Stay on the loader screen and nothing happens. What could be the problem? One thing I've notice is that I can't click on Do Not Install when it says to me install the SuperSu. I use TeamWin . Sorry if I've make some mistake or make a question which was already done, I look for but don't found it.
Click to expand...
Click to collapse
Wipe system,data,cache, and flash the ROM again
DO NOT INSTALL THE SUPERSU OFFERED BY TWRP. WHEN TWTP ASKS CONFIRMATION TO INSTALL SUPERSU HOLD POWER BUTTON AND IT WILL RESTART
oppodi said:
Wipe system,data,cache, and flash the ROM again
DO NOT INSTALL THE SUPERSU OFFERED BY TWRP. WHEN TWTP ASKS CONFIRMATION TO INSTALL SUPERSU HOLD POWER BUTTON AND IT WILL RESTART
Click to expand...
Click to collapse
Thaks for the answer, I haven't tried it yet because when I tried I've got a error from the TWRP and now I'm trying to fix the recovery mode which gives me other error.
But thanks anyway, when I fix it and try what you told I make a post here.
You go Mount setting and unclick system mount after flash any rom
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
The usual way can mean a lot, but most important, did you use Magisk 25.1?
Cheers
Tom
ne0ns4l4m4nder said:
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
Click to expand...
Click to collapse
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Lughnasadh said:
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Click to expand...
Click to collapse
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
AlkaDragos said:
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
Click to expand...
Click to collapse
In the past it has worked for some but not others. The key is to make sure you haven't made any modifications to any of the partitions. For example, if you are using a custom kernel it won't work unless you flash all the modified images back to stock beforehand.
Also make sure you patch your own boot image so there is a stock boot image backup Magisk can restore.