Related
I've gotten a few questions about how to run apps on the Nexus Q, so I figured I'd make some sort of post giving instructions, at least basic ones.
1. Enable USB debugging on the Q. This is done by running the nexus Q app on another device, pairing with the Q, and then going to advanced and enabling USB debugging.
2. Installing apps is done by running
Code:
adb install path/to/app.apk
in the command line on a computer.
3. launching apps is done in command line by running
Code:
adb shell
, then typing
Code:
am start package.name/.Activity name
. For example, opening settings is done with
Code:
am start com.android.settings/.Settings
once in adb shell. Netflix is
Code:
am start com.netflix.mediaclient/.UIWebViewActivity
, and Angry Birds is
Code:
am start com.rovio.angrybirds/com.rovio.ka3d.App
. The package/activity names can be determined by running the app on another android device, plugging it into a computer, and running the monitor tool in terminal and looking at the hierarchy viewer.
4. XY coordinates for touch/drag events can be given to the device by using the monkeyrunner tool (documentation can be found on the android developers website). For a brief overview:
start monkeyrunner (located in android-sdk/tools/)
Code:
from com.android.monkeyrunner import MonkeyRunner, MonkeyDevice
device = MonkeyRunner.waitForConnection()
device.touch(x, y, MonkeyDevice.DOWN_AND_UP)
device.drag((startX,startY), (endX, endY), 1, 10)
device.press('KEYCODE_BACK', MonkeyDevice.DOWN_AND_UP)
I realize this isn't very complete, but I'll add some stuff to it as I play more.
Thank you for posting this, this clears up a couple of my questions
This might be handy : link
So theres no UI for the apps? You have to memories each apps command string?
That sucks. lol Is there any chance of a UI in development or a launcher for the apps?
That seems excessively complicated to run for example angry birds with quite an extensive com string.
Agreed, it does really suck to have to use console commands.
Well...lets just say I'm working on something. It may take a few days before I know whether it'll actually work, but I'll let you know.
Why not install the VNC application for droid
in order to run the VNC server on your nexus Q and then use your tablet or other touch enabled android/computer/device to control the Q interface
http://code.google.com/p/android-vnc-server/
https://play.google.com/store/apps/details?id=org.onaips.vnc&hl=en
https://play.google.com/store/apps/...t#?t=W251bGwsMSwyLDEsImNvbS5zY2h1bWkudm5jcyJd
this is just an idea considering you have root the app shouldnt be hard to set a call to on some kind of init.d script path
i think it would serve well for navigation
it's basically identical internals to the galaxy nexus, with some extra hardware outputs, so you can port over a custom rom for galaxy nexus and use that as the UI for now
UKROB86 said:
it's basically identical internals to the galaxy nexus, with some extra hardware outputs, so you can port over a custom rom for galaxy nexus and use that as the UI for now
Click to expand...
Click to collapse
What your saying does make sense, so I'm willing to give it a try this weekend. I will port over the same ROM I have on my VZW Galaxy Nexus (Stock Jellybean 4.1 from Rootz Wiki). In order to do so I will need just a little bit of help... My Q is already rooted, so you can just provide me with a walk thru outlining how to push/port the ROM over. Do I have to hook it to the pc again and start the bootloader with adb or what exactly? Thanks for the help in advance.
You can install droidmote server on nexus q and control it with your android phone.
with droidmote server you simulate a mouse a keyboard a multitouch touchpad etc. etc.
you can play, in remote,also with games that support only the touch screen
...
Today, I finally have found where to post for newbies, so I post, thought 4 hours ago I posted on androidforums.
Here is very difficult to operate with this site, and to use this site for with android devices is quite impossible. Only in windows, and not every comfortable. Anyway, I see, that is the first university on the net
Click to expand...
Click to collapse
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
lovestudio said:
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
Click to expand...
Click to collapse
I am sorry, so no one knows, on 3 sites, no one knows. let me know, then I shall not check every hour this post. I t`s better to know, that nothing possible, that believe that smth. is possible. thanks.
Hello all,
Mirroring through miracast works fine now! I managed to fix the issue I faced with trying to mirror the phone with miracast.
The phone I bought from China came with apparently some manually altered rom. It didn't have much of the bloatware of the Nubia stock firmware. Also, it did not come with the "screen projection" app of Nubia. This app seems to be integrated into the phone. I couldn't find any .apk of it online. I tried a bunch of different apps, none worked. Also, factory resets, did not reinstall that app either.
The solution was simple. I used TWRP to wipe the phone and install the latest (v2.23) rom from the official nubia website: http://ui.nubia.cn/rom/detail/56
After installing it, the app was there and worked instantly.
At the moment now I have some issues with TWRP. I will fix it and see if the build.prop presisted through all of this, I doubt it.
If it did, and any changes are still required, I will update the post.
Kind regards,
Rup7ur3
---- initial post ----
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). Currently when I try mirror with the use of wi-fi direct, it doesn't show the miracast dongle I use (anycast).
I've not any experience in this and am trying to google for solutions. Online I have found some answers, but it's not yet working.
Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.adb.notify=0
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=0
Click to expand...
Click to collapse
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
Miracast is available on Android devices with Android 4.2 Jelly Bean
Click to expand...
Click to collapse
and
no more supported by Android since 6.0
Click to expand...
Click to collapse
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
#property to enable VDS WFD solution
persist.hwc.enable_vds=1
# Add by ztemt for ZWfd begin
#property to set wfd output resolution is 1080P(0) / 720P(1) / 960*540(2) / 800*480(3)
persist.sys.wfd.zte_resolution=0
#property to show wfd sink false(0) / true(1)
persist.sys.wfd.zsink_support=1
#property this is device support wfd 1080p output support(true) not support(false)
persist.sys.wfd.1080p_support=false
# Add by ztemt for ZWfd end
Click to expand...
Click to collapse
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
rup7ur3 said:
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). I've not any experience in this and am trying to google for solutions.
I have found some answers, but it's not yet working. Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
and
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
Click to expand...
Click to collapse
Never try downgrading this phone. It's a nightmare because it's using AVB2.0 which was introduced with Android 8 I think. So getting that to work would be extremely difficult. What I'm not sure about is if nubia is doing anything different from other vendors as, judging by the source code, it looks the same as Sony for example (actually that's no wonder since they got 70% of their code from Sony).
What's difficult about this is that they define custom, vendor and device specific values as you can see with the Z9 build.prop. I'm not that well versed in Android actually and mostly just learning all this stuff by experimenting right now, but I would say your best bet would be some tool that scans a system for possible values in build.prop. However I'm unsure if such a tool exists unfortunately..
Sorry I can't be of more help as of now. I think Lineage is supporting Miracast though? So once I got that to work, it might be an option for you
Nubia z18 support screen cast without internet.
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
jagdishgeb said:
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
Click to expand...
Click to collapse
Thank you for the response, great to hear that it is possible! Did it work immediately?
Also, if you don't mind me asking. Could you maybe check if there are any default screen projection / sink apps pre-installed on your z18?
Mine came without any. I will try reinstall stock to see if that helps. All apps I use go to this screen: https://imgur.com/a/Otf1YO0
Online I read there are supposed to be options to enable wireless display in there. However, I think Nubia disabled it in their UI.
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
I acquired a used Outcome Health (Contextmedia) Wallboard. There have been other posts previously about unlocking the 10 and 13inch tablets, but the steps and procedures used did not work with this wallboard.
The model number is P-WAL-107-ELC-02, and is similar to the item found here: https:// fccid.io/ 2AI6X-PWALELC
It is running on Android 4.4.4
I can open the "secret" configuration menu built into the app, but all the functions are password protected. I've had no success accessing the default android settings menu either. If you close the app, it launches again immediately, and the status bar seems to be locked down so that it can't be expanded.
EDIT: I've tried using a USB keyboard, and used the settings hotkey but no luck with this either. Using the home button pushes a message at the bottom of the screen "Override Launch." I also tried generic passwords in the various menus, but nothing has worked so far.
Any suggestions or experience with these items is greatly appreciated, thank you!
Click to expand...
Click to collapse
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
Flash your recovery image via adb shell on android
JANUARY 16, 2017
//edit: You need a rooted device for this kind of flashing
Hi, ever wondered about how you can flash a recovery.img via adb shell?
A lot of posts suggest flashing it via fastboot. Well my ****ty Samsung phone is not detected by fastboot. Then there is the option to install a dubious binary file which is called flash_image.. thank u internet!
Well damn I have the recover.img whats so hard to use dd and flash it with a single shell command? For those who don't know much about linux commands here we go;
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
Click to expand...
Click to collapse
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
jwrezz said:
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
Click to expand...
Click to collapse
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
slaysher62 said:
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
Click to expand...
Click to collapse
That would be awesome.
Sent from my LM-V350ULM using Tapatalk
bump
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
I am having the same issue
Any further update or progress on this from anyone? This would be perfect for a garage (or wherever) media center.
Any idea where I can find the recovery file? I tried to obtain one via TWRP and no luck.
I was able to install nova laucher and delete the files in data using adb shell. I'm just stuck at the recovery image part.
---------- Post added at 01:11 AM ---------- Previous post was at 12:20 AM ----------
Freak-tab .de website is down. Can someone please send me the image recovery file? Thanks in advance.
slaysher62 said:
bump
Click to expand...
Click to collapse
I'm able to get mine to the Recovery System but I cant run adb shell as I get exec '/system/bin/sh' which is no root. But I can't get into Safe Mode. I have the 32" Wallboard too but mine is ELC-01. What power button combo did you use to get into Safe Mode?
Plug in power and then just mash the power button? When do you stop mashing it?
Mash it as you plug in power and keep mashing?
Plug in power as you hold the power button down?
Stop mashing when it flickers or the screen is white?
Can’t get in to the settings.
ttiimmmmyy said:
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
Click to expand...
Click to collapse
Can’t get into settings. Tried the power button variations, with and without mini usb plugged in to the pc.
Wallboard
There are some typos in the original post commands. I wasn't having any luck with the "rm" commands to remove "zygote" and "sysop" apps, so I used the "ls" and "cd" commands to see what the file names were.
Removing the second file should be "[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]" , the third should be "[email protected]:/ # rm -r data/data/com.contextmediainc.system.sysop"
When you type the command "DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV" you'll get an output, type that output into the next command. ex: dd of="output of previous command".
If you just drop the TWRP onto the USB mass storage drive that appears when you connect the tablet, it will be in "/sdcard" folder. The final command will be something like: dd of="output of previous command" if=/sdcard/RK32.img. If you don't have root access it will tell you "permission denied", so make sure you use the command "su" after "adb shell".
Lastly, I accidentally found that when I performed a factory reset via TWRP recovery menu that the Home button started working. It may also work via the settings menu, but I didn't try it that way.
Anyway, hats off to OP for posting this as it gives use to these massive android tablets.
The secret password is cat10dog
Kinda stuck...
Hey Slaysher62. I'm kinda stuck. Was wondering if you could help me out. I have a few of these due to our hospital just not needing them anymore and telling me I could either keep them or throw them away. I've tried for weeks to replicate your success but I feel like I'm missing a few steps. If you could Message me or something that'd be great.
Thanks,
Pinball Wizard
slaysher62 said:
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
Click to expand...
Click to collapse
Help with recovery
Recently acquired 3 of these 32-inch screens at first I wasn't able to get into safe mode but I deleted everything off the sd card and restarted the screen after that spamming the power button worked and I was able to get the app uninstalled and Nova launcher installed but what I'm having an issue with is getting TWRP to install also I noticed mine isn't a RK3288 its a RK3188
I've tried to flash all the TWRP RK3188 recoveries I could find but none of them work just puts the screen into a boot loop until removing power and restarting
any update from android 4.4
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Uit232b-u03
Thought I'd chime in; I have one of these wallboards, model # UIT232B-U03, nominally equipped with an RK3188. Here's what I've found:
Misc. Device Info
RIL Ver: KitKat ril-rk29-dataonly v3.3.00
Build No.: Z05-outform-32-B4.21-20160324
Build Fingerprint: rockchip/rk3188/rk3188:4.4.4/KTU8Q/eng.root.20151208.162319.eng/test-keys
Board / Chipset: rk30sdk / RK30board
As you might notice from the Build Fingerprint, this model appears to be running an engineering build of Outcome/ContextMedia's KitKat ROM; this screen was pulled from a working clinic, but USB debugging was already enabled and connecting via adb shell automatically dumps you into a root shell. There's nothing more you need to do to gain that access.
The device info (courtesy of Droid Info) references three different RK chips in a few places: RIL Ver. (rk29); board & chipset (rk30); and everywhere else (rk3188, specifically). I don't know what to make of that. Maybe something to do with it being an engineer build? Could be an engineering sample board, too -- I need to check for that info.
Personalization
As mentioned, it looks like this unit (and maybe other UIT2xx-xxx revisions) appears to come pre-rooted with USB debugging already enabled. There's no need to authorize any given machine on the tablet when connecting over ADB for the first time, either. If you still want/need to access the system settings, three-finger-tap on the application logo in the bottom-right of the screen (tapping multiple times will just cause a credits list to pop up). The password to leave the application for the Android system settings is cat10dog, as has been noted elsewhere.
Before I loaded anything new, I went ahead and factory reset it to see what it looked like. Upon doing so, the only system application was Zygote -- it looks like it's a modified version which is serving as the "launcher" for this tablet, and which forcibly reloads the application whenever it is closed for whatever reason. From factory reset, it will launch into a first-time setup screen, where it looks like you can configure the application and get connected to wifi/ethernet and download the remaining system apps (this is my impression; I didn't go through with it, but I imagine the application will want to verify a license or something). Uninstalling the modified Zygote seems to not kill the first-time setup screen (makes sense -- it's meant to stay resident and likely has everything it needs loaded into RAM at the time), but you can install Nova Launcher 5.3 (last version to support KitKat 4.4.4) and then Zygote fully disappears and you won't get bothered about setup anymore. (I have no idea what happens if you remove Zygote and then don't install a launcher. You can probably still connect over ADB, but I've never seen a launcher-less Android.) Other apps can be installed at this time, too.
As noted elsewhere, the Home and Recents soft buttons still do not work. I'm not 100% sure, but I think that's something stuffed in the ROM itself and may not be configurable (maybe through the commandline?). But, you can just use the Back button to go back to the home page at any point.
I have not had any success installing TWRP: It turns out, despite the chip being labeled in all ways as an RK3188, it is in fact a lower-specced RK3188T (1.4Ghz top speed). Every version of TWRP for the RK3188 I've tried has resulted either in a bootloop (unplug from power and plug back in to return to system), or a black screen, or the TWRP splash screen but which never progresses beyond that step. (This reminds me, I need to check on the black screen instances to see if the recovery executable is running at all, and what happens when I try to manually start it.)
On the off-chance anyone has a TWRP build for the RK3188T for me to try, I'd definitely appreciate it! Or indeed any ARMv7-based build, if I'm just going to be blindly loading recoveries to see what happens. (If anyone has any advice for debugging the recovery loading process, I'm rather a noob at this and could use any information about where to look for logging info, or to make it output a log at all if it doesn't by default.)
OH, and uh... if anyone has a stock version of the recovery partition, could you send it to me? I didn't back it up before writing over it...
Other than not getting to install TWRP and get all experimental with ROMs, it is usable in its current state as an old-but-servicable, pre-rooted-for-your-convenience-no-supersu-required, massive Android tablet. Too bad Pocket Camp requires Android 5 since a few builds ago...
Edits for grammar, spelling, extra info.
theugly_bear said:
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Click to expand...
Click to collapse
device configuration and also just to clarify what he meant was tap on that flower looking logo repeatedly until you get the secret device configuration then on top right corner theres 3 lines select network settings and it should ask for a password which is cat10dog
And now I'm stuck
If anyone could give me direction/etc to get past where I'm at, I'd appreciate it.
I bought one of these bad boys from an auction and thankfully found this post and started the task of customizing it. I got to the point to where I deleted the apps listed, all through adb reboot recovery (used Generic RK32 with SDcard).
However, on reboot, it didn't go into recovery and had the Context Health splash to a nature backdrop and an Error: Wallboard not installed message. USB debug wasn't persistent, and trying everything that worked previously, I can't seem to get into Safe Mode, and I haven't found any other ways to get into Settings.
I did find the "reset" hole on back, which otherwise functions as a hardware 'Volume Up', but have yet to find any [Boot to Recover] methods involving only Volume Up and Power that work.
Any ideas of things to try?
Thank you
Update 1: Still no luck overall, but somewhat of progress, I hope: Plugging in the DC automatically boots up everything. If I hold down the hardware volume up/reset while adding power AND have USB plugged in, I get a listing in Device Manager; however, the screen stays black. Otherwise, as far as getting my PC to notice it, this is the only means to do it. There is no connection when powered on normally, rather I plug in USB before or after providing power. Also, spamming the power button while booting in order to get into Safe Mode had worked initially. Now doing it causing a freeze on the second or third splash screen refresh.
So I have recently acquired a bunch (50+) of these 32" screens. They were pre-rooted as @dwkindig had mentioned. I was able to remove all of the Context media apps and unlock the functionality as a basic android tablet pretty quickly. Threw Nova launcher on it and they work great. Has anyone had success in getting anything above Android 4.4 on these? I have a ton and can pull any files that would be of help to do some digging here, so please let me know. I would love to at least get Lollipop on these so that Android Webview could be upgraded and I could use the Wallpanel app for dashboard use on these. Any suggestions or help I can offer?
This guide is from: https://www.gizdev.com/repair-imei-snapdragon-device/
WARNING: Changing your IMEI to a value that corresponds to a different handset is a CRIMINAL OFFENCE. Use this guide only to restore your ORIGINAL IMEI where it is overwritten.
This guide CANNOT HELP YOU if your ESN and MEID are blank. If you know these values, you may be able to restore them with the QPST toolkit - use the diag steps in this guide to allow your handset to communicate with the QPST tools.
Background:
It is possible to accidentally wipe your IMEI information - either through a misconfigured ROM/Radio, or through wiping modemst1/2 for whatever reason. Wiping your IMEI ensures that your phone will never connect to an operator network (or ISP), meaning phone calls, text messages, and mobile data are inaccessible.
Good news! All is not lost. The Axon 7 is a Snapdragon device, with two sim slots. This means it falls into the family of devices that are easily fixed.
You will need:
All downloads, apart from LineageOS SuperSU, are also available at the bottom of this post
I have not tested these downloads. You are responsible for their contents. Keep your system up to date and protected.
- The addon/fastboot tools contained within this post. Download here - you may have other tools, but this version is confirmed to be working.
- The "WriteDualIMEI" tool. Download here
- The Qualcomm ADB drivers - you probably already have these installed, but here is a driver anyway. I BEAR NO RESPONSIBILITY FOR THIS DRIVER. Download here
- A rooted device. If you're on LineageOS, use the LineageOS extras here. Remember, the Axon 7 is an ARM64 device.
Process:
- Make sure you have at least your primary IMEI to hand. Copy it into notepad and check it for errors.
- Connect your phone to your PC. Ensure Android Debugging is enabled.
- Open the folder in which you extracted the ADB toolkit. On Windows, shift+rightclick, and select "Open Cmd Here"
- Type the following into the opened command prompt. Take note of the .exe - this ensures we use the ADB executable in the folder, and not the one in your $PATH.
Code:
adb.exe shell
su
setprop sys.usb.config diag,adb
Note also that between diag and adb exists a comma, not a period
- Now is the time, if you have not already done so, to install the Qualcomm driver.
- Open device manager, and ensure that you have, under COM ports, a ZTE device in Diag mode.
- Open the WriteDualIMEI application and make sure that the COM entry matches what you have in Device Manager. If it is blank, something has gone wrong and you should start again - including disconnecting and reconnecting your phone.
- Copy and paste the IMEI numbers you wrote down earlier into the IMEI1 and IMEI2 fields respectively.
- Click "Start". The process shoudl take no more than a millisecond. Success is delineated by a green square on the right hand side fo the window, with "PASS" in black font in the centre.
- Restart your handset. Check your IMEI values by visiting settings, or entering *#06# in the dialler.
RMX3363
How can i erase imei fastboot way?
Bootloader is unlocked & phone is rooted.
Do you know if this method is applicable for Asus Zenfone 8 Flip which has
Qualcomm SM8350 Snapdragon 888 5G?
I tested it on my mi note 10 pro, everything went well and at the end I got green PASS. But the imei number was not updated after the restart.
So didn't worked for me
At first, thank you for the great work, you did most of it and I only would like to add a small but necessary thing at the end. I could see most persons here couldn't make this work on their devices. I was one of them for the first few hours but then it struck me and I solved it. I am penning down the process as much in detail as possible as to where it went wrong for most of us and of course the fix:
In the adb shell after you put the command - setprop sys.usb.config diag,adb, ideally a ZTE device in Diag mode should have appeared under COM Ports in windows Device Manager. But, for most of us it was an unknown android device with an yellow exclamation showing something is wrong with the driver. Windows wouldn't update the driver and it is not available from the internet i.e., not easily. And hence without the driver the connection failed every time.
The Fix: Download Snappy Driver Updater for windows. I am running windows 11 Pro and it worked fine with mine, so I am guessing it would work fine for everyone. After you've downloaded it, run the updater after you have given all commands through the adb shell i.e, setprop sys.usb.config diag,adb and now scan through Snappy. If your device is uptodate in all other areas, snappy will find the missing driver which is causing the yellow exclamation android entry, and install it in a few minutes. After that just follow the above guide. It should be a success. The IMEI would be written and every functionality would be restored. I could verify the same on my ZTE Blade S7. Worked like a charm. Thank you again. All the best