Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,
Success is disgusted by some people, and will not share any files for free in the future.
It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.
What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...
For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed
Related
Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.
After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!
I just received the Pixel 2. Connected it to a Windows 10 box. Windows installed Microsoft drivers. I can't install Google drivers because Winblows says that the best drivers for my device are already installed. So I open an Explorer window, and there's the Pixel 2. I open that and it's a totally blank window. No, it's not the phone - ES shows directories in internal storage. (To make sure, I took a picture. It's in /DCIM/Camera.)
Enable debugging. Enable unlock. adb devices. No devices.
Okay, manually reboot to the bootloader. (The last line is Device State: locked) Fastboot sees the device.
fastboot boot twrp.img (I renamed it to make it easier). "FAILED (remote: Operation is not allowed in Lock State)"
I've owned Samsungs for so long I forgot that there were other manufacturers. What am I doing wrong? (I know it's got to be me, not the phone.)
How do I force Windows to replace the drivers (or do I really have to boot into Linux?) And how do I get the thing unlocked? Yes, I googled it. I searched here. I'm still stumped.
Maybe try this all in one tool
https://forum.xda-developers.com/pixel-2/development/tool-tool-one-driversunlocktwrpfactory-t3730228
Then check this out:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
flashing unlock did it. Thanks. Now to see if I can install everything (TWRP, Magisk, etc.) then a day of reinstalling all my apps and data.
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Rukbat said:
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Click to expand...
Click to collapse
To get your device to show up you have to pull the notification shade down and then change the device mode to mtp storage mode. As for updating to new security patchs I usually just use the factory image from Google and the flash-all script with the -w option removed in order to keep my data. Then flash my kernal and magisk.
I already had it set - I guess unlocking the bootloader resets it.
Rukbat said:
I already had it set - I guess unlocking the bootloader resets it.
Click to expand...
Click to collapse
It resets Everytime you disconnect the device or reboot for some dumb reason. It gets annoying.
Maybe in an update far away ...
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank You
_satish_ said:
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
Thank You
Click to expand...
Click to collapse
Attaching Screen shot
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrpeev said:
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
View attachment 5603673
Click to expand...
Click to collapse
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Are the drivers installed correctly, ie with admin rights, and if so, is the help in the link that works, but requires more time and effort. With that guide, I will install the win 11 and win 10 drivers myself.
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
hammered58 said:
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Click to expand...
Click to collapse
that was correct, now the fastboot finds the device while in BL, thank you!
Hi!
This is my first post here, I hope I won't make many mistakes and troubles...
A friend of mine asked me to help him with his car Android based mirror.
The mirror is a "4G Adas Mirror" which is now stucked on the boot screen/logo.
Android version on the device is 8.1.
I've tried to reset through the hard reset button, without success.
I tried to connect the device on my PC to try to get access with adb, no success.
Adb cant see the device, the device list is empty.
When I check in the device manager on my PC I can see under "Portable Devices" installed,
with the name "MTP USB Device".
I also downloaded several drivers but can't install them, not for my device.
And now I'm out of ideas.
If somebody have any idea what could I still try to bring back the device into live, I would really appreciate.
Thank you.
Btw.:
My PC is running win10 x64 Pro
You're probably stuck with only the MTP interface (and not a composite device with MTP and ADB) but it might be worthwhile to double check.
Is the MTP interface active? Can you see any files in Windows File Explorer?
You can check with UsbView.exe to see if there is only one interface, the MTP.
The next step is to try various buttons on boot to see if you can get to recovery, fastboot or ROM bootloader.
Thanks for the fast replay, I cant access the device throug any file manager, as you mentioned, I checked with UsbView.exe already, just to be sure.
The MTP is active.
I've tried many many times the switch combination with the reset button, to try to get into any recovery or whatever cmd line mode, but without success.
The device hase only two buttons:
1. Power button
2. Reset button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, there's many ways to skin a cat.
If you open it up there could be a UART with a rooted hardware console.
There could be pushbuttons or test points to get into some other mode.
Good photos will tell us.
So, here we are....
the mirror crashed until I tried to open it.
However, if somebody is interested to hack and poke around this device, I'm familiar to open the device,
make schematics, pictures and try to hack into the device to try to make it alive again.
If somebody is willing to be a part to this pls. let me know and let's get started.
Open it up and take photos.
I'm trying and searching for a way how to open it but not fully crack the mirror, which is actually also a monitor...
I hope I will open the device soo and be back...
Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?
Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...
it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.