Database Develop

[A] Solved the Seven Vibration Brick

\\\Disclaimer: I am not responsible if you mess this up & break your phone///
Checking Your Situation:
*Phone only boots to Fastboot
*Phone does/Doesn't charge
*Power button Seems useless
*Phone Turns on and only shows-
the X screen & Vibrates 7x's
*LED Only shows Green/ Orange
indication light
Things You'll Need:
*Wall Charger
*USB Cable
*Computer (duh)
*Battery (of course)
*FRG83 ROM file http://tinyurl.com/6bym3vg
*Android ADB Setup
*Fingers Crossed
(Tip: if you are using the same Sdcard when the phone messed up, reformat it or use a new one)
Step One:
Download FRG83 ROM file http://tinyurl.com/6bym3vg
and unzip the package into your AndroidSDK Tools Folder
Step Two:
Watch the battery trick video
http://youtu.be/2O5adV-jj64 (Thanks n1newbie)
Once you've analyzed the video enough
plug your phone (while it's off) to the wall
charger and while doing the wall trick !!Make
sure you hold down the Volume-Down Button!! so
you can boot into fastboot.
Step Three:
Once established fastboot, plug the phone
to your computer and let your computer discover the
device.
!!Make sure the device says Fastboot USB!!
Open Command Promt (CMD). If you already
know how to use Android ADB type these commands:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fastboot devices
!!Make Sure You Device ID Shows UP!!
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let the phone run everything through and you should
be one Froyo.
Step Four:
Power down your phone
Reboot into Recovery (to see if your phone is still rooted)
If you are able to get into recovery flash any ROM
you like and Enjoy your UnBricked Nexus One

lilj4321 said:
If anyone needs the fix for this soft brick
let me know so i can post instructions!
Click to expand...
Click to collapse
You might as well write them out. You never know when someone will need them.

taodan said:
You might as well write them out. You never know when someone will need them.
Click to expand...
Click to collapse
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk

n1newbie said:
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
+2, hope it won't occurs

hi lilj4321. thanx for the steps frnd
the youtube link that you provided returns 404 error. so you might use this link for video trick (by myself )
PS- sry if i am wrng. will the device boot into fastboot mode after the seven vibration brick happens
Sent from my Nexus One using Tapatalk

fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.

lilj4321 said:
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
Click to expand...
Click to collapse
oh okies. thanx for using my video buddy
will try this if seven vibration brick happens. but ill pray it shdnt happen
will be helpful for all if it is stickied :thumbup:
just my 2 cents ...
Sent from my Nexus One using Tapatalk

I hoped for something much more useful.
The method of reflashing to stock using fastboot commands has been posted on Nexus One Wiki for 2.5 years now.
And of course, it won't solve any overheating phone, and no "7-vibration brick".
Thanks for trying to help, but the post is kinda (very) useless.

Stuck in fastboot
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.

ajaymkd said:
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
Click to expand...
Click to collapse
After doing all the stuffs, and after fastboot reboot.. The phone on the same state.. Brick state with 7 vibrate + X sign. Why is that so?

[Q] Force shutdown NOT RESTART

I just unlocked the bootloader of the x890 using fastboot. I am not sure if I made a mistake since now the Warning Bootloader Unlocked screen is the only powerup option.
It no longer boots into the fastboot menu. I have tried the pwr+vol_down key combo but it just keeps restarting. Windows 7 recognizes the device but is not listed as a fastboot device to interact with.
On my old phone I could pull the battery, short of waiting for the battery to die and hoping it charges again. Is there an option to force the phone to SHUTDOWN? I think there was an issue with the power down, power up normally, restart, etc. that I tried. I don't think I actually hit power off like I was supposed to.

hopefullyfixed said:
I just unlocked the bootloader of the x890 using fastboot. I am not sure if I made a mistake since now the Warning Bootloader Unlocked screen is the only powerup option.
It no longer boots into the fastboot menu. I have tried the pwr+vol_down key combo but it just keeps restarting. Windows 7 recognizes the device but is not listed as a fastboot device to interact with.
On my old phone I could pull the battery, short of waiting for the battery to die and hoping it charges again. Is there an option to force the phone to SHUTDOWN? I think there was an issue with the power down, power up normally, restart, etc. that I tried. I don't think I actually hit power off like I was supposed to.
Click to expand...
Click to collapse
Do you find the device with 'adb devices'? Cause if so, then you can do: 'adb reboot-bootloader'

No. I can not find the device with adb devices. It lists nothing - same as the fastboot.
dagoban said:
Do you find the device with 'adb devices'? Cause if so, then you can do: 'adb reboot-bootloader'
Click to expand...
Click to collapse

hopefullyfixed said:
No. I can not find the device with adb devices. It lists nothing - same as the fastboot.
Click to expand...
Click to collapse
Your phone probably died by now, do this:
Press Volume down and then attach it to your PC (and do not hit the power button) it should automatically go into the bootloader now.
---------- Post added at 22:42 ---------- Previous post was at 22:41 ----------
If you can't charge your phone anymore, get a factory cable / adapter, then it will boot up using the power from the usb plug

dagoban said:
Your phone probably died by now, do this:
Press Volume down and then attach it to your PC (and do not hit the power button) it should automatically go into the bootloader now.
---------- Post added at 22:42 ---------- Previous post was at 22:41 ----------
If you can't charge your phone anymore, get a factory cable / adapter, then it will boot up using the power from the usb plug
Click to expand...
Click to collapse
So it finally works.
I installed CWM via fastboot, rebooted into CWM and flashed Cynagen mod 11. This gave a Status 7 error which relates to the age of the recovery version.
I switched to the most recent version of TWRP and flashed it with fastboot.
I then installed CM11 and google apps. Phone works great. Thanks.

Lock-Bricked nexus 6

Hello,
I have trouble with my nexus 6. I tried to flash the latest factory image for 5.1. But my system.img did not flash... after hours, I did not found any solution, so tried to lock and relock the bootloader again. Locking worked as espected... but unlocking returns the following message:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Now I sit here, no booting device because of missing android version and I can not unlock the bootloader anymore... Somebody can help?
Thanks
Andy

Sorry - it's not good news:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497

**** that's really bad!!! But thanks for your reply!!!

ANDYx1975 said:
**** that's really bad!!! But thanks for your reply!!!
Click to expand...
Click to collapse
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk

narezese said:
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!

ANDYx1975 said:
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
Click to expand...
Click to collapse
Im talking about mine.. Before flashing 5.1 the option was checked..
Sent from my Nexus 6 using Tapatalk

You sir have a brick. Your only option as of right now is to try to get Motorola to replace the device for you.
Sent from my Nexus 6 using XDA Free mobile app

ok... tkanks I have to try this... even if I think my chances are almost zero!!! Thanks anyway!!!

Have you tried to adb sideload the ota .zip?

yeah I only have access to fastboot... and he does not find the device

From fastboot can you get to stock recovery? After selecting recovery in fastboot, you'll get the Android dude ... But you have to hit the power and volume up/down as well (forget the exact combo) to get into recovery. From there you select install install via adb (forget the exact verbiage, but it's the second option from the top). From there you run adb, not fastboot
---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------
http://www.droid-life.com/2015/03/1...1-ota-updates-for-nexus-devices-4-5-6-7-9-10/
^ d/l link with a link to (better) flashing directions

to be honest I do not know it's already out home to the repair service... ****... I should be more patient!!!

Gotcha ... Don't feel bad, you're not alone. I, and many others, did the same/similar and ended up in the same situation.
I been rooting/tinkering for 6+ years across 10 or so devices and it turns out a friggin NEXUS is the first device that I brick! ?
(I'm fully aware of the risks we take with unlocking amd rooting, but IMO Google screwed the pooch with this OEM Unlock "feature" in developer options! Why make unlocking dependent on a setting WITHIN the OS??!)

So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found

ANDYx1975 said:
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
Click to expand...
Click to collapse
You need to boot into stock recovery. From the screen you are in press volume up and power.

What ^ he said ... Then once in stock recovery select the second option (install update from adb (or something like that))

ok... I can not go into recovery... the google logo appears and nothing happens... ****!!! But hey thanks anyways!!!

That sucks! Sorry man!

@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6

Casper34 said:
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, thats what I said.

Nexus 6 stuck in google screen

Hello, I have read about this problem but I still have some questions.
The phone was stock, not rooted or anything, a friend of mine tried to uptate the phone via OTA with only 8 percent of battery so now the phone is stuck in google screen.
I read about this here http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 about fastboot commands but the problem is that I have not never checked the USB debugging mode.
It shows "Device is locked" and "Status code:2"
Thanks, I hope it works again.

You don't need debugging enabled to use fastboot. That's only for issuing commands while in the OS.

Nothing you can do if "Enable OEM Unlock" is not selected. Needs to be sent to Google / Motorola.

danarama said:
Nothing you can do if "Enable OEM Unlock" is not selected. Needs to be sent to Google / Motorola.
Click to expand...
Click to collapse
Thanks, but wait, I'm just wondering, I have read that every nexus has its OEM thing unlocked from the beginning, so how you asumme it is off?

espinal123 said:
Thanks, but wait, I'm just wondering, I have read that every nexus has its OEM thing unlocked from the beginning, so how you asumme it is off?
Click to expand...
Click to collapse
Almost correct. On 5.0, it seemed to work if you unlock before booting device first time without checking the setting. But won't work since 5.1
Sorry, I assumed you'd actually tried to unlock the bootloader. If you haven't, you probably should try. That will tell you once and for all whether you need to return it or not.

danarama said:
Almost correct. On 5.0, it seemed to work if you unlock before booting device first time without checking the setting. But won't work since 5.1
Sorry, I assumed you'd actually tried to unlock the bootloader. If you haven't, you probably should try. That will tell you once and for all whether you need to return it or not.
Click to expand...
Click to collapse
Thanks, So i tried to unlock it through the NRT nexus root toolkit and it says this:
fastboot devices
ZX1G22KCPZ fastboot
Connectivity Status: Fastboot Device Connected
fastboot oem unlock
Click to expand...
Click to collapse
Then it asks me to reboot and enable debugging thing, so I cannot, do you thing is unlock? Now I'm gonna try to "flash stock + unroot" on this program, I'll let you know.
Thanks.

graydiggy said:
You don't need debugging enabled to use fastboot. That's only for issuing commands while in the OS.
Click to expand...
Click to collapse
Thanks, but this guide says that you have to turn the debuggin mode on. I tried to flash, (assuming OEM is on) through the Nexus tool kit but it gave me a lot of fails.

@Evolution_Tech
Aren't you more versed in this area? Maybe you can lend a hand?

graydiggy said:
@Evolution_Tech
Aren't you more versed in this area? Maybe you can lend a hand?
Click to expand...
Click to collapse
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.

Evolution_Tech said:
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.
Click to expand...
Click to collapse
He is trying to use toolkit. It requires USB debug enabled as it uses both adb and fastboot. Needs to forget the toolkit and go to manual fastboot.

prdog1 said:
He is trying to use toolkit. It requires USB debug enabled as it uses both adb and fastboot. Needs to forget the toolkit and go to manual fastboot.
Click to expand...
Click to collapse
+1

That's what I was thinking. However I'm not as familiar with manual fastboot. I also don't have a computer at hand at the moment so I can't quickly get all the commands for the OP.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
Since it seems that there is no OEM unlock on the device, would he be able to push a factory image to the phone and install it like a regular update through recovery?

Evolution_Tech said:
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.
Click to expand...
Click to collapse
OEM seems that is Unlock, the toolkit says this.
fastboot devices
ZX1G22KCPZ fastboot
Connectivity Status: Fastboot Device Connected
fastboot oem unlock
Click to expand...
Click to collapse
Now, that toolkit doesn´t work, so I'm trying to use fasboot thing. But it seems that I need debbuggin thing On, I'm using this guide http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 I don't know how to do this things I just do what the guide says.
So the big question is how can I flash wihout usb debugging thing enabled.
Thanks :good:

espinal123 said:
[/COLOR]Since it seems that there is no OEM unlock on the device, would he be able to push a factory image to the phone and install it like a regular update through recovery?
Click to expand...
Click to collapse
OEM seems that is Unlock, the toolkit says this.
Now, that toolkit doesn´t work, so I'm trying to use fasboot thing. But it seems that I need debbuggin thing On, I'm using this guide http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 I don't know how to do this things I just do what the guide says.
So the big question is how can I flash wihout usb enabled.
Thanks :good:[/QUOTE]
Flashing via fastboot does not need USB debugging enabled. If your bootloader IS unlocked, you are good to go.

If I'm not mistaken debugging is for inside the OS only... It's been like that for my Samsung devices. It's so your computer can push a command to the phone while it's completely booted. Don't worry about the toolkit from this point. I'm sorry I can't be of more assistance. Just give us a little more time and we shall get you sorted. Hopefully

Have you ever just tried entering recovery and doing a factory reset?
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
Otherwise, from fastboot, just try: fastboot format cache

Evolution_Tech said:
Have you ever just tried entering recovery and doing a factory reset?
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
Otherwise, from fastboot, just try: fastboot format cache
Click to expand...
Click to collapse
I cannot enter to recovery, It appears a dead android and a warning sign on his chest. But I already did through fastboot command as you say, but I don't know how to flash in fastboot i cannot find the proper guide.
I already did the command "fastboot devices" and it recognizes my device. I tried to put a new recovery but it wont let me.

espinal123 said:
I cannot enter to recovery, It appears a dead android and a warning sign on his chest. But I already did through fastboot command as you say, but I don't know how to flash in fastboot i cannot find the proper guide.
I already did the command "fastboot devices" and it recognizes my device. I tried to put a new recovery but it wont let me.
Click to expand...
Click to collapse
OK, first, when the "dead android" appears, hold power and press volume up once. That is the normal procedure for entering stock recovery.
Second, why can you not flash a custom recovery? I have a strong suspicion that your bootloader is locked and there is some communication issues here. Go to stock recovery and do a factory data reset.

Evolution_Tech said:
OK, first, when the "dead android" appears, hold power and press volume up once. That is the normal procedure for entering stock recovery.
Second, why can you not flash a custom recovery? I have a strong suspicion that your bootloader is locked and there is some communication issues here. Go to stock recovery and do a factory data reset.
Click to expand...
Click to collapse
Thanks, I cannot enter recovery mode as you said, I also cannot "fastboot oem unlock". Here's one picture.
At least it recognizes my device.(as youll see in the picture)
Does it mean my oem thing is blocked? And I cannot do anything?
If so, what about this http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518

espinal123 said:
Thanks, I cannot enter recovery mode as you said, I also cannot "fastboot oem unlock". Here's one picture.
It recognizes my device, does it mean my oem thing is blocked? And I cannot do anything?
If so, what about this http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
No, that fix does not apply here.
I'm going to try this once more.
Disconnect from your PC.
Power off your nexus.
Hold power+volume down to enter bootloader.
Once in bootloader, use volume down to select recovery mode. Press power to select it.
Once dead android appears, hold power button and press volume up once.
Once in recovery, use volume down to highlight " wipe data/factory reset "
Press power to select.
Reboot when prompted.
If the device boots up, wait patiently for the reset to completely finish. It may take as long as 20 minutes or more.
If this processes doesn't work, you have one option, RMA.

ADB Works, Fastboot still "waiting for any device"

I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps

superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.

RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?

reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.

RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode

reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time

Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan

TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?

RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.

RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm

TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer

Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol

reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.