Related
I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.
did you try re-installing the drivers after you plugged in the USB it fastboot? i had a problem similar to this a long time ago, and the drivers were only loading in normal mode when android was booted up for adb and all that good sh*t. i booted into fastboot, plugged in the usb cable, and installed the drivers while at the fastboot screen. hope this helps any
I think I have. I kind of remember uninstalling the drivers, restarting my computer, plugging it in (while in fastboot) and installing the drivers when the "found new hardware" screen popped up. Guess I will try it again and report back.
Thanks.
I fixed it...
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
aron4588 said:
This is updated with the lastest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Goto the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
Original G1 Bootloader/Splash Image
Click to expand...
Click to collapse
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.
NICE!!! I tried a whole bunch of solutions as well. Finally, I stumbled on yours, and it worked! Hell yeah! I think maybe adding fastboot folder to the path of system variables may have done the trick, too.
Thanks!!!
ccunningham83 said:
I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.
Click to expand...
Click to collapse
best advice i got was load up your phone is fastboot connected to pc...run the same commands in cmd but go through SDK/Tools and run fastboot from there once your in tools...skip putting it to your desktop...that didn't work for me
Hey guys, I have a problem, the driver is installed, but I can't see the device when I go to the cmd. I need help please!
Also, since my recovery is dead, and my cyanogen rom is dead, I have no way to revive my phone... can anybody help me please?
99.9% of the problems with getting fastboot to work are actually problems with windoze and incorrect_drivers/driver_conflicts/windoze_is_retarded.
Best thing to do is use Linux. No special drivers needed.
And this is not to start a linux is better than windoze fight (even if it *is* better )... it is simply a matter of this; android *is* linux, it was developed with linux, that's what all the platform developers use, and simply put, it is absolutely and fully compatible, so when all else fails, that is what you should use as well.
Option a) grab latest fedora livecd and boot off that,
Option b) grab latest fedora installdvd and install it to something and boot it up,
Then:
copy the fastboot executable into any directory (download from developer.htc.com),
connect USB,
put phone in fastboot mode,
./fastboot flash {partition} {image}
And it'll "just work".
Note: http://www.fedoraproject.org/en/get-fedora
omg. countless hours spent on trying to do this. and all i had to do was to use the fastboot in the sdk? thanks youuuuuuuuuuuuuuuuuuuu!
ccunningham83 said:
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.
Click to expand...
Click to collapse
I recently upgraded my G1 to the cyanogenmod 2.1 ROM and everything went fine untill i went to the market and installed a program called ROM manager. while i was using ROM manager it had an option, i cant remember what its name was, that said it fixes FC's if needed. Well i was getting those in ROM manager so i clicked it. It did a bunch of stuff and then suddenly tossed an error at me. Next thing i know im getting LOTS of FC's and when i rebooted my phone im suddenly stuck staring at the G1 boot screen and thats where it stays......indefinetly.
I cant get into recovery mode, already tried that. And so far the only thing(that i know of) that i can do is get into fastboot. Does anyone know how i can fix this? Its gotta be software related from whatever that ROM Manager program did to my permissions. But now im basically bricked and cant do anything.
My storage card still has all of the ROM's and files from when i flashed last but i dont know if or how i can use that to re-flash my phone again and start over.
Any suggestions?
I had a similar issue just yesterday. Dowloaded rom manager from the marketplace - attempted to flash recovery - pulled an error and ended up on the G1 screen. Could not get into recovery, but fastboot was available.
I followed these instructions
( reboot holding camera button, connect usb and press back button )
on pc
HTML Code:
fastboot erase system -w
fastboot flash recovery <recovery.img>where <recovery.img> is the full path to the recovery you want to flash
I had to do a full erase in fastboot - that is the first line of text above, I then flashed my recovery.img again - that is the second line of text above (I placed my recovery.img file directly in the adb folder - so it easy to find )
Once I was able to get back into recovery - I restored my last back-up, and the phone booted once again.
If you do not have any backups - I am not aware of the next step. Hopefully someone with more experience can direct you accordingly
Good luck
How is it that you send the commands? I plug in my USB, then hit back and it says FASTBOOT USB but how do i input the HTML codes to get it to do anything?
Do i make an HTML file on the pc and upload it, if so, how? I understand all of it except how to get the commands into it.
Well that and what the full path will be for the recovery.img.
well i feel like a total moron !!! lol
I had been being a script kiddie for the last few years and forgot my roots. I got it figured out and got the commands sent to fastboot in a CMD prompt.
Ugh, i gotta stop using google so much and finding all the easy ways out of things that others have already written.
Thanks for the help, much appreciated and worked a treat. I flashed everything and its working great again
So, I've been banging my head against the wall for a few days now, and though I usually don't post questions (90% of the time I find the answer somewhere on the interwebs) I'm a bit stuck.
So I'm trying to get used to creating my own boot images, and have found the article android-dls article among others very helpful in understanding everything (would post the link, but can't yet)
It was easy enough to find the boot image on the Fire, and I have been using the unpack_bootimg.pl to unpack the boot image, then make the necessary changes, and mkbootfs to pack up the ramdisk. Everything goes swimmingly.
The problem arises when using fastboot to boot the new boot image using the command below:
fastboot boot boot.img-kernel.gz boot.img-ramdisk.cpio.gz
It loads it to the Fire fine, but never boots. My guess is it has something to do with offsets, but to be honest, it's a bit of a blind guess. I have also attempted to repackage the boot image into a testboot.img with the same results. I've even tried just unpacking an re-packing the known good image thats already there, without changes.
Also, not sure if this is relevant information, but mkbootfs and mkbootimg was compiled in OS X (10.6.8 for those that care) directly from the android 4.0.3 source.
Does any one have any suggestions on what to try next? Or even better, any additional articles, threads, etc. that I may have missed. Any help would be appreciated.
Oh, forgot to mention, I also have the firefirefire bootloader installed (1.2) and TWRP. Don't think it matters though.
This may not apply as I do not own a KF...
Have you ever successfully used fastboot in that manner with the KF? Any kernel I mean...
I was never able to use fastboot like that with my inspire 4g... but could use it to flash the very same image quite successfully.
Dont know if that helps or not...
I've found that those scripts do not play nicely with the Fire's boot images for whatever reason, and repacking with them renders all of my images unbootable as well. I've ended up using dsixda's ROM kitchen just for the boot image scripts because those work fine. I'm not entirely sure where the disconnect is on the perl scripts, but I haven't looked at them truly extensively.
Unpacking and re-packing boot images
gumbi2400,
Have you tried loading another boot.img/rom and going back to the one you have edited? I am only asking for my own stupidity. with your post it has my mind going places, well it should not go just yet in the Kindle. I am pretty sure it not much different then myself building GhostBSD. Let me know please!
Thanks,
JohninLex
Changed the Boot Logo and now stuck at boot
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
wayoung said:
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
Click to expand...
Click to collapse
you could try to get to twrp by issuing:
fastboot oem idme bootmode 5001
fastboot reboot
in the case it says <waiting for device> power off the kf by holding pwr ~20sec
power on again - at some point the command gets finished
power off and on again
once in twrp you have adb available and can copy a good file over the bad one
take care of the permissions !
or just restore a backup or flash a new rom
maybe you have to check your drivers in device manager:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Sorry it took me so long to reply, got distracted by other modding projects.
@JohninLex:
I actually tried simply unpacking and re-packing the stock image that was already on there, just to make sure I was packing it back properly, but got no love.
@eldarerathis:
I think I had stumbled across the ROM Kitchen previously, but wasn't sure if it was what I was looking for. I'm fairly new to this low level of messing with Android, I have a tad bit of experience with Linux proper, but I know things can get pretty murky. I may end up ripping the scripts apart and seeing whats actually in there. Thanks for the tip!
Life is busy right now, and I haven't gotten a chance to mess around with modding my Kindle more, may be time to start again.
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)
If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.
Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again
nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it