Related
Hello XDA,
I own a SGS II GT-I9100.
It has been running on CM7.1.0 , Android version 2.3.7 since I got my phone and I'd like to update it.
I have PARANOIDANDROID 2.54 in mind to update into.
I am wondering what steps do I have to take as I do not understand the instructions stated in the rom's thread.
The instructions state:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
Specifically at the part after doing a factory reset. How do I install rom/gapps after I do a factory reset?
Do I use "ROM Manager v4.5.0.1"? And also, will it still stay after doing a factory reset?
JustGotAnSGSII said:
Hello XDA,
I own a SGS II GT-I9100.
It has been running on CM7.1.0 , Android version 2.3.7 since I got my phone and I'd like to update it.
I have PARANOIDANDROID 2.54 in mind to update into.
I am wondering what steps do I have to take as I do not understand the instructions stated in the rom's thread.
The instructions state:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
Specifically at the part after doing a factory reset. How do I install rom/gapps after I do a factory reset?
Do I use "ROM Manager v4.5.0.1"? And also, will it still stay after doing a factory reset?
Click to expand...
Click to collapse
after doing a factory reset copy the rom and gapps zip files to your internal or external sdcard.
Paranoidandroid does not come with google apps (gapps) as part of the rom it is a seperate zip file.
reboot in to recovery.
scroll down to install a zip from sdcard. install rom. reboot.
reboot into recovery again install gapps.
reboot.
No rom manger will not stay but paranoid does not use it. It is only recommend for use with cm roms only.
avoid using ROM manager on this particular device, it is known for beign the cause of lots of problems and malfunctions
Thanks for the reply guys.
Let me confirm the steps I have to take:
1) Factory reset my phone.
2) Copy the rom+gapps into internal/external sd.
3) Reboot phone into recovery.
4) Scroll down to install zip from sd card -> install rom -> reboot.
5) reboot into recovery and install gapps
6) Reboot.
Is that correct?
Also, I read this thread, http://forum.xda-developers.com/showthread.php?t=1990102 about dong a factory reset on a custom rom.
Is there a chance that I would encounter the same problem as I'm running on CM7?
I apologise for having so many questions. It is my only phone and I'm afraid that I'd brick it.
Thanks again for the help, really appreciate it.
Got another question.
For kernels, is there anything I have to take note of?
Like will my current one affect anything like it not being compatitble with paranoidandroid?
Read the ParanoidAndroid thread (first page in particular; but as much of it as you need to in order to get an answer), normally compatible kernels in those threads.
Learning is fun.
MistahBungle said:
Read the ParanoidAndroid thread (first page in particular; but as much of it as you need to in order to get an answer), normally compatible kernels in those threads.
Learning is fun.
Click to expand...
Click to collapse
Thank you for your reply.
If my kernel is not compatible (kernel automatically changed when I flashed CM7.1.0), what do I have to do?
I have read the first page of the thread and also ran a search on my kernel (2.6.35.7-g1e46077 [email protected] #1) in that thread.
Sadly, there were no answers as to whether my kernel was compatible.
Hmm, just wondering, if cm7.1 came with a compatible kernel, would flashing into ParanoidAndroid actually come with a compatible kernel as well?
Find the ParanoidAndroid discussion thread (not the development thread; You'll quite rightly get baked if you post a question like this there), and post asking if the kernel you want to use is compatible with the rom.
Or you could always read the thread. XDA search is complete/utter poorly coded rubbish (and I'm being very kind in saying this), I'm not surprised you didn't get meaningful results from a search.
Edit - Yes, I think you'll find the rom will come with its own kernel which is (obviously) compatible. But lots of people change kernels for all kinds of reasons. Up to you.
I tried finding their SGS II discussion thread but was unable to find it. (Only managed to find one for LG Optimus One)
From what I understand so far after reading around, is it true that my current Android version (2.3.7), Kernel and Mod version will not affect the process of flashing into a new rom?
Like will everything change after flashing into a new rom? In this case would be the Android, Kernel and Mod versions will change according to what the ParanoidAndroid rom is of?
If my understanding is correct, can I proceed with these steps:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
S3 in bootloop after install Paranoid 5.1
Hi all!
I'm in troubles with my S3.
I downloaded paranoid 5.1 for S3 webparanoird /legacy/i9300 (pa_i9300-5.1-20150822.zip), then I saw that I had to download GAPPS , so I downloaded: androidrootz . com/2015/03/download-android-51x-lollipop-pa-gapps.html (STOCK version), and finllay I read that was recommended to use boeffla-kernel, so I went to his web and downloaded last version (boeffla-kernel-4.0-alpha13-CM12.1-NG-i9300.recovery.zip).
After get it all, I put it in the SDCard, I when in recovery, I did Wipes: dalvik, cache and data. Then I install in this order (I read this order somewhere) ROM, then, GAPPS, then wiped cache again, finally I install Boeffla kernel. Then wiped again dalvik and cache and rebooted the phone, but before reboot TRWP said If I wanted to root the phone, so I accept. Finally, phone restart, but is in bootloop from more than 30 mins.
How can -I make run the device,??
Thanks in advance
Shudy
xShudyx said:
Hi all!
I'm in troubles with my S3.
I downloaded paranoid 5.1 for S3 webparanoird /legacy/i9300 (pa_i9300-5.1-20150822.zip), then I saw that I had to download GAPPS , so I downloaded: androidrootz . com/2015/03/download-android-51x-lollipop-pa-gapps.html (STOCK version), and finllay I read that was recommended to use boeffla-kernel, so I went to his web and downloaded last version (boeffla-kernel-4.0-alpha13-CM12.1-NG-i9300.recovery.zip).
After get it all, I put it in the SDCard, I when in recovery, I did Wipes: dalvik, cache and data. Then I install in this order (I read this order somewhere) ROM, then, GAPPS, then wiped cache again, finally I install Boeffla kernel. Then wiped again dalvik and cache and rebooted the phone, but before reboot TRWP said If I wanted to root the phone, so I accept. Finally, phone restart, but is in bootloop from more than 30 mins.
How can -I make run the device,??
Click to expand...
Click to collapse
boeffla alpha 13 is based on latest unofficial cm12.1 release 7 by Justarchi, which was released some days ago. Your desired ROM is older (08.22) so maybe it does not support the newer kernel. try to cleanly flash the rom and gapps again without flashing any additional kernel (wipe system, data, cache, flash rom then gapps, no additional steps needed). If it boots with stock kernel. you can try different older releases of boeffla kernel if one of them boots. if you want to go back to stock kernel, you simply have to reflash the rom without wipe (data will be kept)
btw, your desired gapps seems to be a bit old. try some newer one and use a small package (mostly they are called pico/nano or mini package) with only the core gapps needed for playstore and download all additional gapps you need from playstore. IMO it is the better way. there are many actual and good gapps available, for example open gapps, slim gapps, delta gapps, banks gapps, etc.... (I personally use open gapps pico package)
Darkened_Sky said:
boeffla alpha 13 is based on latest unofficial cm12.1 release 7 by Justarchi, which was released some days ago. Your desired ROM is older (08.22) so maybe it does not support the newer kernel. try to cleanly flash the rom and gapps again without flashing any additional kernel (wipe system, data, cache, flash rom then gapps, no additional steps needed). If it boots with stock kernel. you can try different older releases of boeffla kernel if one of them boots. if you want to go back to stock kernel, you simply have to reflash the rom without wipe (data will be kept)
btw, your desired gapps seems to be a bit old. try some newer one and use a small package (mostly they are called pico/nano or mini package) with only the core gapps needed for playstore and download all additional gapps you need from playstore. IMO it is the better way. there are many actual and good gapps available, for example open gapps, slim gapps, delta gapps, banks gapps, etc.... (I personally use open gapps pico package)
Click to expand...
Click to collapse
Ok I'm gonna try as you do, with pico gapps from oppengaps.
Just one question more, where can I take origina kernel? just to have if any thing goes wrong.
And thanks for the answer! (I'll say something about hoes it goes)
xShudyx said:
Ok I'm gonna try as you do, with pico gapps from oppengaps.
Just one question more, where can I take origina kernel? just to have if any thing goes wrong.
And thanks for the answer! (I'll say something about hoes it goes)
Click to expand...
Click to collapse
Darkened_Sky said:
boeffla alpha 13 is based on latest unofficial cm12.1 release 7 by Justarchi, which was released some days ago. Your desired ROM is older (08.22) so maybe it does not support the newer kernel. try to cleanly flash the rom and gapps again without flashing any additional kernel (wipe system, data, cache, flash rom then gapps, no additional steps needed). If it boots with stock kernel. you can try different older releases of boeffla kernel if one of them boots. if you want to go back to stock kernel, you simply have to reflash the rom without wipe (data will be kept)
btw, your desired gapps seems to be a bit old. try some newer one and use a small package (mostly they are called pico/nano or mini package) with only the core gapps needed for playstore and download all additional gapps you need from playstore. IMO it is the better way. there are many actual and good gapps available, for example open gapps, slim gapps, delta gapps, banks gapps, etc.... (I personally use open gapps pico package)
Click to expand...
Click to collapse
OK, I have installed with out more problems.
What I have done:
I install first of all, the Stock rom, to run the phone. (so the pone was as stock)
then.
- Downloaded TRWP for I9300, and flashed with Odin.
- Copied Rom Paranoid, PicoGapss from OppenGapps and boefflakernel (this time, this version to be sure: boeffla-kernel-4.0-alpha1-CM12.1-NG-i9300.recovery)
- Restarted phne in recovery mode, and whiped Data, system, cache and Dalvik.
- Installed from SD, first the rom, then the gapps, and restarted the phone, but didnt worked, so I go again to recovery
- Install Boeffla Kernel, whiped chache and dalvik, and restarted again.
- TRWP asked for root the phone, so YES ! XD
The waint less than 5 mins, and phone started .
Thanks for all the help!
@xShudyx: Paranoid official is imo the only S3-ROM, which came and still come with non-booting kernel. So think about its usability. As mentioned here, alpha 3 or Anykernel alpha 4 works. But they are outdated too.
Alright, plenty of you folks might already be enjoying Cloudy/Stock ROM but there are guys out there, like me, who would sacrifice a very few LG core apps for the outstanding AOSP ROM i.e Resurrection Remix.
So here in this guide I'll show you all the steps that i followed to Flash Resurrection Remix over CloudyG2 3.3 (Obviously this guide will work for Stock Rooted ROM too with TWRP ofcourse!)
Have a look at the Pros and Cons BEFORE proceeding with the procedure!
Pros:
1. It's AOSP ROM dude!
2.Excellent Battery timing.
3.Super Smooth with ZERO LAG!
4.You get continuous updates.
5.Tremendous customization's via RR Rom.
Cons:
1. Camera not as cool as Stock.
2. NO fully supported Quick-Remote
3. No Quick Note or any other Stock app you liked.
Should I proceed or Stick with Cloudy/Stock?
Well, to be honest, its worth the hassle. The only thing i really miss was the Stock G3 camera that came with CoudyG2 but i guess CameraNext ain't so bad too. Moreover u get a hell lot of improvements with UI and other AOSP gimmicks.
NOTE:
I TAKE NO CREDIT IN THE DEVELOPING OF ANY APP/ROM SHARED!
Please Follow each step carefully, I'm not responsible if you mess up your device, no one is forcing you to do so, proceed at your own risk[ Nah, don't worry, i tried all this personally and nothing went wrong. Just be careful though!]
*****************************************Instructions************************************************
I'm assuming you already have a Rooted device with Custom Recovery installed.
What you need! [Links at the END]
1. RR Roms
2. KK Baseband
2. Gapps Package (for 5.1)
3. LP Bootstack
4. Quick-Remote
5. Partition Back&Resore
6. Donation to all the Devs who made this possible [If you can afford one ]
BACKUP:
Its always good to create a Backup of a very few System partitions and if something goes wrong, you'll thank me later for this!
1.Install Partition Backup&Restore
2.Backup The following Partitions [Your own Bootstack].
aboot, boot, dbi, laf, rpm, tz, sbl1, persist
3.Backup Modem.
Modem, Modemst1, Modemst2.
4.You can backup your apps too via Titanium Backup.
5.Copy All your Saved Partitions to your PC.
Getting Ready:
1.Copy ROM, KK baseband, LP Bootstack, Quickremote and Gapps Package to your phone.
2.Boot into Recovery.
3.Backup System, EFS and boot.
4.Wipe cache, dalvik cache, data and System.
Now, follow these steps in the following order.
1.Flash LP Bootstack.
2.Flash KK Baseband.
3.Flash ROM.
4.Flash Gapps.
Now, clear dalvik cache and cache .
Reboot your device.
Finally, if all went fine you'll be seeing RR booting.
Setting up Quick-Remote:
1. Goto Setting -> Configurations -> Miscellaneous -> Set SeLinux to Permissive (Make sure you give root permission to Setting via SuperSU).
2. Download Int.D Enabler via Playstore and Enable Int.D via this app.
3. Download BusyBox and install it. (Do not forget to install Busybox files within the app).
4. Reboot to Recovery and Flash Quickremote.zip.
5. Clear Cache and dalvik cache.
6. Reboot
Other [Must] addons:
Beside the awesomeness already provided by RR, let's crank it up a little bit
Boost Sound(Yup, you gotta do it!):
1. Download mixerpath.zip and extract it.
2. Goto System -> etc -> rename mixerpath.xml to mixerpath.bak (creating a backup just in case).
3. Now copy the extracted mixerpath.xml to System -> etc.
4. Download Viper4Android.
5. Install apk and run it (choose the "ViPER4Android_FX_A4.x.apk" file).
6. It'll ask for which driver to install, Choose High Quality.
7. Reboot.
Improve Camera:
1. Download CameraNext.
2. Reboot to recovery and flash it.
3. Wipe cache and dalvik cache.
Other thoughts:
LTE should be working as it's available in the Setting.
Goto Setting and apply the PitchBlack theme (if you like).
There you go, now i guess you won't regret your decision of choosing AOSP ROM for your G2.
Hit Thanks as i won't ask you for a drink or hoe
LINKS:
ROM+Gapps
KK Baseband
LP BootStack (Click on 'View Full file' to Download)
Viper4Android
awesome guides, works great.
I really want to update to update to marshmallow but have no idea which bootstack to use. I've never needed to change bootstack when updating other phones.
Update TWRP before installing ROM
Thanks for the guide. I had an issue after installing this ROM on D802T, whereby I could not longer boot into TWRP recovery and received a "secure boot error" followed by a blank screen. Before installing RR, I had to update TWRP to blastagator's TWRP w/ Thermal Control & F2FS (twrp-3.0.2-1-d802-bump-blastagator-signed.zip).
MonsieurLorax said:
Thanks for the guide. I had an issue after installing this ROM on D802T, whereby I could not longer boot into TWRP recovery and received a "secure boot error" followed by a blank screen. Before installing RR, I had to update TWRP to blastagator's TWRP w/ Thermal Control & F2FS (twrp-3.0.2-1-d802-bump-blastagator-signed.zip).
Click to expand...
Click to collapse
You actually messed up the recovery partition. You had to flash the D802T recovery NOT D802. If your phone is booting then do so else restore to Stock and reproduce the steps. Good luck!
Sent from my LG-D855 using XDA-Developers mobile app
Kind attention!!
Currently I am on cloudy g2 3.3 and i have a full backup of cm13 rom,which I was using earlier.My question is, can i simly restore that backup through twrp or not?
akki809 said:
Kind attention!!
Currently I am on cloudy g2 3.3 and i have a full backup of cm13 rom,which I was using earlier.My question is, can i simly restore that backup through twrp or not?
Click to expand...
Click to collapse
Cm13 uses LP bootstack so i think there won't be any issue but I'm not sure about the modem though, do backup everything before you proceed.
Sent from my LG-D855 using XDA-Developers mobile app
hi i was wondering if i can triple boot my s3 with CM13 Nightly, AMCHA ROM, and 4.3 Stock Jellybean or 4.4 Kitkat (Back_to_n00t)
or duel booting CM13 and Amcha Rom
P.S i know it kinda sounds weird
I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
---------- Post added at 02:18 PM ---------- Previous post was at 02:04 PM ----------
spyroz540 said:
hi i was wondering if i can triple boot my s3 with CM13 Nightly, AMCHA ROM, and 4.3 Stock Jellybean or 4.4 Kitkat (Back_to_n00t)
or duel booting CM13 and Amcha Rom
P.S i know it kinda sounds weird
Click to expand...
Click to collapse
I did this so i could still use the mhl support on touchwz and use a custom lollipop daily driver. Good setup with good kernel tweaks
kush2.0 said:
I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
Click to expand...
Click to collapse
kush2.0 said:
I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
Click to expand...
Click to collapse
ok thanks how can i do this? can i use boeffla kernal?
spyroz540 said:
ok thanks how can i do this? can i use boeffla kernal?
Click to expand...
Click to collapse
Boeffla does not support duel boot and never will. The Arter97 kernel you need is this http://www.arter97.com/s3_kernel.htm v4.1 and final v5 both support cm12.1 lollipop 5.1.1 I used the v4.1 because there is loads more customizations compared to v5. I think arter97 just removed the most liable instabilities so he could move on to newer devices hence why it ends with lollipop 5.1.1 support. Anyway not a big step to marshmallow anyways. Read threw the change log and overview etc.
Right first thing I did was all downloads to ext SD card inc.
1. KK 4.4.4 back to noot ROM,
2. Arter97 v4.1 kernel,
3. Dual boot 2.2.zip
4. SuperSU 2.4.6.zip (very important)
5. 5.1.1 Gapps.zip
And 6. Your 5.1.1 lollipop ROM.
Note that first time I did this setup I used Ressurection remix v5.5.9 lollipop 5.1.1 cm12.1 ROM as my 1st ROM and KK 4.4.4 back to noot ROM as the 2nd ROM but unless I crancked my CPU up to 1800mhz on a performance governor my sgs3 would crash and reboot when I inserted the mhl-hdmi lead so I swapped the ROMs around and found that the 2nd ROM (lollipop) wouldn't install. Not sure why!!
That is the reason I flashed temesak cm12.1 v18.0 5.1.1 lollipop (by arter97) as the 2nd ROM and this was successful and in truth I'm happier with this setup. And now I don't have the mhl issue of crashing even when my CPU is settled at just 200mhz!!!
I use twrp 2.8.7.0 for this process.
Assuming you have backed up everything boot into twrp 2.8.7.X and go to wipe - format SD card. This will warn you it will wipe all data/media from partition type "yes" hit "go". Now for good measure hit home then wipe again - advanced wipe and check first 3 boxes data/factory reset, cache and dalvic cache. Now install / flash 4.4.4 back to noot ROM wipe cache/dalvic and reboot recovery. Next install / flash arter97 v4.1 or v5 kernel and finally flash superSU 2.4.6.zip and then advanced wipe and just wipe the dalvic cache only (1st check box). Reboot system and setup your first 4.4.4 KK back to noot ROM and make sure its stable and running fine.
Now reboot into recovery and go to install and flash arter97 dual boot 2.2.zip ( now anything flashed as during this visit to recovery will flash onto you 2nd ROM partition until you leave recovery. So every new visit to recovery will require you to flash dual boot 2.2.zip to install anything onto 2nd ROM ) it will say this in twrp install script. Next flash cm12.1 temesak 5.1.1 lollipop v18.0 ROM. Don't wipe anything now as it will probable wipe the 1st ROM. Next flash Gapps and finally flash superSU 2.4.6.zip ignoring all warnings that " unable to mount pre-load " as this ROM is not using pre-load. You do not need to flash arter97 kernel. Next reboot recovery. And advanced wipe dalvic cache only (1st ROM) next reboot system.
You will now boot into 1st ROM ( back to noot 4.4.4 ) so use newly installed aswitch app to boot into 2nd ROM and visa versa. If you chose the temesak v18.0 lollipop 5.1.1 ROM be patient on first boot as it really does take some time to first boot.
Also if you find that aswitch and atweaks apps are not installed in 2nd ROM check kernel version. If its not arter97 v4.1 or v5 kernel then reboot recovery and flash the kernel also (flashing dual boot 2.2.zip first) but I didn't need to.
Also if twrp at any time offers to root device then don't use that method. The superSU 2.4.6.zip is the best way to obtain root access which you must have to be able to use the aswitch and atweaks.
Hope this is helpfull
kush2.0 said:
Boeffla does not support duel boot and never will. The Arter97 kernel you need is this http://www.arter97.com/s3_kernel.htm v4.1 and final v5 both support cm12.1 lollipop 5.1.1 I used the v4.1 because there is loads more customizations compared to v5. I think arter97 just removed the most liable instabilities so he could move on to newer devices hence why it ends with lollipop 5.1.1 support. Anyway not a big step to marshmallow anyways. Read threw the change log and overview etc.
Right first thing I did was all downloads to ext SD card inc.
1. KK 4.4.4 back to noot ROM,
2. Arter97 v4.1 kernel,
3. Dual boot 2.2.zip
4. SuperSU 2.4.6.zip (very important)
5. 5.1.1 Gapps.zip
And 6. Your 5.1.1 lollipop ROM.
Note that first time I did this setup I used Ressurection remix v5.5.9 lollipop 5.1.1 cm12.1 ROM as my 1st ROM and KK 4.4.4 back to noot ROM as the 2nd ROM but unless I crancked my CPU up to 1800mhz on a performance governor my sgs3 would crash and reboot when I inserted the mhl-hdmi lead so I swapped the ROMs around and found that the 2nd ROM (lollipop) wouldn't install. Not sure why!!
That is the reason I flashed temesak cm12.1 v18.0 5.1.1 lollipop (by arter97) as the 2nd ROM and this was successful and in truth I'm happier with this setup. And now I don't have the mhl issue of crashing even when my CPU is settled at just 200mhz!!!
I use twrp 2.8.7.0 for this process.
Assuming you have backed up everything boot into twrp 2.8.7.X and go to wipe - format SD card. This will warn you it will wipe all data/media from partition type "yes" hit "go". Now for good measure hit home then wipe again - advanced wipe and check first 3 boxes data/factory reset, cache and dalvic cache. Now install / flash 4.4.4 back to noot ROM wipe cache/dalvic and reboot recovery. Next install / flash arter97 v4.1 or v5 kernel and finally flash superSU 2.4.6.zip and then advanced wipe and just wipe the dalvic cache only (1st check box). Reboot system and setup your first 4.4.4 KK back to noot ROM and make sure its stable and running fine.
Now reboot into recovery and go to install and flash arter97 dual boot 2.2.zip ( now anything flashed as during this visit to recovery will flash onto you 2nd ROM partition until you leave recovery. So every new visit to recovery will require you to flash dual boot 2.2.zip to install anything onto 2nd ROM ) it will say this in twrp install script. Next flash cm12.1 temesak 5.1.1 lollipop v18.0 ROM. Don't wipe anything now as it will probable wipe the 1st ROM. Next flash Gapps and finally flash superSU 2.4.6.zip ignoring all warnings that " unable to mount pre-load " as this ROM is not using pre-load. You do not need to flash arter97 kernel. Next reboot recovery. And advanced wipe dalvic cache only (1st ROM) next reboot system.
Click to expand...
Click to collapse
Thank you so much! here are my questions
can i change the first rom (back to n00t)?
if you tried AMCHA ROM can i have your opinion whats better back to n00t or AMCHA ROM? (if you havent tried it then you can skip this question)
does Offline Charging work?
kush2.0 said:
Boeffla does not support duel boot and never will. The Arter97 kernel you need is this http://www.arter97.com/s3_kernel.htm v4.1 and final v5 both support cm12.1 lollipop 5.1.1 I used the v4.1 because there is loads more customizations compared to v5. I think arter97 just removed the most liable instabilities so he could move on to newer devices hence why it ends with lollipop 5.1.1 support. Anyway not a big step to marshmallow anyways. Read threw the change log and overview etc.
Right first thing I did was all downloads to ext SD card inc.
1. KK 4.4.4 back to noot ROM,
2. Arter97 v4.1 kernel,
3. Dual boot 2.2.zip
4. SuperSU 2.4.6.zip (very important)
5. 5.1.1 Gapps.zip
And 6. Your 5.1.1 lollipop ROM.
Note that first time I did this setup I used Ressurection remix v5.5.9 lollipop 5.1.1 cm12.1 ROM as my 1st ROM and KK 4.4.4 back to noot ROM as the 2nd ROM but unless I crancked my CPU up to 1800mhz on a performance governor my sgs3 would crash and reboot when I inserted the mhl-hdmi lead so I swapped the ROMs around and found that the 2nd ROM (lollipop) wouldn't install. Not sure why!!
That is the reason I flashed temesak cm12.1 v18.0 5.1.1 lollipop (by arter97) as the 2nd ROM and this was successful and in truth I'm happier with this setup. And now I don't have the mhl issue of crashing even when my CPU is settled at just 200mhz!!!
I use twrp 2.8.7.0 for this process.
Assuming you have backed up everything boot into twrp 2.8.7.X and go to wipe - format SD card. This will warn you it will wipe all data/media from partition type "yes" hit "go". Now for good measure hit home then wipe again - advanced wipe and check first 3 boxes data/factory reset, cache and dalvic cache. Now install / flash 4.4.4 back to noot ROM wipe cache/dalvic and reboot recovery. Next install / flash arter97 v4.1 or v5 kernel and finally flash superSU 2.4.6.zip and then advanced wipe and just wipe the dalvic cache only (1st check box). Reboot system and setup your first 4.4.4 KK back to noot ROM and make sure its stable and running fine.
Now reboot into recovery and go to install and flash arter97 dual boot 2.2.zip ( now anything flashed as during this visit to recovery will flash onto you 2nd ROM partition until you leave recovery. So every new visit to recovery will require you to flash dual boot 2.2.zip to install anything onto 2nd ROM ) it will say this in twrp install script. Next flash cm12.1 temesak 5.1.1 lollipop v18.0 ROM. Don't wipe anything now as it will probable wipe the 1st ROM. Next flash Gapps and finally flash superSU 2.4.6.zip ignoring all warnings that " unable to mount pre-load " as this ROM is not using pre-load. You do not need to flash arter97 kernel. Next reboot recovery. And advanced wipe dalvic cache only (1st ROM) next reboot system.
You will now boot into 1st ROM ( back to noot 4.4.4 ) so use newly installed aswitch app to boot into 2nd ROM and visa versa. If you chose the temesak v18.0 lollipop 5.1.1 ROM be patient on first boot as it really does take some time to first boot.
Also if you find that aswitch and atweaks apps are not installed in 2nd ROM check kernel version. If its not arter97 v4.1 or v5 kernel then reboot recovery and flash the kernel also (flashing dual boot 2.2.zip first) but I didn't need to.
Also if twrp at any time offers to root device then don't use that method. The superSU 2.4.6.zip is the best way to obtain root access which you must have to be able to use the aswitch and atweaks.
Hope this is helpfull
Click to expand...
Click to collapse
spyroz540 said:
Thank you so much! here are my questions
can i change the first rom (back to n00t)?
if you tried AMCHA ROM can i have your opinion whats better back to n00t or AMCHA ROM? (if you havent tried it then you can skip this question)
does Offline Charging work?
Click to expand...
Click to collapse
I tried it with Mr modys M.D.4 galaxy S6 port v1.0 which is a 4.4.4 kitkat ROM first but it didn't support the arter97 kernel.
Not tried amcha ROM. No!!
Offline charging works fine on both ROMs at my current setup however when I had the resurrection remix ROM (1st) and back to noot ROM (2nd) setup offline charging would only work if I powered off from resurrection remix ROM an not the back to noot (2nd) which became a problem as if for example my battery died whilst hml mirroring a movie or something I was unable to get power into my battery completely because of this bug.
But as it stands right now its all good.
I just installed Resurrection remix on my Galaxy S2 i9100 using the instructions from team android website. everything looked to have went ok but the phone wont get past the Resurrection remix logo, i am able to access recovery and have tried wiping all data and clearing cache but it still wont get past it, does anyone know what the problem is.
Rock7 said:
I just installed Resurrection remix on my Galaxy S2 i9100 using the instructions from team android website. everything looked to have went ok but the phone wont get past the Resurrection remix logo, i am able to access recovery and have tried wiping all data and clearing cache but it still wont get past it, does anyone know what the problem is.
Click to expand...
Click to collapse
Please list out the steps that you've done so we can see what you've done wrong. (Even if website gives instructions, you may have had to do something different depending if something happens)
You may have forgot to wipe system or may have flashed the wrong files. More importantly, the recovery you used could have been outdated. Please also tell us if you are coming from stock 4.1.2 or the original ROM you were on. More detail = better help.
I'll include the correct procedure here anyway for everyone to look at:
- Make sure you are on CWM 6.0.4.8 or newer or any new build of TWRP (Philz recovery will work fine as well) This can be done by installing any kitkat kernel or lollipop kernel.
- Download the latest Resurrection remix ROM from the official website
- If you require Gapps, you will need to repartition your phone. If you are talking about lollipop, then yes, this is a necessity. Otherwise you don't have to do this. Download Gapps. Make sure to download the correct version for your android version and chose pico version if you use opengapps.
- Do a factory reset
- Wipe cache partition
- In the mounts and storage menu, wipe system (important)
- Flash Resurrection Remix ROM
- Flash Gapps (optional)
- Reboot device
gsstudios