Related
Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
MarvinFS said:
Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
Click to expand...
Click to collapse
Why not contact the CM team?
donalgodon said:
Why not contact the CM team?
Click to expand...
Click to collapse
Would you be so kind to point the correct way to contact 'em on that particular matter?
MarvinFS said:
Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
Click to expand...
Click to collapse
Yes i know, its like by LG's, while pushing vol + and vol - just plug the usb cable, but thats where im stuck too. We need the right drivers for that, find 5's drivers wont work, tired already. As you know without right diag drivers, we cant go to next level, hope youll help here
os_man said:
Yes i know, its like by LG's, while pushing vol + and vol - just plug the usb cable, but thats where im stuck too. We need the right drivers for that, find 5's drivers wont work, tired already. As you know without right diag drivers, we cant go to next level, hope youll help here
Click to expand...
Click to collapse
Actually we do have drivers, in a preloader mode the device is detected as
Qualcomm HS-USB Diagnostics 9008
the drivers are here
https://yadi.sk/d/Um0Nk1FIWR6vK
or here
https://yadi.sk/d/5XdeaZFvMBpQ6
but QPST is not working - MDM port is not opened! One guru from our Russian forums found a way to open MDM port, but for ZTE Nubia phones... and it's not working with OnePlus. Needs further research!
Actually all Qualcomm based devices must be somewhat similar in terms of low level flashing!
MarvinFS said:
Actually we do have drivers, in a preloader mode the device is detected as
Qualcomm HS-USB Diagnostics 9008
the drivers are here
https://yadi.sk/d/Um0Nk1FIWR6vK
or here
https://yadi.sk/d/5XdeaZFvMBpQ6
but QPST is not working - MDM port is not opened! One guru from our Russian forums found a way to open MDM port, but for ZTE Nubia phones... and it's not working with OnePlus. Needs further research!
Actually all Qualcomm based devices must be somewhat similar in terms of low level flashing!
Click to expand...
Click to collapse
About ZTE Nubia phones you can ask me everything, i can even write imei to them, ZTE GRAND S II too, and no, they are different. QPST is not working becouse cant connect to the phone in download mode ( sees in download mode ). I will try these drivers now too, if it sees as "HS-USB Diagnostics 9008" might be ok, becouse normaly its HS-USB QDloader 9008 without right driver, if i manualy turn it to 9006, qpst can connect, but this mode is for bricked phones i think ( as in oppo finf 5, in this mode oppo's own service program can write to phone.)
---------- Post added at 07:50 PM ---------- Previous post was at 07:37 PM ----------
Sadly no, i had tried these drivers too, its still QDLoader, not Diagnostic port, we need the diag drivers from the Manufacturer i think, not generic from Qualcom, and i must add i believe this mode is not we are looking for, phone must be online for Qpst to be able to make changes, so we need the right dial code for engineer-service menu (or somewhere hidden in *#808#, all in chineese, still trying to figure it out if its there )
---------- Post added at 08:04 PM ---------- Previous post was at 07:50 PM ----------
"I'm making a preparations to help revive hardbricked phones", can be used if phone is bricked maybe, to download all the sytem to the phone again ( as in Oppo Finf 5 same example again ), but i need a working Qpst that actualy connect to phone "online".
---------- Post added at 08:40 PM ---------- Previous post was at 08:04 PM ----------
pm me for further instructions please..
i install twrp after unlock bootloader , i flashed stock rom but i forgot to wipe system , data before flashed
My device's No Fastboot, No recovery, No Display, hard bricked
i's only vibrate when i press power button
red blink when connect usb cable
anyone has same problem? help me pls..
Same here. But i have yet to find anyone to get it past the black screen.
.
when you try to boot into recovery.. try to. hold the vol up button for a sec after it it should have loaded.. that whats mine was doing.. black screening
Any news? My device also bricked.
Me to, I got stuck in updating firmware process or corrupted firmware file. I'm also stuck with black screen no recovery, Fastboot mode, computer won't recognize device, phone just blinks red notification light when cable plugged in, power button vibration, also looking for fix. The phones only week old, had to buy another one. I'm now stuck with the new device can't get into twrp just presented a black screen when booting into twrp, only way to get into twrp is with adb, fastboot/boot/twrp.Img which sucks really like the device
Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?
Roxy34 said:
Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?
Click to expand...
Click to collapse
I've been working on a similiar issue on a ZU680KL for a friend of mine for a few months now. I ended up buying a USB-C type of an EDL cable. I am able to get some software's to better recognize the phone now including Xiaomi's MiFlash, and have found variations of the files that QPST wants when trying it as a solution, but the raw flash programmer file's I have found, though for right chipset, or probably intended for other devices are the partition tables for example would all be different. This whole project to me as I just recently described it, feels like trying to glue a shattered light bulb back together using liquid glue like the kind they use to have us use in Elementary school on paper projects, and to make it more fun, every time you look away, someone's throwing away more and more of the puzzle pieces on us. lol. Frustrating as all hell. It's as if Asus never wanted or intended for us to restore these phones from an EDL or low level NVRAM status. Wish I had the exact answer. Plan to waste a few hours of today on it again though, being how I found this thread researching it some more. Good luck to all.
solved? I have easy way to fix
regards
grean said:
solved? I have easy way to fix
regards
Click to expand...
Click to collapse
what's easy way to fix? thanks^_^
If you watch YouTube videos, you find virtually nothing. There is one Portugese video, but they never show the phone in a completely dead state of black screen with a couple vibrations & an occasional blinking light. This state is truly bricked. There are a couple fake videos also, wanting you to just look at stuff, but it's just a stupid ad. We have one working Zenfone 3 ultra, & one seriously did one. I've offered 100's of $$ to anyone to bring it back to life, & have received ZERO takers. Anybody who's not insane can understand what that means. In other words, so far, forget it. No one has been able to unbrick this model. Only the other Asus models. This Asus model has relatively few purchasers - & has even fewer people willing to mess with it. What a shame.
.
Hello, if someone has a working zu680kl device we could extract the necessary image and fix it using this tutorial:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I think it looks very promising.
I also have a bricked zu680kl device and I don't think about to give it up !!!!
We have a working one, but my better ½ is not about to give it up for an experiment.
.
hillg001 said:
We have a working one, but my better ½ is not about to give it up for an experiment.
.
Click to expand...
Click to collapse
I think there is no risk to brick the device because there will be no installation of any kind of firmware at all. The only thing is to make a backup of all app data because a fresh clean device (factory reset) is necessary. If you like to have a look at the whole procedure search for
Guide, if you are NEW “Qualcomm HS-USB QDLoader 9008” MODE
on the mentioned page
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
If it would be possible to get the eMMC image I would try to go through the rest of the process. Maybe this brings back our dead devices to life.
Buy your better 1/2 some flowers before you ask
I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!
luckychild said:
I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!
Click to expand...
Click to collapse
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip
gubbilo144 said:
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip
Click to expand...
Click to collapse
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
deadmatrix said:
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
Click to expand...
Click to collapse
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Were do run the ftm-flashall.cmd in qfil or adb
gubbilo144 said:
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
Were do run the ftm-flashall.cmd in qfil or adb
Click to expand...
Click to collapse
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.
deadmatrix said:
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.
Click to expand...
Click to collapse
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive
gubbilo144 said:
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive
Click to expand...
Click to collapse
Glad to hear it! So we have a now reproducable cure after years of nothing in the pipe really. I am thinking of writing a start to finish post of how to deal with it for beginners that can be pinned by a mod. If someone else wants to beat me to this, feel free - especially since I don't actually even own this model of phone.. Might maybe pick it up though.
I have win 10 in test mode.
Device manager shows a windows driver.
It won't let me run the qualcom driver.
"Windows has determined that the best driver is installed"
Any way around this?
Any way around this, if i brick my phone i won't be able to use the awesome megabrick tool. [email protected]#$ microsoft.
In devices and printers it show as windows phone, in device manager under portable devices it shows as oneplus 6003 very strange. Either way same message.
Think you need to slow down a bit, start again....none of this made any sense!
I think he is trying to instal the ADB driver in Windows?
Just put the phone in Qualcomm download mode like you would to use the unbrick tool and see what happens in the device manager. Look for "Qualcomm HS-USB QDLoader 9008" device. If it shows up then the unbrick tool will work if not install the drivers
I got the same message. The msmtool worked nevertheless.
for the msmtool you're shutting down your phone and connecting it with vol down(?) held down, see what device it'll show up as at this point. i've got adb, fastboot, qualcom and op6 drivers all working as they should atm, what device shows up depends on the current state of the device
snigor said:
for the msmtool you're shutting down your phone and connecting it with vol down(?) held down, see what device it'll show up as at this point. i've got adb, fastboot, qualcom and op6 drivers all working as they should atm, what device shows up depends on the current state of the device
Click to expand...
Click to collapse
Dear Sir (& whomever else can help),
I flashed the newest Oxygen rom update for my oneplus 6 and rebooted from the TWRP. It however appears that the flashing i did didn't really work and there was really no rom installed because i had earlier formatted system, dalvik and data with the intention of starting anew with the new rom. Therefore, the phone could only boot into fastboot. The device is not detectable via windows adb but by fastboot command line (adb, fastboot and oneplus 6 drivers had long been on my pc). However, attempts to use TWRP img to reboot the phone into TWRP throws up these:
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.661s
I download enchilada_22_O.27_181025.zip which contains MsmDownloadTool V4.0.exe and MsmDownloadTool V4.0_factory.exe, alongside enchilada_22_O.27_181025.ops. Running the non-factory msm.exe, it does not seem to be doing anything nor detecting the phone.
On downloading the said Qualcomm drivers for the PC, there is a problem with installing it. There is no .exe or any other executable file. Moreover, since my phone has long had the necessary drivers, adb and fastboot installed and was easily detectable even in fastboot, the Device Manager of Windows does not see it as a device in need of (new) drivers and ignores my efforts to get it to "update" the existing driver for the "Kedacom" device (this is the way it sees it when in fastboot).
Also, no amount of power and/or volume button pressing (singly or in combination) alters the boot pattern into fastboot or the status quo. I don't know how to get the msm tool to work. Please help me.
Thank you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
Filgaliel said:
I got the same message. The msmtool worked nevertheless.
Click to expand...
Click to collapse
Dear Sir,
Please how do you use the msm tool? I ran it but it only showed blank cells in its table. Pressing "Start" (while in its self-selected "upgrade" mode) only showed Running:upgrade in its status. Nothing really seemed to be happening.
Please how am i supposed to use it, eg confirm communication with device, etc.
Thank you.
It has only just occurred to me that the msm tool version i used may not be exactly that of the one that worked for you. Could you upload your version without the rom, and give me its link? I already have a rom (.ops type) from the one i already have and don't have sufficient internet data for another such large download.
Thanks again.
Phone Now Detected, But... "Param Processing"
Chris Kerry said:
Dear Sir (& whomever else can help),
I flashed the newest Oxygen rom update for my oneplus 6 and rebooted from the TWRP. It however appears that the flashing i did didn't really work and there was really no rom installed because i had earlier formatted system, dalvik and data with the intention of starting anew with the new rom. Therefore, the phone could only boot into fastboot. The device is not detectable via windows adb but by fastboot command line (adb, fastboot and oneplus 6 drivers had long been on my pc). However, attempts to use TWRP img to reboot the phone into TWRP throws up these:
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.661s
I download enchilada_22_O.27_181025.zip which contains MsmDownloadTool V4.0.exe and MsmDownloadTool V4.0_factory.exe, alongside enchilada_22_O.27_181025.ops. Running the non-factory msm.exe, it does not seem to be doing anything nor detecting the phone.
On downloading the said Qualcomm drivers for the PC, there is a problem with installing it. There is no .exe or any other executable file. Moreover, since my phone has long had the necessary drivers, adb and fastboot installed and was easily detectable even in fastboot, the Device Manager of Windows does not see it as a device in need of (new) drivers and ignores my efforts to get it to "update" the existing driver for the "Kedacom" device (this is the way it sees it when in fastboot).
Also, no amount of power and/or volume button pressing (singly or in combination) alters the boot pattern into fastboot or the status quo. I don't know how to get the msm tool to work. Please help me.
Thank you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
Dear Sir,
Please how do you use the msm tool? I ran it but it only showed blank cells in its table. Pressing "Start" (while in its self-selected "upgrade" mode) only showed Running:upgrade in its status. Nothing really seemed to be happening.
Please how am i supposed to use it, eg confirm communication with device, etc.
Thank you.
It has only just occurred to me that the msm tool version i used may not be exactly that of the one that worked for you. Could you upload your version without the rom, and give me its link? I already have a rom (.ops type) from the one i already have and don't have sufficient internet data for another such large download.
Thanks again.
Click to expand...
Click to collapse
I finally found out why i could not get the PC device settings to see my oneplus 6 as Qualcomm device. I held the up vol. button for only 5 secs (as directed). In one of my retries, I was distracted in answering someone, thus holding for at least 15 secs before plugging it to the PC. The msm tool now detects it and connects: one cell in its table shows COM Connected.
However, on pressing start, it gets stuck on "param processing" (after some firehose commands) at around 5 - 7 secs. Need help please.
So after I installed the Official Android 10 GSI just out of curiousity, it worked and the only reason I didn't stay with it was because it didnt have the new gestures and no lockscreen options. Everything else worked amazingly.
At this point I just wanted to install LineageOS and root but the phone kept rebooting to TWRP over and over no matter what I'd flash and no matter how many times I wiped it kept rebooting until it eventually got no response at all.
I tried everything restoring back up nothing, when I tried just flashing the zip file the recovery screen just kept flashing then rebooted back. I cannot save this for life of me I am left with a paperweight.
Ive tried the classic Moto G force restart trick but no luck in anything. No matter what I tried now it wont respond to any button presses. Am I just screwed? I'm waiting 24 hours before trying again while plugged in. What am i to do?
Metro By T-Mobile Variant if that helps at all
uHeash said:
So after I installed the Official Android 10 GSI just out of curiousity, it worked and the only reason I didn't stay with it was because it didnt have the new gestures and no lockscreen options. Everything else worked amazingly.
At this point I just wanted to install LineageOS and root but the phone kept rebooting to TWRP over and over no matter what I'd flash and no matter how many times I wiped it kept rebooting until it eventually got no response at all.
I tried everything restoring back up nothing, when I tried just flashing the zip file the recovery screen just kept flashing then rebooted back. I cannot save this for life of me I am left with a paperweight.
Ive tried the classic Moto G force restart trick but no luck in anything. No matter what I tried now it wont respond to any button presses. Am I just screwed? I'm waiting 24 hours before trying again while plugged in. What am i to do?
Metro By T-Mobile Variant if that helps at all
Click to expand...
Click to collapse
Connect to a PC
In Device Manage
If phone is shown as
QHSUSB_Bulk or qloader
It's in emergency download mode
You will need a Blankflash file or a mmcblk0.img
sd_shadow said:
Connect to a PC
In Device Manage
If phone is shown as
QHSUSB_Bulk or qloader
It's in emergency download mode
You will need a Blankflash file or a mmcblk0.img
Click to expand...
Click to collapse
Hi my phone stay in bootloader but dont work, fbank flash say waiting for devices, and qhusb or qloader dont appear in my pc, help me
iFelipe97 said:
Hi my phone stay in bootloader but dont work, fbank flash say waiting for devices, and qhusb or qloader dont appear in my pc, help me
Click to expand...
Click to collapse
You cannot use a blankflash if device is in fastboot mode
Sent from my ali using XDA Labs
---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Sent from my ali using XDA Labs
sd_shadow said:
You cannot use a blankflash if device is in fastboot mode
Sent from my ali using XDA Labs
---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Please help me flash stock firmware not work for me error remote failured
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!🤭
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps