[HELP] Z380KL stuck in qhsusb_bulk mode - Asus Zenpad 8.0 Questions & Answers

I accidentally flashed my Z380KL (P024) with stock ROM using TWRP, and now the tablet won't boot. The tablet is only recognizable under qhsusb_bulk mode. There is no ASUS logo, and the screen won't turn on. I have all the necessary tools ready, including Tool Studio, eMMC DL and QFIL, but I have trouble finding the stock ROM including the mbn or the rawprogram.xml file, and there is not enough resources on the net. I looked up some blogs and they told me to have a backup of someone's eMMC backup, but I can't seem to find one online. Any help is much appreciated.
Also I have a TWRP backup of the LineageOS ROM earlier if that helps.
Does anyone have the full firmware for Z380KL? The one that contains rawprogram.xml, patch.xml and such

Related

[Q] Only Fireware Update Screen Appears

Hi,
first of all, thanks for reading this thread.
My problem is the following:
I rooted my device and wanted to flash a CWM over the Rom Manager and got a Success Message. The custom recovery apperantly didn't work. Now I am stucked in the Firmware Update Screen (no fastboot, no ADB, no reboot)
I looked up the "General" many different options including this thread http://forum.xda-developers.com/showthread.php?t=2582142, but I couldn't find any files for my specific model. Can anybody provide me those.
I had the Software D80220H
I tried the LG Mobile Support with the stock reset as well as the LG Flash tool 2014 with the corresponding files from here. All these options stopped working between 33% and 40%. The LG Flash Tools (for .dz Files) doesn't recognize my device at all
Does anybody can provide help ?
Thanks in advantage.

Unbrick and Full system backup *.bin?

First, apologize for poor English.
Does anyone have full system backup as single img or bin file? Accidentally flash ZUK Z1 rom when porting MIUI8 and now my device is bricked, and partitions is a mess. QFIL doesn't allow me flash because detect ZUK device. Is anyone kind enough to make backup with EMMCRAW_1.4.0.0 or something similar? It's important to be a software without model check, just simple raw copy as single file.
update: Things goes worst. Tried to save it with Qfil but it fail, Miflash fail too and ruined my partitions. Long story short, now my device doesn't boot, blank screen, windows XP,7 and 10 recognize Qualcomm 9008 mode if i power it on without battery. With plugged battery recognized as Linux CD...something, without partitions. ADB and Fastboot doesn't work on any case. On many tries, Qfil accept only ZUK Z1 rom, flashing fine but doesn't boot off course. If i start QPST Configuration tool, it detects port but progress bar loading and never goes full, EMMC Software Download tool fail too. So, i'm asking for advice.
I found a friend with the same phone and make raw system dump, but result is same, only Qualcomm 9008 mode. Is my mainboard broken?
Did you try with older qfil? QPST ver2.7.422?
maybe this help
Krasimir said:
First, apologize for poor English.
Does anyone have full system backup as single img or bin file? Accidentally flash ZUK Z1 rom when porting MIUI8 and now my device is bricked, and partitions is a mess. QFIL doesn't allow me flash because detect ZUK device. Is anyone kind enough to make backup with EMMCRAW_1.4.0.0 or something similar? It's important to be a software without model check, just simple raw copy as single file.
update: Things goes worst. Tried to save it with Qfil but it fail, Miflash fail too and ruined my partitions. Long story short, now my device doesn't boot, blank screen, windows XP,7 and 10 recognize Qualcomm 9008 mode if i power it on without battery. With plugged battery recognized as Linux CD...something, without partitions. ADB and Fastboot doesn't work on any case. On many tries, Qfil accept only ZUK Z1 rom, flashing fine but doesn't boot off course. If i start QPST Configuration tool, it detects port but progress bar loading and never goes full, EMMC Software Download tool fail too. So, i'm asking for advice.
Click to expand...
Click to collapse
try volume down + power and try formating everything fro that menu
K920
Hi,
I have exactly the same problem. Did you resolve it?

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.

Asus Zenpad Z380M Wont turn on or boot to any mode after attempted magisk root with locked bootloader

Okay, Let me explain exactly what I did here... I first flashed Twrp using SP flash tool which worked without too much problem. Then I attempted to install the latest super su zip which told me the boot.img was already patched and it could not find a ramdisk... So I moved on and flashed the latest Magisk zip which flashed no problem. Rebooted the device and it came up with a red boot state telling me it would boot in 5 sec. It did not boot at all. Turned off the tablet and rebooted into twrp again. I then flashed the OTA update system.img, boot.img, and re-flashed twrp from twrp itself instead of the SP flash tool. It booted into twrp no problem, however now it said it could not mount the system partition. I did a full data wipe, factory reset, rebooted into twrp again. Same issue. So I attempted to re-flash the firmware with SP flash tool. Did not notice i had it set to format and download and not only download. It said formatting for maybe 2 sec and gave me an error. Now the device will not turn on at all... no screen whatsoever, no recovery, etc... I have had no luck getting the asus flash tool to even recognize a com port however SP flash tool seems to be able to flash the device no problem. I extracted the .raw firmware file I have for the latest firmware, modified the scatter file to allow flashing all partitions, and I did a full firmware flash of the device using SP flash tool. However it still does not turn on... it does nothing... So I'm assuming that I accidentally formatted over the bootloader... And I cannot find a bootloader flash file for this device anywhere... So I'm stuck with an Asus ZenBrick... Does anyone know a way to fix this issue? When I plug the device into my computer and open device manager it switches between the preloader and mtk serial port very quickly not staying on either one very long. I'm assuming this is why I cant get the asus flash tool to work and SP flash tool works off just the initial preloader. I just bought this tablet from someone and managed to hard brick it in less than a days time... Any help at all with a way to revive this device will be greatly appreciated. Thank You in advance to anyone who tries to help me fix my mess up.

onn 100003561 stock restore

I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
sethfoxen said:
I don't know how to leave well enough alone, and I've been working on the Onn 8" Pro (100003561) tablet trying to at least get root. I managed to unlock the bootloader, but was unable to use SP Flash Tool to dump my own boot.img, so I picked up one I found online that I'm pretty sure is from an older firmware version (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) and now it keeps giving me errors, bluetooth crashing, etc, even after a factory restore from the recovery.
I CANNOT get SP Flash Tool to load the scatter file that deadman was using in his comment (https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/page-9#post-82619259) it just gives me an invalid scatter file error. I just want it back to factory, start all over, but no matter what I do I can't figure out how to flash deadman's firmware file, or ANY firmware backup for that matter. I keep getting scatter file errors, and SP Flash doesn't even wanna find my device. I've got the drivers installed properly, it shows up as "MediaTek PreLoader USB VCOM (Android) (COM3)" in my device manager. I've tried changing the COM port, running the flash tool in compatibility mode for Windows 7 (I'm on Windows 11 btw) running it as admin, and nothing. I can get an empty scatter file from WWR 2.51 to load in flash tool, but when I plug my device in it just does nothing. If I unplug my device, it gives an error that says "BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)".
I can get into fastboot mode, but I can't open the settings in the normal boot because it instantly crashes to the ONN boot logo whenever I open anything. I'm at a complete loss here.
Click to expand...
Click to collapse
Ugh, I feel so stupid. I FINALLY got SP Flash to recognise my device, by FOLLOWING THE DIRECTIONS :eyeroll:
So yes, you DO have to tear the back off of the tablet, and unhook the battery before you can do anything.

Categories

Resources