Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
r243 said:
Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
Click to expand...
Click to collapse
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
GeekyDroid said:
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
Click to expand...
Click to collapse
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
r243 said:
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
Click to expand...
Click to collapse
Haha! Actually you won't brick your device by installing a ROM for your device. You can only brick it by flashing a ROM from other device without porting it, and I think this will be then only soft-bricked. A hard-brick can be done by flashing basebands from different devices. But I hope you won't do that
Actually by installing a ROM only your system(apps, vendor files, tweaks, etc.) and boot partition(kernel, etc.) will be overwritten. And that won't hard-brick your device
But I can understand your fear. I was same as you when I was a beginner
Related
Hi Guy,
I got a BIIIGGG problem.
After doing some VERY quick research i decided to get started by rooting and installing VillainROM, which worked lovely...no probs, however because there was a lack of themes (the main reason i rom'd the phone), I was swayed to go for Cynogen.
After downloading CM7.1 and installing through CWM my phone will not boot.
I have tried to do a factory reset through CWM, wipe the cache, and reinstall VillainROM but to no effect and stupidly i didnt backup my data.
Any advice on what i can do or have I bricked my phone?
What does the screen show? Can you get into download mode or recovery? Have you tried flashing the rom twice? This worked for me in the past.
Ricey
yep i can get into recovery and download mode, but when i boot the phone no joy
Ive tried installing the rom several times
Try formatting /data, /cache and /system from CWM recovery before flashing the new ROM.
If that doesn't help flash a stock ROM from Intratech's thread in the dev section via Odin.
1st- Boot into recovery.
2nd- wipe data/factory reset
3rd- wipe cache
4th- go to advanced/ wipe dalvik cache
5th- go to mounts and storage - format/system
6th- go to install ROM from SD card - select the ROM you'd like
7th- reboot system DO NOT TOUCH MAY TAKE A WHILE
8th- let it sit for 10 minutes once its booted so all the cache can build back up
9th- reboot, set up, and enjoy!!
Hope this helps!
Enzopreme you are a legend many thanks indeed
Hi Guys
Im having some problems trying to install a custom rom into my new Galaxy SIII I9300.
The rom in question is OmegaRom V35
After roooting and all, yesterday i tryed installing the rom with mobile odin, following all the instructions.
The result was the phone rebooted after the instalation seemed to be ok, but got stuck on the booting animation, and never got out of there.
I Had then to inject cwm with odin desktop, wiped data, cache anda dalvik, and then proceed to install the stock rom with desktop odin. All went well and the phone worked great.
I thought that maybe the problem was with mobile odin pro. So today, i went and proceeded to install Omega V35 via CWM. I again put the file on internal sd card, wiped data, cache and dalvik, and the rom started flashing. It all started good but, with no warning, at the mniddle of the installation, when applications were being installed, the phone went automatically and wuickly back to CWM!
Of course the installation wasnt finished, so i was stuck with cwm on reboot. Again made wipe data, cache and Dalvik, tried again to flash Omega V35, and again, the same problem...
In the end, i had to flash the stock rom again.
I searched the forum, but i cant seem to find the problem for this. I followed all the instructions, and had no error messages besides CWM skiping the format of the card, and some message (that i've seen in videos as normal), when wiping Dalvik!
Any clue to what's happening?
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
JJEgan said:
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
Click to expand...
Click to collapse
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
rebentador said:
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
Click to expand...
Click to collapse
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
THE.W!ZARD said:
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
Click to expand...
Click to collapse
I had already checked the md5, and the file is ok...
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Amritttt said:
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
None whatsoever. The flashing process seems to be running ok, It starts, i select default instalation, after i can see the apps being installed and suddenly, it all stops and goes into cwm without any message or warning...
Hi,
I've recently rooted my phone and installed my first ROM - Resurrection Remix - and it's notified my of an update (v3.1.3) and downloaded the zip for me. My question is how do I safely update RR?
When I first installed it I had to perform a number of steps wiping and clearing things before installing from a zip using CWM. Hopefully I don't have to do all of these as I don't want to have to completely reinstall every update, but do I have to do any of them still or do I just install from the zip in CWM without any other steps?
abc.mikey said:
Hi,
I've recently rooted my phone and installed my first ROM - Resurrection Remix - and it's notified my of an update (v3.1.3) and downloaded the zip for me. My question is how do I safely update RR?
When I first installed it I had to perform a number of steps wiping and clearing things before installing from a zip using CWM. Hopefully I don't have to do all of these as I don't want to have to completely reinstall every update, but do I have to do any of them still or do I just install from the zip in CWM without any other steps?
Click to expand...
Click to collapse
Have you read the first posts of the ROM thread?
Maybe there is a description of how to install the update.
If not, then you can just flash the update zip file in CWM recovery and try to reboot normally.
If everything works fine ... that's it.
If you have issues, boot into recovery, wipe cache and Dalvik cache and reboot normally again.
If that does not help, then you might have to wipe data (do a factory reset) in recovery.
But I think that these steps are not needed as you are already on this custom ROM.
(Usually you only have to do the complete wipe steps when coming from another / stock ROM - and the other way round.)
Good luck !
P.S.: Always create a nandroid backup before flashing. So you are able to "go back" if needed.
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.