Related
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Simax8 said:
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Click to expand...
Click to collapse
I'm using the GPE ROM, its great!! Rogers i337m
Sent from my GT-I9505G using XDA Free mobile app
Simax8 said:
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Click to expand...
Click to collapse
I'm on sgh-i337m with cm12 for the jflte and it's working great you need to change the name of device in updater script and all is working
sorry for my bad english
mugensiz said:
I'm on sgh-i337m with cm12 for the jflte and it's working great you need to change the name of device in updater script and all is working
sorry for my bad english
Click to expand...
Click to collapse
So you are not having any issues at all? I am considering doing this. Do you have a link to a guide you used?
I use the AntaresOne Rom from this Link http://forum.xda-developers.com/showthread.php?t=2557353 with my sgs4 (sgh-1337m) from Fido and the only issues are wifi is kinda wonky(doesn't always save network info, doesn't always connect, sometimes drops connexion, but it DOES work fine when connected) and battery sometimes drains really fast. NB that this last issue has been labelled "cosmetic" by someone who knows a great deal more than me about Android. I have NEVER had my phone run out of battery and shutdown., just some days at 6pm it says 25%, other days it reads 76%. Kinda random. About to test the "Danvdh's GPE Edition ROM" 5.0.1 Lollipop, will post when I can confirm working or not.
EchoeROM is a good one.
No service after flashing...
I was on SlimKat 4.4.4 which was good, but wanted to upgrade to Lollipop after seeing it on my Nexus 5 (which is now broken). I have a Bell SGH-I337M
I first tried the CM12 Optimized build, wouldn't ever get past the boot screen...
Tried GPE, and it installed and ran fine, but my service was cutting in and out (so basically useless)
Tried SlimLP, it also installed fine but I was having the same service problem as with GPE.
How are you guys installing these ROMS? The only info I could find to fix the problem involved modem/radio.. I tried flashing a LP modem with the ROM but it didn't work. And all the radio-related information was from 2011 so I didn't bother with it. Any help would be much appreciated, I've been messing with this for 2 days now and get seem to fix it
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.
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
I would also ask in the SPRINT forum .
JJEgan said:
I would also ask in the SPRINT forum .
Click to expand...
Click to collapse
Good idea, thanks.
jdd1960 said:
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
Click to expand...
Click to collapse
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
ShaDisNX255 said:
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
Click to expand...
Click to collapse
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
jdd1960 said:
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
Click to expand...
Click to collapse
You're welcome. Happy flashing!
Hi everybody,
I am new to the forum and new also to modifying android phones. I have a G900F and I wanted to try a few custom ROMs. I first installed Lineage 14.1 and everything went pretty smooth. After I wanted to try the official S5 MIUI7 v6.5.27 which I downloaded from the MIUI website. I wiped everything I could and installed the zip file with TWRP. There was no progress bar but it seemed to perform tasks. When finished, I rebooted but the phone is stuck on the Samsung logo without any progress. I tried many times and I always had the same issue. Could you please help me out with this? What can I do to fix the install issue? My phone is now working (installed the Super Lite by Vincom) but I would like to give MIUI a try. Any suggestions?
Thanks in advance
Miui 7 is based on android lollipop so you gotta flash lollipop bootloader and modem in order to get it working.
I would like to suggest you MIUI 8 by blackbuga, you can find the thread on Galaxy s5 development (snapdragon).
Sent from my SM-A720F using Tapatalk
Thanks! That was a quick reply!
I imagined that there was some issue of this kind. I was driven to v7 for its being an official release and stable. I saw that blackbuga's is beta and thought it was unstable. Well actually I wasn't relying on my skills, as I said I have been playing around with rom's for a week or so.
I'll give that a try
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