Related
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.
Hi everybody!
Normally I was using OxySlim ROM and had no poblems with it at all.
Yesterday I tried to flash CM13 with Nano-Gapps. Everything worked
and I configured 4 fingers for fingerprint unlock. After some more
configuration and app installations I tried to unlock with my fingerprint
and my phone freezed completely. I rebootet with long press of On/Off button
and retried, but it freezed again.
Then I restored my OxySlim Nandroid backup and even there my phone freezes now
with every fingerprint unlock attempt. I tried the "[Guide] OnePlus 2 Home Button Dead Solutions", but no change. (Sadly I have no *#808#-menu with OxySlim)
My homebutton and all other buttons are working well, but phone freezes with every fp-unlock attempt.
Find some logs attached. Fingerprint messages are tagged with "FingerPrintLogUtil".
Thank you for your help!
hello.. i faced the same issues wen i switched to cm 13 from OOS.. fp sensor would not work even wen i tried on different roms like crdroid and bliss pop.. also after d first reboot on every rom, d dialer app would force close..
den i read somewhere about d new modem.. i looked for it and flashed it, after factory reset and clearing cache.. den i installed d cm 13 again wid mini gapps.. not facing a single issue after dat and d fon works flawlessly now..
so u might consider flashing dat new modem, if u havnt already..
here's d link:
https://androidfilehost.com/?fid=24407100847293158
Thanks for your answer @meetg22 !
Which CM13 are you using? CM13 from @Seraph08 ?
Because I read here that Seraphs cm13 requires old Modem? I would give it a try but
since getting back the old modem seems not so easy I would stick to the old one until I'm sure to do the right thing.
yes @obermeier i am using Seraph's cm 13..
also i visited the link that you mentioned... i can see that there it is written to flash d new modem for seraph's rom if coming from oos.. please confirm again
obermeier said:
Thanks for your answer @meetg22 !
Which CM13 are you using? CM13 from @Seraph08 ?
Because I read here that Seraphs cm13 requires old Modem? I would give it a try but
since getting back the old modem seems not so easy I would stick to the old one until I'm sure to do the right thing.
Click to expand...
Click to collapse
meetg22 said:
yes @obermeier i am using Seraph's cm 13..
also i visited the link that you mentioned... i can see that there it is written to flash d new modem for seraph's rom if coming from oos.. please confirm again
Click to expand...
Click to collapse
Seraph's build will work on both modems. I confirmed again.
if you read carefully you'll know what I said.
1. Which modem/firmware should I flash before I install this ROM?
This is question raised by many people who have security settings crash or bootloop. So I wanted to write upon this in two ways.
If you are coming from Leaked H2OS Marshmallow ROM then,
First, you need to flash the revert2lollipop zip from here How to revert back to Lollipop by Yash98 if not your device will be in boot loop.
Below are the ROMs you can flash directlywhen you come from Leaked H2OS MM or Based ROMs after flashing revert2lollipop zip.
ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
If you are coming from OxygenOS/HydrogenOS Lollipop ROM then,
I installed O2OS every time for testing I changed ROM, it really is a hectic task.
Below are the ROMs you can flash directlywhen you come from OxygenOS
[ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
Click to expand...
Click to collapse
Install *new*modem from https://androidfilehost.com/?w=files&flid=49404 for below ROMs
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
I tried it with new modem, no improvement.
But you are right, Seraphs CM13 build works with both modems.
I can confirm that.
I was then trying krishnas solution mentioned here.
But, I can only give you one suggestion. Try installing OxygenOS, check your fingerprint from 808 menu and then flash CM13. This will make your fingerprint unlock normal again.
Click to expand...
Click to collapse
Thank you very much @krishna442, that worked! Even without clean install of CM13. I just flashed my nandroid backup again.
obermeier said:
I tried it with new modem, no improvement.
But you are right, Seraphs CM13 build works with both modems.
I can confirm that.
I was then trying krishnas solution mentioned here.
Thank you very much @krishna442, that worked! Even without clean install of CM13. I just flashed my nandroid backup again.
Click to expand...
Click to collapse
:highfive:
Hello!
Every custom rom I try to use in my redmi 2 pro 2014819 (prime in USA, pro in Brazil) shows random restarts, usually when the screen is off.
I have tried to use different bootloaders (miui KK and miui LP), different versions of TWRP (2.8.7.2 and 3.0.2.0), remove the sd card, different ways to flash, change the Linux from permissive to enforcing, disable the kernel panic , Different roms (the only one that did not restart in 4 days was CrDroid 4.4.4); And all led to random restarts.
I have already tested RR mm, RR N, Cyanogenmod, LineageOS, TeslaN, Tesla MM, AOSP Extended, Dirty Unicorns, AOSIP, Mokee 6, Mokee 7.1, among others, and unfortunately all presented the same problem.
I would be very grateful if anyone could help me; I believe that the problem is not in the process of flashing, but everything is possible.
Thanks in advance!
Did u try miui lolypop firmware provided on Lineage os thread?
Post ur problem with Model name,Logcat and Dmseg on ROM thread.
raymond_bqg said:
Did u try miui lolypop firmware provided on Lineage os thread?
Post ur problem with Model name,Logcat and Dmseg on ROM thread.
Click to expand...
Click to collapse
I tried to flash, but reboots continued to occur; The only change that occurred was that I could not get into twrp anymore, I will restore via fastboot and reinstall. Not put in the roms thread as it happens with all, and I believe it to be some problem on the device chip, twrp or something.
You should try the Jerrica Cosmos Kernel on RR or Mokee Rom.
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Redemptioner_ said:
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Click to expand...
Click to collapse
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Redemptioner_ said:
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Click to expand...
Click to collapse
Reverting to KitKat from Android 5.1+ (Lollipop, Marshmallow & Nougat) requires you to flash stock KitKat ROM.
Or you can try this firmware: https://forum.xda-developers.com/le...itkat-lolipop-firmware-base-switcher-t3249046
Though I haven't tested this myself, I believe it will work fine.
---------- Post added at 07:39 AM ---------- Previous post was at 07:04 AM ----------
Since you are on Nougat:
- Download KitKat firmware.
- Wipe dalvik, cache, data, system (don't wipe internal).
- Flash KitKat firmware & then flash the CM11 ROM over it.
If you choose to flash Stock KitKat ROM, do the normal flash:
- Wipe cache, data, system, dalvik & then flash Stock KitKat ROM.
Doing the latter (flashing KitKat ROM) will bring your device to the state of first, out-of-the-box, fresh boot.
What this means is that you'll have to start all over again (i.e flash recovery again).
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
RR 7.1 May 9 build. try this. smooth for my lenovo 1gb.
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
Sumer_7 said:
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
Click to expand...
Click to collapse
Sorry, no such problem for me.
Try to flash ROM again.
Best of luck.
:good:
vishal_kaushal said:
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
Click to expand...
Click to collapse
Can u plsss give the link for official lineage OS for a6000???
Hello everyone
I have S5 g900f 16GB on Stock marshmallow ROM and an unknown baseband
I managed to be run aosp 6.0 and 7.1 as well as 8.1 ROMs smoothly without any problems, but when it comes to 9.0 ROMs things start getting ugly. I get stock on the first boot screen showing Samsung Galaxy ST and then reboots to the same screen again
I tried dirty flashing and clean flashing too but with no luck I tried with and without gapps and root but again same result
ROMs I have tried are Los16 by haggertk and AOSP Extended
Please help.
Managed to have it working by flashing boeffla kernel 15.1 ???