Database Users

Phone gone?! please help!!!

Hi, I think this should go into Dev section, but i dont have enough Posts yet... This forum is my last hope. I already did Custom Recovery, Root and Custom Rom on a different phone, but I think this time ive briked my Phone
I rooted my brandnew Play yesterday and landed in a bootloop today, i think i had a wifi Problem, however, I then tried out FrAsErTaG's FTS Customrom and everything worked fine. Afterwards I wanted to flash the DooMLoRD Kernel. Now I cant access my phone anymore... Cant get into Bootloader mode nor into flashmode or anything, the led on the Powerbutton stays black. But when i press the Powerbutton, the phone vibrates for a second and a blue or green light flashes for a millisec. When i do the same while connected via usb, the phone does nothing, and the phone isnt recognized by the pc. any Help PLEASE??? Phone was brandnew

Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.

arihellmichimich said:
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
Click to expand...
Click to collapse
You need to flash a new kernel/boot.img by the looks of it, maybe try flashing the stock kernel as you know it works, if boot partition is corrupt or badly flashed, flashing a rom wont solve the problem
Sent from my R800i using Tapatalk

I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...

arihellmichimich said:
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
Click to expand...
Click to collapse
Just flash doomlords kernel from fastboot, that has CWM embedded into the kernel, so you get to keep your recovery and get to boot your phone
just to be safe, use the command "fastboot erase boot" before you flash a kernel, this will format the boot partition so you can make a clean install
doomlord thread:
http://forum.xda-developers.com/showthread.php?t=1176502

Thanks a lot! Right now, when i connect it to the Powercable, the red led flashes every few seconds. I will try as soon, as my battery is charged again..

... I have a really bad feeling again. After the red led stopped blinking, i connected via Fastboot (blue light), erased the Boot partition and flashed DoomLords Boot Image. Sais 1 bad block encountered! (it told me already, that i had 10 bad sectors when i flashed the rom before but i didnt think this was the problem, because it bootet up at that time).
For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???

arihellmichimich said:
... For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
Click to expand...
Click to collapse
Good luck with this. I basically did the same thing on Sunday. I gave up trying to fix late Sunday night, but when I tried again yesterday evening I'm only getting the blinking orange light. I did leave the device on charge last night, but the light didn't come on to say it was charging. How do you know your battery is charged?
I'll take AH's advice and if I ever manage to get the blue light back I'll erase boot, installed DoomLords custom kernel and then hope recovery can fix the rest.
I'll post back here if I make any progress before you (and please let us know how, if you manage to fix it in the mean time).
Daeron.

I've spent the last couple of days searching the forum, search google, search the forum some more and I've made a bit of progress.
After finding similar threads in the X10 forum I believe the flashing red light is related to the battery. Also my inability to get a fastboot blue light was caused by uninstalling SE Companion while trying to use other drivers for a Flashtool stock image flash (I didn't get that to work either). I have reinstalled SE Companion and can now connect to my PC in fastboot mode (with the blue light).
This is where my progress ends. I have tried using using this and the commandline outputs this
Code:
F:\Xperia Play\Boot Unlock\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 41547kB/s
OKAY [ 0.549s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.552s
but the phone does nothing except the blue light goes out. Which leads me back to the battery.
After trying to fastboot the recovery image the only thing I can do is disconnect, take out the battery, put battery back and plug into mains charger. The red light starts flashing again for a short while then I can try again with fastboot.
Next step is to leave it on charge for a few hours (only did 30mins last time) and try again. I think the reason the recovery didn't work is the battery won't hold enough charge to boot on its own, so I need a new battery
The only other thing I haven't tried is to erase partitions before booting recovery. I'll give that a go before booting recovery image in a few hours.
D.

When i boot into CWM from the boot image via fastboot. It will shut off the phone. Just unplug the device, wait a sec, and try to enter fastboot again. Usually it hangs and then goes to CWM. And when you flash a new rom, You need to factory reset in CWM clearing data and cache or else it will bootloop. Thats just basic Android rommage right thurrrr. Mine was stuck, and i just flashed the stock system.sin and kernel.sin and erase the /data and /cache with Clockwork.
fastboot flash system system.sin
fastboot flash boot kernel.sin

Sooo sorry, i didnt post before, but i moved out of my flat and had a lot of other stuff to do last week...
In the End this helped for me.
1. FULLY CHARGE YOUR PHONE!!! I was told to remove battery for 30minutes, then put it back in but without sim card and withough SD Card. Then plug the charger back and charge for at least 5-10 hours!!!
2. Connect your Phone in Fastboot mode (blue light) by pressing the searchbutton before connecting.
3. Do the steps of relocking your play through Fastboot
4. Try SE Update again with the official Sony Software, it said software could be updated :-D
So in the end, the blinking red light was just a battery problem, i couldnt imagine it was such a big deal, because i always charged for at least an hour and i thought the usb port of my netbook was at least strong enough to provide power during the flashing progress BUT IT WAS NOT!!!
Thank you soo much for the help!!!

Everything worked out fine that way.

I need a stock recovery image

My device is really messed up. I guess the update got corrupted. It will not boot. Not at all. It will not boot to download mode or enter recovery. I"m not sure what happened, but it is inoperable. I have tried to run the RUU, but it says the battery is below 30% because it won't charge either. Somebody help me. These things are tanks, and this one is giving me headaches. I need a stock recovery image to flash so that hopefully it will charge afterwards, and I can run the RUU. I have been all over the threads for about 3 hours. I can not find a download link for the stock recovery image;.

Sleepycloud said:
My device is really messed up. I guess the update got corrupted. It will not boot. Not at all. It will not boot to download mode or enter recovery. I"m not sure what happened, but it is inoperable. I have tried to run the RUU, but it says the battery is below 30% because it won't charge either. Somebody help me. These things are tanks, and this one is giving me headaches. I need a stock recovery image to flash so that hopefully it will charge afterwards, and I can run the RUU. I have been all over the threads for about 3 hours. I can not find a download link for the stock recovery image;.
Click to expand...
Click to collapse
You can extract the latest recovery from the firmware thread. Download the full firmware packet and simply pull out the recovery IMG. Flash as you normally would with fastboot.

deakelem said:
You can extract the latest recovery from the firmware thread. Download the full firmware packet and simply pull out the recovery IMG. Flash as you normally would with fastboot.
Click to expand...
Click to collapse
I tried that. I've done that many times in the past, I'm not able to get a recovery.img to show on anything that I extract. I"ll try another one.

I finally got a recovery.img and tried to flash it. It says it is not allowed in s-on state. I have flashed this phone over a hundred times. It is not supposed to do this. I'm not sure what happened in the update, but it will not boot and I can not flash anything at all. I can't even fastboot oem lock it. I tried to run the RUU but it is not charged to 30%. I am extremely puzzled by this current situation. Any bright ideas?

Sleepycloud said:
I finally got a recovery.img and tried to flash it. It says it is not allowed in s-on state. I have flashed this phone over a hundred times. It is not supposed to do this. I'm not sure what happened in the update, but it will not boot and I can not flash anything at all. I can't even fastboot oem lock it. I tried to run the RUU but it is not charged to 30%. I am extremely puzzled by this current situation. Any bright ideas?
Click to expand...
Click to collapse
how are u trying to flash the recovery img? be specific...
if u are s-on, you can only flash signed firmware zips

OMJ said:
how are u trying to flash the recovery img? be specific...
if u are s-on, you can only flash signed firmware zips
Click to expand...
Click to collapse
I've tried flashing them with ADB and using the SD card method. I've tried flashing the recovery.img and boot.img with ADB too. It says I can't flash any of it being S-On. I have flashed all of this, on this device, more than a hundred times. I went back to unrooted stock with the RUU from HTC website. When I took the last update, all it does is power cycle. I can get into download mode, or recovery. I can only get directly into the bootloader menu by holding both volume up and down and the power button. Like I already stated, it won't charge ether, so the RUU won't execute. Any help would be appreciated.

Sleepycloud said:
I've tried flashing them with ADB and using the SD card method. I've tried flashing the recovery.img and boot.img with ADB too. It says I can't flash any of it being S-On. I have flashed all of this, on this device, more than a hundred times. I went back to unrooted stock with the RUU from HTC website. When I took the last update, all it does is power cycle. I can get into download mode, or recovery. I can only get directly into the bootloader menu by holding both volume up and down and the power button. Like I already stated, it won't charge ether, so the RUU won't execute. Any help would be appreciated.
Click to expand...
Click to collapse
Sounds like u need to contact HTC... If you were stock and the ota effed it up, they should be able to help

OMJ said:
Sounds like u need to contact HTC... If you were stock and the ota effed it up, they should be able to help
Click to expand...
Click to collapse
That is what I'm thinking. I'm gonna mess with it one more time today. I've learned that numerous flashing processes that get jacked up and become unresponsive will sometimes work on the 20th attempt. That's why I keep at it until I know it is dead. It was responding to USB but somehow that stopped. I'm pretty certain that I can pull the screen off and charge the battery. I'm 100% certain that it died in the in the update process right on the battery charger script. I'm positive that it is just a dead battery so it can't boot. Im about to pull the battery and solder charger wires on directly and test it with my volt meter until it is fully charged. I'm certain this is the problem.

Hard brick? Can't boot to recovery

So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.

You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM

vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.

I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.

hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.

eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!

Cant leave fastboot after unlocking bootloader....

So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.

Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.

Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.

William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over

MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing

Can you place the device in edl? It will not display any lights or images when it is in edl.

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!