Database Info

[ROM] [Acer Iconia Smart S300] [25/06/2012] MIUI ROM found on other website

Dear all,
First of all, I do not wish to take any credit for this ROM, I am just sharing it for the community as I do think it is a very nice addition to the collection and may help and progress development for other ROMs.
[credits]
I have found it on a Russion website:
http://acer-club.ru/topic/18146-custom-rom-miui-%D0%B4%D0%BB%D1%8F-acer-iconia-smart/
If you want a translation, Google Translate does the job:
http://translate.google.nl/translat...%D0%B4%D0%BB%D1%8F-acer-iconia-smart/&act=url
Click to expand...
Click to collapse
[downloads]
It can be downloaded from here:
http://narod.ru/disk/53152553001.2989f43dffd6f91bb6c8e726afe7aaf3/update.zip.html
Modded version (1.0) where I changed /mnt/sdcard/external_sd into /mnt/external_sd:
http://www.multiupload.at/8WAHWX3L4S
Additonally changed the default language, so here's a newer version (2.0):
http://www.mediafire.com/?npdyofr2uhn3but
If necessary I can upload to other locations as well.
Click to expand...
Click to collapse
[release notes]
According to the website, everything works (I'll be testing during the next days), except:
If the MMC is not ready to insert a picture from the camera is locked mms.
(translated using Google )
Click to expand...
Click to collapse
[instructions]
I installed it as follows:
Download update.zip, download see above
Install ClockworkMod Recovery
Reboot into ClockworkMod Recovery (Volume-Up, Focus & Poweron)
Copy "update.zip" to your external (!) sdcard
Note: internal sdcard is not supported by Clockworkmod Recovery
Make a backup of current ROM: "backup and restore" -- Backup
Check whether all backup files are > 0 kb (make sure backup is correct and store it safely)
Perform factory reset: wipe data/factory reset
Optional: I have also formatted /system, /data, /boot
Choose "apply update from sdcard"
Reboot
If language is Russian and you wish to change it, please see next section (screenprints)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Regards,
Nika.

[screenprints]
And here's some screenprints from my device
First boot will show you are Russian screen:
{
"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"
}
1. The Homescreen
2. Click Menu and then middle, bottom button, for Settings
3. Click the middle top button for System Settings:
3. Click the bar with the keyboard, Lanuage & Input Settings appears:
4. Click second bar from the top, Support Languages screen appears:
5. Click reboot (as some screens are still in Russian)
6. After reboot, just one item is still in Russian:
Nice, huh?!

That's very nice indeed
Too bad it's not Android 4 but it's still great.

paugustin said:
That's very nice indeed
Too bad it's not Android 4 but it's still great.
Click to expand...
Click to collapse
Yeah, it really is. I must say that this is the best ROM so far. I do have one major issue where I cannot select an APN and therefore have no 3G / 2G connection. Needless to say, this is a huge issue which may render the ROM to be unusable for me... Let me know what you guys experience if there's still some people willing to install new ROMs on their device

Do you mean there is no way to set the APN? I'm seriously considering flashing this ROM, but this APN issue that you mentioned is holding me back...

TooUglyForU said:
Do you mean there is no way to set the APN? I'm seriously considering flashing this ROM, but this APN issue that you mentioned is holding me back...
Click to expand...
Click to collapse
When you make sure you create a backup you can check and always restore the backup. The APN issue might also be related to my carrier or SIM card.
Please note that I definitely had to format /data (ie. factory defaults) because it will not work with the data of another rom. Also make sure to make an extra backup of your backup onto your system, just to be sure - in my case it has created corrupt files many times (ie. 0 kb)...
Good luck!
Regards,
Nika.

Unable to view External Sd card files
I'm a big fan of miui but when I installed the rom was unable to view external SD files had to revert back to stock rom any help how to get this working

t_avin said:
I'm a big fan of miui but when I installed the rom was unable to view external SD files had to revert back to stock rom any help how to get this working
Click to expand...
Click to collapse
Hi all,
I checked today and the external SD is available, but not under /mnt/external_sd but under /mnt/sdcard/external_sd. Not sure why it is in a subfolder, but see below some screenprints to demonstrate this. If anyone knows how to solve something like this, let me know
Regards,
Nika.

Well, that was easy, changed the vold.fstab and build.prop files and zipped it. Works fine when installed using cwm recovery. /mnt/external_sd is now the correct external sdcard
You can download the new version here:
http://www.multiupload.at/8WAHWX3L4S

While searching for a solution to fix my APN problem, I also changed the default language into English. APN is still an issue, so if someone knows what can cause APNs not to list in MIUI ROMs I'd love to know
Here's the download for the English version of this ROM (including the external storage fix ):
http://www.mediafire.com/?npdyofr2uhn3but

Be interesting to see if this will flash to my device, seeing as none of the other custom ROMs have ever done so...
EDIT: Well, it installed OK and runs, but like you, I have no APN's and setting them up manually doesn't seem to work. Also, a fair number of FC's, especially when trying to search networks...
EDIT2: This appears relevant to the APN problem: http://www.modaco.com/topic/351027-cannot-add-apn-with-both-cyanogen-and-miui/

FloatingFatMan said:
Be interesting to see if this will flash to my device, seeing as none of the other custom ROMs have ever done so...
EDIT: Well, it installed OK and runs, but like you, I have no APN's and setting them up manually doesn't seem to work. Also, a fair number of FC's, especially when trying to search networks...
EDIT2: This appears relevant to the APN problem: http://www.modaco.com/topic/351027-cannot-add-apn-with-both-cyanogen-and-miui/
Click to expand...
Click to collapse
I've not had any FC's - did you Factory Reset / wipe cache etc?
For APN, I'll see whether I have time to test this week. My device is getting buggier by the day, sdcard is not working anymore and has random reboots, so I may need to take it apart again. sdcard is quite a problem as that is impossible to reach without spare-parts did you see the "take device apart" device on the russian forum? quite cool
http://www.youtube.com/watch?v=ILYMc9Hkz1Y&feature=player_embedded

I needed internet, so for now, I've flashed back to my previous ROM. TBH, I'm not a fan of MIUI, but at least the bloody thing installed!
Oh, what I wouldn't give for ICS or better, JB, on our Smarts....

Yeah ICS would totally rock on the Smart ! too bad Vache broke his, he only needed to fix 3G on CM9. Well "only" may not be the word. Thepasto is using Vache's source to get CM9 on the Liquid MT and they weren't able to get 3G working so far.

paugustin said:
Yeah ICS would totally rock on the Smart ! too bad Vache broke his, he only needed to fix 3G on CM9. Well "only" may not be the word. Thepasto is using Vache's source to get CM9 on the Liquid MT and they weren't able to get 3G working so far.
Click to expand...
Click to collapse
Damn..
I really wish more devs would pick up Acer devices... I'd do it myself, but with a full time programming job and a family, I just don't have the time to learn the intricacies of ROM building.

FloatingFatMan said:
I needed internet, so for now, I've flashed back to my previous ROM. TBH, I'm not a fan of MIUI, but at least the bloody thing installed!
Oh, what I wouldn't give for ICS or better, JB, on our Smarts....
Click to expand...
Click to collapse
Agree, but I must say, that MIUI build is half not as bad as I expected! It really is good, definitely better than stock (other than the APNs not working for some SIMs - note the Russians do not seem to have any issue with it)...

nikagl said:
Agree, but I must say, that MIUI build is half not as bad as I expected! It really is good, definitely better than stock (other than the APNs not working for some SIMs - note the Russians do not seem to have any issue with it)...
Click to expand...
Click to collapse
I don't suppose there's any ROM builders out there who can take a look at this and see if they can do anything about the APN issue, is there?

Hi all,
Anyone interested in TeamWin Recovery Project (TWRP)? I've build an initial test version:
http://forum.xda-developers.com/showthread.php?t=1882747
To figure out how to mount the internal sdcard, can someone run the following commands on their device?
Code:
adb shell
su
cat /proc/mounts
cat /proc/emmc
ls -lR /dev/block | busybox egrep -i "rec|sos"
Regards,
Nika.

nikagl said:
Hi all,
Anyone interested in TeamWin Recovery Project (TWRP)? I've build an initial test version:
http://forum.xda-developers.com/showthread.php?t=1882747
To figure out how to mount the internal sdcard, can someone run the following commands on their device?
Code:
adb shell
su
cat /proc/mounts
cat /proc/emmc
ls -lR /dev/block | busybox egrep
Regards,
Nika.
Click to expand...
Click to collapse
Hi Nika
Sure, pls provide me specific instructions (from the PC? from the phone with terminal? ...?) and I'll be more than happy to help (if possible)
KR

ivan69_mi said:
Hi Nika
Sure, pls provide me specific instructions (from the PC? from the phone with terminal? ...?) and I'll be more than happy to help (if possible)
KR
Click to expand...
Click to collapse
Hi KR,
It can be done from both terminal on the phone or PC. Did you root your device? You should be doing to following when doing it on the PC (easiest):
1. Root your device, see http://forum.xda-developers.com/showthread.php?p=17569226
2. With rooting you also install drivers for adb, so that's ok
3. Connect your device with USB
4. Open a Command Prompt
5. Run "adb shell" (adb.exe is also available in the files for the recovery)
5. Type the following commands:
Code:
adb shell
su
cat /proc/mounts
cat /proc/emmc
ls -lR /dev/block | busybox egrep -i "rec|sos"
After each command you can copy/paste the results. Wrap the results between CODE tags when pasting it here or use stuff like http://pastebin.com/ and return the results
Thanks!
Regards,
Nika.

[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.

[Q] How to get dynamic storage (/sdcard ->/data/media) on One S, "Insufficient Space"

[Q] How to get dynamic storage (/sdcard ->/data/media) on One S, "Insufficient Space"
Ohh, I'm getting so fed-up with seeing "Insufficient Space on Device" errors in the Play Store. What good is Android if I can't download any games or apps?!
I'm running CyanogenMod 12.1, latest nightlies. But the ROM thread isn't the right place to put this, because it's a device/partition-level issue.
I've got hboot 2.15 and S-OFF, and from what I've seen, hboot 2.16 brings with it the "dynamic /sdcard" feature that creates one big partition out of /data and uses part of it for a "virtual SD". What I have now seems to be a fixed /data size and a huge, almost completely unused /sdcard partition. I keep running into "Insufficient space on device" errors all the time, without even downloading new apps - just trying to update the apps I have. Nothing big, either - the biggest app I have is freakin' Candy Crush. It appears that I'm only given a 2GB /data partition, and 1.1GB of that is Dalvik-Cache, and 900MB of it is apps & data. Yeah, the dalvik-cache is bigger than the damn apps it's caching!
I'd be willing to wipe it all out again (sigh... SIGH) if I can get dynamic /data to work, perhaps by updating to hboot 2.16. I'd even go S-ON again if need be - the only reason I'd gone S-OFF is to try to get more stability out of the glitchy radio firmware constantly dropping the internet connection, but those problems still persist too...

Well, I dug really, really deep and discovered that hboot 2.16 is what brings the "dynamic /sdcard" to the One S. You can follow along with much more information in my replies here: http://forum.cyanogenmod.org/topic/113169-storage-space-running-out/#entry535206
The key is to install hboot 2.16 from this post: http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266
I'm hoping - hoping and hoping* - that I can restore my TWRP backup into the new /data partition. To get it working, I had to use TWRP's "repair/change filesystem" on both /cache and the /data partitions (though strangely, /system was left intact and valid, apparently because the sector location didn't change). This means that all USB storage (/sdcard) and internal storage (/data) will be lost, so be sure to backup and transfer to your PC before updating to hboot 2.16! You also lose the ability to mount internal storage as USB (using USB Mass Storage mode), because /sdcard is now a virtual drive, no longer FAT formatted. In my opinion, this is a very worthwhile and acceptable tradeoff... because /data is now 12 GB!
* - edit: I'm full-on freakin' ecstatic right now.
"Internal storage - Total space: 12.06 GB -- Available: 7.63 GB"
And not a single thing was lost or changed. Booted right up as if I'd just switched the thing off and back on.

Hey FalconFour,
Thanks a lot for sharing your progress with us.
As you saw in my thread, I'm facing the same annoying storage issues like you (and a lot more people on the internet...).
I'll give your solution a shot during the next couple of days and report back as soon as I have some results.
My status quo: HTC ONE S / CM 12.1 / S-ON / HBoot 2.15
Do you have any advice for me before I start?

Urds said:
Hey FalconFour,
Thanks a lot for sharing your progress with us.
As you saw in my thread, I'm facing the same annoying storage issues like you (and a lot more people on the internet...).
I'll give your solution a shot during the next couple of days and report back as soon as I have some results.
My status quo: HTC ONE S / CM 12.1 / S-ON / HBoot 2.15
Do you have any advice for me before I start?
Click to expand...
Click to collapse
** Crap -- I just realized you said you're S-ON. See the bottom of the post for advice on that. **
1) Backup. I used TWRP 2.8.7.0.
2) Earlier versions of TWRP seem to have a bug in "Mount USB storage" function - on mine, it was horribly, unusably unreliable to actually present the "linux file gadget" USB device or whatever it was. 2.8.7.0 seems to fix that. It mounted reliably after the update, and I backed up all the files on the "internal SD" - including the backup I just made.
3) Grab hboot 2.16 and apply it per the fastboot commands in that thread.
4) For safety, I ran "fastboot oem erase_phone_storage" from the new 2.16 bootloader (fastboot mode).
5) Before rebooting, I reflashed TWRP 2.8.7.0 with "fastboot flash recovery" just in case it changed.
6) Reboot to TWRP recovery.
7) Under "Wipe", "Advanced", use "Repair/change filesystem", and I applied F2FS to /data and /cache, since at least /data will now be unformatted (or corrupt) due to the partition layout change. Since ext4 isn't designed for Flash storage and I'd like my phone to last as long as possible, I figure the bit (a few hundred MB) of "wasted" storage space on F2FS' logs is totally worth it, now that I have 12GB of storage available between /data and /sdcard combined.
8) Enable MTP mode in TWRP (under Mount) and transfer all my SD card contents back to the phone.
9) Now, I restored my backup - excluding /system and /boot. It warned me about the backup being made with ext4, but worked fine.
10) Now, the phone will boot as if nothing had happened -- but your /sdcard will not be accessible, due to the change in structure. You need a new kernel image that's compatible with hboot 2.16's partition layout. I did this by updating my ROM to the newest (9/1) snapshot of CM12.1 - here: http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266 -- so I applied that zip, the newest GApps, and the SuperSU zip.
That's it! Just like it was yesterday, but with practically infinite room to move. :good:
Update -- for S-ON, I think you need to get S-OFF in order to modify "hboot". I'm not actually sure. If you get to step 4 and you do NOT see hboot 2.16 installed, you should grab Rumrunner and let it work its magic. It's a very condescending and often frustrating program at first, but it gets quite genuinely hilarious in its status messages as it runs. As long as your environment is clean (ADB driver matches the ADB version bundled inside rumrunner's executable, which you can check while it's running by examining the files in a hidden folder it creates when you run it), it'll work its magic and you'll become S-OFF. Backing up is a good idea before embarking on rumrunner, of course. Also -- I've used Moonshine before as well, and it seems like Rumrunner was created to fix a lot of program-logic bugs in Moonshine - does a much better job of recovering from unusual conditions that hang up Moonshine. Rumrunner > Moonshine. :victory:

Thank you very much for your summary. I really appreciate your work here!
At the beginning I was really excited after going through your posts... Now, after my first attempts, I'm back to reality ^^
At first I tried to flash the bootloader while staying S-ON. During the update process I received the following error: remote: 99 unknown fail.
I can't really define what causes the error but I thought it could be related to S-ON. That's why I decided to go for S-OFF.
After using rumrunner and moonshine (which both failed) I found out, that apparently I need to go back to a stock rom. Switching to S-OFF and having cyanogenmod installed seems to be not supported.
At this point, being tired and bugged, I stopped for a rest...

Urds said:
I can't really define what causes the error but I thought it could be related to S-ON. That's why I decided to go for S-OFF.
After using rumrunner and moonshine (which both failed) I found out, that apparently I need to go back to a stock rom. Switching to S-OFF and having cyanogenmod installed seems to be not supported.
At this point, being tired and bugged, I stopped for a rest...
Click to expand...
Click to collapse
Hah, yep, I can relate... it's a HUGE pain in the rear to find the right RUU to get this thing fully stock again. But I think I've mastered the process, and I'll pass that along here as well.
Even through all this, once you get it S-OFF'd and updated to hboot 2.16, you can restore TWRP (or your preferred recovery) and restore your ROM just as it was before - most likely. Performing "S-OFF" also allows recovery to flash the "boot" (kernel) partition, instead of needing to use "fastboot flash boot" separately from installing the ROM.
For my RUU, I believe I used a package called (*deep breath*... may need to remove spaces) RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe - which contains every iota of data that the phone consists of - bootloader (it will S-On your phone again), radio firmware, kernel, system storage, partition layout, *everything*. So definitely back up your ROM and the resulting internal /sdcard contents before doing it.
When you run that, it'll pretty much do everything on autopilot, though you may want to launch it from Fastboot mode (Power+VolDown from powered-off state). I found that it only works reliably in a system with an older OS, though - I had trouble with Windows 8 and obviously Windows 10 as well, as they wouldn't detect the bootloader device. Windows 7 may be compatible, but I did it on a Server 2003 (Windows XP) system myself.
Then, you can Rumrunner it, then (may need to) unlock it again (HTC method), verify you're at hboot 2.16 (perform steps above if needed), restore your recovery, restore /sdcard, restore your ROM using MTP mode, and should be good to go!

FalconFour said:
(Instructions omitted)
Click to expand...
Click to collapse
Hey @FalconFour,
Just wanted to express my thanks for writing your OP. Earlier today I found it when I was looking for a way to increase my data partition. Thanks to you this was a totally effortless process. Thanks! :victory:

voidzero said:
Just wanted to express my thanks for writing your OP. Earlier today I found it when I was looking for a way to increase my data partition. Thanks to you this was a totally effortless process. Thanks! :victory:
Click to expand...
Click to collapse
Thanks @voidzero! It'd be awesome to gain some +rep for it :laugh::good:
{
"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"
}
update: Oh! I see you already did, LOL. Sorry! Well, for anyone else passing through these internet tubes, then! Crap, now I wish I could delete.

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.

[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