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?
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.
Hiya people..
So I was on the first Beta by Team DRH ICS but decided to go back to Beastys.
I went to CWM, wiped everything, installed the beastys.zip and rebooted the G-Tab.
But now when I turn the G-Tab on the screen is just black after the "Notion Ink" bootanimation..
I've tried NVFlashing 4349 Rev4 with the CWM Touch 5504 B14.
Tried with Calkulin+ClemsysFroyo and Beastys+ClemsysFroyo, also tried with and without the SOD Fix for Froyo ROMs.
If I just let the G-Tab boot after the NVFlash it works, it boots up to the TnT ROM.
I've also tried unplugging the battery for 15 sec or so, and pressing the internal reset button.. Still no luck =/
Anyone at all got any clue on how to fix this? =/
ZoZo- said:
Anyone at all got any clue on how to fix this? =/
Click to expand...
Click to collapse
Do these two things:
1. Boot into CWM, run this ADB command and post the output.
Code:
C:\SOME\PATH> [B]adb shell fdisk -l /dev/block/mmcblk3[/B]
2. After installing the ROM of choice in CWM, and before rebooting into the ROM for the very first time:
- power off the gTab
- connect the USB cable to PC.
- run this ADB command on the PC (and keep it running until you encounter the black screen):
Code:
C:\SOME\PATH> [B]adb logcat -v time > logcat.txt[/B]
- now power on the gTab.
This sequence will ensure that all the logs are collected, and right from the start. Kill the log collection after some time and post that output here too.
Ehum... Could the adb shell fdisk -l command have done anything?
Because after another NVFlash 4349 > NVFlash CWM Touch > Flash Beastys... It magically works!
I couldn't initiate any logcat, only get "waiting for device"
ZoZo- said:
Ehum... Could the adb shell fdisk -l command have done anything?
Click to expand...
Click to collapse
If you ran the fdisk while in CWM, then no--the fdisk was just a diagnostic command.
I couldn't initiate any logcat, only get "waiting for device"
Click to expand...
Click to collapse
That is how it should be. ADB will wait until the device is booted up and the ADB server on the device runs.
Different tablet, same problem
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
I ran "adb logcat" and can see the system processes running, but screen stays blank, making the tablet unusable.
I ran "adb logcat -v time > logcat.txt" and here is the file:
https://dl.dropbox.com/u/18476770/Android/logcat.txt
This tablet being fairly new, I could not find any support forums for it; I opened a ticket with the supplier, but they are very slow responding.
I turn to XDA, knowing the knowledgeable and helpful people here will shine some light my way.
Thank you in advance
./B
kozmo2k4 said:
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
Click to expand...
Click to collapse
Since I don't have that tablet, it's difficult to do comparisons to determine deviant behavior. So, what follows are just guesses:
1. There is this error message in that log which might be relevant (or it might not--I've no idea):
Code:
06-12 21:12:30.659 E/SurfaceFlinger( 85): couldn't find an EGLConfig matching the screen format
06-12 21:12:30.729 E/DisplayDispatcher( 85): Open Display Device Failed!
06-12 21:12:56.849 E/DisplayManagerService( 149): Open Display Device Failed!
2. I noticed that some 3rd party live wallpapers were being loaded. Did the problem start after the live wallpapers were installed? Maybe that's causing problems.
Given that you are able to see 2 (?!!!) boot animations before the display goes blank, I would have to guess that its no. 2 (heh!) that's causing problems. Uninstall all the live screensaver packages using ADB. Use this as a guide.
As a last resort, you could try going into CWM (if it's installed) and do a "wipe data/factory reset", then re-install the ROM. You will lose all data with this.
Thank you for the fast reply, rajeevvp.
I'm sorry I said it wrong earlier, there is only one boot animation, the "old school" letters: ANDROID, with a light beam running across them. There are two "boot logos" that flash on the screen prior to that. My PC, right now logged in on Win7x64, recognizes the tablet connected (USB device connected jingle) at the Android bootani.
I'm going to try to adb uninstall some of the apps and we'll see what happens.
Thanks for the insight.
./B
[EDIT]: Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this. Only physical buttons are: Power, Menu and Escape. I tried all combinations, but it just boots up.
---------- Post added at 05:23 PM ---------- Previous post was at 04:50 PM ----------
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
In adb shell, after remount rw, command: rm -f /data/app/.apk
says "No such file or directory"
I know I typed the package name (com.cellfish.livewallpaper.marvel_avengers-1.apk) correctly. Hmmm
./B
kozmo2k4 said:
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
Click to expand...
Click to collapse
What is the exact command you used? As the document says, if you are using ADB, you should do:
Code:
C:\SOME\PATH> [B]adb uninstall [I]packagename[/I][/B]
Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this.
Click to expand...
Click to collapse
If you can figure out how to get into stock recovery (it would be very unusual to not have one--its needed for ROM upgrades for instance), then you could try this:
Clear Cache and Data from Stock Recovery
Thank you for the reply.
Here is what I've tried:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
then the app full name I found in Play Store
Code:
adb uninstall The Avengers Live Wallpaper
Al I get is "Failure"
Next I tried
Code:
adb shell
[email protected] # mount -o rw,remount /data
[email protected] # rm -f /data/app/com.cellfish.livewallpaper.marvel_avengers-1.apk
The I get:
rm failed for -f, No such file or directory
I was not able to figure out how to get to recovery of any sorts; like I mentioned, only 3 physical buttons, Power, Menu and Esc. Tablet has microSD slot, Mini HDMI, 3.5mm headphone, Mini-B USB and full USB ports. That's all. I'm getting close to opening the case to see if there is a reset button, but waiting for my colleague's pernission (she'll most likely just send it back).
Update:
I was able to remove the live wallpaper in adb (just omitted the -f after rm), but no cookie....black screen after boot.
Is there a way to wipe-factory reset with adb? Just delete the contents of /data/app directory? .... Only one way to find out...
---------- Post added at 06:22 PM ---------- Previous post was at 05:59 PM ----------
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Thank you again for all your help!
Linux ROCKS
./B
Follow up post
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
kozmo2k4 said:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
Click to expand...
Click to collapse
You have to use the package name and not the apk name to adb uninstall. Look inside the /data/system/packages.list file to determine this.
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Click to expand...
Click to collapse
A bit drastic, but, that works . But, I wouldn't have recommended wiping the /data partition like that while inside the ROM. This is why a recovery mode exists.
I wouldn't be surprised if after a wipe like that and a subsequent filesystem check, the /data/lost+found directory contained more than a few files/dirs.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
kozmo2k4 said:
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
Click to expand...
Click to collapse
+1 kozmo2k4. We need more smart users like you on the board.
Thank you for the kind words, rejeevvp. I love to "tinker" with things and do not give up that easily.
I know the "adb shell wipe data" was an overkill, like chasing a fly with a .50cal, but at that point in time it was the most feasible.
I've tried all possible button combinations to get into recovery, but everything led to regular boot.
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did another Wipe Data and wipe Cache and rebooted.
Everything seemed to be working fine afterwards, and my colleague texted me that the tablet is running faster and smoother than when she first got it, so everything is all good.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Here is the front:
Sent from my NookColor CM9 using Tapatalk 2
kozmo2k4 said:
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .I did another Wipe Data and wipe Cache and rebooted.
Click to expand...
Click to collapse
+1 again. That is the right thing to do.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Click to expand...
Click to collapse
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Reset Brightness
rajeevvp said:
+1 again. That is the right thing to do.
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Click to expand...
Click to collapse
Soft buttons work while in ICS; when tablet was off, only "hard buttons" were available.
I would be more than happy to run few tests, but I returned that table on Sunday (have the feeling that wasn't the last time I saw it, though).
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class; I have "/sys/class/pwm-backlight/" tree on both devices:
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
But I did not get to try any of that, since I got lucky with Android Commander and ScreenCast.
kozmo2k4 said:
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class;
Click to expand...
Click to collapse
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
I have "/sys/class/pwm-backlight/" tree on both devices:
Click to expand...
Click to collapse
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data.com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
Click to expand...
Click to collapse
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
rajeevvp said:
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
Click to expand...
Click to collapse
That was a TYPO on my part (fixed on original post for future reference).
My gTablet is on ICS (actually I just flashed AOKP, running pretty good so far) with TeamDRH kernel. My phone is on stock EL29-repack (Calkulin's v3.0) kernel.
Hope all this info will come in handy for someone in the future!
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
fazluke said:
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
Click to expand...
Click to collapse
Do you have ADB.set up on your PC?
If so, go ahead download and install Droid Explorer (there is a link few posts back).
Once installed, run it, ensuring you "powered on" tablet is recognised. Along the top row of icons, there is one called Screen Cast (hovering over the icons will show the name). Select it, let the Java applet install, then click Screen Cast and that should open a new window, mirroring the tablets screen. Then you can navigate on the tablet to settings.... and get it set.
I think there may be a video on YouTube showing this.
Hope this will help.
[Edit] Here is a link to Youtube:
http://www.youtube.com/watch?v=eEeHaszOMi0&feature=youtube_gdata_player
Sent from NOOK Color CM7.2 using Tapatalk 2
Thanks for the quick response, will download and follow your directions, then report back tonight.
fazluke said:
Thanks for the quick response, will download and follow your directions, then report back tonight.
Click to expand...
Click to collapse
Worked exactly as described with minor issue. Screen cast does not work on locked device. I see the locked screen but can't unlock it and the Youtube link confirmed that too.
I tried to turn it off and on, to see if I can get hold of it before it goes into locked mode and after few tries I got it to work.
Another issue was that my mouse will not control it. SO looking at the computer screen and moving my finger on the tablet surface, I managed to get to setting/display and adjust brightness.
Thank you again for your help.
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.
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.
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