Database Develop

[stock rom][3.0.1] P7100BUKDF + bootloader unlock

Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !

Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?

bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !

Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.

Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now

No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?

My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.

Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.

Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method

gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery

Added the SD-CARD wipe notice for ya

How do root this firmware ?
Thanks

http://forum.xda-developers.com/showthread.php?t=1079781 ?

any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.

Has anyone tried flashing with Heimdall in Linux?

As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.

Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).

I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.

The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!

Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?

Moto G xt1072 won't boot at all after installing TWRP+SuperSU

Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?

Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.

If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:

None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.

The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?

LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.

Very hard Brick. Only Bootloader warning

Hello there. Me was given a Razr i XT890. If i turn on there only the "Warning Bootloader unlocked". I try to get in Fastboot mode or any other mode but i only stuck in this window or nothing. I dont even get a Batterylogo if i load with the wall charger. I put it on my PC but nothing happens. No new Device. No ADB. Nothing. Can i rescue the phone or is it only a paperweight?

Most likely a brick. U could try to do something with the xfstk flasher. Search it up, get the right files and hope it works

It's recoverable!
Gindler said:
Hello there. Me was given a Razr i XT890. If i turn on there only the "Warning Bootloader unlocked". I try to get in Fastboot mode or any other mode but i only stuck in this window or nothing. I dont even get a Batterylogo if i load with the wall charger. I put it on my PC but nothing happens. No new Device. No ADB. Nothing. Can i rescue the phone or is it only a paperweight?
Click to expand...
Click to collapse
The first thing you should do is to see this video (https://www.youtube.com/watch?v=OTzaiwj-bGw) to install libusb on your computer (if you are using Win 8 or 10 you will need to remove the signing imposition on driver installation - search for it).
The second action is to download the programs provided in this other topic of the community:
Download -> https://forum.xda-developers.com/attachment.php?attachmentid=1795067&d=1362945847
Topic Forum - >https://forum.xda-developers.com/showthread.php?t=2184877
Then follow the instructions:
1 - With the cellphone turned off, connect it to the pc by the USB cable holding the camera button, when vibrate, release. (The green light should be on).
2 - Run xFSTK-SoC-Driver-Setup-1.0.3.exe and follow the instructions. (Your cellphone will probably turn on and will be locked on the bootloader unlock warning screen).
3 - If the phone has turned on, it will remain locked, then press and hold the camera buttons + volume down + power button. (It should vibrate, then release the buttons, if all goes well it will turn green).
4 - Run the unbrick.bat, when you start the prompt keep holding down the volume button of your cell phone. (If all goes well it will restart, continue with the down volume button pressed, when on it should enter fastboot mode.
If you get here and he gets into fastboot mode, CONGRATULATIONS you got it. Now just install the rom via RSD Lite. (Look up if you do not know)
Remember that your cell phone must have the bootloader unlocked for installation of the factory rom.
I do not guarantee origin, be aware that it is at your own risk
I hope I have helped!

Great! People from everywhere thanks you a lot.

brun0_csa said:
It's recoverable!
The first thing you should do is to see this video (
) to install libusb on your computer (if you are using Win 8 or 10 you will need to remove the signing imposition on driver installation - search for it).
The second action is to download the programs provided in this other topic of the community:
Download -> https://forum.xda-developers.com/attachment.php?attachmentid=1795067&d=1362945847
Topic Forum - >https://forum.xda-developers.com/showthread.php?t=2184877
Then follow the instructions:
1 - With the cellphone turned off, connect it to the pc by the USB cable holding the camera button, when vibrate, release. (The green light should be on).
2 - Run xFSTK-SoC-Driver-Setup-1.0.3.exe and follow the instructions. (Your cellphone will probably turn on and will be locked on the bootloader unlock warning screen).
3 - If the phone has turned on, it will remain locked, then press and hold the camera buttons + volume down + power button. (It should vibrate, then release the buttons, if all goes well it will turn green).
4 - Run the unbrick.bat, when you start the prompt keep holding down the volume button of your cell phone. (If all goes well it will restart, continue with the down volume button pressed, when on it should enter fastboot mode.
If you get here and he gets into fastboot mode, CONGRATULATIONS you got it. Now just install the rom via RSD Lite. (Look up if you do not know)
Remember that your cell phone must have the bootloader unlocked for installation of the factory rom.
I do not guarantee origin, be aware that it is at your own risk
I hope I have helped!
Click to expand...
Click to collapse
Hey, Bruno! You prolly don't open this forum anymore, but I'm trying to unbrick a moto razri that has this exact problem. I'm trying to follow the steps you sent, but it's pretty confusing, since some of these files are from 2009 or from some other windows like XP, Vista, or 7, and I'm trying to do all of this on my Windows 10 machine. Can you please try to update these steps? Thanks!

Attempting to enter recovery mode...

I recently bought this device. I usually root/unlock bootloader on my devices. I haven't attempted anything on this watch yet, but I did try to enter recovery mode. I reset the device and waited for the screen to turn off. Once the screen turned on and showed the LG insignia, I swiped my finger from the top left corner down to the bottom right (as I read on another post). This took me to the bootloader. After that, I selected the recovery option. This caused the classic Android with it's chest open, red triangle, with an exclamation point. My current phone (OnePlus 3) has an unlocked bootloader and root. I doubt it's related, but could that be causing an issue since they're connected? Android Pay works on the watch even though it won't work on the rooted phone.
Is there not a stock recovery on this device, is it locked, or is this a result of the current state of my phone?

The red triangle means a fatal loading error and all processes have ceased. In other words it isn't letting you into the recovery, same if you hold the two buttons you can get to the bootloader but selecting recovery gives you the same result.

Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.

matejdro said:
Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.
Click to expand...
Click to collapse
No known way to connect it while in the bootloader menu? I've been using it with Android Studio to work on watch faces and an instrument tuner. I haven't tried connecting while in the bootloader menu though.
The command is:
adb connect (your watch ip address)
Thinking about it though, I think they both have to be on the same WiFi network. Maybe it's not possible.

This only works with ADB (when watch is fully turned on). It does not work with bootloader.

Works on download mode as well but couldnt get anything to do in there

Grumps said:
Works on download mode as well but couldnt get anything to do in there
Click to expand...
Click to collapse
Do tell more. You can actually connect to the watch when it is in download mode?

matejdro said:
Do tell more. You can actually connect to the watch when it is in download mode?
Click to expand...
Click to collapse
Yes had to setup my home wifi to be open. then reboot in download mode
But as i said once in download i dunno what we can try?
Gets IP adress which is the same ip it gets with adb and can connect with adb on that ip so it is possible to connect to wifi somehwo in that download mode.
Youtube Video : https://youtu.be/IVNmEXj-6Pk
Trying to get lg Flash tool to connect but need dll. it has network option so it should be possible
Can even ping the ip so we should be able to do something?

Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.

matejdro said:
Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.
Click to expand...
Click to collapse
Hopefully. Older Samsung phones are rooted via download mode so maybe it will be possible somehow

Well, I plan to try it as well, using your findings (thx!) with this.Wish me luck. Having flashing available is just one step. we don't have twrp or magisk yet

Hello, could you please repost your video? because I am trying to do the same, and I am failing. I set up guest wifi between my laptop and the watches. it is not protected by any password/wpa. watches are pingable, and I am able to adb to it. but after rebooting to bootloader, I am unable to connect. I would like to perform at least oem unlock, but I can't, as I am unable to connect to it.
Could you please provide more detailed howto?

BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
From there, we can sideload ZIP. Question is, what zip? I can only assume that it has to be genuine firmware (OTA) and that it has to be downloaded to internal memory prior of rebooting to recovery. So manual update is possible.
Problem I have right now is, that bootloader is locked, and in order to unlock it, we'll need fastboot connection. But the bootloader in the watch does not support so called 'SoftAP' feature. Seems like it will need an update from Google. But when this will happen I don't know. Possibly with Android 9 update? There must be a way, but LG says that they do not share technical specs, ATT gave me unlock code (I assume for SIM unlock, but my watches are already SIM unlocked). Any ideas? There has to be a way to connect to watch once in recovery, download or bootloader (all three modes are fully functional, just without wireless connectivity).

Question
Virnik0 said:
BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
.
Click to expand...
Click to collapse
I have a Ticwatch Pro and am trying to get past the exclamation/no command screen when going into recovery. I have tried literally every combination of button presses with the two side buttons and still cannot get any results. Google searches have turned up little in the way of solutions. So, to all the smart folks here on XDA, how can I get this damn watch into recovery!?!?
(background on why - didn't wear the watch for a few weeks, watch battery dies. When charged and rebooted, got a message that my watch was locked with find my device. From there, I have tried all my potential passwords to unlock but nothing worked. I am left to reset outside the OS now so help is GREATLY appreciated)

you need to press in "phone info" long press until you see adb enable bro

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.