Black screen - Bricked - Xiaomi Mi A2 Lite Questions & Answers

Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.

zk_eu said:
Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.
Click to expand...
Click to collapse
That´s really strange... Will windows detect the phone when you connect it?
Maybe you´re in edl-mode. If yes, you could get out of it by pressing pwr for more then 10 seconds.
If that doesn´t help and you will not be alble to do anything (incl. going to fastboot) you can restore you phone by going to edl by usng the test point method. But thant will break your warranty - you have to open the phone...
If you want to do it you need to do the following.
1. Download latest fastboot rom and MiFlash
2. Install MiFlash, unpack fastboot rom and selct extracted folder in MIFlash.
3. Open your phone: https://www.youtube.com/watch?v=PmpHdqRUlDA
4. Remove the metal cover over the mainboard
5. Remove battery
6. short these both pins: https://www.youtube.com/watch?v=mhsRv42rsqI
7. connect your phone to pc (in device manager you should see "qualcomm qdloader 9008"
8. In MiFlash click on refresh (now you should see something with com-port)
9. On the lower right corner you can selct "clean all", "save user data" and "clean all and lock" - if you were on 10.0.3.0 before, you can select "save user data" if not, you have to wipe by selecting "clean all". Now click "flash"
I did this once and needed a few tries... It´s a bit tricky to connect both pins and then the phone to pc - after the 4th try I got it running.
I had the problem of locked bootloader and a not booting phone...

Hi!
Yes, Windows detects the device. I can see the phone in the device manager by the name Qualcomm HS-USB diagnostics 900E (COM10).
If I hold power on and volume up or down, I can hear via Windows sound that it gets reconnected. So there is some life still in it.
The device is also detectable by MiFlash tool. But unfortunately since I can't get into Fastboot, I can't flash it. I've been trying to flash it, but this is where I get (it just stays here no matter how long I leave the device):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know about the method you posted. I still have a year and a half warranty on the phone. So I will sent it on repair and see what they will say. Maybe the won't notice and I will be able to keep my warranty.

i am in the same situation right now, after try to update the twrp, what tool you use to open the phone?.

I think you can also use the deepflashcable for the same effect.

Related

[Q] Is my Gnex motherboard faulty?

Hi guys,
I can't flash any ROM/Kernel/whatever file via Bootloader/ODIN & Recovery. Worst still I can't access Recovery now.
My Nexus can goto Bootloader or ODIN mode but once i started to push files to it, it will just freeze. Please refer below for photos:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BEFORE
AFTER
My Gnex was on the latest Paranoid ROM and Franco kernel.
Timeline:
1. It just went into bootloop when I am just browsing the internet.
2. Went to Recovery to clear cache. (that's my mistake, should have waited longer for my device to boot :crying
3. Still bootloop.
4. Went to recovery to flash stock kernel as I suspect it's kernel fault.
5. Kernel flash failed as it the operation was aborted and restarted. Bootloop again.
6. Done battery pull and went to Recovery to Restore my backup Nandroid.
7. Flashing halfway and it frooze.
8. Can't access Recovery anymore.
9. Tried to restore stock rom using ODIN. Failed at NandWrite as the screen froze as the above image.
10. Tried WugfFresh to restore back to stock rom and failed again as the screen froze.
So guys, can i conclude that my motherboard is the culprit here?
Thanks in advance.
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
ual4720 said:
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
Click to expand...
Click to collapse
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
d3vils said:
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
Click to expand...
Click to collapse
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
cmaag said:
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
Click to expand...
Click to collapse
corrupt nand partition... that's an interesting theory... will explore on the solutions on the manual fastboot commands...
thanks!!

Another Firmware update issue.

Hey all,
Noobie question time! Did the firmware update (or so I think) and now I do have adb connection but not fastboot? or mounted sd card. (Did re-format and now it seems to be available). I messed something up along the way obviously, it looked very much finished after both adb and the phone were inactive for a minute or so.
Currently in what seems to be factory recovery?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^^^ Not working?
Android Recovery
HTC?htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam12161528
(up and down for opions)
rbt sys
rbt boot
apply from adb
apply from sd
wipe/factory reset
wipe cache
Also access to everything else works.
What's next guys? I need twp and Venom update. *** Sideload option available didn't want twrp, because of not having fastboot?
Also showing:FILE/mnt/media_rw/ext_sd/0PJAIMG.zip
File not found.
Thanks for all the help, I'd be useless with out you!
I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk
shivadow said:
I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Shivadow, do you have a link for that twrp I can't seem to find it.
Thanks for the info!
Update:
Got twrp 2.8 on. Won't take newer versions of venom, assuming they need 3.0.
I noticed that the error on the bottom of the device - 0PJAIMG.zip file not found on sd path is RUU related? If so should I try the ruu again as I might have a partial install??
0pjaimg is for flashing but in your case it'll do more damage than good.
You can get twrp 2.9.0.1 from the repo or various sites. Google is your friend.
Sent from my HTC One M9 using Tapatalk

Friend's Pixel stuck in bootloop, flash unsuccessful

My friend's unlocked Pixel got stuck in a bootloop about a week ago, and we're unable to get into Recovery Mode so we've been trying to flash it instead. I've used minimal adb and fastboot v1.4.3 and v1.3, and the latest and next to latest Marlin image files.. Currently on 1.3 and the latest image file, and the process gets stuck while trying to erase 'cache.'
screenshot of flash-all.bat:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be very appreciated. (I'm a total noob with these terms and tools btw. My realm is computers, not phones. :/ )
i think the problem is that you're using minimal adb and fastboot. v1.4.3 was updated in february 2018. the official platform tools from google have gone through several updates since then, the most recent being last month. i suggest trying again with the latest android platform tools and the latest marlin image.
the latest android platform tools can be downloaded from here.
altwu said:
i think the problem is that you're using minimal adb and fastboot. v1.4.3 was updated in february 2018. the official platform tools from google have gone through several updates since then, the most recent being last month. i suggest trying again with the latest android platform tools and the latest marlin image.
Click to expand...
Click to collapse
I already had the official tools but I never thought to use that.. So I tried that and we got somewhere. It looks like it was successful on this end, but the phone is still in a bootloop. Does that mean that this thing is a paperweight?
i wouldn't give up yet. it does look like the flash was successful and user data got wiped. did you see any error messages to indicate that something went wrong with the flash? you probably got a bunch of warnings about certain images not being available. those are normal.
if the flash went through with no errors, then the only other thing i can think of to try is to flash both slots. here's how:
get the latest platform tools from here.
flash the factory image like normal, with flash-all.bat.
wait for the phone to reboot and finish the install.
reboot to the bootloader.
look for the line that says "Boot-slot". it will be either a or b.
change to the other slot with this command.
Code:
fastboot --set-active=a or fastboot --set-active=b
reboot the bootloader
Code:
fastboot reboot-bootloader
run flash-all.bat to flash the factory image.
same exact thing as last time.. So I run flash-all.bat and it finishes in 134 seconds, then immediately after, the phone reboots. But it gets to the google splash image and then it'll power off again, and reboot again. It only stays on the google image for a few seconds. Nothing else ever happens.
So both slots are now flashed and the problem still exists.
Dallas Roberts said:
same exact thing as last time.. So I run flash-all.bat and it finishes in 134 seconds, then immediately after, the phone reboots. But it gets to the google splash image and then it'll power off again, and reboot again. It only stays on the google image for a few seconds. Nothing else ever happens.
So both slots are now flashed and the problem still exists.
Click to expand...
Click to collapse
Try factory reset in recovery if you haven't already..........ya never know.
crackerjack1957 said:
Try factory reset in recovery if you haven't already..........ya never know.
Click to expand...
Click to collapse
I thought I put this in the original post but we can't access recovery mode, it just reboots like normal.
Dallas Roberts said:
I thought I put this in the original post but we can't access recovery mode, it just reboots like normal.
Click to expand...
Click to collapse
I seen that but if flash was successful I thought maybe you would have recovery..
crackerjack1957 said:
I seen that but if flash was successful I thought maybe you would have recovery..
Click to expand...
Click to collapse
I tried it again after your message just in case it might be working again, and I got nothing. So maybe the problem is hardware-related?
Dallas Roberts said:
I tried it again after your message just in case it might be working again, and I got nothing. So maybe the problem is hardware-related?
Click to expand...
Click to collapse
Probably hardware
Just to make sure you know how to get to recovery & navigate after no command image
https://www.youtube.com/watch?v=P1RGEle3qN0

Flash protocol/files because of bootloop : soft brick :(

What I've got:
T800 (wifi) updated by mfg. NOT rooted, all is stock (new in 2015 and I've never messed with the OS) and last version was marshmallow 6.0.1 (def marshmallow but version is strictly from memory).
Problem:
Couple of days ago, tab went into endless boot. It would show the android screen then samsung screen then it would load and all looked ok. This would last for maybe 30 seconds then rebooted into the android screen then samsung screen etc. : endless loop.
What I did:
Did some research and booted into recovery mode. Only cleared the cache then rebooted/or shutdown several times. Same looping. Tried cache clear 3-4x with no success. Once I got into the desktop, it lasted ~30 seconds and then booted me out again.
Alright, I bit the bullet and did a factory reset. Well, now it only gives me the android screen and then the samsung screen. Then cycles over again. I cannot get to the desktop anymore, at all.
Found a thread regarding looping but then the threads about upgrading to nougat by @Schischu --> https://forum.xda-developers.com/galaxy-tab-s/development/rom-android-7-nougat-t3449078 then part 2 https://forum.xda-developers.com/galaxy-tab-s/development/rom-t3498956 and then another one by someone else in regards to upgrading past 7.0 (which I'm not ready to do).
The instructions as posted
INSTALLATION INSTRUCTIONS
Cleaning System
This step is only necessary on the initial installation.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Install this ROM
Go into Install
Flash aosp-XXX.zip
On initial installation it is necessary to Reboot to Recovery. Don't skip this step!
(E:unknown command [log] messages can be ignored.)
Install Google Apps and SuperSU
Go into Install
Flash GAPPS.zip
Flash SuperSU.zip
Reboot to System
Click to expand...
Click to collapse
I've got a few questions as I am a TOTAL newb at this.
1)I've got the following files:
a) aosp_chagallwifi-userdebug-20161116.zip
b) open_gapps-arm-7.0-nano-20191002.zip
c) SuperSU-v2.82-20170528234214-TEST-1.zip
d)twrp_3.0.3-1_sm-t800_10217.tar
Are these the correct files? Do I need any more?
2)when I start the process, do I need to put the ZIP file on an SD card then insert that in the tab?
OR do I unzip the file and put that on the SD card?
OR can I just leave them in a folder (on PC desktop) and access them from there?
3)do I put ALL those files at the same time on the SD card or are they accessed one at a time?
Because I can get the android/samsung splash screen I assume I've still got the correct (ie 6.0) bootloader in place. Correct?
If thats true, then again (q.1): am I ready to start the process?
I figure I should do this to get nougat rather than going through the same procedure to just re-load marshmallow.
Any thing else I should know or have missed?
First some pessimism: when a factory reset doesn't work, it's very likely to be a hardware problem.
But let's assume flashing a new rom can do the trick.
I haven't played around with this tablet, or even another Samsung device, so I'm no expert either, but I think I can guide you a bit.
You'll have to start by installing a custom recovery like TWRP. The one you've found is very old, I would assume that you can find a newer one.
People talk about using a PC program called Odin for flashing recovery, maybe you can search for that. Or read here:
https://wiki.lineageos.org/devices/chagallwifi/install
where they use an equivalent program called Heimdall.
Thanks for the info and link.
Started to look at odin but not having any experience or sure of the files needed, I thought I'd wait and see who might respond.
Interesting times. Was able to find the correct file for odin to use. Appears to be successful but I don't know.
This screen shot is what I got after trying to install gapps.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says chagall BUT that was b4 I was successful with odin. The error message is the same for Gapps flash. Also, same
error message for SUPERSU
The previously posted instruction said to reboot to recovery. I can only do that if I power down then back to recovery. I do have
an option "reboot to bootloader". Is that the same??
I should mention that I tried the AOSP file (first post) and odin wouldn't accept it. Per instructions I found for odin, the file should end .tar.md5 which I did find
T800XXU1CPK2.tar.md5
Both gave me the same error message though.
+++++++++++++++
I can't install twrp on the tab as its not accepting input so I'm installing android studio on my PC and trying that way.
Well, it must be something else. Although I couldnt load the nougat version with odin, I successfully loaded marshmallow ("PASS" in odin).
https://samfrew.com/download/Galaxy__Tab__S__10.5__-WiFi-__/3klk/XAC/T800XXS1CRI5/T800XAC1CRI5/
BUT I still have the endless boot loop. Plugging in the power cord shuts it off/puts into charging mode.
Do you think it's still a hardware issue?
If you've got an SD card installed, try removing that.
But really, you've reached the end of my knowledge, so let's hope someone else chips in.

Flashed corrupted boot image and now can't can't boot into bootloader or recovery

Hi all.
Did a stupid thing.
I downloaded firmware file for my Galaxy S20 Ultra 5G (SM-G988B) Exynos as an MD5 file and extracted the file which came out as a .img file instead of .lz4 (which I overlooked until the damage was done!).
So not noticing the file was the wrong type, I used 7-Zip to tar it, copied it to my phone's SD card, then patched it with latest Magisk manager app. After this, I copied it back to my laptop and flashed this file using Odin.
Result: Phone goes to insecure boot warning screen but of course here it goes wrong:
It won't proceed to booting up
Power+volume up key combination or power alone do nothing no matter how long you hold them in
It boots to to same insecure boot warning screen if you use either power+volume down, or power+volume down+volume up key combination with cable unplugged. With cable plugged in it restarts to a charging icon, which promptly freezes, and stays on the screen even if you unplug the cable.
I have managed to get it into stock recovery by holding power+volume up+volume down randomly once in a while (usually it goes to insecure boot warning screen as usual), but if I select Reboot to bootloader, it does not manage to open download mode, and hangs on red text that says "entering fastboot mode"
QUESTION: If I can get it back into recovery, is there a way to re-flash stock firmware without download mode on this device using ADB (or any other method)?
Or is my phone a brick for good?
FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!
jesterpaul said:
FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!
Click to expand...
Click to collapse
will that method work on my note10+?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources