Hello dear xdaers,
I have an n9006 which I have been using with Omega rom for quite a while. And the phone itself is a genuine n9006, not a clone, I checked the first day.
I just recently decided to get my hands on a new rom and get the kitkat feeling so I have tried some custom roms and they worked fine. Then I decided to try an AOSP rom, W03 Slimkat v23 (http://forum.xda-developers.com/showthread.php?t=2638116)
This thing seems really well working for me except for one little! problem and it is the fact that there seems to be no baseband. And the status page shows unknown for practically everything except wifi.
In the light of this I panicked a bit and flashed latest stock rom from sammobile with odin. Everything works fine again (except the exclusion and the effort to make sure google services stay away. I remember struggling a lot to get google playstore and services installed. Then giving up and installing omegarom which kept me going for a while)
After this I backed up EFS and Radio from twrp recovery and flashed the W03 Slimkat v23 again, did the restore from the recovery and bam!
nothing.
Everything seems to be the same. I went back and forth between stock and slim and couldn't fix it.
The thing is I have nowhere the knowledge level of the users in this forum and I just have to learn all the things like odin and recoveries and download modes in one day and apply them. I probably am missing some fundemantal stuff. (heck I don't even know if EFS and Radio has anything to do with baseband) So please feel free to correct me on what I'm doing wrong and thanks in advance!
Update: I just tried to flash slimkat NON aosp version : http://forum.xda-developers.com/showthread.php?t=2669713
Same thing all over.
Backup EFS
Here bro, this may help you. http://forum.hovatek.com/showthread.php?tid=310#sthash.VtNUlpur.YxNJv18Z.dpbs
I am having constant reboots with Lollipop roms. While I am setting up or operating the phone everything seems to be working fine but once left alone it will constantly reboot. I have flashed numerous custom and stock roms on my I9505 ( without much or many problems ), until I started installing lollipop. I have flashed Netanalyzer, iB4STiD and 2 versions of Danvdh ( all cm12 roms ) and have tried different recoveries ( Philz 6.07.9 & 6.15.4 as well as TWRP2.7.01 & 2.7.10 ) always with full wipes. I would greatly appreciate help with this problem.
try to use TW 2.6.3.3. Once installed and booted up, allowing the rom the setup itself for a while before you setup. Importantly, follow the install notes of the OPs with true letter n spirit. most likely you are missing something. Your problem looks weird to me.
ph0n3n3rd said:
I am having constant reboots with Lollipop roms. While I am setting up or operating the phone everything seems to be working fine but once left alone it will constantly reboot. I have flashed numerous custom and stock roms on my I9505 ( without much or many problems ), until I started installing lollipop. I have flashed Netanalyzer, iB4STiD and 2 versions of Danvdh ( all cm12 roms ) and have tried different recoveries ( Philz 6.07.9 & 6.15.4 as well as TWRP2.7.01 & 2.7.10 ) always with full wipes. I would greatly appreciate help with this problem.
Click to expand...
Click to collapse
I tried a few different recoveries but lollipop would only boot up on my I9505 using philz_touch_6.58.7-jflte.zip not sure why or if it makes a differentce but is worth a try.
This is the ROM i flashed and works great
http://forum.xda-developers.com/showthread.php?t=2555569
alvinasnow said:
try to use TW 2.6.3.3. Once installed and booted up, allowing the rom the setup itself for a while before you setup. Importantly, follow the install notes of the OPs with true letter n spirit. most likely you are missing something. Your problem looks weird to me.
Click to expand...
Click to collapse
Thankyou for your help ( will hit the thanks button ), couldn't find TWRP 2.6.3.3 for I9505 so downloaded and installed TWRP 2.6.3.1. Didn't make any difference ( was still rebooting ), but as I don't have wifi ability, I tethered through Bluetooth and let it settle/load what it needed and it is working as it should ( no reboots ).
zerocoolhf said:
I tried a few different recoveries but lollipop would only boot up on my I9505 using philz_touch_6.58.7-jflte.zip not sure why or if it makes a differentce but is worth a try.
This is the ROM i flashed and works great
http://forum.xda-developers.com/showthread.php?t=2555569
Click to expand...
Click to collapse
Thanks for your reply, I finally have it working as it should ( must have needed to download/upload data to complete installation ).
Very happy with this ROM.
[ROM]【5.0】Google Play Edition 【JFLTE-GPE】 - 01-01-2015
http://forum.xda-developers.com/showthread.php?t=2557353
hey everyone
so ... i decided not to flash any samsung rom again as they are like @ [email protected]!# !!!! they are extremely laggy and CM is awesome even with some bugs but i don't know why my device seems to be the only one which has this problem
after installing tean canjica rom at the begging i got no service then the signal appeared for about couple of seconds then no service again
and that never stops and 99.9999% of time is no serivce
tried 3 different modems with 3 different methods ( TWRP , CWM & odin )
but still no luck
ps. when i flash samsung stock the problem disappears but on TeamCanjica or Remix rom the problem appears
thanks for your time
DaRkEMpRoR said:
hey everyone
so ... i decided not to flash any samsung rom again as they are like @ [email protected]!# !!!! they are extremely laggy and CM is awesome even with some bugs but i don't know why my device seems to be the only one which has this problem
after installing tean canjica rom at the begging i got no service then the signal appeared for about couple of seconds then no service again
and that never stops and 99.9999% of time is no serivce
tried 3 different modems with 3 different methods ( TWRP , CWM & odin )
but still no luck
ps. when i flash samsung stock the problem disappears but on TeamCanjica or Remix rom the problem appears
thanks for your time
Click to expand...
Click to collapse
Hi,
Wait for new build comes up. I see on TeamCanjica's thread, the developer will update the ROM. I tested GearCM and no network problem (before I revert to Prism Barebone). The problems you mention above might apply on all CM based ROMs that using TeamCanjica's device tree until their sources updated.
Possibly workaround is to update your modem.
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.
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.