I would like to have more information if users have experienced the issue of often freezing and shutting down of the device on the k50-t5.
This is happening to a specific device that has never been rooted neither by recovery, not even by softrooting with applications such as kingroot.
A hardreset on the device through the lenovo recovery did not improve the issue.
A hardreset through the chinese recovery has not been performed yet.
I myself due to immediately rooting it have not tested the official stock rom to have more insight to compare it with this other device.
I'm not thinking of rooting this device since this problem, what i had in mind is also resetting through the chinese recovery and if the problem persists update a later version of an official stock rom to see if it has improved.
I would appreciate it tremendously if someone had more information over this matter or any opinions.
I have encountered many of these issues in the past yet all of were fixable. Mostly software issues or what comes into my mind is a defect battery.
Could be more however i am hoping for the best.
The device has been used one month and since 2 days ago frequently shows this issue.
Within an hour it has been 6 times the last being directly after a hardreset with no applications installed.
topic solved turned out being no hardware problem. it was unusual however for it happened also in the recovery not just the OS
thanas said:
I would like to have more information if users have experienced the issue of often freezing and shutting down of the device on the k50-t5.
This is happening to a specific device that has never been rooted neither by recovery, not even by softrooting with applications such as kingroot.
A hardreset on the device through the lenovo recovery did not improve the issue.
A hardreset through the chinese recovery has not been performed yet.
I myself due to immediately rooting it have not tested the official stock rom to have more insight to compare it with this other device.
I'm not thinking of rooting this device since this problem, what i had in mind is also resetting through the chinese recovery and if the problem persists update a later version of an official stock rom to see if it has improved.
I would appreciate it tremendously if someone had more information over this matter or any opinions.
Click to expand...
Click to collapse
I've tried I think about 9 ROMs in total now, some from hackerpower's excellent thread and some from NeedRom, including the latest ROW and Chinese ROMs - none of which have been stable for me. Well, the best so far was the Lemonchello Novamod, in terms of features, smoothness and battery consumption, but after a few days that too crashed and the phone refused to boot any more. The problems have occured often whilst using YouTube or embedded video, and sometimes just using a web browser (I've tried various).
What was the hardware issue you encountered, and what was your solution? Many thanks!
i havent been handson with the device having this problem, although the issue was due to official stock rom and recovery.
Related
Users following our Turkish Optimus 4X forum had lagging problems after v20C firmware update even after they performed a factory reset on the phone.
They complained that the phone was working very slowly and even after closing a simple application, the icons on the launcher page disappeared and appeared again.
Following is the solution that helped the users who had this problem:
Run LG Mobile Support Tool (use B2CAppSetup.exe to install) and connect your phone to the PC with USB cable.
In the application menu select Customer Support/Recovery Phone and follow the instructions.
The application is going to download the latest JB firmware for your phone and reflash it on the phone.
Hope this helps the users who have a similar problem.
Please note that although other flashing options might also be useful, this is a simple solution which can be performed by anyone who can use LG software.
(The solution was posted by a 53 year old forum user who is not an expert on neither Android phones nor Windows OS.)
I am gonna try this right now!
UPDATE: still laggy.....
That problem also happened on V20A in my opinion..
Yes....I flashed v20a, v20b, v20c...then I did factory reset everytime...and problem still persist.....I started to have this problem when I installed v20a
Needed to wipe phone anyway as G-Apps had an issue
But cant see a difference so far
*edit*
I noticed last night my play store UI changed
I did a factory reset, then followed the recovery in LG support tool.
Memory use stayed the same, but so far having no other issues with my phone.
Good day all, first timer posting but have been reading the forms for a while now.
I have a major problem with my galaxy note GT- N7000. I have browed through the forms and have not seen a problem like mine. I really need help with my phone.
Problem:
The phone is rooted with paranoid android rom; current version PA_n7000-3.60. I have been using this for over a year with no problem, when all of a sudden the phone goes into android update screen and ever since been on that screen whatever I do. I never tried to update the rom or anything when this happened, just found it like that. All auto update are turned off.
I have tired installing the rom again using CWM and even tried installing the latest update still the problem persists.
I don’t want to format the phone because I have some very important information I will lose if I do. Cannot back up using CWM, getting error messages, cannot get access to phone via connection to my computer. I am in a jam and really need help with this.
Thanks.
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.
Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.
What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.
This is a boot image issue
Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution
He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.