QPST Not Working With One X Tegra? - HTC One X

Hi,
I've tried to link my phone up to QPST but ever time I try to add new port it comes up with: There was an error enabling. The port may not be working or maybe busy.
I've put my phone into diag mode using this guide- http://forum.xda-developers.com/showthread.php?t=1619314 and it didn't give me an error so I assume it's in Diag mode.
I then booted it into fastboot went to device manager and noted down the com port (com1) and I tried to add it in QPST to be greeted with the error mentioned above.
Any help would be much appreciated as I am a beginner.
Regards,

enya123101 said:
Hi,
I've tried to link my phone up to QPST but ever time I try to add new port it comes up with: There was an error enabling. The port may not be working or maybe busy.
I've put my phone into diag mode using this guide- http://forum.xda-developers.com/showthread.php?t=1619314 and it didn't give me an error so I assume it's in Diag mode.
I then booted it into fastboot went to device manager and noted down the com port (com1) and I tried to add it in QPST to be greeted with the error mentioned above.
Any help would be much appreciated as I am a beginner.
Regards,
Click to expand...
Click to collapse
The problem is that there is no Qualcomm modem or SoC to speak of.

oh thx bro

Hi,
Thanks for clearing it up! You saved me alot of wasted time. Are there any utilities that allow me to do the stuff that QPST does? I would like to debrand the phone from all the 02 nonsense that it's been sold to me with. I've done googling and I've found custom roms debrand although I'm not confident with roms as I hard bricked my old Galaxy.
Regards,

enya123101 said:
Hi,
I've tried to link my phone up to QPST but ever time I try to add new port it comes up with: There was an error enabling. The port may not be working or maybe busy.
I've put my phone into diag mode using this guide- http://forum.xda-developers.com/showthread.php?t=1619314 and it didn't give me an error so I assume it's in Diag mode.
I then booted it into fastboot went to device manager and noted down the com port (com1) and I tried to add it in QPST to be greeted with the error mentioned above.
Any help would be much appreciated as I am a beginner.
Regards,
Click to expand...
Click to collapse
QPST is something to do with Qualcom?
This forum is for the quad core Tegra 3 One X, not the dual core Snapdragon. If you can't find the right phone, I'm not surprised you bricked one. Anyway, bricking an HTC is harder due to the bootloader, but I wouldn't recommend you try it.

enya123101 said:
Hi,
Thanks for clearing it up! You saved me alot of wasted time. Are there any utilities that allow me to do the stuff that QPST does? I would like to debrand the phone from all the 02 nonsense that it's been sold to me with. I've done googling and I've found custom roms debrand although I'm not confident with roms as I hard bricked my old Galaxy.
Regards,
Click to expand...
Click to collapse
ROMs are the only way until we can change the CID.

Related

[Q] Bricked Galaxy W (What I did, What I get)

Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
nemli said:
Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
Click to expand...
Click to collapse
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
nemli said:
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
Click to expand...
Click to collapse
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
Thanks for your valuable responses. I will try what is recommended in those two links, and of course will give the feedback to here to help the (potential) brickers.
full brick
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
nemli said:
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
Click to expand...
Click to collapse
same problem as me
usb does not recognize my phone
if u find a solution contact me please
Solved by JTAG
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
nemli said:
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
Click to expand...
Click to collapse
How much did he charge you for the JTAG? I am looking to JTAG few phones
MayB4ck said:
How much did he charge you for the JTAG? I am looking to JTAG few phones
Click to expand...
Click to collapse
Nearly 20€ per JTAG.
If someone need QHSUSB_DLOAD solution...
Maybe I can help him...
You need Qualcomm Drivers... forgotten which one exactly I have used...
QPST Version Build 411
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9
Procedure looks similar to this:
forum.xda-developers.com/attachment.php?attachmentid=2754655&d=1400627472
In this Thread I have tried many things...
http://forum.xda-developers.com/showpost.php?p=52808706&postcount=282
I could prepare files for testing for I8150...
Not tested by me nor confirmed with I8150... as only S8600 for me available...
If someony want test... PM me.
Next few hours or days I could upload files for QPST...
Code:
MBR from I8150
DBL from I8150
OSBL from I8150
Need testers and feedback please.
Best Regards
Will check my HD for Qualcomm drivers...
Maybe upload later...
Here are test files... because untested...
Risk to reach other bad status... So you could need JTAG...
Short description...
DBL and OSBL are taken from JTAG dump...
It seems chinese Version could be different...
But MBR... first 512 Bytes are 1:1 same in all I8150 JTAG dumps I have on my HD...
partition.mbn is MBR from I8150... 512 Byte
DBL and OSBL have size from partition... extracted from JTAG dump...
DBL is in partition 2
OSBL in partition 3...
Settings for QPST are hopefully visible in Screenshot...
It is mandatory to use QPST Build 411... older Versions not accept MBR as partition.mbn without header...
Header in MBR not deadly but could be bring other trouble...
For testing now only correct drivers "missing"...
I have so many stuff downloaded...
Will try to find correct one.
Again, I have only S8600 for test...
Maybe with I8150 not possible...
But before you buy JTAG you can try.
Good luck.
Best Regards
Edit 1.
Qualcomm driver to find should be not impossible... use magic search word: QHSUSB_DLOAD... for instance here:
http://forum.xda-developers.com/showpost.php?p=40072841&postcount=1
or try this one:
http://forum.xda-developers.com/showpost.php?p=40195799&postcount=7
And here again Link for working confirmed QPST Version Build 411... tested successfully by me with S8600:
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9

Htc desire 320 rebooting bootloop (no recovery, no OS, no bootloader)

hi to everyone,
I have a htc desire 320 and I rooted it then flash a not compatible recovery moded and got in bootloop.
after this said the cellphone keeps restarting so I cant use the adb fastboot because its always disconnecting from computer.
I have no recovery to restore from my backup.
I have no OS to boot on.
I never had a bootloader locked or unlocked. none.
I have connecting problem to computer as adb should help.
my brain hurts and my phone is dead I think.
what should I do to just put on a recovery or unlock a bootloader I never had to bring everything back to normal ?
thanks in advance for support,
have a nice day.
mitch1490 said:
hi to everyone,
I have a htc desire 320 and I rooted it then flash a not compatible recovery moded and got in bootloop.
after this said the cellphone keeps restarting so I cant use the adb fastboot because its always disconnecting from computer.
I have no recovery to restore from my backup.
I have no OS to boot on.
I never had a bootloader locked or unlocked. none.
I have connecting problem to computer as adb should help.
my brain hurts and my phone is dead I think.
what should I do to just put on a recovery or unlock a bootloader I never had to bring everything back to normal ?
thanks in advance for support,
have a nice day.
Click to expand...
Click to collapse
Sorry this is for the desire.
Saf98 said:
Sorry this is for the desire.
Click to expand...
Click to collapse
Whats the real codename of the desire 320 is it still like bravo
I finally had pass the problem with flashing it and facing error from the CID
supercid on this model is possible?
Help
mitch1490 said:
Whats the real codename of the desire 320 is it still like bravo
I finally had pass the problem with flashing it and facing error from the CID
supercid on this model is possible?
Click to expand...
Click to collapse
Hello!
I also flashed a recovery.img which put the phone into a boot loop. I am not able to flash my backup because in SP Flash Tool my HTC Desire 320 keeps disconnecting (error 2004).
How did you manage to flash your phone? Could you please help? Or is my phone dead?
Thanks.
Avan7 said:
Hello!
I also flashed a recovery.img which put the phone into a boot loop. I am not able to flash my backup because in SP Flash Tool my HTC Desire 320 keeps disconnecting (error 2004).
How did you manage to flash your phone? Could you please help? Or is my phone dead?
Thanks.
Click to expand...
Click to collapse
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
mitch1490 said:
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
Click to expand...
Click to collapse
Thanks a lot! I am going to give it a try .
Blessings.
mitch1490 said:
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
Click to expand...
Click to collapse
I have Tried plugging mine in holding down the down button and still just kept disconnecting and reconnecting. Is there any other way you know of to flash back to stock? or installing cwm/twrp?
I have even tried on multiple computers...
n3m37h said:
I have Tried plugging mine in holding down the down button and still just kept disconnecting and reconnecting. Is there any other way you know of to flash back to stock? or installing cwm/twrp?
I have even tried on multiple computers...
Click to expand...
Click to collapse
please try removing the battery first.
mitch1490 said:
please try removing the battery first.
Click to expand...
Click to collapse
Already tried, with battery in it boots and crashes, when plugged in without battery it just connects and disconnects over and over.
Have tried multiple cords, usb 2.0 & 3.0 ports. Same story.
Installed mediatek driver, uninstalled; you name it I tried it with the exception of opening it. Haven't got to that stage yet, I'm lazy.
n3m37h said:
Already tried, with battery in it boots and crashes, when plugged in without battery it just connects and disconnects over and over.
Have tried multiple cords, usb 2.0 & 3.0 ports. Same story.
Installed mediatek driver, uninstalled; you name it I tried it with the exception of opening it. Haven't got to that stage yet, I'm lazy.
Click to expand...
Click to collapse
if adb cant be able to be able to connect and stay connected ( bootloop or restarting problems )
then take SP Tool flasher to flash the Scatter MT6582 from stock KK by only remove battery first and let it out.
plug the universal usb port on cable but on the end of the cellphone dont plug it yet...
in SP Tool check the checkboxe in settings to checksum DL DA. and select usb high speed and W/O battery options.
then when the scatter is loaded then you ready to flash. the latest SF Tool is recommanded.
click on Download on SP tool when done the steps. it will hang on idle but at this moment press de volume down button first.
keeps holding that button until the end of flashing process and when hold it now plug the cable to your computer and bam you will be able to flash it to stock or custom your desire 320 without problems and its will not disconnect during process since you holding the volume down button.
that's how I did resolve my problem about months and find my own solution.
hope this helps... dont be shy to let me know if it worked for you or if you still need assitance.
have a nice day.
peace.
This is a forum for the HTC Desire Bravo A8181.
This is a forum for the HTC Desire Bravo A8181.
See with your own eyes.
Help please
mitch1490 said:
if adb cant be able to be able to connect and stay connected ( bootloop or restarting problems )
then take SP Tool flasher to flash the Scatter MT6582 from stock KK by only remove battery first and let it out.
plug the universal usb port on cable but on the end of the cellphone dont plug it yet...
in SP Tool check the checkboxe in settings to checksum DL DA. and select usb high speed and W/O battery options.
then when the scatter is loaded then you ready to flash. the latest SF Tool is recommanded.
click on Download on SP tool when done the steps. it will hang on idle but at this moment press de volume down button first.
keeps holding that button until the end of flashing process and when hold it now plug the cable to your computer and bam you will be able to flash it to stock or custom your desire 320 without problems and its will not disconnect during process since you holding the volume down button.
that's how I did resolve my problem about months and find my own solution.
hope this helps... dont be shy to let me know if it worked for you or if you still need assitance.
have a nice day.
peace.
Click to expand...
Click to collapse
After searching and searching, seems someone actually had the same problem as I do. But for my part even when pressing the volume down before connecting to the computer doesn't keep the phone from connecting and disconnecting, even tried all the buttons combination you can imagine.
I'm wondering if it could be a driver issue, in your case was your device disconnecting every 5 seconds? And do you have any special driver that I should be aware of, personally I have Preloader USB VCOM port version 2.0.0.0...
I hope you got something in mind, I don't know where to look anymore haha.
Thanks again
PS I did everything else, remove battery, disable signature, got scatter MT6582 + download agent for flash tool (also updated), tried with ADB but can't detect device (of course it keeps deconnecting :silly: )
Metal Addict said:
After searching and searching, seems someone actually had the same problem as I do. But for my part even when pressing the volume down before connecting to the computer doesn't keep the phone from connecting and disconnecting, even tried all the buttons combination you can imagine.
I'm wondering if it could be a driver issue, in your case was your device disconnecting every 5 seconds? And do you have any special driver that I should be aware of, personally I have Preloader USB VCOM port version 2.0.0.0...
I hope you got something in mind, I don't know where to look anymore haha.
Thanks again
PS I did everything else, remove battery, disable signature, got scatter MT6582 + download agent for flash tool (also updated), tried with ADB but can't detect device (of course it keeps deconnecting :silly: )
Click to expand...
Click to collapse
even if you have mediatek usb vcom driver or adb drivers else original driver it works on all with the button press.
but set the setting like I said USB support normal without battery W/O and high speed.
don't set it to mediatek com ports on SP tool. but if you have mediatek com port change to port 20. that's what I did change the port com.
mitch1490 said:
even if you have mediatek usb vcom driver or adb drivers else original driver it works on all with the button press.
but set the setting like I said USB support normal without battery W/O and high speed.
don't set it to mediatek com ports on SP tool. but if you have mediatek com port change to port 20. that's what I did change the port com.
Click to expand...
Click to collapse
What version of SP Flashtool are you using?
Well I have tried everything everyone has said so far
No matter what I try I get
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
Have tried using both
SP_Flash_Tool_v5.1352.01
SP-Flash-Tool-v5.1532.00
Both do the exact same thing, tried checking the AD DL ALL with Checksum boxes, unchecked usb high speed and full speed. Pressing the down button before plugging it it, after. Nothing I do seems to work, in the device manager it just keeps appearing and disappearing over and over
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
The correct version of the SP FlashTool we need for our device is the SP_Flash_Tool_v5.1348.01_SEC (http://mediafire.com/download/eaar07r2nm1v7t6/SP_Flash_Tool_v5.1348.01_SEC.rar). I read somewhere that it was because of the HTC Desire 320 has a security boot.
If you got a 4008 error, it's probably because you're using Win8-Win10. You need Win7. I'm installing Win7 on my PC right now, so I will tell you more about it later.
If you looking for the stock roms, I found this site : http://easy-firmware.com/index.php?a=browse&b=category&id=1449
If you speak russian, feel free to correct me.
Have a good one guys.
Source: http://4pda.ru/forum/index.php?showtopic=331715&st=12120#entry40719887 (Russian)
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Hi
I have desire 200 won't turn on,stay in HTC logo
I just have recovery and fastboot with hboot 1.20.0000,,,s-on
I want to flash any ROM on it
Any one help me,please?
Sent from my V3 Plus using Tapatalk
cafestrabac said:
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
The correct version of the SP FlashTool we need for our device is the SP_Flash_Tool_v5.1348.01_SEC (mediafire.com/download/eaar07r2nm1v7t6/SP_Flash_Tool_v5.1348.01_SEC.rar). I read somewhere that it was because of the HTC Desire 320 has a security boot.
If you got a 4008 error, it's probably because you're using Win8-Win10. You need Win7. I'm installing Win7 on my PC right now, so I will tell you more about it later.
If you looking for the stock roms, I found this site : easy-firmware.com/index.php?a=browse&b=category&id=1449
If you speak russian, feel free to correct me.
Have a good one guys.
Source: 4pda.ru/forum/index.php?showtopic=331715&st=12120#entry40719887 (Russian)
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Click to expand...
Click to collapse
You my friend are a gentleman and a scholar! downloaded and flashed right away and booted up Am on Win 7 x64 Pro
cafestrabac said:
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Click to expand...
Click to collapse
Thanks for it, i've got that problem after trying to install custom recovery. I also got the error 2004 but i fixed myself by using DA_SWSEC.bin. Not sure if it work for ur guys or not.
I also learn that althrough HTC 320 is Mt6582 devices but we cant use the method they wrote in mtkrom site to install custom recovery. Now i can find the stock rom of my phone to check flashing custom rom via splashtool. I used telus rom above and i got problem wrong CID and the flash camera not work, if i have msg or phone call missing, it flashes like notice led! At least now my phone is working ok then. I'll try to contact HTC to get stock rom of my phone
Leoisback said:
Thanks for it, i've got that problem after trying to install custom recovery. I also got the error 2004 but i fixed myself by using DA_SWSEC.bin. Not sure if it work for ur guys or not.
I also learn that althrough HTC 320 is Mt6582 devices but we cant use the method they wrote in mtkrom site to install custom recovery. Now i can find the stock rom of my phone to check flashing custom rom via splashtool. I used telus rom above and i got problem wrong CID and the flash camera not work, if i have msg or phone call missing, it flashes like notice led! At least now my phone is working ok then. I'll try to contact HTC to get stock rom of my phone
Click to expand...
Click to collapse
Yeah I forgot to mention that, you need to use the DA_SWSEC on the SP Flashtool. What's your htc 320 model? Your probably have the wrong rom. The telus one is only for NA device.
EDIT: Are you using the HTC Desire 320 with dual sim: http://drop.ndtv.com/TECH/product_database/images/15201573649PM_635_htc_desire_320.jpeg
If this is your device, the Telus rom is not for your device.
This is the EU rom: http://www.mediafire.com/download/z...NSE53_htc_europe_1.00.401.3_by_jamesjerss.zip

LG G3 dead. Black screen. No booting. Help????

Hi,
I tried to install a custom rom on my LG G3 d858hk model. I was in twrp recovery and trying to install rom. Suddenly the phone got stuck. I waited for some time and then pulled the battery out and reinserted it. But still no light etc. Even nothing happens when I plug in charger. Looks like its completely dead. Any body any idea, how can i recover it from the black screen.
Regards,
Khurram.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 follow this guide just download ure files
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
antony990 said:
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
Click to expand...
Click to collapse
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
cesarandres_8911 said:
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
Click to expand...
Click to collapse
Yes I have a warranty. But I had installed a custom ROM (cloudy g3), so I guess that violates mine. The phone is dead, and shows up in device manager as LGE AndroidNet USB Serial Port. Don't even know why its showing up like that
Okay, am i'm searching for any available software fix that's gonna work for me at least before I resort to opening up the phone
Let me shed some light on what caused my phone to go dark, to save someone else from repeating the same mistake... I was trying to upgrade twrp from version 2.8 to 3.0. I thought using autorec would help me achieve that. But once it had finished, I attempted to boot to recovery and since then my phone has gone completely dark
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300
cesarandres_8911 said:
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300[/url]
Click to expand...
Click to collapse
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr....
My phone is an LG g3 d855, so please guide
antony990 said:
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr...and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
cesarandres_8911 said:
The first thing you should do is download the .tot file corresponding to your Variant (D855), I think that you can find it here: http://forum.xda-developers.com/lg-g3/help/tot-dll-file-d855-t2859828
Follow this guide to use boarddiag:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
In the "Image EXTRACTION" sections, in "BIN" must locate the file .tot that you downloaded.
In "DIR" you put the location where will be extracted the content of the .tot file.
Note that "DIR" and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
antony990 said:
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
Click to expand...
Click to collapse
And then, every time I unplug the device and plug it back into the PC, the device ends up being undetected by windows, and I have to redo the shorting procedure again. Is this normal behaviour, or something is wrong??
Also, when I put the battery back, and plug the device, it shows up as LGE androidnet usb
Anyone explain to me what this means. Please check the image attached
antony990 said:
Anyone explain to me what this means. Please check the image attached
Click to expand...
Click to collapse
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
singingandroid said:
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
Click to expand...
Click to collapse
It could also mean your device isn't in EDL mode 9008.
TheMadScientist said:
It could also mean your device isn't in EDL mode 9008.
Click to expand...
Click to collapse
I believe I am in the right 9008 mode. Screenshot is attached.
singingandroid said:
I believe I am in the right 9008 mode. Screenshot is attached.
Click to expand...
Click to collapse
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
TheMadScientist said:
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
Click to expand...
Click to collapse
Yeah, I've tried pretty much everything, but thank you for the reply.

something between soft brick and hard brick

Hey guys,
I have lg g3 d855 it was with lolipop v21a (TWN version) and now I kinda of destroyed it when I flashed a marshmallow rom for hong kong lg g3 d 858HK(wish i had know that earlier) ,
so what i currently have is a phone with no wifi or signal ( so no way of connecting to internet) and it is not recognized by computer ... I can enter download mode but still i get the error usb device not recognized
any idea or suggestion of how to fix it ? or is it hard bricked ?
any idea any one please ? :crying:
patrs63 said:
any idea any one please ? :crying:
Click to expand...
Click to collapse
please ?
so its lost, how can I close thread ?
patrs63 said:
so its lost, how can I close thread ?
Click to expand...
Click to collapse
It's probably not lost, but you'll need to get to work & it is a mild pain in the a** to do so...
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Dont mind the sprint variant, just use the proper files for your phone this time around
I brought a phone up last week via this method. The hardest part is getting the phone to show up as qualcomm 9008 & to communicate with it(need the proper drivers and need a good cable). It can be a little tricky, but once you figure that part out the flashing part is easy.
*The method I linked above should be considered a last resort.*
But I thought you posted you can get into download mode earlier, so make sure your computer isn't the issue. Uninstall all lg drivers & reinstall them. If you have download mode/firmware update displayed on your phone screen and it shows up as lge serial port(or something like that) in device manager you should just be able to TOT or KDZ your stock firmware. I believe there are instructions for that in the link as well; if not - google is your friend.
Gd luck:good:
startswithPendswithOOH said:
It's probably not lost, but you'll need to get to work & it is a mild pain in the a** to do so...
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Dont mind the sprint variant, just use the proper files for your phone this time around
I brought a phone up last week via this method. The hardest part is getting the phone to show up as qualcomm 9008 & to communicate with it(need the proper drivers and need a good cable). It can be a little tricky, but once you figure that part out the flashing part is easy.
*The method I linked above should be considered a last resort.*
But I thought you posted you can get into download mode earlier, so make sure your computer isn't the issue. Uninstall all lg drivers & reinstall them. If you have download mode/firmware update displayed on your phone screen and it shows up as lge serial port(or something like that) in device manager you should just be able to TOT or KDZ your stock firmware. I believe there are instructions for that in the link as well; if not - google is your friend.
Gd luck:good:
Click to expand...
Click to collapse
well my computer is not the problem since i tried 2 or 3 other computers and few other cables , still no luck recognizing it in download mode ... so i guess ill go for the qualcomm method :/
but what exactly does shortining the pen mean ? and is there a video for that ?

MiFlash Can not read from port com - whyred

Hi, can someone help? I was about to flash the official whyred Linedage OS for my Redmi Note 5. I did that with note 3 and note 4 before, so kind of knew what I was doing.. But was not aware of the antirollback thing.. So after i decided to flash the new miui 10 firs for the firmware..(wasn't the best idea I know) and you know the rest.. something went wrong and now I am stuck with dead phone.. no recovery, no fastboot, nothing.. I had unlocked bootloader officially a few weeks ago, got the device connected with the mi account (not sure about if the account is authorized or not).
I tried the test point method - dissembling the device from miui dot com
I have the right driver listed in device manager (Qualcom HS-USB QDLoader 9008)
I tried several roms listed here or miui dot com
I tired several versions of MiFlash
Every time I only get the message about not reading the com port (tried all USB ports on two PCs, reinstalled drivers .. everything) .. It starts flashing "read hello packet", then after 5 seconds stops with the mesage "can not read from port comXY"
In edb its just waiting for the device on any command (or not devices found)
Anyone can help please? I spent the whole day searching for solution and found nothing, or nothing helps
thx in advance
I am in your same situation. did you solved it?
thank you
rfiore said:
I am in your same situation. did you solved it?
thank you
Click to expand...
Click to collapse
Yeah, posted my ID on the forum, got authorized, then used the "portable" miflash and it worked.. But on the other PC still got errors in miflash.. didn't even check for the authorization, so I suppose its PC related.. perhaps something with the drivers..
FKuzel said:
Hi, can someone help? I was about to flash the official whyred Linedage OS for my Redmi Note 5. I did that with note 3 and note 4 before, so kind of knew what I was doing.. But was not aware of the antirollback thing.. So after i decided to flash the new miui 10 firs for the firmware..(wasn't the best idea I know) and you know the rest.. something went wrong and now I am stuck with dead phone.. no recovery, no fastboot, nothing.. I had unlocked bootloader officially a few weeks ago, got the device connected with the mi account (not sure about if the account is authorized or not).
I tried the test point method - dissembling the device from miui dot com
I have the right driver listed in device manager (Qualcom HS-USB QDLoader 9008)
I tried several roms listed here or miui dot com
I tired several versions of MiFlash
Every time I only get the message about not reading the com port (tried all USB ports on two PCs, reinstalled drivers .. everything) .. It starts flashing "read hello packet", then after 5 seconds stops with the mesage "can not read from port comXY"
In edb its just waiting for the device on any command (or not devices found)
Anyone can help please? I spent the whole day searching for solution and found nothing, or nothing helps
thx in advance
Click to expand...
Click to collapse
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Simple.. Disconnect and Reconnect with your PC Via Testpoint.. Thanks.
thank you very much
Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
I was lose hope because 12 hour my mido error cant read hello packet, and now fix it with your tips.. thanks a lot man
Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
Thank you. I was in the "read hello packet" part and i was able to flash the Chinese rm
Thanks
Can u please give me your mi authorized I'd it will help for me
Am also stuck on edl mode redmi note 5 pro so please give me your mi I'd
Raviganthy said:
Am also stuck on edl mode redmi note 5 pro so please give me your mi I'd
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Help!
Help! i am also stuck on this problem on my Redmi 3. Can someone please help me?:crying:
---------- Post added at 06:18 AM ---------- Previous post was at 06:15 AM ----------
FKuzel said:
Yeah, posted my ID on the forum, got authorized, then used the "portable" miflash and it worked.. But on the other PC still got errors in miflash.. didn't even check for the authorization, so I suppose its PC related.. perhaps something with the drivers..
Click to expand...
Click to collapse
What forum?
can not read from port com xy
guilherme06 said:
Thank you. I was in the "read hello packet" part and i was able to flash the Chinese rm
Thanks
Click to expand...
Click to collapse
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.
talhosvi said:
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.
Click to expand...
Click to collapse
I have the same problem with my jasmine(which used to be wayne) when I tried to change it back into wayne again... do you have any solution already ?
kunoir said:
I have the same problem with my jasmine(which used to be wayne) when I tried to change it back into wayne again... do you have any solution already ?
Click to expand...
Click to collapse
have you find any solution?
jayspiker said:
have you find any solution?
Click to expand...
Click to collapse
i had the same problem but fixed with edl cable
Prabudeva005 said:
I faced the similar situation. I pasted the ID in the russian and english forum. I got no message for weeks, I thought of flashing again, Voila. Device flashed and turned ON. Your device is hard bricked as mine, it needs authentication from Mi to flash via EDL mode. All you need to do is download the MI flash tool portable, and paste your Mi ID in forums.
Unfortunately both the forum's date to paste the ID has been expired. But still you try to get help from someone else from the forum or the moderators.
I'll explain different errors I faced and the solution for it.
"not reading the com port" --- You get this error when you flash Global version of the ROM. Use the Developer version of it.
"It starts flashing "read hello packet"" --- You get this error because edl is turned off in your phone. To turn it back ON, just remove the USB cable from your phone and then press the power button for 10-15 seconds. Then connect your phone back again and try to flash.
"edb its just waiting for the device on any command" --- Actually this is not an error. Your phone is hard bricked. While in hard bricked mode adb won't work. ADB works only in fastboot mode.
Click to expand...
Click to collapse
where can i find this chinese rom for MI A3
talhosvi said:
can not read from port com xy
Hello, I've tried even developer rom, it displays the same error can not read from port com xy.
Even after doing test-point all over again.
By mistake I flashed wayne rom once, and phone boots but in a messed up fastboot mode.
Click to expand...
Click to collapse
same problem with me . Have you solved it ?? let me know please
Hi Guys,
I have the same problem trying to flash MIUI 11 in mi A3 with MIUI 12. Anyone knows a solution for this?

Categories

Resources