Hi guys! my s3 neo started randomly bootlooping after 1 year, I had RR 5.5.9 on it. I noticed that if I press button_vol_up when bootlooping the phone starts to access recovery, but suddenly continue rebooting so I tried to wipe ALL in the s3 neo from TWRP and with Odin I reflashed a new version of TWRP. After that, I clean installed the RR 5.5.9 and for a few days started working good.
Yesterday night the problem seems reappeared and then I soldered a new power button thinking it was the problem ( even if it's a random problem, it seems) but without fixing this problem. So I decided to desolder the power_button and starting using without it, and the phone was working very good, after 6 hours booom! the bootlooping is still here.
Can anyone help me? Thanks in Advance
When your RR is based on CM12.1 then the bootloop occurs when you install some new updated apps. You have 3 choices.
1) avoid these apps
2) Inform the developer of the apps, that with the new update your cm12.1 version gets a bootloop. The bootloop occurs, when the updated Version of the app was build with the new android build tools. The Solution is to use aapt instead of aapt2
3) upgrade to cm13 or cm14.1 . Theres also a RR based on 14.1. I didn't try this version, but i think with this rom you will not have the bootloop
same problem.
I have tried to flash it with many firmware without any success.
any help
alaa92 said:
same problem.
I have tried to flash it with many firmware without any success.
any help
Click to expand...
Click to collapse
What exactly is your problem?
Meanwhile there are quite stable Custom Roms that would be there:
- CM 12.1 from December 2017 (no more bootloops!)
- LOS 14.1 from August or also December 2018
- crDroid from November 2018
Related
Hi guys i have been having random reboots on all 7.x.x roms i flashed afther i had miui8, on RR i only had random reboots when i was listening to music with headphones and on seraph unofficial cm14.1 i got a lot of random reboots (about 8) when i first flashed it then i didn't have any and now they are happening again. Hope you guys can help me! tnx in advance! (sorry for my bad english)
Current setup:
latets offcial twrp
cm 14.1 12/08 seraph
no custom kernel
this is what i posted in the thread fo the rom afther all of this happend i think i go in more detail in it:
Hi @ashu01 i have been using your rom for a while, i had a great time with it and i had the most screen on time i ever had on a rom. but i switched back to more stock roms (nougat). And since that i switched from your rom i have been having random reboots on every single rom i flashed. i hope you could help me because this si really anoying.
timeline: i had MIUI8, then i flashed RR 7.1 i didn't have random reboot only when i lisent to music with headphones. i could not handel this any longer so i switch since i thought that it was just RR even tho i didn't see a lot of complains about the same issue i had on that thread. so then i flashed unofficial cm 14.1 by seraph the first 30 minutes i had more then 8 random reboots constantly (i was not listening to music at all- then afther a while i decide to do an extra wipe of cache and dalvik cache. this fixed the constant random reboots. but then i found the other issue again, it still random reboots when i listen to music with headphones. it doesn't reboot imidiatly some times i am just listening for 10 minutes and it reboots and some times i cna bee listenign for more then 1 hour and then it happens.
music app: spotify
extra info: i never flashed a custom kernel on any of the 3 roms and i clean flashed every single rom.
i really hope you could help me out because i can't seem to find why this is happening. i suspect the kernel but that is diffrent for every rom so idk anymore.
hope you have any idea about this.
tnx in advance!
-The nuub
Same problem here.. Need help
The nuub said:
Hi guys i have been having random reboots on all 7.x.x roms i flashed afther i had miui8, on RR i only had random reboots when i was listening to music with headphones and on seraph unofficial cm14.1 i got a lot of random reboots (about 8) when i first flashed it then i didn't have any and now they are happening again. Hope you guys can help me! tnx in advance! (sorry for my bad english)
Current setup:
latets offcial twrp
cm 14.1 12/08 seraph
no custom kernel
Click to expand...
Click to collapse
Lots and lots of users have this problem. Can such people send their logcat to the forum so that there may be a chance to catch the culprit.
suchiqaz said:
Lots and lots of users have this problem. Can such people send their logcat to the forum so that there may be a chance to catch the culprit.
Click to expand...
Click to collapse
its hard to log it because it mostly happens when its in your pocket but thats the thing its only when i listen to music with headphones. and i never flashed the new modem or new h2o to get volte. i saw a lot of people with this issue but all of them where trying to get volte working. but i didn't. still tnx for reply!
heithclif said:
Same problem here.. Need help
Click to expand...
Click to collapse
also when you listen to music with headphones ? only then or also while performing other tasks?
I've had this issue on any rom until i checked and realised that my bootloader had been locked even though I never did that. Then I couldn't unlock it again as the bootloader was locked and i couldnt flash stock recovery. Just use qualcomm flash tool to restore to complete stock. The guide is somewhere in General section of the forum
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
The global trouble with all nougat firmware
Hi guys. I amn't alone, I met 10-15 users at 4pda with such problem.
We have the bug at all nougat roms by any devs with different trees...
The sleep of death.
Personally I notice it after/during mobile internet using, but I'm not sure. For long time at home(for a week, for example) with WiFi I have no troubles. But if I am anywhere without WiFi and use 3g(don't have LTE in my country), my phone "sleeps" for some times during just one day... It isn't powered off as it's needed 10-15 seconds of button pressing to turn it on at least.
As the ROM and developer has no meaning I guess that here are the errors in the kernel. @fir3walk says that here are many bugs in our nougat tree and perhaps the trouble is involved in last_dmesg... Or some system force stopes, dozes work improperly.
Not many users have this trouble but it exists an a fact. So it would be great to detect an error and try to fix it. Perhaps not in nougat, at least in new Oreo(I haven't tried it yet so no information about this bug there). We have many ROMs, they are updated for some times a week, new roms are rolling out... But the bug stays still.
If someone else has such problem, write here. Perhaps somebody has any ideas and together we will be able to find solution...
So, all the devs who can detect an error, write us... Any tests, information, logs, etc.
P.S. By the way it is impossible to write logs of powering off(deep sleeping) via logcat or another's. If I run the logging I have no "sleepOFdeath".
It is really global trouble so let's try to fix it together.
I'm sorry for your trouble.
Lets start by figuring out which device is in question
I have a 3s prime and never saw this issue.
So do you have a 3s or 3x or 3s prime?
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
i face it in rr rom but no in dnd rom
Guys did anyone here with the sod, flash global stable/developer in edl mode?
leyD said:
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
Click to expand...
Click to collapse
Hello. No, I didn't try miui based on nougat.
But other users say that they notice such trouble at miui(7 android) as well.
So it isn't the cause...
Also about my phone:
Redmi 3s, 2/16, 2016030, FPC, aa1 motherboard.
bekcicandrej said:
Guys did anyone here with the sod, flash global stable/developer in edl mode?
Click to expand...
Click to collapse
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Dmytox said:
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Click to expand...
Click to collapse
17.5 h of SOT on what ROM?
Recently i'm facing no sound in call from other side in every rom expect arrow os, tried with flashin nxp still no solution.
Always did clean flash and have latest firmware. Never tried sound mods.
Can't hear anything neither anyone from another side
tried flashing nxp didn't worked.
Now i'm stucked in arrowos and can't even update rom. Any solution?
Flash dolby plus,it should fixed
DinIslamJoy said:
Recently i'm facing no sound in call from other side in every rom expect arrow os, tried with flashin nxp still no solution.
Always did clean flash and have latest firmware. Never tried sound mods.
Can't hear anything neither anyone from another side
tried flashing nxp didn't worked.
Now i'm stucked in arrowos and can't even update rom. Any solution?
Click to expand...
Click to collapse
Just download and flash permissive zip in magisk manager
jesh1 said:
Just download and flash permissive zip in magisk manager
Click to expand...
Click to collapse
not working. disabled, switched did all things possible, now using another rom which have premissive selinux by defaulf
Have you solved the problem? I also have the same problem
I unlocked the bootloader 2 weeks back. I have tried havoc os 2.9 3.3 rr pie lineage 17.1 miui by rinku, op5 port etc. I took backup all most every rom. I think I also made a couple of calls(call was working on havoc 2.9 previously). Yesterday while I was on havoc 2.9, I received a call. I attended the call. I was not able to hear any thing from the other side. The other side was unable to hear anything. Same with speaker also. Then reinstall (fresh install, restoring backup fresh install with gapps also) havoc 2.9, 3.3, rr pie, lineage 17.1. but same result. But no problem with miui. And no problem with superior OS Q. I have searched xda and found certain foxes for gsi's and dolby patch for oreo. But my problem is not with gsi or oreo rom. Does anybody have the same problem. Any solutions?
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.