When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
hozza94 said:
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
Click to expand...
Click to collapse
did you root your phone?
what rom are you actually using?
did you try to update Rom Manager to an earlier version?
I assume your phone is rooted already. Don't continue if it's not.
I thought there was an official one released for the phone. Are you using the newest version of ROM Manager?
If yes, and our phone model is still not listed, then you'll need to install Clockworkmod Recovery by following this thread:
http://forum.xda-developers.com/showthread.php?t=1151396
It involves downloading a program called ODIN. You need to flash (transfer) the Clockworkmod file to your phone through USB. It's all in the thread above.
I had the same problem - installing the latest Rom Manager (free version) from the store didn't have Galaxy5 listed as a ClockworkMod possibility.
I flashed the whole thing by hand with ODIN and installed CyanogenMod - and presto; the version supplied with it had Galaxy5 support and I had no problem doing the "read only partition" installation.
Rom Manager is pretty crappy anyway - I prefer manual installation over it...
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Rigardi said:
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Click to expand...
Click to collapse
Why did you say that??? If the phone is rooted you can download CWM by RomManager without fear.. the important is that when the popup with phones versions come up, you choose only - ONLY! - Galaxy 5 voice! If this voice is not present into the popup, don't choose nothing at all! Choosing another phone might brick yours!
I downloaded and installed and even only update CWM by RomManager a lot of times and everything was always fine! No problem at all!!
You cannot scare people for nothing: your problems are not bug or issues, but only YOUR problems! and YOUR errors!!!
So, boyz, don't worry installing CWM by RomManager.. but remember to choose only Galaxy 5 voice, no other phone, 'cause you could brick your phone selecting a CWM that is not compatible with our GT-I5500..
hello, I have noticed that when you install rom manager and flash CWM with it, It makes the sch-i905 (SGT LTE) go into bootloop. I believe this is because the one that rom manager flashed was for wifi only... can someone explain to me how to possibly flash a clockworkmod recovery to stop the boot loop? or am I wrong and there's something else I have to do? Thanks for all the help in advance.
ROM manager isn't all encompassing when it comes to supporting the flashing of various ROMs and recoveries on all Android devices so what you're finding is what others already know; it doesn't support the GT 10.1 models well.
About the only reason I'd use ROM manager on my tablet would be to run the fix permissions from within the OS itself. Instead though, I just do it in CWM and I do not have ROM manager installed.
Dump ROM manager on the tab and use the latest CWM that pershoot distributed instead:
http://forum.xda-developers.com/showthread.php?t=1090289
There's a link to his blog site in the original post in that thread. Download links for your tab version (SCH-i905) are there as are instructions for using Odin to flash it.
The app itself doesn't direct the files properly on where it needs to be pasted
I currently have 2.3.1 installed on my note. I want to update to 2.6.3 so I can install CM11.
I only have TWRP installed and my current ROM (some verzion of PA) has already been factory reset (aka I can not actually use my ROM/Phone).
In order to update to CM11 I need to use the latest TWRP.
Edit: When I try to install the .zip for 2.6 from 2.3 it gives me an "error" message
Have you tried installing through GooManager?
Sent from my SCH-I605 using Tapatalk
The5ickne55 said:
I currently have 2.3.1 installed on my note. I want to update to 2.6.3 so I can install CM11.
I only have TWRP installed and my current ROM (some verzion of PA) has already been factory reset (aka I can not actually use my ROM/Phone).
In order to update to CM11 I need to use the latest TWRP.
Edit: When I try to install the .zip for 2.6 from 2.3 it gives me an "error" message
Click to expand...
Click to collapse
make sure you are frlashing the correct recovery
here is a link to the correct file http://goo.im/devs/OpenRecovery/t0ltevzw/
i just updated to 2.6.3.1 from inside TWRP with 0 issues
When downloading the zip to flash check the md5 sums. I've had that be my only problem when upgrading. I think I checked sums of different downloads. they smust be the same
Anyone of these file explorers do a good job
Root Explorer
es file explorer
Solid Explorer
sorry they won't let me post links!
Hello :angel: I'm kind of new to modding android and ran into a few issues. Basically I want to get Paranoid Android on my Galaxy S4 sgh-i337 running 4.4.2.
I rooted my device using towelroot but have failed to install a custom recovery. Both CWM and TWRP said they installed successfully but ended up with the same problem; when I selected reboot in recovery mode it would reboot saying Samsung Custom and then go into odin mode saying "Could not do normal boot".
I'm not sure if I installed CWM/TWRP correctly, as all the guides I found online were outdated. I installed the recoveries from the corresponding apps (CWM - ROM manager, TWRP - TWRP manager)--but like I said, both apps said recoveries were successfully installed. I also tried getting CWM using Loki on my phone + terminal emulator, but the terminal said something about loki not being the correct version for my device.
In CWM I tried the option to flash a custom ROM from sd card, but it didn't seem to recognize any files on the card while the normal samsung storage did.
So now I'm really confused and frustrated and can't seem to find answers anywhere. I would be really grateful if someone could guide me in the right direction in an easy to understand way.
Thanks for any help!
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.