Database Info

[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing

This is an update to the TWRP recovery for the Nabi 2.
​
{
"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"
}
At this point this recovery is still considered in testing. The normal disclaimers apply. Have a good backup moved to your computer from the previous recovery.
Before starting this your Nabi should be updated to 1.9.37. 2 people that have 1.9.34 - (Madagascar Bundle) and 1.9.35 or 1.9.36 - (UK Versions) were having issues.
Please check your version in Settings-About Tablet-Product version, it needs to be 1.9.37 currently, other tablet versions besides 1.9.37 are experimental see below.
This is for Nabi 2
Nabi JR 4GB is HERE
NabiXD is HERE
Nabi JR 16GB is HERE
If you have Nick/Disney read up about different build for those.
Updates
Mar 15th 2015
TWRP 2.8.5.0 KK and JB http://forum.xda-developers.com/showpost.php?p=59452953&postcount=2592
2.7.1.0 http://forum.xda-developers.com/showpost.php?p=54972620&postcount=105
Jan 9th 2013
-Change to symlinked partition structure in recovery.fstab as we have found some Nabi's may have different structure
-Added Nabi Kernel version to TWRP screen for easier troubleshooting
-Added Nabi logo in place of Android(just for fun)
Initial
-Latest TWRP 2.3.3.0
-Changed to the prebuilt kernel from Nabi 1.9.37
-Fixed touch issues with some tablets with previous recovery(still testing this)
For more information on TWRP and change log see the TeamWin Website
Download
There are 5 downloads provided. The first is an installer for those less comfortable with the command line, it can install either version of TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second two are for people that just want TWRP 2.3.3.0 and can do a manual install. The final two are the last 2.3.3.0 with static partitions should you need to revert.
Auto Installer
Recovery Installer for Nabi(Recovery installer for both old and new kernel TWRP 2.3.3.0, TWRP 2.2.2.1, and STOCK recovery) Use install method 1
Current recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Older recovery recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Installation
-Method 1 (Recommended install , guided installer)
-Download "Recovery Installer for Nabi" from above
-Extract TWRPinstaller.zip
-Run RecoveryUpdater.bat
Code:
Select option 1 for a Nabi on 1.9.37 and follow directions
Select option 2 for a Nabi not 1.9.37 (UK 1.9.35 or 1.9.36 or Madagascar 1.9.34)
Select option 3 to go back to 2.2.2.1 recovery if option 1 or 2 do not work
Select option 4 to return your Nabi to stock recovery after restoring stock ROM
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 2.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 2.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_mt799
TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/
Credits
TeamWin team for TWRP.
Dees_Troy for build tutorials.
jmztaylor for the device code to work from.

aicjofs said:
Anyone want to guinea pig a TWRP build I made?
It's version 2.3.3.0 with the latest Nabi kernel. I don't think it will fix touchscreen issues but worth a try. EDIT: Some early results are indicating it is fixing touchscreen issues.
You can try it without installing it permanently
extract recovery.img from TWRPrecovery.zip to your adb directory
adb reboot-bootloader
fastboot boot recovery.img
That won't put it on the device just boot it to ram and you will maintain your current TWRP after a reboot. To make it survive reboot obviously you would need to
fastboot flash recovery recovery.img
http://home.comcast.net/~aicjofs/TWRPrecovery.zip
Click to expand...
Click to collapse
Tried your recovery, all I could say it's perfect. Touch screen in TWRP recovery is 100%. Have ben plagued with the touch screen error in recovery prior to aicjofs latest 2.3.3.0 TWRP recovery.
jmztaylor, aicjofs, t499user, e2950 deserve the XDA Nabi 2 award. Have owned the tablet maybe 3 weeks, in that time was able to restore from soft brick, get a working gapps witout 'Android Upgrading", and new updated 2.3.3.0 TWRP recovery. Got to Love XDA community.
All we need now is our own forum :laugh:
Sent from my GT-I9300

+ 1 on all that above
+ i wanted a updated version -
+ thank you
ps: *MY* nabi box says "ages 4-to 40" i think no matter what the age is
they all going to be happy with all this cool stuff.

good job
Glad to see people are happy u made this
:good:

Great to see more development starting to happen for the Nabi 2, thanks!

maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?

I have 2 responses from people where this version has touchscreen issues. It is for a 1.9.36(UK Version) and what I believe is a 1.9.34(Madagascar version) I updated the OP but it looks like you should only be using this on 1.9.37 right now.
Eric Karz said:
maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?
Click to expand...
Click to collapse
I always have usb plugged in so I never noticed.

CWM
aicjofs are you doing a CWM recovery for the nabi 2?

Eric Karz said:
aicjofs are you doing a CWM recovery for the nabi 2?
Click to expand...
Click to collapse
I did a CWM for the Nabi. Everything worked except I was having a hard time mounting the /sdcard properly. The internal sdcard as we know it is actually in /data/media(so it's on the data partition), I was able to manually "mount" it(symlink) through shell, but I couldn't make it auto mount. I'm sure it's something simple through init.rc or something but I couldn't get it working right to mount at boot time. On a side note to that, since it's on the data partition care has to be made that if the data partition is wiped that the sdcard is moved off and then back. I'm not sure if CWM does that with a loop device or something, just moves it or what, but it's dangerous. Lot's of devices have it set up this way so I think it would be accounted for, but I know TWRP accounts for it. I'm not sure extendcommand was working correctly either, it appeared to, but log was complaining about it. As it was I had early feedback that new TWRP was fixing touchscreen issues so I put it on back burner, as part of the reason for even building CWM was for those that had touchscreen issues. Only real change was to the BoardConfig.mk for BOARD_HAS_NO_SELECT_BUTTON to make CWM "function" less mounting problems.
Now I'm trying to decide if we are better using /dev/block/platform/sdhci-tegra.3/by-name in the recovery.fstab for those Nabi's with different partition structure. jmztaylor was kind enough to give me his ear and I think we should do tegra by name. No reason we shouldn't have one TWRP version, 2 at most. Once I get TWRP working for all Nabi versions for sure, I will probably revisit it.

Updated to symlink partitions for Nabi's that have been found that might contain a different partition structure.
Nabi kernel version added for easier troubleshooting
Nabi logo

Test Report
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks

Eric Karz said:
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks
Click to expand...
Click to collapse
Ok I really need to make a thread for Nabi Lab. Was that a hint? haha. Excellent feedback as always.
1. Yes you are correct that it should be added. I will add it.
:Main_7
adb\adb.exe kill-server
EXIT
2. What version of windows are you using? Also 32bit or 64bit? I had no issues with 7 and 8 64 bit after disabling windows driver signature enforcement, are you sure it took the "disable driver signature enforcement" after the reboot? That's the only thing that I know that would cause that. XP worked but I did manual mode as you did while testing. It's a modified Samsung driver so it might display that.
3. Also possibly related to the above. However I don't think so... It's possible that installing PDA net doesn't remove driver store/inf(depending on windows version). For example on Windows 7 open /windows/system32/driverstore/filerepository and search for "android" there is likely extra ones. So it just reinstalled the PDA net one. It should say Fuhu Nabi 2, so I think you are using the old driver. Both drivers are so you see the option for Nabi labelled one. You would have to unisntall in device manager and then remove all of android infs. Then reinstall.
4. Useful feature. That's not too hard to add since it detects the mode based off of it can run the getprop command. Give me an example when you would want it to do this so I can add it logically. Just really adding "fastboot reboot" and detecting. Are you thinking automatic detection like refreshing on it own?
Thanks for the feedback. You were already credited in the readme, but maybe you need some more credit

before i forget http://forum.xda-developers.com/showthread.php?t=1905674&page=131&highlight=nabi post 1302.
i was thinking
after the driver install
something like
1) test 1- Action > adb.exe reboot-bootloader
@echo Do you see the pretty green word "Bootloader" ? lol sorry i am tired

nabilab.bat
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .

Eric Karz said:
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .
Click to expand...
Click to collapse
Will that even be necessary if we go with the driver.bat you posted integrated in to the main bat file? I have been busy with my job last few days but I was able to run it in a few environments and it was working. The driver works, Im just working for an experience where anyone that can click a mouse/use a keyboard can install it. I think the PDAnet one is messy, that program even installs the apk to your tablet. Nonetheless the driver from a fundemental standpoint is the most important part, even if most people already have some functional driver. I want to get the driver cleaned up and the 2 known typos(although the 2nd might not be necessary if the driver install changes)
If I get those fixed make a Nabi Lab thread and work on ideas people have or want to see. Since you have been over the code what do you think of my hack job? Haha. Just notepad, not even notepad++, let alone a proper sciprting editor, I just kept adding stuff, it started as a simple recovery installer and then I got sloppy, and my variables and calls are a mess and named ridiculous. Kind of embarrassing. I haven't written that much code from scratch in 20 years, most of the time you have a base and can just work from there. That driver you linked gave me an idea of adding color to highlight errors and important parts, mostly cosmetic. For line by line color changes I have to use chgcolor and echoj. Easy enough to add to the download but changing all the echos is a tone of work.
I hope you know I appreciate your contributions.

opps my bad - forgetting the part about adding it to the main bat file .
just getting nabi lab to work for every one that uses it is the main goal.
code always has to start some place - i am sure as time goes on people will recommend things to to it.
the color in the Install bat was just to wake you up and watch what you are doing.
here is a example of something my brain skips over - Even though its proper and must be read in order to achive the goal
“Then hit VOL - until Recovery Kernel is selected
My brain only wants to hit vol 1 time haha
my brain should tell me to keep pressing Vol - until I see “Recovery Kernel” selected.

I see that Twrp is up to 2.4.0.0
Is there anything that nabi 2 users would benifit from it ?

Re: [recovery][nabi2] twrp 2.3.3.0
I too am wondering this!
Sent from my EVO using xda app-developers app

Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements
Click to expand...
Click to collapse
Seems interesting, I'll see about making a test build sometime this week unless someone beats me to it.

I'm short on time these days. Here is a build that boots. I tested an install. You can try and put through paces. fastboot boot recovery.img to test and not replace current.
Download TWRP 2.4.0.0

[TOOL][NABIXD] NabiRootXD Root, Gapps, Recovery

NabiRootXD v2​
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery​
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries​
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab​
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible

Weeee more Easter goodies haha.
thanks aicjofs

Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...

first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results

srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time

Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?

i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .

Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?

aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?

I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.

cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious

srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.

ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?

i am trying to get this tablet to use my network opendns settings and web filters

Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.

Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.

yup getting the dead droid

Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.

OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse

aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.

NuVision TM800A510L- General Info (Root, Recovery, Unbrick)

This thread intends to be a general thread for all things about the NuVision Tablet. The aim is to help other users of this tablet to be able to root their device, get a temporary recovery and to unbrick their device. I will add the guides for the following posts below in time. This would not have been possible without help from @andrei_kr.
{
"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"
}
Technical Specifications:
Display: 8-inch IPS HD capacitive touchscreen
Resolution: 1280 x 800
Operating System: Android 4.4 Kit Kat
Processor: Intel® Atom Processor
Memory: 1GB DDR
Storage: 16GB
Micro SD Card Slot: Yes, expandable up to 64GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer

Backup/Root/Recovery
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
How to backup of your stock ROM, install CWM and Root your device.
Requirements
ADB/Fastboot Drivers
Intel Android USB Drivers
SDcard (8GB of higher)
Temp recovery script
SuperSU
Steps
Download and unpack IntelAndroid-FBRL-07-24-2015.7z
Power off tab.
Hold Vol+ and press Power on the tab 5-10 seconds
You can see logo about 10 sec and after that DROIDBOOT will load
Connect USB cable to PC
Run launch.bat from IntelAndroid-FBRL-07-24-2015 folder
Type ACCEPT and press Enter
Type 5 and ENTER (cwm.zip)
Type T3 and ENTER (or T4)
CWM will load after 10 sec.
Select backup to external sd card.
After the backup is complete, copy it to the PC to ensure it's safe.
Follow steps 1-10 again and go to install zip from sdcard or external and select the SuperSU zip file and flash it.
NOTE: DO NOT FLASH ANY ROMS WITH THIS RECOVERY IT IS ONLY TEMPORARY. I DID NOT TEST XPOSED SO BE CAREFUL.
Credits
@andrei_kr
@social-design-concepts
@vampirefo
@Chainfire

Unbrick your Tab!
To unbrick your device all you simply have to do is go back to the CWM and restore your backup that you created earlier. If you don't have one, here is a copy of a working backup ---> Google Drive. Credits to @andrei_kr, say thanks!

How to fix touch!
If you unbricked your tablet and your touch isn't working, there is no need to worry. @andrei_kr has provided a guide on how to fix that touchscreen. Credits to him.
NOTE: If your touch is working then do not try this, it will mess up your touch!!
You probably got this touchscreen issue by flashing a different kernel with incorrect drivers.
Now your configuration is likely to differ from the native. You can view the konifig in command prompt or in the terminal :
Code:
cat /proc/gt9xx_config
(only mtk) or using the gtp_tools apk (it is in the attached file below).
It starts with the byte sequence: 0x41 0x1C 0x02 0xC0 0x03
0x41 - 65 version
0x1C 0x02 - 540 horizontal resolution
0xC0 0x03 - 960 vertical resolution
Touch must somehow work to press the button, if there is support otg, then it's easier, you can connect a mouse.
1. Install the gtp_tools_v2.6_20140126_special.apk
2. Go to the option Firmware update. Click refresh, see IC Version: 913_1020 then touch GT913 firmware and 1020.
3. Go to the option Config Settings, press read, the data were considered. Under Normal Config we have:
65 version
540 horizontal resolution
960 vertical resolution
4. Click browse, select click browse to the native config.
5. Native configuration take from your device, in the same paragraph, press the save (saves the backup config file). Native configuration for Fly IQ446 in the attached file. Press send.
6. If nothing has changed, look at the version you have and native config. Then change the version of the file in the native config in your hex.
Example: 0x41 = 65 home, a stranger 0x49 = 73 => replace the 0x41 to 0x49.

Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk (711.77 KB)
Number of downloads:
11,141,690 in total · 8,610 in the last 24 hours
MD5 checksum:
de4f0dc569f96dbcc5668d40fa76040b
Uploaded on:
Tuesday, May 20, 2014 - 21:59
Changes:
- Fixed a crash with some apps (Disa, Rdio)
- Some minor UI improvements
- A few translation updates
Now either use an android terminal emulator or ADB and run these commands
1. su
2. echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
3. chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Now you can install the Xposed framework.

max0r4axor said:
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk .
Click to expand...
Click to collapse
Thanks for report.

First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?

Jingbadguy said:
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Click to expand...
Click to collapse
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?

kirito9 said:
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
Click to expand...
Click to collapse
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...

Jingbadguy said:
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Click to expand...
Click to collapse
Oh I thought they were working. Follow the procedure above to fix.

NuVision TM101A510L
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry

Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...

ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)

williamglick said:
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Click to expand...
Click to collapse
I think the models numbers are specific so I can't say for certain that this will work with your tab. Try the fastboot/rooting procedure first and then maybe you can just restore the system partition only not corrupting the boot/kernel.

Unidave199 said:
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
Click to expand...
Click to collapse
You're welcome. I waited months also before finding a working backup.

Jingbadguy said:
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
Click to expand...
Click to collapse
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?

kirito9 said:
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
Click to expand...
Click to collapse
ill let you know just as soon as i can get back to working on those devices... im prety sure if memory serves correctly, that I was getting some errors regarding unable to mound sd or ext sd. I could be wrong but thats what comes to mind.
Im up to my neck in jobs on other devices. (rooting galaxy S5, changing imei on another S5, IMEI change on a LG Stylo 2 plus, Galaxy Tab 2 system issues need to diagnose, and several screen and lcd replacments)

STUCK
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?

after ive flashed super su, when i go to restor the working backup i see a list of backups... including yours but when i select it i always get :
checking md5 sums...
md5 mismatch!
what now?
(i tried just flashing the boot but even that comes back with same error)
I know on other devices the recovery is an img file any the one you provide is a rar... i extracted to my desktop and was gonna try flashing with abd/fastboot but since its not an img file, im thinking it wont work...
any thoughts?
Im still unsure how to flash the recovery that u supply in the section for fixing bootloop....

Jingbadguy said:
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
Click to expand...
Click to collapse
The too many links error is common for this device. Touch doesn't work with TWRP on this device so CWM is out only go. You can root and using cwm like any other root method.

Twrp 3.3.1. UmiDIGI Power 4G

TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file

reserved 1

Reserved 2

TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!

SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck

SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.

Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!

Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?

mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:

I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.

mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.

SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash

I will build one other version of recovery soon...

mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.

Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock

Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!

SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?

Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.

TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.

[GUIDE] Rooting the Moann inkPalm 5

Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.

qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !

I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...

So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada

Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !

squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language

ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.

This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.

Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button

qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.

reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).

qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.

squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada