Cydia Impactor
How it works?
It used the Master key exploit to drop SuperSU binary, if the master key exploit does not work it will attempt to use another Signature Bug found in Android.
What is the Master Key Exploit?
The Master Key Exploit was discovered by BlueBox Security, it can modify the contents of an application package without affecting the cryptographic signatures.
Would it work on Your Xperia?
If you are running anything below 4.4 KitKat then Yes this would work on Your Xperia!
If you have the Xposed Master Key Exploit Patch this will not work.
And On Stock KitKat it may or may not work (Not Tested)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download: http://www.cydiaimpactor.com/
Enable USB Debugging, Then Run the Program and click Start and then Install SuperSU from the Play Store!
Say Thanks because your Rooted!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
UPDATE:
Not Working on Xperia Z on Android 4.2 and Above, Firmware .244 & Above
Sony Xperia Z with stock 4.3 - no device found.
Sony Xperia Z Ultra Stock 4.3 - Signature bugs unavailable
tried on Xperia Z stock 4.3
Code:
signature bugs unavailable
themonyo said:
tried on Xperia Z stock 4.3
Code:
signature bugs unavailable
Click to expand...
Click to collapse
Getting the same error. For those facing device not found error, check your phone for a dialogue to provide access to the app. Too bad this doesn't work, would have been great for the Xperia Z on Android 4.3.
Ereckson said:
Getting the same error. For those facing device not found error, check your phone for a dialogue to provide access to the app. Too bad this doesn't work, would have been great for the Xperia Z on Android 4.3.
Click to expand...
Click to collapse
It is because the master key exploit is patched by Sony as early as .244(4.2) firmware (if I remember correctly)
Not working on Dell Venue 7 with Intel Atom processor and Android 4.3
Cydia Impactor On Hanspree HSG1279 Tablet
UltraGamerHD said:
Cydia Impactor
How it works?
It used the Master key exploit to drop SuperSU binary, if the master key exploit does not work it will attempt to use another Signature Bug found in Android.
What is the Master Key Exploit?
The Master Key Exploit was discovered by BlueBox Security, it can modify the contents of an application package without affecting the cryptographic signatures.
Would it work on Your Xperia?
If you are running anything below 4.4 KitKat then Yes this would work on Your Xperia!
If you have the Xposed Master Key Exploit Patch this will not work.
And On Stock KitKat it may or may not work (Not Tested)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download: http://www.cydiaimpactor.com/
Enable USB Debugging, Then Run the Program and click Start and then Install SuperSU from the Play Store!
Say Thanks because your Rooted!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
UPDATE:
Not Working on Xperia Z on Android 4.2 and Above, Firmware .244 & Above
Click to expand...
Click to collapse
How do you install the program. Tried to run it with the tablet connected to PC via USB. Clicked on impactor.exe, clicked start and all I get is "no device found". I am able to copy the Impactor folder to the tablet internal and external sdcard and run impactor.exe but I get no device found.
I am on Android version 4.2.2. Any ideas?
AHLASSICH said:
How do you install the program. Tried to run it with the tablet connected to PC via USB. Clicked on impactor.exe, clicked start and all I get is "no device found". I am able to copy the Impactor folder to the tablet internal and external sdcard and run impactor.exe but I get no device found.
I am on Android version 4.2.2. Any ideas?
Click to expand...
Click to collapse
Enable USB Debugging and install drivers!
Then just hit start and Install SuperSU!
Cydia Impactor On Hanspree HSG1279 Tablet
AHLASSICH said:
How do you install the program. Tried to run it with the tablet connected to PC via USB. Clicked on impactor.exe, clicked start and all I get is "no device found". I am able to copy the Impactor folder to the tablet internal and external sdcard and run impactor.exe but I get no device found.
I am on Android version 4.2.2. Any ideas?
Click to expand...
Click to collapse
Thank you UltraGamerHD. Enabling USB is a given. Like I mentioned, I was able to copy to both internal and external sd cards from my PC. I think that means USB is enabled. I guess you install Impactor on the PC, plug the tablet into USB and make sure USB is enabled and then run the impacter.exe. I still get device not found error. I also tried installing SuperUser SU using an UPDATE.zip thru the recovery mode. It appeared to run just fine then heartbreak, I got "Installation Aborted". :crying: Several people have gotten root so I know it can be done. At the moment, nothing is working for me. The only thing I haven't tried is the ADB approuch. I don't know how to use it. I have JS Terminal from the app store installed. Maybe someone can give me a link to step by step input instructions for using the terminal to get root.
Side question: I installed ES File Explorer and I am able to open the system folder and see xbin and open xbin. I see busybox and sqlite3 amoung other files in the xbin folder. I do not see an su file though. I thought you could not open system without root. Do I have root and not know it? Anybody have any idea whats going on with my tablet? I am running windows 8.1 on my PC. I don't know if that is relavant or not.
AHLASSICH said:
Thank you UltraGamerHD. Enabling USB is a given. Like I mentioned, I was able to copy to both internal and external sd cards from my PC. I think that means USB is enabled. I guess you install Impactor on the PC, plug the tablet into USB and make sure USB is enabled and then run the impacter.exe. I still get device not found error. I also tried installing SuperUser SU using an UPDATE.zip thru the recovery mode. It appeared to run just fine then heartbreak, I got "Installation Aborted". :crying: Several people have gotten root so I know it can be done. At the moment, nothing is working for me. The only thing I haven't tried is the ADB approuch. I don't know how to use it. I have JS Terminal from the app store installed. Maybe someone can give me a link to step by step input instructions for using the terminal to get root.
Side question: I installed ES File Explorer and I am able to open the system folder and see xbin and open xbin. I see busybox and sqlite3 amoung other files in the xbin folder. I do not see an su file though. I thought you could not open system without root. Do I have root and not know it? Anybody have any idea whats going on with my tablet? I am running windows 8.1 on my PC. I don't know if that is relavant or not.
Click to expand...
Click to collapse
"If you are on Windows, you may have to install a device driver to talk to your device over USB. If your device is not detected, use Impactor's USB Driver Scan feature to attempt to automatically construct and install a driver for your device".
AHLASSICH said:
I thought you could not open system without root.
Click to expand...
Click to collapse
You can read, but not write to the system partition if you're not rooted.
My device shows up in device manager and I have usb debuging on but it keeps saying device not found?
Anyone tried this on Z1 (534 firmware)?
It should (theoretically) work...
Sent from my C6903 using Tapatalk
Any help would be greatly appreciated.
slaveinc said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to install ADB Drivers. Google Universal ADB drivers and you should find it. I think you might be able to use the driver package provided by Flashtool.
Sent from my C1505 using Tapatalk
UltraGamerHD said:
You need to install ADB Drivers. Google Universal ADB drivers and you should find it. I think you might be able to use the driver package provided by Flashtool.
Sent from my C1505 using Tapatalk
Click to expand...
Click to collapse
I will try that. Thanks.
---------- Post added at 04:13 PM ---------- Previous post was at 04:07 PM ----------
It says they are already installed. It shows up in device manager.
slaveinc said:
I will try that. Thanks.
---------- Post added at 04:13 PM ---------- Previous post was at 04:07 PM ----------
It says they are already installed. It shows up in device manager.
Click to expand...
Click to collapse
Enable USB Debugging
Sent from my C1505 using Tapatalk
UltraGamerHD said:
Cydia Impactor
How it works?
It used the Master key exploit to drop SuperSU binary, if the master key exploit does not work it will attempt to use another Signature Bug found in Android.
What is the Master Key Exploit?
The Master Key Exploit was discovered by BlueBox Security, it can modify the contents of an application package without affecting the cryptographic signatures.
Would it work on Your Xperia?
If you are running anything below 4.4 KitKat then Yes this would work on Your Xperia!
If you have the Xposed Master Key Exploit Patch this will not work.
And On Stock KitKat it may or may not work (Not Tested)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download: http://www.cydiaimpactor.com/
Enable USB Debugging, Then Run the Program and click Start and then Install SuperSU from the Play Store!
Say Thanks because your Rooted!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
UPDATE:
Not Working on Xperia Z on Android 4.2 and Above, Firmware .244 & Above
Click to expand...
Click to collapse
AWESOME!!! Run great on my Yifang M7000NBD or Amlogic Next7HD8G (NX007HD8G) whatever!!
works with xperis sp?
anyone tried?
Related
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
plug the phone, open a terminal as administrator/root and type
adb stop-server
adb start-server
adb devices
the last command must return your device name-id
If not there is smth wrong with your installation
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
theminikiller said:
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
No you don't need to enable mass storage, but you need to enable USB debugging from dev settings from the device. Use these drivers
https://www.dropbox.com/s/ryn7l7z0nfc842g/u8800_pc_drivers.zip
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
theminikiller said:
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
Click to expand...
Click to collapse
You have to install them manually from device manager.
Sent from my U8800
After i choose the folder with the drivers i only get a message saying it didnt find any drivers. Do you know why i cant install them?
Is it the same drivers when I'm using aurora ics as gingerbread roms?
Sent from my U8800 using Tapatalk 2
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
theminikiller said:
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
Click to expand...
Click to collapse
I think its safe mode
Sent from my Impulse 4g running vPure Professional CM7.
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thank you the instructions in the link provided worked for me. I am able to see my listed by adb device command...
help
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
jakk181571 said:
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
Click to expand...
Click to collapse
this is not the forum for ur device..
then please tell then where is the correct forum.
i only when to this one because google brought me here, and it was on adb, which is what i am have trouble with.
Re: Adb - device not found (I had same problem) Fixed
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue updating my Nexus 7 in adb download mode device not found. You will also notice in system setting device driver is showing an error. You can download Adb driver installer which should detect any missing driver and fix the issue.
It worked for me straight away otherwise I had no way round getting to solve the problem. Fheww!! hope it works for you
Many Thanks.
adbdriver.com/downloads
---------- Post added at 05:55 PM ---------- Previous post was at 05:43 PM ----------
You may be missing the device driver when switching to USB Debugging mode using ADB Command prompt device not found.
Please download and intsall adb driver installer. It found my device and installed missing driver straight away problem fixed now I dont seem to have any issue.
adbdriver.com/downloads/
Glory be to Almighty God. Thank you!!
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
same problem...
I have fresh installed N7 3g 4.2.2
adb devices show me "device offline" on Linux.
Do anybody help me solve?
AW: 4.2.2 adb device offline
It's a New security feature: in your device a popup with a hash key should be shown asking you whether you would allow the PC to connect to your device. After accepting that, the device can be accessed from the PC.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
It's a New security feature: in your device a popup with a hash key should be shown asking you whether you would allow the PC to connect to your device. After accepting that, the device can be accessed from the PC.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for answer. But I don't see popup window.
I install TWRP. Then in recovery mode install root access.
Now I can use local shell via android terminal with su.
Code:
setprop ro.adb.secure 0
getprop ro.adb.secure
1
How to change this property?
seting in /system/build.prop didn't help
Solved. Latest adb installed. Popup fingerprint window appeared.
svs57 said:
Solved. Latest adb installed. Popup fingerprint window appeared.
Click to expand...
Click to collapse
sorry for noob question but how you update your adb?
Yeh how do you update adb, is it through sdk manager
Sent from my Nexus 7 using XDA Premium HD app
azfarmiera said:
sorry for noob question but how you update your adb?
Click to expand...
Click to collapse
Download the android adb fastboot files in this thread link and if usb debugging is enabled and you connect your phone to you computer you should get a pop-up on your phone. It worked for me
http://forum.xda-developers.com/showthread.php?t=2144709
Also I think I opened the fastboot.exe and adb.exe files too
I couldn't update through SDK manager, t just kept popping alert that I need dependant lib, so I just uninstalled whole SDK and installed again, worked like a charm.
azfarmiera said:
sorry for noob question but how you update your adb?
Click to expand...
Click to collapse
To update ADB use SDK Manager.
For some reason the SDK Manager does not automatically show the new release versions of Android SDK Tools and Android Platform-Tools, so if the versions of your Android SDK Tools and/or Android Platform-Tools are respectively older than 21.1 and 16.0.1, you will need to first delete them then reload the SDK Manager to get their new release versions to be displayed and available for installation.
Also, it appears that Android Support Libraries (under Extra) is also required for ADB to work, so you should install it as well.
Also, to get ADB-over-WiFi to work, first use ADB-over-USB to the same given PC/Laptop and grant access with "always" box checked.
digixmax said:
To update ADB use SDK Manager.
For some reason the SDK Manager does not automatically show the new release versions of Android SDK Tools and Android Platform-Tools, so if the versions of your Android SDK Tools and/or Android Platform-Tools are respectively older than 21.1 and 16.0.1, you will need to first delete them then reload the SDK Manager to get their new release versions to be displayed and available for installation.
Also, it appears that Android Support Libraries (under Extra) is also required for ADB to work, so you should install it as well.
Also, to get ADB-over-WiFi to work, first use ADB-over-USB to the same given PC/Laptop and grant access with "always" box checked.
Click to expand...
Click to collapse
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Leonhan said:
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Click to expand...
Click to collapse
I use Android Debug Bridge version 1.0.31.
http://developer.android.com/sdk/index.html
http://dl.google.com/android/adt/adt-bundle-linux-x86.zip
Leonhan said:
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Click to expand...
Click to collapse
They are the latest version and solved the problem for me.
Sent from my Nexus 7 using XDA Premium HD app
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
Click to expand...
Click to collapse
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
DrFredPhD said:
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
Click to expand...
Click to collapse
yup it is r21.1 i checked it... in fact i downloaded all components in android sdk and they are all updated
thats why im puzzled why the adb still not updated(not detecting device)
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
thanks bryant, your first post helped
seems like we need to use the command prompt to let the pc know our device code?
just felt strange why google implement 4.2.2 update and not telling users to update their adb on their pc as well..
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
I finally managed thanks to you ..
✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!
Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!
v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app
Actually!
Are you on 32bit? I included 64bit.
I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD
jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.
Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.
disregard....
working great! thanks OP