Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
romanrsr said:
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
Click to expand...
Click to collapse
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
AsItLies said:
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
Click to expand...
Click to collapse
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
romanrsr said:
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
Click to expand...
Click to collapse
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
AsItLies said:
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
Click to expand...
Click to collapse
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
romanrsr said:
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
Click to expand...
Click to collapse
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
AsItLies said:
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
Click to expand...
Click to collapse
You were correct! I Press the volume down + power keys, and then pressing the up key several times the QFIL detected it again. I have already flashed your backup and boot OK.
Now I have the following problem, when I insert another SIM it does not appear to enter the unlock code, but I get the error "This phone is permanently locked and can not be unlocked", did you have any experience with this?
It occurred to me to try to update it to the latest version via FOTA and LG Software, but it tells me that the latest version is already installed. Can you think of something? Thanks!
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
AsItLies said:
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
Click to expand...
Click to collapse
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
romanrsr said:
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
Click to expand...
Click to collapse
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
AsItLies said:
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
Click to expand...
Click to collapse
Check this:
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
romanrsr said:
Check this:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Use this xml. I created it to flash Q all at once, there aren't 0-6 luns, as the names are unique and not needed.
But just as a warning, it should work, I've used it, but it's only been tested on my device, which was originally at&t. And, I'd point out, doing this isn't going to unlock the sim.
cheers
Related
Hi all,
I going to tell you the complete story and any ideas orsuggestions will be appreciated.
I bought my mi5 in July. It came with a fake ROM but Ichanged it to OFFICAL GLOBAL STABLE .
Since then, I used the device perfectly fine, and follow theMIUI forum regularly.
Then in November I applied for betatesting Team and theyaccepted me. As my bootloader was still locked, I tried option one from abovetutorial, so I directly downloaded in my phone the GLOBAL DEV ROM and Ichoosing the package I started using Nougat for about a month, more or less.
Then, the tragedy happened. I was in a bar, having my phonein my trousers back pocket, and I set down that way. One minute, no more. Thephone´s battery was around 70%. When I realized I quickly took it but it wasnot able to turn on… Nothing pressing power volume + or any combination… I came home and let it charging all night (wallcharger) and nothing the morning after.
I tried to connect it to my PC but nothing happened in the screen,but pressing Power Volume+ the Windowsdevice Manager recognized it as “Android phone”, so after reading some threads about bootloader issues I decidesto flash it. I requested permission and then flashed it with the latest CHINADEV version. The flashing was completed, but the phone still not turningon. NEXT STEP: Local Technical Service.
They had my phone during a week. They tried to change thescreen, nothing, the battery nothing, and I don’t know which other tests theyperformed but they called me back to tell they were not able of doing nothing.
Having the phone back at home, now I was not able to get thePC seeing it as Android phone again. Nothin. Desperate me, I continued to read in internet and found in XDA a video where basically, you open the phone (remove back, and some screws),short two pins, and the PC is able to see it through the Qualcomm USB driversin EDL mode. Then flashing IS POSSIBLE. That is true. I am able to flashing,and I have tried CHINAs, GLOBAL, older ROMs about a dozen. Always the flash processsucceed, but the phone still not turning on.
After flashing I let the phone the whole night plugged inthe PC usb. Nothing
Now is plugged again to the wall charger, but nothing.
There are many threads with different solutions, so guys,please, anyone with a good idea to try??
Many Many thanks in advanced
https://forum.xda-developers.com/mi-5/help/bricked-mi5-t3528810
Read this and
Use only the versions mentioned
this device is just a chinese junk i regret bought it , just after 2 days i bought it got hard bricked .
anyway flash 7.2.4 and if phone didnt boot use 3 button ( up + down + power ) for 1 minute or more and it must boot , it did work for me .
I just got brick yesterday and followed those instructions. It really worked. I was finally able to flash china dev 6.11.10. Latest dev said just "missed hello packet".
MiFlash version 2016.04 and china dev 6.11.10 was right combination for me. I connected Mi5 to PC while pressing vol- and power buttons, then I released them. I opened miflash, selected rom and chose "flash all". Flashing was completed. I tried to power on my phone pressing power button but nothing. But when I pressed vol- and power, I was able to get to fastboot mode. Rest is history. I flashed TWRP, booted to it and flashed LineageOS again.
Hope it works for you too!
xmmn said:
this device is just a chinese junk i regret bought it , just after 2 days i bought it got hard bricked .
anyway flash 7.2.4 and if phone didnt boot use 3 button ( up + down + power ) for 1 minute or more and it must boot , it did work for me .
Click to expand...
Click to collapse
Which 7.2.4 please??
[email protected] said:
Which 7.2.4 please??
Click to expand...
Click to collapse
hope it work for u . i read some people + me got device booted with this .
gemini_global_images_V7.2.4.0.MAAMIDC_20160129.0000.14_6.0_global
you can download from xiaomininja just search in google
xmmn said:
hope it work for u . i read some people + me got device booted with this .
gemini_global_images_V7.2.4.0.MAAMIDC_20160129.0000.14_6.0_global
you can download from xiaomininja just search in google
Click to expand...
Click to collapse
not worked
Nbkdnssr said:
I just got brick yesterday and followed those instructions. It really worked. I was finally able to flash china dev 6.11.10. Latest dev said just "missed hello packet".
MiFlash version 2016.04 and china dev 6.11.10 was right combination for me. I connected Mi5 to PC while pressing vol- and power buttons, then I released them. I opened miflash, selected rom and chose "flash all". Flashing was completed. I tried to power on my phone pressing power button but nothing. But when I pressed vol- and power, I was able to get to fastboot mode. Rest is history. I flashed TWRP, booted to it and flashed LineageOS again.
Hope it works for you too!
Click to expand...
Click to collapse
im not able to find the rom... could you help me?
[email protected] said:
im not able to find the rom... could you help me?
Click to expand...
Click to collapse
Sorry, it was global dev 6.11.10 that I used, not china dev.
I downloaded it via this link: http://xiaomininja.com/2016/11/11/m...1-10-is-out-download-it-here-for-your-device/
Nbkdnssr said:
Sorry, it was global dev 6.11.10 that I used, not china dev.
I downloaded it via this link: http://xiaomininja.com/2016/11/11/m...1-10-is-out-download-it-here-for-your-device/
Click to expand...
Click to collapse
Thanka for your hel but finally not worked...
Did you already tried to pressing and hold vol up + power button then at the same time repeatedly pressing vol down button until mi logo appear..?, id not yet..just try this method repeatedly.
JJeamy said:
Did you already tried to pressing and hold vol up + power button then at the same time repeatedly pressing vol down button until mi logo appear..?, id not yet..just try this method repeatedly.
Click to expand...
Click to collapse
I am trying that but screen is istill black.. maybe is a hardware issue? it is weird having flash working fine, isn´t it?
[email protected] said:
I am trying that but screen is istill black.. maybe is a hardware issue? it is weird having flash working fine, isn´t it?
Click to expand...
Click to collapse
Yup..it's weird thing...i suspect there's a hardware issue too..
But anyway..did you already tried to flashing fastboot rom with QFIL (qualcomm tool) too..?, if not yet..just try it..you can follow tutorial from this youtube here , just bypassing the step for installing any driver if your phone already detected as qualcomm port in your pc.
I try this method to get back my friend Mi4c from dead with condition like this too..just edl or qualcomm port while connect in device manager, then after flashing with this tool..i've try to power on with vol up + power and repeatedly vol down method above..then mi logo appear.
Hope your phone get back turn on soon..
JJeamy said:
Yup..it's weird thing...i suspect there's a hardware issue too..
But anyway..did you already tried to flashing fastboot rom with QFIL (qualcomm tool) too..?, if not yet..just try it..you can follow tutorial from this youtube here , just bypassing the step for installing any driver if your phone already detected as qualcomm port in your pc.
I try this method to get back my friend Mi4c from dead with condition like this too..just edl or qualcomm port while connect in device manager, then after flashing with this tool..i've try to power on with vol up + power and repeatedly vol down method above..then mi logo appear.
Hope your phone get back turn on soon..
Click to expand...
Click to collapse
Can you help me to find a correct ROM to try?
[email protected] said:
Can you help me to find a correct ROM to try?
Click to expand...
Click to collapse
You can try this official global stable fastboot rom that's still based android 6.0 here
If above direct link doesn't work..just visit this link , then choose "Xiaomi Mi5 Global Stable or China Stable Version Fastboot File Download..
If getting error while flashing..just put extracted folder of fastboot rom in the root of your system..ie C:\[folder_fasboot_rom]
Hi all,
After a million tests, now the phone is able to go to fastboot mode easly just pressing power&volume- (even having a black screen...) Any idea to see if this is still worth to fight?
Regards!
[email protected] said:
Hi all,
After a million tests, now the phone is able to go to fastboot mode easly just pressing power&volume- (even having a black screen...) Any idea to see if this is still worth to fight?
Regards!
Click to expand...
Click to collapse
Just try typing command "fastboot oem device-info" to see the status of your bootloader...is it still at unlocked or already relocked..?
If still at unlocked state..you can flashing fastboot rom with miflash tool.
Anyway what about QFIL method above that i said before..?, any change happen after flashing with this tool..?
[email protected] said:
not worked
Click to expand...
Click to collapse
Did you test it?
Keyvannn said:
Solved with this way
Originally Posted by adwinp
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fu...ni&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
------
I do this way several time but with updated miflash and fastboot rom and nothing happen.
But with this mi flash and global stable 7.2.4 and only selected #all flash#
My phone flashed
Im very happy
Thanks alot
Sorry for my bad english
Click to expand...
Click to collapse
Keyvannn said:
Did you test it?
Click to expand...
Click to collapse
I tried this and not worked for me...
JJeamy said:
Just try typing command "fastboot oem device-info" to see the status of your bootloader...is it still at unlocked or already relocked..?
If still at unlocked state..you can flashing fastboot rom with miflash tool.
Anyway what about QFIL method above that i said before..?, any change happen after flashing with this tool..?
Click to expand...
Click to collapse
I havent tried yet QFIL, but I will and let you know... Thanks so much!
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan
TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm
TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me
Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon
Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing
hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha
KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files
I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.
KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?
yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot
Damn!! I hope you find some way to fix your device. Good luck.
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?
yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working
tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS
Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.
What do you mean it doesn't work?
Can't enter into fastboot mode?
gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...
gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today
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.