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 am trying to build Cyanogenmod 14.1 on my computer and I get to the part of the instructions located here that ask for the proprietary files to continue the build. It specifically says you need to be on the same branch of cyanogenmod to get those files. The issue there is that 14.1 has not been officially released for the nexus 10. When getting the files off of both stock and cm13, the build fails missing /system/etc/soundfx/libfmas.so. Is there any way to resolve this?
I suggest waiting... I tried building CM today and its not even booting for me...
there will be nightlies when its usable. for now I recommend sticking to omni or AOSP
I have f320l, I am using cm 12.1 which is quite good and stable.
I thouI have f320l, I am using cm 12.1 which is quite good and stable.
I thought box flashing cm 14.1....I was annoyed
Then thought of cm 13.1 ......same result.
Why?
For Nougat I tried
1: Xosp
2: Aosp
3: CM 14.1
4: Lineage os
First I wipe everything then flash Hybrid bootsatck followed by a ROM karnel and gaaps.. In nougat everything runs fine I can open settings take screenshot and stuff but when I run any app it won't it just won't run any apps..this is the case in all the roms I tried and different karnels, the issue remains the same.
When I tried Marshmallow
Same procedure everything's go fine while booting it takes 2 hours. This happens with the different ROMs.
Right now I have lollipop my device is f320L. I am using TWRP bump recovery... Please tell me where's the issue.ght of flashing cm 14.1....I was annoyed
Then thought of cm 13.1 ......same result.
Why?
For Nougat I tried
1: Xosp
2: Aosp
3: CM 14.1
4: Lineage os
First I wipe everything then flash Hybrid bootsatck followed by a ROM, karnel and gaaps.. In nougat everything runs fine I can open settings take screenshot and stuff but when I run any app it won't it just won't run any apps crashes everything..this is the case with all the roms I tried and different karnels, the issue remains the same.
When I tried Marshmallow
Same procedure everything's go fine while booting it takes 2 hours. This happens with all the different ROMs.
Right now I have lollipop my device is f320L. I am using TWRP bump recovery... Please tell me where's the issue.
Hi guys!
I have SM-A500FU and I'm using stock ROM 6.0.1 rooted. First I want to remove some system apps but I'm not sure on what to remove and what to keep. Do you have any suggestions on what is safe to remove?
Also I've seen that there is not any stable and full working android 7 ROM (correct me if I'm wrong) Is there any good 7 ROM out there?
Sorry if my questions are stupid but I'm trying not to brick my phone.
Thanks!
Roms
vagdal said:
Hi guys!
I have SM-A500FU and I'm using stock ROM 6.0.1 rooted. First I want to remove some system apps but I'm not sure on what to remove and what to keep. Do you have any suggestions on what is safe to remove?
Also I've seen that there is not any stable and full working android 7 ROM (correct me if I'm wrong) Is there any good 7 ROM out there?
Sorry if my questions are stupid but I'm trying not to brick my phone.
Thanks!
Click to expand...
Click to collapse
You can try the Resurrection Remix Nougat 7.1.1 Rom for your Galaxy A5 Sm-A500FU.
Resurrection Remix ROM
It was made for the SM-A500H but it will work with the "FU" too.
I installed it on my SM-A500FU two weeks ago without any problems.
The only thing is that NFC doesn´t work. But I don´t need it.
I hope this is " stable and full working " enough for you because i did not found a better Rom with Android 7.
If you want a more stable ROM with Android 8 you should try this:
LineageOS 15 ROM
You can remove every Google App from you Phone like Hangouts or GMail.
You can try my Lineage 14.1 ROM, which is android 7.1.2 nougat.
It is designed for a500fu
Lineage 14.1
The ROM is very stable and suitable to be a daily driver. Some features like NFC I haven't tested but should work, I only built this yesterday
Also if there are bugs please tell me.
Hi,
I want to install LineageOS 15.1 on my Galaxy S4 (GT-I9505) to get Oreo on it, and I understand LineageOS is probably the closest to AOSP there is (correct me if I'm wrong). I'd like for all device functions to work (especially important ones like voice call, SMS, GPS, WiFi, BlueTooth, camera, etc), so it sort of has to be "daily driver" ready.
I also want it rooted with Magisk.
Is this possible? If so, what are the exact steps to do so? I've rooted other phones before but not a S4.
Thanks!
Anyone? It can't seem to find a LineageOS 15.1 for the jfltexx. Was able to find 14, 16 and 17.1 but they seem to be "unofficial" build. Are there stable builds, and if so, what's the latest stable version?
Thanks!