Hi,
My girlfriend bricked my phone (i think), Everything i do always saying Fastboot Mode Started but when i try to do some commands, gives-me errors, usb_read() transation failed etc..
On my computer, device detected as CMCC Composite ADB Interface.
Can anyone help me?
Thanks
leonardoc said:
Hi,
My girlfriend bricked my phone (i think), Everything i do always saying Fastboot Mode Started but when i try to do some commands, gives-me errors, usb_read() transation failed etc..
On my computer, device detected as CMCC Composite ADB Interface.
Can anyone help me?
Thanks
Click to expand...
Click to collapse
What was she doing when it bricked
Can you boot into OS normally?
itsbighead said:
What was she doing when it bricked
Can you boot into OS normally?
Click to expand...
Click to collapse
I don't know, i think that was updating and run out off battery..
No, only fastboot, but i think is bricked, because i do "fastboot erase boot" and keep saying "earsing 'boot'" and is stuck :/
Actually i can put phone into qualcomm 9008, but BoardDiag3.99c gives-me error when testing :/
Related
hey guys my phone is bootlooping again i know i can fix it i just need to get into recovery the problem is my vol buttons are both broken before i used a program that booted my phone into recovery but i cant remember the name for it ive tried looking for it again but cannot find it can anyone help? its not omap
EDIT: i think its soft bricked my comp is recognizing it tho as galaxy nexus
Do you mean ADB?
you have adb on your computer ? adb reboot recovery ?
acras13 said:
you have adb on your computer ? adb reboot recovery ?
Click to expand...
Click to collapse
no im actually not sure whats wrong now its recognized as omap 440 omap flasher works without any errors but still bootloops adb doesnt work it recognizes it but says its offline
so the current situation is im bootlooping cant get into fastboot or recovery the computer recognizes my device and its called samsung adb interface under device manager and samsung mtp device. adb wont work because it says my device is offline any help would be highly appreciated odin doesnt recognize my device either (
My lg f180l is bricked at the moment, i install the proper drivers but it keeps on phone not detected and only android adb detects, please help me guys, i tried all the tutorials but it says phone not detected. what was the problem?:crying:
Meeko12 said:
My lg f180l is bricked at the moment, i install the proper drivers but it keeps on phone not detected and only android adb detects, please help me guys, i tried all the tutorials but it says phone not detected. what was the problem?:crying:
Click to expand...
Click to collapse
Fix your drivers
Go to download mode, plug in the phone
Open device manager, there must be a device not installed or showing yellow exclamation, fix that.
Same goes for when in custom recovery and trying adb.
Sent from my GT-P3100 using Tapatalk
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )
I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
engpika said:
I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
Click to expand...
Click to collapse
Does fastboot recognize a device at all?
Yes, you are in EDL mode. When I was in EDL mode, I couldn't flash on my laptop. Switched to my desktop and I was finally able to flash the recovery ROM.
What error message are you getting when using MiFlash tool?
dgrasley said:
Does fastboot recognize a device at all?
Click to expand...
Click to collapse
no...
C:\WINDOWS\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\WINDOWS\system32>
golfinry said:
Yes, you are in EDL mode. When I was in EDL mode, I couldn't flash on my laptop. Switched to my desktop and I was finally able to flash the recovery ROM.
What error message are you getting when using MiFlash tool?
Click to expand...
Click to collapse
I have a success flash message. but device not booting at all.
Few things to try:
Different Cable
Different Computer/Port
Try different drivers
Turn off the phone - Once you turn it on, try to flash again right away.
Is the Miflash tool detecting the phone on COM port?
engpika said:
no...
C:\WINDOWS\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\WINDOWS\system32>
Click to expand...
Click to collapse
Isn't adb for android os? You have a bricked device so you need to try using fastboot to connect to phone, not adb. If you have fastboot and adb, "fastboot devices" will show your device if it is in fastboot mode. You can try to manually wipe then flash the parts of the ROM through fastboot or install twrp and recover nandroid backup.
MiFlash say successful but the phone still doesn't boot? Try to hold all the buttons(vol+,vol-,power) for at least one minute and check if something happens.
When I bricked my MI5 it took +- 5 hours to boot it after flashing a fastboot ROM. Just give it some time.
Sent from my MI 5 using Tapatalk
engpika said:
I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
Click to expand...
Click to collapse
Hi,
I know this is old, but I made the exact same mistake last night. Did you manage to fix it? How?
Thank you in advance
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???
Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question