Related
Hey guys
I did a terrible mistake. Instead of just normally resetting the phone to factory settings in CWM after unlocking it, my finger slipped to the "format /system" option.
This happened before, but then I just sideloaded the rom and everything was ok. Oddly enough, this doesnt work anymore.
Whenever I want to push something to my phone using adb, I get the error that the device was not found and I cannot do anything to access the phone (when entering the command "adb devices" for example, no device shows up). I installed every driver I can think of, I installed all the packages in the sdk manager and now I dont know what to do.
I know that the debug mode is required, but since theres no OS anymore, I really ran out of ideas.
Please help me! :crying:
PS: additional information:
- HTC One m7 (unlocked)
- Clockwerkmod Recovery
- Windows 8
- Hasoon2000's all in one kit
EDIT: I found this site that recommends flashing via fastboot. (blog.syedgakbar.com/2013/02/01/android-installing-system-images-using-flashboot/)
where do I find these images?
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
Q&A for [ROM] HUAWEI Ascend W1-U00 | v1.00
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
DerSchorsch1 said:
It seems that in this video it's described, how the sdcard-problem can be permanently solved, so that we don't have to put the card out and in after a shutdown. Is this right?
Can this be implemented in the rom?
I don't understand the steps to do in the video. I can only recognize that i has something to do with visual studio. Can someone describe it more detailed?
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
Everyone please donate, so he can buy a new gorilla glas display!
Click to expand...
Click to collapse
You did notice that this is an emulated device I hope? Rules for an emulator and for a live device are usually different.. just because a fix works in the emulator it doesn't have to work with the device.. and as far as I'm aware it doesn't.
Carrier Lock
Hi there,
Thanks for the ROM dev work!
I have a W1 which was O2 branded, after the procedure of installing the ROM, my phone has become carrier locked..
Is there an option I missed during install?
Regards,
Ed
I need help
Hello, I also use the HUAWEI Ascend W1 I come from China, I would like to know about the method of making the rom, and I open the app file will get a mbn file and do not know how to proceed, and I'm very interested in this, you can explain under it? (My English is not very good, but please forgive me use google) If you teach me, would be extremely grateful!
Hello,
thanks WojtasXda for the effort!
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
It will be possible to install the rom from Osx or linux?
Registry tweaks from russian forum (4pda)
Here, guys, tweaks for our HUAWEI W1.
Go to \Windows\Packages\RegistryFiles and place OEMSettings.reg here.
First bootup will be ~2 minites.
Tweak list:
-Camera sound on/off in sound settings;
-Wi-Fi connection sound on/off;
-3g/Wi-Fi arrows in status bar switched on;
-Activated PfD (don't install program);
-Jailbreak(interop unlock,capabilities unlock)
-Can be installed hacked appx's from wp-seven
-SDK registered
-Search button opens google
-Any app can be placed to camera's button (e.g. OneShot)
-Now you have Nokia Lumia 920 (doesn't really work).
To make your phone 'NL920', you must mount in regedit 'SYSTEM' and install 2nd (zip). After that, you can easily install all Nokia Exclusives via SysApp Pusher (also, more apps in store!).
I think you've got a typo in the OEMSettings.reg file (inside the same-named archive), on one of the tweaks that's supposed to give file system via USB:
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\controlset001\services\MtpSvn]
should be
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\controlset001\services\MtpSvc]
unless it's supposed to control the Media Transfer Protocol Subversion
Will this work with Huawei Ascend W1-U00 from Globe PH plan?
Hi.
My phone was given to me by my mother who received it with her Globe (a Philippine mobile network service provider) postpaid plan (which unusually uses prepaid services). I've been frustrated with this phone's storage becoming full very easily even though I only have very few apps (except for Spider-Man Unlimited which downloaded a 200-MB DLC) installed and I don't put any files in the phone storage. Since Huawei seemingly abandoned their Windows phones, there's no hope of us getting any update so we're stuck with the stock WP8 update 1. Will this custom ROM work with this particular W1-U00? Does anyone know where I can get a stock ROM for this particular phone?
Name: Windows Phone
Model: HUAWEI W1-U00
Software: Windows Phone 8.0
Screen Resolution: 480x800
OS version: 8.0.10211.204
Firmware revision number: 1030.5614.29400.20500
Hardware revision number: HD1U8835M Ver.B
Chip SOC version: 8230
WojtasXda said:
Hello everyone !
I have new W1, but this is U34 version. Anyone tried flashign this model? Acctually QPST shows error "Cookie (if present) not received.
Click to expand...
Click to collapse
I have the U34 and I've not been able to flash it. I always get the same cookie error in QPST, and handshake failure error in WP8 Flash Tool.
I hope you will be able to find the way to flash the U34.
You need install Windows 7, Use Qemu or Vmware. Drivers from package with QPST doesnt works in W8.
Click to expand...
Click to collapse
That's not true at all. QPST works perfectly fine on Windows 8. The only issue is if you're running a x64 OS, in which case you need to run the QPST programs as admin.
Is this ROM only in English language?
Problems with Flashing
Hello!
At First thanks for the good work. I will donate it, if i getting it work for me.
I got some Problems with flashing.
1) With Flash Tool:
Diag Setting is on, Phone is resetted and with the Flashtool i get the "Firmware Handshake Fail"-Error.
2) With QPST i can get into Download Mode (Qualcomm ... 9008) but then it shows me a "Cookie not received"-Error.
I tried the Flashtool in Downloadmode but that doesnt recognize my device.
My PC-Config:
Windows 7 Ultimate 64-Bit
Intel i5 Notebook
My Handy-FW:
Huawei W1-U00 Simlock Free
OS Version: 8.10.14203.306 Developer Preview
Thank you very much!
Edit:
I got the Problem. It only works for me without Diag Settings and only with QPST.
The folder from the Repair Bootloader was: W1-U00 Repair bootloader/flashing/
and i only copied the "flashing" folder. Now no "Cookie"-Error.
Hope this helps someone....
Step 2 error
I finish step 1. Flash custom ROM with QPST (Windows 8.1 x64).
Phone in mass-storage mode (all disk available).
Qualcomm MMC Storage USB Device present in Device manager.
When run WP8CRUU get error: Cannot open device "Qualcomm MMC Storage USB Device" Error 5 .
Whats wrong?
Problem solved:
With phone connected as mass storage reinstall Qualcomm USB drivers!
Lag issue on the scroll
Hi @WojtasXda, I installed this wonderful ROM yesterday and everything is working perfectly THANK YOU SO MUCH <3
but when I scroll something with the finger always placed in the screen it lags a bit.
Huawei Ascend W1-U00
If you could help me to find a fix I thank
Error 109 on WP8CRUU.exe
Does v1.10 require v1.00 flashed first? I'm getting an error 109 (Cannot open device Qualcomm MMC Storage USB Device) when I run WP8CRUU.exe. My phone's (W1-U00) already in mass storage mode.
Now, I'm getting an error 5 (Cannot open device Qualcomm MMC Storage USB Device).
Can anyone please help me with this? I was able to flash the ROM with mass storage mode capability and set my phone to mass storage mode. Now, I can't flash the custom ROM because of this error. I don't think I missed anything. I'm running this on a Windows 7 Ultimate 64-bit. I didn't install MS Visual Studio 2013 since it requires Windows 8.1. I did install the Qualcomm USB drivers, simpleio, and QPST. I have MS Visual C++ 2005, 2008, and 2012 (all 32-bit) installed.
Arhy's workaround didn't work for me, by the way.
personal settings/data
Hi everybody,
is there a possibility to flash the rom and still keeping the wp8 personal settings (like contacts, certificates, calendar arrangements,...)
Or is it possible to do a "backup" of personal data in wp8 and do restore in wp8.1 ?
Any hints welcome.
BTW
Thanks for the rom and the hard work...
blonder_andi said:
Hi everybody,
is there a possibility to flash the rom and still keeping the wp8 personal settings (like contacts, certificates, calendar arrangements,...)
Or is it possible to do a "backup" of personal data in wp8 and do restore in wp8.1 ?
Any hints welcome.
BTW
Thanks for the rom and the hard work...
Click to expand...
Click to collapse
Try going to Settings -> backup.
tempname said:
Try going to Settings -> backup.
Click to expand...
Click to collapse
Thanks for the reply...
As far as is can see you just can backup fotos, messages, and IE-settings.
(no contacts, calender-information, certificates,...)
Is there another way to get at least my contacts from WP8 to WP8.1?
An additional question:
Is it possible to get back to WP8 after flashing the WP8.1 rom?
Any hints welcome
best regards
andi
install HUAWEI Ascend W1-U00 | v1.10
Hi, i try to install these rom.
To install that i do this steps:
1) Enter Qualcomm emergency mode
2) Click Start>All Application>QPST>QPST Configuration and configure phone
3) Start>All Application>QPST>eMMC Software Download，Click “Load Build Contents…” Select contents.xml in unrared W1-U00(C00)Repair bootloader.rar，Check "Program Boot Loaders",UnCheck "Program MMC device", Click Download
4) After complete, the port will change into Qualcomm HS-USB Diagnostics 9006
5) UnCheck Program boot loaders，Check Program MMC device，Select Qualcomm MMC port，Click Download again.
6) Wait for it to complete, disconnect phone.
7) Press and hold "vol -" then also press and hold Power button and connect the phone to the computer, now the device manager will display WP8 UEFI USB SimpleI/O Port.
8) Run Flash Tool , select ROM file / Config XML and click "Scan && Download".
9) When phone displays 100%, and the inscription OK. The process of flashing rom is complete. Now you need Reset the phone (press power button on 15 sec or remove battery). Flash tool displays information about the bad file FFU, just ignore it
10) Run device in mass storage mode
11) Run WP8CRUU.exe... BUT
No instrunction, only black console. when i close the console the copy begin.. but stop at 45% with "Error: cannot write 5 file. Error 5"
Suggestion?
SOLVED: must be waiting on the black console
I can not find Data\\PROGRAMS\\WINDOWSAPP directory，how can I get full FS access ？
I read many posts and articles the past few hours and realized a few things, would you correct me if they are wrong please.
My phone:
Pixel 4XL, adb reboot recovery gives "no command" it would seem it might have been rooted at some point before I bought it, but now the bootloader is locked and no custom recovery is on it.
Can I not recover data without root?
Saw few articles mention `adb pull' and `dd` to copy block device, which I can't do with no root.
Is it possible to just install busybox with adb and be able to copy block device?
As per this article https://www.andreafortuna.org/2018/...imaging-android-file-system-using-adb-and-dd/
I might have to wait a bit for TWRP as I did upgrade to Android 11 and it seems it is only supports Android 10 at the moment.
In order to put TWRP on my phone I probably need to unlock the bootloader and would that mean lose all user data? Then I really have no hopes of recovering the audio file I'm looking for as then I couldn't decrypt it?
I know the file's mount point and can figure out which block device it was on, but wouldn't the encryption get lost if android was wiped?
Is there a way to get TWRP without factory restore phone, or busybox or something that will help get block devices out.
Someone mentioned that these dm block devices are decrypted, are they? I will attach a screen shot with list of my block devs.
Thanks for any help or pointer, I can't be destroying this phone as I have money on it and other stuff needed for traveling, so I don't even feel like trying to install busybox to see if adb pull would work, and others mentioned if trying to get block dev off the phone while partition is mounted might lose some data, so they advised using TWRP while partition is unmounted and then copy it's image.
I also found this but I would need root, he mentions 'temporary root' is that even a thing?
Extract Android Userdata Partition for Recovery and Forensics - Root101 | Fundamentals of Linux Administration
Open Source and Linux. Guides and Ideas for Designing Highly Available and Scalable Production Environments
www.root101.net
@GogoAkira - Your long, rambling post is very confusing, and you do not clearly state what it is you are trying to do or the current state of your phone. I want to start by saying that if you have not done so already, you need to be on the very latest version of the adb/fastboot binaries. If the phone is working fine and you can access all your files, there are some non-root ways to back up almost all of your data, but you're NOT going to get anything near a nandroid backup. If your phone is working fine on 11 (why would you not be on 12?) you can also enable usb debugging from within the developer options menu and then use it from the RECOVERY mode. You cannot use adb from your PC without first enabling adb debugging. I say this because you claim "adb reboot recovery" won't work. Of course it won't work. You cannot access adb in the FASTBOOT mode. Probably the first thing you need to confirm is that you have enabled USB DEBUGGING and whether or not your ALLOW OEM UNLOCKING toggle can be set to yes. Whether or not you can do this will tell us alot. If it is greyed out in the off position your bootloader is a) currently locked, and b) probably will not be able to be unlocked. Knowing that, then clearly state what it is you are trying to accomplish and people will try to help.
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
laticola said:
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
Click to expand...
Click to collapse
You should download the official Google drivers.
elong7681 said:
You should download the official Google drivers.
Click to expand...
Click to collapse
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Which version of platform-tools do you have? You should only be using v33.03. I would also encourage you to use the Pixel Flasher Thread 'PixelFlasher for Google Pixel 7 Support Thread.' https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-support-thread.4505289/
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
I suggest you follow the advice I gave and the other member ended up doing quoted below from another thread (his experience is fairly similar to yours and/or achieving the same things would get to the same end result -- might be worth reading through the whole thing) -- it seemed to work out for him...
simplepinoi177 said:
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Click to expand...
Click to collapse
GodieDan said:
SOLVED! thanks especially to @simplepinoi177 for cracking the case!
In case someone has this same problem in the future, here's the solution:
1. Open device manager and locate the misbehaving driver. If it's not obvious, plug and unplug the USB cable and watch for the appearing and disappearing entry.
2. Right-click the driver > click properties from the drop-down menu > select the driver tab > driver details
3. To be safe, use the snipping tool or something to take a picture of the file directories. Before you change anything in a system file it's always good to keep a record of how things were, but also you'll need to know the directories for the next step.
4. Unplug the device from the computer. As the directory list vanishes, use the screenshot to locate the .dll files.
5. Again to be safe, don't just delete the .dll files; instead just cut and paste into a backup folder somewhere. Also save the screenshot of the directories in the same folder, so you will know where to put them back if you need to. I didn't, and who knows, maybe I could be overcautious, but best practices and whatnot
6. Open device manager and again plug your android in. This time the driver will probably have a different name. Locate it as you did in step 1.
7. Right-click and select "uninstall device." Tick the box and say OK
8. Unplug the phone and reboot the phone and the computer both
9. Plug it back in
I have also determined the cause of my problem: Drive Booster, a program designed to automatically update drivers. It's not an unsafe program, but it is bad at installing the correct driver. I uninstalled it.
Thanks again!
Click to expand...
Click to collapse
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Why do you think fastboot and recovery are the same? I haven't been in recovery for a bit but fastboot is available once connected to the computer but is recovery mode supposed to as well? Don't make me go into recovery mode please. But I thought recovery mode was device only.
I'm using platform tools v34.0.1, and I worked through the steps simplepinoi177 suggested for the drivers. I then discovered that my problem was something very basic: I was mistakenly using files for a Pixel 7 Pro instead of a Pixel 7 (my actual device). Once I flashed the correct boot, dbto, and recovery for my device, I was fine.
Apologies for the error, and thanks so much for the help. You all rock! And I will read up on Pixel Flasher.