Develop Bugs

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

Anyone have this issue?

So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.

Hmmmm
steve45058 said:
So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.
Click to expand...
Click to collapse
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T

Jack Ketch said:
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T
Click to expand...
Click to collapse
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.

steve45058 said:
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.
Click to expand...
Click to collapse
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:

Jack Ketch said:
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:
Click to expand...
Click to collapse
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird

steve45058 said:
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird
Click to expand...
Click to collapse
I have a backup of all my pictures on google + they give 15GO i have all my video and importants stuf backed up. When I have a problem with the phone hard reset and reinstall the rom. I use philz recovery is working like a charm to me

[Q&A] [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)

Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.

temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..

Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app

lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out

Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.

total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.

bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.

arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.

bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option

arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!

bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...

HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.

flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!

spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.

This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.

spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.

chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).

I've haven't tried it but since it's a 4.4.4 rom they should work fine.

Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).

Phone shuts down abnormally.

Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone

on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)

YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.

promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)

YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps

promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display

promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?

YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.

promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?

YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.

now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.

I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me

Galaxy S9 reboots every 1 min 48 seconds. Fine in Recovery mode

I tried factory reset, removed the memory card, no joy. It does it with battery in any charge state including fully charged. It stays on long enough to check a few things, but since it doesn't reboot while in recovery mode, it seems there is a problem in the software. Running Android 10. Any ideas?

Does it do it in safe mode?
If not it's a 3rd party app.
Stock launcher, right?
By watching running services you might see the cause list before it reboots.
Otherwise reflash it; possibly corrupted or bad firmware.
Use known good rom.

blackhawk said:
Does it do it in safe mode?
If not it's a 3rd party app.
Stock launcher, right?
By watching running services you might see the cause list before it reboots.
Otherwise reflash it; possibly corrupted or bad firmware.
Use known good rom.
Click to expand...
Click to collapse
Yes, it does it in safe mode as well.
Yes, everything is stock.
Sorry, I'm a noob, so I don't know how to watch the running services.
I will try a reflash. Any suggestions on where to find a good rom? Does it have to be a samsung rom?
Thanks!!

lapsmith said:
Yes, it does it in safe mode as well.
Yes, everything is stock.
Sorry, I'm a noob, so I don't know how to watch the running services.
I will try a reflash. Any suggestions on where to find a good rom? Does it have to be a samsung rom?
Thanks!!
Click to expand...
Click to collapse
Developer options>running services
Try clearing the system cache.
Doesn't have to be the stock rom but it would make troubleshooting easier probably.
A Samsung Experience Center at Best Buys can also run advanced diagnostics on it and reflash it.

blackhawk said:
Developer options>running services
Try clearing the system cache.
Doesn't have to be the stock rom but it would make troubleshooting easier probably.
A Samsung Experience Center at Best Buys can also run advanced diagnostics on it and reflash it.
Click to expand...
Click to collapse
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.

lapsmith said:
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.
Click to expand...
Click to collapse
Oh and clearing the cache didn't help.

lapsmith said:
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.
Click to expand...
Click to collapse
Disable updates. Try disabling the internet at start up... see if that helps.

blackhawk said:
Disable updates. Try disabling the internet at start up... see if that helps.
Click to expand...
Click to collapse
Ok will try that when I get home and let you know.

lapsmith said:
Ok will try that when I get home and let you know.
Click to expand...
Click to collapse
Tried disabling internet at startup so no updates and same issue. Then tried just leaving it at the let's get started screen and still reboots. I'm guessing reflashing is next. I found instructions on youtube, do you suggest using Odin3? Also do you know of a safe place to download the stock rom? If not I guess another rom will suffice.

lapsmith said:
Tried disabling internet at startup so no updates and same issue. Then tried just leaving it at the let's get started screen and still reboots. I'm guessing reflashing is next. I found instructions on youtube, do you suggest using Odin3? Also do you know of a safe place to download the stock rom? If not I guess another rom will suffice.
Click to expand...
Click to collapse
I never had to reflash any of my phones. I'm far from the ideal mentor for how to do a reflash, lol nothing bricked yet.
If you look around on XDA you can find links. Get the exact stock rom needed for that device.
You can use a custom rom but it may end up being a Pandora's box of trouble. I run stock for a number of reasons.
Using the same rom be preferably first to ensure it was a corrupted rom.
Normally they don't become corrupted. Using a different rom introduces more variables. It could be a mobo failure in which case a custom rom might give you a work around for it or not depending what failed. It be nice to know the hardware is good from a troubleshooting prospective... and save you needless hair pulling.
A Samsung Experience Center at Best Buy might be a better option as they can reflash it to the original stock rom.

Hey, just thought I'd let you know that I found the stock rom and was able to flash it using Odin. Unfortunately, it didn't help, but something did change. Now the phone reboots every 30 seconds rather than every 1 min 48. That doesn't eliminate a firmware problem, but it also still could be hardware. Bummer. Thanks for your help and maybe I will try a non factory rom since I've got nothing to lose.

lapsmith said:
Hey, just thought I'd let you know that I found the stock rom and was able to flash it using Odin. Unfortunately, it didn't help, but something did change. Now the phone reboots every 30 seconds rather than every 1 min 48. That doesn't eliminate a firmware problem, but it also still could be hardware. Bummer. Thanks for your help and maybe I will try a non factory rom since I've got nothing to lose.
Click to expand...
Click to collapse
Developer options>running services, ram usage
Watch what ram memory is doing. If it dies at the same amount in use regardless of the rom version loaded, you got a bad ram chipset.
It may be a corruption of the bootloader files allocating memory, I don't know as it's beyond my knowledge base.
This sounds a lot like a memory issue though.
Memory allocation among processes | App quality | Android Developers
developer.android.com

Good point about the rom usage with the new vs. original rom load. Unfortunately, I didn't write down the memory usage before flashing. Now it uses about 1.8G of ram on average. The screen locks up just before the reboot so I don't see any memory spikes. Settings is using about 150M and one UI about 200

lapsmith said:
Good point about the rom usage with the new vs. original rom load. Unfortunately, I didn't write down the memory usage before flashing. Now it uses about 1.8G of ram on average. The screen locks up just before the reboot so I don't see any memory spikes. Settings is using about 150M and one UI about 200
Click to expand...
Click to collapse
Try opening some memory intensive apps and see that kills it quicker.
If you got a bad mobo better to known sooner than latter.

Good idea. I tried a few times but since the phone is fresh, there aren't many apps. I'll have to play around with it some more tomorrow. Have a good evening!

lapsmith said:
Good idea. I tried a few times but since the phone is fresh, there aren't many apps. I'll have to play around with it some more tomorrow. Have a good evening!
Click to expand...
Click to collapse
I think you're right about the memory. It works fine in recovery mode, which probably uses minimal memory. And the build I flashed is UI 2.5 whereas I think the old one was 2.0. I would imagine 2.5 is more memory intensive.

lapsmith said:
I think you're right about the memory. It works fine in recovery mode, which probably uses minimal memory. And the build I flashed is UI 2.5 whereas I think the old one was 2.0. I would imagine 2.5 is more memory intensive.
Click to expand...
Click to collapse
My only question if so, is could the bootloader have become corrupted and is somehow causing this rather than the hardware?
Just a guess... if it has basis in fact I don't know.