The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
Related
When will it arrive?for 101 i mean
It won't happen until we get permanant root. No telling when that will happen.
a better question is, when will root be available, doesn't seem we have people with the right skills interested on the 101
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
adb push root/rageagainstthecage /data/local/tmp
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
./data/local/tmp/rageagainstthecage
Click to expand...
Click to collapse
It should kick you out and display some messages on the screen...just not errors. Then type:
adb shell
Click to expand...
Click to collapse
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
jerdog said:
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
It should kick you out and display some messages on the screen...just not errors. Then type:
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
Click to expand...
Click to collapse
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Tsusai said:
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Click to expand...
Click to collapse
Maybe have something to do with newer ARM architecture?
Sent with my fingertips and voice on my Evo
Why do you need permanent root?
Archos kindly released SDE which provides a way to install your own builds in dual boot.
Some links for more info:
http://forum.xda-developers.com/showthread.php?t=871335
http://www.openaos.org/
IRC #openaos on freenode
Maurice
The SDE require booting in recovery mode, and people said that it's often not perfect.
A permanent root for main OS would still be very useful, and still allow us to dual boot when we need to..
I think so too. PermaRoot would be very usefull.
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
This thread has been deleted.
This thread has been deleted.
This thread has been deleted.
***** really really really reserved*****
Working w/ Root on a Mac (OSX Yosemite)
CONFIRMED: This works using AT&T (SM-R750A), OSX (Yosemite), VirtualBox and Windows XP. See this link for the driver setup I used on my Mac.
http://www.onebadkid.com/?p=6930
I also find that after factory reset, I still have root! Great job!
---
Also, I haven't been able to get the scripts to work in the virtual machine so I've just been "pushing" the files manually. I did open up the scripts to get the destinations for the various files, so thank you OP. Also, you have to have the Tizen Wearables SDK installed and then use SDB commands in the terminal.
Remember, when using SDB on a Mac, it's: ./sdb [command] (you have to use the "dot-slash")
./sdb devices (to show whether or not your device is connected)
./sdb root on
./sdb shell (puts you into the device's shell so you can navigate the device in a Darwin/Linux terminal)
./sdb push [/full path of the file you want to upload to the device] [/full path of the desination]
I usually open up three Darwin/Linux Terminals on my Mac. One to use to navigate my watch in shell, the other to run the ./sdb command (just like in Windows, you have to run SDB on the mac from within it's home location: "/Users/[you]/tizen-wearable-sdk/tools"), and a third to drop files into so I can quickly see their full file path/location.
"PWD" = print working directory so you can use that in the Darwin/Linux Terminal so you don't get lost.
I'm using Windows 8.1 (don't know if it matters) but after updating to this driver my PC no longer recognized my Gear S. Had to roll back to previous driver.
Ohhhhh!!!
ohh SO installing these and getting it ready for the rest
Edit: got rootfs.img odin'd in so now i wait lmao
Wondering
Good write up so far. I had already gotten root from the previous thread with horrible direcions. LoL After I got my replacement gear s (ALWAYS CHECK YOUR SIM COVER), I rooted it using the bad direction method again (luckily I already know how to do these things), but your directions are very clear cut and noob friendly. You're doing a huge favor to new comers who come looking to root their gear. Hopefully they don't brick them before they find this.
cipherswitch said:
Got any request for certain alarms, notification sounds or ringtones? Shoot me a PM and I will get through them as fast as I can and repost here.
No themes as of yet, but I will definitely be working on custom clock faces apart from everything else
Click to expand...
Click to collapse
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Do this
sdb root on
sdb shell
chmod +x /bin/setup-folder.sh
./bin/setup-folder.sh
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
cipherswitch said:
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
Click to expand...
Click to collapse
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
new rootfs uploaded as of 12/17/14 8:42 am est, I also updated the link in the writeup.
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Megaflop666 said:
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
Click to expand...
Click to collapse
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
You'll be fine!
You will be fine. I've been able to restore from this screen using stock.
Um actually..... its easier. Connect your gear, drop your content into the right folders (eg; ringtones, alerts and such) and run the update script. done and done.
ipstack said:
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Click to expand...
Click to collapse
sbrownla said:
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
Click to expand...
Click to collapse
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Megaflop666 said:
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Click to expand...
Click to collapse
Hm ... what was it doing when you tried to flash?!
I was working on changing some permissions, rebooted it and it never came back, don't even have recovery. From what tmo said, this has happened to other people on this watch
Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
romfury88 said:
Got an Oppo R9s through aliexpress. First time it arrived the home button wouldn't work, neither the fingerprint scanning. After sending it back and waiting three months I got a working device, but seems to have malware on it.
The lock screen is filled with chinese pictures. Doesn't seem malicious, but I can't remove it. After resetting the device to factory settings it's the first thing that installs itself after giving it network access. The wallpaper option in settings doesn't work. More importantly, when I add a phone contact, the phone app crashes opening as well as the contacts app, which renders the phone completely useless, not being able to make a simple phone call. Also, simple mode doesn't work either.
So my guess this is a modified rom to have some malware always present and basic functionality is either removed or crippled. Following instructions to enter fastboot mode (volume up + power on) seem to enter an endless loop, so it looks like this option is disabled. Using volume down I'm able to enter a recovery mode, where it says it's version 1.2 (root), and allows me to select some rom for flashing.
Before trying to wade through all the threads regarding rooting and flashing, I was considering simply replacing the ColorOS rom with a clean one. However I'm unable to find any for R9s, is it that this model doesn't have one available? Even looking at the international Oppo forums they don't have any R9s download links. So I guess I have to spend some hours reading and fishing links from long threads like https://forum.xda-developers.com/android/help/oppo-r9s-rooting-t3496781 ?
The about info of the device says this is an Oppo R9s, ColorOS v3.0, Android 6.0.1, MSM8953 OctaCore, 4GB ram, build number R9s_91_A.28_191025, baseband version Q_V1_P14,Q_V1_P14, Kernel 3.18.24-G201710252140.
Click to expand...
Click to collapse
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
theashleyd123 said:
Are you trying to replace the ROM or just remove the Malware? I've never heard of this device before so I can't point you towards any ROMs, But I can certainly help you remove Malware embedded in the ROM.
Click to expand...
Click to collapse
I'm not interested in changing ROMs, just remove the malware that prevents normal device usage. That's why I was asking for links to ColorOS firmware, I presume reinstalling those would restore normal operation. However if that's not possible I'll take any non-malware ROM.
I followed the recommendation from http://community.oppo.com/en/forum.php?mod=viewthread&tid=50113 to use "adb shell" commands and disable ROM programs, finally getting to remove the lock screen pictures. After a while of having the phone turned on, I heard a weird ping sound and then the touch screen stopped responding. It works fine, since I can power off swiping to the right on the off screen, or I can swipe down and play with the toggles, but the launcher and settings app don't seem to receive touches. So maybe I disabled something affecting the screen? I did run:
adb shell pm hide com.android.browser
adb shell pm hide com.android.contacts
adb shell pm hide com.oppo.usercenter
adb shell pm hide com.nearme.gamecenter
adb shell pm hide com.nearme.atlas
adb shell pm hide com.nearme.statistics.rom
adb shell pm hide com.oppo.launcher
adb shell pm hide com.oppo.market
adb shell pm hide com.oppo.music
adb shell pm hide com.sohu.imputmethod.sogouoem
adb shell pm hide com.redteamobile.roaming
adb shell pm hide com.redteamobile.virtual.softsim
adb shell pm hide com.coloros.lives
adb shell pm hide com.nearme.themespace
adb shell pm hide com.nearme.themespacelib
adb shell pm hide com.coloros.pictorial
Rebooting or recovery mode doesn't work, so I figured to install a ROM from https://forum.xda-developers.com/showpost.php?p=70366156&postcount=13 in recovery mode (where the touch screen works fine). After installation the "optimizing android apps" kept there forever, so I turned it off/on manually, and now I launch into the original launcher with a few chinese icons, but still the screen doesn't seem to work.
Touches work for the notifications and such, but nothing for the launcher or settings, so now I'm unable to turn on USB debugging to send adb shell commands. :crying:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
Also try reenabling the input method.
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
romfury88 said:
theashleyd123 said:
You've disabled your launcher and a couple of required android services (Browser etc) Use adb again to sideload a new launcher too.
I did these after installing replacements, like that post explained. Chrome as browser, Google APKs for contacts/calendar, Novo launcher instead of stock… and everything seemed to be working fine.
I can't enable debugging on the device, adb commands don't seem to reach the device. I've never used sideload before, does it work even without debug mode enabled?
Click to expand...
Click to collapse
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
theashleyd123 said:
romfury88 said:
You can sideload an app via recovery by pushing it to /system/app
And then use adb shell chmod 644 "/system/app/APKNAME"
Click to expand...
Click to collapse
I can't due to adb not being able to connect to the device, since I can't put it in debug mode. When the device is in recovery mode I can't access it either, I only get "- waiting for device -"
Click to expand...
Click to collapse
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
$ adb shell pm hide com.oppo.music
Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS.
Click to expand...
Click to collapse
romfury88 said:
Finally managed to flash a good original ROM on the device. Conveniently the chinese rom prevents running dangerous adb commands, but at least I seem to have gotten rid of the malware and I'm able to change desktop wallpapers and the lockscreen magazine
Click to expand...
Click to collapse
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Oppo R9S
ulyong23 said:
hi romfury88 how did u manage to flash original ROM can u guide me pls. thanks
Click to expand...
Click to collapse
Just bought an OPPO R9S and was wondering you managed to flash the original ROM? I have the exact same issues that romfury had.
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?