Database Info

[PC-UTIL] [Discontinued] [Source Opened] Android RTL Auto-Patcher + ProTools (v.1.5)

Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"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"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
​​
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.​
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:

Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)​

If it will work man i'll give you a real big THANKS!

Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..

Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App

congratulation
Congratz of your new Project!
I will give it a shot as soon as i can

my teset here ..
this is my test in the log file attached
thx

I appreciate your efforts
reverse numbers problem still exits
big thanks

Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.

Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping

Thank you
Thank you very much for your great work.

The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/

NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.

this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0

Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App

Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App

Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!

Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing

jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.

This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).

[APP][4.0+] Root Transmission - Root other devices using your phone!

Root Transmission
{
"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"
}
Root Transmission: the ONLY app that allows you to root other phones straight from your own device!
Inspired by Kos's p2p-adb hacking toolkit (http://hak5.org/episodes/hak5-1205), this app is a pleasant, easy way to root other phones while away from your computer! Just two buttons, Root and Unroot! Connect the cable and root away! It couldn't be simpler!
Even has its own terminal window so you can see exactly what's going on while your phone does its thing!
You will need a ROOTED device capable of USB hosting (USB On The Go), a USB OTG cable and one-click root scripts for the devices you wish to root.
Scripts and their associated files should be placed in /sdcard/RootTransmission/*devicename*/*version*/, otherwise it will not be available for use. *devicename* and *version* can be whatever you want.
Note that this is an UNSTABLE version, and you use this app at your own risk. Occasional force closes are to be expected (though they will most likely not break the phone you are trying to root). Incorrectly written scripts can permanently damage or brick both devices involved, so only use trusted 3rd party root scripts and at your own risk.
Click to expand...
Click to collapse
Screenshots
Changelog
1.01unstable
fixed bug that sometimes caused crashing when user closed app
fixed bug that caused app to crash if scripts directory did not exist
Much smaller size (166k)
made it for Android 4.0 and up (accidentally had it for 3.1 and up in Play Store, will re-add Honeycomb support if I find that it works reliably with it)
1.0unstable
initial public release
Click to expand...
Click to collapse
Planned features
Downloading scripts within the app
Nicer GUI
In-app help text
??? Suggest some!
Click to expand...
Click to collapse
(Removed from Play Store because Google said it was "dangerous")
Please do not mirror this apk, it is to be downloaded exclusively from XDA-Developers. Failure to comply will result in the removal of this app from XDA.
I've attached a zip with the files needed to root a Verizon Galaxy S3 (SCH-I535), extract it to /sdcard/RootTransmission/ to use.
Note that since I only have one USB host-capable device (my own S3), no warranty is provided over the functionality of this zip since I am unable to fully test it. (It is a repackaged version of the DebugFS one-click root found at http://forum.xda-developers.com/showthread.php?t=1883984 and thus will only work if the device to be rooted is running ICS, which shouldn't be a problem as of yet.)
Again, this is an unstable test version. It should mostly work, but no guarantees on its functionality.​

Reserved for future use

Reserved for future use.

what device is supported? what device supported that can be rooted?

chev said:
what device is supported? what device supported that can be rooted?
Click to expand...
Click to collapse
In order to run the app, your device (the device that is already rooted) must support USB hosting/USB OTG. Most newer devices have this.
This app uses adb and scripts (which you must provide) to root devices. If there is a root method for the device that uses adb, then it will work.
In the case of the Verizon Galaxy S3 (my primary device), the root method for a stock ROM is to use adb to push an exploit that will allow us to install Superuser and the su binary. I believe the Asus Transformer Prime uses a similar method.
If the only root method available involves using a program such as Odin/Heimdall or a manufacturer's phone flashing utility, or a zip must be flashed in recovery in order to gain root, it will definitely not work. In the case of the HTC Sensation, you must flash a recovery and boot into it, then flash a zip containing the su binary as well as a controller app such as Superuser in order to gain root. So the HTC Sensation could NOT be rooted with this.
In the future I plan on building a compatibility chart within the app to determine which phones can run this app and which phones can be rooted with it, as well as downloads for the rooting process. In the meantime, if there is a phone you are looking to root with this, let me know and if possible, I'll craft a zip to use with this.

Updated Root Transmission to 1.01unstable.
Following changes were made:
-bugfix: app occasionally FC'd when closing app
-bugfix: app crashed if scripts directory did not exist
-smaller size (166k, old version was 1.62mb)
-made it available only for 4.0 and up (had it set to 3.1 and up by accident)
Available in first post or in the Play Store.
Keep sending in those bug reports, it really helps!
Also, if you have any new features you want to suggest, let me know.
I'm considering the following so far:
-Downloading scripts in-app
-Nicer GUI
-Help text

Added script for the Asus Transformer tablets (TF101/TF201/TF300T/TF700T) to the first post. It will only root tablets on 4.0 or below.

This app looks promising, keep it up this great work, :fingers-crossed:

Theoretically could this run any script over adb on another device. not just a root one?

one x
Hey does this work with the one x international version?

I believe that in order for the app to work properly, adb must be running as root, so no. It's not possible to use this with a non rooted phone.
HTC One X should be able to be rooted (as well as other devices relying on fastboot), but I haven't added support for it yet. A fastboot binary for ARM is available, so I'll package that into the app for next release. Stay tuned. However, I don't know about unlocked bootloaders and all that on HTC devices, so beware.
I'm also going to take a look at the Heimdall source code later so that you can perform Odin flashes over USB. This means that basically any Samsung phone should be able to be rooted, even without a one click root script.
All this stuff will take time though, and with school still going on it might take some time. But I'm definitely working on it!
Sent from my SCH-I535 using Tapatalk 2

Would it be possible to use this app to flash unsecured boot.img and then recoveries? Basically have it set up to download the recoveries and boot.img from a ftp or something? Can we basically just use the host phone as a standard ADB and Fastboot commander? Using regular commands?

root tranmission
i download the file, and recive the next error while unstalling:
parse error
there is a problem parsing the package
there´s any fix?
thanks in advance

Draciel882 said:
Would it be possible to use this app to flash unsecured boot.img and then recoveries? Basically have it set up to download the recoveries and boot.img from a ftp or something? Can we basically just use the host phone as a standard ADB and Fastboot commander? Using regular commands?
Click to expand...
Click to collapse
This is on my to-do list. I might also include a terminal emulator with access to the app's adb/fastboot binaries.
teran220 said:
i download the file, and recive the next error while unstalling:
parse error
there is a problem parsing the package
there´s any fix?
thanks in advance
Click to expand...
Click to collapse
Try installing from Play Store.

wchill said:
This is on my to-do list. I might also include a terminal emulator with access to the app's adb/fastboot binaries.
Click to expand...
Click to collapse
That would be awesome, let me know if you need some help testing. I've been wanting to be able to do this for awhile. It would pretty much eliminate the need for a computer when flashing roms on devices that have their bootloader already unlocked.

how to check my device is usb otg/host capable ?

anazhd said:
how to check my device is usb otg/host capable ?
Click to expand...
Click to collapse
Use this app by Chainfire
https://play.google.com/store/apps/details?id=eu.chainfire.usbhostdiagnostics
Sent from my SCH-I535 using Tapatalk 2

Wow, the idea behind your software is brillant!
I yet see a future world in which handset liberation is achieved and spread among users in dark corners of the streets! :silly: :laugh:

Hey there wchill , seems like you are an app dev rookie as I seen some stuff , well you aren't so different from me , PM me , I will help you in your project , btw I have seen a small thing , that the Settings button does nothing , to remove it remove in your mainActivity the lines that say onCreateOptionsMenu , as long as you don't need an options menu !
EDIT : No offence for calling you a rookie , I may have underestimated you , because your work is amazing , but I was talking the Java side of your knowledge , sorry if I offended you !

seaskyways said:
Hey there wchill , seems like you are an app dev rookie as I seen some stuff , well you aren't so different from me , PM me , I will help you in your project , btw I have seen a small thing , that the Settings button does nothing , to remove it remove in your mainActivity the lines that say onCreateOptionsMenu , as long as you don't need an options menu !
Click to expand...
Click to collapse
I know that the options menu is there, but I'm planning on adding to its functionality so there's no point in removing it yet. Don't worry, I didn't forget about it
Also, I only have one year of experience in Java, so my skills definitely are not the most top notch out there. I'd say not bad for being self taught though.
Anyway, in app downloads should be working by this weekend, depending on how much homework I get this week. Did a lot of it today, just need to make the frontend for it. After that I'll work on improving the GUI, because I really couldn't be bothered to spend more than 5 minutes making it what it looks like right now.
Expect an update in the next few days
Sent from my SCH-I535 using Tapatalk 2

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

[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

LineagOS - Jingpad

Has anyone looked into compiling / porting LineagOS for the Jingpad A1? They released the source code. Why use LineagOS and not their released because theirs is in Chinese and it's lacking features available in LineagOS. I understand that the company has stopped developing their default OS and everyone with them now kind of has a dead product. I someone ported UBports to it, but Ubports lacks somethings that LineagOS / Android brings to the usefulness for a tablet. I know they had android app support that you could install on their default OS, but it has bugs and some apps were slow or errored out upon launch.
jingpad-bsp
jingpad-bsp has 421 repositories available. Follow their code on GitHub.
github.com
Android ROM source code for JingPad A1
The source code has been zipped into the 8 packages below, you have to download them all before you compile. How to compile Full compilation (take the userdebug version as an example, if you are editing the user version, just change the ud710_3h10_native-userdebug-native in the instruction to...
forum.jingos.com

[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS

Excellent thank you for this. I am trying to flash my system with the image in the post. The process worked, thank you for showing me the post.
How to change to english
edit the following file in the source code
/source/device/sprd/roc1/ud710_2h10u/jingos/device.mk
edit the following lines.
persist.sys.language=en
persist.sys.country=US
persist.sys.timezone=America/New_York
persist.sys.locale=en-US
ro.product.locale.language=en
ro.product.locale.region=US
and compile
cd /source/vendor/sprd/release/IDH/Script
./build_pac.sh -a ud710_3h10u_native-user-native -b all 2>&1 | tee build.log
​

Have there been any new developments for the JingPad? I have one and I would consider putting Lineage OS on it. However, I'm not competent enough to build it from scratch. Is anyone developing AOSP for this tablet?
I am presently running UBPorts (Ubuntu Touch) and it is certainly less than stellar. I can't get WayDroid to run. Things might change when UT upgrades from 16.04 to 20.04 in the near future. But for now, I am checking everything before I stick it in the closet.

Hmm, I guess no one has mirrored the instructions?
Because all jingos.com links are now dead.
Maybe someone who has copied the instructions or the original author could add them to this thread?

I have a lot of the files for this tablet including the flashing application Research Download, the .pac file from January 2022, and USB drivers for Windows. I have the .docx file with the Research Download instructions.
I am leary to reinstall the JingOS without clear instructions on how to do it since I now have UBPorts installed.

LoTo62 said:
[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS
Click to expand...
Click to collapse
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.

r3d10tu5 said:
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.
Click to expand...
Click to collapse
No. Sorry. The only files I have are the original files distributed with the JingPad.

I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007

r3d10tu5 said:
I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007
Click to expand...
Click to collapse
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.

jmd8800 said:
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.
Click to expand...
Click to collapse
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
How did you install the gapps?
I tried again today, and finally found how I was able to use gapps before.
You should have booted to the system once, before you boot to recovery and flash gapps.
“open_gapps-arm64-10.0-pico-20220215.zip” and “open_gapps-arm64-10.0-nano-20220215.zip” are probably the only two available version that work.
After reboot, you should get an error like “This device isn’t Play Protect certified” which keeps popping up, not “There is a problem contacting with google server”.
Steps:
Go to play store, click sign in;
It said “This device isn’t Play Protect certified”, click that green link “g.co/AndroidCertifiedDevice”;
Follow Google’s instructions to register your device;
Go to Settings, try your best to force stop gms & play store and clean their data;
(But do NOT clean gsf’s data! Clean cache is enough)
Go to play store and sign in before gms know it.
Click to expand...
Click to collapse

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to ask that you properly clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
Looks like I have some work cut out for me. If I can get this to work and cover my needs I'll be happy. If not .... back in the closet it goes and I will buy an Apple or Samsung next week as I need something for travel.
Thanks

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?

jmd8800 said:
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?
Click to expand...
Click to collapse
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears

r3d10tu5 said:
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears
Click to expand...
Click to collapse
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again

jmd8800 said:
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again
Click to expand...
Click to collapse
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
{
"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"
}

r3d10tu5 said:
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
Click to expand...
Click to collapse
Thanks. I was just about to try again when I saw your post. Using this method I got better results but I cannot install because 'my driver version is too low'. I'll have to dig into this. But it appears to contact the JingPad and even errored out in the status bar. Progress!
I don't use Windows so I don't have a legitimate Windows OS working. It says it is test mode as I've not registered it. I can source the BIOS to find the key and hopefully that will let me get to a point where I can update the driver required to connect the PC and the JingPad.
Thanks again

Success! Thanks for all of your help @r3d10tu5
Well.... Success installing the pac file. I'm still working on the gapps. the adb command said it was a successful instal but Google software is not on the screens.

Just a thought as I was playing with this. Has anyone tried to use microG instead of going through all the hoops to get Google services running?