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
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.
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
Press vol+ vol- + power at the same time until phone vibrates
Sent from Mi A1 with Tapatalk Pro
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I also had this issue I think it is because of any xposed modules or magisk modules.
When I flashed xposed uninstaller, the phone revived
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I have the same problem, my Mi A1 dont boot and i cant open fastboot mode (and screen dont turn on when charging), how you solved it?
Stuck on black screen
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
ideepeshtiwari said:
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
Click to expand...
Click to collapse
im also having the same issue. while flashing aex v6.2 on my mi a1
help me out from the same problem
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
khadar709 said:
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
Click to expand...
Click to collapse
Flash the previous rom and everything will be back to normal.
Shilldas said:
Flash the previous rom and everything will be back to normal.
Click to expand...
Click to collapse
I am not able to do that I can't go to twrp mode here also same black black screen.I can go to fastboot mode but I am not enabled usb debugging mode and system is not recognising mobile.
Help me how can I solve this..
Thanks in advance. ?
Install 'scrcpy' in your PC. Try to flash twrp from PC using fastboot and adb method. (I hope fastboot shows up on your phone) if u can boot to twrp via PC then go ahead and install any other rom. If u can't then connect your phone to PC and open scrcpy.exe here you can control your screen. (Most custom roms come with usb debugging enabled, if not try " AEX V.6.1 rom)
Usb debugging is compulsory. Thanks a lot for the information I will try this.
So i had this exact same issue. It was booting to twrp but screen was just blank.
i was trying to root the devive so i flashed the zip file by following command through adb
adb shell twrp install /sdcard/Magisk-v23.0.zip
it flashed the magisk and it was done. Similarly you can flash any zip file. If zip file is not copied to internal memory you can copy it using following command
adb push Magisk-v23.0.zip /sdcard/
I hope it helps someone in need.
Thanks.
Hi similar problem. Phone was locked in bootloop. I use reset pin and flash latest fw, flash successful in 220sec. Then screen stays black. Holding any combination will power up phone with black screen... wonder if it burn resistor or it is a flash issue. Trying to reflash again, however it stays 1000sec and still flashing.
Hi have mine FIXED.
Tried again to flash with android 9. Not able to finish flash in 4hrs. Then disconnect. Screen show battery 100%, then again only black screen but powered. Also 3 buttons are lighting. So I start pushing them and the screen, got some feedback and sound from touching the screen. Then the phone restart, screen ON. Show the normal white screen and ENCRYPTING storage screen that should come after flash. Then again reboot itself and start installing android (just taking a lot of time). Now all work on android 9, not giving option for OEM update to android 10, however afraid to flash again... good enough for my son (either way will break it in an year).
p.s
Im Samsung S class user for 10 years, so it is quite unfriendly phone... (need debugging on to connect to PC, for file transfer )
At last I found a way to run TWRP on tissot correctly without black screen.
Just install oreo 3.2.1-2 on Mi A1 (tissot).
This file (recovery-3.2.1-2-oreo.img) is working well.
Download it from this site:
https://androidfilehost.com/?fid=818070582850498337
Reference:
https://forum.xda-developers.com/t/...2-1-2-oreo-touch-recovery-2018-03-06.3688472/
Download Android 13.00 unofficial ROM for Mi A1 and install it easily by TWRP oreo 3.2.1-2:
https://sourceforge.net/projects/lafactorial-tissot/files/
Good luck,
Sed
Releases ยท zignas/twrp_device_xiaomi_tissot_treble
android 9.0 Device tree for TWRP 3.5.2 with Tissot manager - zignas/twrp_device_xiaomi_tissot_treble
github.com
also working fiine
So I updated my rooted 6t to Android 10 using Magisk, and everything went as expected prior to rebooting. I hit uninstall and restored images via Magisk, downloaded and installed the Android 10 update package to the inactive slot, downloaded the TWRP A/B partition module then finally installed Magisk to the inactive slot as well. Finally, from there I rebooted and it seemed to boot normally, hung a bit longer on the animation than normal but no more than 30 second or so.. it then skipped the lock screen and went straight to my wallpaper (the same one i has set, not default) BUT the system doesn't start. No icons. Can't pull up the app drawer, can't pull down the notification menu. No notification bar... Nothing.
The only thing I can do is restart the phone by holding PWR button but that just brings me right back to the same deal. I tried fastboot>TWRP recovery and was able to determine that all the system data is in fact present anyway but rebooting from TWRP also lead to the same situation.
I'm asking for advice BC the last time I messed around without knowing fully what I was doing, I hard bricked it. I'm using Blu_Spark TWRP if that makes any difference at all...
It's possible that I just need to wait longer, I read a number of reports of pixel users needing to wait hours after OTA updates but they were stock on the boot logo/animation. I'm beyond that point, only it skips the lock screen, goes straight to my wallpaper and that's it. I can't do anything at all from there.
PLEASE HELP?
Thanks!
QNE
Use MSM tool.
Download MSM tool. Unzip it on PC desktop. ConnectUSB typC cable to PC. Shutdown your OnePlus 6. Open msm download too. Click start. Press volume up and dn key simultaneously(don't touch power button). Now connect cable to phone. Progress bar of MSM download too will be active. Let it completed. Phone will boot to os. Now upgrade to Android 10. That's it.
I ended up factory resetting prior to your response, but thanks just the same. Fortunately, I didn't lose root which was my main concern anyway so no harm done. Thanks again!
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
DaveyBoy2002 said:
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
Click to expand...
Click to collapse
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Haven't tried a android 9, I'm back at work and used 4gb of data screwing around yesterday trying to get things fixed so I gotta go easy today ?
moshe_lm said:
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Click to expand...
Click to collapse
Yea I've had the same results as well.
Try Havoc and PE from these links. They are phhusson based and work with some bugs but at least you can boot up after the third time
https://sourceforge.net/projects/expressluke-gsis/files/
moshe_lm said:
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Click to expand...
Click to collapse
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
DaveyBoy2002 said:
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
Click to expand...
Click to collapse
It is working after second restart ? or one time ?
moshe_lm said:
It is working after second restart ? or one time ?
Click to expand...
Click to collapse
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
DaveyBoy2002 said:
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
Click to expand...
Click to collapse
volume down isn't go to fastboot mode ?
moshe_lm said:
volume down isn't go to fastboot mode ?
Click to expand...
Click to collapse
Not if you let go when you see the screen turn off, then it's just a dirty restart I guess?
In my case, it only happens when you use the Encrypt password to start the device.
So I suggest skipping the encrypt part on startup setting and the problem should gone.
*Sorry for my bad English.
In my case, Don't use the "Secure start-up" thing when you set up your phone in Android 10.
Nor It will mess and cause a black screen on your device.
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube