I'm quite perplexed. I was using my p600 today, and it worked fine like normal. Tonight I took it out to do some reading, and noticed some flickering streaks across the screen. I thought nothing of it, and did a reboot.
It turned off, but never rebooted. The back and menu buttons flashed once, and then went dark.
I've been trying without success to get it to boot for a half hour, nothing. There is no response to plugging it into a charger, and my computer does not recognize it as being plugged in. (Currently have no access to windows, so unsure of ODIN).
I was running Tamasek's unnoficial 18.1 build at the time.
Any ideas. Would greatly appreciate any help, even just to get some notes off if it is indeed dead.
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
diabl0w said:
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
Click to expand...
Click to collapse
Doesn't seem to work for me.
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
greenmatrix said:
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
Click to expand...
Click to collapse
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
Thanks, I'll let you know how it goes.
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
I am unable to get the p600 to show under adb devices. However, adb does work successfully for my nexus 6 so it appears to be generally working.
This is on mac, so I don't believe it could be a driver issue. I spent a good while trying to get adb working on windows with no success for either device (killed and restarted adb server, tried reinstalling drivers, different cables, etc).
Frustrating, because the p600 will connect fine to the computer, and I can view files and interact with it. Odin also recognizes it.
I appreciate the help, and any further ideas.
if odin recognizes it then why dont you just try to flash stock again?
diabl0w said:
if odin recognizes it then why dont you just try to flash stock again?
Click to expand...
Click to collapse
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
greenmatrix said:
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
Click to expand...
Click to collapse
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
diabl0w said:
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
Click to expand...
Click to collapse
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
greenmatrix said:
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
Click to expand...
Click to collapse
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
diabl0w said:
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
Click to expand...
Click to collapse
Yeah, when I flashed TWRP a few weeks ago I believe i used odin 1.8x, can't remember. However I know that it wasn't 3.10.7. I'll see how 3.10.7 works.
It appears to still be hanging on SetupConnection.
greenmatrix said:
It appears to still be hanging on SetupConnection.
Click to expand...
Click to collapse
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
diabl0w said:
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
Click to expand...
Click to collapse
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
im glad you were able to figure it out
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
epithetic said:
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
Click to expand...
Click to collapse
This was exactly it. 15 minute fix and everything was golden.
Related
OK here's the quick version of what happened.
Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
eqjunkie829 said:
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
Click to expand...
Click to collapse
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
cubsfan187 said:
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
Click to expand...
Click to collapse
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
cupfulloflol said:
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
Click to expand...
Click to collapse
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
cubsfan187 said:
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
Click to expand...
Click to collapse
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
cubsfan187 said:
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
cupfulloflol said:
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
Click to expand...
Click to collapse
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
cubsfan187 said:
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
cupfulloflol said:
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
Click to expand...
Click to collapse
This is exactly what I am gonna try after getting the new phone set up. :good:
Before posting I tried looking through every thread after I searched for this but it seems that there was always TWRP to fall back on.
Here's my problem thus far. Rooted my G Pad on Lollipop successfully. Followed this guide after rooting, to install TWRP recovery.
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
Followed the first step to downgrade the aboot to 4.2.2, then restarted the tablet like an idiot as I glanced at the wrong browser tab with a different tutorial open. I did NOT follow the second portion of the tutorial to get TWRP even installed and I'm sitting here with the Secure Booting Error in the top left corner. Cannot access download mode, factory reset, normal reboot or safe boot without getting that error. Any help here at all or is this the first time I'm SOL with a device.
UPDATE!
Managed to actually get it into download mode after 20+ tries of just rebooting and trying. Will update if I can successfully reflash with LG Flash Tool or not.
You should be able to flash it no problem since you're in Download mode. FYI, although it doesn't work all the time, someone in my ROM thread found a way to flash aboot (for instance, to flash the Lollipop aboot so you could get back into the ROM) from Fastboot mode. That is, they found a way that sometimes works to get into Fastboot mode.
Also, there's a chance you could perform the required steps to get TWRP installed via ADB with the tablet in Download mode. Not sure, though, since I haven't tried it.
I can certainly experiment, now that I've realized I can fall back on download mode if things go wrong. Flashed the Lollipop KDZ with no problem in download mode so at least the tablet is up and running to take another crack at. Thanks a ton for actually having those KDZ's so readily available being linked in your signature.
Sayt123 said:
I can certainly experiment, now that I've realized I can fall back on download mode if things go wrong. Flashed the Lollipop KDZ with no problem in download mode so at least the tablet is up and running to take another crack at. Thanks a ton for actually having those KDZ's so readily available being linked in your signature.
Click to expand...
Click to collapse
Cool, you're welcome mate!
roirraW "edor" ehT said:
Cool, you're welcome mate!
Click to expand...
Click to collapse
Ended up just downgrading to 4.2.2, using towelroot, and loki_flash\twrp. Enjoying CM12 now. Will probably update the original post with instructions in case someone makes the same mistake as me for some reason.
I'm Having the Same Issue
I cannot get download mode to work. Just the Lg symbol, and secure booting error in top left.
I charged it overnight, plugged into a wall, with it off.
Held both vol keys while off, and plugged into cpu using the original/undamaged cable. Tried a different cable that also works, and tried plugging it into the computer both ways (OFF and plugged in the computer first, then the tab, and vice versa.)
Was there any other trick you had getting into DL mode???
Any help is appreciated.
UPDATE: So i left the tablet plugged in, and just kept rebooting it, and held just power and vol up, and now, in a barely visible screen, it says download mode, but my computer thinks there's nothing connected. With 2 different cables, and 2 different flash tools saying this, even with correct drivers installed.
segadennisis76 said:
I cannot get download mode to work. Just the Lg symbol, and secure booting error in top left.
I charged it overnight, plugged into a wall, with it off.
Held both vol keys while off, and plugged into cpu using the original/undamaged cable. Tried a different cable that also works, and tried plugging it into the computer both ways (OFF and plugged in the computer first, then the tab, and vice versa.)
Was there any other trick you had getting into DL mode???
Any help is appreciated.
UPDATE: So i left the tablet plugged in, and just kept rebooting it, and held just power and vol up, and now, in a barely visible screen, it says download mode, but my computer thinks there's nothing connected. With 2 different cables, and 2 different flash tools saying this, even with correct drivers installed.
Click to expand...
Click to collapse
Hi, glad you at least found out the right button combo for Download mode. Can you be specific about the drivers you installed? Were they "LG_VZW_United_WHQL_v2.22.0.exe"?
Try rebooting after installing the drivers, with the tablet unplugged from the PC. After the reboot is finished, put the tablet in download mode and plug it into the PC. It can take up to 10 minutes to load the drivers once you plug it in. Use a USB 2.0 port preferably. Of the two cables you tried did you use the original cable? That's preferred, also.
You can look in Device Manager in Windows and see if the driver is still loading for the Android device listed under the "Modem" section. If after 10 minutes it still hasn't loaded the driver, try a different USB port. Lastly, if you need to, try a different PC. I know it's possible you don't have easy access to a different one, but sometimes that's the solution.
here's what I did so far: (pc is using win10pro and original samsung USB cable, swapped with 2 other cables)
put tablet in odin mode, plugged a cable in to tablet and pc, ran odin. odin refuses to recognize the tablet. no error messages, but no com port number comes up. I've downloaded new drivers and installed them several times. when tablet gets plugged in, win10pro comes up with "USB device not recognized." perhaps part of the problem?
looking for the braintrust's advice. tried searching, but my google/bing-fu has fummed...
jaypea500 said:
here's what I did so far: (pc is using win10pro and original samsung USB cable, swapped with 2 other cables)
put tablet in odin mode, plugged a cable in to tablet and pc, ran odin. odin refuses to recognize the tablet. no error messages, but no com port number comes up. I've downloaded new drivers and installed them several times. when tablet gets plugged in, win10pro comes up with "USB device not recognized." perhaps part of the problem?
looking for the braintrust's advice. tried searching, but my google/bing-fu has fummed...
Click to expand...
Click to collapse
And you have usb debug enabled?
buhohitr said:
And you have usb debug enabled?
Click to expand...
Click to collapse
perhaps that's the trick. I'll try it. the instructions I was looking at didn't mention that.
ugh. I was able to connect to the tablet, but it just won't root (as far as I can tell). I'm on 5.1.1 on the sm-p600 wifi (lt03wifi). debugging is on. odin connects, I use the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file, and eventually it resets and I get "pass" from odin. the tablet reboots, I get the red "seandroid" warning, the knox count is 1 (I'll take that as a badge of honor), but root checker says it's not rooted, and there's no superuser installed. I'm going to give it one more shot and see what happens.
all this because the OTA of 5.1.1 made the thing so sluggish that I wanted to grab something else to use. I've successfully rooted and re-loaded a couple of other tablets, so I though this would be easy. ugh.
meantime, any other ideas on gaining root? thanks for the help.
jaypea500 said:
ugh. I was able to connect to the tablet, but it just won't root (as far as I can tell). I'm on 5.1.1 on the sm-p600 wifi (lt03wifi). debugging is on. odin connects, I use the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file, and eventually it resets and I get "pass" from odin. the tablet reboots, I get the red "seandroid" warning, the knox count is 1 (I'll take that as a badge of honor), but root checker says it's not rooted, and there's no superuser installed. I'm going to give it one more shot and see what happens.
all this because the OTA of 5.1.1 made the thing so sluggish that I wanted to grab something else to use. I've successfully rooted and re-loaded a couple of other tablets, so I though this would be easy. ugh.
meantime, any other ideas on gaining root? thanks for the help.
Click to expand...
Click to collapse
Nope, you did it wrong. Your method is wayyyyy outdated.
Yes, check out my instructions here. Very easy.
http://forum.xda-developers.com/gal...l/how-to-root-lp-5-1-1-supersu-2-6-1-t3266010
buhohitr said:
Nope, you did it wrong. Your method is wayyyyy outdated.
Yes, check out my instructions here. Very easy.
http://forum.xda-developers.com/gal...l/how-to-root-lp-5-1-1-supersu-2-6-1-t3266010
Click to expand...
Click to collapse
cool beans. I'll try it tonight. thanks for the info. unlike my other tablets, there seems to be so much confusing information out there for this tablet. I'm grateful this forum exists...
I don't know what's happening, but something is still wrong. I'm still not rooted, even with following your instructions.
all the "prep" is cool. in "execution" I flashed the full 5.1.1. all is good.
then I flash TWRP. from there it goes sideways. when I hold the vol-up+home+power buttons, it goes to the opening logo (I do see the "SEAndroid" warning on the screen), but it then goes blank, and the logo/warning returns. this happens as long as I hold the buttons. when I let go, the battery gauge comes up. try the key combo again, the same sequence occurs. it seems I never get into TWRP. I did once get to all-red-blue-yellow text "Android Device Recovery" where you use the volume and power keys to select options, but that didn't look like TWRP to me and wouldn't flash anything not "officially signed."
what's supposed to happen when I flash TWRP? what does odin show? do I have to wait for "PASS?" how do I get to the key combo before the tablet reboots? should odin not be set for "auto-reboot" when flashing TWRP? do I flash the compressed TWRP tar file, or do I extract the contents of the tar before flashing?
by the way, I'm trying to use the original non-touch TWRP in your instructions, not the TWRP-touch version.
can you please expand on the execution of this procedure a bit more? my swiss-cheese, colander-like brain isn't grasping something somewhere. thanks...
nevermind. I got it. the fifth try I guess I was fast enough to get to the key combo before it booted.
again, thanks for the help...
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.
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
LumberjackZac said:
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
Click to expand...
Click to collapse
Can you still boot into TWRP?
dhplap said:
Can you still boot into TWRP?
Click to expand...
Click to collapse
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
LumberjackZac said:
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
Click to expand...
Click to collapse
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
That is awesome. Been looking at Note 4's on ebay because.... not looking good
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
Hey buddy. I've been reading that qhsusb_bulk is a hard brick, possible fried bootloader. But I guess if you can make this unbrick.img on to a sdcard it may work. I'm scratching my head on what files go into this unbrick.img and if I can make it myself. Any ideas