Recently my phone started rebooting in random moments. After doing some research I think that some system files are corrupted. I tried doing factory reset in recovery, but thats not what I wanted because my system version is still 7.0, while initially it was 6.0 and the problem still occurs. Is there a way to do complete reset to factory setting and restore system?
There's no way back to 6.0 for now unfortunately, updating to 7.0 updates the bootloader so any attempt to flash 6.0 back with a pc will leave the phone unable to boot. I think a signed bootloader from 6.0 would be required, and hasn't been released.
There are ways to re flash the stock firmware of 7.0, but I'm not sure if that'd help as I did that recently and still get the occasional reboot.
You also get this random reboots? Is it more common problem?
Your best bet is probably to find an alternative download for the same firmware you have now. Hopefully that helps.
I OTA'd to Nougat the day I got my Z, it was on MM, and all is well. So not sure it's an issue with N itself, more likely corrupt download, as you said.
No, you cant downgrade, not without great risk. Same for all Moto's these days.
wojwen said:
You also get this random reboots? Is it more common problem?
Click to expand...
Click to collapse
Yeah i do get them but rarely, and i am on a custom kernel so it could be that causing it for me. If factory reset doesn't help I would try flashing stock Nougat again.
Related
My device is a local re-branded and enhanced Xolo a500s/it's like a karbon a5 a think. After successfully updated my device via OTA and after my device rebooted. My screen started to flicker randomly. My phone is not rooted and im still using the official stock rom. I found a temporarily solution by doing a Factory Reset, the flickering would be gone but it will come back after my phone screen goes off and on. Anyway to fix this?
I suspect that the new lockscreen bloatware system app that comes with the update causes this, but hey I only suspect it and i'm new to the android community. I can't disable it(googled already, and the only way to freeze/remove it is to root.) I can't root my device for something like a hunch. I'm waiting for a software update that would fix my device's touchscreen collide bug.
Appreciate all of your thoughts.
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
UltraWelfare said:
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
Click to expand...
Click to collapse
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
*edit
okay, i've managed to enter recovery menu. the one where you use the volume buttons to move. Is it really safe to select Wipe Data/Factory Reset there? Is that what you're prompting me to do in your post?
drckml said:
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
Click to expand...
Click to collapse
Report back if something new happens
UltraWelfare said:
Report back if something new happens
Click to expand...
Click to collapse
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
drckml said:
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
Click to expand...
Click to collapse
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
UltraWelfare said:
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
Click to expand...
Click to collapse
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
drckml said:
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
Click to expand...
Click to collapse
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
UltraWelfare said:
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
Click to expand...
Click to collapse
Thanks a lot man. I've flashed a stock rom and my device got fixed from screen flickering. Really looks like a firmware bug. So I've just downgraded.
Again thanks a million
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
I know there are many forums addressing this problem but mines is a bit different, I know the common solution is App Info > Clear Data but this doesn't help. Neither does a force stop, reset or a clearing of settings cache.
I resolved to needing to do a data wipe, however I received this message, "failed to stat /data/date/com.android.defcontainer/cache" and nothing wiped. I started the phone to the exact same home screen and apps, but I had lost wifi settings and such, and can't open settings to set up wifi yet again.
I contemplated reflashing CM through the installer but wasn't sure if the failed to stat problem would interfere and potentially brick.
Any help would be much appreciated, cheers.
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
boomboomer said:
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
Click to expand...
Click to collapse
I read online that downgrading from 4.4 (CM) to Stock 4.3 would hard brick the device, is there any merit to this?
No, if you use the right firmware and do it properly there is no more risk than with a normal flash.
Problems with all roms SM-T210
Hi!
This problem is driving me crazy!
I have a similar problem!
I have Samsung Galaxy Tab SM-T210
For a long time I used RocketTab rom. I decided to try out new Android 4.4.2 Rom.
I started to get an error "Unfortunately settings has stopped" when I tried to open settings. I also got another application errors.
Now, it does not matter what rom I install, i get application has stopped error.
Even the RocketTab rom.
I flashed original stock rom via Odin, same problem.
I tried CWM and TWRP recovery.
I wiped dalvik cache, system, cache, Data, internal storage.
After flashing a new rom via odin or recovery, same problem.
I don't understand how it's possible that after deleting everything, I still get the same error.
Sometimes when I open settings, instead of getting an error, tablet restarts.
Tablet was 100% working before flashing Android 4.2.2
Any ideas?
Thanks guys
Why are you asking in the i9300 forum?
boomboomer said:
Why are you asking in the i9300 forum?
Click to expand...
Click to collapse
Because the problem seems to be very similar.
Point taken!
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs
Hi
I got the s21 Exynos. After the android 12 update many of the apps keep crashing. They are all up to date. I cant seem to find any solution to this problem. Am i the only one with this problem ? Cant find any other info about this issue.
Factory reset. Do not use SmartSwitch to reload the apps.
A factory reset is always best to do after a major OTA firmware upgrade to avoid issues.
blackhawk said:
Factory reset. Do not use SmartSwitch to reload the apps.
A factory reset is always best to do after a major OTA firmware upgrade to avoid issues.
Click to expand...
Click to collapse
Okey, is this a common issue ? Never had it before.
Dardo27 said:
Okey, is this a common issue ? Never had it before.
Click to expand...
Click to collapse
Don't know but a factory reset is SOP.
I never upgrade an Android if it's fast, stable and fulfilling its mission.
Upgrades tend to break things...