Anybody have one of these? I recently got my hand on one, and the estation c1650 printer also, and wondering if there is anybody else with on, would like root, and or wipe the device and get ride of the stupid hp touchsmart UI. it would be a dream to run a galaxy tab rom or something. I though i saw a galaxy tab floating around? a system dump maybe? But any help would be appreciated.
HP Zeen
OK, I managed to use the latest Android (2.3) SDK usb drivers to get the windows to recognize the device. I could copy files to/from the SD card.
USB\VID_03F0&PID_9F11&REV_0223&MI_01
USB\VID_03F0&PID_9F11&MI_01
To get it to work, I had to edit the inf file at location:
"[SDK PATH]\google-usb_driver\android_winusb.inf" and add the following information:
;FOR ZEEN
%SingleAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&REV_0223&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&MI_01
ADB currently will not recognize the device. I'm not sure what's messed up. Calling HP now to see about proper USB drivers.
Zeen
OK, HP says the USB drivers for the zeen come with the printer and even though I plugged in the first time it didn't work, the second time it did and Win 7 recognized it as a HP zeen. Ran the disk install in between.
That said ADB still has no idea. Fresh eclipse SDK install. Any thoughts on how to get ADB to recognize it?
Let's keep this thread alive. I got the drivers installed with your help. Can't get adb to see mine either. There has to be something we are missing. I think this device is similar to the pandigital novel so I have been reading over there. I will keep working.
Apparently, some firmwares seem to disable "adb" service...
Nice to hear someone else is out there trying. I found the following in a different post about the galaxy s, tried it with the Z4root, and while the command seems to take, it didn't work to get ADB. I tried it on a couple of different machines, let me know if it works for you. Also, when I called HP about the drivers they (at least the support techs) didn't know squat about android. Not helpful.
"Apparently, some firmwares seem to disable "adb" service on the Galaxy S.
So in case you run into this problem (adb unable to see the device) what you will need is to modify /default.prop on the SGS.
Here is what I had originally:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
To enable ADB on SGS
1. Run on the device: setprop persist.service.adb.enable 1 to temporarily switch it on.
2. pull /default.props with adb and modify the "ro.secure=0" and "persist.service.adb.enable=1"
2. mount -o remount,rw rootfs /
3. push modified default.props back to /
In more detail:
1. Root your device (see FAQ sticky post)
2. Install shell emulator on the device
3. In shell emulator, enable ADB (not sure if you need to run "su" before that):
setprop persist.service.adb.enable 1
4. Now, you should be able to connect to the device with ADB (temporarily). If not, make sure your udev rules (for Linux: /etc/udev/rules.d/51-android.rules) are smth like:
SUBSYSTEM=="usb|usb_device", ATTRS{idVendor}=="04e8", MODE="0666"
5. To make the change permanent:
adb pull /default.props .
(this will copy default props to local directory)
6. Modify the two properties as follows:
ro.secure=0
persist.service.adb.enable=1
7. Re-mount the root filesystem on the device in read-write mode (requires "su" before that):
mount -o remount,rw rootfs /
8. Now overwrite the /default.props on the device with modified one:
adb push default.props /default.props"
Okay, z4root did give me root access. I installed root explorer and terminal emulator. I am trying to find adb wireless so I can see if we can adb into the device using that. I think if I can i can install the market on the zeen
RootExplorer
Got a link to the RootExplorer APK? When temporarily rooted, I tried to install the market APK and got the finger. Did you perma-root or just do temporary?
I don't know anything about wireless ADB. What's the story with that? (admittedly, I'm a developer but getting up to speed on hacking the thing open).
I dont think I am aloud to post the root explorer apk. Wireless adb is just supposed to let you use adb without plugging anything in. Unfortunately, it says my device isnt rooted when trying to run it. Im gonna keep playing around with it.
Hey can you try to run adb over wifi. Just hook up your zeen to wifi and your pc and run adb like normal, but when you first run it type "adb connect xxx.xxx.xxx:5554
replace xxx with your zeen ip address. See if it lets you connect like that.
all the zeen but the adb drivers are in the zeen itself your just useing and uncapatable cable so it wont install usb driver and masstorage ones with out the proper cable, the adb drivers you will only get when useing sdk tool and has to be in debuging mode and pluse it has to have the correct cords like useing a samsung usb with a motorolla usb and sry i faild english and hate typeing so to lazy to do spell check like any one else will u get my giff the adb driver will install same time sdk will just its kinda tricky getting access to them and makething them work, a good way to test is plug in your w.e droid and go to your cpu cmd window, and type adb shell if it finds you droid then your golden but if not then bad cable or not in debuggin mode and have to have sdk installed and packages installed that come with it....
untile you can take the h p block of the android makret it wil never install or wont install properly more or less a complete rom will come out in like 3-5 months with the market on it and idk if the printing app will still be there but trust me you wont get it but there are 3 other alterative markets out there and 4shared.com has not let no one down............
if you want the android market on the hp tablet for the zeen or any other tablet that people are haveing a problem get anything and don't like yam or black market or any of that b.s g0od t0 4shared.kom and download a apk file with the name applanet and you should install the version 2.7.3 and i tried all the other version some will install and some wont but so far this one install and has 92 percent of the real adroid market and looks just like the market i found everything from root explorer to romanger and every app i seen in my droid i found on there and updates trust me if you want a g0od makret, well i just gave you the answer, n0w s0me one make 2.2 work on this thing, i have one to donate, [email protected] for some work to be done
Thanks for the tip on the Android Market! I installed it on mine and it works
How did you install market?
Sent from my Desire HD using XDA App
Anyone still working on the some development for this device? Thanks in advance!
There are various threads around xda with people trying bits and pieces. Slow progress though!
Okay thanks.
anthonbob said:
Anyone still working on the some development for this device? Thanks in advance!
Click to expand...
Click to collapse
Yes I will continue development after my exam will open in August an development thread to collect the knowledge of developers and not to sit weeks trying to get some information about the device and try to get adb working on Linux like I did
Gesendet von meinem Skate mit Tapatalk 4 Beta
Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great
Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Hi!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me... :crying:
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help. Good luck.
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.
So here's the thing; I still own a Galaxy Tab 2 that I hardly ever use. But having bought Panasonic Lumix GH3 I suddenly found it useful. The GH3 can only be completely controlled through a 'Lumix Link' app and Panasonic in all their (money making) wisdom decided to stop developing at 4.2.2 (Jellybean I think).
It appeared I had stopped upgrading the Tab 2 at cyanogenmod 13. I remember being happy that CM had by then created a complete ecosystem with automatic downloads and their own recovery image. Unfortunately right after that they stopped the development of all. And the recovery/boot image was no longer recognized by W10 1909. In weeks I found no way to get Odin to connect because the device simply wasn't recognized. Than I discovered ADB over wifi and that seemed to work!
After trying out a few nights, reading a lot of forum posts that would redirect me to a usb connection eventually all the time. But then today came the breakthrough.
1. .\adb root (once connected of course)
2. .\adb disable-verity
3. .\adb remount --> remount succeeded
4. .\adb shell rm /dev/block/mmcblk0p6
5. .\adb shell "dd if=/storage/6AC8-29A7/twrp.img of=/dev/block/mmcblk0p6" (having put the twrp.img on my sdcard)
35816+1 records in
35816+1 records out
18337808 bytes transferred in 0.921 secs (19910757 bytes/sec) was the result
6. .\adb reboot recovery
and it hangs on the black screen with the white letters "Samsung Galaxy Tab 2 10.1"!
Device not recognized through usb
And I realized I would have most likely done step 6:
.\adb enable-verity
No button combination brings me anything anymore unless there is a secret one left I don't know about.
Can any experienced android/ Samsung expert please tell me if I can throw away my device :crying:? Because I think so. But if there's any chance....
Edit: after a complete battery drain the tablet boots into system again. I tried my suspected method but to no avail. I need to get some SU installed and make sure it's rooted.
Try entering Samsung Download mode via RESISTOR TRICK and flash official tar via Odin if still needed. Get it from eg. from HERE.