Guys i heard official CM 12 for Galax s4 i9505 released, i wanna install it, the problem is im a completely noob for install custom OS, never done it, im afraid i might brick the phone, can you guy guide me to do this please, current stock version 4.4.2 is very laggy :S
Thanks
Firstly, you have to be rooted.
I used this guide to root my s4. Installation instructions on second post.
Warning: Make sure you have the right model. Do not use CF-Auto-Root if you have an AT&T or VZW branded s4.
After rooting you will need a custom recovery.
There are several custom recoveries. The most popular being ClockworkMod Recovery (CWM) or Team Win Recovery Project (TWRP).
You can use ROM manager from the play store to install a custom recovery.
Or go here and use that guide.
After rooting and installing a custom recovery you can flash a custom rom. What you need to do when flashing a custom rom depends on the rom itself. See the rom installation instructions for that.
It's not hard if you follow the guides carefully. Or you can as a friend (who is more experienced at this) to help you
GDReaper said:
Firstly, you have to be rooted.
I used this guide to root my s4.
After rooting you will need a custom recovery.
There are several custom recoveries. The most popular being ClockworkMod Recovery (CWM) or Team Win Recovery Project (TWRP).
You can use ROM manager from the play store to install a custom recovery.
Or go here and use that guide.
After rooting and installing a custom recovery you can flash a custom rom. What you need to do when flashing a custom rom depends on the rom itself. See the rom installation instructions for that.
It's not hard if you follow the guides carefully. Or you can as a friend (who is more experienced at this) to help you
Click to expand...
Click to collapse
Thanks mate, i heard that the CM 12 for s4 is not even beta, i will wait for the stale version. :angel:
Demitha said:
Thanks mate, i heard that the CM 12 for s4 is not even beta, i will wait for the stale version. :angel:
Click to expand...
Click to collapse
You could flash the Google Play Edition ROM found here. I use it myself and it's very stable and haven't encountered any problems so far.
Edit: Only downside is that you can't move apps to sd card. It's not supported yet.
GDReaper said:
You could flash the Google Play Edition ROM found here. I use it myself and it's very stable and haven't encountered any problems so far.
Edit: Only downside is that you can't move apps to sd card. It's not supported yet.
Click to expand...
Click to collapse
that sucks :. im a heavy app user ,anyways did your phone lagg on stock android? mine is very laggy.. its on 4.4.2
Not able to move apps to sd card is only a problem when you have the 16GB version. But I heard there is some workaround for this.
In my opinion stock rom was pretty fluid. Didn't have any stuttering. Only lag I ever experience was when changing music tracks and the home button lag. But I have the international (unbranded) version of the S4. Which means no carrier bloatware to suck up the power and performance of the phone.
The gpe rom does seem faster and smoother compared to stock firmware.
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ
ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work
Hmm, no idea then. If you find any solution kindly don't forget to tag me.
AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )
i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4
Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )
Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.
i have a verizon galaxy note 4 i haven't used in ages that i need to start using again and i wanted to go to stock rooted and clean up some bloat. what is a good way to do this?
thanks!
some more details
The phone is currently running EmotionOS 7.1.1 and 2CPL1
i decided to stay with custom roms:
upped to twrp 3.2.1, wiped memory, odin to CQL1, twrp installed RR and open gapps.
anyone know a rom that has working miracast to windows 10 or any OS?
I have been test LOS 14.1 and it works okay but a little unstable. Seems like the best I can get on this phone will be as close to stock as possible. I had it working well enough but I wanted to root the device.
So I would like to know what combination of bootloader and firmware/Rom will give me
unlocked bootloader
Twrp
Stock MM
Root
Best cell performance
Thanks in advance
Hi all,
I have a Galaxy S4 GT-I9505 with 4.3 Jellybean rooted from stock.
I want to update the OS because of having the advantage accessing newer apps.
The auto update function comes up with a 4.4.2 KitKat. Should I choose this or something newer?
It is 2018 and not 2015 and the android development will positevely affect this device too.
Thanks in advance.
Flash the latest stock 5.01 rom using Odin.
racing4mat said:
Hi all,
I have a Galaxy S4 GT-I9505 with 4.3 Jellybean rooted from stock.
I want to update the OS because of having the advantage accessing newer apps.
The auto update function comes up with a 4.4.2 KitKat. Should I choose this or something newer?
It is 2018 and not 2015 and the android development will positevely affect this device too.
Thanks in advance.
Click to expand...
Click to collapse
Latest stock is not too bad but it may struggle if you have more apps opened and all. the best bet is to use cyanogen mod either 13 or 14 but it may not fit your likings because of the style
Thank you for the info.
I will check both options.
Will I have to root again after the update?
UPDATE!!!!
I was handed a S4 a year ago and flashed LineageOS 14.1 (Android 7.1) and it runs smooth as silk and slick as snot. These companies stop updating to pin you into buying new fones. Follow the guides, first get TWRP recovery up and running then you can get Lineage OS installed. Lots of guides out there. KK isnt even sufficient for a kids tablet these days. Better my suggestion, you'll have 7.1 Nougat and something that can hang on a few more YEARS.
racing4mat said:
Thank you for the info.
I will check both options.
Will I have to root again after the update?
Click to expand...
Click to collapse
I have a Samsung galaxy s4 and where it shows the signal it's showing a no service and when I check my updates it says this devised has been modified in an unauthorised way and I am on cell c
colleenmuller57 said:
I have a Samsung galaxy s4 and where it shows the signal it's showing a no service and when I check my updates it says this devised has been modified in an unauthorised way and I am on cell c
Click to expand...
Click to collapse
Is the phone rooted? Which ROM is it running?
bigbertha248 said:
I was handed a S4 a year ago and flashed LineageOS 14.1 (Android 7.1) and it runs smooth as silk and slick as snot. These companies stop updating to pin you into buying new fones. Follow the guides, first get TWRP recovery up and running then you can get Lineage OS installed. Lots of guides out there. KK isnt even sufficient for a kids tablet these days. Better my suggestion, you'll have 7.1 Nougat and something that can hang on a few more YEARS.
Click to expand...
Click to collapse
My S4 GT-I9505 is the International version, JSS15J.I9505XXUENAA.
Is there a guide to safely flash the LineageOS 14.1?
Do I need to install the TWRP recovery first?
My knowledge is average on flashing Android phones, but I learn fast
Don't wanna brick it though...
racing4mat said:
My S4 GT-I9505 is the International version, JSS15J.I9505XXUENAA.
Is there a guide to safely flash the LineageOS 14.1?
Do I need to install the TWRP recovery first?
My knowledge is average on flashing Android phones, but I learn fast
Don't wanna brick it though...
Click to expand...
Click to collapse
1) Backup all data to external source.
2) Download and copy LineageOS rom, Open_Gaaps_ARM_7.1 and su(arm)_14.1 to MicroSD (see the links below).
3) Flash TWRP to RECOVERY from PC via USB (see the link below).
4) Boot to RECOVERY and Advance Wipe everything on the phone from TWRP.
5) Flash everything from the MicroSD in step2 with the same order and reboot.
* The only issue with LineageOS for S4 (and probably all Samsung models) is that the camera is prone to crash because the camera software is reverse engineered. When it does, you have to reboot the phone. Good luck and have fun.
https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html
https://download.lineageos.org/jfltexx
https://opengapps.org/
https://download.lineageos.org/extras
Hello !
Has anyone actually managed to get any custom ROM to work on a Samsung Galaxy A40 SM-A405FN/DS ?
Mine is currently running the current latest stock ROM (SM-A405FN_2_20211030045838_jg43vcqbiw_fac) downloaded with Frija and I managed to install TWRP from here : https://forum.xda-developers.com/t/recovery-a40-teamwinrecoveryproject-3-6-x-unofficial.4364575/
However, ANY custom ROM that I try to install :
https://forum.xda-developers.com/t/a11-r-arm64-a40-lineageos-18-1-unofficial-by-kevios12.4335409/
https://sourceforge.net/projects/eurekaroms/files/Samsung/A40/R/lineage/
GSI
maybe others that I forgot
will either bootloop or end up with a black screen.
Looking at the following threads, I'm starting to wonder if the SM-A405FN/DS is custom-ROM-compatible at all ?
https://forum.xda-developers.com/t/help-my-a405fn-wont-boot-any-custom-rom.4337041/
https://forum.xda-developers.com/t/samsung-a40-black-screen.4354421/
https://forum.xda-developers.com/t/galaxy-a40-infinite-loop-impossible-to-turn-on.4337343/
Im running CrDroid 7.13 without any issues with root and gapps. Many custom roms bootloop because of your newer firmware with Bit/SW REV.
Security Patch Lvl. being 4 and those custom rom were built on the older firmware with probably patch level 3. I had installed DotOS fan edition fully working like a year ago, then I tried some new custom roms, which somehow broke my system so the system couldnt start up even after reflashing original boot image, so I reflashed to the newest firmware which was working, then I tried flashing older one and it wouldnt boot, it just shows black screen with error bit/sw 3 boot 4. So you have to flah roms, whose are built on the newer bit level to boot up, the best is CrDroid and now the newest ALT-F4 version 0.0.3 from this forum: https://forum.xda-developers.com/t/rom-oneui-3-1-a40-alt-f4-v0-0-1-updated-2021-12-18.4373813/
I tried it myself and it is the best for this phone, it is fully debloated and pre-rooted stock rom. I also tried CrDroid 8x, everything works for me, but it fells slow and the ram is almost maxed out. I also recommend upgrading to this TWRP: https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
The unofficial twrps had some bugs for me. I hope this helps and happy flashing!
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
breversa said:
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
Click to expand...
Click to collapse
Good luck!
Well, luck has not been enough: after updating TWRP to the official version, I tried yesterday to install ALT-F4 0.0.3 but got the exact same result: black screen, need to reflash the stock ROM to make it boot (even to recovery !!) again.
Would you have any other idea ?
EDIT:
I actually tried crDroid in the past, to no avail either.