Database Users

Unbrick lg g3 qhsusb_bulk, qualcomm 9008 workking 100% by board ver 2.9a

How to Fix "error device not found in dload trying flash programmer" when use boardiag .
Lg g3 qualcomm 9008 when install driver then use tool boardiag fake tool say device not found in dload trying flash programmer
when you use tool fake board share in xda another tool say device not found in dload trying flash programmer. You need remove battery (of lg g2 hold power 1 minute) then connect cable again and use tool again
Sure install driver 100% wrong
With windowns 64 bit you need restart pc then click f8 choose disbable driver singturne....
Then remove battery (hold power 1 minute with lg g2) then connect cable try use tool unbrick >> sure done 100%
I will updload video error dload
Remember disbbale tool sony erricson if you have open tool in taskbar
How to fix “No response from the device. Check PMIC first and
if still boot problem, replace AP.”
Remove battery and connect again put qualcomm 9008 then use tool in topic
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/​ Just as helping
[*]I see very topic unbrick qualcomm 9008 lg g2, lg g3 but all tool can not use.
I have full tool board ver 2.9.( only 2.9).
Link download drive.google.xxx /file/d/0B_Hol5T47S-bYjNETmVPZkdWUms/view?usp=sharing (xxx= com)
Support lg g2, lg g3 workking 100%.
Download tool, open BoardDiag and choose file tot correct model phone of you( you can download tot in xda)
See guide in pictrure : very easy.
Note
Hold power 2 minute and connect cable ( or remove battery)>>And open tool check ap, emmc test again
Then unbrick done remove cable, hold power 30 second and hold volume up connect cable phone put downloadmod >> Use lgflashtool 1.5 flash file tot again >> done.
If done pls donate a few beers paypal of my Thank you very much.​

Man you saved my ass Thank you so much !1 when i get my salary ill donate to you and tell everybody to do so cuz this tool is amazing. im in download mode now ill try to flash with lg flash tool.

Thank so much man but my g3 last week unbrick qualcomm i had I submit for warranty[emoji24] [emoji24] I am very Star-crossed [emoji20]

Hello friend willcracker
Hello friend willcracker :good:
I hope all is well;
I saw this little tutorial so I want to ask for help
I have a LG G3 D855p and my phone is dead (bricked)
I can not quite understand the method you friend
not turn on my phone
I can not enter the "" Download Mode ""
VOL + Up when I connect the USB cable to the PC recognizes me as:
Qualcomm HS-USB QDLoader 9008 (COM10)
why I ask for help to revive my g3
If you help me ... .. I promise to donate something for you
you send a file "picture" attached
- - As I can get to "" Fastboot Mode "" on my phone
I hope your prompt response, please do not ignore my message :crying:
greetings from peru

You need to Disassemble Phone and Expose the TP Location
See pictrue
Expose the TP Location.
Done phone put qualcom 9008>> use tool unbrick
Remeber unplug battery connect only cable and short testpoint

Thanks for responding, but I need your help please friend
Hello willcracker I have no such tool you indicate "tool unbrick testpoint"
I could do this step with some type of cable or wire?
- If you Might tell me how to do that step with another option
leave your email. to chat google chat (Houngts) and you help me please
I'm worried because my g3 d855p not light, or anything like I said ....
await your prompt response, I hope you can help me

TOT Firmware, must match installed version?
Hey, thanks for providing this tool!
Final question, the TOT file must this match the installed version?
My situation:
Lollipop was installed, goal was to move to a custom rom (blisspop v2.3)
Rooting was successful
Install of twrp not, reboot into recovery caused the 'signature verification error'
Tried to flash the kitkat rom via the download method, failed, ...
Currently, I have the same verification error also when trying to get into download mode and have the Qualcomm HS-USB QDLoader 9008 in my device manager.
I have the LGD855AT-00-V10e-EUR-XX-JUL-08-2014-16G+0.tot file and did the first step of your procedure. Can I do the second step with this extract of kitkat even if lollipop was installed?
any feedback greatly appreciated!

Hello willcracker thanks, thanks for reply but I need your help please
Hello friend willcracker not have any of those tools indicated in its response = "testpoint tool unbrick"
I can do this step with some type of cable or wire
- I want you to guide me step by step how to perform the process
**will commit without any error.
And haci get my phone g3 ... haci I could also help others or siblings who need help to solve any problem with the g3
- I can not enter download mode
- I can not enter recovery mode
- When I turn on my phone, get the LG logo goes about three letters at the top left, then flashes a red, blue lights ...
- The PC recognizes me as Qualcomm HS-USB QDLoader 9008 (COM10)
You could leave your email. Google to chat chat (Houngts) and help me please
*....
Waiting for your prompt response, I hope you can help me
Please do not ignore my message willcracker friend
Greetings from Peru

themusic1510 said:
Hello friend willcracker not have any of those tools indicated in its response = "testpoint tool unbrick"
I can do this step with some type of cable or wire
- I want you to guide me step by step how to perform the process
Greetings from Peru
Click to expand...
Click to collapse
NO you need find google how do short testpoint samsung n7100 you see they guide short testpoint . Lg when short testpoint phone detect qualcomm 9008
And you use tool board diag unbrick.

???
themusic1510 said:
Hello friend willcracker not have any of those tools indicated in its response = "testpoint tool unbrick"
I can do this step with some type of cable or wire
- I want you to guide me step by step how to perform the process
**will commit without any error.
And haci get my phone g3 ... haci I could also help others or siblings who need help to solve any problem with the g3
- I can not enter download mode
- I can not enter recovery mode
- When I turn on my phone, get the LG logo goes about three letters at the top left, then flashes a red, blue lights ...
- The PC recognizes me as Qualcomm HS-USB QDLoader 9008 (COM10)
You could leave your email. Google to chat chat (Houngts) and help me please
*....
Waiting for your prompt response, I hope you can help me
Please do not ignore my message willcracker friend
Greetings from Peru
Click to expand...
Click to collapse
I'm in the same boat! Could you please explain it a little better?

frank.devliegher said:
Hey, thanks for providing this tool!
Final question, the TOT file must this match the installed version?
My situation:
any feedback greatly appreciated!
Click to expand...
Click to collapse
You need extract file tot d855 and put phone to qualcomm 9008 and unbrick . DOne flash stock rom. Find rom 5.01 link another

Ahh now i see!
Well ive tryed this guide with two different computers, but all i get is ap check failed, i do get into qualcomm mode and everything. Why does it fail!!? Am i doing something wrong?

@willcracker
The link doesnt work !? Where can i download the BoardDiagTool?
I have a F240L and this totfile BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0 .Can I use it?
I have tried with this file but i get the message AP Check or Check PMIC first

sourly64 said:
@willcracker
The link doesnt work !? Where can i download the BoardDiagTool?
I have a F240L and this totfile BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0 .Can I use it?
I have tried with this file but i get the message AP Check or Check PMIC first
Click to expand...
Click to collapse
what do you mean?
The link unbrick only g2 g3 and gpro2
Phone of you G pro i not upload tool . Unsderstand.

Magnerion said:
Well ive tryed this guide with two different computers, but all i get is ap check failed, i do get into qualcomm mode and everything. Why does it fail!!? Am i doing something wrong?
Click to expand...
Click to collapse
Model Lg d851? writh
rememer ber tool suppoer only lg g3 f400s/l/k , lg d855 16gb and 32gb.
If use tool say error pcmic on tool not support (Ex: lg d851)
I up load only msm8974ac g3 msm8975ac g3 no upload

Magnerion said:
Well ive tryed this guide with two different computers, but all i get is ap check failed, i do get into qualcomm mode and everything. Why does it fail!!? Am i doing something wrong?
Click to expand...
Click to collapse
It seems won't work.I have gone through about this problem.Alway AP Check fail.QPST reported that phone had been in Sahara download mode for few seconds.A RMA fix my phone.But it cost me about 50dollars

willcracker said:
what do you mean?
The link unbrick only g2 g3 and gpro2
Phone of you G pro i not upload tool . Unsderstand.
Click to expand...
Click to collapse
Hello willcracker !
Thanks for the note,do you know the totfile is the right one ?
I get with this file ,when is extraced the message in BoardDiag Check PMIC first and if not boot Check AP

TOT Version
willcracker said:
You need extract file tot d855 and put phone to qualcomm 9008 and unbrick . DOne flash stock rom. Find rom 5.01 link another
Click to expand...
Click to collapse
I have a TOT file, but for kitkat, not Lollipop. Can I use this TOT file?
(have only a kdz file for lollipop)
Thx!

frank.devliegher said:
I have a TOT file, but for kitkat, not Lollipop. Can I use this TOT file?
(have only a kdz file for lollipop)
Thx!
Click to expand...
Click to collapse
YES you can use tot kikat unbrick .

sourly64 said:
Hello willcracker !
Thanks for the note,do you know the totfile is the right one ?
I get with this file ,when is extraced the message in BoardDiag Check PMIC first and if not boot Check AP
Click to expand...
Click to collapse
sr i have not upload hex lg gpro waitting comming soon.

Lg g3 auto-rec "hard brick" fix

Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.

The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?

wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk

@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk

Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks

Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.

@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.

Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk

Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!

Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?

Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk

Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!

i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..

vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me

ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!

Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC

mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/

He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.

Apply update from sdcard FAILED : Rooted Crosscall Trekker M1 on BOOTLOOP

Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !

Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?

-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can

Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip

-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it

Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)

-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"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"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788

Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?

Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?

-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?

Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers

-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit

After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.

Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset

-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.

Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted

-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.

oneplus 6T stuck on fastboot bootloop

hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:

ritork said:
hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:
Click to expand...
Click to collapse
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/

Ethos001 said:
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/
Click to expand...
Click to collapse
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
{
"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"
}

ritork said:
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
Click to expand...
Click to collapse
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:

Ethos001 said:
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:
Click to expand...
Click to collapse
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate

ritork said:
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate
Click to expand...
Click to collapse
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Thanks again mate <3

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?

HackerGames197 said:
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?
Click to expand...
Click to collapse
PM me

Gracie mille !!! First brick and i hope never again but you where there.. Huge thanks.

Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.

bigmikey307 said:
Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.
Click to expand...
Click to collapse
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.

Micheal86 said:
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Hope this helps

I have the same problem
PLeaseeee help me I have a rooted oneplus 6t. I performed a backup and wipe in hope to clear a problem and am now stuck in fastboot mode. Im pretty sure as I tried to reboot it said no os detected, and then I got stuck. I have tried to install the latest oxygen os by manualling flashing 4 files. all tutorials i read have bootloader and other files while i just have - system_matrix , system_manifest , vendor_matrix, vendor_menifest (XML files by the way). I have flashed these files and rebooted only to go back to the fastboot screen.

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing ?
And my bootloader is also locked how can i solve this problem pls help me

For anyone running into a similar problem these are the steps I used
1. Download and extract files
a. Qualcomm drivers
b. MSM Oneplus 6t download Tool
2. Disable Driver Signature Enforcement by restarting your pc whilst holding shift, Choose trouble shoot, then going into more recovery ,select Advanced Options > Startup Settings > and then click on Restart.
3. Now PC will restart and Now you will see a list of startup settings that you can change. Select option 7 ‘Disable Driver Signature Enforcement’ by clicking f7
4. Now switch off your phone (by navigating through fast boot options)
5. While switched off hold both vol up + down for 5secs before connecting to your pc. *Your pc should recognise a phone is connected however nothing will be displayed on your phone*
6. Open device manager from start- Under Other devices there should be your phone (although it will be called smthn else), right click that and select update drivers
7. Browse computer for driver software and select folder with extracted QUALCOMM drivers (for me it was called unbrick).
8. The open the MSM application (run as admin tho) it should say device connected
9. Press start and you download should start- if error occurs or download stops unplug, power on, power off and the plug it again, now it should be fine.
10. Wait for download to finish and then your phone should be rebooted
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
mohitgaba14 said:
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing
And my bootloader is also locked how can i solve this problem pls help me
Click to expand...
Click to collapse
Look at the post above

Xiaomi Redmi 7A EDL mode don't turn off

Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.

SEBILOWSKI said:
Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.
Click to expand...
Click to collapse
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.

SubwayChamp said:
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.
Click to expand...
Click to collapse
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.

SEBILOWSKI said:
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.
Click to expand...
Click to collapse
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.

After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?

SEBILOWSKI said:
After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?
Click to expand...
Click to collapse
SubwayChamp said:
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.
Click to expand...
Click to collapse
.

SEBILOWSKI said:
.
Click to expand...
Click to collapse
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.

SubwayChamp said:
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.
Click to expand...
Click to collapse
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.

SEBILOWSKI said:
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.
Click to expand...
Click to collapse
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
{
"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 this box is checked, only these items are listed...
And when you uncheck this box, you'll see other options
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.

SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
Więc nie martw się, nie musisz znajdować więcej sterowników, ani robić nic więcej, PO PROSTU zaktualizuj poprawnie sterowniki, w tym konkretnym elemencie, gdzie jest wymieniony pod Port COM.
Click to expand...
Click to collapse
SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.
Click to expand...
Click to collapse
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication

SEBILOWSKI said:
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication
Click to expand...
Click to collapse
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.

SubwayChamp said:
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.
Click to expand...
Click to collapse
I still don't know how to solve this, can I contact you through something other than XDA and help me?

SEBILOWSKI said:
I still don't know how to solve this, can I contact you through something other than XDA and help me?
Click to expand...
Click to collapse
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.

SubwayChamp said:
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.
Click to expand...
Click to collapse
I keep getting it, don't know what to do with it anymore

SEBILOWSKI said:
View attachment 5846575
I keep getting it, don't know what to do with it anymore
Click to expand...
Click to collapse
I´m pretty sure, unfortunately, that the motherboard got damaged, and needs a replacement.
I had the exact situation, with a device in the past, no matter what I did, I couldn´t get it to work, but then, replaced the motherboard, and need to flash something through EDL mode, at the first attempt it worked fine,
There are another repairing method. that is anyway, up to the service center, the motherboard can be repaired, but, most of times, they consider, that the effort don´t worth it, and they ask just for a replacement, the procedure is called reballing, but again, like most of times, they don´t want to do it, not even, will mention that.