Database Develop

[Q] 5.0.1 and ADB not finding device

OMG!!! I've hit the end of my rope with this. Let me start off by saying I don't post things, I find answers to them but this problem is killing me.
I have a Sprint Nexus 6 that I am trying to update to 5.0.1. However its being terrible, I reboot into bootloader with with power and volume - or adb reboot bootloader, and attempt to adb sideload (updatefile.zip) and error device not found. I do adb devices and sure enough its not there, however fastboot devices shows it. If I reboot into the OS and issue ADB devices OH **** THERE IS MY PHONE, adb reboot bootloader, and its gone again.
I've tried drivers froom google search direct google usb drivers, naked drivers 0.73, I've uninstalled inside of the os and reinstalled I've uninstalled in bootloader and reinstalled nothing works. I can issue fastboot commands but adb just eats a bag of ****. I also have an issue where adb gives an error that it is out of date and must restart, it then restarts and everything is peachy. I've tried to download something called adb fix, but it says there is nothing wrong. So I have no idea what is going on and if anyone could possibly help me get my phone updated so this notification goes away and I don't go into an OCD rage on everyone around me I would be much appreciative.
Side note
I cannot update via ota, no idea why it says installing then just errors out, I assumed it was because of the unlock, also when I'm in bootloader and I attempt to go into recovery there is just an android dude with his chest open. Now its been a while since I've had a nexus but shouldn't there be like a menu or something there? I also did the whole no encrypt boot.img nonsense here. I thought that was the problem so wiped data and flashed the stock boot.img... I'm seriously out of ideas......

well first off you have the stock recovery... that is the android dude.
I dont really have answers for you but the two things i would try would be a different computer and just using WUG http://www.wugfresh.com/nrt/ i have had issues in the past using an old ADB/fastboot.
If you have modified anything the OTA is going to fail.

Tried on two different computers,I'll try wug. Thanks

first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).

Maybe I am reading this wrong, but you are trying to adb while in the bootloader?

PaisanNYC said:
Maybe I am reading this wrong, but you are trying to adb while in the bootloader?
Click to expand...
Click to collapse
If you're reading it wrong so am I. Definitely sounds like he is incorrectly trying to use Adb in the bootloader.
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
Lucke said:
first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).
Click to expand...
Click to collapse
USB debug mode has nothing to do with boot loader or recovery. I'm sure you know this as you said it when booted, but many will read this and think you need debug in recovery or bootloader which wouldn't be true.

Help with Bootloader.

Morning everyone. I'm having some troubling problems with my bootloader. I've had it soft bricked before and was fairly easy to fix. But something is drastically different now. It seems every time I try to restore one of my saved backups, it freezes after a certain point, and sends me back in the boot loader loop. Every time I try to wipe system/data/cache it freezes and back to the bootloader loop. I tried opening a command prompt in adb, but it just says device isn't connected. I can still get into twrp and into the bootloader selection modes. It's just when I do certain things it freezes. For my backup I was able to get it to 36% completed before it froze. My phone is a Moto X 2nd Gen xt1097, and I am running a nightly CyanogenMod on it. Updated it last time about 2 days ago. I just cant find anything on how to fix this. Any help will be much appreciated!! Thanks!

Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?

USA1791 said:
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
Click to expand...
Click to collapse
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?

Gus Ghanem said:
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Click to expand...
Click to collapse
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.

USA1791 said:
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
Click to expand...
Click to collapse
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have

Gus Ghanem said:
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Click to expand...
Click to collapse
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.

USA1791 said:
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
Click to expand...
Click to collapse
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.

Gus Ghanem said:
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Click to expand...
Click to collapse
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?

USA1791 said:
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
Click to expand...
Click to collapse
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?

Gus Ghanem said:
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Click to expand...
Click to collapse
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.

USA1791 said:
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
Click to expand...
Click to collapse
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working

Gus Ghanem said:
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Click to expand...
Click to collapse
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.

USA1791 said:
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
Click to expand...
Click to collapse
Yes it looks like fastboot is working, you should delete those screenshots now.

Gus Ghanem said:
Yes it looks like fastboot is working, you should delete those screenshots now.
Click to expand...
Click to collapse
Oh. Okay got them deleted. Didnt think they'd show anything personal?

After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 0 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
USA1791 said:
Oh. Okay got them deleted. Didnt think they'd show anything personal?
Click to expand...
Click to collapse
Sort of, unique to your own phone, like IEMI, Serial Number, etc.

Gus Ghanem said:
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 9 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Click to expand...
Click to collapse
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!

USA1791 said:
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
Click to expand...
Click to collapse
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2

New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?

Gus Ghanem said:
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
Click to expand...
Click to collapse
Oh thanks, I guess they are dated lol.

USA1791 said:
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Click to expand...
Click to collapse
No don't flash supersu, it causes problems
Yes try copying the CM and Gapps zips to you phone, and try flashing them with TWRP...
which version TWRP you have on the phone?

Downgrade android 9

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:

So I tried to unlock via EDL...

...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.

Question Straight forward way to unbrick Redmi note 10 pro global version!

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..