Develop Bugs

Lenovo Vibe Shot Z90A40 Cant Turn the device on after miflash completes successfully

Hi,
I am not getting Qualcomm 9008 mode even after installing and reinstalling the drivers manually or via setup
I see this under Other Devices in device manager
QHSUSB__BULK
Then I ran miflash it worked fine as per following attached screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I unplug device and turn it on it does not show any thing, just a long (2/3 seconds) vibration and done
So basically I cannot get any thing on my screen, Plz help me to get to recovery mode, as if I get till that point
I would be able to flash a proper stock ROM form SD Card
(I have tried the things after removing SD card as well)

it is fixed now
I resolved it, the Diagnostics 9006 mode problem happened to my device twice due to various reasons
in first attempt I was seeing a lot of read only partitions when I connected phone, it was solve using QPST/QFill
before resolving this problem I was able to go to Stock recovery almost all the times but was unable to flash
any thing from there even with the use of SD card
2nd time the problem was same, but this time I was not seeing any partitions in my Computer
actually both times the real problem was going to proper 9008 mode which I finally got to know how to do it from
following thread
http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
I feel I shall put the text as well:
If you were on Lollipop : Phone must be completely off. Pressing �Volume Up�
key plug the USB cable in WITHOUT PRESSING POWER BUTTON ! Port will open.
If you were on Marshmallow : Phone must be completely off. Plug the USB cable in
and immediately press Power On button. Port will open.
Since I bricked from Marshmallow, so I used the Plug in Cable + Power button only to got
to 9008 mode and once there I knew I can make a come back, which yet came after a couple of tries
as one has to click immediately on Download button when Qfil can see 9008.

Actually I bricked my phone a whole lot of times even after my post thats because once I knew that it is just soft bricked and I can get it back somehow, I got the confidence and tried advanced things that bricked my phone again and again
And it was only the recent time (around 3 weeks ago), that I figured the 100% working 9008 method for my phone
actually u have to drain the battery completely out then it will get 9008 mode to do it u shall try turning your phone on again and again so that battery goes off
For example: Press Power button for a few seconds to turn it on.
Or press 3 buttons at same time (VOL+, VOL- and Power), then release only Power button when you get vibration. Then after 2 seconds release both VOL buttons as well (this is for going to recovery mode)
This way you can drain all battery of phone, and you will know when the battery is all gone when you will press the Power button and phone will not show any LED light or screen light, it will just vibrate and will be off
Now you connect ur phone to PC in following way:
If at bricking you you were on Lollipop (Android 5): Pressing VOL+ key and plug the USB cable in WITHOUT PRESSING POWER BUTTON ! 9008 will open use Qfil to flash the ROM u want
OR If at bricking you were on Marshmallow (Android 6): Plug the USB cable in phone, then connect cable to PC and exactly at the same time press power button (some times u dont need to press power button so try with both options). Then if you see 9008 mode in Qfil, then immediately press the Download button in Qfil
If you see Qfil error then repeat the above process to get 9008 mode and use miflash instead of Qfil miflash worked for me better than Qfil from such situation as Qfil often gives error in between
And when you get the flashing 100% then phone will either auto restart or you have to restart it manually Using Qfil it shows u message when it is restarting the phone, and I think using miflash it just says process 100% complete then u have to restart phone yourself
Remember at this point (after restart) connect your phone charger properly in a electricity power socket instead of PC as the battery was already drained so you need to charge the device while it shows the long booting process due to new ROM flashed.
Good luck,

[Fixed] I hard bricked my Vibe P1

Dear developers!
After successfully flashing and upgrading a friend's Samsung, I got the courage to do the same with my Lenovo Vibe P1.
I followed this video and everything was perfectly: I unlocked the bootloader, connected using QFIL and flashed the TWRP recovery he provided, until the 8:00 minute in the video the program said "Waiting for reset done..." and my QFIL just stucked on that message, so after waiting 5-7 minutes I disconnected the cable in hope that it will reboot to recovery, got some log errors and since then the phone is hard bricked.
Turning on does not work, recovery/bootloader/charging does not work, essentially the screen is dead, the only thing that works is recognization in QFIL program.
When I try to flash stock rom or that recovery from that video again, it first says a protocol error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to Download again, now it gets stuck at the Working folder (last message in the log, see below)
EDIT: Depending on the QFIL version, the version below actually gives the same error as above after few minutes.
In addition, any attempt to connect the phone to Windows using USB results in numerous partitions being shown from the phone internal memory (many of which Windows does not recognize as formatted):
(https://i.imgur.com/otd7e0M.png)
Is there anything that could be done to recover my phone please? Not having the right financial situation to purchase a new one and school starts soon so pretty bad situation for me now.
Kind regards,
kangarko

Update! I deleted all partitions from the phone and was successfully able to flash a couple of ROMs from the Internet (including a stock one). However, after each flash one, I get the "Waiting for reset done..." message and than the phone gets disconnected from my Fusion (virtual Windows 7 in Mac), and when it gets connected again it says Finished but the phone is completely black. No signs of any activity, it does not restart itself nor vibrates, and I end up with the problem in my first post again ;(

Help still needed... noticed I typed "Lenovo" in the thread title instead of Vibe, I corrected that but the PHONE IS STILL BROKEN.

Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650

kangarko said:
Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650
Click to expand...
Click to collapse
Hi there.Did you experience USB not recognized?I already removed the battery-reconnect-hold volume + then connect the usb cable but still USB not recognized.

I Bricked my phone, Please Help

Hello, Friends from XDA
So long story short, I was trying to fix my Redmi Note 8's charging issue (slow charging and charges only when booted to OS). Then I decided to install a new rom from twrp (current was MIUI China, trying to install Xiaomi .eu) hoping that it might solve the issue but dumb me accidentally wiped the "system" partition during the wiping proccess. Now I am greeted with "The system has been destroyed" message". Cannot boot to twrp anymore. I really regretted doing that.
P.S. tried fastboot, doesn't work, ask for more
Anyone, please help. All suggestions are welcome.

When flashing a ROM you have wipe the system as well. This will fix that issue you are having(flash this after flashing ROM. This is a VBmeta.img):
https://mega.nz/#!r54FzQIZ!LgD3zSOBm1gOIzY6w8r8l-A8GChgWk_Z7HIN6y_bVLc
Use this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I suggest that you join the Telegram group as that's where I got this file from. Plus you will get help much faster.

@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
That is alarming, so your device can boot into fastboot mode but won't be recognized by the PC?
Try using it on another PC because if you can't use fastboot or Recovery, the only thing that will save you is the EDL mode, and I have heard people say that the only way to access that is with an authorized account (which only xiaomi service centers have) or you will have to open the back of your phone and short circuit the EDL Chip.

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy

Zulfi said:
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy
Click to expand...
Click to collapse
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized

Judroidz said:
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized
Click to expand...
Click to collapse
In SS you can see the cover on device clearly

Zulfi said:
In SS you can see the cover on device clearly
Click to expand...
Click to collapse
Oh sorry I didn't see that. OP did you get anywhere with fixing your device

Judroidz said:
Oh sorry I didn't see that. OP did you get anywhere with fixing your device
Click to expand...
Click to collapse
Well bro, I'm still trying. Going to give the EDL mode a try and as you can probably tell, I am a newbie.
Any precautions, maybe tips that I should know about?
here's what I've gathered
1. Remove back cover
2. Find the edl testing points
3. Short circuit the testing points
4. Plug the device to pc (asap after shorting)
5. Flash using MiFlash (Hopefully recognizes the device)

So, it seems like you need an Authorized Account for flashing in EDL. I was hoping to find a diy solution but things get complicated. Well, I'm just going to send the device to a trusted local Xiaomi repair center and get it fixed (they have authorized accounts) and also solve the charging issue. Again, Thanks to everyone and XDA.
P e a c e

HELP NEEDED - Having issues with pc connection/downloadmode/recoverymode

Device Name: Sony Xperia XA2
Device ID: H3113
Internal Storage: 32 GB
Software Version: Android 8.0.0
What i want to do: Install LineageOS 19.1 on the phone.
How far i got: I'f been trying to follow the instructions here https://wiki.lineageos.org/devices/pioneer/install
However after 2 hours and no progress i decided to ask on XDA...
On the PC i installed platform-tools_r33.0.2 for windows and UniversalAdbDriverSetup
Then i added this path %USERPROFILE%\adb-fastboot\platform-tools to "Environment Variables"
On the Phone i have USB Debugging Enabled also OEM and Bootloader are both unlocked.
I am ready to install LineageOS however when i connect the Phone to the PC and check device manager there is a yellow marker, something is not right.
The Phone asked me what shall be transfered and i selected data, still the PC doesnt seem to "like" the phone.
I have installed LineageOS on a samsung device before and there only difference i can spot now is that for samsung i installed usb drivers on the pc, however for sony i cannot find usb drivers for the Xperia XA2. Do i need these and where do i get them??
I have noticed another "issue" when i try to boot the phone in recovery by pressing Volume Down + Power, the phone vibrates once and the screen goes on fully white with the sony logo.
After that nothing happens i continue to press Volume Down + Power and everything repeats, phone reboots, vibrates once and shows sony logo, this will go forever untill i stop pressing Volume Down + Power and the Phone now boots normally to system. It seems i cannot boot into recoverymode?
The phone is acting wired, when i press Volume Up and connect it to the usb/power cable sometimes it does nothing and shows the battery % while sometimes it boots to system and sometimes i managed to get into download/fastboot mode where ican see a blue light but the screen remains off.
I was going to install TWRP with ADB but since the phone isn't showing on the PC i cannot continue, i have no idea what to do... cant be so hard can it? So many people flashed lineage on this phone so there really should be a way... i hope someone can help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi, I believe I have the same issue.
When pressing "volume up" (for bootloader) while connecting the USB cable I get an "Android" device without driver. I've tried several drivers without result. Emma sees the phone (but gives "device locked"), Windows sees the phone, adb sees the phone, but when in bootloader... no result.
Any assistance is welcome.
WIndows 10 64
Xperia XA2 (H3113)

You have to know how your device is presenting: ABD? Fastboot? Bootloader?
You need to look in Device Manager and identify devices that are not happy.
Try to install a stock driver. If you can't, then identify the VID/PID of the device.
You may need to make a copy of the stock Google .inf file and make new entries for your device.
Then you can try to install that, although you'll have to use the procedure for unsigned drivers.
In any case, if things are not going right, don't bother with long adb or fastboot commands. Just try.
Code:
C:\>adb devices
...
C:\>fastboot devices
...

Thanks for the reply,
While stock android is started
ADB gives:
List of devices attached
CQ3001ERRN device
Fastboot devices: No result
Reboot phone in flash mode (Volume down): Emma recognizes phone(but locked)
Reboot phone in recovery (Volume up): Unknown Android device.
When trying to install the Google driver (or any other related) I just get: could not find the driver for your device. In my view this has nothing to do with unsigned (message is different).
Uninstalling "Android" and re-installing it, does not help, picking it out of the list of available drivers does not help.
"You may need to make a copy of the stock Google .inf file and make new entries for your device."
How would one proceed with this, keeping in mind that when the phone is booted using stock ROM it is fully recognized as a Xperia XA2?
Any advice is welcome

A device needs drivers for every single different mode that it can be in.
For the thing that you can't load drivers on, you need to get the VID/PID and if there is an MI.
Just go to DeviceManager > MysteryDevice > Properties > Details > Device instance path
From DM it's not possible to see if this is ADB or Fastboot but the driver is the same.
Copy over the Google .inf file to your own.
Add what you found in DM to look just like the others.
Note that you need to enter the same line twice in the NTx86 and NTamd64 sections.
When you try to install a driver using your .inf it will obviously be unsigned.
Do the restart PC with allow unsigned and install.

@Renate You have made me a happy man.
I'm looking at a Xperia with LineageOS running smoothly
Thank you for your instructions

Question Pixel CDC-ACM device hard brick help

The pixel6 pro has an automatic reboot after aosp is flashed in, then it won't boot and becomes a brick, all buttons are unresponsive. I don't know what the problem is, the original Android version is 14, the one I flashed in is 13.
After installing the driver and plugging it into the computer, the port device will appear, and the QFIL software can recognize this port. Need "FireHose Programmer" && "rawprogram*.xml,", please help to solve the brick method or related resources
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since there is no Google service in my area, I can't send it back to the manufacturer for repair.

If your Pixel device is hard bricked, meaning it is completely unresponsive and cannot be turned on, there are a few steps you can take to try to resolve the issue. Here are some steps you can try:
Try a hard reset: Press and hold the power button and volume down button simultaneously for at least 15 seconds to perform a hard reset. If your device is responsive, this should force it to reboot.
Check your USB connection: Make sure that your device is properly connected to your computer via USB. You can try using a different USB port or cable to see if this resolves the issue.
Use fastboot to flash a factory image: If your device is still unresponsive, you can try using the fastboot tool to flash a factory image onto your device. This process can be complex and may require technical knowledge, so it is recommended to follow a detailed guide or seek professional assistance.
This is based on my experience but maybe some expert can suggest better treatment, I request them to suggest a solution.

GcamApk said:
If your Pixel device is hard bricked, meaning it is completely unresponsive and cannot be turned on, there are a few steps you can take to try to resolve the issue. Here are some steps you can try:
Try a hard reset: Press and hold the power button and volume down button simultaneously for at least 15 seconds to perform a hard reset. If your device is responsive, this should force it to reboot.
Check your USB connection: Make sure that your device is properly connected to your computer via USB. You can try using a different USB port or cable to see if this resolves the issue.
Use fastboot to flash a factory image: If your device is still unresponsive, you can try using the fastboot tool to flash a factory image onto your device. This process can be complex and may require technical knowledge, so it is recommended to follow a detailed guide or seek professional assistance.
This is based on my experience but maybe some expert can suggest better treatment, I request them to suggest a solution.
Click to expand...
Click to collapse
Thank you for your answer.
1. no response to any key operation on the device, the power button volume keys +- tried many times for a long time, there will be no response
2. replace the usb and port to connect to the computer there is no connection device other than the com port
3. I can't connect the phone to the computer to use Google's online fastboot tool to reset the phone because I can't turn it on.
Thanks again for your answer.