Related
Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks
Are you using a custom rom of any kind, rooted etc. giving details like this helps people answer questions.
My advice is if you are useing a custom rom then backup your apps etc. then redownload the rom and flash it as new then recover your apps.
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.
msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.
So enjoy the fix if you ever run into the above issue.
Im fine with stock, but I miss the fun of trying new roms.
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
OK, here is kernel log. I powered on the device, let it boot to the latest Lineage OS (lineage-17.1-20210201), then entered pin number and waited. Screen turned off, and a couple of second later device restarted (showing "Mi" and at the bottom "unlocked"). Then I imediately pressed "power + volume UP" to boot into recevery, where I copied log file).
I noticed multiple i2c errors, but couldn't find where exactly device initiated reboot.
klepec said:
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did you do clean flash? Wipe data, cache, system, on internal storage android directory must be deleted?
What's your firmware? I guess old oreo and not new one - pie, it should be 11.0.3 or newer!
Update Firmware first using MI FLASH TOOL NOT FROM RECOVERY!!!
Than clean flash Official LOS 17.1 again.
If your WiFi won't work after that your persist partition is corrupted.
For extra info search xda forums.
Good luck and stay safe!
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
klepec said:
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Yap all above 11.0.3 is ok..
Advice: don't rush! Read and take it slow. If you rush you'll probably mess it up... unlock your bootloader first, its easy to bring it back to life if you gonna mess up your phone.
For better overview watch how flash and what options to pick
Good luck and stay safe!
Hi, first post btw, but as the title says, my phone has had problems after flashing back the stock ROM
The previous ROM installed was Lineage OS, and I wanted to go back to stock, so I flashed it using SP Flash Tool, but after flashing the stock rom. I've noticed 3 problems after the flash:
Problem #1
I've noticed the screen was very dim even on the Realme logo in boot, which normally goes to full brightness first then goes back down when booted. When I tried to adjust the brightness, it was not as bright even on max, I've also tried to turn on auto brightness, but no success
Problem #2
There are no biometrics available to use on settings, so I can't use fingerprint or Face Unlock.
Problem #3
The volume is always on max, when I turn the volume down, it shows the volume slider UI go down, but no change in the actual volume. Even when I plugged in my earphones, it still doesn't change
Problem #4
Mic not working, even my earphone's mic isn't working on my phone, but it works on other devices.
I haven't found any more problems yet, but these 4 have been the biggest problem I have, no money to buy a new phone, so it would be really helpful to have a solution to this.
I've already used the scatter file a few times before when my phone was stuck on bootloop, but back then there were no problems, just now.