So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.
Take the Oreo .zip, unzip it, boot into bootloader, open up a Command Line/Terminal (depending on your OS), cd to the unzipped Oreo folder, type in fastboot flash-all, wait for that to end, then reboot into bootloader again and fastboot flash both boot and system (it should automatically flash it into the assigned partition)
I did this in order to update to MR1
downgrade issues
not what was being asked.
you need to use a 3rd party usbA to usbC cable (stock cable doesnt play well)
once thats done, test its connected using 'fastboot devices' you should see the serial number of your phone.
then run the flash_all command (remember to unlock bootloader and critical partition beforehand)
minimal adb and fastboot installer PLUS android bootloader interface driver is required if not installed already.
good luck
I just bought 4 micro USB to type c usb adapters from Walmart's website for 7 dollars. I can use all of my previous cables from my old phones. I haven't had one issue with them and my old fast charger from my Nexus 6 works and charges the phone rapidly. It's kinda clunky but beats spending 30 bucks on 1 cable.
It was a long night and I was on my 5th beer when I typed all that up!
My USB-C cable from OnePlus works fine with this phone on my laptop
I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Click to expand...
Click to collapse
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.
jal3223 said:
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.
Click to expand...
Click to collapse
Don't I need to use fastboot to flash the kernel :-/
Sent from my Phone 2 using Tapatalk
have you solved this problem?
Spunkybob said:
So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.
Click to expand...
Click to collapse
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
fastboot flashing unlock_critical doesn't work for you?
Ventigo said:
fastboot flashing unlock_critical doesn't work for you?
Click to expand...
Click to collapse
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day
capxcom said:
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day
Click to expand...
Click to collapse
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.
Lucifer6 said:
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.
Click to expand...
Click to collapse
Change the USB cable and try a different USB port,I think that may work for you.good luck!
capxcom said:
Change the USB cable and try a different USB port,I think that may work for you.good luck!
Click to expand...
Click to collapse
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
I just use a different cable and a different USB port , which I did all this before and it didn't work,but I don't know why it worked this time.
I just use the command" xxx\fastboot flash unlock_critical"(hope I memories this right,better find it on the Razer website),the same command with the Razer phone 1 which is posted on Razer official website .You have to unlock the bootloader first just like the Razer phone 1, the only difference is you don't need to unlock the bootloader by typing unlock bootloader on the pc ,you can just operate on the phone to unlock bootloader by pressing the "unlock the bootloader "in the bootloader interface.
When you use the command to unlock the critical ,it might let you to select yes on the phone's bootloader interface ,you can also see it on the CMD of you pc,it say something like xxx success,and if you run the command again it will say something like " unlock failed (already unlocked)"
Then you can try with flashing the stock firmware to see if you unlock the critical successfully,if you can flash the stock firmware then you can use any fast boot command on this phone .I installed the costume kernel right after I flashed the stock firmware.it works like charm.:fingers-crossed:
now the phone never get over heating again and the battery can last a whole day under my havey use.
---------- Post added at 07:47 AM ---------- Previous post was at 07:35 AM ----------
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Maybe you can also try to install the right bootloader driver which can be found on Razer website ,just check the official tutorial about flashing the stock firmware for Razer phone 1.
The bootloader driver is different from the adb diver.Better do everything exactly the same as it says in that tutorial step by step.
capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
Edit: my phone didn't load newer posts
For everyone else, I was able to do this at work yesterday and I'm back on 8 and loving it.
Edit 2: it was either the different cable (same one as at home just lives at work) or the laptop did something different.
Sent from my Phone 2 using Tapatalk
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Click to expand...
Click to collapse
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
If you can install the stock firmware you should be able in use any fast boot command
capxcom said:
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Click to expand...
Click to collapse
I've already done it just saying what my issue was.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
I've already done it just saying what my issue was.
Click to expand...
Click to collapse
Good for you!
I'm suggesting everyone to unlock the bootloader and the critical first before start to use it.My last RP2 can't start up ,it will freeze on the starting screen as I didn't do anything before using it,I can't do anything with it as the locked bootloader.Lucky for me,I returned it and then I bought a new one .I love this hardware but Razer's software team should be fired !Just hire someone from xda should work perfectly:laugh:
Related
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..
Are you using minimal or full sdk (by Google) platform tools?
Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha
I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird
A different pc solved the issue.. wtf.. thank you..
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..
...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?
dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.
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.
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?
Robbie D said:
My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?
Click to expand...
Click to collapse
I would suggest side loading TWRP via adb in fastboot, at least you'll get recover back and can start from there.
I have tried to do that.. for some reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
edit : grammar.. using cheap phone till I can get my sweet restored and working again.
Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?
Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
Further to what I said above, try this method
Xavind said:
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?
Click to expand...
Click to collapse
no.. nothing happens
Robbie D said:
no.. nothing happens
Click to expand...
Click to collapse
Adb should be in root path c
It should be started with admin rights and of course the drivers for the phone should be installed before
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
Xiaomi Redmi Note 10 Pro USB Drivers | Device Drivers
The drivers to connect/unlock the Xiaomi Redmi Note 10 Pro smart phone to backup,tether, network and more are below. Be aware if you are looking to unlock the bootloader or other advanced software functions it most likely will void any existing warranty. Also Functions used at the fastboot...
oemdrivers.com
Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
update drivers , then pc should read fastboot.
download and then flash recovery using
fastboot flash recovery (***).img
through recovery install rom again
I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though
Finally got back to this and made sure to put all of the files in c: drive... It shows something on a port, but no devices..
I connected my cheap moto g play and it shows up. I guess that eliminates bad cable and possibly phone is literally Perma bricked?
Xavind said:
I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though
Click to expand...
Click to collapse
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?
Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?
No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.
Robbie D said:
No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.
Click to expand...
Click to collapse
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices
Laptapper said:
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices
Click to expand...
Click to collapse
Did you look at the photos in my previous 2 posts? The first shows something is there, but doesn't give a device name or number.. The 2nd shows my moto g play and it is identified by fastboot devices... I think the entire storage, including any factory recovery or images are all completely gone..