Related
Fix Modem / Baseband JB AT&T ONLY... Sure did fix my problem!
Diagnosis for: (Random) no sound; no phone connectivity such as: WIFI; BLUETOOTH; GSM.
Can happen: Flashing wrong fw; Flash failure.
NOTE: Android SDK is required, go to your OS below and view "prerequisites" for more information...
Windows 7 methodPrerequisites: Android SDK - Tools and SDK! (install here.)
Instructions:
(1. Make a folder in the directory "C:/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "C:/qinara/" folder.
(4. Open a cmd prompt.
(5. Change Directory (CD) the cmd to your install location of Android SDK's Platform Tools (type it in to the command prompt.) to make
a command like the following example. Example: CD C:/users/YOUR-USERNAME/android/sdk/platform-tools
(6. Type the following command in...
Code:
fastboot flash modem C:/qinara/NON-HLOS.bin
(7. Wait for the modem to be sent and installed.
(8. Type the following command in...
Code:
fastboot reboot
(9. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(10. Open up your multi-tasking menu and open settings.
(11. Set "select network" to "automatic," then your done.
Ubuntu / Other Linux-distro methodPrerequisites: Android SDK - Tools only! (to install type the following cmds in terminal...)
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Instructions:
(1. Make a folder in the directory "/home/USERNAME/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "/home/USERNAME/qinara/" folder.
(4. Open a terminal.
(5. Type the following command in...
Code:
fastboot flash modem /home/USERNAME/qinara/NON-HLOS.bin
(6. Wait for the modem to be sent and installed.
(7. Type the following command in...
Code:
fastboot reboot
(8. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(9. Open up your multi-tasking menu and open settings.
(10. Set "select network" to "automatic," then your done.
Downloads
-NON-HLOS.bin
Ask any questions below... :fingers-crossed:
Kinda feels that way...but on the Linux instructions just use ~/qinara/NON-HLOS.bin instead of /home/USERNAME/qinara/NON-HLOS.bin
~/ means the users home directory
Also, and I'm gonna add this to my faq, but download the fastboot I linked, rename to moto-fastboot, place it in ~/bin and add that to $PATH in ~/.bashrc (or where ever your preferred disto prefers it to be)
My actual path line in .bashrc (the part above I'm referring to is in bold)
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/share/android/bin:/share/android/adt/sdk/tools:/share/android/adt/eclipse:/share/android/adt/sdk/platform-tools:$HOME/bin:"
For the curious, I keep all my Android stuff on its own partition (/share/android) so all I have to do is add those directories to my $PATH if I decide to disto hop. If you dualboot, you can do the same thing only set the partition as NTFS or ext2 (there's an windows ext2 driver). I disto hop about once a month.
Don't have access to my desktop right now trying to install my new ssd and put Linux mint on it. (Noticed your a Linux guy, do you like mint?) Anyways I'll be sure to add that in later. Thanks.
Sent from my MB886 using xda premium
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
help...
can you tell me its working or not cause i have some gsm problem no signal due to band change
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.430s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.720s
Oooooh Cool.....now after trying to find how to get out of the mess that created. I still dont have signal lol
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
yashrab said:
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
Click to expand...
Click to collapse
Yeah this method bricked my phone. I had to go back to stock through RSD, and lost root access. The good news is it was so easy to reacquire root thanks to Dan Rosenberg's programs.
Can I install stock though myth tool.. I think it does work just like RSD?.. Plz tell me cause I am totally noob in this part.. And I don't want to brick my phone..
Sent from my MB886 using xda premium
Moto Atrix work on any GSM carrier or.. ?
skeevydude said:
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
Click to expand...
Click to collapse
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
lonesomedove said:
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
Click to expand...
Click to collapse
You should be able to, but I'll tell ya that some users have gone through multiple places to get it unlocked since not all the unlock services have the updated unlock codes we need.
Nope
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
BackDoorNoBaby said:
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
Click to expand...
Click to collapse
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Thanks
skeevydude said:
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Click to expand...
Click to collapse
Got it. Thanks.
I'll check it out after my classes tonight and give an update.
Yup
Yup. That did it. Fixed the issue.
Back to my 4G!
Thanks again.
Anyone tried with CM10.2?
Nope. I know Cyanogenmod has issues at the moment, but I don't know if this will fix it.
Best I can say is to try it. Worst case: you reinstall the ROM. Or you can wait for a release version of CM 10 instead of a nightly.
I can say this didn't brick my phone, so you shouldn't have to worry about it. (but as always - no guarantee)
Sent from my Atrix HD using xda app-developers app
I really need help, I need something like this but for a company in Mexico. I tried this but it didn't worked.
Question if i reflash back to stock eith RSD LITE or myth tools will that fix my baseband i delete my baseband by accident
Dumb me
wcdma and lte network problem
i happen to own the mb886 the lte and wcdma used to work then i mistakenly went to change my base band to cellular (800-mhz) then the network went off so i changed it to (aus2 band (gsm-900/ dcs-1900/wcdma-850/wcdma-pcs-1900) but now am only able to get 2g or edge networks but am also in a 3g coverd area. can you guys please help me out
Greetings,
Apologies if this has been asked somewhere else before, but I haven't found it anywhere after hours of searching. I've been trying to get ADB to work on my Kindle Fire HD 7 with no success. I've downloaded many drivers and the Android SDK and Android Studio as well. After installing all different drivers, when I connect the tablet to the laptop and test fastboot connection, I get the following:
C:\android-sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
I believe this is expected when I run this command, which I guess means the fastboot cable is working and perhaps the driver too? (not sure). However, when I run the following ADB commands this is what happens:
C:\android-sdk\platform-tools>adb devices
List of devices attached
(this comes empty, no result)
C:\android-sdk\platform-tools>adb shell
error: device not found
error: device not found
I've tried this in two different laptops and I get the same result on both. Both laptops are running Windows 7 and my tablet is currently running version 7.5.1. Any help would be greatly appreciated. And thanks in advance.
jbomxda said:
Greetings,
Apologies if this has been asked somewhere else before, but I haven't found it anywhere after hours of searching. I've been trying to get ADB to work on my Kindle Fire HD 7 with no success. I've downloaded many drivers and the Android SDK and Android Studio as well. After installing all different drivers, when I connect the tablet to the laptop and test fastboot connection, I get the following:
C:\android-sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
I believe this is expected when I run this command, which I guess means the fastboot cable is working and perhaps the driver too? (not sure). However, when I run the following ADB commands this is what happens:
C:\android-sdk\platform-tools>adb devices
List of devices attached
(this comes empty, no result)
C:\android-sdk\platform-tools>adb shell
error: device not found
error: device not found
I've tried this in two different laptops and I get the same result on both. Both laptops are running Windows 7 and my tablet is currently running version 7.5.1. Any help would be greatly appreciated. And thanks in advance.
Click to expand...
Click to collapse
ADB doesn't work in fastboot mode,only fast boot commands do
Sent from my GT-i9100 running CM11
SafinWasi said:
ADB doesn't work in fastboot mode,only fast boot commands do
Sent from my GT-i9100 running CM11
Click to expand...
Click to collapse
LOL, THANK YOU SO MUCH! I can only LOL. I thought the ADB commands had to be run in Fastboot mode. No wonder. IT WORKS!!! Thanks again!!!
I am trying to flash factory image 5.1 to my Nexus 6 so OTA updates will work. I have installed android studio (tried basic tools first, thought this might help) and the LMY47D factory image and unzipped everything. My phone is recognized by the computer as Android device - Google Nexus ADB interface in device manager. It will not show up in portable devices or other devices. The phone was rooted with CF-auto root but that has been undone and root checker verified it is no longer rooted. I cannot get the command prompt to recognize fastboot. I am using windows 8.1 and the only account and therefore the administrator. I have researched this for days and cannot figure it out. Any help would be greatly appreciated.
lsmo58 said:
I am trying to flash factory image 5.1 to my Nexus 6 so OTA updates will work. I have installed android studio (tried basic tools first, thought this might help) and the LMY47D factory image and unzipped everything. My phone is recognized by the computer as Android device - Google Nexus ADB interface in device manager. It will not show up in portable devices or other devices. The phone was rooted with CF-auto root but that has been undone and root checker verified it is no longer rooted. I cannot get the command prompt to recognize fastboot. I am using windows 8.1 and the only account and therefore the administrator. I have researched this for days and cannot figure it out. Any help would be greatly appreciated.
Click to expand...
Click to collapse
are you connected to your computer via USB AND in your bootloader? fastboot only works in the bootloader, adb everywhere but in the bootloader.
lsmo58 said:
I am trying to flash factory image 5.1 to my Nexus 6 so OTA updates will work. I have installed android studio (tried basic tools first, thought this might help) and the LMY47D factory image and unzipped everything. My phone is recognized by the computer as Android device - Google Nexus ADB interface in device manager. It will not show up in portable devices or other devices. The phone was rooted with CF-auto root but that has been undone and root checker verified it is no longer rooted. I cannot get the command prompt to recognize fastboot. I am using windows 8.1 and the only account and therefore the administrator. I have researched this for days and cannot figure it out. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Windows 8.1 may require you to disable driver signature checking. That's what I had to do on my work PC in order for fastboot to work.
Evolution_Tech said:
Windows 8.1 may require you to disable driver signature checking. That's what I had to do on my work PC in order for fastboot to work.
Click to expand...
Click to collapse
really? thats a new one for me
I'm Wow, thanks for the quick response. Guess I'm not as savvy as I thought about this stuff. Would you mind telling me how to do that?
simms22 said:
really? thats a new one for me
Click to expand...
Click to collapse
Yep. I was in the same boat. ADB worked perfectly fine but fastboot wouldn't recognize at all. Disabled signature checking and all good.
---------- Post added at 04:56 PM ---------- Previous post was at 04:47 PM ----------
lsmo58 said:
I'm Wow, thanks for the quick response. Guess I'm not as savvy as I thought about this stuff. Would you mind telling me how to do that?
Click to expand...
Click to collapse
https://youtu.be/gmw86KplqmU
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
Also, if still having driver issues after that, try this:
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
Ok, I've gotten closer. When I flash-all the process starts but I get cannot load bootloader img then cannot load zip. The unlock oem bootloader command works , I get bootloader is already unlocked message.
lsmo58 said:
Ok, I've gotten closer. When I flash-all the process starts but I get cannot load bootloader img then cannot load zip. The unlock oem bootloader command works , I get bootloader is already unlocked message.
Click to expand...
Click to collapse
Do not use flash-all. Doesn't work. Flash images separately.
Heres the command prompt from my atempt(s)
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32> C:\Android\shamu-lmy47d-factory-6c44d402\shamu-lmy47d-facto
ry-6c44d402\shamu-lmy47d\flash-all
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: failed to load 'image-shamu-lmy47d.zip': No such file or directory
Press any key to exit...
lsmo58 said:
Heres the command prompt from my atempt(s)
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32> C:\Android\shamu-lmy47d-factory-6c44d402\shamu-lmy47d-facto
ry-6c44d402\shamu-lmy47d\flash-all
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: failed to load 'image-shamu-lmy47d.zip': No such file or directory
Press any key to exit...
Click to expand...
Click to collapse
Fastboot can't see the files you are trying to flash. Put them in the platform-tools folder.
Sorry Evoluton_Tech I didn't see your post, I'l try that.
Thanks to everyone for there help. I restored to factory 5.1 and the 5.1.1 OTA update worked. THANKS!
Evolution_Tech said:
Fastboot can't see the files you are trying to flash. Put them in the platform-tools folder.
Click to expand...
Click to collapse
Or better yet, everyone learn how to use fastboot properly. We should never have to put anything in the platform-tools folder. Its a shortcut to misery
danarama said:
Or better yet, everyone learn how to use fastboot properly. We should never have to put anything in the platform-tools folder. Its a shortcut to misery
Click to expand...
Click to collapse
I concur. I use fastboot installed system wide, thanks to the 15 second installer. I just use my desktop and flash all files from there. It really has simplified things. Works flawlessly on my home PC running Windows 7.
My work PC also has it system wide but I had to disable driver signature checking for fastboot to work.
I hope that's what you meant.
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
MrCsabaToth said:
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
Click to expand...
Click to collapse
Just OEM unlock from the settings...
domsch1988 said:
Just OEM unlock from the settings...
Click to expand...
Click to collapse
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
MrCsabaToth said:
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
Click to expand...
Click to collapse
Try running
Code:
sudo fastboot devices
casual_kikoo said:
Try running
Code:
sudo fastboot devices
Click to expand...
Click to collapse
Yes, sudo didn't make any difference from the beginning.
Hello,
I too am going crazy trying to get fast boot to work on this OnePlus 3T. My research prior to purchasing indicated that this phone was friendly to rooting. I'm no on hour 6, and still can't get fast boot to work. Using Ubuntu 16.04, and the adb and fastboot packages installed from the standard repositories (apt-get install adb..)
sudo, sudo -s, udev rules, etc. nothing has worked.
If anyone has used this phone and os combination to get the unlocking working, please advise.
I've found out the root cause of my problem. I thought that fastboot is one step further from the "actual" fastboot screen. You have to issue the fastboot commands when you see the screen what is in my android stackexhange link.
So I could unlock the bootloader now, now when I try to flash TWRP I get:
Code:
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash recover twrp-3.0.3-1-oneplus3t.img
target reported max download size of 440401920 bytes
sending 'recover' (17588 KB)...
OKAY [ 0.560s]
writing 'recover'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.580s
The USB device I see is
Code:
Bus 001 Device 018: ID 18d1:d00d Google Inc.
and I set up udev rules for it.
Ok, it was just a typo: recover -> recovery
Finally!
Thank you MrCsabaToth!
After 2 more hours trying this following instructions for Windows 7, and OS X (after Ubuntu 16), MrCsabaToth's reply looks to be the way to get past the fastboot oem unlock step.
You have to run it while actually on the phone's boot screen where it gives you options of what type of boot to do, where the top line option is "fast boot". Only then, will the fastboot command from the terminal work.
Not even the oneplus web site tutorial, which is for this exact phone, mentions this. WTF......
Hey folks, long time xda user heavy search user results in minimal posts..
ok here we go.
I unlocked bootloader and rooted device with magisk now im attempting to re lock my boot loader.
i factory reset device and flashed google factory image with supplied zip file from google
command im using is
"fastboot oem lock"
results
C:\Users\RyeMc>fastboot oem lock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
this is first lines from google factory image...
Sending 'bootloader' (8761 KB) OKAY [ 0.253s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
next i opened cmd and entered
"fastboot flash boot" then went and moved boot file into cmd window and said successful also tried boot_a and boot_b
unsure why i have tried to re download sdk manager android studio and input the file locations in the path under advanced settings.
albeit iv been out of the root game for a couple years made the mistake of getting a note 8 so i was stuck in that eco system.
some help or advice would be nice thanks.
before i rooted i made sure i was able to lock and unlock bootloader .
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Thaiban said:
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
device is currently unlocked looking to relock device..
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
uicnren said:
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
Click to expand...
Click to collapse
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
RyeMcFly17 said:
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
Click to expand...
Click to collapse
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
What he said! :laugh:
Easier Windows choice : r29.0.6
download the latest platform tools and extract it, in the folder with the PT files in the top search bar type cmd and then try.
oem unlocking already unlocked
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
RyeMcFly17 said:
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
Click to expand...
Click to collapse
:good::good:
glad you got it sorted.