I'm trying to flash Resurrection Remix 4.4.2 KitKat over Stock rom.
The installation fails in CWM and doesn't finish, I downloaded the zip file couple of time but I'm facing same issue.
Is there any other way I need to flash this, also is there any issue in flashing rr directly over Stock.
Thanks in advance.
manukaul said:
I'm trying to flash Resurrection Remix 4.4.2 KitKat over Stock rom.
The installation fails in CWM and doesn't finish, I downloaded the zip file couple of time but I'm facing same issue.
Is there any other way I need to flash this, also is there any issue in flashing rr directly over Stock.
Thanks in advance.
Click to expand...
Click to collapse
You need to do a full wipe ie format system-data-cache etc please read up on how to do this probably.I suggest using PhilZ recover as there is a option in settings to install a new rom that wipes all the necessary files for you. And of course backup everything including efs.
Related
------------- 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 was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
noppy22 said:
I'm assuming you have stock unrooted firmware? The easiest way is to install philz kernel from stock(3e) recovery, then reboot to recovery and flash a newer recovery that is capable of flashing the newer versions of android. If you just want to install CM12.1 straight away just back up your efs then:
1. Download the DVLSH kernel .zip from HERE
2. Download the philz 6.48.4 from HERE
3. Reboot into stock recovery, flash the DVLSH kernel(if your firmware build is DVL**, you could probably reboot into system no problem)
4. Reboot to recovery(not system), flash the philz 6.48.4
5. Reboot to recovery(not system), follow the steps for installing in the CM12.1 thread after backing up etc
Keep the DVLSH kernel. Once you install CM, you will have CM recovery, which only allows you to flash signed .zips(which this one is)
EDIT - The philz 6.48.4 is also signed and is probably the more useful one to keep, being compatible with the newer roms
Click to expand...
Click to collapse
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
KiranP23 said:
I was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
Click to expand...
Click to collapse
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
noppy22 said:
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
Click to expand...
Click to collapse
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
KiranP23 said:
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
Click to expand...
Click to collapse
All you need to do is
1. Flash either of the philz kernels
2. Turn phone off and reboot to recovery
3. Full wipe, flash slimsaber(and 4.4.x gapps if you want)
4. Reboot to system
You don't need the slim kernel
Sorry everyone. I can't post this on the original forum.
I need to know how I can remove this rom and go back to a older rom I installed and backed up via TRMP.
Unfortunately I am having problems with this rom as I have had it installed for over a month now and really can't be used as a daily.
Have changed the kernel to trmp but it only gives / directory with 0 bytes. Cannot mount any other system etc to restore a working rom.
Have tried installing a rooted rom via Flashtool but keep getting errors.
I am trying to avoid wiping the whole phone and start afresh. Any ideas or help would be greatly appreciated.
You can restore your back up via twrp.
fnldstntn said:
You can restore your back up via twrp.
Click to expand...
Click to collapse
I have tried but trwp when in recovery will not recognize any of the other partitions. It can only see / partition. I have also used trwp app. When I reboot into system from trwp it says no system available but will boot into RR rom.
Hi everyone,
I flashed a custom rom after sticking with the stock for a while, i did flash a rom before going to stock rom and it all worked fine.But now after i flash a custom rom with philz recovery after the rom is booted every app starts crashing even google framwork and all those core apps.I also tried without flashing gapps.last time i flashed the stock rom with flashfire i didnt wanted to flash custom rom with that because i showed partition protected after loading the zip file in it.Need help.
Thanks in advance.
I tried flashing linage os rom and it worked guess the rom was buggy.
@manushamil: fine. Further I suggest to step over to TWRP-recovery (though you can't restore Philz' backups).
rp158 said:
@manushamil: fine. Further I suggest to step over to TWRP-recovery (though you can't restore Philz' backups).
Click to expand...
Click to collapse
Thanks for your reply i already did everthing i flashed resurrection remix since linage os was draining my batteries
Working perfect
rp158 said:
@manushamil: fine. Further I suggest to step over to TWRP-recovery (though you can't restore Philz' backups).
Click to expand...
Click to collapse
Thanks for your reply i already did everthing i flashed resurrection remix since linage os was draining my batteries
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
xBinyWolf said:
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
Click to expand...
Click to collapse
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Retrial said:
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Click to expand...
Click to collapse
I already did and found no success, even repaired file system and did that thing of chaning in exfat2 then 4 again. Changing to Orange fox recovery solved my problem. Thank you for the reply.