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.
The only S5 Kitkat ROMs I've found either haven't been updated in over a year, or many users are reporting severe bugs like no camera support, or severe battery drain issues.
I'm just trying to get an app called Winulator running so I can play Starcraft: Broodwar on android, but it isn't working and one user said that is because Lolipop broke it (I'm on 5.1.1 atm). The app is no longer supported so I don't think it will ever run properly on 5.x. If anyone knows of a way to emulate 4.x for just 1 app maybe that would be the best shortcut for me overall here.
Barring that, could someone please recommend a guide to installing a lightweight, power-user-oriented ROM that is 4.x or older and has excellent battery life? I was going to try the official 4.4.4 VanirAOSP release but there are too many reports of poor battery performance in the last 2 pages of that thread for my liking.
I think the first thing I need to do is unlock the bootloader, and I've yet to find a definite answer on the best method of doing this from FOL1 (12/15). It seems I will need Odin on my PC and I have it. I've also started backing up all the data from my phone by manually copying/pasting to my PC.
I guess once everything is finally backed up (it's taking FOREVER, explorer literally been calculating time to copy for 10 minutes now just on the phone/android folder), then I will try and flash the official 4.4.2 VanirAOSP ROM since that one doesn't have any reports of battery issues and possibly only the camera and a few things won't work.
BTW, is there a step specially to unlock the FOL1 bootloader that I am missing, or can I just flash that ROM with Odin straight up? I found a comment stating NOT to flash 5.1.1 with Odin or I'd be stuck on Lollipop until some new bootloader-unlock method comes out. The 5.1.1 I'm running wasn't flashed with odin it was sent OTA and I've never rooted or had custom rom/bootloader, so I should be good on that I guess?
I am actually about to dive into this, if no one has any suggestions for me: http://forum.xda-developers.com/showthread.php?t=2752995
So I'll just pick one at random then? Thanks for the help...
You haven't even listed your model S5 or the ROM it's running now
And of course KK hasn't been updated in over a year, Lollipop and Marshmallow are released, they're not going to keep updating KK when a newer version of Android is released
I've using a UK EE SM-J500FN, using the Stock Rom with the Marshmallow update. And I ran out of room with all the updates for the installed software, and I can't even move them to the SD card.. It doesn't help that the Storage is half full with the Rom versions of many apps that I don't use, and old versions of the apps I do use.
It's been years since I've updated the ROM of a phone, (Last Modded phone update was Motorola DEXT/CINQ to ) . But I've got a feeling this won't be too hard if I follow the instructions.
I am looking for suggestions for a replacement Rom for my day to day phone, but without the Bloat.
I'm currently working on bringing my 2FA apps to work with my Nexus 7.
MikeSharpeWriter said:
I've using a UK EE SM-J500FN, using the Stock Rom with the Marshmallow update. And I ran out of room with all the updates for the installed software, and I can't even move them to the SD card.. It doesn't help that the Storage is half full with the Rom versions of many apps that I don't use, and old versions of the apps I do use.
It's been years since I've updated the ROM of a phone, (Last Modded phone update was Motorola DEXT/CINQ to ) . But I've got a feeling this won't be too hard if I follow the instructions.
I am looking for suggestions for a replacement Rom for my day to day phone, but without the Bloat.
I'm currently working on bringing my 2FA apps to work with my Nexus 7.
Click to expand...
Click to collapse
Maybe you should try the LineageOS 14.1 by SoUnd001. Its on the J5 (2015) ROM section. Great, wery stable and no bloat. Everything what you expect from a clean AOSP rom.
Here is the thread link:
https://forum.xda-developers.com/ga...om-lineage-os-14-1-samsung-galaxy-j5-t3549552
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