Database Users

[Q] Boot verified failed and APX driver problem

Hi!
I have tried to flash unlocked bootloader V3 from civato's guide, and I could not pass step 6 (flashing bootloader with nvflash or blacthund3r's tool). None of this method didn't work (Nvflasher didn't flash anything, and blackthunder tool was stuck at formating some partition (can't remeber which one).
Last successful step was flashing ICS rom (full leaked version of 1.031.00).
After that I could boot up, and rom worked all fine.
But, after that, I got my self in trouble.... I pressed Vol- & PWR, tablet did his thing, and when reeboted, I got stuck in Acer logo screen with red writing "Boot verified failed"
I understand that I have messed boot somehow... And to fix this i have to flash new bootloader through nvflash and apx mode. I tried to put update.zip on sd card, but it didn't helped (I still get boot verified failed)
Here, I got another problem. When I have connected tablet in apx mod to pc, i got message "driver not installed". Now, in devices I have "unspecified APX device".
BTW, adb doesn't see my device?!
I hope that You guys can help me with these problems, so that my tablet is operational an running again.
Thanks in advance!

boot verified
I have the same problem but I can not find the v3 bl and CWM Recovery Package to flash with the apx flash utility. If you find them let me know.
This what you have do:
Your recovery is borked so u have to put a new one on there, the best way to
go about doing this is to:
Download the V3 AND CWM Recovery package and apxFlash that.....Done!!
your need to flash the WHOLE PACKAGE b/c ARI reports yr BL as plain old stock
You cannot replace the failed recovery with CWM with the plain old stock BL!!
You have to flash the patched BL as well, so again
You must flash the whole pckg just like in the guide OK
if later u want the stock recovery back u can use ARI to do that but after the apxflash!!!

Thanks for your replay! I'l try to do this and hope it will work...
By "WHOLE PACKAGE" you mean unlocked bootloader and CWM? Or, something else?
Check this thread for V3 and CWM.

boot verified
Yes "WHOLE PACKAGE" unlocked bootloader and CWM
The tread you sent me I do not know how to use the nvflash never works for me.
I have been trying for 3 days and no luck.
Let me know if it works for you or how you make out

zozo10k said:
Hi!
I have tried to flash unlocked bootloader V3 from civato's guide, and I could not pass step 6 (flashing bootloader with nvflash or blacthund3r's tool). None of this method didn't work (Nvflasher didn't flash anything, and blackthunder tool was stuck at formating some partition (can't remeber which one).
Last successful step was flashing ICS rom (full leaked version of 1.031.00).
After that I could boot up, and rom worked all fine.
But, after that, I got my self in trouble.... I pressed Vol- & PWR, tablet did his thing, and when reeboted, I got stuck in Acer logo screen with red writing "Boot verified failed"
I understand that I have messed boot somehow... And to fix this i have to flash new bootloader through nvflash and apx mode. I tried to put update.zip on sd card, but it didn't helped (I still get boot verified failed)
Here, I got another problem. When I have connected tablet in apx mod to pc, i got message "driver not installed". Now, in devices I have "unspecified APX device".
BTW, adb doesn't see my device?!
I hope that You guys can help me with these problems, so that my tablet is operational an running again.
Thanks in advance!
Click to expand...
Click to collapse
Did you install acer usb drivers.

EDIT: SOLVED!
Mods, you can close this thread.
shaun298 said:
Did you install acer usb drivers.
Click to expand...
Click to collapse
Hi!
Yes, I have dl the drivers from Acer site and installed them. But pc only recognize tab in APX mode. And adb doesn't see my tab.
Every method that I have tried (APX flash tool and nvflash) hangs at some part. APX flash tool hangs at "Flashing bootloader EBT - stage two, and nvflash hangs at formating partition 4.

Hi, I´m having similar troubles to get acer drivers working on windows 7 32. I installed newest acer web drivers, ADB works OK. When I get to apx mode I need to manually point to drivers, I have an APX driver with a sign and turns to Acer Picasso USB Boot-recovery driver. The problem is that not any of the tools sees this as a connected tablet in apx mode (afterota or apxflash).
I am doing something wrong? I know a500manager shows me the tablet is in apx mode "please install drivers" when i get APX driver with Sign, after installing the driver manually it just doesn´t show connected anymore.
thanks

hernborc said:
Hi, I´m having similar troubles to get acer drivers working on windows 7 32. I installed newest acer web drivers, ADB works OK. When I get to apx mode I need to manually point to drivers, I have an APX driver with a sign and turns to Acer Picasso USB Boot-recovery driver. The problem is that not any of the tools sees this as a connected tablet in apx mode (afterota or apxflash).
I am doing something wrong? I know a500manager shows me the tablet is in apx mode "please install drivers" when i get APX driver with Sign, after installing the driver manually it just doesn´t show connected anymore.
thanks
Click to expand...
Click to collapse
Download and install the Google USB drivers.
Google.... Android USB Drivers, and you should get the page for the Android SDK with google drivers.
In Apx mode, go to device manager on your PC, and manually install the drivers. Don't let it search automatically, do it manually. If you get a compatibility warning, ignore it.
Should hook you up with normal, ADB and APX drivers.

zozo10k said:
EDIT: SOLVED!
Mods, you can close this thread.
Hi!
Yes, I have dl the drivers from Acer site and installed them. But pc only recognize tab in APX mode. And adb doesn't see my tab.
Every method that I have tried (APX flash tool and nvflash) hangs at some part. APX flash tool hangs at "Flashing bootloader EBT - stage two, and nvflash hangs at formating partition 4.
Click to expand...
Click to collapse
THANKS FOR NOT TELLING US HOW YOU SOLVED IT:good::good::good::good:

SM-A500FU can't be detected by a PC, booting into recovery boots the system.

Hello,
I have installed a custom rom (Marshmallow) for my SM-A500FU through the adb. Now when I want to install a different rom I have to either boot into TWRP and I can't do that because booting into recovery simply restarts a phone, or I have to boot into Download mode and install it with the adb. The problem is that when the system is running, the phone simply charges, no Windows notifications or devices appear and when the phone is in Download mode Windows detects that a device is plugged in but can't recognize it. I have all the adb drivers, KIES and all that so it's not a problem. Can I somehow boot into TWRP or make Windows recognize my phone so I can use adb?
Thanks.

before installing a rom, have you wiped system, cache, dalvik and data? If yes try with a hard reset and if it doesn't work, too flash stock firmware

Hey,
yes, I wiped everything, I have flashed many roms earlier and I believe I have flashed it properly. I have managed to get into TWRP so I can actually flash FWs. I have only updated my rom to the newest CW13 build there is for my A5. Is there any way to flash a stock FW (for example a XEO KitKat) without ODIN? I can only use ADB through TCPIP and TWRP, so there is no way for me to flash it through ODIN.
Thanks.

so, if you press power+home+vol- it doesn't reboot in download mode, right?

It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.

whzq said:
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
Click to expand...
Click to collapse
Well, you can't flash samsung firmwares with twrp. Try flashing another rom through twrp

Alright, I have tried to flash multiple ROMs. Currently sitting on a Lollipop. Nothing changed, though. On every single ROM the problem still persists. It's not a problem with the PC as I've tried to connect my A5 to a laptop with freshly installed Windows and KIES and it behaved the same way as on my PC. The cable is fine as well, I have tested it with my old SGS3, it worked just fine on both my PC and laptop. Frankly, I have no idea what to do next, I'm starting to think that the port is physically broken. It's weird though, as I can still charge my phone and there is a response when the phone is in Download mode, just that Windows can't recognize it.

Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?

zyxw-androidiani said:
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
Click to expand...
Click to collapse
Yes, ihlf his device can boot he can use mobile odin. Have you tried with other PCs, just to see it isn't a problem of your pc?

In my experience usb device descriptor errors are related to the specific PC the error occurs on due to device driver conflicts, but if you get the same error on another pc then it could be the hardware.
I'd certainly be trying another cable first on a fresh PC.
Anyway regardless of all that you can flash the stock firmware with FLASHFIRE available on play as long as you have root.
Sent from my SM-T280 using XDA-Developers mobile app

Unable to install qualcomm driver for Lenovo a6000 plus

I was trying to install custom rom and my device got bricked, now its stuck in boot logo. I am trying to install a rom but tried with qfil/qspt but device is not getting detected. Once I was able to install qualcomm hs-qd loader 9008(com 3) but it was not working so I removed it and now I am unable to install it again.
I tried to enter the recovery mode by flashing TWRP recovery, My device was prerooted and already i had install TWRP but a device was brick I was unable to access it. After flashing TWRP, I got the Mount screen of teamwin but touch is not working.its saying unmodified system partition detected. but after that I am unable to got to next step to install a rom in my device as qualcomm hs-qd loader 9008 not getting installed. Please guide me, I am new in all this,need expert help. thank you

@amitpandey, have a look AT THIS.

Still not detecting by my pc. Also unable to disable driver signature as in my laptop no option of troubleshooting option available in advance startup menu.

Dead Kipper!

Hi all, my Wileyfox Storm has more or less died, ironically it happened soon after (with much help from these forums) I got my Axon 7 going on Lineage OS
Anyways, my Storm was running well on Lineage 14.1 nightlies, had TWRP installed and was rooted. It stopped overnight.
Now it only starts in Bootloader mode. I can flash and reflash a (TWRP) recovery.img via fastboot mode from a PC, although I can't boot to it. I can't access the phone in adb mode.
I've been unable to find a Lineage system.img to flash. Miflash sees the phone as a Qualcomm 9008 device but will not write to the phone any Lineage or CM13 zip file I can find. I haven't been able to find a zip that will flash via fastboot.
I've also tried the Qualcomm QFIL software (worked well on the Axon 7) with no success. It doesn't find the port the phone is on, a driver issue, but I haven't been able to force a driver for this to succeed. I've trawled many threads looking for answers, but have ended up starting this new one.
So all advice very gratefully received : )

OnePlus5 soft brick?! Bootloader fine but TWRP not working, can't sideload ..

Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K

Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!

on my phone TWRP shows no files on in any folder. can you pls help?

krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method

Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.