Develop Bugs

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

[Q] What should I do to restore my Nexus 7 (2013) to work on which I tried to root?

Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.

karsnen said:
Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
Click to expand...
Click to collapse
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.

sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
It worked. Thank you so much.
I just want to know, if you could recommend a guide for rooting the new nexus 7 on windows machine, what would that be?
Thank you once again.

Check in the stickies for detailed instructions. If you just want a simple summary:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339

sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.

tr00gle said:
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
Click to expand...
Click to collapse
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.

karsnen said:
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
Click to expand...
Click to collapse
Are the commands the same in terminal, or should I run windows in a VM to use the command line?

The only cmd in that post is flash-all
It is the same. Get into the directory and enter flash-all when you have to, in the terminal.

When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.

tr00gle said:
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.

sfhub said:
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
Click to expand...
Click to collapse
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp

course ndighdl
tr00gle said:
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
Click to expand...
Click to collapse
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.

tr00gle said:
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
Click to expand...
Click to collapse
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194

sfhub said:
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
Click to expand...
Click to collapse
Is that link to the guide? there wasn't one on that link. I appreciate you replying this many times already, but I just need one set of steps to follow, that are clear and detailed. That's all. Do I need to use windows, mac or linux? I have a macbook pro, but I can run windows or linux in parallels if necessary. I just need to KNOW. Please.

Best custom rom for the LG G4?

Hello, I'm getting today the LG G4(H815) and Im wondering what is the best rom to install?
I've heard the battery life is not very good becuase of the LG interface, so a custom rom should fix it, and from what I've seen there's not much different between Android 5.1 and 6, so I don't really mind, what custom rom do you use, and why?
Thanks.

I'm running die latest nightly of CM 13 and in my opinion it's very good!
Everything I need for daily use just works fine.

There is no "BEST" for every body. There is only what people have found is best for them based on how they use their phone, their signal, setup, preferences, etc. They found what was best for them by reviewing all the top listed ROMs in the development section. The top list means they are the most active. Read the first few posts on each and find out what features they have and if those are the ones you are looking for. Then read the last 10 pages or so to see if anyone has any problems and how they fixed them. Then choose the one you want to try...back up your current setup, wipe all data and flash the new ROM. Give it a try and see if that is the one that is BEST for you. If not, restore your setup or try again.
Happy Flashing!

KennyG123 said:
There is no "BEST" for every body. There is only what people have found is best for them based on how they use their phone, their signal, setup, preferences, etc. They found what was best for them by reviewing all the top listed ROMs in the development section. The top list means they are the most active. Read the first few posts on each and find out what features they have and if those are the ones you are looking for. Then read the last 10 pages or so to see if anyone has any problems and how they fixed them. Then choose the one you want to try...back up your current setup, wipe all data and flash the new ROM. Give it a try and see if that is the one that is BEST for you. If not, restore your setup or try again.
Happy Flashing!
Click to expand...
Click to collapse
First thanks for the detailed comment, second, can you please remind me the order from stock new phone to flashing custom rom?(I mean, first you root the phone, then open bootloader, install TWRP, etc etc) Thanks.

I'm running CandySiX. It's very good.

msacco4 said:
First thanks for the detailed comment, second, can you please remind me the order from stock new phone to flashing custom rom?(I mean, first you root the phone, then open bootloader, install TWRP, etc etc) Thanks.
Click to expand...
Click to collapse
Assuming you have the unlockable/rootable device this thread should help you with all of that.

KennyG123 said:
Assuming you have the unlockable/rootable device this thread should help you with all of that.
Click to expand...
Click to collapse
I'm having trouble finding my "Device ID", the method mentioned there is not working, I tried downloading a few apps but its not the correct device id, not sure what to do and how to find it, any help? ;s

msacco4 said:
I'm having trouble finding my "Device ID", the method mentioned there is not working, I tried downloading a few apps but its not the correct device id, not sure what to do and how to find it, any help? ;s
Click to expand...
Click to collapse
Go into your app drawer. Go to Settings then to the very bottom for device info, then something that sounds like Hardware info. You will find your IMEI number in there.

KennyG123 said:
Go into your app drawer. Go to Settings then to the very bottom for device info, then something that sounds like Hardware info. You will find your IMEI number in there.
Click to expand...
Click to collapse
Its not IMEI number, its device id, its 64 notes long..

msacco4 said:
Its not IMEI number, its device id, its 64 notes long..
Click to expand...
Click to collapse
Oh..THAT Device ID. Here is a better explanation on how to get it if you have fastboot and ADB drivers installed and working:
http://www.androidexplained.com/lg-g4-unlock-h815-bootloader/

KennyG123 said:
Oh..THAT Device ID. Here is a better explanation on how to get it if you have fastboot and ADB drivers installed and working:
http://www.androidexplained.com/lg-g4-unlock-h815-bootloader/
Click to expand...
Click to collapse
I already tried that as well, but its not working for me, the cmd says "Device not found", but the device is connected(and the computer is recognizing the phone as well), I also tried to getting into fastboot through flashtool, but its not working as well, I tried many options, usb debugging on/off, mtp/the other one, but its not working(but the computer is recognizing the phone and I can enter the phone storage).

msacco4 said:
I already tried that as well, but its not working for me, the cmd says "Device not found", but the device is connected(and the computer is recognizing the phone as well), I also tried to getting into fastboot through flashtool, but its not working as well, I tried many options, usb debugging on/off, mtp/the other one, but its not working(but the computer is recognizing the phone and I can enter the phone storage).
Click to expand...
Click to collapse
If it says Device not found, you do not have ADB drivers properly installed. Try to download and install fresh drivers for your phone..or plug it into another port and watch the driver installation to make sure all drivers are installed. If you get a red X for ADB driver then you need to remove drivers, download updated ones and install.

On the same topic, how is the camera on other roms?
I'm assuming on all STOCK variants we have the same camera app as LG provides.
But what happens with CM13 for instance? (do we have manual controls, is the quality degraded...?)
Thanks

KennyG123 said:
If it says Device not found, you do not have ADB drivers properly installed. Try to download and install fresh drivers for your phone..or plug it into another port and watch the driver installation to make sure all drivers are installed. If you get a red X for ADB driver then you need to remove drivers, download updated ones and install.
Click to expand...
Click to collapse
I did all those, and still, for some reason it isn't working :\ not really sure what to do, is there no other way to find the Device ID?

msacco4 said:
I did all those, and still, for some reason it isn't working :\ not really sure what to do, is there no other way to find the Device ID?
Click to expand...
Click to collapse
Either way, your device will need to be recognized by ADB to unlock the bootloader. Make sure if you are using a desktop to use the USB ports in the back directly on the motherboard and not the ones in the front. Do you have any errors in device manager? Whichever error you have you need to fix that driver. With my 6P I had problems with the Google USB driver. Took me 2 hours to realize which was the problem and find one that would install somewhere on the net.

KennyG123 said:
Either way, your device will need to be recognized by ADB to unlock the bootloader. Make sure if you are using a desktop to use the USB ports in the back directly on the motherboard and not the ones in the front. Do you have any errors in device manager? Whichever error you have you need to fix that driver. With my 6P I had problems with the Google USB driver. Took me 2 hours to realize which was the problem and find one that would install somewhere on the net.
Click to expand...
Click to collapse
I actually do have a little problem, sometimes, with different time periods, but every now and then, my keyboard stops working for like 2 seconds, my computer is trying to find usb keyboard driver, it fails to update it, but the keyboard still works, don't know if it have any connection, but I'll try to do it on another computer(don't know why I didn't thought of it until now ;o)
Edit - not working on other computer as well, really don't know what to do ;\

Custom ROM's are generally good overall. CandySIX and Resurrection are both extremely good ROM's. However, where they lack seriously is the quality of sound generally from the speakers and headphones. That being said, its best to settle for a Stock based ROM. IMHO Imperium ROM is unparalleled in that department, best battery backup and of course awesome sound. It even integrates with Viper Audio very well. Its my everyday ROM at the moment. If anyone thinks differently, please do let me know. I would love to get some opinions on this.

Need To Obtain Procedure As To How To Get Into Recovery Mode

Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David

Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]

Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David

That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David

Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.

Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David

How To Guide adb doesn't discover phone but fastboot does - trying to install Lineage OS

I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.

Try fastboot commands in bootloader

yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload

Try "fastboot reboot" or "fastboot reboot bootloader"

yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.

If it's Windows your using it may be a driver issue.

yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?

johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222

heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment

johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too

heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.

bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool

heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?

i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware

heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?

johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself

can you tell me which version your phone have? IN/CN/GLOBAL/INDIA

Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above

heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America

johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos