Hello everyone,
I'm currently using a rooted Samsung Galaxy S3 int(i9300) using CWM with cm11 installer build.
It's giving me some issues lately, would it be fine if i were to dirty flash cm11 installer into the latest cm11 snapshot?
Or that is not possible at all?
Regards,
thatasiankid
Go to CWM recovery Mount/Storage - Format system/data/cache.
Go back Wipe data,cache, dalvik cache. Flash the rom
Related
hey guys
i was on Temasek CM11 v142 + PA pico-gapps-20140916a + Boeffla kernel omnirom NG beta6a
now i wanna update to latest build, i mean v151
but when i follow these steps [the method that i always use]:
- wipping cache and dalvic cach
- formatting /system /cache /preload
- installing rom + gapps + kernel
after reboot, it will stay on Samsung logo for a long time and then it will reboot to the recovery menu by itself
i tried full wipe, fresh install of the latest Temasek CM11 v151 + gapps + kernel , again, same problem
even i tried without gapps or kernel, only rom, and no success
i tried fresh install of the latest Slimrom 8.6.1 with latest Slim gapps, same problem also latest L-Droid 4.0.0, no success
tried latest Philz and TWRP recovery, same problem
extra info: but when i try installing Temasek CM11 v142 [for testing] there's no problem
i think it's about something new in new builds of the roms...
can anyone help plz?
SignalX said:
hey guys
i was on Temasek CM11 v142 + PA pico-gapps-20140916a + Boeffla kernel omnirom NG beta6a
now i wanna update to latest build, i mean v151
but when i follow these steps [the method that i always use]:
- wipping cache and dalvic cach
- formatting /system /cache /preload
- installing rom + gapps + kernel
after reboot, it will stay on Samsung logo for a long time and then it will reboot to the recovery menu by itself
i tried full wipe, fresh install of the latest Temasek CM11 v151 + gapps + kernel , again, same problem
even i tried without gapps or kernel, only rom, and no success
i tried fresh install of the latest Slimrom 8.6.1 with latest Slim gapps, same problem also latest L-Droid 4.0.0, no success
tried latest Philz and TWRP recovery, same problem
extra info: but when i try installing Temasek CM11 v142 [for testing] there's no problem
i think it's about something new in new builds of the roms...
can anyone help plz?
Click to expand...
Click to collapse
First of all,for Temasek you should use Cm kernel,not Omni kernel(Boeffla recommends). Second,if you use Philz let recovery do the wipe by choose instal new rom option afte you select factory reset option.
Flash rom then gapps then boot and after first boot ,change the kernel.
Sent from my GT-I9300 using XDA Free mobile app
andjeomilosrdja said:
First of all,for Temasek you should use Cm kernel,not Omni kernel(Boeffla recommends). Second,if you use Philz let recovery do the wipe by choose instal new rom option afte you select factory reset option.
Flash rom then gapps then boot and after first boot ,change the kernel.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
thanks for answer
i tried all of these different methods, but same problem again
i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom + gapps + kernel doesn't works, still bootloop
also i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom (only rom, without gapps or kernel) and again bootloop
tried two above methods with these roms: latest Temasek CM11 rom - latest L-Droid v4.0.0 - latest Slimrom 8.6.1 with Philz recovery and TWRP recovery
extra info: this Bootloop that i said, i mean after installing rom and rebooting system from recovery, phone will stay in "Samsung" logo for about 10 seconds and it will reboot to recovery menu automatically
another suggestion plz...
SignalX said:
thanks for answer
i tried all of these different methods, but same problem again
i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom + gapps + kernel doesn't works, still bootloop
also i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom (only rom, without gapps or kernel) and again bootloop
tried two above methods with these roms: latest Temasek CM11 rom - latest L-Droid v4.0.0 - latest Slimrom 8.6.1 with Philz recovery and TWRP recovery
extra info: this Bootloop that i said, i mean after installing rom and rebooting system from recovery, phone will stay in "Samsung" logo for about 10 seconds and it will reboot to recovery menu automatically
another suggestion plz...
Click to expand...
Click to collapse
Try reflash Philz recovery ,something is wrong with recovery. Maybe it's outdated. Flash 6.48.4 is the latest one.
Sent from my GT-I9300 using XDA Free mobile app
andjeomilosrdja said:
Try reflash Philz recovery ,something is wrong with recovery. Maybe it's outdated. Flash 6.48.4 is the latest one.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
i'm using latest version of Philz recovery, also tried latest TWRP recovery
reflashing recovery doesn't fix this problem
current rom that i'm using is Temasek CM11 v142, when i full wipe my phone and flash this 142 again, there's no problem and phone will boot
SignalX said:
i'm using latest version of Philz recovery, also tried latest TWRP recovery
reflashing recovery doesn't fix this problem
current rom that i'm using is Temasek CM11 v142, when i full wipe my phone and flash this 142 again, there's no problem and phone will boot
Click to expand...
Click to collapse
In that case it's something beyond my knowledge. I can only reccomend the hard way and that is flashing stock rom and then all over again,rooting ,flashing recovery etc. Wait,maybe someone can help you and save you the trouble or do it as i said if it's not to much hassle for you.
Sent from my GT-I9300 using XDA Free mobile app
Hi friends, I have currently the great Arter's Back to Noot v9 rom installed (with arter kernel 4.1) and I like to try LUKEROM 4.4.4, is it possible for me to install it securely?
Thanks in advance for your response...
1.Before flashing any rom at first flash stock rom. Because clean install is best.
2.Install any recovery cwm or philz
3.goto recovery Wipe data,Cache, Dalvik cache
4.install Luke Rom
5.Reboot system...
I still have a rooted galaxy s3 i9300 with philz recovery installed, and back to noot rom v9 installed...do I have to go back to 4.3 Samsung stock rom before flashing lukerom 4.4.4 or is it possible to do it from back to noot rom (with a clean install from philz recovery)?
lbls55 said:
I still have a rooted galaxy s3 i9300 with philz recovery installed, and back to noot rom v9 installed...do I have to go back to 4.3 Samsung stock rom before flashing lukerom 4.4.4 or is it possible to do it from back to noot rom (with a clean install from philz recovery)?
Click to expand...
Click to collapse
possible. Goto philz recovery.
Mounts & Storage- Format/system,cache,data,
Wipe cache,dalvik cache, clean to install a new rom
install luke rom
reboot system
Sureshtuty said:
possible. Goto philz recovery.
Mounts & Storage- Format/system,cache,data,
Wipe cache,dalvik cache, clean to install a new rom
install luke rom
reboot system
Click to expand...
Click to collapse
Thanks for your help, my friend...I'll try it ....
Hello guys,
I have problems running latest official PA for GT-I9300 (Int'l).
After wiping dalvik, cache, system and data I installed rom zip and gapps zip and rebooted. Phone automatically rebooted me to recovery (TWRP 2.8.5.0).
Again I wiped everything installed rom zip and now I tried installing boeffla kernel 3.1 CM12 NG and gapps zip. After rebooting I see installing apps and when it completed all my applications forceclosed and phone rebooted. Now I keep getting optimizing apps and when it completes phone just reboots.
I tried doing same thing but with leanKernel AOSP v5.1 but I get same thing as installing no kernel.
I appreciate any kind of help. If you need more information just ask.
Thank you.
Official Paranoid is the only LP-ROM for S3, which doesn't boot with build-in kernel. So don't expect anything from that and take Gokulbalram's Inofficial.
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.
Hey guys,
I have a samsung galaxy s3 i9300 running cm11.
My question is, can I install cm13 the same way I installed cm11?
I did it this way:
>Went into recovery mode (twrp)
>Wiped data, cache and dalvik cache
>Installed cm11.zip
>Rebooted the system
>Went into recovery mode again, and installed gapps ARM 4.4 Aroma
>Rebooted the system
I rooted it before ofc
Greets
Sure
Yes you can just make sure to backup everything on sdcard via recovery