Hey guys,
So I properly powered down my phone and went to go into the bootloader by holding vol down + power button. As soon as it opened up the bootloader the phone turned off. I went to turn it on and it flashes the white sprint screen for less than 1 sec and turns off. When I plug it into a charger the light turns on for a few secs then goes away.
I have s-off + cwm.
I have read that if your battery dies in the bootloader after installing cwm your battery won't charge and the phone won't boot. I am not sure if this is the case but was hoping to get some input.
I am not sure what percentage my battery was at when this happened.
Thanks!
Go to bootloader (cwm) and reinstall your back up rom that outta do it. And after download the rom you currently have but replace your old one and flash it over usin cwm
Supa Dupa Troopah
My phone only stays on for 1 second tops. I cannot go to my bootloader. My computer sees the phone even when it won't turn on witch is weird. I also cannot communicate with the phone with adb / fastboot etc. The only thing I have not tried is hacking a usb cable to communicate. Any advice would be great. I will try a battery tomorrow.
ADB
Wow hey ok so I can see the phone in ADB after all... List of devices attached
HT167HX05101 recovery
Is there a way to flash the old recovery?
Or can someone point me to the RUU.exe? Not the ZIP
Thanks!
EDIT:
Well never mind... I had adb and booted into bootloader and flashed team win recovery from fastboot and it failed - sending 'recovery' (5016 KB)... OKAY
writing 'recovery'... FAILED (status read failed (Cannot send after transport endpoint shutdown))
Now the light stays on when I plug in but no longer flashes when I power button and no more adb. I'm screwed
Idk what your problem is since i do not have your phone in front of me, either you deleted an import file and are now screwed no offense and cant boot your phone my suggestion is to either call or take it to the store by gettin a new one. I would tell them your phone got hot all the sudden and just crashed that way its under warentee
Supa Dupa Troopah
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
hopefully this works for me !!
Thanks
il Duce said:
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
Click to expand...
Click to collapse
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
SpyFi said:
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
Click to expand...
Click to collapse
yeah if you can't get into the bootloader/adb/recovery/rom then sprint can't either
Sorry to be a bother.. but can someone check out my problem? I really need help. I know, i am such a troll coming to another post to look for help.
-Mike
Check out this threath i hope it helps..
http://androidforums.com/evo-3d-all-things-root/385959-error-16-sprint.html
Supa Dupa Troopah
Related
I unlocked my phone with the htc method. I had root, and superuser. titanium backup worked fine. I made a nandroid backup before I started messing with ROMS. I decided to flash infected's ROM first. Everything seemed to be going ok. It rebooted, and I got the cool beats animation. Then I got the htc splashscreen. then it just flipped back and forth between them for a half hour or so. something was obviously wrong. I tried rebooting the phone: same results. I can get into bootloader, both by holding volume down while powering up, and through the command prompt, via adb. I have a nandroid backup through twrp recovery, so no problem, right? well, it didn't work. So now, I can boot into the bootloader screen, but nothing else. I tried flashing a different ROM, but to no avail. Eventually, I noticed that I had htc sync running while I did all this. Did that wreck me? Any ideas what I can do now? I just tried to restore my nadroid backup again, without htc sync running, but all I get is a white htc screen. Please help me unbrick my phone!!!
whenever I try to flash ANY other rom, I get to the part where I have to use fastboot to flash the boot.img, and it says "sending boot" and just stays there forever.
Tried flashinf recovery.img, and the same thing happens. "sending recovery" and screen pause
God I hope someone smarter than me feels generous enough to help here...
Are you on windows? Did you install htc drivers?
Sent from my PG86100 using XDA App
I am on windows 7, and I have the htc drivers installed. Like I said, I successfully completed the htc unlock method. I had no problems until I tried to flash a rom
So you hold volume down and power to enter fastboot. Select fastboot by hitting power again. Then plugin usb and it should say fastboot usb. Then what command do you type after that?
Sent from my PG86100 using XDA App
now it wont even go into hboot. not with vol down and power, or through command prompt. before, it was going into hboot just fine, and I was using fastboot flash boot boot.img to flash the rom, but everything froze
now when I plug it in and use the command prompt to enter adb reboot bootloader, it just says device not found. holding power and vol does nothing
Hmmm.. Not sure why you can't get into fastboot but your using the wrong command. You want to type fastboot boot recovery.img. Recovery being the name of the recovery image in your folder.
Sent from my PG86100 using XDA App
thanks. I'll try that if I can get back into the bootloader
What you did works for that only installs the kernel. Then you need to flash the rom. I never did it that way nor do I use twrp
Sent from my PG86100 using XDA App
I did flash the rom.zip from twrp recovery. when it rebooted, it started to work, then just went into a boot loop. then I started trying to fix it, now it wont even come on
For now, I'm hoping that the battery just discharged during the process. I'm gonna let it charge for a few hours, and see what happens. I'm afraid that I might have done a battery pull in the middle of the process, though. When I first flashed the InfectedROM, the phone rebooted and got stuck in a loop between the beats graphics, and the htc quietly brilliant screen. it just kept going from one to the other. It went on for quite a while, and eventually, I think I pulled the battery to stop it. However, I was still able to get into the bootloader after this. I tried to reflash the rom, and a couple of others to no avail. When I decided to try to reflash recovery.img, is when it hit the fan, so to speak. after that, I was unable to boot into fastboot, or even get adb to recognize that there was a device there at all. Man, I hope letting the battery charge works. Like a moron, I don't have any insurance on my phone.
when I plug it in, windows intermittently makes the gong noise that something is connecting or disconnecting, and windows explorer briefly recognizes that a removeable drive is present, but I can't get the thing to charge, or turn on at all, and adb refuses to recognize that it connected, so I still cant manually put it into fastboot
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
izzy spun said:
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
Click to expand...
Click to collapse
Pull the battery
Wait 2 minutes.
Put battery back in.
Hold down Vol - and power.
Do not be connected to anything. And are you SURE your battery is good?
PM me if you see this and I dont answer.
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
izzy spun said:
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
Click to expand...
Click to collapse
Ok, soundslike you have a "PG86IMG.ZIP" on the root of your SD card. Dont worry, just swap cards with your old lady but put the ROM on it first.
You wont be able to do anything until you swap Sd cards or otherwise delete the PG86IMG.zip.
when I use command prompt to enter bootloader, I get the opening menu: bootloader, reboot, reboot booloader, and power down. If I press power to choose booloader rather than fastboot, the phone immediately goes back to asking me if I want to update, and no matter what I choose, the results are the same. it reboots to the htc screen
So I just used Bootmanager for the first time. I was having alot of issues so I rebooted and now it sits at the splash screen and it isn't going into the bootloader. Kind of freaked out.
What do I do to fix this?
Thanks.
are you s-on or s-off?
I'm S-off on 1.49
edit: sorry, I meant 1.40
If u can get to recovery, go to install zip and find the boot manager folder, look in there for a phone Rom folder, their will be an update.zip, flash it and reboot.
I can't get to the recovery. It wont even boot to the spash screen unless it's plugged in.
Pull the battery, put it back in, hold vol down and power, what happens?
Well if it's unplugged it wont do anything. But, if it's plugged in, it goes to the splash screen.
Plugged into what, ac power or USB to comp? Try taking out the sd card and then try vol down and power.
Either the usb to computer or AC. It does it for both.
Took out the sd, no change.
I haven't seen a prob like this, without hboot you'd never see the splash screen, it has to be there. Maybe leave the battery out for a few minutes then try holding vol down+power. If you can get to hboot then you're good but with no hboot your not so good.
Hmm, so my red charging led is blinking now while the phone is off, wasn't doing that before, any idea on what that means?
I know that when I drain my battery all the way till it shuts off, it won't charge and I get the blinking red led. I have to put in a spare battery and let the other sit for a few hours befor it'll charge.
What's it do when u just press power? Just goes to the white HTC screen and stays?
Yeah it does that, I'm wondering if there is something wrong with my vol down.
Does it feel like it "clicks"? Take the case off and try to press vol down+power.
edit..Lol, just tried it without the case and its not as easy as I thought.
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
I wouldn't think so... I've had to pull it in situations like that, generally you just don't want to pull the battery during an ruu update or a pg86img update, when its writing to certain partitions. What recovery are you using and what Rom did you try to flash with boot manager?
I'm using TWRP 2.0 and my phones rom was on mean rom. I put ics playground on slot 1 and was having alot of issues getting the phone to wake up and random freezes and crashes. I attempted to boot back to my phones rom but it wasn't doing it. So I attempted to flash Chads AnthaX ICS playground kernel and bootmanager crashed. so I decided I would just boot into recovery and do flash the update zip for bootmanager.
That is everything I did
brenstar said:
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
Click to expand...
Click to collapse
It just sounds like something weird happened to your recovery partition. If you pull out the battery and put it back in, then plug a usb cable into your computer. Do not turn it on. Run the command "adb reboot bootloader" (from your computer). that should turn on the phone and put it into the bootloader. From there, redownload your custom recovery of choice to your computer. Make sure you have a .img file. Type in "fastboot flash recovery [NAMEOFRECOVERYIMAGE].img". Now run your custom recovery and restore the update.zip for your ROM.
~co~
I'd be very surprised if your phone is broken. Sounds like an easy fix and I wish I could help more. You really can't do anything without getting to the hboot screen. No ruu, no turning s-on to re downgrade, no loading a recovery from fastboot.... I'm trying to think, maybe somebody else will jump in here and teach both of us somethin.
I know that a couple of other ppl had prob with a certain release of playground and twistedumbrella fixed them right up. Maybe you could hit him up. He's way more pro than I am.
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
TugboatTony said:
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
Click to expand...
Click to collapse
Are you saying volume up + power button does not restart your phone nor does any help? Check if your phone is detected in computer and if so you can issue and adb reboot command
also since there is no removable battery HTC added a reboot function press home vol down and power that should do the trick
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Vol up + Power was the key. I was thinking it was volume down. Thanks for all your help
TugboatTony said:
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Click to expand...
Click to collapse
Its volume up mate + power not volume down
pradeepvizz said:
Its volume up mate + power not volume down
Click to expand...
Click to collapse
Hi Do you have a HTC one max stock Rom I could use??
Thanks
mini88448 said:
Hi Do you have a HTC one max stock Rom I could use??
Thanks
Click to expand...
Click to collapse
There have been lots of request for this, ill upload a stock rooted ROM soon.
pradeepvizz said:
There have been lots of request for this, ill upload a stock rooted ROM soon.
Click to expand...
Click to collapse
OMG THANK YOU SO MUCH!!!
:victory::victory::victory:
Just wanted to point out I ran into this issue also (Stuck on white HTC boot screen) after wiping my ROM and Vol UP + Power did the trick for me also (and then Vol Down + Power to get back to the bootloader).
i need help, guys
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Sounds like you're flashing the wrong TWRP.
Sent from my Galaxy Nexus using Tapatalk
suieitori said:
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Click to expand...
Click to collapse
May I suggest following these instructions?
http://forum.xda-developers.com/showpost.php?p=51753483&postcount=129
If you're able to complete those instructions outlined in that post, this should set you up with the latest HBOOT, Radio and TWRP (Recovery) for the Verizon HTC One.
Make sure you read the post fully before you start, especially this part:
fastboot flash zip firmware.zip (Be sure it finishes saying 'successful', not 'please flush again immediately'. If it says the flush again, rerun the command)
If you succeed in getting that done, see if TWRP still causes the phone to reboot and get back to us.
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Why you did that? You can't update rooted phone
Idiocrate said:
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Click to expand...
Click to collapse
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
piskr said:
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
Click to expand...
Click to collapse
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
james194zt said:
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
Click to expand...
Click to collapse
ok I'm looking for a solution for hours now... so I just lokked how works our phone and I think the trouble must be in the preloader, because I can't even make my phone being recognized by any computer and I can't access to recovery.
I found this :
http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/
Which could help. I'll leave that topic on for some days (if it could help someone) and I'll open a new one to know if there is any easier solution ! thanks and good luck.
I sorted mine, it was only 2 days old so I got it replaced by the shop I bought it on. I would say it was something like a pre loader from what I saw. I have never bricked an Android phone and I must have had 15-20 of them since my first HTC Magic and before that Windows Mobile which again I messed with tons reloading with all sorts of ROM's!! These phones are wayyyy too sensitive to being messed with, I always remember though that you never mess with the boot loaders, but it looks like these updates do to get it bricked to that point.
Idiocrate said:
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
Click to expand...
Click to collapse
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
piskr said:
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
Click to expand...
Click to collapse
Euuum..... maybe yes ? I used fastboot but I don't think it really matters now, there's nothing working on it. And I've sometimes hold the buttons for 30-40 second while praying lol
korenisko said:
Why you did that? You can't update rooted phone
Click to expand...
Click to collapse
local update
I just hard bricked my Honor 7 the same way. Is there really no solution? Other China-Phones are pretty much unbrickable, since you can always fix it via the preloader. No such luck here? Back to the shop and hope they actually replace it? While I admit it was stupid to just hastily start the OTA while having twrp and not stock recovery (no root, though), this is a terrible design flaw on Huaweis side.
Anyway... any hope or no chance?
i just hard bricked my honor 7 PLK-L01
it the same thing it is doing . not recognized by the computer
tried all the combination of buttons. but no hope
and it only vibrates when tried to turn on
Need urgent help please
@Idiocrate try to boot into bootloader mode just by pressing Vol DOWN button and simultaneously connecting it to a PC, don't press Power button, if it boots into it, then follow the method given by @piskr in third post.