Hello everyone,
Me, and so many people using this tab suffered from a bug that prevents us from installing TWRP successfully or even Non-Regional Samsung ROM.
What exactly happen is that when we install TWRP etc using odin TWRP won't normally boot after pressing vol+ and pwr and home, it just keep restarting so many times, and after restarting so many times it enters TWRP with a touchscreen that doesn't work at all, the exact same happen to me when I installed a Samsung ROM from another region, that problem
appeared after the update "T585XXU7CUH1".
If any developer can help us, please reach me out, I can provide logs, and test and help as much I can, hopfully this bug will be fixed soon, please share this thread with any developer you know.
Related
Hi all,
I've recently upgraded from a Samsung Galaxy S3 (i9300) to a Samsung Galaxy S5 (SM-G900F). Phone seemed to be working as desired so decided to go ahead, root, and install a custom ROM for enhanced functionality and customisation. Root process went smoothly, just running a simple CF-AutoRoot with Odin3 (voids KNOX, but no other problems), then installing PhilZ Advanced CWM Recovery.
From there I decided to install an unofficial build of CyanogenMod 11; found information on this forum. Flashing worked perfectly (and took rather little time!), but upon installation I noticed a strange problem. If I hard reboot (power off, power on) the device, with Wifi & Mobile Data off, the time and date are reset to incorrect values. Usually 01/01/xxxx and the time around 00:00. Same problem occurs even if when I turned off Network-allocated time and tried and set time manually.
The same problem occurred with other similar CyanogenMod based builds such as [AICP] and [AOSB]. I decided to restore back to the stock ROM and noticed that the clock and date were set correctly on reboot (and also on custom versions of 4.4.2 such as SpeedROMv7).
I checked with the terminal the value of the 'hwclock' (from BusyBox) and it reported an odd date somewhere in 1970, but different to the ones in found on CyanogenMod etc.
Does anyone have any idea what could cause this kind of problem and how to fix such an issue? If anyone wants any additional information about my device, please don't hesitate on commenting in this post. Would be grateful for any feedback. Thanks! :good:
PS: Also seem to be experiencing a problem with WiFi randomly disconnecting after a period of time. Not seen many threads with this said explicitly however. Problem with no voice in phone calls with headphones still persists but I've acknowledged that this is a known bug at the moment.
A.
Bump
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Anyone?
AlfieJPalmer said:
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Click to expand...
Click to collapse
Same Issue.
I have been encountering this very same problem for a while now, in fact, I am expriencing the same issue with my Galaxy S4 (i9505). So this must really be an issue of the CM code I guess.
Any ideas on how to solve this would be welcome since it is a really annoying issue
remove me
Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance
motoplayguy said:
Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance
Click to expand...
Click to collapse
You should return to a pure stock configuration (including recovery) and start over, preferably using RDS Lite. It won't be easy as there are no giudes written explicitly for the G4P. You will have to derive the procedure by reviewing other threads.
A less comprehensive approach is detailed in the following thread but it may not solve your radio issue.
https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797
As for not booting to system that's likely due to a procedural error when twrp was first flashed. Check the TWRP threads for corrective action.
Hey guys, I have some problems with my s4 and hoping you could fix these. I'll try my best to include details of what I did and any details that are missing that I will include
Started with me trying to install lineage ROM on my s4 when things started to grease up.
Ok the problem is the phone would not boot to the main OS but when it did I flashed the recovery(twrp)with odin which seemed to work for about a minute or two before powering off. Also I couldn't get to the recovery(twrp) even when pressing the correct combos I just flashed it again and again until it worked but wouldn't work sometimes. I went back to the stock ROM which didn't work either.
I know I am missing out on a few details but if any of you guys can help me that would be great.
partition error ?
Crooton said:
Hey guys, I have some problems with my s4 and hoping you could fix these. I'll try my best to include details of what I did and any details that are missing that I will include
Started with me trying to install lineage ROM on my s4 when things started to grease up.
Ok the problem is the phone would not boot to the main OS but when it did I flashed the recovery(twrp)with odin which seemed to work for about a minute or two before powering off. Also I couldn't get to the recovery(twrp) even when pressing the correct combos I just flashed it again and again until it worked but wouldn't work sometimes. I went back to the stock ROM which didn't work either.
I know I am missing out on a few details but if any of you guys can help me that would be great.
Click to expand...
Click to collapse
try this, have problem like that, but i cant use any os greather than kitkat
but make sure you DUMP your partition that mentioned ! to PC
https://forum.xda-developers.com/galaxy-s4/help/battery-disconnect-upgrade-os-t4005567
I have some serious issue with my samsung m30s .
My phone restart in ever 1,2 min.
I tries flashing stock firmware through odin .
Still it wont worked.
I tried installing twrp and magisk.
After that i tries to install Prish os . But still before booting into system . Its restart every time .
I need help
Please help me.
Badal meherr said:
I have some serious issue with my samsung m30s .
My phone restart in ever 1,2 min.
I tries flashing stock firmware through odin .
Still it wont worked.
I tried installing twrp and magisk.
After that i tries to install Prish os . But still before booting into system . Its restart every time .
I need help
Please help me.
Click to expand...
Click to collapse
Hey, sad to hear that you are facing issues, but it seems problem is something else, as you mentioned it rebooting on STOCK ROM as well so.
If you can share some screenshots of about device we can check BL version and few things also feel free to text me on telegram @neel0210 so that we can have proper convo and can help you as much as possible.
I too have freeze and reboot problem whenever I use device, its random and cannot be predicted when its going to happen,i tried all ROM ,still same issue persists
yes me too have freeze and reboot problem whenever I use device, its random and cannot be predicted when its going to happen,i tried all ROM ,still same issue persists
why we have same problem in same time? this is from samsung or what?
Hi, is there some new development yet?
Been having that same problem for the last few days now. There were short periods where I could use the device without any issues, but now it's restarting after just one or two minutes, if it even gets that far.
I have the same issue as well
For me the device fails to boot now.
The only way to get it to boot is force off encryption and using lineage.
Yet the phone panics in any app like even amazon.
Service people say it's hardware fault and needs the board to be changed costing 80% of what I paid for the phone itself.
Any help?
Guys, same issue is happening with my sister's A50 from last july(2021) and is still present. On stock rom it was not even usable but on lineage os i am able to use it for YouTube, songs and pretty much other stuff.
Looks like the issue is with the memory ic but I can't check it with anyone as in india even the people who repair devices are not well versed with knowledge and speculate on everything.
I've seen foreign repair guys, they have great knowledge when it comes to repairing of the devices.
I wish we had knowledgeable local repair guys in india too(went Little off topic but what can I do, I've been feeling this a lot lately).
If anyone knows anything or can point in the right direction then pls help.
Thanks for reading.
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?