Database Info

[mod] Clockwork recovery 3.0.2.8 [easy install] v3

I have put together a little program to allow me to install recovery quicker because I got fed up of it taking so long.
Its dead easy to use!
instructions
download file
unzip
connect vega and make sure usb debugging in enabled
click windows_install, mac_install, or linux_install to flash depending on what your running (u should know that )
wait for that to finish
to boot into recovery click the recovery icon in your app draw
Download v3 clicky - mirror 1
another v3 - mirror 2
For those of you that are having an "error: device not found"
It means that you dont have the adb drivers installed correctly
To check right click on the windows folder and click command prompt here. then type adb devices
If nothing shows up then it means the drivers arent installed
To install them correctly follow this guide
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
Click to expand...
Click to collapse
v1 - windows only
v2 - added mac and linux
v3 - updated to CW 3.0.2.8
thanks go to @mad murdock for making the image and now for fast mirrors
also thanks to @bob1369 who has made a mac and Linux version

i have created mac and linux versions
linux; http://www.megaupload.com/?d=JNEP1GJ5
mac; http://www.megaupload.com/?d=O73B61F0
i suggest creating a small automator app on the mac to further speed installation of clockworkmod just drag run shell script into a work flow and write in the box below the code you would usually use to run the script from terminal e.g.
cd /route/to/script
./install.sh

This worked a treat for me.
I used it to update cwm to the latest version.
Thanks very much for a time saving app.

bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
ahh nice work! i will add to the first post and mention you
i will test linux some time

bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
I have tested the linux version. It works. Same thing with the chmod... I guess you cannot chmod something that is not there.. Just remove the trailing slash. It should work then....

help
my computer cant detect my advent vega
i try xp win7 and vista
help

device no find
after i use install
the word"device no find"
anyone help

fung58745 said:
after i use install
the word"device no find"
anyone help
Click to expand...
Click to collapse
on the vega or pc?

on pc and my vega is in usb debug

same ad "add.thebad " devices not find
my i hav been setup up adb

well done! pretty userfriendly - will link to this post

i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
hope that helps...
mirror1: clockwork_recovery_3.0.2.4_vega_noflash.zip size: 73M (76109336 bytes)
mirror2: clockwork_recovery_3.0.2.4_vega_noflash.zip md5sum: 4d8cf9aa85331e8e2673b3406646fbc5

fung58745 said:
on pc and my vega is in usb debug
Click to expand...
Click to collapse
fung58745 said:
same ad "add.thebad " devices not find
my i hav been setup up adb
Click to expand...
Click to collapse
odd, does the vega show up if you do "adb devices"?

mad-murdock said:
i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
Click to expand...
Click to collapse
o yeah, that speedy download is nice i will put in first post thanks.
i have merged mac and linux as well attatched to first post
i will pm

same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.

fused#1 said:
same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.
Click to expand...
Click to collapse
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7

fused#1 said:
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7
Click to expand...
Click to collapse
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list

add.thebad said:
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list
Click to expand...
Click to collapse
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)

fused#1 said:
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)
Click to expand...
Click to collapse
hmmm, a little confused by this one. mines works correctly and shows up under adb devices but mine shows up as android composite adb interface
try an install like this
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
i think that should set it up right
have you used the vega and adb before?

Thank you. I will try that right now. Used adb with a desire until today.

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

very interesting Hashcode,thanks for the information :good:

Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.

Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped

esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.

Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!

AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.

seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail

AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now

Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked

Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.

seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?

Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide

AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle

How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed

dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode

PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!

You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

ADB Device not found, HELP !!!!!!

Hello, Today i have installed Cyanogenmod 11. But after rebooting i connected my mobile to PC and in command prompt
i gave a command " adb devices" and the list is empty. :crying: This happened after flashing CM11. HELP !!!!!
I can access internal memory as a media device.

Did you enable the ADB?

cyrus_ae said:
Did you enable the ADB?
Click to expand...
Click to collapse
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB

dubidu said:
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB
Click to expand...
Click to collapse
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .

srujan21 said:
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .
Click to expand...
Click to collapse
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?

deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
Its working, Thanks

ADB Device not found
deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
i had same problem, plz help me

vardhanram said:
i had same problem, plz help me
Click to expand...
Click to collapse
The thing you are quoting is solution my friend. It also has a question if solution doesn't work. Please answer that

I get the error "device not found" in adb shell when I type a command

Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.

KodRoute said:
Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
Click to expand...
Click to collapse
Whats your device?

LS.xD said:
Whats your device?
Click to expand...
Click to collapse
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.

KodRoute said:
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
Click to expand...
Click to collapse
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders

LS.xD said:
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
Click to expand...
Click to collapse
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.

KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
May you press "thanks" for my posts if i helped you ?!

KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
Doh! I hate when that happens. It's always the little things.

Question ADB TCPIP mode w/o cable

I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. The Tasker trick is waaay too complicated, and I couldn't make it work on my Pixel 7 Pro.
When root is available, things look simple: run "setprop persist.adb.tcp.port 5555" or modify /system/build.prop to include a line to that effect. Assume that I go to the trouble of rooting my phone, and make the requisite change in /system/build.prop, will I be able to un-root afterward while keeping the change I made intact?
Edit: here's a wild thought: maybe I can actually tinker with the official Android factory image, hence add the requisite line to /system/build.prop in vitro, as it were, repackage the whole thing as a modified image, and then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?

Aqua1ung said:
I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. (...)
Click to expand...
Click to collapse
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

ze7zez said:
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.

Aqua1ung said:
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.
Click to expand...
Click to collapse
Are your tools up to date? What is the output of:
Code:
adb version

Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb

Aqua1ung said:
Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Click to expand...
Click to collapse
Update your tools, you should be on 33:
Code:
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as /usr/lib/android-sdk/platform-tools/adb

I have a script for that, I forgot to include it...
Edit: can't attach it for some reason, anyways, here's a link to my git: update_platform_tools

Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service

Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
Do you have your phone and PC connected via wifi to the same router?

ze7zez said:
Do you have your phone and PC connected via wifi to the same router?
Click to expand...
Click to collapse
Same router, yes, though my PC is on a wired connection.

Aqua1ung said:
Same router, yes, though my PC is on a wired connection.
Click to expand...
Click to collapse
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.

ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
I was about to see if I could do that, lol, my box is wired as well

ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?

Aqua1ung said:
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?
Click to expand...
Click to collapse
As for things you can do with root, I have nothing to offer, in fact, I am totally against it. It just causes unnecessary problems with the device.
However, you *may* be able to modify the stock rom with an Android ROM Kitchen, emphasis on the "may".

Aqua1ung said:
(...) then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?
Click to expand...
Click to collapse
So what's would the point of OTA file signatures if anyone could modify the original ROM with dangerous changes?

Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
It worked fine for me after killing adb ($ adb kill-server)

Tasker and LADB app are working on my P7P perfectly, no cable required, no root - more info here.