Hello all, I'm facing an issue with my OP7pro that is making me mad
After the update to Android 10 (stable) my phone was absolutely brilliant (data formatted in F2FS) but one day, completely random, some apps started to FC. I decided to reboot my phone and I got a bootloop. I thought that a factory reset should be able to fix the issue but nothing has changed: FC and then bootloop. I tried full wipe from twrp and the msm tool as well but I'm still have the same issue (ext4 and F2FS). Any advice?
Related
Hi,
As the title says:
Have a Nexus 5 running the latest lollipop build that has been working properly for a while (Phone is a Google refurb from November 2014, replacing my original N5 that had battery issues; Warranty expired Feb 2015)
4 days ago, it randomly rebooted and then got stuck on the "Optimizing apps" page on initial bootup - would never go past a certain app number
First tried wiping cache - which didn't complete even after 48 hours
Next tried full wipe from recovery, which worked but then shutdowns still happened
Reflashed all stock images (Phone is stock, not rooted) last night - problem still exists with random shutdown - but I can always get past initial setup; shutdown problems happen a little while later during use
Wiping cache from recovery now gives a "Could not mount /cache/" error in recovery
My hypothesis - that there's sector(s) on the eMMC that's borked. It's a 32GB phone - is there a way I can flag off a certain sector as "bad" and put the cache partition somewhere else? Also open to other suggestions, including replacing the eMMC chip if needed (I can find someone set up for BGA work).
I considered doing a file check from Philz / TWRP, but since the issue persists after a full reflash/reformat I assume that it's not a software bug.
Thanks in advance for the help, let me know if there's any other information I can provide that might be useful.
Anyone?
Hi all,
Rooted and installed cyanogenmod some while ago and had go into the habit of updating it every month or two. In December, I updated (20151202) and it seems to have borked the phone - I am getting the "unfortunately google play services have stopped" issue.
I have been searching for an answer for some time, but there seems to be a much deeper issue:
- I cannot remove play services, but more to the point, neither can I factory reset
- I have tried reflashing, but neither the bootloader nor recovery seem to work properly
- cannot clear/wipe data or cached
- cannot factory reset
- cannot re-flash
the android robot image flashes, but disappears quickly
I have tried re-flashing recovery (both cyan and twrp) but although adb reports everything ok, on the screen I see a note saying "mismatched partition size (recovery)"
I may be doing something stupid - any help gratefully received
Thanks
Robert
No worry, if you have windows (xp, 7, 8 10), use this program: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
Thanks - that seems to have done the trick. Working now
Brilliant
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516
Running AOSP Exstended 8.1.0 while seemingly normal use (in actual fact data stopped working, so I reset the phone to solve that issue).
It then proceeded to reboot loop a few seconds after it gets to the lockscreen. I'm not sure if it's related to the data partition, but it seemed to be the culprit, since wiping caches from TWRP or re-flashing the system.
I did end up making a backup of said partition and then wiping it, but I'd like to recover everything from data if possible (maybe flash it back later and fix it somehow?).
Can anyone recommend any specific steps?
I've never encountered the particular issue of it rebooting only after the lockscreen (regular boot loops in my experience are the boot logo).
I haven't been able to find anything useful on google though I did find a lockscreen reboot case on XDA that was unsolved.
Thanks in advance!
It happened again today.
Does nobody have any similar experiences? Would anyone know if it's the phone itself causing this issue or would it be tied to the ROM?
Hello,
Since June 2020, I have been facing erratic issues with my oneplus 7.
- Started with a reboot loop. Did a factory reset, things were ok for a day.
- After that the phone randomly reboots atleast 2-3 times a day. Factory resetted many times. With a hope that beta build may solve the issue, installed BETA software from oneplus. But no luck. Problem continues.
- Recently noticed that sometimes, all of a sudden my contacts disappear. Wiping cache or disabling and reenabling Google contact sync brings them back.
- Wipe Cache data doesnot help in resolving this issue of random reboots
- Occassionaly apps like Whatsapp, Phone dialer or Launcher crashes. Wipe cache temporarily resolves the issue, but it again comes in a day or two.
I have not installed any unauthorised apps and all my apps are from verified google play store...
Totally frustrated with the problem of the phone...
Anyone has any luck in getting a solution to this problem?
Try latest open beta
Thanks for the reply, but I am already on the latest beta
This is because maybe the last ota installed (before this problem started) was not done porperly. Try full reset your phone and flashing the rom again through fastboot or you can try going back to h2os (which is the main rom when all the OnePlus phones are made with then switched to o2os) and then switch to o2os which will be a clean flash. You can find the procedures in the forums. I faced your problem a lot because I switch roms a lot and tried out these which solved mine