Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
AWretchSavedByGrace said:
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
Click to expand...
Click to collapse
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
thelad said:
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
Click to expand...
Click to collapse
So done that and got one black screen and the white light,went to work had 3g/4g on all day didn't get one black screen,got home connected to wifi and I got a black screen,so something to the with wifi seems to cause it for me
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Paradoxxx said:
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Click to expand...
Click to collapse
I think I'll have to its pissing me off now,goes great for hour or two then I'll get this black screen 4 or 5 times in a row
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
nono77240 said:
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
Click to expand...
Click to collapse
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
I don't know how much time after, maybe 6 hours later or so...
I had a freeze yesterday evening and had to reboot my phone.
Everytime it freezes on reboot and I have to wait 3 to 4 tries before the phone really boot.
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
I created a RMA ticket this morning.
My phone will go to repair center
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
My situation
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Breecko said:
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Click to expand...
Click to collapse
Have you tried holding power and volume down for a few seconds without the cable plugged into the phone?
thelad said:
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
Click to expand...
Click to collapse
acmerw said:
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
Click to expand...
Click to collapse
AWretchSavedByGrace said:
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
Click to expand...
Click to collapse
I received a mail yesterday evening saying that they can't take my phone and I have to do a factory reset.
I replied to this mail saying that I did multiple factory resets and even do a remote session with a oneplus tech support.
They sent me a mail an hour after with a number and the process to send my phone.
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Hi
to get to another mode you need to have the phone connected to a PC or Mac, so plug it into the usb and power off, once it is off hold volume down, this should make it go into download mode from there follow this link ( https://forum.xda-developers.com/razer-phone/help/razer-phone-os-t3772424 ) and you should get back to stock and you can retry to root from scratch or leave your phone as stock
Hope this helps
adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
If you got it to download mode but cannot communicate with the phone check your fastboot and drivers. You need Google USB drivers and the absolute latest fastboot. There are other posts here that can help you find the right stuff
adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
tabletalker7 said:
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
Click to expand...
Click to collapse
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
incinandseril said:
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
Click to expand...
Click to collapse
Hi follow the link from my comment above and give yours a try, don't think yours is toast just think it's in a boot loop cycle
My comment is second one down
incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
I´ve got this Screenproblem with the Oreo Update with sideload, it flash but then only this Screen, i found my mistake.
My solution was to do an critical unlock for Bootloader, than install 7.1 and than sideload 8.1 OTA, now it works very fine and much smother than before
[EDIT] After letting the battery run dry again last night, plugging my phone back into my laptop booted into download mode, again with the same display as below. Fastboot again recognised the device & after doing some searching, I'd seen another suggestion somewhere else I hadn't yet tried, which was forcing the phone to partition a (to be honest I couldn't even remember which partition I'd left it in from the attempted root)
The command is "fastboot set_active a && fastboot reboot"
I did this as soon as I was able to, rather than leaving it charging (this may be unrelated, but worth considering if you're still stuck)
after this, I got to the Razer logo screen lock (instead of the blank screen lock below), I was then able to follow Razer's instructions - which are linked in one of the comments on the link from the 2nd post here (hope that makes sense)
Now I'm happy to report everything is working, back to factory
I hope this can help someone else [EDIT]
I'm unfortunately in the same position, did you have any luck flashing back to factory?
I also tried following the guide from the 2nd link, these were the steps I took:
(I can confirm my bootloader is unlocked & critical also unlocked)
1. allowed battery to run dry
2. plugged into laptop whilst holding volume -
3. phone now in download mode with battery charge symbol on screen, I left it some time to charge but noticed it got stuck as per the screenshot (for approx. 6 hours)
4. device not recognised by adb, but recognised by fastboot
5. phone not accepting any fastboot commands, when attempting 'flash_all.bat' just hangs on the first line (flash partition:0 gpt_both0.bin), I have to close command line & reopen to try anything else, however whatever I try I get the same result, so basically the only responses I'm getting from fastboot are that it is aware of the device and confirms the bootloader incl. critical is unlocked
My next thought was the perhaps the phone attempted to boot once it reached the picture charge level and therefore locked in the same way it had initially on the razer logo. Should I attempt flashing the factory image immediately once the phone enters download mode, rather than allowing it to continue charging until it's flashed? Any ideas would be greatly appreciated!
Cheers
Been a while since anybody posted, I know... but did anyone who had this problem end up figuring it out? I am in the same situation and am freaking out a little bit, I JUST got this phone...
Just try this and should solve your problems
https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip
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!