Database Users

Hard Brick P10 Lite - need help

Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.

Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny

Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.

lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?

I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please

edl mode; cannot receive hello packet

Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.

I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?

foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.

udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.

foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol

Disable driver enforcment to get the hello packet.

TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet

Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?

Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?

foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it

Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling

apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?

foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.

foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section

I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:

THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3

udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!

[PROBLEM] MI A1 Black Screen Image after boot Image

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

Did I just brick my phone?...

Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.

lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"

DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.

lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.

Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:

lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...

lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted

DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader

lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.

DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.

lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.

DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?

lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.

DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.

This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?

lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.

DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.

Phone in bootloop, cant access recovery

Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.

pleasuremann said:
Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.
Click to expand...
Click to collapse
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.

levone1 said:
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.
Click to expand...
Click to collapse
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process

pleasuremann said:
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process
Click to expand...
Click to collapse
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...

levone1 said:
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...
Click to expand...
Click to collapse
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance

jayeffpee said:
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance
Click to expand...
Click to collapse
Does fastboot work? Also, what do you ultimately want to do, return to stock?

levone1 said:
Does fastboot work? Also, what do you ultimately want to do, return to stock?
Click to expand...
Click to collapse
yes, after hard work to install drivers, I managed to get the phone to be recognized by Flashtool in fastboot mode. But the phone is not charging when turned off, and its not rebooting. I wanted to try again with stock ROM, since I got some battery issues with LineageOS (phone turned off while playing some games, and worked fine while doing the same with usb cable charging to laptop or AC charger.)
But I cannot do anything right now. Only fastboot mode and force restart works, but it stuck in Sony logo (after normal bootloader unlock 5 seconds warning). What can I do?