Database Info

[Q] Need Help with RoyQueen 9-Inch Allwinner13 Android Tab Touchscreen

Hello Everyone! I need help with my Royqueen 9-Inch Android Tab's Touchscreen..
This Tab was brought to me for repair because it was stuck on boot Android Logo so I went to Recovery and Factory Reset the device.. And it booted succesfully. All features are working except that I cannot install my downloaded apps even if I have checked the option to allow installation for unknown source. SO I decided to rooted the device with CWM a13-10part-v2, backed up the ROM in ClockworkMode..And Flashed A13 CM10.1 v1 it was again stucked in bootlogo..Resetting again to factory settings didn't solve the issue. I tried to restore the 2 back ups i have made prior to flashing and both failed to restore showing error while restoring system.. So I tried flashing it with some roms for a13 android, they all boots up but touchscreen isn't working.. I have tried all the ts module I can find but nothing solved my problem.. When I checked the serials on the touchscreen felx inside my device it shows goodix gt 827. I tried updated it with modules that has goodix driver and gt8xx but still not solved..I tried looking for gt 827 driver and I found in code google website but it is on h file type. And i don't know how to add it on my android system files correctly. I am not familiar with this file type.
Anyone knows where I can get gt 827 touchscreen module in zip file so I can update it on my device using cwm or debugging script?
I have found a stockrom of this device mx913_firmware_20121005 but it is a corrupted file and that's the only one I could find.
Firmware filenames that I have tried on this device are:
-9in_a13_android_4.2
-9INCH-TWA0910,GSL3680,DM-ARD06,RTL8188-IVVI-LOGO
-0259
-A13_CM10.1_MID13_v1
-cm_a13_20130628
-2.1 713b
-FaaastJB
-MaPan_MX913_DC_Jelly_Bean_4.1os_Root_Firmware_D20130601_UP (current)(TS not working)
Device Specs
Android Roy queen 9 inch screen ICS 4.0
8Gb Memory
Allwinner13 CC021CA 1CE1
Dual Core
800x480 screen
512 MB DDR3 RAM
board number A91V02 20121005
Here are images of my tab and its board
{
"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"
}
Hope you could help me..
Anyone could help me on any of these things listed below?
- gt827.ko touchscreen module
- stock ROM Mapan MX913 20121005
- custom ROM that has Goodix.ko and gt827.ko touchscreen modules.
I am very hopeful someone could help me.

Xposed Framework For Orginal Nvidia Shield Tablet Running 6.0.1?

I recently rooted my tablet and I would like to get Xposed Framework but I'm getting this error
"Xposed is not (yet) compatible with Android SDK version 23 or your processor architecture (armeabi-v7a).
CANNOT LINK EXECUTABLE: library "libdvm.so" not found."
Can anyone help??

You're trying to use an old version of Xposed.
http://dl-xda.xposed.info/framework/sdk23/arm/
Grab the latest (v85) zip from here and flash it.

Xposed Framework
Can this be done without a computer? (I have twrp) And also how safe is this

Help would be highly appreciated

I am on a OnePlusOne running CM13 (6.0.1) and got the same error after flashing the latest xposed-v86-sdk23-arm.zip

Where can I find the apk
Sent from my SHIELD Tablet using Tapatalk

Hfhdhshb said:
Can this be done without a computer? (I have twrp) And also how safe is this
Click to expand...
Click to collapse
Yes just download the zip on the tablet then boot to recovery and flash it worked fine for me in fact when I was doing my tablet all I did with the pc was the OEM unlock and the pushing of twrp after that is just used twrp to do root and xposed.

I'm having trouble flashing the zip file. Everytime I try I get 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"
}
After this all hell breaks loose while trying to boot. Running the uninstaller partially fix the problems but then I get no system partition free space.
In the end I must revert to the backup I did before.
Anyone having the same issue? I'm using twrp 3.0.2-2-shieldtablet
I also tried different versions (85, 84, 83, 82) but they all had the same error.

First you need to uninstall some apps from system partition using "System app remover" (root needed), then you can install xposed (official). It worked with me

Hi!
That's precisely how I eventually solved the issue I noticed that the system partition only had around 4MB of free space and xposed is bigger than that.
But thanks for the reply anyway and it will tip anyone that have the same issue in the future.

I got the same error message as above attempting to install v87 on my original shield tablet and I have 20gb free on the internal memory so that's not the issue for me.
Any suggestions?

How to install gapps on stock rom F3113

Hi, I think my problem is easy to solve, but I want to try others solutions. Well the thing is that I erased all gapps from my phone via rootExplorer (gms.apk, gmail.apk, sky...something.apk, etc) because I don't like those services; Until there, all works great (almost 4 months). I had problems with the internal storage (it was 99% but I didn't have many apps or big files) then, I erased the partition 'data' via TWRP, restarted the phone and all ok (the phone restored), but after set language, choose a name and last name and select a pin I can't go to the next step (in the section 'Google services' a dialog says: "unfortunately Google Play services has stopped") I guess it is because I don't have gapps installed...
I tried to flash gapps via recovery but I think it is not for stock roms...I know that the best solution is download the stock rom and flash it, but I don't have the capacity to download 2.7 GB...
So, someone who has idea about this problem??
sorry for my english, I'm still learning...
here a screenshot
{
"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"
}

Jesus Pocoata said:
Hi, I think my problem is easy to solve, but I want to try others solutions. Well the thing is that I erased all gapps from my phone via rootExplorer (gms.apk, gmail.apk, sky...something.apk, etc) because I don't like those services; Until there, all works great (almost 4 months). I had problems with the internal storage (it was 99% but I didn't have many apps or big files) then, I erased the partition 'data' via TWRP, restarted the phone and all ok (the phone restored), but after set language, choose a name and last name and select a pin I can't go to the next step (in the section 'Google services' a dialog says: "unfortunately Google Play services has stopped") I guess it is because I don't have gapps installed...
I tried to flash gapps via recovery but I think it is not for stock roms...I know that the best solution is download the stock rom and flash it, but I don't have the capacity to download 2.7 GB...
So, someone who has idea about this problem??
sorry for my english, I'm still learning...
here a screenshot
Click to expand...
Click to collapse
Download this version of Google play services from the link below
http://www.apkmirror.com/apk/google...s-10-2-98-446-146496160-android-apk-download/
It's the correct latest version for the xa and is totally safe I'm using it myself..
Sent from my Xperia XA using XDA Labs

update errors... 'This package is for "rk3368" devices; this is a "PX5" '

update errors... 'This package is for "rk3368" devices; this is a "PX5" '
Trying to update my unit from Android 8 to Android 9. Tried the simple and direct update but it failed. But, I didn't get the black screen. So, I made the bootable sdcard and tried that way. SD card runs, does it's thing, says it was successful and tells me to remove it to reboot. When I do, it goes to a black screen and nothing else. Even after leaving it sit for 30min. That SD flash process was waaaay fast for it to have actually flashed the image.
Now, I can't get the unit to do anything without that SD card.
I have found that if I pop the SDcard out between the logo screen and when the flash process starts it errors and takes me to recovery. From there, I've tried many different roms. Hal9k versions, Malaysk versions, stock 8.0, ota 9.0 for my device, and even a 6.1.1 version.
After going to "Installing update..." most give me an error "Warning: No file_contextsE3004: This package is for "rk3368" devices; this is a "px5"" then a couple of other errors before a (Status 7) Installation aborted.
All the roms that didn't do that have some kind of signature error. Likely need to redownload but haven't tried yet.
Not really sure what to try from here...
The device had the MCU of MTCE_GS_V3.01_3 when I started. I was able to update it to MTCE_GS_V3.40
The original build number was px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.201812222.104950 test-keys though I suspect that doesn't really matter.

Couple photo screenshots.
First one is the error.
Second is what it says after the bootable sdcard runs. I see nothing there about installing the update.zip
Last is what I get sometimes if I eject the ad card too soon trying to get to the recovery menu.
{
"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"
}
Sent from my Redmi Note 7 using Tapatalk

And... I fixed it.
Didn't find anything for this error using the search here. Did a search on google and it linked me to a post on this thread https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3929597
A reply told the user having the same problem to follow the SD card instructions at the beginning of the thread.
Instructions were the same as what I already followed but the file linked in the first post is different.
So, went through the process again. Installed that recovery and then was able to actually flash Android 9 onto mine.
Now for the fun part of getting everything configured and decide if this custom rom is the rom for me, if I go with the other one, or if I go to a more stock one. Least I can listen to the radio again...

Bootloop on Samsung Galaxy S3 with TWRP and Lineage OS 17.1

Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"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"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!

Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you

@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.