HardBrick By Flashing Recovery Only !!! Showed QHSUSB_Bulk Help Please - Nexus 6P Q&A, Help & Troubleshooting

hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?

Google probably won't do anything for you as you installed it at your own risk

mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.

Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.

Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.

anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)

mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.

Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help

mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.

@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.

mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc

If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse

mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.

mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.

Related

D802 bricked?

Hey guys, i dont know if its bricked or not, but i have download mode and recovery, i am on stock, but ... my modem is unknown, and after several kdz upgrade stills so .. could it be that my partitions are wrong? i rooted and changed recovery, and my recovery is not properly functional ... sometimes looking via explorer I see the "0" folders but should they dont be removed by turning back to stock via lg support tool?
Thanks for help!
Greetings
vyrus973 said:
Hey guys, i dont know if its bricked or not, but i have download mode and recovery, i am on stock, but ... my modem is unknown, and after several kdz upgrade stills so .. could it be that my partitions are wrong? i rooted and changed recovery, and my recovery is not properly functional ... sometimes looking via explorer I see the "0" folders but should they dont be removed by turning back to stock via lg support tool?
Thanks for help!
Greetings
Click to expand...
Click to collapse
now it works, damn wtf asigjkalö but what have i to do now? Root does not work so i cant do a full recovery
vyrus973 said:
now it works, damn wtf asigjkalö but what have i to do now? Root does not work so i cant do a full recovery
Click to expand...
Click to collapse
still totally buggy .. any ideas please? How much would it cost to reset the chip at a LG centre? g
ty
@vyrus973 dont use lg flashtool now, read the go back to stock guide and flash your phone with .tot or kdz again, root the phone, install recovery and if your modem is still unknownnyou flash it from this forum.
wulsic said:
@vyrus973 dont use lg flashtool now, read the go back to stock guide and flash your phone with .tot or kdz again, root the phone, install recovery and if your modem is still unknownnyou flash it from this forum.
Click to expand...
Click to collapse
flashed with kdz to 4.2.2, rooted, flashed recovery, flashed baseband, still buggy ... now i did the same and toggled the ROOTED status from download mode and i upgrade to the latest, so maybe I can say to LG centre that after ota bricked, its in warranty, or should i do something else?
greets
@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.
wulsic said:
@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.
Click to expand...
Click to collapse
i just played on my efs backup 1 week ago, but did anything, is there any other method to fix it?
greets
wulsic said:
@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.
Click to expand...
Click to collapse
i just played on my efs backup 1 week ago, but did anything, is there any other method to fix it?
the bug is that he dont start the service, he does not even try to read my sim card, still no connection, and he self restarts like a loop, so i cant even use it really long time, sometimes he gets connection but even than with really bad signal, when i put on fly mode and return back he does not connect more, even the data connectivity than does not work, since i flashed the optimus v3 rom, i tried each kdz for my phone but no one did really fix it, sometimes at the first runtime it function and than after restart still buggy aaaaa its make me crazy, actually i am using a 6inches big china phone and that cant be a permanent solution.
greets
@vyrus973 so you still have the backup? If so then you can try to restore it. You can also google about g2 efs recovery to restore it but I am not sure if it is possible. I think that your efs partition is corrupted or got removed.
wulsic said:
@vyrus973 so you still have the backup? If so then you can try to restore it. You can also google about g2 efs recovery to restore it but I am not sure if it is possible. I think that your efs partition is corrupted or got removed.
Click to expand...
Click to collapse
i restored it many times, i backuped it on 4.2.2 and on 4.4.2 but anyone does properly function, i went in the assistent center and they are going to sent it to labor, at the end i restored all, i hope that they cant see that i played with the root/bootloader, in download mode is written UNROOTED, hopes thats all ahah, in 7 days I update
greets
@vyrus973 ahh okay, if you flashed back to stock and removed root temper flag then you should be okay. If you live in europe then it didnt matter that you had rooted your phone I thought. But your download mode said unrooted so the temper flag got resetted.
Goodluck with your phone and have fun with it, dont brick it
wulsic said:
@vyrus973 ahh okay, if you flashed back to stock and removed root temper flag then you should be okay. If you live in europe then it didnt matter that you had rooted your phone I thought. But your download mode said unrooted so the temper flag got resetted.
Goodluck with your phone and have fun with it, dont brick it
Click to expand...
Click to collapse
ahahah i were not happy with the g2, nice design but mhhh don´t know ... i think after i´ll sell it, and yes i live in italy so ehehe *finger crossing* hope it will go all right ahah at the end i dont think they have to repair hardware, just plug it in their universal computer and flash all again, at the worst case they have to open it and flash on board yey

D802 no recovery after failed TWRP install on 5.0.2

i have experimented with custom ROMs on this phone in the past but have been using the stock lollipop 5.0.2 ROM for a while now after reverting back with a KDZ and so i figured i knew what i was doing.
i found out about the recent stability of cm13 nightlies on this device and wanted to give one a try so i decided to root the device with super su, which went well and then attempted to install TWRP with autorec for lollipop. It stated that the installation was a success and to reboot but when i did, it booted to a black screen.
i found this thread http://forum.xda-developers.com/showthread.php?t=2582142 which seems to say that i should be able to fix it if my device shows qualcomm 9006 in the ports menu, however my device shows up as marshall london HS-USB Diagnostics 9006, and i don't know what jellybean version this device was running so i dont know what images to use to to attempt this method anyway. I'm hoping someone more experienced with this **** that me will be able to tell me how to fix this. thanks for the help, King of Hard Bricks
try to see if skr tools works .. if not see in no download no recovery thread.. or post in back to stock thread.
not sure if that error is the one you need to short circuit your motherboard.. but search fisrt those places...cause i think somone suggested to do another step instead of the short circuit way..
raptorddd said:
try to see if skr tools works .. if not see in no download no recovery thread.. or post in back to stock thread.
not sure if that error is the one you need to short circuit your motherboard.. but search fisrt those places...cause i think somone suggested to do another step instead of the short circuit way..
Click to expand...
Click to collapse
I used the unbrick tool and my phone is working, thanks man
KINGOFHARDBRICKING said:
I used the unbrick tool and my phone is working, thanks man
Click to expand...
Click to collapse
Am glad you sort it out, now pass the knowledge to other is same situation. :good:

There is no lineage development for the LG K8?

As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
caedmonro said:
As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
Click to expand...
Click to collapse
No, we can`t even flash twrp on the phone... i guess until then there is no chance to flash another rom at all.
I could not flash twrp and therefore boot rom cm14
Still there is apparently I try to port but I brickea, porte recovery twrp for lg k350h and experiencing I found a way to rootearlo at the beginning with the help of a friend but the steps were very long which was brickeaba easily now I saw that simplified it Thanks to a user of xda, thank you very much, after doing all that porte rom but was stuck in the logo, so far I could not flash twrp just boot because it is restored to the factory what I discovered is that the recovery is independent Of the menu that appears to be the recovery that shows two buttons if or not try in all possible ways but I have not succeeded
lineage 15.0 lg k8 android 8.0
caedmonro said:
As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
Click to expand...
Click to collapse
There is one but I install it and the hard brike we go that I was left without mobile and neither doing the test point nor in mode meta a brick.
lineageosroms.org/forums/topic/lg-k8-lineage-os-15-android-oreo-ro
tattoosmistery said:
There is one but I install it and the hard brike we go that I was left without mobile and neither doing the test point nor in mode meta a brick.
lineageosroms.org/forums/topic/lg-k8-lineage-os-15-android-oreo-ro
Click to expand...
Click to collapse
Well, you shouldn't ever download anything from sites which have similar name to some ROM but it's not officiall site, in most cases that are sites who just want visits without actuall content. Also in ROM file name there is 64bit and AFAIK none of K8's have 64bit kernel. Next thing recovery they provided is over 16mb in size, that is a recipe for getting bricked in best case it will refuse to boot/flash, also kernel offset ramdisk offset are wrong according to my model (k350nds), that is also good recipe, I didn't check the kernel but I doubt it's right one, I'll unpack ROM just to see what is inside.
When you download ROM please use only trusted sites.
Edit: this is ROM for Tecno camon c7 its same chipset but it doesn't mean it is suitable for our phone. Whoever created this and said it's for k8 is an first class A-hole..
Professor Woland said:
Well, you shouldn't ever download anything from sites which have similar name to some ROM but it's not officiall site, in most cases that are sites who just want visits without actuall content. Also in ROM file name there is 64bit and AFAIK none of K8's have 64bit kernel. Next thing recovery they provided is over 16mb in size, that is a recipe for getting bricked in best case it will refuse to boot/flash, also kernel offset ramdisk offset are wrong according to my model (k350nds), that is also good recipe, I didn't check the kernel but I doubt it's right one, I'll unpack ROM just to see what is inside.
When you download ROM please use only trusted sites.
Edit: this is ROM for Tecno camon c7 its same chipset but it doesn't mean it is suitable for our phone. Whoever created this and said it's for k8 is an first class A-hole..
Click to expand...
Click to collapse
What do you mean, I got left without a phone or got an arrangement?
tattoosmistery said:
What do you mean, I got left without a phone or got an arrangement?
Click to expand...
Click to collapse
Sorry I don't understand what are you trying to say..
gottlasz said:
No, we can`t even flash twrp on the phone... i guess until then there is no chance to flash another rom at all.
Click to expand...
Click to collapse
if you flash recovery what happens ? it bootloops or it gets replaced by stock ? I have an idea on how to make it work ...
KevMetal said:
if you flash recovery what happens ? it bootloops or it gets replaced by stock ? I have an idea on how to make it work ...
Click to expand...
Click to collapse
If you flash it then the phone will not boot up just turn off after the warning message. Its becouse the recovery partition is checked during boot up so the lk (little kernel / bootloader) partition should be tweaked first to skip recovery checking...
gottlasz said:
If you flash it then the phone will not boot up just turn off after the warning message. Its becouse the recovery partition is checked during boot up so the lk (little kernel / bootloader) partition should be tweaked first to skip recovery checking...
Click to expand...
Click to collapse
have you tried flashing a no dm -verify .zip before booting
KevMetal said:
have you tried flashing a no dm -verify .zip before booting
Click to expand...
Click to collapse
Yes, but that zip only tweaks the boot image... (and it doesn't even work for our device)
then, first we need to get rid of the little kernel, so we can flash twrp and just then we can think in porting a lineageos rom for it?
SummonerArthur said:
then, first we need to get rid of the little kernel, so we can flash twrp and just then we can think in porting a lineageos rom for it?
Click to expand...
Click to collapse
Well if we get rid of it completely it will probably won't work at all, we need someone to alter function that checks if kernel or anything else is legitimate so that function always return true. If that is how it work.

BRICKED! any fkx for this?

Hi guys
Well after messing with my phone trying to get root I finally bricked it big time. No power at all. Totally dead. Except it does show 9008 mode when connected to the computer.
I had gotten TWRP installed in the DirtySanta rooting process then flashed a stock ROM and then flashed Super SU. I flashed super su immediately following the flashing of the ROM. Not sure if I was supposed to reboot THEN flash super su. But I read in a thread that I didnt need to reboot between ROM and super su.
It was totally my fault...looking for a possible fix..as small a chance of that maybe.
Tha ks in advance!
markmessier8888 said:
Hi guys
Well after messing with my phone trying to get root I finally bricked it big time. No power at all. Totally dead. Except it does show 9008 mode when connected to the computer.
I had gotten TWRP installed in the DirtySanta rooting process then flashed a stock ROM and then flashed Super SU. I flashed super su immediately following the flashing of the ROM. Not sure if I was supposed to reboot THEN flash super su. But I read in a thread that I didnt need to reboot between ROM and super su.
It was totally my fault...looking for a possible fix..as small a chance of that maybe.
Tha ks in advance!
Click to expand...
Click to collapse
If there is kdz for your model you can flash that.
Still_living714 said:
If there is kdz for your model you can flash that.
Click to expand...
Click to collapse
Yes i have the .kdz file but how to run the program
You can't flash KDZ when the phone is in 9008 mode. There are no options currently. Your phone is as good as dead.
But, we are looking into a de-BRICK method, involving SD-Card boot. May or may not work.
Still_living714 said:
If there is kdz for your model you can flash that.
Click to expand...
Click to collapse
askermk2000 said:
You can't flash KDZ when the phone is in 9008 mode. There are no options currently. Your phone is as good as dead.
But, we are looking into a de-BRICK method, involving SD-Card boot. May or may not work.
Click to expand...
Click to collapse
Ok..cross my fingers
Can the LG service center fix this if I bring my phone to them?
markmessier8888 said:
Ok..cross my fingers
Can the LG service center fix this if I bring my phone to them?
Click to expand...
Click to collapse
If not fix, they probably will replace the motherboard for you, if you're under warranty.
askermk2000 said:
If not fix, they probably will replace the motherboard for you, if you're under warranty.
Click to expand...
Click to collapse
Ok thx!
Will the LG service center know that I tried to root or tried to modify my phone?
I will go in person to my local LG service center tomorrow
Probably will not if they simply replace the motherboard.
That is what they seem to do, but I can't be sure. Might depend on the service center.
When I bricked mine the first time they just did a MB swap, but I specifically told them I flashed the wrong file. I didn't mention root though. I let them imply that I used LG UP and it failed somehow
Do you guys think the reason it bricked is because of the wrong ROM or because I didnt reboot after installing the ROM and flashed SUPER SU directly after and then I rebooted?? I did it through TWRP
markmessier8888 said:
Do you guys think the reason it bricked is because of the wrong ROM or because I didnt reboot after installing the ROM and flashed SUPER SU directly after and then I rebooted?? I did it through TWRP
Click to expand...
Click to collapse
9008 is usually due to flashing the wrong kdz or erasing your bootloader. a rom will not cause 9008

Hard bricked,only vibrates

Hello guys,i was trying to flash LOS and after many tries i hard bricked my phone.At start,screen wasnt turning on and phone vibrated sholtly every 1 sec.I did EDL and then flashed different roms but still phone just vibrates but for a bit longer.When i do EDL it gets recognised by pc.Also when i flash a rom before i try to boot,if i connect it to power the led is blinking.
I dont want to be this guy who opens a thread that has opened many times,but i couldnt figure out a solution whatsoever.Thanks in advance.
Did you try downgrade from pie to oreo? Can you enter fastboot mode?
I bricked my phone too. Nothing worked for me. I hope you have more luck.
How it got bricked? Did you read the whole tutorial ?
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
degen1997 said:
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
Click to expand...
Click to collapse
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
emiljano539 said:
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
Click to expand...
Click to collapse
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
Check it :https://forum.xda-developers.com/showpost.php?p=75711835&postcount=2
I hope it helps
degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
XtraWater said:
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
Click to expand...
Click to collapse
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
emiljano539 said:
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
Click to expand...
Click to collapse
I recommend you to read a lot about flashing custom ROMs before trying to do it.
LineageOS has a pretty explicit installing tutorial.
If you can get into fastboot mode there is hope.
Remember that you must have the bootloader unlocked.
my thread
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
Hi everyone, I have rooted Mi A1 (pie), I have a hard brick. but fixed, when flashing Rom with TWRP, my phone cannot receive the partition / 'cache', when root receives the message: error: 28, I need help, thank you very much

Categories

Resources