I Bricked my phone, Please Help - Redmi Note 8 Questions & Answers

Hello, Friends from XDA
So long story short, I was trying to fix my Redmi Note 8's charging issue (slow charging and charges only when booted to OS). Then I decided to install a new rom from twrp (current was MIUI China, trying to install Xiaomi .eu) hoping that it might solve the issue but dumb me accidentally wiped the "system" partition during the wiping proccess. Now I am greeted with "The system has been destroyed" message". Cannot boot to twrp anymore. I really regretted doing that.
P.S. tried fastboot, doesn't work, ask for more
Anyone, please help. All suggestions are welcome.

When flashing a ROM you have wipe the system as well. This will fix that issue you are having(flash this after flashing ROM. This is a VBmeta.img):
https://mega.nz/#!r54FzQIZ!LgD3zSOBm1gOIzY6w8r8l-A8GChgWk_Z7HIN6y_bVLc
Use this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I suggest that you join the Telegram group as that's where I got this file from. Plus you will get help much faster.

@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
{
"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"
}

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
That is alarming, so your device can boot into fastboot mode but won't be recognized by the PC?
Try using it on another PC because if you can't use fastboot or Recovery, the only thing that will save you is the EDL mode, and I have heard people say that the only way to access that is with an authorized account (which only xiaomi service centers have) or you will have to open the back of your phone and short circuit the EDL Chip.

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy

Zulfi said:
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy
Click to expand...
Click to collapse
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized

Judroidz said:
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized
Click to expand...
Click to collapse
In SS you can see the cover on device clearly

Zulfi said:
In SS you can see the cover on device clearly
Click to expand...
Click to collapse
Oh sorry I didn't see that. OP did you get anywhere with fixing your device

Judroidz said:
Oh sorry I didn't see that. OP did you get anywhere with fixing your device
Click to expand...
Click to collapse
Well bro, I'm still trying. Going to give the EDL mode a try and as you can probably tell, I am a newbie.
Any precautions, maybe tips that I should know about?
here's what I've gathered
1. Remove back cover
2. Find the edl testing points
3. Short circuit the testing points
4. Plug the device to pc (asap after shorting)
5. Flash using MiFlash (Hopefully recognizes the device)

So, it seems like you need an Authorized Account for flashing in EDL. I was hoping to find a diy solution but things get complicated. Well, I'm just going to send the device to a trusted local Xiaomi repair center and get it fixed (they have authorized accounts) and also solve the charging issue. Again, Thanks to everyone and XDA.
P e a c e

Related

[Boot verification failure] Broken dl mode, broken recovery, won't boot

I tried rooting my D855 with this method, however it caused my phone to go into a boot loop, so I pulled the battery and tried turning it on, now I get a "boot verification failure"
{
"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"
}
This error appears when you try boot, enter download mode, or you try factory reset, after the error the screen turns back and the notification light flashes blue and red.
I can't find any way around this, please help!
**UPDATE**
The only time I could get my phone turned on with something on the screen was with the battery out and connected to the PC, however the phone shows up as Unkown USB Device (Device Descriptor Request Failed)
It happen to me. Still waiting for help or another tutorial...
I had similar one but I could still go to download mode by plugging cable when off and golding volume up. If that doesn't work I don't really see any way to unbrick since you're unable to push or execute any files to it. Maybe some way to hard reset it, probably the only hope.
un4tural said:
I had similar one but I could still go to download mode by plugging cable when off and golding volume up. If that doesn't work I don't really see any way to unbrick since you're unable to push or execute any files to it. Maybe some way to hard reset it, probably the only hope.
Click to expand...
Click to collapse
Yes, if we could entered download mode we can pushed the kdz file or tot file.
This problem won't let me stay on download mode, it straight goes to black screen and blinking led.
And now, ended with "relink usb hs qloader 9008" on device manager.
Already try the method on xda with no luck, now i sent my phone to friends who has jtag.
Hope it will boot..
wiwid.colgate said:
Yes, if we could entered download mode we can pushed the kdz file or tot file.
This problem won't let me stay on download mode, it straight goes to black screen and blinking led.
And now, ended with "relink usb hs qloader 9008" on device manager.
Already try the method on xda with no luck, now i sent my phone to friends who has jtag.
Hope it will boot..
Click to expand...
Click to collapse
Since I don't have a JTAG available near me I may have to try the hard brick fix by shorting the pins.
ceeenek said:
Since I don't have a JTAG available near me I may have to try the hard brick fix by shorting the pins.
Click to expand...
Click to collapse
Shortwire? It succeed??
Sol
Sent from my Mi 4i using Tapatalk
wiwid.colgate said:
Shortwire? It succeed??
Sol
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
I went with the shortwire method and the phone is now fixed and running MM.
ceeenek said:
I went with the shortwire method and the phone is now fixed and running MM.
Click to expand...
Click to collapse
Finally.
Mine still won't boot up.
Pls check your inbox, i've sent you a PM.
Sent from my Mi 4i using Tapatalk
Finally, alive again... Thanks @ceeenek
Sent from my Mi 4i using Tapatalk
Facing the same problem...
Tried to use LGUP to reflash but in order to do so it will try to reboot the phone, which will cause it to be stuck in the red/blue LED.
I only have access to download mode, how did you solve this?
Short wire, boarddiag, and then lg flash tools
Sent from my LG-D855 using Tapatalk

[STOCK ROM] [QFIL] [GUIDE] Stock CyanogenOS 13.1 for QFIL + Unbrick from 900E/9008

Hey XDA!
I found somewhere in web stock rom for QFIL, that you can flash when your phone is hard bricked (like mine was) or when you want to remove Add-X for free. Here are the downloads:
Qualcomm 64Bit drivers
Full Qualcomm flashing suite
QFIL image
My mirror of QFIL image (use when AndroidFileHost is slow for you)
Here are the steps to flash it:
1. If your phone is in 900E mode and you can't reboot to 9008, get a spare USB type C cable or microUSB to USB-C adapter.
1a. If your phone can boot into 9008 mode without problems by holding all 3 buttons, go to step 5.
2. Now you must cut your cable like this (image credit: [email protected] from MIUI forums)
{
"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"
}
3. Burn plastic on green and black cable
Something like that:
4. Now when your phone is fully turned off (you can get back cover off and disconnect battery), connect cable to your pc, short green and black cables together and connect it to your phone. After about 10 seconds separate the wires. Now your phone will boot into 9008 (aka EDL) mode. If you will get Unrecognized USB device prompt, connect battery when phone is turned on into 9008, detach EDL cable and connect normal cable.
5. Launch QFIL and set it like that:
6. Click "Download" and wait until finish. If QFIL will error with "system.img/cache.img/userdata.img not found" create empty files named "system.img", "userdata.img" and "cache.img" in stock rom folder.
7. When QFIL will finish flashing, hold power button in your Swift 2. It should boot to system now. If not, try to flash TWRP/Stock rom via fastboot, doing factory reset in Cyanogen Recovery or "fastboot format userdata".
Credits:
Me
Mike's Tech Life from http://mikestechlife.blogspot.com that posted stock QFIL rom, Add-X removal tutorial (http://mikestechlife.blogspot.com/2018/01/removing-add-x-from-wileyfox-swift-2-2.html) and QFIL Screenshots
[email protected] from MIUI Forums EDL cable images
​
I have long written the exact same guide. What is yours for?
JavaVOBIS said:
I have long written the exact same guide. What is yours for?
Click to expand...
Click to collapse
I see your point about duplicate but I guess you could say @puszekkkkk added photos and info on kicking into 9008 ...your guide was the inspiration or first but both guides are useful to people ...hopefully i won't need either but neat trick with spare usb to get into qfil mode
This destroyed my computer :'-(
I'm sad/frustrated to report that I attempted to follow this guide and completely destroyed my desktop computer in the process! ? I made the cable exactly as instructed and made sure everything was carefully wired with nothing touching anything it wasn't supposed to. I tried repeatedly to get my ZTE device to boot into EDL mode but it simply would not. And then, when I was trying once again, holding the green and black wires together for a few seconds, I suddenly noticed an electrical burning smell. Looking at my beloved little mini-desktop PC, I noticed a very bright orange-yellow piercing light coming from within and then realized this was a flame!! ? I quickly unplugged the PC and ripped the case off, and then blew out the small flame that had started to burn a specific chip on my motherboard. I think this chip must have something to do with USB-port power supply/support. It's a very specific chip and not one I can find online to purchase to repair/re-solder myself. My device is four years old now and is unfortunately out of warranty. I called the tech support center for my device anyway (ASUS) to see if they could do anything, and also wanted to inform them that their product had caught on fire, but they just took my information and said they were sorry but that they couldn't help me with this at all.
So now I am without my main desktop PC. ???
And my stupid ZTE device is still a useless paperweight... ?
richaardvark said:
I'm sad/frustrated to report that I attempted to follow this gu ?
... Homemade cables are a bad way to enter edl
Use fastboot :
fastboot oem edl
Using test point:
Search on YouTube for a video on how to open your phone and "shorting" two contacts to enter edl ( this is the method used by technicians and manufacturers)
Click to expand...
Click to collapse

The current image(boot/recovery) have been destroyed and can not boot.

Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
{
"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"
}
Then I faced a similar problem described in this topic https://forum.xda-developers.com/re...-3-pro-boot-recovery-destroyed-t3938481/page3
When you turn on the phone an error pops up for 20 seconds and then phone reboots and everything goes in a circle.
If you press the power button once, the reboot process stops and the phone turns off.
I tried to enter fastboot mode by pressing the power + volume button -
But I didn't succeed.
Can you tell me what I'm doing wrong ?
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
kkffiirr said:
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately due to this error fastboot does not load.
If you can tell me how I can flash the phone I will be very grateful.
I would not like to contact an unofficial service...
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
kkffiirr said:
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
Click to expand...
Click to collapse
Before lock, I installed TWRP, but idk if it's still there.
UMF cable will help me ?
Me i too i got same your problem i bricked my realme x2 i still didnt find the solution to flash it again
Maybe contact service center
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medusa Box; they seem to have underground connections with manufactors, they may provide a solution too.
EDIT. Thanks to the clarification from @T1MOXA, you can enter EDL mode by holding VolUp and VolDown and plugging the switched off phone to a computer.
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
yakovpol said:
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medisa Box; they seem to have underground connections with manufactors, they may provide a solution too.
Click to expand...
Click to collapse
I've tried this option before, but it led me to the same error screen.
I turned off the phone with a single press of the power button, then pressed all the buttons at the same time.
razu031 said:
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
Click to expand...
Click to collapse
I just got the same error.
When you connect the cable, the phone boots with the same error.
narshi shukla said:
Maybe contact service center
Click to expand...
Click to collapse
Unofficial ?
They too bad in my country.
They can easily make it worse.
I can buy a UMF cable, but whether it will help me I do not know.
What do you think ?
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
T1MOXA said:
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
Click to expand...
Click to collapse
Most phones will be able to flash in this mode using qfil tool,
But first you need to find necessary firmware, idk if stock rom downloaded from official site will work or not, maybe fastboot one will work.
This mode is called emergency download mode (edl).
But pls do a lil research as its a newly launched device and you can easily mess it up.
BTW exact same error(boot recovery destroyed) is common error on realme Phones and it can be fixed by flashing vbmeta.img using fastboot.
See attached image for reference only
The 1kb vbmeta is modified to bypass boot verification.
Idk if such vbmeta is available for x2.
If not then flashing stock vbmeta might work.
T1MOXA said:
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
Click to expand...
Click to collapse
I have the same problem. On 4pda there is a firmware for MsmDownload Tool and the tool itself, but it requires a username and password. Are there alternative options to restore your phone?
Problem: The current image have been destroyed and can not boot
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Iamsanthoshravi said:
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Click to expand...
Click to collapse
Look friend i had the same problem and i fix it u have to download the firmware RMX1991 not ozp file then u have to buy the password of the firmware there are sone website they ask you to install teamviewer because thet gonna flash your phone online ok friend i did as i mentioned and i fixed so there is no other way to fix it i cant put the link of firmwares because last time xda warned me
I got same
Hey bro can you fix your phone?
Today I experience same.
What can I do now?

Unlocked/locked LineageOS Redmi Note 8 - "The system has been destroyed"

Hello everyone,
I'm new here and I'm looking forward to reading your answers about my problem.
In 2018, I successfully installed LineageOS 17.1 in an unlocked Redmi Note 8. But I have accidentally locked it again using the terminal line "fastboot oem lock".
The fastboot mode is still available but I can't flash anything with fastboot or Xiaomi MiFlash tool (snapshot 1).
- MiFlash : error: Writing "xbl" FAILED (remote: 'Flashing is not allowed in Lock State').
{
"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"
}
So I tried to unlock it again using Xiaomi Unlock tool (following this tutorial) but it doesn't work (snapshot 2). I can't get access and modify the phone Settings.
- Mi Unlock Tool: "Please add your account in MIUI's settings".
Do you have any clue to fix this problem?
Thanks in advance !
You have to send your phone into EDL mode, but you might need authorization. Im not sure.
Also try fastboot oem unlock
Probably wont work but hey why not?
Boot Redmi Note 8 Into EDL 9008 Mode:​
Power off the device if possible.
Open back cover of dead Redmi Note 8 . [You may do Google to tear down Redmi Note 8 at home]
[Be careful at the time of removing back cover of the device and make sure you are not going to damage any hardware of the device]
Once you are able to remove back cover, disconnect the battery connector first. Battery not required for EDL mode.
Now remove the black tape to visible the edl points of .
IMPORTANT: Most of the other Xiaomi phone’s edl mode points are visible but inRedmi Go it comes in hidden mode. Reasons are not disclosed by Xiaomi. But you can visible these test points by removing the black tape. After removing the black tape you can see two test points easily.
Now EDL mode or Xiaomi Redmi Go edl test points are in front of you. And you can use them to install the firmware on Redmi 7 without unlocking the bootloader.
Thanks for your tips. The first doesn't work:
fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
I'll try the EDL mode.
I tried the EDL mode following this tutorial: https://forum.xda-developers.com/t/...ight-turns-on-for-a-second-using-edl.4228641/
I've disconnected the battery and shorted the 2 pins to get into EDL mode. But when I connect the phone (first without then with the battery connected) to my computer with the USB cable, Windows doesn't recognize it. No sound is triggered.
The phone is recognized in fastboot mode and I tried to use QFIL anyway. I got the Sahara protocol fail.
Any clue?
I finally got it. I tried several times to plug and unplug the USB cable and the phone entered in EDL mode and has been recognized by Windows. I also runned QFIl several times and it finally downloaded the rom.
Thanks Kenora_I !
ossook said:
I finally got it. I tried several times to plug and unplug the USB cable and the phone entered in EDL mode and has been recognized by Windows. I also runned QFIl several times and it finally downloaded the rom.
Thanks Kenora_I !
Click to expand...
Click to collapse
Nice ! so what now ? the BL is re unlocked ?
loopypalm said:
Nice ! so what now ? the BL is re unlocked ?
Click to expand...
Click to collapse
Yes indeed. I flashed the Miui ginko rom and the BL is re unlocked. So I had to carry on the Miui Unlock procedure and have to wait 168 hours... I've lost my files but I have a backup and the phone works again.

[Help me]Xperia XA2 Brick I also don't know what the reason for this is

I use this phone normally to watch youtube, and use social apps, and he changed wallpaper without i do nothing, i try change to my wallpaper to normally, but he dont response, and i reset the phone and when turn on, stayed like this, i try format and no sucess, any have idea how to fix him ?
Hmmm...
Custom ROM or not, root or not?
Go into recovery mode and clear the cache.
ze7zez said:
Hmmm...
Custom ROM or not, root or not?
Go into recovery mode and clear the cache.
Click to expand...
Click to collapse
not custom rom and not root, in video i show recovery mode and i cant enter in android configuration
Go into recovery mode (with the device powered off, hold Volume Down + Power) and you see what options are available. I'm not suggesting anything because I don't know the device, but I'll hint when I see a screenshot in recovery mode.
ze7zez said:
Go into recovery mode (with the device powered off, hold Volume Down + Power) and you see what options are available. I'm not suggesting anything because I don't know the device, but I'll hint when I see a screenshot in recovery mode.
Click to expand...
Click to collapse
{
"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"
}
this is recovery mode i turn on hold volume down and power, in this phone, he call "Security Mode" in my language, dont have options in screen
and i try turn on with hold volume up and power, one blue light appears and the phone dont response
HeenryL said:
this is recovery mode i turn on hold volume down and power, in this phone, he call "Security Mode" in my language, dont have options in screen
Click to expand...
Click to collapse
The image shows that the system booted into safe mode, not recovery mode. Can you check with the adb devices command how the phone connected to the PC responds?
Recovery mode looks like >this< video at 1:30.
ze7zez said:
The image shows that the system booted into safe mode, not recovery mode. Can you check with the adb devices command how the phone connected to the PC responds?
Recovery mode looks like >this< video at 1:30.
Click to expand...
Click to collapse
i try enter in recovery mode according to the video, he fixed in loop boot and use the ADB commands in CMD the phone dont response, just returning "waiting device", i buy new battery for my old phone to the fix him, will arrive in two days, I bought this xperia 2 months ago, its already broken its very sad for me, in my country this phone cost 2 salary, and sony dont offer oficial support here, i just put he in closet and forgget him, guy very very thanks so much to try help me, and your time too, thanks
try download the firmware with xperfirm later flash with newflasher but the newflasher files in firmware downloaded archive next cilck the newflasher exe and good luck i hope make a back up of yoru drm keys
sony xperia xa2 ultra stuck on dead battery and sony screen and wont go past them
so this morning in class I lightly dropped my phone from my hand onto the table lightly, and that was it, I had this phone for a while so its filled with stuff. Its stuck on loop on the Dead battery sign to the white sony screen and none of the...
forum.xda-developers.com

Categories

Resources