I'm using Redmi Note 7. Never had such problem while using my custom ROM. (crDroid 6, Android 10, latest)
I changed my screen resolution to a lower one through this app, used it for a while, restarted and now I see a black screen after startup animation, but system is running, I just can't see or interact anyhow.
I cleared the cashe via Orange Fox Recovery,
I tried to change the resolution back via:
[/B]adb shell wm size 1080x1920[B]
Also tried this command to reboot into safe mode:
adb reboot safe-mode
It didn't work as well, so I tried this:
[/B]adb shell setprop persist.sys.safemode 1 && adb reboot[B]
I tried to connect to my phone via Mirroid (have been using it for a while), to share it's screen with my PC, didn't help, I saw a black screen.
What should I do?
Related
Hi there,
I was able to boot the Q fine. I enabled USB debugging, used ADB to reboot into bootloader ran the oem unlock/unlock_accept command successfully. I rebooted and flashed CWM recovery v 6.0.2.7 steelhead. Once this was done, I rebooted into recovery and used adb to push the latest stable release of CM 10.1 to the sdcard. I then flashed this via CWM recovery, and performed a factory reset.
Now that I have rebooted system, it just sits on the cyanogenmod loading splash screen. I left it for over 2 hours at first, then I power cycled device and left it over night. I attempted to go back into recovery, but covering the LED on the top does not seem to result it anything. I power cycled the Q again, and held my hand over the LED from boot to attempt to get into recovery but I am not able to. I also powered device up and waited until the ring LED began to light up, then covered the top LED to see if this allowed to boot into recovery but still no change.
I let the Q boot up once more, and after sitting on the splash screen loading for about 10 minutes, I connected the device back to my PC, and found that adb can see the device. However now that it is running CM 10.1, adb security is enabled and my PC is unauthorized. I am unsure how to proceed at this point. Do I need to try a different PC than the one that was originally used to flash to see if it works (I doubt it will as that wont be authorized either, right?) or am I doing something wrong while trying to get into recovery?
If anyone can shed some light, or assist even getting into recovery, or providing a way to get around the adb authority requirement it would be greatly appreciated.
Ok scratch the above.. I managed to tap on the top LED about 50 times during boot, at which point it turned to red solid LED ring and loaded enough for me to get in using fastboot. I flashed the recovery again, ran a factory reset/wipe cache on it twice, and rebooted. it is now sitting at the home screen ready for me to purchase an OTG USB cable tomorrow and set up cyanogen mod!
I made my own custom boot animation. I used an existing boot animation structure. Difference was mine used *.png files instead of *.jpg files. Which I thought all boot animations were supposed to be png. The other difference is the fps, I changed fps from 24 to 4
I renamed /system/media/bootanimation.zip to /system/media/bootanimation.bak
Copied my custom boot animation to /system/media/
Rebooted..
Google appears with the small unlocked icon for a few seconds, then disappears to blank screen, which I'm assuming is my boot animation. It never shows, never boots, just sits on blank screen.
Tried turning it off, it auto reboots, never powers off. If I hold all three buttons it will reboot and pull up the boot loader. I try going into recovery, google appears with unlocked icon, and never goes black never loads recovery.
This nexus 7 is running paranoid Android 4 beta1 or 3.99 rc2 can't remember..
Twrp 2.2.2.0 for recovery..
As of now I'm letting it show the black screen waiting for battery to die in hopes that I can charge it, without it powering on, then hold all three buttons, load boot loader, then load recovery and it work.. But I don't think this will help..
I've tried a bit of googling for nexus 7 bad boot animation, and found nothing useful.. Hope someone can help, thanks!
Update....
The nexus 7 is not bricked.. When it loads black screen it is loading my boot animation, and obviously fails, the tablet dies finish booting, even though I didn't think it was.. If I turn tablet horizontal I can see the right 2-3 inches appear, apps, lock screen, etc.. But rest of screen is still black, but if I touch other part of screen while in app drawer, it does open that app.
So in vertical mode I have a black screen overlay.. In horizontal I have only about a 75 percent black overlay that is left justified.
I'm hoping I have adb enabled so I can go in and delete the custom boot animation I made and all will be well.. Or at least see if I can navigate only seeing the right part of screen so I can enable adb or even delete the boot animation itself..
Never heard of this issue, even if you put in an incompatible bootanimation and forget to change permissions to it (which I don't believe you did) your tablet should still boot fine and perform just fine just get a blank screen during boot up
Is it possible you did something else? As this issue seems yo be more than just a bootanimation
If I were you right now I would attempt to flash or at least boot a new recovery through fastboot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Or just
fastboot boot nameofrecovery.img
In this recovery adb should work fine
adb pull /system/media/bootanimation.bak /location/on/pc
Now change it back to bootanimation.zip
adb push /location/on/pc/bootanimation.zip /system/media/bootanimation.zip
Now either fix permissions in recovery or chmod with adb, also may need to mount system first
And for future reference always make a backup first
Sent from my Nexus 7 using XDA Premium 4 mobile app
I did nothing else, the tablet actually boots, but all black screen in vertical mode.. In horizontal mode you can see maybe 25% of the screen, the rest is black, but still functions..
If I adb in from Linux, move original boot animation back, reboot, works fine.. I think it's something to do with my zip file or something, I've even took original stock boot animation and edited its images, created a zip, installed, reboot, same thing..
Adb in, move original, reboot, good to go again..
Today I'm going to try unzipping, and just rezip, install without changing any files and see what happens..
If you want upload me a copy of original along with a copy of the new one you made and I'll have a go at it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Just got a new phone from warranty to replace old one with digitizer problems.
So basically I rooted and then I installed TWRP via AutoRec, then was in TWRP and wanted to upgrade TWRP to the blastorgator thermal helping version and put recovery.img on /sdcard/ and went to the end of step 3 on a guide for flashing twrp on phonearena (stupid I know), I can probably PM guide if requested but can't post in this thread due to postcount.
After going into fastboot, the phone would go to a black screen while still backlit, and the notification LED's would alternate between green and blue. Couldn't go to regular OS at this point, but while in adb shell I could run adb reboot recovery and go back to TWRP. I figured maybe I did something wrong somehow with system and wiped all the stuff available in TWRP (dalvik, system, sdcard, cache) and then installed Cloudy G2 3.3 from TWRP's install menu, the little gui to install came up and it ran the commands and then prompted to reboot iirc, and then it went to a black screen, no notification LEDs on.
If I hold down power and lower volume, LG splash screen comes on and goes back to the normal black screen with backlight.
If I connect the phone to usb, windows gets spammed with a ton of "You must partition this drive to do anything with it G:/" all the way through the alphabet. adb devices is blank, commands don't run.
At this point I rebooted back into TWRP and formatted the phone, and then pushed Cloudy.zip back onto it and tried to install again. Same **** when it reboots after installation (with the black backlit screen and the disk formatting in windows).
So thats a no-dice. Can still reliably get into TWRP however.
Is there anything I can do?
I know about the no recovery mode fix, but I don't have the binned version of my rom. I have an identical phone with an identical rom (ie the digitizer problem one), could I in theory pull the binned version off that phone and use it to fix this one? Or something else I can do?
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
Yesterday I dropped my phone, cracking the screen protector on the right side, a little lower than the middle of the screen. The screen worked fine at the time.
A few hours later I noticed that the bottom of the screen was not working properly. Upon removing the screen protector I saw a barely visible crack, running upwards along the right side of the screen and bending left towards the top.
At this time I connected the phone to my PC and with some fiddling managed to authorize adb, clicking the checkbox to always trust this device. (I had to open an app that enabled screen rotation, so I could get the checkbox and "ok" button on the working part of the screen. I downloaded scrcpy and verified that it worked. I also made an additional backup of my images, although they should be backed up to my NAS.
This morning the screen is almost completely gone. I tried to connect to adb because I remembered I have some recorded calls I want to keep, but I could not get a connection. While trying to accept the connection I inadvertently rebooted the phone to TWRP.
While TWRP is starting I have adb access. I can sort of make out the top left of the TWRP logo on the phone. After 90 seconds the adb connection drops. at the same time the logo disappears and is replaced with some buttons I can't read. some parts of the screen give a haptic feedback when touched. I can disable/enable the screen using the power button, but that's it.
$ adb reboot
$ adb reboot bootloader
$ adb reboot system
$ adb reboot safe mode #(probably not right?)
withing 90 seconds after boot all cause the phone to reboot to recovery
I'm hoping to achieve the following from best, to worst solution:
* use scrcpy while I set up my new phone
* boot to system, so I can transfer files using USB
* make the adb connection stable, to recover files
* copy files directly from the SDcard to Windows, macOS, or linux. (SDcard is formatted as internal)
* copy files during the 90 second window
The last one I can probably manage, but will be tedious to do manually, some automation would be nice.
I'm thinking about a script that I can start from adb, that will move items to a usb otg device. However I can only plug in the usb otg after I disconnect the adb usb cable.
For completeness:
It's a j5xnlte, with LineageOS 17 from here: https://forum.xda-developers.com/t/...al-stable-lineageos-17-1-for-j5-2016.4070629/
I have a 64GB micro SD card formatted as internal storage.
The phone is not encrypted.
The phone is rooted using magisk
The images I used to flash twrp, lineage, magisk and gapps are still on the phone. I could try reflashing them, but I don't know how to do that withing the 90s adb window.
I hope there is something that can be done. If not, thanks for helping this phone last 6 years already.