yashsingh1/xdaforums huggingface dataset:
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] RichDoe252:
superbrick.

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.
[ASUS ROG Phone II Questions & Answers] reg66:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
[ASUS ROG Phone II Questions & Answers] RichDoe252:
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.
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] RichDoe252:
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.
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] TikiThePug:
Bro get to sleep! Such a good Samaritan
[ASUS ROG Phone II Questions & Answers] reg66:
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
[ASUS ROG Phone II Questions & Answers] TikiThePug:
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
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?
[ASUS ROG Phone II Questions & Answers] TikiThePug:
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.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
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.
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] reg66:
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 [MENTION=10748381]RichDoe252[/MENTION]. 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.

[MENTION=10748381]RichDoe252[/MENTION] 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
[ASUS ROG Phone II Questions & Answers] reg66:
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
[ASUS ROG Phone II Questions & Answers] RichDoe252:
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.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
Oddly enough, my PC is old enough all it has is USB 2.0

I think.
[ASUS ROG Phone II Questions & Answers] reg66:
Hey fella. Sorry, I chose to email the info to your allocated email address with xda. Have you checked there? I just checked my sent messages on xda but there's no record of the messages. Check your emails, if there's nothing there, i'll type it out again and pm you instead of sending to email (with a link to your inbox on xda, hopefully it'll work)

---------- Post added at 03:05 AM ---------- Previous post was at 02:48 AM ----------

OK, so I just saw your email to me. Have sent a link to a guide and some key notes for you... Good luck, let us know how you get on
[ASUS ROG Phone II Questions & Answers] RichDoe252:
I have the tab pulled up right now and I am going to try to muddle through the process. If you don't mind clarifiy some things for me:

Why does QPST need to be installed on or near the PC's root?

I currently have it recognized on my PC as "Qualcomm HS-USB QDLoader 9008"

Ok, so the MiFlash tool isn't seeing it. I just shows "COM3" instead of the unique device ID.
[ASUS ROG Phone II Questions & Answers] reg66:
Well I've just been googling it, there's not a lot of info so I can't be sure. But I have seen images where other users have been Xiaomi devices without Device ID but COM10 or COM5 etc. So you may be good to go. I'll keep looking though, it's up to you if you want to try the flashing process

---------- Post added at 03:24 AM ---------- Previous post was at 03:21 AM ----------

Did you click the 'refresh' button after it shows COM3?
[ASUS ROG Phone II Questions & Answers] RichDoe252:
A-Firm. QPST shows the same thing too. I'll go with your suggestion and just follow the flashing instructions.
[ASUS ROG Phone II Questions & Answers] reg66:
OK dude, fingers crossed. If it does flash without error, also be sure to do step 6...

Press the Volume Up/Down keys until you see “Recovery Mode” on the top of the screen. Then press the Power button to confirm and boot your ROG Phone 2 into the stock recovery mode.

Once in stock recovery, use the Volume keys to select ‘Wipe data/factory reset‘ and press the power button. Then select ‘Factory data reset‘ and press the Power button again to confirm and perform a factory data reset. Finally, select ‘Reboot system now‘ in stock recovery to boot your phone into the system
[ASUS ROG Phone II Questions & Answers] RichDoe252:
No dice. Unable to flash it. It looks like the .bat file that it uses the get the phone into EDL is actually using fastboot, which isn't currently working on my phone.
[ASUS ROG Phone II Questions & Answers] reg66:
When you say you're trying the .bat file, do you mean the one described in step 2 of the guide - 'reboot into EDL mode.bat'? Maybe you didn't see my message from before, I'm thinking/hoping that your phone is already in EDL mode, so step 2 doesn't apply to you.

If so, ignore step 2. Do steps 3, 4 and 6. Or are you saying that you tried to flash the image folder using miflash tool but without success?
[ASUS ROG Phone II Questions & Answers] RichDoe252:
So this is getting a little ominous.

"cannot recieve hello packet"

I'm going to try and go through what other services may be trying to get into my phone in case one of them is preventing communication with the MiFlash tool.

Is it possible the phone is still running in a loop? That it is still hanging on something and that's why it isn't responding to anything? I did leave it uncharged for over a week.
[ASUS ROG Phone II Questions & Answers] reg66:
OK dude, i think you're getting that message because EDL mode has timed out. However, that's only a guess going from what others have said about 'cannot recieve hello packet'. But it could be as simple as a fussy USB port

So, options;

1. try once more to hold vol- and power button for 20-30secs to see if the phone restarts. If it does, get the miflash tool open and ready for flashing. Connect phone to PC using side port. Power on the phone. Click refresh in miflash tool. If recognised, try the flash again.

or 2. try once more to hold vol- and vol+ and power all at the same time for 20-30secs to see if the phone now powers down. If it does, get the miflash tool open and ready for flashing. Connect phone to PC using side port. Power on the phone. Click refresh in miflash tool. If recognised, try the flash again.

or 3. You could be getting the 'cannot recieve hello packet' message simply because it's not liking the USB port. Try another port.

If none of the above options are working ie button pressing to power off or restart, one possible way to detect if the phone has run out of battery is to connect it to your pc (pretty sure you mentioned that you still got the device connected sounds when plugging it in). Plug the phone in once per day, if you hear a sound, then the phone is still on. No sound should mean it's finally run out of battery.

Option 4. If none of the above work, you're gonna have to wait until the battery is definitely dead. I've got no idea how long it'll have to be left for as it's got a big 6000mAh battery. But, once it's DEFINITELY empty of battery, charge it up for an hour or so (to be sure the battery doesn't fail during flash) and get the miflash tool open and ready for flashing with the 'select' option pointing to the 'images' folder. Connect phone to PC using side port. Power on the phone. Click refresh in miflash tool. If recognised, try the flash again following the steps on that guide.

Probably the easiest option to try is changing USB ports.
[ASUS ROG Phone II Questions & Answers] reg66:
Sorry to add yet more content to this thread... But, I've had problems before using the portable version of miflash tool - it kept giving an error. However, when I used the Mi Flash tool included in MiFlashPro, it worked (although, admittedly this was on a Xiaomi device).

So, if option 4 above still does not work, download and install MiFlashPro from here. Open the software up and (ignore the home page/tab) go directly to the Mi Flash tab (4th tab along the top of the UI). Click on 'select' again, navigate to your 'images' folder and click 'OK'. Plug the phone in (side port), click 'refesh' and provided your device shows as either ID or COMx, try to flash using that version.

One more thing... If I recall correctly, Mi Flash tool didn't flash due to errors when the long-named images folder was located deep in D: drive ie I think the path to images folder was too long. You may need to have your images folder in root of C: drive (or close to the root)
[ASUS ROG Phone II Questions & Answers] RichDoe252:
Reg66, I want to thank you for all your help, but I am caving and just sending my phone off to ASUS to get restored back to factory default. I will still have to unlock it, reroot it and do all that jazz to get the WW distro on it, but I am still going to be back at square one with it not taking calls and barely texting on t-mobile. Hopefully ASUS will let me know exactly what happened to it so I can actually find out.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
So I don't know if anyone is still following with thread, but I got my phone back from ASUS, unrepaired. They cannot repair it as it is the tencent version and was originally sold in china. They only repair North American phones or just non-chinese phones. I am now back to square one. I still have not been able to get any response from the phone what so ever. As the only application that was able to recognize anything from that phone was QPST, I am going to go learn more about it and see if I can get back on the right track. I am hoping to make a more complete and more accurate guide to the rooting process in the end as most of the most crucial information is not readily available.

Thank you all for your help and do drop me a reply if you are still willing to lend a hand.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
The First Drop of Success

I honestly don't know if it was the position of the obsidian on the dark alter of my CPU cooler, or just that I got everything on my PC to stop trying to talking to my Phone, but I have actually gotten MiFlash to start the flashing process on my bricked phone. I am currently flashing the QPST Firmware to my phone. 294 seconds in and everything is actually working.

I am still not exactly certain where to go from here, but if EDL mode pops up, I may just cry.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
First Sign of Life

I have a single blinking red light at the top of the screen.

That is it.

A cursory search states that this make be a critical low power state, so back on the charger it goes. Either way this is the most life it has shown in months. I don't really know what to do from here, but if I can get it into EDL you can bet your biscuits that I will be all over this forum to get it back to the lastest WW distro ASAP.

Otherwise, I may just let it charge for a long while and then try flashing it again.
[ASUS ROG Phone II Questions & Answers] RichDoe252:
It's alive! The charging screen is up! I've never seen anything so beautiful!
[ASUS ROG Phone II Questions & Answers] reg66:
:laugh::good:
[ASUS ROG Phone II Questions & Answers] RichDoe252:
What Comes Next

Ok, so it has booted into Android, and appearently, flashing it once with MiFlash was enough to get it back to operating. I don't doubt that my phone is not 100% stable, but from here on out, I just shouldn't do what I did last time.

I still have the WW distro, but I don't believe it is rooted. My understanding from this point forward is to modify a boot file, copy that to the phone, and reboot it with root now enabled. I will go review the various guides, I feel like all of them are partially complete, or leave out critical steps or troubleshooting points.
[ASUS ROG Phone II Questions & Answers] waiflih:
I don't know if it's really related, but with the last win10 update I can't see my phone in fastboot mode, I had to use an old notebook with win7 to flash the boot image to update. Its a win10 problem
[ASUS ROG Phone II Questions & Answers] RichDoe252:
So a while back I was finally able to get fastboot/adb working, and then I promptly bricked my phone by just throwing stuff on it with fastboot while attempting to root it.
[ASUS ROG Phone II Questions & Answers] becker666:
Wow I don't wanna brick my LG Stylo2 plus which still works wonderfully...I've been trying on Mac/Win7/Win10 and all give me the same : adb devices lists my phone but fast boot stays on waiting on any device
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] andre tan:
Didnt experience any of these isuue tho... have you updated the game opt. Service via galaxy store?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] auToeXeC_g33k:
Yes, everything is up to date.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] chieco:
Samsung ****ed every exynos user. It's simple as that. Also, no fix, EVER. If you can return it DO IT. No one is going to do anything about it. Everyday I see people starting threads on xda or reddit complaining but nothing is happening. We in Europe have laws that protect us against this kind of ****ery but again no one is ready to fight Samsung. If this continues 80% of forums post will end up like this one.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] auToeXeC_g33k:
My issue is not related to temperature and most of the problems that come with the Exynos chip are due to it running hotter and throttling. I don't think this is it.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] PhatBurana:
I have the exact same issue you described with my S20. Searched but haven't found any solution either. Any information on this would be nice.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] stefan243546:
I do not own an S20 Exynos, I have the Snapdragon variant, but with my S10+ Exynos, I swear that after the Android 10 update I had started to experience the same issue. Even Clash Royale dropped for no reason to 20fps, not to mention Asphalt 9. It would sometimes go away after a reboot, other times not. Guess all you can do is wait for the Android 11 update, unless samsung issues some game optimizing service update that fixes this issue.
[Android Q&A, Help & Troubleshooting] alysia00:
I have a custom firmware for RK3288 that I'm trying to extract the img file and modify some of the files and system settings. I've tried lots of different tools to try and extract it but no luck. Here's a link to the file: https://drive.google.com/file/d/1HX0sLvRID2G_20z21Dykn4QF0oKUOckY/view?usp=sharing

I would really appreciate if anyone could help me out with this :)
[Android Q&A, Help & Troubleshooting] Sands207:
Try aik or superr's kitchen, either one should work [emoji106]
[Android Q&A, Help & Troubleshooting] alysia00:
Tried both already, they don't work :\
[Android Q&A, Help & Troubleshooting] Sands207:
Are you extracting from a rooted device or are you working with firmware?
[Android Q&A, Help & Troubleshooting] alysia00:
I figured it out. It needed special tools make for the rk3288 to extract the img file. I needed AndroidTool_Release_v2.38.
[Android Q&A, Help & Troubleshooting] Sands207:
well done! :)
[Huawei Mate XS Guides, News, & Discussion] avetny:
To block all advertisements just fill this address in private DNS

dns.adguard.com

Enjoi browsing without advertisements.