Related
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
guys, anyone?
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Moix123 said:
guys, anyone?
Click to expand...
Click to collapse
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
BarryH_GEG said:
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Click to expand...
Click to collapse
i was facing this problem when i was on stock. My phone had Vodaphone UK RUU.
i contacted htc, got the following reply
With reference to your query, please kindly update your phone to the latest software version since we have released a recent update which optimizes system performance as well as battery performance.
Meanwhile, you can also follow below steps to set your phone under safe mode for monitoring:
First verify that Fast Boot is not enabled, Settings > Power > Make sure Fast Boot is not selected. To enable safe mode:
1. With the device turned off.
2. Press the power button.
3. Once the device turns press and holds the volume down, once you see the splash screen.
4. Press and hold thevolume down button (DO NOT RELEASE THE VOLUME DOWN).
You will know it has worked because the device will give a brief vibrate or 3 quick vibes. Once it loads you will see on the “Safe Mode” on the bottom left of the screen. This disables all 3rd party apps and drivers from launching. Use the phone normally for 24-48 hours like this. Do not use 3rd party apps or install from the market or the test will be inconclusive.
If the issue will not occur under safe mode, please uninstall the 3rd applications.
Should the problem still persist when your phone is under safe mode, please kindly back up your personal user data and follow below steps to set your phone back to factory default settings:
Settings> Storage> Factory Data Reset".
but this happened on Safe mode too, so i decided to go and get replace by the market guy, but he ..... nvm
After that i switched roms and faced the same issue
srashedian said:
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
Click to expand...
Click to collapse
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Moix123 said:
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Click to expand...
Click to collapse
You find it in
Home> HTC One X> One X Android development
btw is this possible that my stats are incorrect, reason for asking is that. it shut downs like its out of power. and it takes ages to charge up completely even if its on 86%. I install franco, and now its on charging, it will take almost 2 hours plus to get charge completely.
I will post update after wiping battery state
Moix123 said:
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
Click to expand...
Click to collapse
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
theDroidfanatic said:
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes sir i did try that out too,
I flashed the kernel and i charged my battery to 100%
and tried battery stats wipe, still i am having same issue.
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
logs?
poodleDoo said:
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
Click to expand...
Click to collapse
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
I would use ODIN or KYES to flash it back to OEM stock firmware. Also remove the micro SD card if you have one in there, sometimes corrupt cards can cause boot loop.
true
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
sharing
poodleDoo said:
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
Click to expand...
Click to collapse
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
dsilx said:
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
Click to expand...
Click to collapse
The tablet did the same without the sdcard, and I tried a couple times to do a factory reset with no luck.
The fact that it does the same with a different ROM and kernel is what makes me think it's hardware related
moonbutt74 said:
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
Click to expand...
Click to collapse
Cool, i'll get syslog installed and see if I can find anything.
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
awesome
poodleDoo said:
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
Click to expand...
Click to collapse
Awesome to hear sounds like @moonbutt74 was right
Hope it keeps working have fun
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
cool
poodleDoo said:
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
Click to expand...
Click to collapse
Well that sucks u have to have battery saver on all the time but at least its working now
hmmm
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
moonbutt74 said:
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
Click to expand...
Click to collapse
I'm running rooted deodexed stock ROM with Blackhawk 2.1 kernel.
But as I mentioned in the OP, the problem was there with the full stock device, the new ROM and kernel were installed after the problem started.
ouch
i think you pegged it right with internal storage being damaged.
only thing i can think of besides getting your money back is do a full data partition wipe and format
and a full system wipe and format
either way that has to suck. sorry i couldn't help.
m
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty
athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.
athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.
I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.
Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.
Can this be related to SIM carrier:Radio drivers?
I dont think so.. Because i havent changed Sim
Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.
I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?
Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.
I updated to Nougat couple of days ago at firmware 2.41.400.5 stock rom
Battery issues was huge to me and couldnt find out why, can anyone help me to identify why my phone was awake overnight? It happens even in safe mode.. ><"
Will be glad if anyone could help or suggest anything, did a cache partition wipe and reset from recovery after the update.
These are some additional stats from GSAM battery
Mine is definitely shorter, but not as yours. And no issue like the OS huge consumption. I saw some other guys have the same.
I used to get 6h+ screen on time, now is less than 4h30.
Alpert3 said:
Mine is definitely shorter, but not as yours. And no issue like the OS huge consumption. I saw some other guys have the same.
I used to get 6h+ screen on time, now is less than 4h30.
Click to expand...
Click to collapse
What should I do mate, any idea? This is crazy.
Anything in the BBS or WLD that I can deal with?
johnteolh said:
What should I do mate, any idea? This is crazy.
Anything in the BBS or WLD that I can deal with?
Click to expand...
Click to collapse
Sorry man, I don't know. I'd say a hard reset, but that works 50-50 for the users who ran into the issue.
johnteolh said:
I updated to Nougat couple of days ago at firmware 2.41.400.5 stock rom
Battery issues was huge to me and couldnt find out why, can anyone help me to identify why my phone was awake overnight? It happens even in safe mode.. ><"
Will be glad if anyone could help or suggest anything, did a cache partition wipe and reset from recovery after the update.
Click to expand...
Click to collapse
hi
in download mode > bootloader > recovery mode > factory reset > reboot
goodluck
Alpert3 said:
Sorry man, I don't know. I'd say a hard reset, but that works 50-50 for the users who ran into the issue.
Click to expand...
Click to collapse
Thanks man for your time to go through my post, appreciate it Maybe I will give the system another few day try before factory reset again. Not gonna flash any rom yet, as it will breaks its warranty
2.41.400.5
johnteolh said:
Thanks man for your time to go through my post, appreciate it Maybe I will give the system another few day try before factory reset again. Not gonna flash any rom yet, as it will breaks its warranty
Click to expand...
Click to collapse
Anyone can provide 2.41.400.5 stock ROM, or RUU stock file ROM.
mrsyamsul said:
Anyone can provide 2.41.400.5 stock ROM, or RUU stock file ROM.
Click to expand...
Click to collapse
hi
for you : https://www.androidfilehost.com/?fid=457095661767155503
What result?
It's kernel issue and I have same issue on all rom (custom and stock) and factory reset, custom kernel don't help me.
Ohio_wakelock - kernel wakelock. I think it's hardware problem.
Tornado77 said:
What result?
It's kernel issue and I have same issue on all rom (custom and stock) and factory reset, custom kernel don't help me.
Ohio_wakelock - kernel wakelock. I think it's hardware problem.
Click to expand...
Click to collapse
I had this issue both before and after i upgrade to nougat, but anyway, what I did was I let the battery drain the same way it does for about 1 week and recharge it every single time. I think after that the battery sets and now the battery life is pretty awesome during idle, less than 1% drain sometimes overnight, less than 5% if wifi is on. Perhaps just be patient. I doubt its a software problem.
Hope that helps mate.
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.