Related
my mi a1 phone stuck in android one logo...how to overcome this...need urgent help...thanks....please help
press the power button until you get a reboot. This may give a full & complete reboot to the main screen
berlin51 said:
press the power button until you get a reboot. This may give a full & complete reboot to the main screen
Click to expand...
Click to collapse
tried to hold the power button, but same things happening...actually when pressing the power button in 1st page below MI logo "unlocked" showing and in next page android one logo stucks
The next thing to try is to press -vol and power to go into fastboot mode. Then once in fb mode press the power button for a while to exit fastboot & reboot to the main screen.
berlin51 said:
The next thing to try is to press -vol and power to go into fastboot mode. Then once in fb mode press the power button for a while to exit fastboot & reboot to the main screen.
Click to expand...
Click to collapse
no bro....same problem....can't go further....same stuck at android one page....have to go to service centre:fingers-crossed::crying:
Tell us more. What did you do before?
pharix said:
Tell us more. What did you do before?
Click to expand...
Click to collapse
Tried to install gcam once. But couldn't installed it. then after not tried. But today while seeing youtube phone suddenly restarts and stucks in android one logo
any solution for this stuck problem ?
i read somewhere about extracting something from the Stock ROM
sevensaints said:
any solution for this stuck problem ?
i read somewhere about extracting something from the Stock ROM
Click to expand...
Click to collapse
Why are u not flash new fastboot rom using mi flash tool!
sahu.trilochan said:
my mi a1 phone stuck in android one logo...how to overcome this...need urgent help...thanks....please help
Click to expand...
Click to collapse
Did you manage to solve it ?
or you just reflash it over new rom ?
Same issue with my Mi A1 that is not even a month old, I was reading a news page when all of a sudden it stopped responding. I tried to do a hard shutdown but when it rebooted the phone is now stuck in the Mi/AndroidOne logo.
I cant get into the menu to perform a factory reset, when I try to go into the bios menu by pressing and holding power+volume up, the phone just restarts and gets stuck in the Mi/AndroidOne logo again.
I will try to flash the rom and see if that help, although I have been unable to locate the stock rom for the Mi A1 therefore I will be flashing it with Android 8.0.0 Oreo (OPR1.170623.026.V.9.5.10.0.ODHMIFA)
This is the link to the steps I will be following:
xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1
I will update to let you guys now if it work, in the mean time if anyone has a different method to fix this I would appreciate the info.
I too have Android one logo issue
Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.
My Xiami Mi A1 running latest July 2018 patch of Oreo just started getting stuck also. I'm rooted and running Magisk.
Applying the July OTA update is the only thing unusual I've done recently. But that was about 10 days ago.
I rebooted one day just for good practice, and the phone showed the unlocked bootloader warning and then got stuck on the Android One screen. I left it for like 10 minutes, and absolutely nothing. I tried booting into fastboot (Volume Down & Power) and then reboot again. The only good news is I managed to keep trying to reboot, reboot into fastboot, boot again. Finally, I got a dead android robot looking icon and something like "no command found". I rebooted again, and everything was great.
Now, I've just tried a reboot again (a couple days later), and same **#^#! again... stuck on the Android One logo screen.
How can I figure out and actually repair this?
Note: I can still use fastboot to boot into TWRP and see all my files.
dadnammit said:
My Xiami Mi A1 running latest July 2018 patch of Oreo just started getting stuck also. I'm rooted and running Magisk.
Click to expand...
Click to collapse
If you are using Magisk 16.0 update to 16.7 beta.
sipollo said:
If you are using Magisk 16.0 update to 16.7 beta.
Click to expand...
Click to collapse
I am in fact on 16.0. Is this a known issue?!
In the meantime, just booting in and out of Fastboot over and over eventually seems to work. :/
dadnammit said:
I am in fact on 16.0. Is this a known issue?!
In the meantime, just booting in and out of Fastboot over and over eventually seems to work. :/
Click to expand...
Click to collapse
Yes, it's a known bug. Magisk 16.6-16.7 beta work better.
sipollo said:
Yes, it's a known bug. Magisk 16.6-16.7 beta work better.
Click to expand...
Click to collapse
If I'm currently running Magisk 16, can I safely flash 16.7 over it?
KalolParty said:
If I'm currently running Magisk 16, can I safely flash 16.7 over it?
Click to expand...
Click to collapse
Yes, you can update from Magisk Manager or flash .zip in twrp without problems.
sipollo said:
Yes, you can update from Magisk Manager or flash .zip in twrp without problems.
Click to expand...
Click to collapse
I am running Magisk Manager 5.7.0 because it is the last version to support OTA updates properly.
And I can't update Magisk before updating Magisk Manager (if I try to do it within Magisk Manager). So I will flash the .zip.
dadnammit said:
I am running Magisk Manager 5.7.0 because it is the last version to support OTA updates properly.
And I can't update Magisk before updating Magisk Manager (if I try to do it within Magisk Manager). So I will flash the .zip.
Click to expand...
Click to collapse
Last zip includes Magisk Manager too.
Hi eveybody.
Yesterday night I was watching some YouTub videos but then I fell asleep. I woke up in the middle of the night (4/5 hours later) and my 6T was off, because (I think) it ran out of battery. So, I plugged it into the charger and the "magic" happened. The phone got stuck at "the bootloader is unlocked..." screen. I tried EVERY key combination for recovery, bootloader and force power off, but it's still there. It's almost 5 hours that it's in this state. I can exclude some sort of root-related issue, because before falling asleep I did reboot the phone because I've installed a Magisk module. The PC doesn't recognize the phone.
What should I do? Thanks!
Remove USB cable and hold the pwr and Volume up buttons for at least 15 seconds
kantjer said:
Remove USB cable and hold the pwr and Volume up buttons for at least 15 seconds
Click to expand...
Click to collapse
Man, I swear. I tried this before, but no luck. Now that you posted this, it worked. WTF.
Pipodi93 said:
Hi eveybody.
Yesterday night I was watching some YouTub videos but then I fell asleep. I woke up in the middle of the night (4/5 hours later) and my 6T was off, because (I think) it ran out of battery. So, I plugged it into the charger and the "magic" happened. The phone got stuck at "the bootloader is unlocked..." screen. I tried EVERY key combination for recovery, bootloader and force power off, but it's still there. It's almost 5 hours that it's in this state. I can exclude some sort of root-related issue, because before falling asleep I did reboot the phone because I've installed a Magisk module. The PC doesn't recognize the phone.
What should I do? Thanks!
Click to expand...
Click to collapse
I had this exact issue this morning. It took me holding those buttons well over a minute.
suzook said:
I had this exact issue this morning. It took me holding those buttons well over a minute.
Click to expand...
Click to collapse
Man, I think that the buttons aren't so responsive when in that screen. The first time I tried to root the 6T I had to reboot from the OS, because I couldn't boot with the buttons. Do we have a problem, here?
i'm getting this too! are you guys rooted & flashed permanent twrp? i usually charge w/ my phone booted up. once i get to 100% i turn it off with the charger plugged in. instead of the battery charging animation, i get stuck on the b/L screen just like you guys here. @kantjer's suggestion does work
maxq1 said:
i'm getting this too! are you guys rooted & flashed permanent twrp? i usually charge w/ my phone booted up. once i get to 100% i turn it off with the charger plugged in. instead of the battery charging animation, i get stuck on the b/L screen just like you guys here. @kantjer's suggestion does work
Click to expand...
Click to collapse
I'm rooted, but when the issue happened I didn't have the permanent TWRP.
Pipodi93 said:
I'm rooted, but when the issue happened I didn't have the permanent TWRP.
Click to expand...
Click to collapse
The issue is related to Magisk.
As long as Magisk is installed, you will have the issue.
I had the same problem where it was getting stuck on the unlocked bootloader screen. I simply had to reinstall Magisk from TWRP and it all worked again.
tehbigbug said:
I had the same problem where it was getting stuck on the unlocked bootloader screen. I simply had to reinstall Magisk from TWRP and it all worked again.
Click to expand...
Click to collapse
You don't have this issue anymore? Just by reinstalling Magisk... I have been charging till full then turn off when not using , than power up in the morning... Still sucks though.
Me too
answered here
kantjer said:
Remove USB cable and hold the pwr and Volume up buttons for at least 15 seconds
Click to expand...
Click to collapse
Had the exact same issue. Found this thread and this worked. I guess I didn't specifically try Volume Up and only did just Power or Power+Volume Down. Shrugs.
Any fix for this issue? Didn't exactly get what @kantjer had to say.
Pipodi93 said:
Hi eveybody.
Yesterday night I was watching some YouTub videos but then I fell asleep. I woke up in the middle of the night (4/5 hours later) and my 6T was off, because (I think) it ran out of battery. So, I plugged it into the charger and the "magic" happened. The phone got stuck at "the bootloader is unlocked..." screen. I tried EVERY key combination for recovery, bootloader and force power off, but it's still there. It's almost 5 hours that it's in this state. I can exclude some sort of root-related issue, because before falling asleep I did reboot the phone because I've installed a Magisk module. The PC doesn't recognize the phone.
What should I do? Thanks!
Click to expand...
Click to collapse
Happened to me in the beginning too, after setting up magisk and everything. Every single key combination didn't work. Try plugging the charger off and power+vol down. It suddently worked at one point for me, kinda weird.
Domnisto said:
Any fix for this issue? Didn't exactly get what @kantjer had to say.
Click to expand...
Click to collapse
Yeah just hold down Volume Up+Power for 15+ Seconds. That's it.
So: no solution for this issue?
I can't charge while the phone is off?
Just happened to me too.
I was on beta14, TWRP and magisk enable all going fine
Dirty updated to beta15 (through TWRP, by flashing OTA file, reinstalling TWRP zip, rebooting, then doing my usual business in recovery flashing smurfkernel, magisk, smurkernel again, then booting to system, adding magisk modules and stuff.
When I do reboot to enable the magisk module I get stuck at that dam "the boot loader is unlocked..." spash screen. Pressing vol up + vol down + power does manage to force poweroff the device, but booting up again (be it only power button, or pwr+VolUp, or pwr+VolDown or pwr+VolUp+VolDown) only gets stuck again at that same splashscreen.
Damn it...
Any help is welcome... I hope the device isn't bricked
edit: rinstalled everything (after factory reset, and complete b14 install). it seems its the miracast magisk plugin which is ****ing the bootloader upon reboot >.<
(my phone is not usb connected)
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted
DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?
lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.
hey!
Device is having power-up issues.
e.g., I press the power button then choose Restart option.
During power-up cycle, the phone always hangs. Device is stuck on the screen displaying Essential logo and the Powered by Android. ??
Any help, would be appreciated.
PS: Every time I am forced to hold the power and lower volume buttons to reset the power cycle.
Tom23824 said:
hey!
Device is having power-up issues.
e.g., I press the power button then choose Restart option.
During power-up cycle, the phone always hangs. Device is stuck on the screen displaying Essential logo and the Powered by Android. ??
Any help, would be appreciated.
PS: Every time I am forced to hold the power and lower volume buttons to reset the power cycle.
Click to expand...
Click to collapse
That sounds like a bootloop. What happened prior to this starting? Update, flash a ROM, install an app, install a kernel or Magisk, sudden power off due to low battery?
As a general rule, I would fastboot flash the same or newer stock to recover. Or sideload an OTA to recover. Those are available on the Essential developer builds page.
Tom23824 said:
hey!
Device is having power-up issues.
e.g., I press the power button then choose Restart option.
During power-up cycle, the phone always hangs. Device is stuck on the screen displaying Essential logo and the Powered by Android. ??
Any help, would be appreciated.
PS: Every time I am forced to hold the power and lower volume buttons to reset the power cycle.
Click to expand...
Click to collapse
As ktmom says, also I'd specifically like to know if it was after the Feb update this occurred do you also have TWRP installed as a couple of others do that may have the same issue, see
https://forum.xda-developers.com/essential-phone/help/booting-feb-security-update-t4045545
edit: see bornroyal comments on other thread, serms TWRP not compatible, but someone on reddit made a compatible version.
ktmom and IronRoo,
This has been happening to my phone for atleast 4 months now.
I usually reboot the phone not often but sometimes. lets say once in two weeks.
PS:
I am stock and unrooted.
Accepted and installed the latest update.
I think you might be served by a factory reset. If course, that means you lose everything on the phone.
If that doesn't help, my knee jerk is the same, I would sideload the OTA.
Actually, I personally would unlock the bootloader and fastboot flash with the wipe to both slots. Or, sideload the OTA to one slot, them reboot to bootloader, if necessary, switch slots and sideload the OTA again. In theory, rebooting after sideling should switch slots so I would pay attention to where I start and where I am each step. OTAs, by design flash to the inactive (opposite) slot.
ktmom said:
I think you might be served by a factory reset. If course, that means you lose everything on the phone.
If that doesn't help, my knee jerk is the same, I would sideload the OTA.
Actually, I personally would unlock the bootloader and fastboot flash with the wipe to both slots. Or, sideload the OTA to one slot, them reboot to bootloader, if necessary, switch slots and sideload the OTA again. In theory, rebooting after sideling should switch slots so I would pay attention to where I start and where I am each step. OTAs, by design flash to the inactive (opposite) slot.
Click to expand...
Click to collapse
Factory reset is a good option.
I have used 68GB so far. What app or software do you recommend for backup and restore the contents ?
Have you done any factory reset on your phone without loosing any data?
How long would the reset would take with 68GB of data?
TY
IronRoo said:
As ktmom says, also I'd specifically like to know if it was after the Feb update this occurred do you also have TWRP installed as a couple of others do that may have the same issue, see
https://forum.xda-developers.com/essential-phone/help/booting-feb-security-update-t4045545
edit: see bornroyal comments on other thread, serms TWRP not compatible, but someone on reddit made a compatible version.
Click to expand...
Click to collapse
The person on Reddit only made a patched boot.img for magisk, twrp is still out of the question on the February patch
Tom23824 said:
hey!
Device is having power-up issues.
e.g., I press the power button then choose Restart option.
During power-up cycle, the phone always hangs. Device is stuck on the screen displaying Essential logo and the Powered by Android. ??
Any help, would be appreciated.
PS: Every time I am forced to hold the power and lower volume buttons to reset the power cycle.
Click to expand...
Click to collapse
Mine and my wife's phone does the same thing. Just be more patient and wait for 5 min and it will complete the reboot. This length startup started to happen a few months ago.
I saw it pop up on the stable channel. I waited a few days, checked here and saw nobody complaining so I went for it. Recovery saved it, so no big deal, but still killed about 20 min. 20.4 has been working fine for me.
similar result, updated and just made the phone crash at boot; restored and I guess no more updating for the meanwhile
21.3 still has the same crash.
tdusen said:
21.3 still has the same crash.
Click to expand...
Click to collapse
I confirm - crashed on boot. But I am not sure that the reason is Magisk itself, may be the Magisk Manager is the reason ....
21.0 works all after do not.
Bricked my V20 VS995 this morning trying to update to 21.4. Notification had been nagging me for a week and I finally gave in, now my device has a gray screen with very small text, and at the top it says "LGE Crash Handler: Crash on the LK!". I cannot get into TWRP, and a factory reset has no effect. Still no boot into Android.
I was just talking to my girlfriend yesterday about how it was getting time to upgrade. Careful what you wish for, I guess.
that's why I finally turned off the update notification.
Have you tried booting into recovery by the holding keys method?
Assuming you have TWRP installed
hold vol down and power.
when the LG appears, release power the press and release power (one time) while still holding vol down.
you boot to the factory reset screen. select Yes twice
that will boot into twrp
Same here, updated Magisk and bricked my V20 H910.
Then I've used TWRP to try to queue install the following zip :
1 - H910_20h_Oreo_full_rooted
2 - H910_v2.2-mk2000
3 - Magisk-v19.3
4 - Hide_warning-att
Back to Oreo setup, all good even if datas are lost. Then again I've updated Magisk (was not really sure it was because of that, should have read here first!) and same problem, the unfamous "Crash on the LK!". Magisk killed my phone, again.
So I was ready for another run (but the magisk update of course). Stupid me.
I know can't even acess the recovery tool, ok for the Down/Power then Power to get the first recovery prompt and then the confirmation but no TWRP but the crashed multi-colored messy pixel screen and boot again to Crash LK screen.
I have no clue of how to get out of here, guys any help is more than welcome!
Anyone install 23 yet?
I don't see 23 on the Beta channel, nor on the stable channel.
I have 22.0 installed and running fine.
Does anyone have 22.1 installed? Is it fine?
i had an app update waiting for me 23 installed fine on note 3 and on my v20