Database Info

[Q] adb can't find my D800 after OTA on rooted

Hello,
this is my first post here.
I recently rooted my LG G2 AT&T (D800). It was running D80020y.
Also recently AT&T offered the update to Lollipop (D80030f). I did not accept the update but ATT pushed it anyway when I rebooted the phone.
After that the phone would not boot, it would just go into recovery mode. I have TWRP v2.8.5.1.
Many of the posts addressing situations like this require installing the D800 drivers in computer, and installing adb.
I am trying to solve this problem from a PC running Windows 7 Pro. The PC is not able to see the device.
"adb devices" returns nothing. Not an errror, but an empty list.
When I connect the G2 to the PC, the (windows) device manager lists it twice:
1) Under "portable devices there is an entry "LG-D800", and there I get "this device is working properly", and it uses Microsoft drivers under C:\windows\system32\ and under C:\windows\system32\DRIVERS.
2) Under "Other Devices" there is an entry like before, "LG-D800", with an error sign. When I open that entry I get:
"The drivers for this device are not installed. (Code 28)
There is no driver selected for the device information set or element.
To find a driver for this device, click Update Driver."
Even if I click "update driver" and navigate to the installed LG drivers they won't load. The PC says that nothing was found.
I've tried this also on Windows 8.1 with the same results.
However, with the phone plugged into the PC I can see its contents with Windows Explorer, and I can copy files into it.
I just can't run adb or fastboot.
Of course, I am not able to change to "USB debugging" mode because I can't boot the phone. For the same reason I can change to PTP mode.
So the larger question is how to get my phone back to booting, and I've seen references to that in xda-developers, but all of them use adb,
and for that I need the PC to be able to see my G2.
Thanks!
Asttor

Can you access download mode?
By powering off your phone and then press and hold volume up button and connecting usb from your pc.
Sent from my LG-D800 using XDA Free mobile app

Mustafa Jafri said:
Can you access download mode?
By powering off your phone and then press and hold volume up button and connecting usb from your pc.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know what Download Mode is but I tried what you suggested. It took me to the same place, i.e., it loads TWRP. TWRP seems to be fully functional.
Thanks for answering

Go to LG and download the latest USB drivers and try connecting again.

Thanks for the answer. I had tried that and it did not change the results.
However, I don't really have more time to devote to this. I have spent a lot of hours during the last week.
I thank for the answers though.
How do I close this thread?
Asttor

Sony Xperia Z3 D6616 possibly hard bricked?

Hi all! I have a Sony Xperia Z3 I recently acquired, it seems to be bricked, possibly hard bricked I'm not sure, but the phone refuses to boot into fastboot or flashmode. Here's what I've noticed so far:
EDIT: The bootloader on the device was never actually unlocked! After getting in contact with the previous owner, all he did was use KingRoot to gain root access on the phone, then installed SuperSU and Clockworkmod recovery respectively. After installing the custom recovery the previous owner had then attempted to flash a variant of Cyanogenmod but the flash failed, since the bootloader wasn't unlocked, resulting in the bricked state the phone is currently in.
The phone shows a red LED when left plugged in to charge overnight
If power button + volume up buttons are held, the red led turns off and the phone vibrates 3 times, but nothing else happens
When connected to the computer via USB, the red led will appear again for a couple seconds, then disappear, then appear, and repeats this process until unplugged. While this is happening you can hear the computer recognizing the phone being constantly plugged in and unplugged.
When plugged into the PC, flashtool recognizes the phone as "Device Connected with USB debugging OFF"
Booting into fastboot or flashmode doesn't work, no matter what button combinations I've tried none of them worked to put the phone in either of these modes.
Is there any way I can unbrick the phone? I don't think this is a driver issue as the computer is recognizing the device in device manager and flashtool sees it, however shows "Device Connected with USB debugging OFF". Is there anyway to somehow enable USB debugging in this state?
I've also tried using adb commands to reboot into fastboot, however this is pointless as the phone is not recognized as an ADB device, when you type "adb devices" there is no devices listed.
HUGE thanks to anyone who has any input on my situation, any help is gladly appreciated! Thank you everyone!

I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked

lavin40 said:
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
Click to expand...
Click to collapse
EDIT: I just got in contact with the previous owner, the bootloader was actually not unlocked, the phone was simply rooted via KingRoot, after that SuperSU was installed, then Clockworkmod recovery. After that the previous owner had attempted to flash a new custom rom from clockworkmod but it failed, resulting in the brick. So as it turns out the most probably reason for the brick was because the bootloader was never unlocked, causing the flash to fail, putting the phone in this bricked state. Does anyone have any suggestions on what I can do at this point to unbrick it, now knowing the bootloader was never unlocked? Thanks!

If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.

Omario-242 said:
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Click to expand...
Click to collapse
When I try to go into flash mode or fastboot, nothing happens except for the phone vibrating 3 times and getting the red LED. I've also tried plugging it in and running EMMA however it's not recognized at all by it.
Flash tool recognizes the phone, but throws this message everytime its connected
"Device Connected with USB debugging off"
Is there anything I can do with Flash Tool with the phone being recognized in this state?
I guess as a last option I could try to get in contact with a repair service and ask if they'd be able to unbrick it, however I do not know of any as I've never been to one, hopefully theres another way to unbrick it without having to go here.
Thank you everyone so far who has replied to my thread so far! Please let me know if anyone has the same issue or has an idea for helping unbrick my phone, I appreciate all the tips I've gotten so far.

I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.

Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick

Omario-242 said:
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Click to expand...
Click to collapse
Hi, thanks for the tips, I just tried downloading and installing the Sony Update Service program however it terminates immediately after opening and checking for updates as Sony has discontinued the program since Sony PC Companion replaces this program.
If I type "ADB devices", the phone does not appear on the list, as for some reason ADB is not finding the phone in the state that it's in. I've tried repeatedly typing in this command numerous times when its plugged with no luck.
I've also even tried holding down the volume down/up buttons with a rubber band as i plug the device into the computer however no change, I still get the same result.
Thanks for the tips though!
tz16 said:
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Click to expand...
Click to collapse
I've already tried using Sony PC Companion however it does not detect my phone at all in the current state for some reason. I've tried everything the program told me to do, pressing and holding numerous button combinations however the program will not recognize the phone. Thanks for the tip though.

when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs

tz16 said:
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
Click to expand...
Click to collapse
I've tried this exactly as you showed above, however this is the screen I get stuck on, since Sony PC Companion does not recognize my phone. Look at the picture below. Please let me know if you know how to get past this/get Sony PC Companion to recognize my phone, thanks!
{
"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"
}

Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ

tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
Hi, thanks for the link and instructions, I just installed the drivers successfully, however Sony PC Companion still isn't recognizing my Xperia Z3.
Anything else I can try? Please let me know, thanks

Unplug your device
Hold Volume+ ....and plug in back till your pc load device " flashmod"
I remember this way, when i do it my pc reconized my device with other name

tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.

Omario-242 said:
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Click to expand...
Click to collapse
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks

sebzter said:
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
Click to expand...
Click to collapse
Ok I think I'm out on this point as I honestly have no idea about the whole test point procedure. About repair service though, I guess they don't repair it because they may have to give warranty on their repaired products. Maybe try a mobile repair service in your neighborhood if there's one, but like you said I don't know if the price for a repair exceeds the devices worth.
I guess if you can find this test point it would be a reasonable option for you and I really wish you good luck with that and your phone.

Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers

sebzter said:
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
Click to expand...
Click to collapse
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.

ndmuni said:
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
Click to expand...
Click to collapse
Hi, thanks for the tip, however the phone doesn't seem to be recognized in fastboot devices either. Heres a screenshot of what I get when I type in adb devices and fastboot devices. Thanks

Try installing Minimal adb with fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
If youconnect your device in fastboot mode....power off, hold vol up ..does your pc sees it?

Moto G USB Problem

Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly

Hello, did you try typing in `fastboot devices` while in fastboot ?

-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).

Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.

Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers

[Hisense A5] How to Enter Hardware EDL mode

Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
{
"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"
}
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware

joygram said:
Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware
Click to expand...
Click to collapse
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?

try step.
no adb required.
just jump point and connect power cable.
you should retry until catch QFIL catch port.
CrotteDeChien said:
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?
Click to expand...
Click to collapse

Anybody who knows:
How do you open the device without breaking it?
Ehere to begin to open it?
What tools (i.e. screwdrivers T5?) you need?
Does an Edl-Hardware USB-Cable works with the Hisense to enter Edl-Mode? How?

Yeah, how to open the Hisense A5?

Use something like a guitar pic (plastic plectrum) on the edge of the cover and open the cover carefully i.e. upper front.

lillo9546 said:
Yeah, how to open the Hisense A5?
Click to expand...
Click to collapse
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.

Hi Everyone, thanks you your tips.
I went to a phone repair place and paid them 20 AUD to open the phone.
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Reading more there is information regarding PCB (printed Circuit Boards) and the test points. These are the points we are mean to be "jumping".
What is the sequence of events ? Do I turn off the phone first ? Do I turn on the phone while having the points jumped ?
Do I connect the phone to the computer via USB first, and then allow debugging ... and THEN jump the points with tweezers or a paperclip ?
Any ideas would be greatly appreciated.

CrotteDeChien said:
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
See after Step 6., but really be careful. Good luck
https://in.c.mi.com/thread-387857-1-0.html

Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?

Mehedi34 said:
Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?
Click to expand...
Click to collapse
Dear Mehedi,
use the base firmware 6.03.02 for edl-mode flashing in Qfil provided from gowin132
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Then flash this in Qfil see here some general infos
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
use "prog_emmc_firehose_8937_ddr_000bf0e1.mbn"
from the package of joygram
Flash each partition in Qfil Partition Manager (Menu Tools)
After that reboot the device and it should work.
Then upgrade to latest 6.09.06 with TFMode (microSD)
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28

see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951

JLowe said:
see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951
Click to expand...
Click to collapse
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132

Mehedi34 said:
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132
Click to expand...
Click to collapse
Good to hear that you're successful! You can't soft brick these China Qualcomm Smartphones
Have fun with this great device!

5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
1. Boot EDL Mode via ADB Commands
2. Use Fastboot to Boot EDL mode on any Xiaomi smartphones
3. Use Hardware Buttons
===> Turn off your device.
===> Press and hold the Power + Volume Down buttons together and immediately connect the device to the PC.
===> It will automatically boot into EDL mode and LED lights may blink.
4. Use Deep Flash Cable
5. Use PCB Test Points

Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?

hammelgammler said:
Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?
Click to expand...
Click to collapse
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
I made a deep flash cable myself but sadly that doesn't seem to work either. Maybe I did something wrong with the cable but it seems all good to me. I can connect another phone with it and it functions normally, so the only thing that can be defect is the switch/button itself which shorts/connects the green and black wire together.
When I plug the Hisense in my computer with the button pressed it "starts normally" into the boot loop or something and when I let go off the button nothing happens.
As far as I read, you press the button, plug the phone into the computer and after about 8 seconds or so you let go off the button and it will boot into edl mode. But it doesn't seem to work for me.
Thank you. Any help would be very appreciated.
Edit: Okay I got it. For some reason I had to press the button on the cable, volume up/down and power button together for a few seconds until it showed up i QFIL.

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
Same me. I had rooted it but i tried to reflash stock firmware and now has bootloop. How imcan fix? If i flash root it will boot, but i want to go back to stock

Mehedi34 said:
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.
Click to expand...
Click to collapse
I also used my fingernail too, its easy to handle,

Trouble Unlocking Bootloader

I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.

If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.

canero said:
If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.
Click to expand...
Click to collapse
Thanks for responding, I will take a look at the article once.
I have made sure that all steps were followed correctly and I think everything was in order. I have already made sure correct drivers were installed multiple times.
What's weird with my device is that, unlike other Poco F1 devices this one in particular does not have any OTG option in settings, I don't know if it's a software or a hardware issue. The device is on MIUI 12.0.3 Stable(QEJMIXM).

OTG option? OTG is not the traditional adapter that we use to insert a usb stick into the phone? are there some parts that I know are missing, please inform me

Bhavik479 said:
I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.
Click to expand...
Click to collapse
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.

canero said:
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.
Click to expand...
Click to collapse
Kindly read my original post again, I do use the Mi Unlock tool and do connect the phone via Fastboot/Bootloader mode.

I think we can solve this problem, only my ability to speak English makes it difficult for me sometimes. If you want, let's try again step by step, you can call me on Instagram for this? my instagram account name: canerorak_

hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
{
"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"
}

canero said:
hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
View attachment 5752897View attachment 5752899View attachment 5752901
Click to expand...
Click to collapse
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.

Bhavik479 said:
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.
Click to expand...
Click to collapse
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.

Some sentences may be wrong because I wrote with google translate. I'm doing this job, I could help you if you called me on Instagram. I don't have any free time now, take care of yourself, I hope you solve the problem

canero said:
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.
Click to expand...
Click to collapse
As far as I understood, start from fastboot connected state, check for drivers button, the dialogue will ask to reconnect, but do not reconnect. Restart phone by long pressing power button, toggle off and on USB debugging option, restart to Bootloader while still staying connected by pressing Power + Volume Down button. Fastboot shows up and it shows 'Mi Drive Installed' dialogue on screen. Re launch Mi Unlock Tool and hit Unlock option.
If this was the procedure you wanted to convey, I will say sadly it did not work. I successfully got Mi Drive Installed dialogue without disconnecting USB, but still Mi Unlock Tool shows No Device Connected upon relaunching it.

Bhavik479 said:
Anladığım kadarıyla, fastboot bağlı durumundan başlayın, sürücüleri kontrol edin buton, diyalog yeniden bağlanmayı isteyecek, ancak yeniden bağlanmayın. Güç düğmesine uzun basarak telefonu yeniden başlatın, USB hata ayıklama seçeneğini kapatıp açın, Güç + Sesi Kısma düğmesine basarak bağlı kalırken Bootloader'a yeniden başlayın. Fastboot belirir ve ekranda 'Mi Drive Yüklendi' diyaloğunu gösterir. Mi Unlock Tool'u yeniden başlatın ve Unlock seçeneğine basın.
İletmek istediğiniz prosedür buysa, ne yazık ki işe yaramadığını söyleyeceğim. USB bağlantısını kesmeden başarılı bir şekilde Mi Drive Yüklendi diyaloğunu aldım, ancak Mi Unlock Tool, yeniden başlatıldığında hala Cihaz Bağlı Değil gösteriyor.
Click to expand...
Click to collapse
Do not close the mi unlock app after you see the warning that the driver is installed.restart the fastboot mode. When doing this, remember that the usb debugging mode is turned off and the phone is connected to the computer.

Finally, reset your phone and computer and try everything from the beginning. I'm sorry if it's not solved despite everything. This problem is very annoying, don't forget to tell me if you solve it one day. Good luck