(UPDATE)Bricked?! Can't get into fasboot or recovery - Nexus 6 Q&A, Help & Troubleshooting

I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Thank you all for your info and help, I ended up sending it in to Motorola, and they have replaced it at no cost. I am just thankful that i am able to get back to the Nexus!!!!

Jess813 said:
I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Click to expand...
Click to collapse
Have you tried to get into bootloader mode and is the phone visible in device manager?

Yup you are bricked check your device manager. We already have a thread on this.

Yeah device manager shows nothing. Wow ... That's crazy I've been doing this for years, is not like it was a file that I hadn't used before.

Jess813 said:
I was on LiquidsSmooths ROM and wanted to go back to CM12 so I flashed an old nightly I had used before03082015, so I flashed the ROM then gapps then wiped dalvik, then reboot. My phone went into a black screen and that's it...when I connect to the PC the PC makes a sound like it recognizes it, but nothing.Any suggestions????
Click to expand...
Click to collapse
long press the power button for about 20 seconds. after about 3-4 seconds, press volume down as well. this should reboot your device into the bootloader. try it.

Jess813 said:
Yeah device manager shows nothing. Wow ... That's crazy I've been doing this for years, is not like it was a file that I hadn't used before.
Click to expand...
Click to collapse
it only says this when it trys to install drivers "A request for the USB device descriptor failed"

simms22 said:
long press the power button for about 20 seconds. after about 3-4 seconds, press volume down as well. this should reboot your device into the bootloader. try it.
Click to expand...
Click to collapse
While being connected to a pc?

gee2012 said:
Have you tried to get into bootloader mode and is the phone visible in device manager?
Click to expand...
Click to collapse
In device manager it shows up as QHSUSB_BULK....

Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks

beachbum40 said:
Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks
Click to expand...
Click to collapse
how u get yours fixed?

I just used this .http://forum.xda-developers.com/showthread.php?t=2954008I used the method 2 part flashed everything one by one but the problems I was getting was system package not found and image not found in flash all scripts but method 2 got me going.
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
I'm sorry no I didn't use his guide that was giving me wayyy to many issues this is the guide that saved me.http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865

beachbum40 said:
Sorry for this happening to you bro. I know the feeling I was also having major problems with update but eventually got it up and running . Good luck to you and every one else that's unfortunately bricked there n6's it ashame that this is happening to so many folks
Click to expand...
Click to collapse
beachbum40 said:
I just used this .http://forum.xda-developers.com/showthread.php?t=2954008I used the method 2 part flashed everything one by one but the problems I was getting was system package not found and image not found in flash all scripts but method 2 got me going.
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
I'm sorry no I didn't use his guide that was giving me wayyy to many issues this is the guide that saved me.http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Click to expand...
Click to collapse
Was your phone hard bricked? Like you coukdnt get into fastboot? or recovery?

Jess813 said:
Was your phone hard bricked? Like you coukdnt get into fastboot? or recovery?
Click to expand...
Click to collapse
Fortunately I was still able to get into boot loader on my device and fastboot manually all the images but I'm seeing a lot of folks not being able too.
---------- Post added at 01:42 AM ---------- Previous post was at 01:41 AM ----------
beachbum40 said:
Fortunately I was still able to get into boot loader on my device and fastboot manually all the images but I'm seeing a lot of folks not being able too.
Click to expand...
Click to collapse
To answer you first question no it wasn't hard bricked thankfully
---------- Post added at 01:46 AM ---------- Previous post was at 01:42 AM ----------
Sounds like your partitions got locked up or corrupted I'm still searching for fixes for the problem just in case it happens next time I have to do an update

I had to rma I'm waiting on new device. Lost everything

Created an RMA and shipped it out today , will hope for the best, will update.

Just got notification that its been replaced and sent back!!! Woot Woot!!

They sent me an all new device, box and new power plug and everything.

coldconfession13 said:
They sent me an all new device, box and new power plug and everything.
Click to expand...
Click to collapse
Was yours unbranded ? Mine arrives tomorrow and I'm wondering if they ate going to send me an unbranded Nexus as mine was AT&T branded and unlocked to work on T-Mobile. I hope I don't have to unlock it again, it was a PAIN to do so.

Unbranded.
Sent from my Nexus 6 using Tapatalk

coldconfession13 said:
Unbranded.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
But you got an all new box and charger ? I hope I get the same, brand new device too? As in new Imei #?

Related

Warning 10.1" CWM incompatibility - BRICKED!

Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Bec07 said:
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Click to expand...
Click to collapse
At least its only a soft brick...
Definitely good to know...sorry you went through the hassle to find out.
Thanks for sharing with us, lets hope someone can get a recovery working soon so I can be more dangerous!!!!
Sent from my GT-P7310 using xda premium
http://forum.xda-developers.com/showthread.php?t=1133590
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Bec07 said:
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Click to expand...
Click to collapse
Be careful. Sometimes it clears your SD card as well (depending on what exactly you're doing).
To be safe, make a backup of you SD card on your computer.
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
Click to expand...
Click to collapse
Sweet bro.
Sure wished I'd seen this message last night.....
Well, now to see if I can fix mine.
-dana
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Amateur Geologist said:
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Click to expand...
Click to collapse
A hard brick is when nothing shows up no matter what. Screen stays black no matter what you do, power button doesnt work, you cant get into any recovery or bootloader or anything..
I was a little iffy to install it...so glad I didn't. Had some issues with it on my GS2..pfft
i think i have bricked mine new P 7500
but there is nothing wrong i did with this device
tab is now in only conecting in APX
NVIDIA USB Boot-recovery driver for Mobile devices
no sign of charging and no light on display
is there any way to recover it back??????????
this is semi or hard bricked?????
How? this thread is meant for the 8.9 tabs...
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Click to expand...
Click to collapse
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Dunbad said:
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Click to expand...
Click to collapse
Trapped myself in this lobster pot too. Probably hold the record for purchase to soft brick in 10 hrs!
there is a link in second post from op which has the roms and the flashing software (Odin)eunfortunately they only had a 7310 rom when I looked. You need a 7300 rom for your phone to work. Please read as many forums as you can on this first. I ended up flashing an Asian image just to get back on my feet, then ended up flashing overcome and over clocking which works very well. Wish you luck!
same
same thing happened to me .I should of looked here before trying a backup. Used Odin to install this and its all good, and 3.2. megaupload.com/?d=0KYNVV4Z
FYI, I was stupid yesterday and allowed ROM manager to update my recovery partition (it told me there was an update available). Of course the update was for a Tab 10.1 and soft bricked my tab (it went into a boot loop). I recovered by going into download mode and using odin to flash only Tab 8.9 clockwork recovery image.
So, if anyone else bricks their tab by using an incompatible recovery, you should be able to recover back to where you were by just flashing a compatible recovery instead of using a full odin ROM.

Hard bricked

So i've had a CM9 Beta 1 build on my phone, it was running like a charm past week, so while surfing around internet i've found a flashable zip that makes your status bar look like Jellybean (Specified it works with CM9 Beta 1!) and i've got stuck in recovery bootloop like the last time.
I've tried various way's, one of those was to reflash the ROM or flash a stock ROM from Odin, and it keeped getting stuck on stage VerifyPlatform...
So i've found a thread that fixes all of this mess with a .bat file for computer, and after using it my phone actually died.
I can't turn it on, it's all black..
I think i'm seriously lost...
I'm hoping for exact help that could fix it, not an maybe, i seriously need help! ;(
Kramtoske said:
So i've had a CM9 Beta 1 build on my phone, it was running like a charm past week, so while surfing around internet i've found a flashable zip that makes your status bar look like Jellybean (Specified it works with CM9 Beta 1!) and i've got stuck in recovery bootloop like the last time.
I've tried various way's, one of those was to reflash the ROM or flash a stock ROM from Odin, and it keeped getting stuck on stage VerifyPlatform...
So i've found a thread that fixes all of this mess with a .bat file for computer, and after using it my phone actually died.
I can't turn it on, it's all black..
I think i'm seriously lost...
I'm hoping for exact help that could fix it, not an maybe, i seriously need help! ;(
Click to expand...
Click to collapse
do u have i9001 or i9000?I dont know how to fix it.I would give it to samsung to repair it.
cistamlaka said:
do u have i9001 or i9000?I dont know how to fix it.I would give it to samsung to repair it.
Click to expand...
Click to collapse
It's i9001.
I can't give it to Samsung, it's rooted! D:
Kramtoske said:
It's i9001.
I can't give it to Samsung, it's rooted! D:
Click to expand...
Click to collapse
Did you try pulling out the battery for 15 minutes, then try to get to download mode?
Can u get into download mode?
If my post helped, don't mind hitting THANKS
drakester20 said:
Can u get into download mode?
If my post helped, don't mind hitting THANKS
Click to expand...
Click to collapse
So far i did not pulled out battery for 15 minutes, so i'm not sure if this is normal, but the download mode combination does not work. :/
See HERE,i think it would help you.
Lol.. I accidentally hit the thanks button... maybe u can throw one back...
So I was just gonna reply that he can't get into download mode so this is useless my friend..
If my post helped, don't mind hitting THANKS
---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------
U don't even get that phone to pc disrupted like connection picture when u try to boot?
If my post helped, don't mind hitting THANKS
i9000 use hummingbird chip .. can use usb jig or if detect as sp5c110, can use unbrickable mod software to revive it (if not detect then have to do hw mod)
i9001 use different chip ie msm8255t .. try the button combination or usb jig to get into download mode. If it detect as qusb_load something then there might still have chance. If still nothing I'm afraid only jtag/riffbox can help.
I once bricked a Galaxy W i8150 (msm8255t) because of wrong bootloader flashed. Usb jig don't work. Had to use riffbox to revive it.
Yeah if jig doesn't work then u gotta replace the jtag
If my post helped, don't mind hitting THANKS
Hello, it's been a while. Thanks for all the feedback people.
I'm not trying to bump or anything, just saying that i've brought the phone to my carrier and played a little dumb game, lied and got it to be fixed. I hope to get good news soon.
Kramtoske said:
Hello, it's been a while. Thanks for all the feedback people.
I'm not trying to bump or anything, just saying that i've brought the phone to my carrier and played a little dumb game, lied and got it to be fixed. I hope to get good news soon.
Click to expand...
Click to collapse
Lols i almost got the same issue with my I9001. I would have blamed KIES...

Red Triangle Stock Sense 6 update

Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)
Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse
Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.
alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?
Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia
akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.

[Q] HTC One GPE - RUU Install - Phone Shut Down

Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
LATOKYO said:
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
Click to expand...
Click to collapse
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
alray said:
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
Click to expand...
Click to collapse
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
LATOKYO said:
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
Click to expand...
Click to collapse
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
But why? It was completely fine yesterday. The battery was perfect. Why does it completely fail after I do the RUU?
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
There needs to be a way to solve this issue. It cannot be coincidental that it just fails now.
LATOKYO said:
But why? It was completely fine yesterday.
Click to expand...
Click to collapse
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
The battery was perfect. Why does it completely fail after I do the RUU?
Click to expand...
Click to collapse
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
alray said:
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
Click to expand...
Click to collapse
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
LATOKYO said:
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
Click to expand...
Click to collapse
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
alray said:
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
Click to expand...
Click to collapse
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
LATOKYO said:
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
Click to expand...
Click to collapse
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on.
Click to expand...
Click to collapse
Yep and in some cases also went back again in dload mode later....
Anyway good luck
alray said:
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
Yep and in some cases also went back again in dload mode later....
Anyway good luck
Click to expand...
Click to collapse
So now when I plug in the device, it says " USB input device"
Good news, bad news?

Mi K3 Note doesn't boot

I tried all tutorials that I was able to find but, I can't fix the trouble. My K3 note reboot over and over again in an eternal boot. I flash the phone a few times today, in all of the ways Download Only, Firmware Upgrade and Format All+Download with a lot of stock ROMs and revival ROMs . I need help please. (Forgive me for my bad English)
what was the cause
---------- Post added at 06:48 AM ---------- Previous post was at 06:48 AM ----------
what was the cause
I don't know I bought the phone a guy and I don't know the cause
okie
thereaper_98 said:
I don't know I bought the phone a guy and I don't know the cause
Click to expand...
Click to collapse
so,,you brought a damaged phone from someone..wow.
anyways...look whther you can anyhow enter the recovery mode .
Yes I think it will be easy but not. Yes I can entry to recovery mode but if I install a Rom sometimes it start the boot animation but not for so much time It reboots again
Replace battery with lenovo or local one.
thereaper_98 said:
Yes I think it will be easy but not. Yes I can entry to recovery mode but if I install a Rom sometimes it start the boot animation but not for so much time It reboots again
Click to expand...
Click to collapse
Most probably it's battery is a faulty one. Try replacing it. Exactly same thing happened with my friend's Yu Yureka, and replacing the battery fixed it.

Categories

Resources