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.
Related
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.
You can use ADB on unrooted devices to remove the "What's New" option from the NavRing and to remove the Small Apps Widget launcher from Recent Apps.
I will assume you know how to install and use ADB.
To remove the "What's New" option from the NavRing:
Code:
adb shell
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Make sure to reboot before proceeding if you're removing both items.
To remove the Small Apps Widget Launcher from the Recents screen:
Code:
adb shell
pm block com.sony.smallapp.launcher
pm block com.sony.smallapp.app.widget
exit
adb reboot
To revert changes substitute "unblock" for "block" in the command.
Good to note that these work just have to be run seperatley, i tried to block all 3 at the same time and it did not work you have to remove the whats new then reboot then remove the small apps then reboot again
Thanks for this OP i hate that whats new thing
aford89 said:
Good to note that these work just have to be run seperatley, i tried to block all 3 at the same time and it did not work you have to remove the whats new then reboot then remove the small apps then reboot again
Thanks for this OP i hate that whats new thing
Click to expand...
Click to collapse
Thanks, added to OP.
Thank you!
The what's new was really bugging me :-/
do you know if the block command does the same as "deactivate" would do from the Settings->Apps menu? (if it were enabled)
punshkin said:
Thank you!
The what's new was really bugging me :-/
do you know if the block command does the same as "deactivate" would do from the Settings->Apps menu? (if it were enabled)
Click to expand...
Click to collapse
I assume so, the "pm" is for the package manager commands.
I can not thank you enough! I still don't know what Sony was thinking with "What's New".
Favorite'd, I just know I'll be needing this soon enough xD
Working like a charm. Glad to have my recents cleaned up. Any other bloatware we can disable this way? Love to get rid of the walkman, sony app updates, movie, movie creator, etc
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Mr Sliff said:
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Click to expand...
Click to collapse
do adb devices, should be able to see your device listed. if it reads not autorized: unlock your lockscreen and confirm the dialog to give computer access.
cyphomatic said:
do adb devices, should be able to see your device listed. if it reads not autorized: unlock your lockscreen and confirm the dialog to give computer access.
Click to expand...
Click to collapse
Thats the weird thing, my device is listed when I do that.
ADB, SDK, JDK, JRE, USB debug, USB drivers: all set up correctly?
Thanks! worked perfectly for me, at least it did when I installed the Android SDK on my Windows partition instead of my Mac ... Really didn't want to work on the Mac side, nor is there a native way to transfer wirelessly from my Mac but everything works well on the Windows end.
Thanks again OP :good:
Can this method be used to disable the other system apps?
Mr Sliff said:
Im just trying to do this but when I type adb shell reboot it says device not found. It does say im in [email protected] though. Anyone know whats wrong?
Click to expand...
Click to collapse
Got the same thing before I found out you need to exit remote shell before you run reboot command (I'm new to using adb for anything other than push/pull)
So after:
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
phroenix said:
Got the same thing before I found out you need to exit remote shell before you run reboot command (I'm new to using adb for anything other than push/pull)
So after:
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Click to expand...
Click to collapse
Yea, you need to exit shell before running any adb command, I'll add that to the OP.
Alright for some reason it doesent remove whats new for me. Ive rebooted a few times and it doesnt work. Removing the small apps did work though.
Mr Sliff said:
Alright for some reason it doesent remove whats new for me. Ive rebooted a few times and it doesnt work. Removing the small apps did work though.
Click to expand...
Click to collapse
im getting the same thing. says the blocked state is true, then i reboot, still there
ikon8 said:
You can use ADB on unrooted devices to remove the "What's New" option from the NavRing and to remove the Small Apps Widget launcher from Recent Apps.
I will assume you know how to install and use ADB.
To remove the "What's New" option from the NavRing:
Code:
adb shell
pm block com.sonymobile.advancedwidget.entrance
exit
adb reboot
Make sure to reboot before proceeding if you're removing both items.
To remove the Small Apps Widget Launcher from the Recents screen:
Code:
adb shell
pm block com.sony.smallapp.launcher
pm block com.sony.smallapp.app.widget
exit
adb reboot
To revert changes substitute "unblock" for "block" in the command.
Click to expand...
Click to collapse
This whole thread is actually a repetition of what has already been discussed and suggested over here:
http://forum.xda-developers.com/z3-compact/help/deactivated-apps-getting-activated-t2889082
Can you use adb to get rid of the nav bar too?
oh Thankgod ! whats new and the quick launch widget are gone !!!!
Thankyou Thankyou Thankyou
ps; is there a list of commands to get rid of certain other apps, widgets, bloat etc ?
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?
I am trying to get a Nabi Big Tab 20" unstuck after a factory reset
I can get the device into Android System recovery
Code:
Android system recovery <3e>
KOT49H.WW.25.20150521-037-20
Volume up/down to move highlight;
Power button to select.
reboot system now
apply update from ADB
Update/Recover from USB Storage
wipe data/factory reset
wipe cache partition
I have installed Minimal ADB and Fastboot and the Nabilab drivers but can't get the device to fastboot so I can use a recovery image. I am only able to do
Code:
adb sideload <filename>
Any suggestions would be greatly appreciated.
Solution found
hexagon_founder said:
I am trying to get a Nabi Big Tab 20" unstuck after a factory reset
I can get the device into Android System recovery
Code:
Android system recovery <3e>
KOT49H.WW.25.20150521-037-20
Volume up/down to move highlight;
Power button to select.
reboot system now
apply update from ADB
Update/Recover from USB Storage
wipe data/factory reset
wipe cache partition
I have installed Minimal ADB and Fastboot and the Nabilab drivers but can't get the device to fastboot so I can use a recovery image. I am only able to do
Code:
adb sideload <filename>
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
Thanks to @AlaskaLinuxUser for posting the solution earlier this week (see the link below) I just wanted to add the solution here in case someone else found this post and was looking for a solution.
https://forum.xda-developers.com/an...overy-nabi-bigtab-hd-20-t3035372#post82928537
I found a simpler solution
I had the exact same issue (Fuhu servers shutdown, I didn't know this...performed a factory reset...locked out of tablet), but on a Nabi Elev-8 tablet (8" 1280x800, Octa-core Snapdragon processor, 32GB storage, NFC, Wifi, etc.).
I found a backdoor to get into the Android Settings menu, and enable developer options, and thus enable ADB. No TWRP/root required. With ADB, I was able to disable a bunch of Fuhu packages, which got around this problem, and got rid of a bunch of bloatware to boot. I posted this on stackoverflow, but cannot post a link. But here's the details in case it helps someone else:
Although the initial setup doesn't let you exit it, I found that if I hit the power button while in the WiFi setup, when I turn it back on it shows the Nabi lock screen. Rather than unlocking the tablet, you can actually get into the Android setup menu from the lock screen!
In there, I was able to enable developer options (yes!!!):
Settings -> About Tablet -> Tap on "Build number" over and over until it enables developer options
NOTE, tapping on other fields repeatedly also pulls up other hidden gems, like a hardware test, and an Android Easter Egg. Next, go to:
Settings -> Developer options
and enable "USB debugging"
Plug in your USB cable, and install "adb" (android debugger) on your PC. I'm using Arch Linux, so:
Code:
sudo pacman -S adb
did the trick. You might need to accept some RSA key security prompts on the tablet to connect to the PC. Now, onto the fun stuff...
The tablet is NOT rooted...so you can't remove any packages. However, you can disable them! I extracted a complete list of the "fuhu" packages, then tried disabling them one at a time. I found that by disabling most (except for a few exceptions) I was able to get rid of most of the bloatware, and kill the initial setup!
Use this command to launch an adb shell on the tablet:
Code:
adb shell
Then disable the packages with these commands:
Code:
pm hide com.fuhu.nabisystemupdatechecker
pm hide com.fuhu.nabimode
pm hide com.fuhu.nabipass
pm hide com.fuhu.nabi.systemupdate
pm hide com.fuhu.nabiintentmanager
pm hide com.fuhu.nabiui
pm hide com.fuhu.nabidreamtabus.download
pm hide com.fuhu.foozkids.webs.v2
pm hide com.fuhu.nabi.updater
pm hide com.fuhu.appzone.v2
pm hide com.fuhu.addapps.v2
pm hide com.fuhu.drmmanager
pm hide com.fuhu.nabiaccountmanager
pm hide com.fuhu.foozkids.videos.v2
pm hide com.fuhu.nabi.cloud
pm hide com.fuhu.nabi.radio
pm hide com.fuhu.foozkids.nabi.activity
pm hide com.fuhu.foozkids.crafts.v2
pm hide com.fuhu.foozkids.books.v2
pm hide com.fuhu.gallery
pm hide com.fuhu.dashboard
pm hide com.fuhu.timecontrol
pm hide com.fuhu.nabi_video
pm hide com.fuhu.nabi.chores
pm hide com.fuhu.nabiconnect
pm hide com.fuhu.wings.wooshu
pm hide com.fuhu.nabi.sync
pm hide com.fuhu.nabinotification
pm hide com.fuhu.nabidemosetup
pm hide com.fuhu.nabiWeb
pm hide com.fuhu.nabisnm
pm hide com.fuhu.foozkid.univ.v2
You no longer will have the parental controls (never used them anyway), but "Parent Mode" will still be there (you can't get rid of this...the Android UI crashes if you disable it). I got rid of all of the fuhu apps that didn't work, with the exception of "nabi Player" (some sort of media player)...I couldn't find its package. It just throws an error if you try to use it.
The tablet also throws a UI error when you do a cold boot. I just hit OK, and it works normally. All of the Android stuff works fine, including Play Store, Wifi, Chrome, etc.
If you want to see what packages are installed (but enabled), in the adb shell:
Code:
pm list packages
To include disabled packages:
Code:
pm list packages -u
In Linux/bash (outside of adb), to see a list of only disabled packages, you can use diff and grep:
Code:
diff <(adb shell pm list packages -u | grep -i fuhu) <(adb shell pm list packages | grep -i fuhu)
I hope this helps someone! I was able to unbrick my kids' tablets, and they also run a bit faster with a bunch of bloatware disabled.
For whoever needs to get past a factory-reset Fuhu BigTab (mine is a 24", but I don't imagine that the 20" is that much different), I have great news! Despite a lack of activity on this thread, there is still hope. I tried another approach to this problem. I tried sniffing the packets and found that the Big Tab 24 that was stuck trying to contact Fuhu's server was attempting to reach updates.fuhu.com. I set up a static entry in my Ubiquiti EdgeRouter so that any attempts to query updates.fuhu.com could actually resolve. In this case I had it resolve to an internal IP of 192.168.1.182 (my MacBook).
I was planning on further sniffing packets to see if I could "answer" the requests that the device was making of the update servers, but as it turned out I didn't have to. It seems that once updates.fuhu.com could resolve again, the previously greyed-out "Not Now" button lit up and I could escape the setup. I'll cut out the parts that led me to my conclusion, but here are the main points of what you need to do to get past this error:
The BigTab needs to be able to reach updates.fuhu.com. It doesn't necessarily need to talk to that server, but it needs to be able to resolve it via DNS. Find some way of making this happen. If you have a more capable firewall/router that you can define a static DNS entry on, do that. If not then you need to get more creative. I would recommend pihole and an inexpensive raspberry pi, or just run the pihole docker container to give you an easy-to-configure DNS server that you can point to in your DHCP config. The clients will query this server when trying to get anywhere on the internet. The bottom line is, when joined to your wifi, you should be able to ping updates.fuhu.com and get back some IP. I don't think it matters what this IP is, but it must resolve.
Once you can resolve updates.fuhu.com, power up the big tab and let it try to reach out to its update servers again. When it ultimately fails (which it will, the server isn't actually there) you will now see the rightmost-button "Not Now" is available. Tap "Not Now", and you will see that cheesy made-for-kids Fuhu launcher.
I legitimately hope this helps some people who, like I, thought they had bricked this lovely device (in my case, shortly after purchasing it second-hand). Good luck!
Shawn
One more thought--If you were able to get into the filesystem of this tablet, and could add a static entry to the hosts file on the tablet, then that should have the same effect with much less work. I was not able to get to the developer mode settings because I was prevented from doing so after I did a factory reset, but if you have a way to make this change 100% on the device itself it would greatly simplify the process.
I'm an actual dork--If you click on "Try Again" 5 times, the "Not Now" button becomes available. No need to do anything DNS-related. Hope this helps someone.
hexagon_founder said:
I am trying to get a Nabi Big Tab 20" unstuck after a factory reset
I can get the device into Android System recovery
Code:
Android system recovery <3e>
KOT49H.WW.25.20150521-037-20
Volume up/down to move highlight;
Power button to select.
reboot system now
apply update from ADB
Update/Recover from USB Storage
wipe data/factory reset
wipe cache partition
I have installed Minimal ADB and Fastboot and the Nabilab drivers but can't get the device to fastboot so I can use a recovery image. I am only able to do
Code:
adb sideload <filename>
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
fastboot devices
fastboot oem unlock
MaximillianPower said:
I'm an actual dork--If you click on "Try Again" 5 times, the "Not Now" button becomes available. No need to do anything DNS-related. Hope this helps someone.
Click to expand...
Click to collapse
and it works!!!!!
it helped me, I was 5 minutes away from throwing it into the bin
Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
0815hoffi said:
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
Click to expand...
Click to collapse
Hi 0815hoffi, I have already done that as part of removing the Amazon Home screen. What I am trying to get at is how to achieve long-press Home to get directly to wifi settings, like the Wolf launcher did before it was broken. You can't put in key values in the .kl file to do events. It only contains a value for each key on the remote. Events are coded somewhere else, do you know where that is? Unfortunately, I can't get any button mappers to work on firestick. The other alternative is to find a way to create shortcuts on the main Wolf desktop to get right to the Network settings screen. Is there a way to do that?
In the new settings, where it says to factory reset, do you know if that keeps root and simply wipes the OS clean or does it really factory reset and remove root? Also, what about checking for updates, will that remove root as well? Just curious...
Thanks
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Thanks, I will give that a try when I get a chance.
0815hoffi said:
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Click to expand...
Click to collapse
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
seems like a mess I think i'll stay on 6.2.7.1 as i run magisk and xposed without any issues.
kick60 said:
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
Click to expand...
Click to collapse
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
0815hoffi said:
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
Click to expand...
Click to collapse
Hi again 0815hoffi, I installed the settings.apk and even though I get all the icons on the desktop, they all open the same FireTV Settings page with all options e.g. Sleep, Display & Sound, Network... and the focus is always on the Sleep option. I do want all the icons, but I actually want them to open the correct settings page. For example, when I click on the Wifi icon, I want it to open the Network tab of the FireTV Settings automatically (like running su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity) and not see the FireTV Settings page at all. Mayby this has something to do with having previously installed the most recent NewSettingsRoot.apk that just has the one icon and just opens the FireTV Settings page. I manually deleted the NewSettingsRoot directory from /system/priv-data and uninstalled the settings.apk, re-booted and re-installed the settings.apk and still all icons open the same FireTV Settings page.
Is there something else I need to do. I'm so close to what I want to accomplish. Thanks again.
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
0815hoffi said:
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
Click to expand...
Click to collapse
Still no luck and have allowed root access and cleared Wolf Launcher Data and Cache. Each settings icon still boots the same FireTV settings page.
Not sure what to try next. I will try to find a way of putting my network.sh script file on the Wolf desktop somehow and try to find a way to launch it.
Thanks for your help.
SH Script Runner
Can create shortcuts for sh Scripts.
0815hoffi said:
SH Script Runner
Can create shortcuts for sh Scripts.
Click to expand...
Click to collapse
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
kick60 said:
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
Click to expand...
Click to collapse
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Sure, that would be fantastic. Thanks
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
kick60 said:
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
Click to expand...
Click to collapse
?
My code is not perfect either.
It has to work, nothing else matters.
?
kick60 said:
Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
Click to expand...
Click to collapse
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
yurividal said:
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
Click to expand...
Click to collapse
It's all in the "Unlock and Root a Firestick 4K - Part 3" by Paul Jones. I connect using the iso like the Part 2 video as that worked flawlessly. At about the 45 second mark of the video, it tells you where to download the files and how to go about it.
If one's primary focus is getting a custom launcher working with the Home button (e.g. with FTVLaunchX), would I be able to flash rbox's pre-rooted 6.2.7.1 image via TWRP on top of stock 6.2.7.3 after unlocking with kamakiri?
I'm asking because I'm one of the unlucky people who forgot to block updates and had my unrooted stick update to 6.2.7.3.