Database Users

Doens't recognise

Here is my problem,
I had rooted my Xperia Play unlocked boatloader and it got bricked, Ok it was stupid I know many people told me.
But someone had tried to flash it, without succes Now I can't get my Xperia Play if flashmode and my computer doens't recognise it, if it is conected to my pc a red light is flashing.
Can someone help me please?

dont understand you ,if brick by ota update ,you should flash bin4ry fota flashtools
if you wan to recognise your play go to flash mode by seus with holding back button, once seus says your unofficial sw could not be updated means you pc recognise it already ,you can flash now
search button for fastboot is blue led
back button for flash is green led
red light you should find aleJandro to do re programme if im werent wrong
there is a post by him at developer section
good luck
Sent from my unknown device using XDA Premium app

Yeah it was bricked by a ota update but someone tried to flash it, but it went wrong now I can't go into fastboot ore anything.
A red light is flashing when it's connected to my pc.

Seems like your bootloader was flashed incorrectly. Alejandrissimo should be able to guide you into flashing it right again.
Enviado desde mi R800i usando Tapatalk

Should I send Alejandrissimo a pm ore something?

Afghaantje said:
Should I send Alejandrissimo a pm ore something?
Click to expand...
Click to collapse
Yes I can help I will send you a pm whit instructions

Alejandrissimo is the pro!!

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X

A Big Thanks to @Synthio for providing me these files.Without his help,this guide wouldn't have been possible at all. ​
Hi Peeps !!
A hard bricked OPX has nothing but a black screen (nothing ever comes on the screen, not even a boot logo ), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPX should be detected as QUALCOMM-HS USB Diagnostics xxxx. You might have a bricked OPX as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?id=0B3gqVK2lYqBiY1M2NjRjVllvYXM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and while keeping it pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
​

Hi
Great work!
I finally got a mod to close my thread and it has been closed.
I'll wait for the file that does not wipe /data

Thanks a loot. Gonna try it today at the end of the day.
Enviado do meu SM-N9005 através de Tapatalk

OnePlus*X*Unbrick Tool Mini... Only 47 MB is here :-
https://www.androidfilehost.com/?fid=24269982087019810
It doesn't wipe data either...
Sent from my ONE A2003 using Tapatalk

So if we are having the bootloader unlocked and try this tool to make it lock the bootloader? Means is it possible?

Silverstarjigar said:
So if we are having the bootloader unlocked and try this tool to make it lock the bootloader? Means is it possible?
Click to expand...
Click to collapse
No.It will keep the bootloader unlocked if it is unlocked already.

Man you are the real mvp... Thanks a lot some people i know are really screwed up because of thier opx got hard brick and there was no such guide available thanks alot mate really thanks

Will Try
Welp, ordered a new OPX yesterday. Just searched "qualcomm oneplus x driver" right when I woke up before work today and found this thread and felt stupid but saw it was as recent as today so I was pretty pumped. Thanks, will try ASAP and then can sell my other OPX, the new one or refuse delivery tomorrow . They deliver so fast now! 3 days!

thanks master sifoo.. my opx back to alive now ?

Thanks
Hello
Thank you for your post
I did all what's explained and when I run MSMDownloadToolV2.0 and click start it says "Waiting for device" and nothing happen!
I've been waiting more than 30 mints and nothing actually happen ..
Hope you help me ..
Thanks!​

DANETO said:
Hello
Thank you for your post
I did all what's explained and when I run MSMDownloadToolV2.0 and click start it says "Waiting for device" and nothing happen!
I've been waiting more than 30 mints and nothing actually happen ..
Hope you help me ..
Thanks!​
Click to expand...
Click to collapse
Can you give me Teamviewer access? I will see what the issue is and solve it.
Sent from my ONE A2003 using Tapatalk

Naman Bhalla said:
Can you give me Teamviewer access? I will see what the issue is and solve it.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
OfCourse
but I'll download it now and I'll tell you once I finished
Thank you

Naman Bhalla said:
OnePlus*X*Unbrick Tool Mini... Only 47 MB is here :-
https://www.androidfilehost.com/?fid=24269982087019810
It doesn't wipe data either...
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
So, if I used this Mini Tool, what would it change on my phone? Kernel, system, etc...
Thank you for your hard work.

DANETO said:
OfCourse
but I'll download it now and I'll tell you once I finished
Thank you
Click to expand...
Click to collapse
Hi !!
Has your issue been solved or you still need help ? I am online for some hours now.

Aphex13 said:
So, if I used this Mini Tool, what would it change on my phone? Kernel, system, etc...
Thank you for your hard work.
Click to expand...
Click to collapse
It will not change system but will restore kernel to stock.

Naman Bhalla said:
Hi !!
Has your issue been solved or you still need help ? I am online for some hours now.
Click to expand...
Click to collapse
I tried to solve it many times but still remains

DANETO said:
I tried to solve it many times but still remains
Click to expand...
Click to collapse
PM me now with Teamviewer ID and pass. I will fix it in any case.
Sent from my ONE A2003 using Tapatalk

Did layers work for anyone??
Sent from my ONE E1003 using Tapatalk

Thanks my phone's alive once again.
Sent from my ONE E1003 using Tapatalk

Sorry for my bad english
Can this tool unbrick any case of hard brick ? For example when I change the fastboot logo ? When I type 'fastboot erase bootloader' ?
Envoyé de mon ONE E1003 en utilisant Tapatalk

asus zenfone 2 bricked while updating to marshmallow by TWRP RECOVERY

Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.

Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528

Same happend to me, can't even unbrick it.

Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.

kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653

The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk

Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse

kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653

I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse

[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653

That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse

same here

Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed

QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.

t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?

sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)

t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere

sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.

t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?

Nexus 6P Android N Beta - "no command" and phone won't boot

Help!....
So I enrolled in the Android Beta program a couple of months ago with Nougat coming out for the Nexus 6P and all was fine and dandy….. then yesterday – out of the blue – I was just listening to a book on Mort Player – the phone starts shouting at me with a continuous tone siren with a black screen and my immediate reaction is to hold down the off button.
I turn on the phone and it displays “Google” and goes into the boot loop thing…
After a day of research…
I got into boot loader and went into recovery mode and “no command” gets displayed with a dead robot.
I go into Android recovery try to boot from there with no joy.
I wipe the cache and retry with no joy
I wipe the whole thing and retry - nada
I install the Android SDK with fastboot and ADB on my Windows 10 PC.
Fasboot devices recognises the phone – ADB doesn’t see it…. Presumably as the phone is locked…
Fastboot flashing comes up with "OEM unlock is not allowed" Phone is Locked…
ADB sideload obviously doesn’t see the phone
The phone isn’t recognised in the PC device manager – I have selected Google drivers in the SDK download options.
I’m now at a completely dead end – Help!
Android Recovery says that I’m on google/angler/angler 7.1.1/NPF10C/3347772.
Bootloader; BL: angler-03.63, Baseband: angler-03.75, Variant: ANGLER-ROW-VN1
Device is LOCKED and Download is DISABLED.
Help much appreciated!

Same for me i have to send my phone back to amazon for replacement
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk

ArN0V said:
Same for me i have to send my phone back to amazon for replacement
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Click to expand...
Click to collapse
Oh no - I thought that might be the only answer to it - are you on the beta program as well?

Same issue here, see my thread. This issue is going to be getting more commonplace according to huawei

NYYFan325 said:
Same issue here, see my thread. This issue is going to be getting more commonplace according to huawei
Click to expand...
Click to collapse
Much appreciated for passing on the thread - I had a look through the boards yesterday and must have missed it - will get in touch with Google and see what they have to say; will let you know...

Call Huawei - 5 minute conversation (gave them serial number, model number, and imei and they issued me an RMA

Mi A1 Hard brick

Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.

Does it enter fastboot mode? Turn it on holding volume down+power.

whoadood said:
Does it enter fastboot mode? Turn it on holding volume down+power.
Click to expand...
Click to collapse
No, it doesn't even turn on

R4aPt0rX said:
No, it doesn't even turn on
Click to expand...
Click to collapse
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.

whoadood said:
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.
Click to expand...
Click to collapse
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)

R4aPt0rX said:
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)
Click to expand...
Click to collapse
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.

whoadood said:
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.
Click to expand...
Click to collapse
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:

R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
Did you fix the restarting issue?

R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
WiFi not working means you have a wrong kernel. Flash a full system image again

Edwin Hamal said:
Did you fix the restarting issue?
Click to expand...
Click to collapse
Not yet, I am still trying to
tinyXperia said:
WiFi not working means you have a wrong kernel. Flash a full system image again
Click to expand...
Click to collapse
Which image do you recommed me to use, and which tool do you recommed me to use?

R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.

Edwin Hamal said:
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.
Click to expand...
Click to collapse
OMG it worked!! Thank you man!! I really appreciate all the help!

R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Any full image (1GB size) should work. Use mi flash tool to flash it

Hey guys,
I'm having the same problem. My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:

earthscaper said:
My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74978236&postcount=310
https://forum.xda-developers.com/mi-a1/help/mi-a1-stuck-edl-9008-flash-t3724567/

R4aPt0rX said:
Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.
Click to expand...
Click to collapse
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..

my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader

Try persist from other builds.
leo_hacker82 said:
my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader
Click to expand...
Click to collapse
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.

Edwin Hamal said:
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.
Click to expand...
Click to collapse
phone failed i try many persist.img i got latest and old firmwares and when i flash it fails...isnt allowed to download

leo_hacker82 said:
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..
Click to expand...
Click to collapse
Lo cargue con MiFlash con la opción de limpiar y bloquear.
I flashed it with MiFlash with the Clean and lock option active.