Related
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
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).
Hi guys,
I have a one little problem after what I installed CM13 on my phone.
I dont know if can be problem with that, but after what I installed CM13, my phone is very hot and battery is out after 6 hours (i have new battery). Can I fix it, or its dead phone?
Many thanks for your help,
Vanda
use the stock 4.2.2 android.
cm13 id dtill in beta
vanda said:
Hi guys,
I have a one little problem after what I installed CM13 on my phone.
I dont know if can be problem with that, but after what I installed CM13, my phone is very hot and battery is out after 6 hours (i have new battery). Can I fix it, or its dead phone?
Many thanks for your help,
Vanda
Click to expand...
Click to collapse
which app or apps are using your battery more than they should?
Wipe their cache/data or maybe reinstall.
If you can't tell install an app like Trepn Profiler to find the app using your CPU.
IronRoo said:
which app or apps are using your battery more than they should?
Wipe their cache/data or maybe reinstall.
If you can't tell install an app like Trepn Profiler to find the app using your CPU.
Click to expand...
Click to collapse
I think, that problem will not be in apps.
The phone is hot during a call, or sometimes when is GSM signal low.
I think, that whole problem is in GSM modem, not in apps.
When I install new ROM like CM13, must I install some GSM "driver" also? Or all what i need is in the ROM image?
Thanks,
Vanda
I prefer to install Betterbatterystats to find out which app or process is draining your battery/hold your phone awake.
Or
You look with a terminal emulator and the command "top" which process is running highly cpu state, you can look this up with adb shell,too
"adb shell" and the type "top"
In cm13 if you are looking around in menu it gets hot. When you run somethings it get hotter and when you enable mobile it get hottest. If you want to use it than deal with it. And yeah battery sucks. there is s6 ported rom 4.4.4 which is great and there is also s5 ste rom which is also great but Google s5 ste rom. Im currently using it and battery life is alot better like stock 4 2.2.
Sent from my GT-I9190 using XDA-Developers mobile app
vanda said:
I think, that problem will not be in apps.
The phone is hot during a call, or sometimes when is GSM signal low.
I think, that whole problem is in GSM modem, not in apps.
When I install new ROM like CM13, must I install some GSM "driver" also? Or all what i need is in the ROM image?
Thanks,
Vanda
Click to expand...
Click to collapse
Modem is separate to ROM. Do you have one of the latest modems installed? Don't know which model phone you have but for the I9195 the latest modem is CPB2 (see Spitya thread), there have been a lot recently that I have flashed, one a few months ago made a big difference to call quality for me. (backup your IMEI, before flashing, with an app like efs backup!)
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP
Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..
Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP
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.