Related
Hi all,
it has been now nearly two weeks since the rom update leaked, and still so sign of an official update on htc website.
I'm wondering if this was really the final rom version, if so i don't know why htc would wait another two weeks after the leak.
I heard that somebody got that rom from an ftp server which is used by htc to upload data before it gets released. In this case two weeks seems also way too long for a deployment.
Are there any signs of the official release? I'm curious to see whether there are any last minute changes done.
well it could do with both orange and tmobile (in the uk) need to add there custom rubbish to there phones?
I read about major improvements in speed.
BUT - I also read about weather DB issues, WiFi issues, a.o problems.
So, I am definitely going to stay put, until an official release.
I am not going to waste time on reinstalling software etc, by flashing something "maybe-this-is-a-rom-very-close-to-the-final-one"!
yeah of course the carrier updates will take more time, but im talking about the htc update for unbranded devices.
since i made the ruu update i can confirm speed updates (but not huge difference), and i can confirm that more often the browser seems to have issues when going online via wlan. connection is there, signal is there, but the browser cant open pages.
and my device actually freezed two times, i couldnt make softreset and had to take the battery out. annoying.
but overall im satisfied with the performance optimization, still i will make another update as soon as the official rom is out..
and another minor thing: updating weather information manually will result in three updates. the app will update the weather data three times in a row, even though you only pressed update once,
I've had none of those problems, just checked the weather and it seems to update just once. I did have to pull the battery a couple of times BEFORE installing this new ROM when my phone totally locked though.
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
rom t-mobile
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
rhedgehog said:
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
Click to expand...
Click to collapse
yeah two weeks was maybe too much. I was hoping this is not final since i have some new issues since i made the ruu update:
- peep widget updates only every 30th try. I'm trying to update the tweets and it doesn't work for about 20 times, and then somehow it works after many more tries. When i open peep app i get an error message that the service is not reachable.
- wifi has problems. many times it seems the connection is dead, when technically everything is ok.
- freezes (but i installed about 40 apps, maybe this was too much...)
- keyboard has sometimes lags. i never had ANY lags inputting text before the update.
- more force closes by 3rd party apps.
- touchflo force closes seem to occur more often also (but i had them before too so this might be the same).
- freezes when the device is in sleep mode. I was at a meeting, not doin anything with the device. Then i wanted to check the time and the display didn't power on. So the device freezed during some background process by android or any 3rd party app. I never had this problem before the update.
the good:
- yes its faster (homescreens)
- even the contacts list has LESS stutter, but stutter is still there. IPHONE 3gs is way ahead in this regard. i don't know why other lists on android are completely fluid while the contacts app list is not fluid.
- battery seems to last longer
overall the first impression was VERY good, but is somehow stained by the problems that surface after some usage time...i'm not 100% sure if the speed update was worth it...waiting for android 1.6 update, maybe this sorts some stuff out..
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
locutus-of-borg said:
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
Click to expand...
Click to collapse
the RUU update won't work on a branded device. You need root to install the new rom in this case.
foxmeister said:
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
Click to expand...
Click to collapse
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Shahpur.Azizpour said:
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Click to expand...
Click to collapse
Well, Menu->Security->Factory Data Reset should do the job. To be honest though, I'd be more inclined to trust the "standard" Android way of updating your ROM than the HTC RUU process, because, as far as I'm aware, this'll be their first RUU for an Android device.
Regards,
Dave
Interestingly, the second poster here, http://forum.xda-developers.com/showthread.php?t=557628 , indicates that they had a problem with the factory data reset, but a recovery image wipe fixed it. I wonder if this related to your issues?
Even if you don't want to flash the modified recovery image permanently to your phone, you could boot it using fast boot and then wipe.
Regards,
Dave
how does it work? how can i restore a revocery image? isn't this an issue with the latest RUU update, that flashing recovery rom is not possible anymore or am i mixing things up here?
Steps 1 to 5 in this link, http://forum.xda-developers.com/showpost.php?p=4257045 , tell you what you need to do to boot the modified recovery image. Note that this doesn't flash anything to your phone - it just boots off the image you've supplied. You can permanently flash the recovery image later if you wish, but since you took the RUU root, I guess you don't want to put anything "unofficial" on your phone.
I've no idea if you having RUU'd already will prevent this, and I'm not going to RUU my phone to find out, but I doubt you would be stopped booting using fastboot.
Regards,
Dave
okay, thanks for the info!
Modaco wrote on a thread that doing the RUU update will make it nearly impossible to flash a modified recovery image.
I'm going to work with my current setup for some more days. If i see the mentioned problem reoccuring more often, i will proceed with the steps in your post.
or maybe we will see some changes (if not to the rom itself maybe at least the RUU will get an update) with the official rom update.
bye
shahpur
Just searched and you are right, you can't boot the recovery image if you have the new HBOOT from the RUU. However, the situation is not irreversible!
http://android.modaco.com/content/htc-hero-hero-modaco-com/292396/if-you-flashed-the-2-73-ruu-and-got-the-new-hboot/
Regards,
Dave
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
sorry, was busy working, but it seems you;ve got the answers...
i;ve not had any problems that you have had either with those apps. mine is so much better it's ridiculous. but then i wiped first and again afterwards just to make sure.
Lars8000 said:
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
Click to expand...
Click to collapse
Wow cant wait for tht, but 2bh I wud like T-mob to release their update as well at the same time as I am getting the G2 Touch on friday.
So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?
If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk
Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.
Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.
Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk
Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.
What version were you coming from?
Sent from my iPhone using Tapatalk
EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.
Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk
Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.
Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.
Solved by using gesture instead of pincode
satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!
Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.
Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks
Appens to me 2 times, each time i needed to look/unlook the edp screen to solve
My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...
no charge bug here
No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!
tompere96 said:
Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!
Click to expand...
Click to collapse
Hello, why not posting your question in the related thread https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 and search for answers?
You did not mention which steps you take, sounds for me you coming from ressurection remix and just flash the ob6 rom without wiping etc? But I'm sure you did not, so please give exact steps to reproduce the issue.
And read some pages back in the linked pages thread, it's been discussed partially
why not posting your question in the related thread https://forum.xda-developers.com/one...-oreo-t3710003 and search for answers?
Click to expand...
Click to collapse
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.
tompere96 said:
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.
Click to expand...
Click to collapse
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.
tompere96 said:
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.
Click to expand...
Click to collapse
You got it. It's mostly cause of the internal storage you did not format. That's a common problem.
Stuck with 'Just a sec' after Factory reset
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.
Facing same problem
lakshmla said:
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.
Click to expand...
Click to collapse
i had this same issue solved by flashing nano or pico gapps
try this
Facing same problem with my htc 10 (pme)
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
I don't think you would have to root for that. You can just flash your original firmware to system which was working normally. You can find the files on the internet. You can use Odin and it'll be fine.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
Rooting or flashing custom rom won't help as I've tried everything with my galaxy a50 but the issue still persists. It's related to hardware of the device. Maybe some loose connections in the motherboard. Unfortunately, we don't have skilled local repair guys in India(assuming you too belong to India) who could look into this.
abhi-km said:
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
Click to expand...
Click to collapse
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
abhishekpandey.468 said:
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
Click to expand...
Click to collapse
If you under clock all cores below 1ghz and set selinuxe to permissive mode then magic happens.not even single reboot in last 26 days. Before it was restarting every 5, 10 minutes.
I am also facing the same issue with my M21, downgraded to android 10, but it didn't help. Any suggestions?