whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
Click to expand...
Click to collapse
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Awesome Post. Thanks Alot.Need this tool very much .
shimp208 said:
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Click to expand...
Click to collapse
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
KMyers said:
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
Click to expand...
Click to collapse
Or Verizon Store, or any other store that sells smartphones and tablets . You could make a app that has a run button that when pressed automatically run's a root exploit such as Zerg Rush, then permanently flashes a custom recovery, then a custom ROM of your choice all one after the other. Think of it as mix of z4root, EZ-Recovery, and ROM manager all rolled into one. Only problem is not every device supports fastboot so some devices would be left out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
shimp208 said:
eft out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
Click to expand...
Click to collapse
Hello,
Just the host device needs a custom recovery only to install the tools (this can be perm flashed or temp flashed (fastboot boot recovery.img). Once the tools are installed, the recovery is no longer used.
The target device only needs USB Debugging enabled.
You are also correct in your statement that not all phones respond to the Fastboot protocol. The other tools such as Odin and NVFlash are not so easy to package. Some devices such as the ASUS Transformer TF700 have a Fastboot mode, assuming you unlock the bootloader. Fastboot is the standard on all HTC, Sony and any phone bearing the sacred "Nexus" moniker. It is also favored among "cheap/knockoff" devices.
There are several root tools that simply use adb to work.
What?!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
.....
HAVE FUN!!!
Click to expand...
Click to collapse
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
rainabba said:
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
Click to expand...
Click to collapse
Thanks,
I guess the reason many have not downloaded this is because it was stuck in one of the lesser active sections of XDA-Developers. I assume that most people visit the portal and device specific development threads. Aside from being featured on the portal, not many ways to get people in here.
Just tried this out on my nexus 7 running ubuntu, this is indeed awesome, thanks for compiling it
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
rmclardy said:
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
The new "secure adb" that was introduced in Android 4.2.2 will not work at this time. You may be able to try running "adb devices" at root to see if it works for you. If not, you can manually reboot it into recovery and use kfastboot to flash the new recovery
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
rmclardy said:
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
If your device is currently rooted, you should be able to run an App from the Play Store to reboot it into recovery (https://play.google.com/store/apps/details?id=com.liveov.rebooter ), from there, kfastboot will work
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
777.300 said:
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
KMyers said:
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
Click to expand...
Click to collapse
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
777.300 said:
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
Click to expand...
Click to collapse
Yes, I had a similar issue a few weeks ago. I was in Texas for a few days and my HTC EVO 4G LTE had an unfortunate run in with the Drink Cart on the Airplane. I had to go out and purchase a new phone at the Sprint Store in Texas. I had the phone purchased and rooted in about 10 minutes . Thanks to revone, unlocking the bootloader on the HTC one took almost no effort and I had S-Off to boot. All from my ASUS Transformer 700
so this is only for nexus?
Thank you very much!,
Testing on Samsung Galaxy Y
Just what i was looking for
I am yet to test it out, but i surely am very happy to see this thing actually exists. Just googled it out of the the blue and "kaboom!"here it was..
Keep up the good work.
Cheers
the handset is samsung galaxy grand neo I9060. I rooted with kingoroot and it was sucessful. Checking with root checker apps also gives green signal. But i could not get any response for su in linux command mode . Moreover opening the linux, i forgot the actual word, or app, i do not get hash # simple to show it as rooted but a dollar $ sign to show it not as rooted. What is the actual stage?
I want to delete the batterystats.bin to find the cause or to fix the problem of depleing battery after 40 percent. I tried so much things.
how to access the said file, so that i actually manually delete it to see its deletion.
Regarding the battery problem, try if a new battery works for you.
If it fixes the problem, well good job.
If it doesn't the problem is somewhere else and you got 2 batteries now.
If the battery isn't replaceable then you're screwed
Sent from my Samsung Galaxy S7 using XDA Labs
Did you run the command adb devices ? If the daemon doesn't start after you do that, adb isn't working. If you get the serial, or model number, adb is working. I try to find the official way to root, instead of using kingoroot, I don't know if the apps changed, but when I used it, you have to re-enable it every time you reboot. It might not work with adb, since when you reboot, root's gone, and you have to re-enable through the phone being on.
Hello fellows...
I have a problem i never encountered before ...
If I try to connect to my phone by using "adb shell" I only receive this message:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I know, I am "just" not authorized ... but thats my problem!
The phone never asks for granting the permission ...
And I can't revoke any "granted" permissions, since my dev-menu is missing this point.
About my system:
I am running windows 10 with adb 1.0.39, fastboot is working without problems.
My phone is a Cubot X18 Plus running a treble GSI of Ressurection Remix 6.2.1 (Oreo 8.1).
Since other gsi/roms are able to use this, I would even consider the gsi as the problem, but it seems to be dead since it is oreo, but I posted in the thread anyway.
I have lost my device serial number (now 1234567ABCDEF) but this shouldn't be a problem, since it is working on stock rom.
Is there any way to get adb rights granted? Or get the menu action back to revoke all granted devices?
I can use the local shell without any problems, at least I get root access over there.
Greeting
houston
I have written a blog about how to manually add adbkey.pub to phone.
There are termux with root and TWRP on rootless phone methods.
murtezayesil.me/adb_vendor_keys-is-not-set.html
I have returned to stock, since no custom rom really worked.
But tanks for your answer, maybe other ppl will be able to use your post.