Develop Bugs

[Q] How to set up the drivers for flashtool?

I've installed fastboot, and installed the drivers for my xperia play (R800x) while it's in fastboot, so I've successfully unlocked the bootloader (got the code back when you still could for free), rooted using zergRush, and have successfully flashed DooMKernel.
However, i've tried to just flash the CM7 (CDMA of course) using fastboot only to get a black screen (which prompted me to flash DooMLorD's kernel). I saw the .ftf file above the CM7 download, so i googled what to do with it (the post didn't say you had to do anything with it). So, I discovered flashtool, and I've read both this and this guide, however I can't get flashtool to recognize my R800x when I plug it in.
I have extracted both of the flashtool files and merged them, so flashtool loads fine, and the .ftf is read fine, however flashtool just will not recognize my R800x when it's in flashmode (blue light).
For the drivers I did launch Gordon's Gate and install it in the drivers folder (Gordon's Gate folder inside the drivers folder) and i did install all of the drivers from the installer inside that folder successfully.
I can't understand why it won't recognize it, so I just need someone to clearly explain to me how to set up the drivers for flashtool for my Xperia Play. (flashtool 0.4.2 downloaded from here)

By not recognizing it do you mean that it doesn't give the PLAY as a device option? Cuz flashtool doesn't list the PLAY but still works if you select x10 or Arc. And by the way, blue light does NOT mean flash mode, it means fastboot mode. Green light (hold back button when plugging in) means flash mode. So it probably doesn't see your device cuz it's in fastboot mode

You must be in Flash Mode, not fastboot mode, when you are trying to use flash tool. You must hold the BACK button, NOT search button for flash mode.

Oh wow, what a stupid mistake x.x, so I'm not 100% sure I fully flashed it. I went through the procedure til it told me to turn on my phone and then turn on debugging and unknown sources, then i turned it back off and reflashed. The second time it asked me for a device, i chose the Arc according to the jacklebott, then it ended with this
{
"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"
}
I then unplugged it and turned it on, i guess that was the end... right?

That should do it

[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.

Xiaomi Redmi 7 - bricked/only EDL mode available

Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a 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"
}
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas

tamasv said:
Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a screenshot:
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas
Click to expand...
Click to collapse
Hey mate, I'm not sure if you fixed it or not but I'm pretty sure that if it can boot to fastboot it's not bricked. What I suggest you would do right now is install xiaomi drivers onto your pc first and foremost (this actually fixed all my problems) then try to use adb and fastboot tools to fastboot flash recovery twrp.img. if that works you're safe and then proceed to advanced wipe, then vendors and system wipe then in an SD card or an otg flash USB install the lastest global or Europe ROM for miui 11.

LG K10 - Cannot launch TWRP, or download mode - Bootloop

Model: LG K10 K430dsE
Spoiler: bootloop 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"
}
Bootloader is unlocked / oem unlock / usb debugging ON
This happened after i tried to adb reboot fastboot flash twrp.img (because without flashing twrp ididn't launch)
Now my device is bricked? - maybe it was even wrong twrp version, whatever couldn't find anything official for the exact model and device is old
When the phone starts i get the following message
"Your device is corrupt. It can’t be trusted and may not work properly"
Stuck into a bootloop
1. 'adb devices' does not find the connected phone, neither 'device manager' (did before) - cannot start twrp
2. Pressing UP and connecting USB, it goes into Download mode for ~10 seconds then exit and shows;
"Your device is corrupt. It can’t be trusted and may not work properly" and goes into a bootloop again
2.5 PC recognises the COM/PORT for a split second in LGUP + LG Bridge , then it goes away cause phone loops so i cannot enter upgrade and flash the .kdz
3. LGUP shows 'There is no handset connected. Please, connect a handset(s)'
4. LG Bridge does not see the USB, tried different PC and ports.
5. Removed battery, press UP + connect USB device tries to start and closes in 1s
6. When i try to go into download mode, windows shows
'MT67xx Preloader' Looking for updates/drivers, but fails to find it,
Download mode goes into bootloop again and shows 'Your device is corrupt etc'
Spoiler: flip
99,9% i will hear "your device is hardbricked and there is no fix"
It was probably wrong twrp img, K10 K430XX - flashed it and now the phone is gone prob
edit; pressing UP + connecting USB, will show on LGUP and LG Bridge, the device
'connecting' for a split second, then goes away - phone from download mode for 10s will go to bootloop again

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