Need boot loader help - installed wrong bootloader image on 5x - Nexus 5X Q&A, Help & Troubleshooting

Hi all,
Like a complete n00b when updating my boot loader I accidentally flashed the Hammerhead image instead of the Bullhead image. After rebooting my device just powered off. Didn't come back at all. I did not realize until it was too late that I have the wrong image.
Tried all the key combinations and nothing. The version I flashed was hhz12d. It's a brand new Nexus 5x and I'm willing to do anything to get this working again. Any guidance or help would be greatly appreciated.

Look here:
https://r.tapatalk.com/shareLink?ur...share_tid=3251740&share_fid=3793&share_type=t
[REQ] Need help. Unbrick phones with locked bootloader, oem unlock disabled
Sent from my SM-G930V using Tapatalk

Thank you. I will give this a try, but will it work if the device won't even power on? I mean, literally will not react to any button presses.

cstokes86 said:
Thank you. I will give this a try, but will it work if the device won't even power on? I mean, literally will not react to any button presses.
Click to expand...
Click to collapse
Update: This did not work as the device wont power on thus the LGUP app will not detect the device. No combination of key presses does anything.
I do now see in the device manager a device called QHSUSB_BULK showing up. Maybe there's still hope?

Related

[Q] htc wildfire s boot loop problem

So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.
Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you

[Q] My Brand New Nexus 7 Bricked Itself, Can I Do Anything?

Here's the backstory, I bought a Nexus 7, powered it up, and everything was working great. It forced an update on me right when I turned it on which surprised me but I let it go. After this I power it off thinking about installing TWRP on it because I remembered unlocking wipes my data. Anyways, after I power it off it never turns back on. Thinking I got a faulty device, I go exchange it for a new one, but the exact same thing happened again. Am I missing something? Any suggestions. I can't get into fastboot (holding all three buttons or just 1). In fact pressing any combination of buttons doesn't show anything happening at all.
Thanks for your help
Sphaerophoria
EDIT: I fixed it by unplugging and plugging in the charger then holding power for 15 seconds. I followed the instructions here and managed to get it to boot, however I have to do this every time. This is with bootloader FLO-03.05 can anyone else confirm this behavior?
Power + Volume Down is what's used to get into the bootloader. Have you tried rebooting straight into bootloader from the ROM with ADB?
Username invalid said:
Power + Volume Down is what's used to get into the bootloader. Have you tried rebooting straight into bootloader from the ROM with ADB?
Click to expand...
Click to collapse
I can't get into the ROM. It won't boot at all. Even when I plug it in the battery symbol doesn't show up. My guess ATM is that google pushed an update that broke the bootloader but I'm hoping someone can prove me wrong.
Sphaerophoria said:
I can't get into the ROM. It won't boot at all. Even when I plug it in the battery symbol doesn't show up. My guess ATM is that google pushed an update that broke the bootloader but I'm hoping someone can prove me wrong.
Click to expand...
Click to collapse
I mean don't turn the tablet off after the update and instead let it boot into the ROM.
Username invalid said:
I mean don't turn the tablet off after the update and instead let it boot into the ROM.
Click to expand...
Click to collapse
Well it's a little late for that
Sphaerophoria said:
Well it's a little late for that
Click to expand...
Click to collapse
You exchanged it once, you can do it again.
I followed the instructions here and managed to get it to boot, however I have to do this every time. This is with bootloader FLO-03.05 can anyone else confirm this behavior?
Sphaerophoria said:
This is with bootloader FLO-03.05 can anyone else confirm this behavior?
Click to expand...
Click to collapse
Curious, what is the production date on the box?
My unit has bootloader FLO-03.14 and production is listed as 2013.06
Model: K008(NEXUS7 ASUS)
Customer P/N
NEXUS7-ASUS-2B16
P/N: 90NK0081-M00020
AS NEXUS7 ASUS 1A/Q8064/16G/2G
...
NEXUS7 ASUS,BLACK,GL,GPS,2G DDR3L,NFC
APQ8064,CB-802.11abgn+BT4.0,16GB EMMC
1.2M/5M-CAMERA,1CELL3950
Made in China Date: 2013.06

[Q] Hardbricked? do not reboot HELP!!!

hi everybody,
I'm usually more active on auto forums but I need your help.
wanting to install a custom rom, I'm a but lost in the manipulations. Last night when I wanted to turn on the tab (only with the power button), I had the google logo that was displayed at the top right and the small rectangle of recovery menu (start, recovery, reboot bootloader and poweroff). With buttons I could choose one of four functions. I had access to the recovery menu, when I choosen restart bootloader, it well reboot and poweroff worked well too. By when I clicked start I had a small line at the top left telling me "boot failed"
I try to flash everything thanks to a tutorial.
So I'm DL the original elements but still the same issue. Having struggled until 3am I give up. This morning when I tried to turn on the tab, I did even more than what I have explained below whatsoever with the power button or volume down + power nothing happens the screen stays black.
Any Ideas?
PS sorry for the language I'm french
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
stanglifemike said:
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
I'm seriously thinking of this solution but I'm afraid before they give me a new one they send it to their after sales service. If they find out I have rooted it and unlock the bootloader they will make nothing for me
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
sfreemanoh said:
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
Click to expand...
Click to collapse
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
swagstr said:
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you .
No it doesn't works. For the time being my first to issue is to succeed to boot it at least as yesterday evening.
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
geckocavemen said:
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
+1 Try plugging it in for awhile too. You want to get to the bootloader - the screen with the Android where you go through the options with the volume buttons. Once there,you can use fastboot to flash TWRP and fix from there. Again, stay away from the OLD Nexus files.
Sent from my Nexus 7 using Tapatalk 4
geckocavemen said:
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
I tried to keep on the power button during 1 min with and without charger and pluged to PC : nothing happens. I tried the same thing with volume down + power and nothing happens either
I'm not sure what might help next. Perhaps someone with more experience will come along with advice. If it were me I would probably return it and tell them the power button stopped working.
stef77972 said:
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Click to expand...
Click to collapse
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
I'm seriously thinking of this solution. I'm just worry if asus find out everything I made
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Hmm.. This is possible. If your device will not turn on, I'm thinking you are SOL my friend. Or in your native tongue: merde pas de chance. Hopefully that conveys it
Sent from my Nexus 7 using Tapatalk 4
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Yes I used this one but I think I have the old version
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
Oh boy... *Grabs popcorn*
Sent from my Nexus 7 using Tapatalk 4
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
the old nexus 7 or the new 2013 model with a camera on the back? is yours wifi only or 3g capable?
The only thing i can think of is to plug into your pc's usb port and hold the power button for 30sec.
Then unplug from PC and press power button for about 15sec and you should see the google logo - if not, i think your bootloader is bricked from flashing the wrong one.
If you do see the google logo, keep holding power and also press vol down as soon as you see the logo - should get you into the bootloader.
Messing up the bootloader is the only way you can brick a nexus, feel sorry for ya man
noob question: so you are using a Nexus 7 (2013) and you flashed an old-nexus-7 ROM on your device? If you're using the new one, here is the ROM for the new one http://forum.xda-developers.com/showthread.php?p=44054613.
I have just had the same problem. Flash the old nexus 7 kernel on the new one, luckily I fixed it
There is a different forum for the 2012 Nexus 7 here. This forum is for the 2013 version.

[Q] Galaxy Nexus shows "No Command" after Recovery

I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR
<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
GR5000 said:
I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR
Click to expand...
Click to collapse
GR5000 said:
<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
Click to expand...
Click to collapse
when you see this "no command", press power + volume up to see the recovery menu
Thank you so much for the info. I'm trying this when I see the no command screen but nothing happens. The phone is just completely locked / frozen. I have to remove the battery. Any additional help would be much appreciated!
Thanks,
GR
samersh72 said:
when you see this "no command", press power + volume up to see the recovery menu
Click to expand...
Click to collapse
Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11
The phone is completely stock. I've never done anything to it so not sure why I'm having this issue to begin with. But what custom recovery would you recommend I try? Is there a link that you can send me? And how would I install it given that I cannot even get the phone to boot?
Thank you
AndyYan said:
Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
GR5000 said:
And how would I install it given that I cannot even get the phone to boot?
Click to expand...
Click to collapse
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11
When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
AndyYan said:
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
GR5000 said:
When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
Click to expand...
Click to collapse
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11
Just want to thank everyone for all of the help. I really appreciate it. Andy, I did try several of the steps that you mentioned but for some reason the PC just wouldn't recognize the phone in fastboot mode. I tried both the Google and Samsung drivers.
In my searching I found this post though:
http://forum.xda-developers.com/nexus-4/help/nexus-4-stock-recovery-command-issue-t2113478/page2
And realized that I should check samer's advice again. Turns out that I just wasn't pressing those two buttons in the correct sequence. I was doing it simultaneously and I guess you have to do it serially. At any rate was able to restore factory and now the phone is booting. Wow. What a pain. Still not sure what caused the phone to blow up in the first place.
At any rate really appreciate everyone's help.
Warm regards,
GR
AndyYan said:
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse

Cannot enter recovery mode! Please help!

Hey all. I'm thinking I may have bricked my mother's Zenfone So I was trying to help her out by installing a custom rom on the phone as she complained about the bloatware that comes with the phone slowing things down. I couldn't get the bootloader unlocked (tried every procedure under the sun), so I tried entering recovery mode and flashing the boot.img and droidboot.img directly (saw a thread where someone did this, then tried unlocking and it worked).
The phone boots into up fine but now everytime I try entering recovery mode, I get the dreaded USB logo screen. It remains there for about a minute, reboots and comes back again. Does that about 3-4 times before turning off. Is there a way to just completely get the phone back to 100% factory settings? I'd rather just starting over from there. The problem I'm having is pretty much exactly the same as what the person in the video below is experiencing....
Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk
jimchee said:
Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply. If u mean Fastboot mode, where I can see the Product name, Booloader version, etc, then no. That's where I see the USB icon.
You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...
ultramag69 said:
You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...
Click to expand...
Click to collapse
Hmmm. Well I came across this thread...
http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848
They seem to have procedures to help with my issue. But I came across another problem. Hopefully someone there could help with it. I post here if I succeed.
hi, I removed os from my Asus and now it is not entering fast boot mode any one can kindly help me pls.

Categories

Resources