------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
I have an S4 with CM10.2 which was done through the CM installer.
Unlike traditional rooting, cyanogen installer roots and installs the cm Rom in a few clicks automatically.
This new method leads me to believe that I must unroot to stock and root manually in order to use a different ROM.?
Or can I go ahead and download a rom, put it in the sd card, boot into the thing, and flash the ROM?
I'm trying to flash foxhound ROM.
Need an answer guys, it's not on Google.
Bumping this.
I don't have an s4 nor have I ever used a oneclickrootmeapp but to my understanding on how the cyanogen installer works is that it flashes clockwork recovery and cyanogenmod + kernel to your device
So I would say 99% sure that no you don't need to do anything special here, steps I would take
Download ROM of choice + gapps or any extras needed
Check md4sums for match
Put on SD
Boot to recovery
Do a nandroid backup
Wipe everything but SD
Flash ROM and whatever else needed
Reboot
And all should be just fine
Sent from my Nexus 4 using XDA Premium 4 mobile app
I salute you.
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Al-Dazzlez said:
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Click to expand...
Click to collapse
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
warrior1208 said:
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
Click to expand...
Click to collapse
Well that clears up a lot othings so thanks for the reply
Update: It works fine if you update twrp before flashing your ROM.
artrex654 said:
I have rooted my phone using stumproot and have also installed Illusion custom rom... However I cant install Gapps. Every time I try it fails in status 7. I dont know what that means or what to do although I've tried 3 different Gapps packages. If anyone can help before I decide to flash back to stock that would be great.
Click to expand...
Click to collapse
do you have the newest twrp installed? shouldnt matter, i used to run illusion off 2.8.0, but its the only thing i can think of.
TWRP crashes when I install 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.