Related
preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!
-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-
Consider yourself... sticky
Thank you Olinex. Great WORK
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.
Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.
Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.
What specific error message(s) are you getting?
Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.
You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.
but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.
Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.
That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!
thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.
Have you tried taking out the battery of the phone, reinserting it and turning it back on?
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.
I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?
hey,
well obviously I'm a newbie here and i needed to know if anyone can help me find a download link for windows mobile?it crashed on my Siemens pocketloox and i lost my cd so i've been looking everywhere for a downloadable version but i can't find one.
thanks in advance.
Dude a pda is not like a pc where you can freely install any OS you wish... The official Windows Mobile versions must be provided by your manufacturer (there isn't a Universal version per say... if you try to flash the version of another device you'll kill your phone). You may try to check Fujitsu-Siemens homepage for an official ROM update or contact them if needed
Over the net you may find ROMs for pda but bare in mind these are device specific and your device usually needs to be hacked in order to install unofficial versions (your device seems to be quite old... I don't believe you'll find any rom here since xda is almost HTC land).
Also what do you mean by crashed? Did you brick it (OS won't start... all you get is a black screen)? Have you tried removing/reinserting the battery and restarting?
the start menu suddenly has no icons,and neither the camera shortcut button nor the notes one are working.basically,it just opens and almost everything is disabled.
The easy solution is...
Just hardreset the device (seach here) and it will reset your device to factory defaults (it's like a format+reinstall)... Problem solved.
Just make sure you backup your data (photos, contacts, messages...) before because everything will be erased
thanks a lot man it worked.
hi.
I'v got loox n560 that was upgraded to WM6.1-6.5 servel times without any problem.
the last time i did update, i did it accidentally with a bad firmware file(uncompleted download).since then, the device wont boot(just a white screen).and the pc wont recognize it.
any way to save it? or i made myself a nice paper weight?
thanks.
I think there was a way to put the N560 in bootloader mode by pushing some keys and soft-reset hole manually (the "monkey grip" it was called or something similar...) and with the file of the rom to be flashed in a SD card... perhaps you can google for information on this ancient -and more unsure that the cable one- flashing mode. Worth to try it better than have a paperweight...
Good luck!
I give you more information (shame that FIRSTLOOX information is not there anymore)
For manual bootloader mode: press On-Off button + left side button (voice recording) + stylus soft reset (for some seconds). Keep pressed On-Off and recording untill the dolphins appear.
I can't find references to flash from SD card. Anyway, for incomplete flashing, Newplowe gives this procedure:
"You should close process "wcescomm.exe" on PC in task manager. Then hold button record, power and puch reset after that you will come in boot loader. Run the program mtty.1.42 and select usb connect. If You will see the any error just start again mtty. Put command l c:\os_213u.nbf (You should put correct flash file in c:\ or use correct path to os_213u.nbf, l - like L but small). When it will done You should start PocketLOOX5xxFlashTool.exe and flash you PDA."
I got this reference from "http://forum.xda-developers.com/showthread.php?t=429148&highlight=flash+n560+card".
Good luck anyway.
this is very interesting...
i was able to put the device into boot loader mode and ran the command "L c:\os_213u.nbf" ("l" didnt work, but L did).
it did something to the device, a progress bar till the end of the screen.but the device didnt reboot.when i try to run POCKETFLASH program it couldnt connect to the device.
i runing windows 7, so i guess it the problem(ACTIVE SYNC is a XP PROGRAM).
i'll try installing XP on another computer and try this again.
thansks.
almost...
i have installed Windows XP just for this, and everything seems to go well, i connect with MTTY, put the l c:\os_213u.nbf command and the device respond.
the next stage i to flash with PocketLOOXN560FlashTool.
when i start it, i receive connection error, and then i go to recovery mode.the program try to communicate with the device, but i get at the end error that the ROM language is different than the language on the device.it says "(ENGLISH)" and there are also empty
()
Click to expand...
Click to collapse
at the end.
i doubled checked this with the original WM5 English rom, and its the same.
is there a way to change the language with MTTY?
any other ideas? its a shame to stop now after i can get a response from the device...
thanks.
The only idea I have is to check if after the failed flashing your N560 is still an "english" one. Perhaps the defective rom has changed the language of your device to something else...
If your device respond to communication with the XP computer, perhaps you could make a rom dump (in newplowe's page you can got tools for doing that) and check in the dump file with an hex editor which language actually has. You can always check newplowe's blog and forum (with google translator ), or ask him
Sorry i didnt post an update.
i have fixed the rom language.it had a gibberish mark at the end of the ENGLISH, after i have fixed that, .the device was flashed correctly and its working!
thanks for thelp guys
Hi,
I have a big problem.
So I can`t bypass the Android activation screen. I don`t have a data plan and I`m following this guide http://theunlockr.com/2010/01/10/how-to-activate-the-g1-without-a-data-plan-or-sim-card/
I DID IT ONCE BUT I CAN`T DO IT SECOND TIME.
So I`m following this guide http://forum.xda-developers.com/showthread.php?t=1301379 and everything was perfect until I get to this point (II. /7. Go and download a file manager from the android market (I suggest LINDA FILE MANAGER)) I couldn`t download any app, "Download unsecessful". I read about this problem tried out a few methods but they didn`t seem to work. I read that Factory reset could work so I did a Factory Reset... and now it asks me again to activate but I can`t do it. I do exactly step by step but it`s just not possible.
The only difference is that now i have a "Change Language" button, the first time when I had absolutely no problem (from the first time I did it) with the bypass (activating the WiFi) the buttons wasn`t there. I`ve read that it works only on RC29, this guide on II. 7. am I not on RC29? Because everything worked perfectly until this point.
The other problem is that I can`t get it to RC29 if it isn`t because when I connect it vie USB it doesn`t recognises the SD Cards, only the phone itself. This means that I just Can`t upload the files and re-do the steps before II.7 from the guide.
I`ll be really grateful to any help! I can`t use my phone at all at this point.
Thanks,
Boby!
Just upgrade your phone...
This is not possible for me because when I connect the phone via the USB cable the SD card doesn`t show as Disk Device.. it doesn`t show at all.
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?