Database Info

[Q] How to Root the Samsung Galaxy Prevail?

I am a c++ programmer by trade who is just now looking into android phones not only for communication but also for development. I picked up the Samsung Galaxy from Boost Mobile in order to first learn how to root, flash ROMs, and then get into dev.
My first goal is to root the phone so i can use it as a wifi hotspot. I first tried to download quick settings to see if i could get the wifi hopspot that way. I can see the hidden option for wifi hotspot but everytime I press it to turn it on, the phone disables the wifi totally. I then tried z4root, not root. I tried gingerbreak and it did not work. I would try to use superoneclick but cannot find usb drivers that will work with the galaxy prevail while its in usb debugging mode.
Any advice on how to get this phone rooted would great. Can you also list the prevail as one of the device supported on this site to spur development?

Not sure if you've come across the Prevail source code, the file name is SPH-M820_OpenSource_Froyo.zip
I can not post an actual link because I'm new to this site, but you can find the file here:
opensource dot samsung dot com/reception/reception_main.do?method=reception_search&searchValue=m820
replace "dots" with a period

I have not been able to get mine rooted either, but I did find these drivers seem to work for the phone with win7 and xp.
http://dl.dropbox.com/u/12826399/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe

Try Z4root app I think this might work considering there arent any nam locks on this phone go to 4 shared and look for the apk files as this app is no longer available in the market! I have used this app on the following devices, htc hero, sprint zio, samsung moment, droid 1, droid 2, &droid global!

I tried Z4Root it did not work.

recovery mode
recovery mode is vol up + power
says
Android system recovery (3e)
EATH /data/update_sucess
E:Update logfile dose not exsist
#MANUAL MODE#
navigate with vol keys and camera button to select

z4 root and super one click
i tried z4 and the app closed at acquiring root shell
super one click also failed with psneuter and ginger break
fails at running psneuter and at running gingerbreak
also fail with shell root in same way

unrevoked
ps the unrevoked roots just do not detect the phone

odd recover style screen
if you hold down vol + and vol - and camera then tap power a screen comes up that starts with little kernel
vol - and camera makes the phne show "downloading..."
this is shown in windows as "samsung usb compsite device"
and "samsung mobile modem"

on linux
dmesg output of the "downloading..." screen
[ 77.031415] usb 1-1: USB disconnect, address 2
[ 84.590135] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 84.748548] cdc_acm 1-1:2.0: This device cannot do calls on its own. It is not a modem.
[ 84.748762] cdc_acm 1-1:2.0: ttyACM0: USB ACM device
********-laptop:~$

i have tried all known roots to my knowledge: z4 (rageagainstthecage), psneuter, and gingerbreak. none work. so im with you, out of luck.

same here i tired a bunch and no luck

I've been trying too, no luck at all, been at it since last Friday, but my knowledge is not nearly as good as most of you, so I assumed I just didn't know what I was doing.

I tell ya, I'd love to see root on this thing. Sweet little device. Greatly appreciate all who are working on this task

I have not found a way to root this phone but i did accomplish USB tethering. Install Samsung Kies (for usb driver for prevail), install PDAnet on computer and phone, and away you go. I am looking for a windows 7 bluetooth driver for the prevail that way i could tether via bluetooth DUN. Does anyone have any success finding a prevail bluetooth windows driver?

how to root
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.

themonkeymixer said:
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.
Click to expand...
Click to collapse
I wish google could help for that lol. I want to move my apps from the internal memory onto a sd. 164mb internal memory come the **** on

Any1 root this thing yet??????????

Same experience here, z4root required phone reboot as it kept setting off the vibrate function (permanent root) and eventually locked up the phone. z4root temporary root didn't work either. SuperOneClick failed as well with both exploits and locked up on Windows 7 x64 while running exploits. Can't find any information on Google. However, I am a 4th year Software Engineering student and would be willing to work with others to find a fix.
The Samsung Galaxy Prevail is a pretty cool little phone for the money and worth the exploitation effort. For those interested in working on this issue with me know that I am both a Windows (7 x64) and Linux (Slackware x64) user with a Java programming background. Look me up (email) on my profile.

From what I understand... We'd have to set up a rom manipulation environment (cooker?). Unfortunately the only tutorial I can find is the one for manipulating HTC roms. I'm not experienced enough to know if it could be used for all Android roms and too much of a chicken to try it out and risk bricking my phone.
Once the rom manipulation environment is set up you can go and add root support, take out unwanted apps, etc.
I'd also be willing to put in some effort into learning this if someone is willing to put in some time to show me the ropes... or point me in the right direction.

INTF2 Driver INSTALL---ETS---VPST | For You Unlockers

INTF2 Driver / ETS / VPST
Here is missing INTF2 Driver / the hard to find programming tools all in one spot!
I have experimented for a while and found this driver. I remote flash alot of devices but even though I now obtained this missing driver, it is still not reading in full DIAG MODE no matter what I choose after ENABLING the HIDDEN MENU *#22745927 - and DIAG MODE OPTIONS **87284.
Samsung has made this missing driver a complete hidden secret right in the default driver package!
Hoping others that are trying to flash this device to other CDMA Carriers can help finish this project as there are no resources available yet.
Here is the steps to get that driver installed properly:
1) Leaving your device UNPLUGGED, Install the SAMSUNG USB DRIVER FOR MOBILE PHONES here: SAMSUNG_USB_Driver_for_Mobile_Phones_15160.exe - 14.07 MB
2) Plug your phone into your PC
3) Dial *#22745927 to enable the hidden menu, then tap OK. (If ever asks for a code, it is 000000)
4) Dial **87284 And under UART select PDA / Under USB Select CDMA MODEM
5) Open your Device Manager on your PC and verify you are still missing the INTF2 Driver
6) Right Click that missing driver notification and select UPDATE DRIVER
7) Choose BROWSE MY COMPUTER FOR DRIVER SOFTWARE option (NOT THE AUTO OPTION! windows won't find it)
8) Select LET ME PICK A LIST OF DEVICE DRIVERS ON MY COMPUTER
9) wait for the driver MANUFACTURER list to show up results and select SAMSUNG
10) Under MODELS select SAMSUNG HSP PLUS MODEM DRIVER
11) Hit NEXT and OK to install
12) Verify Driver successfully installed. You will see it is Under MODEMS in your Device Manager with its own assigned PORT.
****NOW THAT I HELPED YOU PLEASE REPLY HOW TO GET OUR CDMA WORKSHOP / ETS / VPST / ETC TO READ THIS DEVICE IN DIAG MODE SO WE CAN ALL FLASH IT TO OTHER CARRIERS! I AM SHARING LINKS TO THOSE DIFFICULT TO FIND APPS BELOW *****
NOTE: Page Plus Cellular has an OPEN HANDSET POLICY in which means they allow any device that can be possible flashed into their network. Making all this perfectly legal
"All we need is the very final step to get this thing to read on any of those flashing software listed above...."
Yes we now own this device, the Evo 3D, and the Evo 4G We will be developing Roms for this device soon!
To Bypass the Activation Screen:
1) Press the emergency call button.
2) Then dial *#83786633
"Soft Keys Now Enabled"
3) Press the home key.​
Other steps Attempted for PC Diag Mode:
1) Remove SIM Card, turn on the phone.
2) Connect the phone to PC, Install VIA Telecom USB Driver.
3) Dial **87284, choose USB > CDMA Modem
4) While the phone still connected to PC, Dial **33284 and then
go to ETS Channel. If it's already on USB, change it to DPRAM
and then back to USB.
5) Dial **583, choose Enable CDMA Mode.​
Flash / Unlock Programming Tools:
VPST: VPST_4.4.16_1_.msi - 25.77 MB
ETS: ETS(8.5.17.0)_1_.exe - 20.26 MB
**A Very Helpfull Post by autoprime & dexter35803: http://forum.xda-developers.com/showthread.php?t=1696621

What can be achieved with this?

Re: INTF2 Driver INSTALL---FINALLY!!!!
Yeah ditto... Explain what this means to us?
Sent from my SCH-I510 using xda app-developers app

Purpose of a missing PC USB driver
chefthomas99 said:
Yeah ditto... Explain what this means to us?
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I have worked hard trying to flash this device to other carriers. If you are not looking to get out of Verizon than this does nothing for you. No one is sharing at all how to flash this phone to Page Plus / Cricket Wireless/ etc meaning lack of open source unlock support on this device compared to the Galaxy S3 / Note 2/ etc. This Post shows 1 step closer to flashing this device to another carrier (All drivers should be obtainable). If someone knows how to flash to Other Carriers using this driver, please reply and help others. I can do many device except this one. If you Google this, you will find no answers to even obtaining this driver as I have looked myself (People saying not possible cause it is a Via Chipset and all). I may be in the wrong section and possible need to be in the Q&A. Not sure... If I need to move this Post, please let me know. Thanks!

This is pretty sweet. I'm sure there are at least a few folks out there who would find this helpful.

There's some sort of thread on here by the name of something like "QPST instructions?" but my search returns nothing.
Sent from my SCH-I510 using xda premium

kvswim said:
There's some sort of thread on here by the name of something like "QPST instructions?" but my search returns nothing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Yep. Unfortunately QPST won't work on this device. We use it on all other devices but this one has a Via Chipset. QPST only works on QUALCOMM chips like Galaxy S3, Note2, Evo, etc... I really appreciate you inputs! This post is to hopefully help all in this work-in progress.
Sent from HTC Evo running AlienMOD Series III Beta (Sony X10 spoof) using xda app-developers app

I've succesfully flashed a Droid Charge to my local carrier, but no Data yet.. Voice only. All you have to do is flash Sprint Galaxy Nexus CDMA Radio via odin, reprogram the phone using ETS, and you have to call *583 on every reboot and then choose CDMA Mode ( ..or CDMA Only, I forgot )
This is the radio :
Sprint Galaxy Nexus FC12 Radio
and this is proof :
http://www.youtube.com/watch?v=X6TlHwZTpYU
More information :
http://forum.xda-developers.com/showthread.php?t=1696621
Good luck

robbiejobs said:
I've succesfully flashed a Droid Charge to my local carrier, but no Data yet.. Voice only. All you have to do is flash Sprint Galaxy Nexus CDMA Radio via odin, reprogram the phone using ETS, and you have to call *583 on every reboot and then choose CDMA Mode ( ..or CDMA Only, I forgot )
This is the radio :
Sprint Galaxy Nexus FC12 Radio
and this is proof :
http://www.youtube.com/watch?v=X6TlHwZTpYU
More information :
http://forum.xda-developers.com/showthread.php?t=1696621
Good luck
Click to expand...
Click to collapse
Cool! I am trying it right now Will post results

robbiejobs said:
I've succesfully flashed a Droid Charge to my local carrier, but no Data yet.. Voice only. All you have to do is flash Sprint Galaxy Nexus CDMA Radio via odin, reprogram the phone using ETS, and you have to call *583 on every reboot and then choose CDMA Mode ( ..or CDMA Only, I forgot )
This is the radio :
Sprint Galaxy Nexus FC12 Radio
and this is proof :
http://www.youtube.com/watch?v=X6TlHwZTpYU
More information :
http://forum.xda-developers.com/showthread.php?t=1696621
Good luck
Click to expand...
Click to collapse
Would this work in Samsung Galaxy S Aviator R930 (it's the same phone, this is US Cellular Droid Charge Version) ???
I was able to get to the ETS Channel set up, and changed it to USB, DPRAM.
I also did the the UART and USB changed to PDA and MODEL, respectively.
Tried both in MODEM too.
But neither option allowed me to read the phone on ETS or VPST.
CWS/QPST doesnt work either.
I am able to change the MIN, SID, etc. due to a service menu ##8778#, but havent been abe to flash the PRL.
Regards,
JB

Here is the intf2 at diagnostic port driver
This is a better matched driver for those of you who need it. also attached sprint ga02 cdma radio that i edited in hex editor. you will now see I515fk02 in bootloader,about phone and in ets.

I think your PC is trying to install these drivers because you have 'Fast Charge' enabled.

AJ Bryant said:
I think your PC is trying to install these drivers because you have 'Fast Charge' enabled.
Click to expand...
Click to collapse
...interesting thread...
I don't want to be "that guy" but...
I sorta doubt that a custom kernel with fast charge support
...or the script to enable it below...
has much to do with the USB drivers as detailed by the OP.
Code:
#!/system/bin/sh
#Script to activate force_fast_charge on boot via init.d
echo "1" > /sys/kernel/fast_charge/force_fast_charge
...correct me if I have misspoken...

I'm sure that's the reason..
jheide44 said:
...interesting thread...
I don't want to be "that guy" but...
I sorta doubt that a custom kernel with fast charge support
...or the script to enable it below...
has much to do with the USB drivers as detailed by the OP.
Code:
#!/system/bin/sh
#Script to activate force_fast_charge on boot via init.d
echo "1" > /sys/kernel/fast_charge/force_fast_charge
...correct me if I have misspoken...
Click to expand...
Click to collapse

Need help

I am a new comer in this site as well as this forum, looking for a person who can help me for the followings
1. unlocking
2. user password cracking (incase forget)
3. Installation of a new software
4. How to Flash.
I have NCK box with 16 cables. The box is registered but I have not yet use it. I am using windows 8 however, I prefer windows XP if possible as xp is installed in my laptop which will not shutdown immediately in case power failure.
Finally I am willing to donate who can help me or guide me in this field. Please reply.
Regards
Thohhir

[Completed] CUBOT X6 dead screen, no USB debug enabled, Stock ROM, no root

Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !

SparrowCZ said:
Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist and there is no forum specifically for the Cubot devices at this time but I see that you have already posted an identical message in the General Forum at http://forum.xda-developers.com/showthread.php?t=2728355 which is a reasonable place to start where members familiar with your device might be able to advise you. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=cubot x6 which might be worth reviewing. Since your device is relatively uncommon, please be patient and give the experts there plenty of time to respond.
Good luck!
This thread is closed.

Question Can't connect Pixel 7 Pro to PC (Windows 11) [SOLVED]

The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!

Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.

jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..

GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?

schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?

GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.

Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not

yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?

Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.

GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.

schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".

yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
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.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...

schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse

We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery

I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.

.

H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?

Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
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.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me

GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...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.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!

simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?