Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Related
Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
I rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
mypenismighty said:
I rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
Click to expand...
Click to collapse
volume up button + plug the phone into the computer here is everything you need for stock in one thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
mypenismighty said:
I rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
Click to expand...
Click to collapse
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
jameslee2 said:
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
Click to expand...
Click to collapse
I linked you in the other thread
ThePagel said:
volume up button + plug the phone into the computer here is everything you need for stock in one thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
mypenismighty said:
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
Click to expand...
Click to collapse
Are you using the stock data cable. Also try pulling the battery for 10 sec then pluging in the USB.
Sent from my LG-D851 using XDA Free mobile app
jameslee2 said:
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
Click to expand...
Click to collapse
adb reboot download
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
mypenismighty said:
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
Click to expand...
Click to collapse
I think you made a wrong procedure.
Take the battery out and put back in.
Press and hold volume up button.
Plug in the cable.
Release the button when you see download mode screen.
In addition, make sure you have LG PC Suite with phone driver installed.
Cal-El said:
Are you using the stock data cable. Also try pulling the battery for 10 sec then pluging in the USB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
mingkee said:
adb reboot download
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
I think you made a wrong procedure.
Take the battery out and put back in.
Press and hold volume up button.
Plug in the cable.
Release the button when you see download mode screen.
In addition, make sure you have LG PC Suite with phone driver installed.
Click to expand...
Click to collapse
Thanks but I have already done this with the same result as I've described. I know how it is supposed to be done with the hardware keys and I am using the stock data cable. Even watched a YouTube video demonstrating how it is to be done. Are there any other possibilities?
Just tried it with my nexus 7 cable on a different usb port (which I had done couple times before) and it worked this time! Not sure why or how but appreciate the help, everyone!
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
souvenir1977 said:
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
Click to expand...
Click to collapse
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Still_living714 said:
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Click to expand...
Click to collapse
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
souvenir1977 said:
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
Click to expand...
Click to collapse
have you tried putting it into download mode?
Still_living714 said:
have you tried putting it into download mode?
Click to expand...
Click to collapse
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
hmm very weird. I had a similar problem were the phone wouldn't boot unless I had it plugged into the charger or my computer,give that a try.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
when I had that problem I figured out that it was the battery that was making the phone act weird. Since LG sent me another battery when they had the promotion I used the other spare and that fixed it for me.
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
souvenir1977 said:
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
Click to expand...
Click to collapse
well it's hard to say but without the phone being able to boot there's not anything you can do.....
you are right, flashing need the download mode....
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
jkjambo said:
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
Click to expand...
Click to collapse
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
souvenir1977 said:
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
Click to expand...
Click to collapse
that's what i mean , lge serial xxx , don't remeber exactly . it's in qhsusb mode , hardbricked ...
there is some indian guys who do that , some for free, some for little amount of money ...
search for lg g3 unbrick Qhsusb 9008... don't waste time on tutorials , non of them works with D851 ... i'm in same boat (again ) and tried everything .. nothing works , unless you're connected to lg servers directly , search for people which fixs them
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
jkjambo said:
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Click to expand...
Click to collapse
souvenir1977 said:
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
Click to expand...
Click to collapse
This is why You don't flash the boot chain unless you absolutely must. I was running 20B with the old boot chain (other than rpm, that was updated) and it ran just fine. If you get a bad flash on the boot chain your sol.
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Did you install it thru TWRP?
thekingestkong said:
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Click to expand...
Click to collapse
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
no, the phone picked up the update from the internal storage
dc959 said:
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
Click to expand...
Click to collapse
thanks, I'm aware of that. Some folks experiencing the same issue tried that with no success. My phone is still under warranty and the screw securing the backplate has a seal on it that I dont want to tamper with.
I guess I'll be sending the phone for to Asus for repair...
Don't lose hope.
My phone was in a similar predicament.
No response to any buttons, nothing on screen, no buzzing or LED's at all.
I was able to get it recognized in the xFSTK Downloader and showing up in windows device manager as a Moorefield device.
I tried many times to get it to put the images on the phone through the xFSTK tool and it failed many times.
I was about to give up and tried again this morning and miraculously the writing succeeded and now my phone is in a bootloop (I think the battery may have been completely drained with my attempts to save it's life.)
I have it on charge currently so hopefully when there is enough juice I should be able to flash the raw file and be back up and running.
I see, you can follow the unbricking tutorial in the general section. Works fine for me and saved me from sending it to the service center.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
galagala2 said:
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
Click to expand...
Click to collapse
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
krazy23 said:
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
Click to expand...
Click to collapse
do you lose the data this way?
thekingestkong said:
do you lose the data this way?
Click to expand...
Click to collapse
Unfortunately, yes. Because I ticked the "wipe data" checkbox in the ASUS Flash Tool. Not sure what will happen if I don't. :fingers-crossed:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfon
I also bricked my phone and used the method to fix my phone. Make sure you have all the required drivers installed in your pc/laptop before doing this. I took help of DriverMax to solve the drivers related issues. Make sure before installing and running the XFTSK tool all the drivers and everything is installed otherwise you will see blank forms in the Tool.
Hi Mates,
I have 1789-06 variant with unlocked bootloader.
I installed the pie version via flashall, all were OK.
but upon rebooting the splash screen prompted for "verity mode is set to disabled".
no matter what I tried, all failed - the phone reboots to the fastboot screen.
then I was wondering BP Tools mode where on the screen it was showing "disabled".
somehow I enabled and attempted to reboot - the screen went total black!
is there anything that can revive the phone?
thanks in advance for the support.
cheers.
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
41rw4lk said:
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
Click to expand...
Click to collapse
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
beefytr said:
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
Click to expand...
Click to collapse
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
41rw4lk said:
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
Click to expand...
Click to collapse
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
beefytr said:
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
Click to expand...
Click to collapse
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
41rw4lk said:
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
Click to expand...
Click to collapse
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
beefytr said:
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
All the best mate.
Thanks.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
what if what you advise does not work at all?
then it is a dead one?
beefytr said:
what if what you advise does not work at all?
then it is a dead one?
Click to expand...
Click to collapse
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
41rw4lk said:
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
Click to expand...
Click to collapse
thanks bro.
I will not bother for JTAG as it is - as you have rightfully said - untested.
my phone is still under warranty and I will try a replacement or a refund then.
cheers.
What did you do to boot your device.. Even mine is bootlooped.
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
What did you do to boot your device.. Even mine is bootlooped.
... Is it bootlooping or does it just not power on at all?