Hi all,
So basically I was trying to install Pixelexperience to my Note 7 today and I messed it up big time. So I was having some issues with TWRP and one of the solutions (according to posts I found on Google) was to update the phone firmware. So I went to do that. Downloaded the lavander firmware for my Note 7, put it in the folder with other stuff I was downloading. One of these was firmware for Redmi A5 (which I didn't notice) and ended up flashing that. Now my phones screen is dead (I guess the rest of it also?). When I plug it in to PC the PC produces the sounds that something connected but running fastbood / adb devices doesn't return anything. I tried multiple times booting to fastboot / recovery but I have no idea when the phone is on or off. So it just produces sound on PC that it disconnected and connected like 1 second after but nothing still shows up on fastboot.
Did anyone had similiar issue and is there anything I can do? Or should I go look for a new phone?
Thank you for your time
Try to flash the whole rom again.
VD171 said:
Try to flash the whole rom again.
Click to expand...
Click to collapse
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time
vivida said:
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time
Click to expand...
Click to collapse
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.com/
VD171 said:
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.comI have tried but I just can't get the devices to boot into fastboot and I have no idea in what state it is since the screen doesn't show anything
Click to expand...
Click to collapse
Can you enter in recovery ?
VD171 said:
Can you enter in recovery ?
Click to expand...
Click to collapse
No, the same thing is happening. I just get the sound on PC and that's about it. It isn't recognized by the PC or any software that I tried to use
Try to get new cable and it will work
Eslamloka said:
Try to get new cable and it will work
Click to expand...
Click to collapse
After that's make your phone in edl mode then flash stock miui with miflash tool
Eslamloka said:
After that's make your phone in edl mode then flash stock miui with miflash tool
Click to expand...
Click to collapse
I receive cannot receive hello packet error message now
vivida said:
I receive cannot receive hello packet error message now
Click to expand...
Click to collapse
Sorry but i can't understand,,,is u tried to change a cable and it's working or not
Eslamloka said:
Sorry but i can't understand,,,is u tried to change a cable and it's working or not
Click to expand...
Click to collapse
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account
vivida said:
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account
Click to expand...
Click to collapse
before miflash firstly you must connect your phone with pc or laptop
Related
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.
I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!
Use the MSM tool. I had to do that, too, and it saved me!
bigmikey307 said:
I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!
Click to expand...
Click to collapse
link for help: https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
bigmikey307 said:
I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.
Click to expand...
Click to collapse
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?
This happened to me when I upgraded from 9.0.7 to 9.0.10. When I booted into TWRP, all my internal storage was encrypted, so I couldn't flash the OS again from there. I tried to wipe just the data and dalvik/cache in a hope to fix it. Don't do this as my internal storage got wiped (most likely due to the encryption). I had to download and reflash the OS through OTG with a pendrive in the end. Possibly try to do that first if you have access to it instead of wiping the phone.
bigmikey307 said:
No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?
Click to expand...
Click to collapse
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Phone is recognized as a Qualcomm modem by the computer. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.
Striatum_bdr said:
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.
Click to expand...
Click to collapse
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool
bigmikey307 said:
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool
Click to expand...
Click to collapse
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it
twinnfamous said:
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it
Click to expand...
Click to collapse
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember
twinnfamous said:
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember
Click to expand...
Click to collapse
Ok thanks, I'll keep trying
H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Glad to hear u got it fixed
bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Hi I flashed the installer by mistake once.
The solution is to flash the stock boot image in both slots.
Worked fine for me.
bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
Umm.. That's probably what you did, but make sure to get the driver automatically via internet. If that doesn't help, perhaps a different pc/port/cable will do the trick (different pc worked for me).
H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
I've had to use that tool twice for doing stuff the phone didn't like, testing etc. Saved my bacon both times
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
I was flashing my device
flash is completed
but my mobile didn't reboot
and now my mobile is not turn on
and not charging and i can't turn it on fastboot
what's wrong with my mobile?
please anyone explain??
i need help
c1w3xx said:
I was flashing my device
flash is completed
but my mobile didn't reboot
and now my mobile is not turn on
and not charging and i can't turn it on fastboot
what's wrong with my mobile?
please anyone explain??
i need help
Click to expand...
Click to collapse
very bad, care to share exactly what you did so others don't make the same mistake.
Calm down, explain this in a better way. What did you do, step by step?
I was flashing Global rom
Kafei said:
Calm down, explain this in a better way. What did you do, step by step?
Click to expand...
Click to collapse
That time i was flashing my mobile
for unroot
Now i tell you how it's brick
1. First I turn it on at fastboot
2. I downloaded Global version Rom for flash
3. Open MI flashtool For flash my mobile
4. All is completed
5. Mobile Turned Off
6. NOw it's still of not turn it on
7. Then i try to open fastboot again
8. but it's not running
I think it is bricked
Now how can i unbrick it?
(Sorry For my typeing... I'm week at English)
Did you flash the correct rom? When you plug USB to pc, does it detect anything at all? Does it had enough battery when you were flashing it?
agenius5 said:
Did you flash the correct rom? When you plug USB to pc, does it detect anything at all? Does it had enough battery when you were flashing it?
Click to expand...
Click to collapse
Yes, i did flash the correct rom
Now when i plug USB to pc, it detect Qualcomm HS-USB QDLoader 9008 at Computer Device manager.
Yes It has 50% more battery .
I think it is bricked :'(
Try test point method. I know its dangerous but it works.
mayukh2000 said:
Try test point method. I know its dangerous but it works.
Click to expand...
Click to collapse
Can i flash my mobile with test poin method??
rickyreyne said:
Youtube
Click to expand...
Click to collapse
Is that work perfectly?
c1w3xx said:
Is that work perfectly?
Click to expand...
Click to collapse
Ya that works.
c1w3xx said:
Is that work perfectly?
Click to expand...
Click to collapse
Sure
I also have a Dead phone. I woke up in the morning late because my alarm didnt go off and found my phone wouldnt turn on. I couldnt even boot to recovery. The charge light no longer comes on either. Would anyone know a fix? Is there a diode or a capacitor that can be replaced?
i flash my phone in same situation and i try with test pointe but nothing work help
Phone is probably in EDL mode, try reflashing with MiFlash again
I have a TA-1033 version and a deep flash engerneering cable but im stuck of how to unbrick, my device is detected as QDLoader 9008, also if i try to flash using NOST i get "polling USB device" then a "DEVICE_NOT_CONFIGURE" its an 0x4000 error
if anyone can help me out that would be great!
Sent from my AGS_W09
I have same problem. I don't know what i do, but seems to when i charge my phone over 80 %.
Then i get it download mode and i change edl cable to regular usb cable and then fastboot reconise my phone and i can flash it succesfull.
DoggyStar said:
I have same problem. I don't know what i do, but seems to when i charge my phone over 80 %.
Then i get it download mode and i change edl cable to regular usb cable and then fastboot reconise my phone and i can flash it succesfull.
Click to expand...
Click to collapse
Its completely dead, only detected as QHSUSB BULK and like i said i got one of those deep flash cables from shenzen
When you but it on, can you see android text or just "you phone is unlocked text"?
My phone only shows that unlock text, but after I use edl cable i can get android text showing up.
DoggyStar said:
When you but it on, can you see android text or just "you phone is unlocked text"?
My phone only shows that unlock text, but after I use edl cable i can get android text showing up.
Click to expand...
Click to collapse
No mine just doesnt vibrate or anything
And you have full battery?
DoggyStar said:
And you have full battery?
Click to expand...
Click to collapse
I dont know because its dead as in it wont show any signs of life
Yes yes, but put it ac charger for 2-3 hours and see if you then see something or can you then get it fastboot mode.
My phone has low battery but when I charge it, fastboot start working magically.
DoggyStar said:
Yes yes, but put it ac charger for 2-3 hours and see if you then see something or can you then get it fastboot mode.
My phone has low battery but when I charge it, fastboot start working magically.
Click to expand...
Click to collapse
I modified my aboot.img because i thought i could downgrade but that killed my device
mattwhite7102 said:
I modified my aboot.img because i thought i could downgrade but that killed my device
Click to expand...
Click to collapse
Does qpst tool worked for you?
Emmykay223 said:
Does qpst tool worked for you?
Click to expand...
Click to collapse
Nope, i dont have the files for QPST, but i do have the qfil files and one of those deep flash cables, if you can get my phone fixed i will respect you forever!
mattwhite7102 said:
Nope, i dont have the files for QPST, but i do have the qfil files and one of those deep flash cables, if you can get my phone fixed i will respect you forever!
Click to expand...
Click to collapse
No no i don't want that , if i could help you surely i will .. download qpst tool and Qualcomm drivers on your pc or laptop , if you did all the things and nothing happened yet, so why you don't try this too? We never know which things could give us better results. Hope for the best ??
https://www.qpstflash.com
Download qpst from here
Emmykay223 said:
No no i don't want that , if i could help you surely i will .. download qpst tool and Qualcomm drivers on your pc or laptop , if you did all the things and nothing happened yet, so why you don't try this too? We never know which things could give us better results. Hope for the best ??
https://www.qpstflash.com
Download qpst from here
Click to expand...
Click to collapse
Well i downloaded the 2.7.453 of qpst and flashing with qfil gives me SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED though whats strange is different versions of qfil gives me different errors...
mattwhite7102 said:
Well i downloaded the 2.7.453 of qpst and flashing with qfil gives me SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED though whats strange is different versions of qfil gives me different errors...
Click to expand...
Click to collapse
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear
Emmykay223 said:
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear
Click to expand...
Click to collapse
It does get detected by qpst, might be a driver issue
Emmykay223 said:
Does it able to be detected by qpst.
And did you install Qualcomm drivers?
Just look at this .
Hope all of your problems would clear
Click to expand...
Click to collapse
Nope tried it but coming up with "unable to download flash programmer with sahara protocol"
mattwhite7102 said:
Nope tried it but coming up with "unable to download flash programmer with sahara protocol"
Click to expand...
Click to collapse
Download another android flash zip files from here, 8.0 or 9.0 directly hope it would work
Emmykay223 said:
Download another android flash zip files from here, 8.0 or 9.0 directly hope it would work
Click to expand...
Click to collapse
Can you link me for the TA-1033? its gotta be qfil because my phone doesnt show any signs of life!
mattwhite7102 said:
Can you link me for the TA-1033? its gotta be qfil because my phone doesnt show any signs of life!
Click to expand...
Click to collapse
https://www.google.com/amp/s/forum....-6/help/nokia-6-ota-update-ddls-t3721424/amp/
Emmykay223 said:
https://www.google.com/amp/s/forum....-6/help/nokia-6-ota-update-ddls-t3721424/amp/
Click to expand...
Click to collapse
I cant install these because my phone gets detcted as QHSUSB BULK
As the title says, my phone just boots till asus logo and switches off. The battery was 15% at night. I woke up and there was no juice left. So I kept my phone for charging. The phone just boot loops with big battery icon with no charging animation. Even the recovery doesn't work. I tried flashing via fastboot mode. My phone was already unlocked. But during fastboot, it says FAILED (remote: 'Error flashing partition : Write Protected'). Any help? Yes, I'm using usb 2.0 port.
anagramgenius said:
As the title says, my phone just boots till asus logo and switches off. The battery was 15% at night. I woke up and there was no juice left. So I kept my phone for charging. The phone just boot loops with big battery icon with no charging animation. Even the recovery doesn't work. I tried flashing via fastboot mode. My phone was already unlocked. But during fastboot, it says FAILED (remote: 'Error flashing partition : Write Protected'). Any help?
Click to expand...
Click to collapse
Try following this tutorial all over again.
https://telegra.ph/Guide-to-unlock-bootloader-flash-custom-recovery-and-root-ASUS-Max-Pro-M2-03-06
Anubhav_singh said:
Try following this tutorial all over again.
https://telegra.ph/Guide-to-unlock-bootloader-flash-custom-recovery-and-root-ASUS-Max-Pro-M2-03-06
Click to expand...
Click to collapse
My phone is already unlocked. And now the fastboot isn't working. I already tried unlocking again. I get the above mention error while flashing via fastboot.
anagramgenius said:
My phone is already unlocked. Add now the fastboot isn't working. I already tried unlocking again. I get the above mention error while flashing via fastboot.
Click to expand...
Click to collapse
You get the unlocked bootloader warning while rebooting the device now.?
Anubhav_singh said:
You get the unlocked bootloader warning while rebooting the device now.?
Click to expand...
Click to collapse
Yes. But it doesn't boot to system. It just switches off after displaying asus logo.
anagramgenius said:
Yes. But it doesn't boot to system. It just switches off after displaying asus logo.
Click to expand...
Click to collapse
Join the device group on telegram, it would be easy to get help there as it might be a lengthy process.
Anubhav_singh said:
Join the device group on telegram, it would be easy to get help there as it might be a lengthy process.
Click to expand...
Click to collapse
Yes I have already joined. But I don't have a backup smartphone. So I'll have to wait I guess.
EDIT: Seems no one knows a solution in telegram group either. I asked about this problem there and one or two replied and they stopped replying.
anagramgenius said:
Yes I have already joined. But I don't have a backup smartphone. So I'll have to wait I guess.
EDIT: Seems no one knows a solution in telegram group either. I asked about this problem there and one or two replied and they stopped replying.
Click to expand...
Click to collapse
Okay, try flashing the fastboot rom. It will relock the bootloader and will flash the stock oreo rom. See if this works.
Anubhav_singh said:
Okay, try flashing the fastboot rom. It will relock the bootloader and will flash the stock oreo rom. See if this works.
Click to expand...
Click to collapse
It shows the same error. Nothing can be flashed via fastboot mode.
Was anyone able to resolve this?
mitrokin said:
Was anyone able to resolve this?
Click to expand...
Click to collapse
No.
anagramgenius said:
No.
Click to expand...
Click to collapse
You might need to visit the service center, as recovery can't be booted, also nothing can be flashed as device is write protected.
try to unlockbootloader again and try flashing then
nishant6577 said:
try to unlockbootloader again and try flashing then
Click to expand...
Click to collapse
No fastboot command is working. So I can't unlock bootloader again.(it is already unlocked btw)
anagramgenius said:
No fastboot command is working. So I can't unlock bootloader again.(it is already unlocked btw)
Click to expand...
Click to collapse
Check whether your usb port is 3.0, fastboot needs usb 2.0 ports for fastboot commands.
V9_6b said:
Check whether your usb port is 3.0, fastboot needs usb 2.0 ports for fastboot commands.
Click to expand...
Click to collapse
Yup. It's usb 2.0 port.
Bro,I have same problem as you have.how can I solve it even edl method also shows firehose qloader failed error .how I solve bro!!!
Anyone? Please help us, I'm also in this kind of situation with OP. I still can't use Asus Flash Tool because it needs internet connection I'm just borrowing my cousin's PC and they don't have internet broadband either.
I'm wondering if it also gives an error "write protected" like on Fastboot CMD. And if it does I think our last resort is to flash with QFIL.
If I am right, you'll updated to the 073 pie version of the stock software, which bricked the devices.?
blood1995 said:
Anyone? Please help us, I'm also in this kind of situation with OP. I still can't use Asus Flash Tool because it needs internet connection I'm just borrowing my cousin's PC and they don't have internet broadband either.
I'm wondering if it also gives an error "write protected" like on Fastboot CMD. And if it does I think our last resort is to flash with QFIL.
Click to expand...
Click to collapse
Unable to flash with QFIL either.