Update Fastboot on Linux(opensuse)? - Nexus 6 Q&A, Help & Troubleshooting

Hi, I'm on opensuse 42.3 leap and tried to flash latest factory img, but when I tried Fastboot system.img I got "(bootloader) Data size exceeds download buffer FAILED (remote failure)". I googled it and found that I have to update Fastboot. I use android-tools, v5.1.1, which is an old one, but there is nothing newer on opensuse repos. I installed android studio, but didn't seem to work(couldn't find specific instructions for opensuse). I ended up using a live manjaro omg that has latest android-tools to have a working phone again, but that's not a permanent solution. How can I update my Fastboot or install latest android-tools on opensuse?
Sent from my Shamu using Tapatalk

Did you try to download the standalone version? You should be able to unzip and run the commands.
https://developer.android.com/studio/releases/platform-tools.html

No I didn't, but android studio contains the commands. I suspect there was a conflict between android-tools fastboot and studio 's version, so I have to uninstall android-tools to make this work. I found another thread that suggests using mfastboot(Motorola's tweaked version) and works fine. I'll try both ways on next factory update, because I just completed all the flashings, unless there is a better suggestion. Thanks for your answer anyway
Sent from my Shamu using Tapatalk

Harris P said:
No I didn't, but android studio contains the commands. I suspect there was a conflict between android-tools fastboot and studio 's version, so I have to uninstall android-tools to make this work. I found another thread that suggests using mfastboot(Motorola's tweaked version) and works fine. I'll try both ways on next factory update, because I just completed all the flashings, unless there is a better suggestion. Thanks for your answer anyway
Sent from my Shamu using Tapatalk
Click to expand...
Click to collapse
Need to update adb
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Need to update adb
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Can you propose a method to do this please?
Sent from my Shamu using Tapatalk

You could replace it yourself. Download this:
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
And unpack it.
In terminal cd to platform-tools then:
sudo cp adb fastboot /usr/bin/

Lawstorant said:
You could replace it yourself. Download this:
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
And unpack it.
In terminal cd to platform-tools then:
sudo cp adb fastboot /usr/bin/
Click to expand...
Click to collapse
Does this solution works system wide?
Sent from my Shamu using Tapatalk

Try "whereis adb" and you'll see that's where it is now. After replacing, run "adb version" to make sure it's working properly.

Related

[HACK] Superboot Method for 2.3.2 (GRH78C)

The Superboot root method boot.img for 2.3.2 is now live thanks to Paul over at Android @ MoDaCo.
"Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!"
Using Superboot
- Download the zip file and extract
- Connect Nexus S via USB cable (with debugging enabled - Settings->Applications->Development->Check "USB Debuggging")
- Boot into bootloader mode - (Turn on while holding 'volume up')
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
*Again, All credit goes to Paul at Android @ MoDaCo*
Cool I'm rooted already but nice to see easier ways of doing it for the noobs. Appreciate the work.
Sent from my Nexus S using Tapatalk
Updated today to 2.3.2 and lost root. Used this and I'm back up and running ! Thank you!!!
Sent from my Nexus S using XDA App
2.3.2
can u do this being rooted or do you have to revert to stock
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
i think you would
fastboot
fastboot satus failinvalid command
finally regain root, thank you!!!
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
dakiz71 said:
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
Click to expand...
Click to collapse
Yes. You may have to re-root after updates but your phone will prompt you when OTA updates are available just like normal.
Sent from my Nexus S using Tapatalk
annndrewww said:
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Figures. The answer was staring me in the face the whole time. I think I even remember unlocking it last time I rooted this way. I guess I should just leave it permanently unlocked then so it doesn't keep wiping every time I go to root after an update.
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Am I the only one that did not lose root after the latest 2.3.2 update?
DarkAgent said:
Am I the only one that did not lose root after the latest 2.3.2 update?
Click to expand...
Click to collapse
I used the superboot method for 2.3.1 and also did not lose root in with the 2.3.2 update.
Sent from my Nexus S using Tapatalk
You shouldn't.
P
Windows 7
For me install-superboot-windows is waiting for device long without success :\
No matter ... i had to force my pc recognize Nexus once more
Thank you. This seems simple. I'm stuck with my XP recognizing my Nexus S USB Driver after installing SDK and Google USB Driver even after trying to "update" driver under Device Manager and redirect the directory to Google USB Driver? I'm very confused.
philbs17 said:
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Click to expand...
Click to collapse
Ok buddy heres what you need to do, on the MAC, this is how i do it.:
DL the .zip in the OP.
Extract it on you're desktop
Rename the Extracted file to Nexus (thats what I name it)
youre device needs to have the bootlader Unlocked.
Open Terminal and type
cd desktop
cd nexus
chmod +x install-superboot-mac.sh (press enter)
./install-superboot-mac.sh (press enter)
then you're done. hope this helps.
Let me know.
Simply amazing! Thanks for the breakdown.

Flashable zip of Bootloader 4.18 for grouper & tilapia

Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Re: [delete this thread]‎Flashable zip of Bootloader 4.18 for grouper & tilapia
Yeah works well!
Edit: thought it worked. Stayed on 4.13
Sent from my Nexus 7 using xda premium
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
eric-filth said:
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
oh! coz i saw there stated unlocked.
is it a must to type that?
o0boiboi0o said:
oh! coz i saw there stated unlocked.
is it a must to type that?
Click to expand...
Click to collapse
No, if are unlocked you dont need
Enviado de meu Nexus 7 usando o Tapatalk 2
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
nickporwal said:
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
Click to expand...
Click to collapse
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
When you type in adb devices it returns your device but you'll notice that it says offline next to it.
Therefore you can't send any adb commands to it.
It's a new security measure apparently, the solutions can be found in the forums.
Sent from my Incredible S using xda app-developers app
where are the zips
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
I too tried to create a flashable zip from the OTA, but it doesn't stick. I had to use fastboot
Sent from my Nexus 7
o0boiboi0o said:
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
Click to expand...
Click to collapse
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Adinaky said:
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Click to expand...
Click to collapse
I am in the same boat as well. I am having weird adb issues that won't allow me to fastboot either. I am gonna reinstall SDK and see if i can adb working.
Sent from my Nexus 7 using xda premium
Tone_Capone said:
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
Click to expand...
Click to collapse
Dont think there is any error. It kept stating waiting for device but nth happened on my device side. Seems like the command get thru but nth is done.
Oo more and more ppl are having the same prob as me! :victory: Lol
Lets wait for TS's flashable file!
http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
waiting for a linux version, i hate windows
If you don't have a working adb, you should try this guide: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/ , it's the only one that worked for me.
Sent from my Nexus 7 using xda premium
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
o0boiboi0o said:
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
Click to expand...
Click to collapse
This happened to me when my adb was not working properly, it showed 4.18, but I fixed the adb and installed the bootloader again, just to be sure.
Sent from my Nexus 7 using xda premium
Anyone an idea, why flashing the bootloader does not work with the zip files?
I am somewhere in nowhere and can not fastboot, have only my Nexus 3G with me. Its on 4.2.2 but bootloader still 4.13. Used this ROM:
[ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)
to update. Worked apart of bootloader and radio.

Motorola fastboot for osx

I apologize in advance if this is covered elsewhere but after searching I'm only able to find mfastboot files for osx from 2011 posted on the atrix forums. Is this sufficient? Does anyone know of a current source?
I'm on OSX 10.9 and have adb and fastboot from the android SDK installed but can't find the motorola fastboot utility referred to by
"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility"
I've downloaded the Motorola Device Manager and the stock factory image for the Verizon Developer Edition.
What am I missing?
This is preemptive (I have no current need to flash back to stock) but I'd like to have the ability to do so if needed.
I am not in front of my MacBook at the moment, but I believe the fastboot with the SDK is what you need. At least this is what I used when I rooted and it worked great.
Sent from my XT1060 using Tapatalk
zenrubble said:
I am not in front of my MacBook at the moment, but I believe the fastboot with the SDK is what you need. At least this is what I used when I rooted and it worked great.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
From my understanding due to limitations on the size of the files you can flash using the fastboot from the SDK, you need the Motorola fastboot to flash the images of the stock /system provided on moto's website.
Flashing smaller files like a custom recovery would work with the fastboot from the sdk, but to go back to stock you need mfastboot.
Thanks for the clarification. I don't recall seeing mfastboot anywhere in the files I downloaded from Motorola.
Sent from my XT1060 using Tapatalk
https://dl.dropboxusercontent.com/u/7632904/Mfastboot-4.4.zip
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/Mfastboot-4.4.zip
Click to expand...
Click to collapse
Thank you, that was what I was searching for - I copy the File in the Darwin folder to my SDK folder where the fastboot on my Mac & thats it?
I don't use a Mac, sorry, so I am not certain if you need to add that folder to your path in the OS or run from terminal in that directory.
Someone familiar with them will have to help you with the details.

[Q] help rooting nexus 6 using crunchbang linux

I've got java and SDK tools properly installed. I've tried several methods. Always gives error command fastboot not found. I'm on crunchbang Linux
If you go to general > sticky roll-up thread....
You'll find my fastboot thread which tells you how to use fastboot correctly.
@NiNJAwitaRaZR,
Did you type ./ before the fastboot command?
cam30era said:
@NiNJAwitaRaZR,
try using sudo ./ before the fastboot command.
Click to expand...
Click to collapse
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH
rootSU said:
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH
Click to expand...
Click to collapse
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.
cam30era said:
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.
Click to expand...
Click to collapse
Me too. Personally I just drop them directly in /usr/bin

Emulator-5554 error in fastboot

Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks
bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error
SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good:

Categories

Resources