Database Develop

achieve APX mode and other tricks adhoc

Since this model is new, i assume all facts are new too.
- SAFE mode is started by holding Vol+ and power button at the same time at startup.(adb shell is enabled, nothing is running(single user mode?)
- FIRMWARE upgrade mode seems to be Vol- with USB cable connected at power-on.
- APX mode is started by holding Vol+ and Vol- down at the same time at power up(when pressing power).
* since we do not have a bootloader.bin yet, it will be hard to try anything. can we use htc onex bootloader.bin?
* tegra3 is also locked with a SBK, which we do not have either (i believe).
-Battery mode
Turn off mobile. attach USB cable to pc and mobile. turn on mobile.
- adb reports shell not found and some root details?
im still digging into the fastboot mode, so information can be extracted on the rom rel. etc.. maybe someone already knows?
ill keep this updated, if i find out more.

APX drivers
Do you have APX drivers for 4X ?

not yet, i assume those for asus prime should work as well?

it not work.

@Dexter_nlb
I read that Asus will release NVFlash for Asus Prime.
Do you think it will also work for us?

I believe they for a fully working apx mode since prime got a full recovery using apx mode?

recovery details added.
thanks to 911rsr

updated:
-Battery mode
Turn off mobile. attach USB cable to pc and mobile. turn on mobile.
- adb reports shell not found and some root details?

See also
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/ (for Linux)
http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/ (for Windows)
from http://forum.xda-developers.com/showthread.php?p=26637229

I cannot get my phone to turn on at all. When i plug it into the computer, device manager shows "APX".
I am trying to get into s/w mode... any ideas?
Thanks

faraband said:
I cannot get my phone to turn on at all. When i plug it into the computer, device manager shows "APX".
I am trying to get into s/w mode... any ideas?
Thanks
Click to expand...
Click to collapse
turn off phone
take battery out
hold vol- and put usb cable into phone
if s/w mode starts put battery in and flash kdz

Turbol said:
turn off phone
take battery out
hold vol- and put usb cable into phone
if s/w mode starts put battery in and flash kdz
Click to expand...
Click to collapse
I have tried that. Does not work. Phone screen stays black all the time. No logo, no s/w mode, no recovery. Nothing. Just always black....

Try renoving battery and then press volume down and insert usb cable into pc ther should be sone strange white black lines screen and then leave it for 20 secs
After that try recovery modr and everything again
Posted by a proud owner of a lg p880

raviboy100 said:
Try renoving battery and then press volume down and insert usb cable into pc ther should be sone strange white black lines screen and then leave it for 20 secs
After that try recovery modr and everything again
Posted by a proud owner of a lg p880
Click to expand...
Click to collapse
Nothing happens. Nothing shows on screen. When i hook it to computer, it makes a noise that it found some device, and in device manager shows as APX, instead of as modem or anything else....

Bricked. APX mode only
Did you find how to fix it?. I have the same issue after a failed upgrade using LG mobile support tool.
No SW upgrade mode, no screen or leds activity, no nothing. When is connected to PC, APX device is recognized. I found some drivers and the APX device is displayed now as "NVIDIA USB Boot-recovery driver for mobile devices". I'm stuck there. I was looking into NVflash utility but after the command "nvflash --sync" only get "unknow device found"
Can anybody help me please?.
How can I get into SW recovery mode or something that shows some activity from the phone?.
Thanks and regards

jaob22 said:
Did you find how to fix it?. I have the same issue after a failed upgrade using LG mobile support tool.
No SW upgrade mode, no screen or leds activity, no nothing. When is connected to PC, APX device is recognized. I found some drivers and the APX device is displayed now as "NVIDIA USB Boot-recovery driver for mobile devices". I'm stuck there. I was looking into NVflash utility but after the command "nvflash --sync" only get "unknow device found"
Can anybody help me please?.
How can I get into SW recovery mode or something that shows some activity from the phone?.
Thanks and regards
Click to expand...
Click to collapse
i guess not much can be done. sent mine to the service center and got it back 3 days later fully functional. i guess it's easier to restore for LG since they have all the tools and magic keys.

Hello!
just happened to me.
apx mode you solved anything?
one can solve?
Thank you!

myshu2006 said:
Hello!
just happened to me.
apx mode you solved anything?
one can solve?
Thank you!
Click to expand...
Click to collapse
NVflash doesn't work, at least after upgrade to JB.
Before give your devices as bricked, try to enter in S/W without battery a few times and after with battery on.
Sometimes stressing the device have some results.
But the best you can do is take it to service.

Thanks gingerboy92. I follow your advice and my phone is in a LG service center now. Hope they can fix it.
I think that's the only safe way to recover it. Looks like Tegra 3 devices have security keys that are unique for each processor and without them you can't go further.
Amigo ruedaslocas, I tried many times to do what you say, unsuccessfully. Thanks anyway.
Regards

Phone locked at logo boot, usb debugging disabled

Hi all,
I rooted my phone and unclocked bootloader.
My rom is a stock rom.
I managed to install CWM recovery using lg-optimus-4xhd-recovery-v1.0.apk but something happened.
I rebooted my phone in recovery mode and it is always locked to LG logo.
Pressing Volume up and power I can see normal android system recovery, wiping cache and factory reset don't work.
I haven't usb debugging enable so my computer can't see the phone connected with usb cable, and it's impossible for me flashing the phone with kdz rom methods.
What can I do?
Thx in advance for your answers

No one can help me?
Flashing with kdz results in "phone was not found", is there a way to resolve? I've tried with ubuntu, OS (adb) only see my phone if usb debugging is enabled and it isn't, and with a laptop running win8, installing LG drivers and so on, nothing works.

This is salvagable
If you can get the stock recovery mode, all is not lost, all of the important bits are still functioning.
Power down. Hold VolDn and insert the USB cable. If you get the Software Update screen with a green icon you CAN recover the phone. It may require a battle with Windows to get it to play nice, Windows and USB is always a hit or miss affair; but the phone is ok if that screen appears. Do not use the VolUP + Power LG Recovery mode, there isn't a known tool for that in the wild.
I don't normally run Windows and the couple of times I have booted it to do this it required some hassle and usually skipping the nice way since I had never installed the bundled LG Desktop stuff before things went wrong. So just do what I did, pick the Emergency mode that requires inputting the IMEI instead of letting it detect your phone and then let it fix things for you.

jmorris_42 said:
If you can get the stock recovery mode, all is not lost, all of the important bits are still functioning.
Power down. Hold VolDn and insert the USB cable. If you get the Software Update screen with a green icon you CAN recover the phone. It may require a battle with Windows to get it to play nice, Windows and USB is always a hit or miss affair; but the phone is ok if that screen appears. Do not use the VolUP + Power LG Recovery mode, there isn't a known tool for that in the wild.
I don't normally run Windows and the couple of times I have booted it to do this it required some hassle and usually skipping the nice way since I had never installed the bundled LG Desktop stuff before things went wrong. So just do what I did, pick the Emergency mode that requires inputting the IMEI instead of letting it detect your phone and then let it fix things for you.
Click to expand...
Click to collapse
Many thanks for your answer, I resolved the problem late at night, yes, after a hard battle with windows.
I installed windows 7 32 bit, I tried a lot of Lg drivers, 3.8.1 maybe the best, after inserting the USB cable with SW Update screen some LG peripherals were recognized but the result in KDZ_FW_UPD was always "phone was not found", then I tried connecting USB cable with the Phone in Android recovery mode ( power & Vol up), and OS added a couple more peripherals, and attempting again with SW Upgrade mode worked.

Is there anything I can do? Brick help

My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks

sivd said:
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
Click to expand...
Click to collapse
Do you have all the necessary driver installed? I think yes and that is why you are seeing in (COM3) port. You can do one thing, Unplug the phone from PC and Press and Hold Vol Down (-) and plug in again. If not works then you can also Press and HOLD Vol Down and Press and HOLD Power button until you see Fast boot menu. If don't work then try the same thing with Vol UP button. Then you suppose to see a MI phone logo with a USB cable.

"qualcomm hs-usb qdloader 9008" Is a signal of Hard Brick for QCOM devices (Like for LG G2);
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
As you can see here, for fix it you need all partition files, all system files, and a programm
But i dont know if it will works also on SD820, you might need all files for Mi5
Just a question: How did you bricked your phone?
EDIT:
I had an idea: maybe inside fastboot rom you can find all files you need, it might be worth a try, at least you can send it to your shop where you bought it

sivd said:
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fas,tboot in order to flash the ROM
Click to expand...
Click to collapse
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/fullromdownload.php?d=gemini&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.

adwinp said:
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/fullromdownload.php?d=gemini&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 also had the same issue with black screen and no responses from vol. & power buttons. But when I notice that in device manger it showed the qcom driver, then I new that there was hope to recover the phone. I can confirm that this will unbrick your phone. I MiFlash'd the China Rom (non-dev), unlocked the bootloader, MiFlash'd MiFlash_xiaomi.eu_gemini_V7.2.13.0.MAACNDB_6.0 rom, sideload lastest stable EU rom, TRWP and SuperSU.

adwinp said:
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:
3: download the latest dev rom from here:
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
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!

sivd said:
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
Click to expand...
Click to collapse
Glad you could salvage your device.
Now remember - from great flashing power comes great responsibility ;]

adwinp said:
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/fullromdownload.php?d=gemini&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
Thanks for the guide, 1 q tho: what to do when i get the "missed hello packets, try to recover" message?, wait or restart the process?
Ok, solved by disabling driver sign (press F8 during boot)

Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !

Isteran said:
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Click to expand...
Click to collapse
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.

DrBubblewrap said:
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
Click to expand...
Click to collapse
tryed a lot of time to go to fastboot , but nothing happened...

same issue
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......

tkrave said:
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
Click to expand...
Click to collapse
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk

vf1 said:
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
how do you flash stock recovery if you dont need to go into fastboot? now I am unable to go into recovery or fastboot as the phone does not boot at all. connecting it to PC reconizes the phone as the infamous "Qualcomm HS-USB QDLoader 9008" device.
Its been 4 days and the damn battery hasnt run out yet as I can still plug into pc and get qualcom 9008 to come up. I think I am going to send to china to get it fixed properly if I still cannot get the red flicker of low battery power to come up by tomorrow.

It has happened to me 3-4 times already. It didnt want to boot. No signs of life either. I even sent a message to the shop for sending it back..the only thing that was telling me it wasn't completely dead, was the qualcomm driver ,while on USB connection with the PC, which you are referring to as well
Here is what you could try doing. Try pressing the power button for about 30 seconds at first. If it does not boot, try bending the phone real gently back and forth (don't break it!!). Preferably, hit it gently with your palm while holding it in your other hand.( -- I know it might sound weird --) I noticed that it's shutting down while i have it in my pocket and doing some work which squeezes the phone a bit against my leg.
I came to the conclusion that some connection must become loose when some pressure is being applied to it.. Unfortunately it has to be a design flaw of the phone. Nothing random with yours or mine , in my opinion. // I have a case and tempered glass installed as well since the first minute I got it in my hands..
Sent from my MI 5 using XDA-Developers mobile app

Thanks for the tips Takkaros. I tried what you said but nothing changed (though I was a bit scared to bend it too hard). 1st time it happened to me, I had around 40-50% battery and somehow battery completely drained 24hr later so I got the red blinking low of battery light and was able to charge the phone up and go back into fastboot, which solved everything. this time it happened when I had 96% battery(which I knew cuz I was using the phone, then clicked MI Talk and phone froze, then bricked). I wish there is a way for me to force a battery drain without opening it up. I did opened it up once(on the 1st brick) and disconnected the 3 battery cables, but it was still in brick state when I put everything back.
The qualcomm 9008 driver detection was also my concern about sending back the phone. Chances are by the time my phone reaches the repair shop, battery is completely dead and they simply charge the battery then flash a stable rom and send it back to me without changing out the motherboard or whatever. Which in such case it will be faster for me to just wait a week or two and do myself, instead of shipping it to china and wasting shipping cost and probably will take 4-6 weeks.

I am not sure whats wrong with this phone. Sometimes it turns off while i have in on charge at night, with the Green led lighting. I can get into recovery mode but all the partitions are missing. I cant wipe anything and all my files are not there. If I restart the recovery 2-3 times everything comes back to normal. Maybe there is something wrong with the flash drive. If honorbuy replied to my messages i'd sent it back to them asap. This is not a reliable phone for daily use
Sent from my MI 5 using XDA-Developers mobile app

Try using mi flash. Follow the instruction
Sent from my MI 5 using Tapatalk

I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.

tkrave said:
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
Click to expand...
Click to collapse
This happened to me recently. I used mi flash and the global 7.2.4 stable fastboot rom to get it going again. Wouldn't work for me with with with newer versions. Think edl has been disabled on them.

My Z2 Pro dead .. help me ..!!

i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second

aljthab said:
i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second[/QUOTE try connecting it to the PC, if it doesn't show anything on PC then just hand it over to the lenovo service center and blame it on the device that it stopped booting :silly:. I thought i had bricked my device but they did something and gave it to me in 3 to 4 days and that was done under the warranty no extra charge and don't confess that I had rooted ur device , If u tell them that they will try to extort money from u :crying:
Click to expand...
Click to collapse

aljthab said:
i did something Stupid and my Z2 Pro dead
e LED there is flash yellow for 0.1 second
Click to expand...
Click to collapse
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english

kerei said:
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english
Click to expand...
Click to collapse
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/

same issue with zuk z2
adriano1593 said:
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
Click to expand...
Click to collapse
Hello there... Any solution you found? I am stuck with my zuk z2 in same situation ?? any help ?

I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze

m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk

eryenakgun said:
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your quick response.
The Hardware ID: USB\DEVICE_DESCRIPTOR_FAILURE
"Error Message": This device has been stopped because it has reported errors. (Code 43)
An error occurred while requesting the USB device descriptor.

m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot

OtakuLi said:
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot
Click to expand...
Click to collapse
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"

m_atze said:
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"
Click to expand...
Click to collapse
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them

OtakuLi said:
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them
Click to expand...
Click to collapse
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I don't want to destroy my PC (3000 bugs)

m_atze said:
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I won't destroy my PC (3000 bugs)
Click to expand...
Click to collapse
oh well, good luck

OtakuLi said:
oh well, good luck
Click to expand...
Click to collapse
I will report the result.

OK. I made the deepflash cable.
After using it there is no difference between pressing one of the button combinations I recently mentioned (VOL+ or VOL- or PWR).
The phone will be detected as Unknown device. After intalling my modified driver to match the unknown ID, QFIL don't detect the COM Port.

Hello had the same problem, only with the difference that my battery was not completely discharged.
What has helped:
1 Start QFIL Tool
2 Press the volume +
3 Connect the original cable to the PC
4 QFIL Tool recognized the phone and I could play an original Rome.
Mfg
Ps. Is now the battery cover (glass) broken?

No, I used a hairdryer, a razorblade, plastic tool and a suction cup to lift the backcover glass.
The glass is fully intact no damages.

You have good nerves. I would not have expected that.
But in the end, it does not matter if it does not start anymore.
Thank you again for your great instructions for playing and rooting the mobile phone.
I hope you get your phone back.
Mfg

Good and bad news
The guy unbricked the phone successfully, I received it today.
Now I have an other problem:
The phone is very very slow and laggy now.
The problem occurs everywere, Recovery, boot (the bootlogo laggs), booted System, also the test mode laggs now
Furthermore the sceen flickers sometimes and at the right side the sceen is mirrored sometimes.
Did anyone has an idea?
What I did today:
reflash through qfil
1.9.104_ST
2.3.044_ST
ZUI_2.5.335_ST

Hi m_atze, I am exactly in the same situation as You. After using deep flash cable method, I got "unknown usb device (device descriptor request failed)". Could You tell me what was the solution to unbrick the phone?

[PLZ HELP] Redmi 9c NFC won't enter fastboot, recovery or boot up.

Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED

AvZPablo4 said:
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
Click to expand...
Click to collapse
You can use instead SPFT.

I used SP Flash Tool. I watched a YouTube tutorial:
I didn't had luck, It said me : PTM changed from the ROM; It must be downloader. Please select "Formato Allí + Download" scene and try again
It didn't work on Format All . It grave me this error: ERROR : STATUS_UNKNOWN_STORAGE_SECTION_TYPE (0xC003000C). [HINT]:
I tried to search solutions but nothing.

Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient

SubwayChamp said:
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again

AvZPablo4 said:
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
Click to expand...
Click to collapse
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.

SubwayChamp said:
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
Click to expand...
Click to collapse
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.

AvZPablo4 said:
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
Click to expand...
Click to collapse
Windows not recognizing is normal in this state because your device is trying to boot to system, then Windows can't detect it as MTP BUT to have the device detected properly for preloader mode, you firstly have to install all the proper MediaTek drivers, then, from LibUSB entries listed choose one from all, i.e. Dispositivo Compuesto USB, it doesn't matter that it is the right entry, but this entry, if it is succesfully changed, would serve to recognize it, always that the VCom, and preloader drivers are properly installed.

I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)

AvZPablo4 said:
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
Click to expand...
Click to collapse
You have to keep pressed the buttons, even while the device is connected to the PC, your device will pass through various states, then quickly you have to release your fingers.
Well, preloader is a kind of bootloader, in MediaTek.
Use this tool, to bypass, https://androidfilehost.com/?fid=17825722713688275528 when you have success from the tool, then just run SPFT, uncheck the options LIB USB DA match storage and Storage Life Cycle, also check USB full speed.

I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device

AvZPablo4 said:
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
Click to expand...
Click to collapse
The tool is mirrored from other sites though https://gsmatoztool.com/mtk-auth-bypass-tool-v26-new-update-latest-tool/
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Also download the UsbDk 64-Bit installer from the site I linked, with mtk-client tool you also can do some things.

SubwayChamp said:
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Click to expand...
Click to collapse
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager

AvZPablo4 said:
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
Click to expand...
Click to collapse
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/

SubwayChamp said:
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
Click to expand...
Click to collapse
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi

AvZPablo4 said:
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
Click to expand...
Click to collapse
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off, and interchanging the buttons.

SubwayChamp said:
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off.
Click to expand...
Click to collapse
I kept pressing vol up + vol down for like 10 min, but, nothing

AvZPablo4 said:
I kept pressing vol up + vol down for like 10 min, but, nothing
Click to expand...
Click to collapse
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.

SubwayChamp said:
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
Click to expand...
Click to collapse
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW

AvZPablo4 said:
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
Click to expand...
Click to collapse
Not much I can do. I recommended all the best to bypass this. If you have taken it in consideration, then you should sort it out.
- Uninstall all the drivers, reinstall exactly only what you need.
- Be sure that LibUSB is properly installed.
- Install the UsbDK 64 bits installer from the site I linked and try also the mtk-client tool.
- The option Format all except bootloader in SPFT may help, but consider that it may erase your calibration data and IMEI, mainly.