Database Develop

[Q] There's any form to enter to the bootloader, from my pc?

Pleas i need help. my vol-down button is broken. I need another way to enter into the boot loader.
Thanks

Gab00 said:
Pleas i need help. my vol-down button is broken. I need another way to enter into the boot loader.
Thanks
Click to expand...
Click to collapse
Use the cedesmith's cLK bootloader and cLK Android build. In this bootloader you do not hold the voldown button, you hold down any key (except power) to show the console.
cLK: http://forum.xda-developers.com/showthread.php?t=901305&highlight=bootloader

thanks, i'll try and inform u
spalm said:
Use the cedesmith's cLK bootloader and cLK Android build. In this bootloader you do not hold the voldown button, you hold down any key (except power) to show the console.
cLK: http://forum.xda-developers.com/showthread.php?t=901305&highlight=bootloader
Click to expand...
Click to collapse

clk is a good idea - but you need the volume key to flash it - directions::
make sure you have hspl
- enter SPL by holding VOL DOWN key while powering/resting the phone.
- flash with customruu like you would a windows rom and/or magldr
Click to expand...
Click to collapse
sorry, mate. haven't seen a solution for your problem.
edit - are you running android (i assume so) or WM? if the latter, lots of options.

jsmccabe78 said:
clk is a good idea - but you need the volume key to flash it - directions::
sorry, mate. haven't seen a solution for your problem.
edit - are you running android (i assume so) or WM? if the latter, lots of options.
Click to expand...
Click to collapse
Yeah, you're right. My mistake. It was about the SPL (phone bootloader) ...
But the phone bootloader can trigger via USB cable (for example, when installing the wm6 rom via USB, the windows installer restarts the phone to phone bootloader). I have not tried, but it seems possible

spalm said:
You're right, but the phone bootloader can trigger via USB cable (for example, when installing the wm6 rom via USB, the windows installer restarts the phone to phone bootloader). I have not tried, but it seems possible
Click to expand...
Click to collapse
you are right about rebooting into bootloader - but that is via WM, not android. i have not seen the ability of android to directly boot into WM bootloader without volume key usage. but would be nice if i am wrong, as many are dependent on the volume key! definitely anything is worth a try; hope you get it OP!

jsmccabe78 said:
you are right about rebooting into bootloader - but that is via WM, not android. i have not seen the ability of android to directly boot into WM bootloader without volume key usage. but would be nice if i am wrong, as many are dependent on the volume key! definitely anything is worth a try; hope you get it OP!
Click to expand...
Click to collapse
Yes, again I must agree. I checked.
With the wm6 on board you can trigger phone bootloader via USB and ActiveSync. With android can not.
So when you have a wm on your phone, you can install cLK or maglrd. When you do this, you have no way back with a broken vol-down button - for now.
Thank you jsmccabe78 for correcting

spalm said:
Yes, again I must agree. I checked.
With the wm6 on board you can trigger phone bootloader via USB and ActiveSync. With android can not.
So when you have a wm on your phone, you can install cLK or maglrd. When you do this, you have no way back with a broken vol-down button - for now.
Thank you jsmccabe78 for correcting
Click to expand...
Click to collapse
i saw, in another post, that i can copy the bootloader.exe file into de device and run from the phone. That can be usefull.
thanks

Gab00 said:
i saw, in another post, that i can copy the bootloader.exe file into de device and run from the phone. That can be usefull.
thanks
Click to expand...
Click to collapse
you are running android, correct?
i'm not saying don't try it, but i don't believe exe files do anything in android...give it a go and report back.

jsmccabe78 said:
you are running android, correct?
i'm not saying don't try it, but i don't believe exe files do anything in android...give it a go and report back.
Click to expand...
Click to collapse
I'm running android, i can't enter to the bootloeader. =(
i'll install another dft rom.
Thanks

【Discussion】How to use APX mode of Nexus7

There will be many QUESTIONS ....
Does anyone know how to use APX mode of Nexus 7?
In the APX mode, the fastboot and adb tool can't use, see the attached picture.
Click to expand...
Click to collapse
For Nvidia Tegra3, how to use its APX mode? Is it different with TF300T's Tegra3?
Does Nexus 7 have nvflash tool?
Click to expand...
Click to collapse
BTW, does anyone know how to get the SBK (security boot key)?
Does anyone know how to use wheelie???
Click to expand...
Click to collapse

I'm sorry but what is APX mode?
Verstuurd van mijn Nexus 7 met Tapatalk

Robin2 said:
I'm sorry but what is APX mode?
Verstuurd van mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
When you boot Nexus 7, press the power+volume up, you will access to APX mode.
And the Nexus 7 will stay in Black Screen.

padest.com said:
Do anyone know how to use APX mode of Nexus 7?
In the APX mode, the fastboot and adb tool can't use, see the attached pictures.
For Nvidia Tegra3, how to use its APX mode? Was it different with TF300T's Tegra3?
Does Nexus 7 has nvflash tool?
Click to expand...
Click to collapse
nvflash presumably should just work, try it? I'd assume this is a protocol that's not changing.
That said, I'd personally rather use fastboot to do stuff like flash recovery, etc. nvflash is a pain in the ass IMO.

Yeah, but nvflash is supposed to be able to do something fastboot can't: recovery / unbrick from a shredded bootloader.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1879228
We're already discussing it and looking into it.

HellcatDroid said:
Yeah, but nvflash is supposed to be able to do something fastboot can't: recovery / unbrick from a shredded bootloader.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1879228
We're already discussing it and looking into it.
Click to expand...
Click to collapse
yeah!
Especially, when the N7 access to deep brick, can't use fastboot tool, can't use adb tool!
Do you know something about SBK (Security boot key)?

khaytsus said:
nvflash presumably should just work, try it? I'd assume this is a protocol that's not changing.
That said, I'd personally rather use fastboot to do stuff like flash recovery, etc. nvflash is a pain in the ass IMO.
Click to expand...
Click to collapse
sure!
fastboot and adb are easily to use.
but, i wonder how can i do once the Nexus 7 access to deeply brick.

Bump...
Seems I also deep-bricked my Nexus 7... Any update on restoring it via APX / NVFlash?

If only my Samsung could abuse APX mode. Only thing a hard bricked ace gets is ARM11 dump mode (yay.)
Sent from my Nexus 7 using xda app-developers app

:cyclops:

bigooze said:
Bump...
Seems I also deep-bricked my Nexus 7... Any update on restoring it via APX / NVFlash?
Click to expand...
Click to collapse
when you long press the power key and volume down, can you access to the bootloader?

Hey guys,
I found SBK calculator goo.gl/j9Iic (input your CSSN number founded on nexus box).
I had almost same prolbem. I was on bootloader 3.14 and then i flashed bootloader 4.11.. after that i had google logo appearing and disappearing continiously. I managed to enter APX mode but when i'm trying to get access through nvflash utility it says
Unknown device found.
That's it... I can't do nothing more. I've tried both - windows and linux version of nvflash and both returns same message.
When I run 'lsusb' command from linus i see my nexus 7 as 0955:7330 Nvidia Corp. device.
Plz help anybody. :crying:

TXrTim said:
Hey guys,
I found SBK calculator goo.gl/j9Iic (input your CSSN number founded on nexus box).
I had almost same prolbem. I was on bootloader 3.14 and then i flashed bootloader 4.11.. after that i had google logo appearing and disappearing continiously. I managed to enter APX mode but when i'm trying to get access through nvflash utility it says
Unknown device found.
That's it... I can't do nothing more. I've tried both - windows and linux version of nvflash and both returns same message.
When I run 'lsusb' command from linus i see my nexus 7 as 0955:7330 Nvidia Corp. device.
Plz help anybody. :crying:
Click to expand...
Click to collapse
If you have the Google logo appearing you can Still access the Bootloader..just flash a Stock Image and you should be good to go.

manasgirdhar said:
If you have the Google logo appearing you can Still access the Bootloader..just flash a Stock Image and you should be good to go.
Click to expand...
Click to collapse
How could I flash anything if can't get access to fastboot?

TXrTim said:
How could I flash anything if can't get access to fastboot?
Click to expand...
Click to collapse
If you see the Google logo I think you will have access to the boot loader.

manasgirdhar said:
If you see the Google logo I think you will have access to the boot loader.
Click to expand...
Click to collapse
Google logo appears for like 7-8 sec and then reboot again and again. Volume down + power doesn't work so i can't get into bootloader \ fastboot mode..
[edit]
I could only enter APX mode via press&hold volume+ and power button for current mode.

TXrTim said:
Google logo appears for like 7-8 sec and then reboot again and again. Volume down + power doesn't work so i can't get into bootloader \ fastboot mode..
[edit]
I could only enter APX mode via press&hold volume+ and power button for current mode.
Click to expand...
Click to collapse
Had a similar case. I might say something stupid, but I seem to recall that holding both "Volume +", "Volume -", and "Power" did the trick and brought the bootloader menu back.

nathrinder said:
Had a similar case. I might say something stupid, but I seem to recall that holding both "Volume +", "Volume -", and "Power" did the trick and brought the bootloader menu back.
Click to expand...
Click to collapse
Unfortunately this isn't help in my case.

TXrTim said:
Unfortunately this isn't help in my case.
Click to expand...
Click to collapse
Hello, have you dealed with it?
I have the same problem
Cant access fastboot mode, nothing works only APX mode

bociaan said:
Hello, have you dealed with it?
I have the same problem
Cant access fastboot mode, nothing works only APX mode
Click to expand...
Click to collapse
Unfortunately no. But though my warranty was active ppl at asus service replaced motherboard.

[Q] USB Modem or CP Mode

Does anyone know how to get the Moto X into "Modem" or "CP" mode? I have QPST and need to flash a custom PRL, but Im not sure how to enable it on my phone.
Any help would be appreciated!

NetworkingPro said:
Does anyone know how to get the Moto X into "Modem" or "CP" mode? I have QPST and need to flash a custom PRL, but Im not sure how to enable it on my phone.
Any help would be appreciated!
Click to expand...
Click to collapse
The easiest way to access "Diag" mode is from the bootloader screen.
This post gives an excellent explanation: http://forum.xda-developers.com/showpost.php?p=54156240&postcount=224

samwathegreat said:
The easiest way to access "Diag" mode is from the bootloader screen.
This post gives an excellent explanation: http://forum.xda-developers.com/showpost.php?p=54156240&postcount=224
Click to expand...
Click to collapse
Sam,
Thanks for the thread, thats great. I did that now, and noticed that the phone simply boots normally when I select BP Tools. Do you know, does that mode require a custom boot loader? Is it possible that BP Tools is locked out in the stock boot loader?
Thanks again!

NetworkingPro said:
Sam,
Thanks for the thread, thats great. I did that now, and noticed that the phone simply boots normally when I select BP Tools. Do you know, does that mode require a custom boot loader? Is it possible that BP Tools is locked out in the stock boot loader?
Thanks again!
Click to expand...
Click to collapse
I'm not sure about that. Instead of selecting BP Tools, just see if you are able to communicate QPST from the bootloader screen itself.
You do have the Motorola drivers installed, right?
P.S. There is no custom bootloader. Recovery yes, but not bootloader...and recovery shouldn't matter.

Its starting to make sense, thanks for all the help so far. I found this post that really helped: http://www.rimweb.in/forums/topic/3...rint-moto-x-any-moto-g-cdma-to-reliance-cdma/
If this works out I will update my post with a how-to instead. Apparently when you select BP Mode the phone boots "normally" but has BP Mode enabled.
Thanks again!

[Q] help! Can't access bootloader

My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access bootloader and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:

fwkimi said:
My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access fastboot and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:
Click to expand...
Click to collapse
I doubt that you needed to use that fix. That fix is for the downgraded bootloader brick. I suspect you were only in soft brick. Was it bootlooping?
Hold power and volume down to enter bootloader. Do or did you have TWRP installed?
More information please.

Evolution_Tech said:
I doubt that you needed to use that fix. That fix is for the downgraded bootloader brick. I suspect you were only in soft brick. Was it bootlooping?
Hold power and volume down to enter bootloader. Do or did you have TWRP installed?
More information please.
Click to expand...
Click to collapse
Dear. there is nothing after hold power and volume down, can't reboot, enter bootloader and TWRP... There is nothing on screen even charging... Only black screen. It quite strange
It show new added hardware when the phone connect with PC.
I only root and install xposed. System is 5.1.1, international version.
It showed qhsubs_bulk before I install Qualcomm Drivers. So I think maybe there are similar issue. Thanks
View attachment 3397226
View attachment 3397227

fwkimi said:
Dear. there is nothing after hold power and volume down, can't reboot, enter bootloader and TWRP... There is nothing on screen even charging... Only black screen. It quite strange
It show new added hardware when the phone connect with PC.
I only root and install xposed. System is 5.1.1, international version.
View attachment 3397226
View attachment 3397227
Click to expand...
Click to collapse
Xposed bites another one. Lol

prdog1 said:
Xposed bites another one. Lol
Click to expand...
Click to collapse
oh no:crying: I install it on Nexus4, only reboot more times...

Leave on charger for a while. If battery all way down will not show charging and will not let into bootloader or recovery.

prdog1 said:
Leave on charger for a while. If battery all way down will not show charging and will not let into bootloader or recovery.
Click to expand...
Click to collapse
Ok, have a try.
The phone and charger are not very hot as charging. Will it impact HW issue? I'm lost:crying:

fwkimi said:
Ok, have a try.
The phone and charger are not very hot as charging. Will it impact HW issue? I'm lost:crying:
Click to expand...
Click to collapse
No. But if can't boot at all will have to RMA. N9 and N6 will show nothing if battery completely down. Has to have at least 10% (guessing) before will do anything once totally depleted.

prdog1 said:
No. But if can't boot at all will have to RMA. N9 and N6 will show nothing if battery completely down. Has to have at least 10% (guessing) before will do anything once totally depleted.
Click to expand...
Click to collapse
It's hardly to RMA in China:crying: I doubt it's HW issue...

fwkimi said:
It's hardly to RMA in China:crying: I doubt it's HW issue...
Click to expand...
Click to collapse
If unlocked and can get into bootloader there is a chance. If locked and won't boot not much hope.

prdog1 said:
If unlocked and can get into bootloader there is a chance. If locked and won't boot not much hope.
Click to expand...
Click to collapse
I unlocked it, but can't access bootloader... I need amend my title.

fwkimi said:
I unlocked it, but can't access bootloader... I need amend my title.
Click to expand...
Click to collapse
Leave on charger. Sounds like only hope.

prdog1 said:
Leave on charger. Sounds like only hope.
Click to expand...
Click to collapse
:crying: It seems only I hve this problem, is there anyone else? Or it's a HW issue and just happen on that time...

fwkimi said:
My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access bootload and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:
Click to expand...
Click to collapse
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.

gee2012 said:
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.
Click to expand...
Click to collapse
FWIW: it doesn't work on Ubuntu either.

cam30era said:
FWIW: it doesn't work on Ubuntu either.
Click to expand...
Click to collapse
Oke, it works on Linux according to users

gee2012 said:
Oke, it works on Linux according to users
Click to expand...
Click to collapse
Hmm. Must be me. Thanks. Anyway, I prefer to do it manually. Just like the transmission in my car.

gee2012 said:
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.
Click to expand...
Click to collapse
Sorry, I can't access bootloader. Nothing shows when power+volumn+ or power +volumn-. I think it maybe bricked

hi,
I seem to have the same problem as OP, I have no access to fastboot, either by console or button combination.
I also tried the solution provided by opssemnik but when I try to use blank-flash I get the error "sdl-transfer-image:send-image:sdl-open-multi:target error" when flashing singleimage.bin.
I have Lollipop 5.1.1. Any ideas? My phone seems a goner now...

none
DO you have SDK manager installed on your computer and your phone's manufacturer Drivers? If not install SDK Manager here.
http://developer.android.com/sdk/index.html#top Scroll down to the bottom of the page and select SDK tools only, you will see the link for windows.
After you've installed this and the drivers from the manufacturer go into SDK you just installed and install "Google USB Driver".
From there open a command prompt, plug your phone into the computer and type "adb reboot bootloader" without the quotation marks and that will get you into bootloader. you can also type "adb reboot recovery" without the quotes.
ANother way is to go to Titanium backup, hit menu, scroll down to reboot to recovery. One of those should work.

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.