No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun
Have you enabled USB debugging in the developer options on Android. And are you using sudo or su with adb on Linux?
Sent from my LG-ls990 using XDA Free mobile app
smokey_circles said:
No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun
Click to expand...
Click to collapse
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.
mister_no said:
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.
Click to expand...
Click to collapse
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
I also discovered my fatal mistake was using a kit kat guide that was butchered to be a lollipop guide. Lack of sleep and over-excitedness led to a bootloader lock. Flashed the stock kit-kat ROM, rooted and I'm finally running CM12 nightlies.
No major bugs that irritate me, smooth and responsive. Very happy with the G3
smokey_circles said:
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
Click to expand...
Click to collapse
Not to my knowledge.
Actually when the device is in bootloader the connection protocol is MTP.
You can check it yourself with lsusb command that device's USB ID (idVendor & idProduct) is different for PTP than for MTP. In bootloader device has the same USB ID as when it is running normally and MTP mode is selected.
Related
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2
Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250
no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff
getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3
[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app
pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722
Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250
Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps
ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.
Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.
did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons
thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.
I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
robopilot99 said:
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
Click to expand...
Click to collapse
I had the same issue. Tried it on windows (though I hate windows ) and it worked on windows. I am STILL trying to figure out how and why?
I had the same problem on Ubuntu 15.04, and I fixed it by uninstalling the outdated version of fastboot in Ubuntu's repositories and replacing it with the binary from the Android SDK platform tools.
The fastboot protocol may have changed slightly with Lollipop, and Ubuntu's fastboot and ADB packages say they're from 4.2. Remember to run fastboot as root unless you have the udev rules set up. Hope that helps!
yes i had a similar issue on ubuntu with the repo version. I actually got an error message saying i needed a newer version
Thanks. Using the version I got from the internet worked fine. I'm now getting and error about fingerprinting and stuff. Looks uke I'll have to wait for a way to unlock the bootloader on the latest version.
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
bhoth said:
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
Click to expand...
Click to collapse
You will want the Android SDK tools. Here is the download page:
https://developer.android.com/sdk/index.html#Other
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
joel.maxuel said:
You will want the Android SDK tools. Here is the download page:
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
Click to expand...
Click to collapse
yeah that's what I ended up doing. It's a pain to find it in the huge download but it's kinda your only option.
im currently on the same problems as you too.. cant use fastboot on ubuntu 14.04 lts.. but i found this article online, didnt test it yet since im on my windows right now to use fastboot.. who knows this may help in updating to latest adb bin..
http://bernaerts.dyndns.org/linux/74-ubuntu/328-ubuntu-trusty-android-adb-fastboot-qtadb
Click to expand...
Click to collapse
wait i was wrong, the cmd there is to update adb to latest version and not for fastboot.. cant help anyway, unless download the whole android sdk as mentioned above..
While trying to get Android Pay to work I removed root from my phone using the option in Kingroot's menu and then restarted. Now FireOS doesn't load and doing a factory restart from recovery doesn't do anything either.
I thought I'd just sideload 4.6.3 and restart from scratch, but when I connect my phone in 'sideload from adb' mode from recovery I only get a "Fire" device in device manager. After a minute it gets an error "Device Cannot Start"
Manaully scanning for hardware changes doesn't give me my "Android Composite Device ADB Interface"
Sounds like you don't have the ADB drivers installed correctly. See this post:
http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
Thank You. That's exactly what was wrong.
I didn't think was would be the problem since I had used that 15 second adb installer last night to get adb working before I messed everything up this morning.
In recovery mode I'm sure it connected to my computer as a different device!
Thanks again.
ekztal said:
Thank You. That's exactly what was wrong.
I didn't think was would be the problem since I had used that 15 second adb installer last night to get adb working before I messed everything up this morning.
In recovery mode I'm sure it connected to my computer as a different device!
Thanks again.
Click to expand...
Click to collapse
No problem. Glad it worked out.
cannot read update.bin
Hi
I have the same problem with my phone. I have downloaded 1.2 gb 4.46.3 fire os update but I am not able to push the package after detecting my fire phone in adb sideload method.
cannot update.bin error was thrown by cmd prompt.
How can I recover my phone . Pls help.
Androidhari said:
Hi
I have the same problem with my phone. I have downloaded 1.2 gb 4.46.3 fire os update but I am not able to push the package after detecting my fire phone in adb sideload method.
cannot update.bin error was thrown by cmd prompt.
How can I recover my phone . Pls help.
Click to expand...
Click to collapse
The problem could be the filename. Microsoft Edge and Internet Explorer download the 4.6.3 update as a .zip file. If your folder options are not set to display all files extensions, go to Veiw> Options> Change folder and search options> View>. Uncheck "Hide extensions for known file types" and click OK. Check the filename for update.bin, if the filename is update.bin.zip, changing it to update.bin should correct your problem.
If the fielname is correct, the file path could be the problem. Try entering the complete path to the file, use quotes around the file path if there are any spaces in the file path (for me the file path is: "C:\Program Files (x86)\Minimal ADB and Fastboot\update.bin").
If you still can't install the update, then see Problem with "cannot read update.bin" in 4.6.4 to 4.6.3 downgrade on how to use Safestrap to install update 4.6.3.
Hi
Even my phone is bricked but when I try to sideload update.bin , cmd prompt throwing error as " cannot update.bin". My fire phone is identified by windows 10 with adb drivers.
Can someone suggest how can we fix this issue?
Thanks
---------- Post added at 01:45 PM ---------- Previous post was at 01:35 PM ----------
Thanks, I will try what you had suggested on windows 10 but I can not use safestrap as except " amzon" logo I can not see anything after power on so I am getting to apply update from ADB using buttons. So how can I install safestrap and king root without turning on browser on mobile.
Thanks
Androidhari said:
Thanks, I will try what you had suggested on windows 10 but I can not use safestrap as except " amzon" logo I can not see anything after power on so I am getting to apply update from ADB using buttons. So how can I install safestrap and king root without turning on browser on mobile.
Thanks
Click to expand...
Click to collapse
You won't be able to install Safestrap or Kingroot unless you can bootup your Fire Phone, so sideloading the update is your only option. It appears that your ADB drivers are installed correctly, just to be sure, see DePingus's post.
Thanks, it worked. My fire phone is up.
Hi a little help if you will please.
I've rooted then installed safestrap. Done back up, factory reset then Flashed c11 rom. All looked great. Made up with the ROM but I've tried to use kingroot to root again but it won't work. I can get in to safestrap recovery but says it's inactive. I've tried to search for the fix but can't find anything directly for my problem just how to root with kingroot. Any help would be great. Thanks.
Can't unbrick it.... tried everything
Hi guys, I installed CyanogenMod on my fire phone and it worked for a while... then started rebooting, but before I could do anything it was just rebooting all the time, then I did a hard reset on fire phone and after that... only adb sideload, safestrap was gone... but... adb works fine, everything gets installed, but after rebooting amazon fire phone is lost in a endless rebooting cycle (just shows up the amaozn logo... if powered via USB it tries to do something else, amazon logo shows up for maybe 2-3s longer....
Boys... did I brick my phone forever? Thanks
Hannes
Good evening xda,
Its been to long since ive posted im rooting actively again and ran into an issue. when i utilize kingroot via pc and have the full bpa1 and cpj firmware installed via odin root access confirmed unlock script in adb.exe folder and all drivers installed usb debugging on reactivation off running command prompt in admin mode moving quickly as to not allowing the phone to begin crashing with the temp root and lagging i even confirmed devices connected in adb but when i get to the chmod string in the command prompt it always says no such file or directory found i tried pusing via adb put it on the sd card the internal storage and in the adb folder and keeps saying that error please if im noobing out right now let me know i would greatly appreciate your time thank you guys.
Update: im stuck on the bpa1 and cpd1 with no root is there anything i can do at this stage?
[email protected] said:
Good evening xda,
Its been to long since ive posted im rooting actively again and ran into an issue. when i utilize kingroot via pc and have the full bpa1 and cpj firmware installed via odin root access confirmed unlock script in adb.exe folder and all drivers installed usb debugging on reactivation off running command prompt in admin mode moving quickly as to not allowing the phone to begin crashing with the temp root and lagging i even confirmed devices connected in adb but when i get to the chmod string in the command prompt it always says no such file or directory found i tried pusing via adb put it on the sd card the internal storage and in the adb folder and keeps saying that error please if im noobing out right now let me know i would greatly appreciate your time thank you guys.
Update: im stuck on the bpa1 and cpd1 with no root is there anything i can do at this stage?
Click to expand...
Click to collapse
What do you mean you're stuck on BPA1 and CPD1, it can only be one or the other.
Its a partial firmware cpdi modem i believe but a bpa1 bootloader or the other way around im not on my pc
Sent from my 5056N using XDA-Developers Legacy app
Cpd1*
Sent from my 5056N using XDA-Developers Legacy app
[email protected] said:
Its a partial firmware cpdi modem i believe but a bpa1 bootloader or the other way around im not on my pc
Sent from my 5056N using XDA-Developers Legacy app
Click to expand...
Click to collapse
So you've already rooted BPA1 and you're moving on to rooting CPD1?
I attained root on that partial firmware. Moved onto adb steps to be able to unlock it again as i was already unlocked before i just wanted lineage OS extremely bad. So i followed the guide on xda and then on the 2nd to last string it always says no such file or directory even if the unlock script is on the root of the sd card the internal storage and pc lol still to avail. I followed every step to the T can a pc firewall or something of that affect how smoothly this should be? Ive done it before but i never had this hard of time diff pc as well.
Sent from my 5056N using XDA-Developers Legacy app
[email protected] said:
I attained root on that partial firmware. Moved onto adb steps to be able to unlock it again as i was already unlocked before i just wanted lineage OS extremely bad. So i followed the guide on xda and then on the 2nd to last string it always says no such file or directory even if the unlock script is on the root of the sd card the internal storage and pc lol still to avail. I followed every step to the T can a pc firewall or something of that affect how smoothly this should be? Ive done it before but i never had this hard of time diff pc as well.
Sent from my 5056N using XDA-Developers Legacy app
Click to expand...
Click to collapse
What's the full script that you're trying to execute and which guide are you using? To my knowledge, a firewall has no effect on rooting the Note 4.
quinciebee said:
What's the full script that you're trying to execute and which guide are you using? To my knowledge, a firewall has no effect on rooting the Note 4.
Click to expand...
Click to collapse
Have you tried using kingoroot on the phone? I did it like that and had no issues. Also make sure your developer and security items are ticked.
I think I might know your issue. I had an issue using minimal adb and fastboot. The file that I moved into fastboot "unlock_n4" didn't match the adb command in the instructions. I renamed the file to match the command, and it worked! Up until I figured that out it would say "No Such file".
Hope that helped
Thats a great idea ill have to try that ty.