My question is:
Can you use a Nexus tablet or any android device for that matter, to perform fastboot or adb terminal commands to another device like a Nexus 5 for example, via USB? (terminal emulator?)
Essentially what I'm try to do is unlock the bootloader on my Nexus 5 (replacement that's coming in the mail) and any future Nexus devices, using a Nexus tablet instead of a PC.
The reason I'm asking this:
I'm fed up of laptop computers with mechanical parts, unreliable HDD etc etc..and I'm making the switch to a tablet.
I was dead set on the new Nexus tablet coming out... but then I came to realize without a PC of some sort, how the hell can I unlock the bootloader of my future Nexus devices???
My only alternative is the Microsoft Surface Pro 3 because it still has fully functional windows and can run terminal commands linked to .exe files. via USB attached to an Android.
But for functionality I think the new Nexus tablet coming out will better suit my needs, since windows is certainly not up to par in the mobile world.
no
I had the same question... I'm getting rid of my slow Microsoft PC! Luv my tab and hope someone figures out a way to do this....
Adb yes but its much harder than windows / Linux / Mac. Fastboot no.
Sent from my Nexus 5 using Tapatalk
Maybe if you got Ubuntu to run? (Not sure about Ubuntu Touch though)
Well this is a REAL SHAME, because it means anybody here with an Android, still needs a PC currently..
Unless you throw on dual boot Ubuntu on another Android device to run commands.. and that's just a maybe
Get a laptop/PC with an SSD then, and join the master race:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would this work with a dual boot Ubuntu installed?
THE_KINGDOM said:
Well this is a REAL SHAME, because it means anybody here with an Android, still needs a PC currently..
Unless you throw on dual boot Ubuntu on another Android device to run commands.. and that's just a maybe
Click to expand...
Click to collapse
na, dont need a computer. you can use towelroot to toot your device. then use flashify to flash a custom recovery once you have root. and you can unlock/lock your bootloader with an app as well.
simms22 said:
na, dont need a computer. you can use towelroot to toot your device. then use flashify to flash a custom recovery once you have root. and you can unlock/lock your bootloader with an app as well.
Click to expand...
Click to collapse
It is a good idea to have a computer because if you run into problems and the phone can't boot, all options are exhausted without a computer... If you needed fastboot to repair.
rootSU said:
It is a good idea to have a computer because if you run into problems and the phone can't boot, all options are exhausted without a computer... If you needed fastboot to repair.
Click to expand...
Click to collapse
not saying that its not. im just saying that all is possible without a computer, thats all.
simms22 said:
not saying that its not. im just saying that all is possible without a computer, thats all.
Click to expand...
Click to collapse
True fastboot is not. Substitute methods, yes.
Sent from my Nexus 5 using Tapatalk
Related
Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?
Hmmmm
Ive never herd of this problem. It could be because its a hackintosh. I have a macbook pro and the captivate connects and does everything perfect. If you used a custom rom on the phone that can be an issue. It could be a bad flash. If you have stock then im not sure what the problem could be.
Sorry hope you fix this problem!
Probably not going to be much help but I have a hackintosh and my phone and PC play nice together
OSX is telling you the phone needs to be rebooted? Am I understanding that right? I can fiddle around and see if some settings make mine do the same thing
Are you using a pure vanilla untouched OS X build, or one of those crappy thrown together modded kernel deals.
Used to triple boot Windows, Linux, and OS X on my laptop before it fell off a table.
if you're running a vanilla build then it should work but you probably aren't. what version of OSX and what distro are you using? I suggest posting over at insanelymac since this is most likely a hackintosh issue.
How did you make your hackintosh? Feel free to PM me.
Ethere said:
Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA App
seclm193 said:
How did you make your hackintosh? Feel free to PM me.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
google can be your best friend.
I have no PC. I use XP with Parallels and Bootcamp, and It still is very finicky. Never had a Hackintoch but the newer Macs are Intel. Not sure where I'm going with this, but, yeah.
i dont have any problems with my captivate and my hackintosh. using the vanilla kernel.
Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://tonymacx86.blogspot.com/2010/04/iboot-multibeast-install-mac-os-x-on.html
I am running Cognition 3.04 on my phone. And the minute I plug the phone into USB, this is what I see on the screen. This is not my computer, but it's an image I found on google images, but that's the exact error. I guess it's a kernel panic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't matter if I have USB debugging on, or not. I've pretty much exhausted everything I can think of at this point, unless someone else has a suggestion. On my Windows computer, the phone is seen just fine btw...not sure what the problem could be.
Ethere said:
Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://migre.me/3JFmQ
I am running... is not a phone issue but a hackintosh issue.
Click to expand...
Click to collapse
"Telling me to reboot" and "kernel panic" are two very different things.
Now it's definitely a problem for these guys:
http://www.insanelymac.com/forum/
Yeah, I posted a thread right on TonyMac's website too and they had no clue as to why that happened. Thanks for the link Mike. I'll check it out with them and see what they suggest.
this may be related
From the Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ) FAQ:
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Although Heimdall runs on OS X all Galaxy S devices tested thus far contain a bug in the secondary boot loader that prevents the device registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Update: Samsung have released an updated secondary bootloader that corrects the issue. The correct bootloader is included in the official Froyo release. Obviously you have to get Froyo on your device somehow, but from then on it’s smooth sailing.
Note: Keep in mind if the version of Froyo you’re running is not official then the updated Sbl.bin may not have been included.
Hrm, you may have something there. I'll flash back to stock tonight and see if the Captivate works after that.
I've tried just about everything to get my fastboot working. I'm running on Windows 8. I've tried tool and scripts, different drivers, HTC Sync, EVERYTHING.
I've gotten ADB to work but fastboot won't recognize my phone.When I put my phone into fastboot mode, I can go into my computer and look up the phone in device manager and I do see the phone. Unfortunately, it presents an error that say the device has failed to start. This has been unchanged through out every "fix" I've tried. Any ideas?
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
timmaaa said:
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
Click to expand...
Click to collapse
Oops, sorry. I've tried the tools that are supposed to set up fastboot for you, I downloaded the SDK and got the fastboot and adb files but nothing shows up in the "fastboot devices". I've also tried the HTC Sync route as well as numerous drivers that are claimed to be the "fix".
What about some of the guides that are available that specifically address this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Evita
timmaaa said:
What about some of the guides that are available that specifically address this problem?
Sent from my Evita
Click to expand...
Click to collapse
I've tried all the results on that first page. Nearly every time, I get an error message with a yellow triangle for an icon:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
timmaaa said:
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
Click to expand...
Click to collapse
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
KungPow90 said:
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
Click to expand...
Click to collapse
Download latest HTC driver , go into your device manager in win 8 and in device mgr menu options on top make sure and click show hidden (not connected ) devices. You then will have to click onto the greyed out HTC or android name in device mgr tree and update manually . you have to actually go to the sub folder in the driver update and not just click the folder that its in. Lol its a pain but it does work. You can Google manually install HTC driver for win 8 and there is couple tutorials. Hope it helps. I beta tested win 8
And had to do that. Lol im back to win 7 and Ubuntu now
Senseless Power Unlocked
Hi Guys,
Have literally spent 8 hours trying to fix this damn phone, it's my mothers which needs a complete wipe using the stock rom. Even my younger brother had a go for a week and has been passed on to me. Not touched an Android phone in about two years so very rusty with the whole roms and flashing etc.
The main issue is I can't get Windows 8.1 to see the phone in USB wether it be plugged directly in Android, USB debug, bootloader or Fastboot USB. I have installed ADB with all the drivers, tried multiple HTC drivers and HTC Sync, PDAnet, AMD chipset drivers, USB controller drivers, random drivers from here on XDA as well as a multitude of other sites. Tried USB 3.0 and 2.0 (front and back slots).
How am I supposed to flash a custom recovery without the computer seeing the phone? If I can just get that sorted I am pretty much set with getting the stock rom on there and the rest. Not sure what my brother has put on it or if he has flashed a custom rom or changed the radio/boot because I have no clue what the phone is supposed to be running.
Please some help here, don't really want to be spending more time on this.
Details:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.
old.splatterhand said:
I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.
Click to expand...
Click to collapse
Yes the phone does boot into the OS but again is not properly recognized, PDAnet and HTC Sync find the phone but doesn't show up or in ADB. I have checked well over 30 threads on here regarding Windows 8.1, downloading various tools and drivers etc without success.
Will check out those links.
Thanks.
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.
you sure you got the right drivers?
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?
wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program
Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods
Hi everyone. Could someone please direct me to a guide for going back to the stock firmware? I have been looking everywhere with no luck at all.
Thanks!
Jonny_Bandana said:
Hi everyone. Could someone please direct me to a guide for going back to the stock firmware? I have been looking everywhere with no luck at all.
Thanks!
Click to expand...
Click to collapse
https://c.mi.com/oc/miuidownload/detail?guide=2
This page doesn't like playing with mobile browsers, so if you've got a blank page change the browser to desktop mode.
All required downloads are in the guide.
The Mi Flash Tool will lock the bootloader, by default, after flashing. If you don't want to do this, then change the option at the bottom of the tool before flashing (step 5)
If you wish to lock the bootloader, you must make sure the ROM region matches the phone, i.e. global ROM on a global phone.
Robbo.5000 said:
https://c.mi.com/oc/miuidownload/detail?guide=2
This page doesn't like playing with mobile browsers, so if you've got a blank page change the browser to desktop mode.
All required downloads are in the guide.
The Mi Flash Tool will lock the bootloader, by default, after flashing. If you don't want to do this, then change the option at the bottom of the tool before flashing (step 5)
If you wish to lock the bootloader, you must make sure the ROM region matches the phone, i.e. global ROM on a global phone.
Click to expand...
Click to collapse
Thanks!
However, I'm having a lot of trouble with the tool. It will not recognize my phone. I connect it, and the computer detects the phone. Then I click on "refresh" on the tool, and automatically the USB device is disconnected from the computer and the tool will not recognize it.
I have installed the Qualcomm and ADB drivers, rebooted and nothing changes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, after hitting refresh (device still connected on Fastboot):
Any ideas?
Thanks again
Sounds like a dodgy USB connection.
Try using the best USB cable you can find. If that doesn't work, try using a different computer. Fastboot and adb are very sensitive to the quality of the USB connection.
My old laptop will happily connect normally to my phone and I can transfer files with no issues, but from about a year ago I can no longer use adb and fastboot, with similar problems you are seeing. Using the same phone and cable I have no issues with my wife's laptop.
Robbo.5000 said:
Sounds like a dodgy USB connection.
Try using the best USB cable you can find. If that doesn't work, try using a different computer. Fastboot and adb are very sensitive to the quality of the USB connection.
My old laptop will happily connect normally to my phone and I can transfer files with no issues, but from about a year ago I can no longer use adb and fastboot, with similar problems you are seeing. Using the same phone and cable I have no issues with my wife's laptop.
Click to expand...
Click to collapse
That actually worked. Phone is flashed. Thanks a lot friend.