Help! I think i flashed something wrong for my Z2Pro, now it's stuck in recovery/fastboot mode, i can still access the menu, but i cannot flash anything via fastboot, my computer says waiting for adb device, inputting the command adb devices show nothing. Trying to flash stock ROM via QFIL but instead of port 9008, its showing port 900E, if i try to flash, it says this:
Download Fail: Switch to EDL Fail Failed to switch to Emergency Download Mode.
@OP
Try this method, I think you'll be OK!
But you need to use Google Translation!
and download a Rom from the "Rom Section".
Good luck.
http://www.zukfans.it/2016/07/06/gu...procedure-di-aggiornamento-sui-terminali-zuk/
Edit: I just saw your thread over "ZUK Fans Europe", I'm glad you got it working again!
Yup! Thanks!
Guys I am facing the exact same problem.
Could you please let me know how you resolved it.
Thanks
@digitalguy13 and @alvintan38, did you already solve it? I have the same problem
DavidWel said:
@digitalguy13 and @alvintan38, did you already solve it? I have the same problem
Click to expand...
Click to collapse
Maybe you can get it to work trying this guide: http://www.androidbrick.com/zuk-z2-z2-pro-qpst-qfil-miflash-rom-flashing-guide/
Thanks for the suggestion, I managed to fix the 900e message using the DIY cable. This was a really easy solution So for anyone, which encouters the same problem, just follow the guide from zukfans called "deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily" (sorry, I'm not allowed to post links yet)
Need Help.
BootLoop
Img: postimg.org/image/shtjs0djn/
After installing the latest OTA the phone will not start
[Video]
Vide:youtube.com/watch?v=O7Jq7jglL2g
Video in Twitter Account @Josecrp92
@oneplus @oneplus_ES @oneplus_Support #OnePlus3T #Comunidad #Foro
Problem solved. If you need help contact on twitter: @Josecrp92
Unbrick Tutorial
Josecrp92 said:
Need Help.
BootLoop
Img: postimg.org/image/shtjs0djn/
After installing the latest OTA the phone will not start
[Video]
Vide:youtube.com/watch?v=O7Jq7jglL2g
Video in Twitter Account @Josecrp92
@oneplus @oneplus_ES @oneplus_Support #OnePlus3T #Comunidad #Foro
Click to expand...
Click to collapse
Hello, I bricked my 3T a few days ago flashing a bad update. I had no LED, no screen activity, no charging activity!
I found this guide and restored my phone with it;
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Hope this helps.
bowlandspoon said:
Hello, I bricked my 3T a few days ago flashing a bad update. I had no LED, no screen activity, no charging activity!
I found this guide and restored my phone with it;
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Hope this helps.
Click to expand...
Click to collapse
MSM Error 1 postimg.org/image/l1zoudyf3/
MSM Error 2 / OK? postimg.org/image/glii833pt/
Fastboot Mode postimg.org/image/bx8j6zcnt/
On the phone the OEM unlock function is not enabled and you do not have the USB enabled in debug mode. The device does not start the operating system and does not have access to the recovery mode. It's the same as in the video. Without a recovery mode I can not reinstall the system.
I still can not solve the problem.
Thanks for your time
Josecrp92 said:
MSM Error 1 postimg.org/image/l1zoudyf3/
MSM Error 2 / OK? postimg.org/image/glii833pt/
Fastboot Mode postimg.org/image/bx8j6zcnt/
On the phone the OEM unlock function is not enabled and you do not have the USB enabled in debug mode. The device does not start the operating system and does not have access to the recovery mode. It's the same as in the video. Without a recovery mode I can not reinstall the system.
I still can not solve the problem.
Thanks for your time
Click to expand...
Click to collapse
That sucks. I did encounter a few errors when trying to use the program myself, had to use a different PC to get it to work. Maybe try posting in the thread that has the recovery info. Hopefully they can help you.
bowlandspoon said:
That sucks. I did encounter a few errors when trying to use the program myself, had to use a different PC to get it to work. Maybe try posting in the thread that has the recovery info. Hopefully they can help you.
Click to expand...
Click to collapse
I have 5 computers at home. But I can not post the problem in the OnePlus community and I can not contact them by twitter or mail
(I'll try another computer)
Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE
The app works just fine... Also why are you trying to use a Xiaomi flash tool on an Asus device?
Get out of EDL mode with vol- vol+ power all three together.
EfeKamil said:
Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE
Click to expand...
Click to collapse
Have you tried doing the process with the correct drivers installed? (I have not done this method, but it could be driver related) See here for drivers
EDIT: at the bottom of your EDL thread it does state you need the Qualcom drivers installed, not sure if they're the same as the ones i linked to, but the ones in that thread are here
Also, this post may be of some use to you, might wanna read the rest of the thread too for tips...
'I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).
I have no idea why that's the case but it worked for me.'
Today i unlocked the bootloader and installed AOSIP rom but i decided to revert to stock rom and flashed it( version c26). Then i checked i was on stock recovery. After confirming i was on stock recovery i re-locked the bootloader from fastboot command. After that the phone has gone into loop. It restarts continuously displaying the message "The current image(boot/recovery) have been destroyed an can not boot. Please flash the correct image or contact customer service to fix it". Since i can't get into fastboot mode/bootloader (pressing volume down + power key does nothing) i can't do anything. So if anyone know the solution please help me.
Note: my Computer recognizes the device if i press all three buttons simultaneously( i get device connected sound ).
Bro in the same boat, atleast you get the message saying boot image destroyed, in my case, phone keeps restarting and realme logo flashes
I read thread on gsmmafia that one can help to unbrick for money.
I can't put the external links due to xda policy, write me in direct message
Helg1002 said:
I read thread on gsmmafia that one can help to unbrick for money.
I can't put the external links due to xda policy, write me in direct message
Click to expand...
Click to collapse
Yes he solved it...
How?
Milan-XDA said:
How?
Click to expand...
Click to collapse
He recovered my phone today, CN version. He will provide the tool and image files and use TeamViewer for remote access to enter the username and password. It took approximately 15 minutes to finish. Contact him via his website -
https://www.gsmmafia.com/relame-x2-pro-rmx1931-flash-file/
I was trying to flash a new rom and accidentally hit "boot to fastboot" in the pixel experience recovery
now when i try to boot it goes black and i cant get back into recovery at all
when i put it into fastboot it isn't detected by my computer.... am i screwed?
Worst case just blank flash
Arealhooman said:
Worst case just blank flash
Click to expand...
Click to collapse
How do i do that?
Download Mi Flash Tool and flash Stock.
JingleDraws said:
I was trying to flash a new rom and accidentally hit "boot to fastboot"....
Click to expand...
Click to collapse
Have you tried a very, very long press on power to start up?
Had you flashed already that new rom and pressed then boot to fastboot instead of boot to recovery?
Elinx said:
Have you tried a very, very long press on power to start up?
Click to expand...
Click to collapse
Hey @Elinx you try to help everyone. I like that
Laptapper said:
....you try to help everyone....
Click to expand...
Click to collapse
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Elinx said:
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Click to expand...
Click to collapse
Yep....me too....but new members have a child protection
This just happened to me on the same recovery. I cleared my storage/cache ect then clicked boot to fastboot to flash a new recovery this then led to me just having a black screen.
Also mi flash seems to require fastboot in which my device is not showing.
Also thanks for any help anyone gives
WeeScottishMan said:
.... just having a black screen.
...
Click to expand...
Click to collapse
A black screen does mostly mean that the phone is started in EDL mode.
That is why I advice first to try a very long press on power.
You could check this inside device manager on PC, with or without the right USB drivers.
(Qualcomm HS-USB QDLoader 9008)
Flashing from EDL isn't possible without Mi authorisation as long there isn't a hacked firehose file.
Holding power seems to just be turning it off and on again. Also I cannot seem to find the phone on device manager although it plays the connection sound and refreshes when plugged in and turned on. Do you know where I would find it in device manager.
Thanks again for the help
oh wait yes it is in edl mode does that mean I am massively screwed :<
Thanks again.
WeeScottishMan said:
... yes it is in edl mode does that mean I am massively screwed....
Click to expand...
Click to collapse
If the phone does start black again after very long press.
Yes, you are screwed up with EDL and you need to go to a Mi service center, or try an "online unbrick service" with Teamviewer from a third party.
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
WeeScottishMan said:
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
I don't find the reason, in any of your posts, why it would be bricked. If your device is not really bricked, then to get it out, you have to press the three buttons at the same time for about 9 seconds, while you see the changes in device manager PC, so you can see in which mode it is. Eventually in the booting process, change the hardware buttons as if you will send it to fastboot or recovery mode, it doesn't matter the display is showing nothing, just check the device manager to have an idea.
Thanks for your suggestion.
I tried that yet it still shows the Qualcomm HS-USB QDLoader 9008 (COM3). I am also a bit confused why it has bricked since I really didn't think I had done anything wrong :/
mine appears in device manager, is that a good sign? what do i do from here
WeeScottishMan said:
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
if you do get it fixed please let me know what they did so i can do it as well! thank you and good luck!! ...at least this isn't my main phone..
Be sure to try all the methods to get it in other modes, it's just a timing thing, while device goes from a state to another, then you should try one time to enter to fastboot, and in a new cycle reboot, try to enter to recovery mode, BUT If the device, can't definitely enter to recovery nor fastboot mode, and it always redirects to Qualcomm HS-USB QDloader 9008 (apart than shutting down), then it's bricked.
EDL mode, using MiFlash tool requires a Mi authorized account, just older devices can use it for free, this is not the case, unfortunately.
Instead, you can try with other Qualcomm flasher tool, like QPST, not sure if it still works for this device (for older it does), you should give it a try.
@SubwayChamp is right about that.
There is a difference if EDL came out of the box or after an attempt to update or other flashing attempt.
That is why to try all possibilities to get into fastboot or recovery.
So try Vol up+ Vol down+power, Vol up+power, Vol down+power and only power always first to see if you can get out of EDL.
You can try QPST too, but search for some HowTo with pictures, because it isn't the same as Miflash and is a bit complicated if you never used it.
There still isn't a modded firehose file (prog_ufs_firehose_sm7150_ddr.elf) for RN10P to pass Mi authorization, but there is a very small chance that QPST does work.