yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] sicex:
Device goees black after android logo

Well i got this tablet as a second one to the one i already own and use AOKP. This new one however i tried to get to cm9 on it. I was in a rush and i got into recovery put the cm9 and compatibility zip 1.2 and ran them. I had forgotten to wipe the device >.< so i wiped it then put cm9 and the compatibility zip 1.2 aaaaaaaaaaand i forgot to put gapps. So i hit reboot device.... Now it goes passed the android screen and just sits there. I do not think i have the drivers for this device. I do have android SDK installed and installed the google drivers, but i cannot get livesuite to pick up the device. I follow the instructions after reading the entire amount of pages in this thread. I get the connect sound when i connect the device trying to get device picked up by live suite but no disconnect reconnect sound. In device manager the device just shows as android device with yellow exclamation point. What am i doing wrong? any help greatly appreciated!

Well i get some strange behavior. Sometimes while attempting to get livesuite to pick up the device livesuite will just randomly place itself in the system tray. No message or anything. Is that good? When i hold the power button and the + volume button while the device is off and plugged into the pc it brings up the driver installation screen and is installed as the driver that was in stalled with livesuite

and also if it helps it says its an A13 on the box
[Upgrading, Modifying and Unlocking] Ilithis:
Does anyone know of a 4.1.1 or later rom that I can update the A13 version with? With all the hardware buttons, wifi, and the g-sensor working would be preferable. Most of the results from Google come up with buy pages for the tablet D=
[Upgrading, Modifying and Unlocking] malmostoso:
There's your answer right there. Get those drivers installed and then try again.

For my A10 I used this:

http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html

Not sure I was just lucky, but it all works.
[Upgrading, Modifying and Unlocking] sicex:
Noob question

What do i do with said drivers? Where do i put them?

---------- Post added at 08:49 PM ---------- Previous post was at 08:24 PM ----------

As always the best site for droid developers ever. Finally got my popup message. Not sure what i changed that helped. First i moved live suite 1.09 to my desktop in a folder there. I deleted the other live suite versions 1.07 and 1.09 from downloads folder! Also for stock roms i really wish i could post the ones i have been using. They always work without a hitch! Basically what i had to do was have device manager open and REMOVE all of the livesuite drivers that were taking over my device. After that first try with live suite worked perfect. Having had trouble i went ahead and plugged my device into the pc while on! holding volume up and then repeatedly pressing power to get the driver to pop up and remove the 2 of them there! after that off device went and i flashed F1(A13) 4.0.4 firmware 20121129.1.1.1 from shenzhen lyric pioneer Company look them up they have all the stock roms you could want! Yes it flashed in english. Only problem so far is orientation is always upside down! hahahah. Even included working playstore! Device is more responsive than when it first arrived lol. SO piecing together every little bit from the different post made a big difference. SO those having issues do try or look at your device box. I couldnt get any A10 stuff to run but the first A13 rom worked like a charm :victory:

wifi works auto rotate needed to be turned off due to always doing the opposite of what it should. But wifi working perfect with 4.0.4
[Upgrading, Modifying and Unlocking] sicex:
So i get as far as well not very far at all. i get to command adb pull /sdcard/nanda/script.bin and i get no device found D: noob question i know am i missing something? im doing this via CMD on windows 7 64 bit btw

now when i get to mount it says device is busy >.<
[Upgrading, Modifying and Unlocking] hwengmgr:
Booting into Recovery?!?!

This tablet is most frustrating when it comes to getting into recovery.

I followed the instructions in this thread: http://xdaforums.com/showthread.php?p=39114713

and was able to install CWM successfully. I followed the instructions for doing it with the tablet in normal mode and used adb to run the install-recovery.sh script (you have to remove the parentheses from the first line around the word "dopa").

However, I am baffled by the lack of easy ways to boot into the recovery. So far I have found 2 that work:

1) In "settings" in the "backup and reset" sub-menu, there is an item to "boot into recovery". This one seems to work.

2) The 3rd method in the thread linked a few lines above also works. I did the "echo -e..." command line from adb and followed the instructions to reboot and went into recovery.

However, I have found no other ways to get there. Many posts have magic incantations of button pushes, none of which seem to work for me. On other phones/tablets, its usually some combination of the volume keys and power button at the same time, but none of those seem to work here. Various programs like ROM Manager or Rom Toolbox have a "reboot to recovery" options, but they just do a normal boot. Even the "reboot to recovery" option in CWM ends up doing a normal boot!!!

I am hesitant to put on another ROM until I know I can easily get back to recovery. If a new ROM does not have the recovery boot option in the backup and reset entry, I only have the adb method to get there.

Anyone bumped into some set of button pushes that actually works?

This Trio stealth 7C is an A13 with 10 partitions.
[Upgrading, Modifying and Unlocking] coolbeanz:
HELP I think I bricked mine!

I have a trio step pro from tiger direct (after rebate deal with total defense)

I installed clock work mod but it would only go into clock work mod from the reset button under settings (doesn't go in with vol up plus power hold)

I installed AOPK rom in clockwork mod and then reset and it goes to a black screen ... nothing .. I have bricked my tablet, I tried ADB and no luck

when I boot with volume up and power button I hear the USB on my laptop plugging into something but it is not adb since I cannot connect to adb shell, can anyone help with my brick? :crying: - under drivers it is detected as unknown device with this "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"

Also this is a A13 with 10 partitions

---------- Post added at 04:42 AM ---------- Previous post was at 03:57 AM ----------

Well I just read online that live suite will still flash, can someone post a back up of the original A13 with 10 partitions rom? Much appreciation for anyone who can help me out! :victory:
[Upgrading, Modifying and Unlocking] Ilithis:
I have the TigerDirect version of the tablet that is floating around which is an A13. I'm not sure about the 10 partitions thing, is the only difference between the 9 and 10 partition versions is that one has the microSD card slot working and the other doesn't? I can post my ROM which is what my tablet was shipped with, but I have no idea how one extracts the ROM from the tablet. I can help you get my version of the ROM if you can tell me what I need to do to get it to you.

I haven't tried installing a 4.1.1 ROM yet, but I plan to eventually. If you know of one that works well with this tablet, let me know.
[Upgrading, Modifying and Unlocking] sicex:
Um for recovery i just went to options and boot into recovery. If you have CWM like i did you can also use that option to get into recovery. As for 4.1.1 rom im starting to think there are no plans for one. I am however happy with 4.0.4 rom from http://www.lyxfsz.com/en/downs.htm?sortid=0_22 works better than when i first got it and i dont feel the need to get 4.1.1 anymore:victory:
[Upgrading, Modifying and Unlocking] dolorespark:
An FYI for Stealth Pro 7C owners...

You cannot install any of the "standard-issue" versions of CM10 or AOKP on your tablet. They're all built with an A10 kernel and you have an A13 processor. Certain key components such as the display are handled differently, so they're just not compatible.

If you want to try those mods, you have two choices:

* look around for someone who's already created a hybrid with, say, CM10's "Android" and a vendor's stock A13 kernel & drivers

* if you're ambitious, create your own hybrid (that's what I did for my 4.3-inch A13 tablet). It's a helluva learning experience :D
[Upgrading, Modifying and Unlocking] Ilithis:
So I'm going to start experimenting with this ROM:

htt p://w ww. techknow.me/forum/index.php?topic=4595.0

this weekend permitting my other weekend activities don't get in the way. I'm sure it won't work out of the box and that I'll have to modify some files and find the right drivers, but I'll give it a whirl and hopefully come out with something that has everything working. Wish me luck!
[Upgrading, Modifying and Unlocking] fbueller:
So did you have any success? :)
[Upgrading, Modifying and Unlocking] MDewitt:
Can anyone help with getting Play Store on mine? I've tried everything I've read and cant get anything to work... I bought 2 of these one for me and my gf and kinda sucks not having any apps
[Upgrading, Modifying and Unlocking] pbot:
You can always download the Amazon app store if you need some free apps in the short term. I think there is a paper in the box mentioning another app store as well but I don't have it handy.
[Upgrading, Modifying and Unlocking] malmostoso:
Amazon market, Getjar and Androidpit are the three available on apps.triomp3.com.
[Upgrading, Modifying and Unlocking] crmoody76:
ok i can confirm that this rom is fully compatible with the A13 versions of this trio. after installing you will need the ts zips that are provided at the bottom of the page. after some trial and error the multiple ts zip(3rd one in the list) fixes the touchscreen and rotation issues plaguing the A10 models. this rom zips along and so far i have had no problems. :laugh:

update/edit:

after further review the touch keys dont work and vol up/down are wonky :(....
[Upgrading, Modifying and Unlocking] ftkatyowser:
Just bought this as a replacement for another tablet. When I got it, the wifi would not turn on properly so I flashed this rom going through the recovery menu. Now upon booting, the screen with the android robot comes up, and then switches to a black screen with the backlight on and nothing happens. What I've tried:

-abd reboot recovery results in a restart and nothing else

-abd reboot bootloader also results in nothing

-adb devices does show that it sees the devices

-adb shell results in " - exec '/system/bin/sh' failed: no such file or directory (2) -"

Trying to flash via livesuit results in device not found error, and I can't boot into recovery via the hardware buttons. I glanced through this thread and everything involved booting into recovery, which I can't do. Help?

I'm currently waiting on the tablet to die, assuming the backlight staying on will kill the battery, and see what that will do.
[Upgrading, Modifying and Unlocking] Ilithis:
Update

I can also confirm that the ROM works with the A13 version that many people got from TigerDirect. However, as noted by Toxicro, the touchscreen driver that came with the ROM does not work. I started experimenting with the touchscreen drivers starting with the 3rd in the list as mentioned by crmoody76, but it did not work either. Later on tonight I plan on testing the other touchscreen drivers and hopefully find one that works.

I can also confirm that the volume buttons are off a little bit, and that the 3 capacitive buttons don't work (but that might be because the touchscreen driver isn't right, not sure). Currently the volume up button is the volume down button, and the volume down button performed the functions of one of the capacitive buttons (the one that brought up an options selection in the bottom right hand corner, it had 3 options to choose from).

If anyone knows the touchscreen driver used for the A13 version of the tablet, it would speed up the process so I can get to fixing the buttons. Using lsmod through adb might give the answer, but I forgot to do this before I flashed my tablet to 4.1.1 (dummy me, but I did backup my old ROM). This was my first manual upgrade and it was pretty simple once you have the tools in front of you.

EDIT:

In my tiredness last evening I was not reading carefully and used the 3rd touchscreen driver in the normal list, it turns out I should have used the 3rd multiple touchscreen driver link if I would have read crmoody76's post close enough.

EDIT2:

Over lunch I installed the right touchscreen drivers, the same as crmoody76 and the touchscreen now works. However, I noticed that the g-sensor isn't functional either. So now I just need to fix the g-sensor and remap the buttons to have a fully functional (wireless included) 4.1.1 ghetto tablet. Remapping the buttons shouldn't be difficult, it looks like a simple pull, edit, push for a file, but the g-sensor I actually have to look into.
[Upgrading, Modifying and Unlocking] dolorespark:
A bit of research can save a lot of effort: in post 423 I listed all of the drivers for the 7C and what they do. Your gsensor is (likely) a dmard06 - however, installing just that driver may not get it working. You also need a /system/lib/hw/sensors.exDroid.so which supports that chip. Some versions support a single gsensor while others support multiple chips. The easiest way to find out whether a given version of the library supports the chip in question is to open it in a hex editor and search for the string "dmard06".

Sadly, after all that, the gsensor still may not work if the ROM you flashed didn't originally support a dmard06. The reason is that LiveSuit replaced your bootloader partition, wiping out the tablet's original script.bin which identified the various chips your board used. If the replacement script.bin has an entry for this chip, you're set. If not, you have 2 options.

The simpler is to replace the current bootloader partition with the original. You say you did a backup, so hopefully you have a copy of nanda, the bootloader partition. If so, copy the image to your internal SD card, then from an adb shell prompt, run "cat bootloader.img > /dev/block/nanda" (replace bootloader.img with whatever the actual filename is). You can do this while booted normally or from recovery. A downside to this method is that many vendors add really screwy entries to stuff like the touchscreen parameters so that their version of the driver will work correctly. So, while your current version of ft5x_ts.ko may work now, it may break if the driver requires proprietary entries that the original script.bin didn't have.

The more complicated but more reliable way is to pull your current script.bin, decompile it using fexc, modify the gsensor entry, then recompile it and push it back. While fexc was originally a Linux-based tool, there's now a Windows version - do a search for it here on XDA. If you need further assistance, post a question & I'll try to help.
[Upgrading, Modifying and Unlocking] Ilithis:
Now that I read this, it makes sense why what I was trying to do last night didn't work. I found a driver that made the touchscreen work, thanks to crmoody76 from above, and then I found a g-sensor driver that also worked thanks to your post 423. So I thought that after installing the touchscreen driver, then installing the g-sensor driver, that everything would work. That's not the case though, when I installed the g-sensor driver, the touchscreen stopped working (and the orientation was 180 degrees wrong, but that's an easy fix from what I hear). So since it seemed like a mutually exclusive thing (have the touchscreen or the g-sensor working) I tried mashing the two separate installations together. This resulted in neither parts working because I'm not proficient at driver writing. Basically, what I did was modify the preinstall.sh and setupsensors.sh files, since those are pretty straightforward to edit, to include the touchscreen driver and the g-sensor driver in one package. I wasn't sure what to do with the script.bin and sensors.exDroid.so since they seemed like they can't be hand written.

The script.bin and the sensors.exDroid.so mention dmard06, but don't mention ft5x_ts in the g-sensor's files. Meanwhile, the touchscreen's files mentions ft5x_ts in the script.bin and not in the sensors.exDroid.so and doesn't mention dmard06 anywhere. So what I'm getting is that in reality both the drivers are on my tablet, its this script.bin and sensors.exDroid.so that are giving me grief and that if I can modify their entries to include both drivers for both the g-sensor and touchscreen, life might be good. I'll give fexc a go and decompile these two files and see what I can make out from the results. Thanks for your insight dolorespark!
[Upgrading, Modifying and Unlocking] crmoody76:
:good:

i want to thank you both for the work you've done with this tablet. toxicoro's rom is the one i believe this tablet will benefit the most from, as far as speed and stability. i also forgot to mention that the camera app crashes when you open it. i also just purchased another one off of ebay that has the original firmware which i will be dumping and making an image of so those who want to have an original can flash their tablets back to stock if they want to sell or tinker with it when making custom roms.:fingers-crossed:
[Upgrading, Modifying and Unlocking] Ilithis:
So about your camera issue... I'm not having a problem with it in any of the three modes (P&S, video, or panorama). I think its down to a driver issue to get the camera up and running properly. The drivers I've been messing around with are:

http://www.4shared.com/get/IjAuQW3y/gatgat23-v5.html -gsensor working

http://www.4shared.com/get/Qae35K0B/SolomonSam-v1.html -touchscreen working

As for the g-sensor, I'm a little lost. I popped open the script.bin files of both the driver that made the g-sensor work and the touchscreen work and copied the g-sensor parts over to the script.bin that made the touchscreen work. Then, I recompiled the script.bin, edited the setupsensors.sh to include the insmod lines for the dmard06 and the mma7660. I used both the sensors.exDroid.so files and neither produced results where the g-sensors worked, but the touchscreen still worked on both attempts. It seems the sensors.exDroid.so is linked to the g-sensor so I'll have to decompile it and take a look.
[Upgrading, Modifying and Unlocking] crmoody76:
which ts file are you using, because the one i suggested,(i think) crashed the camera app, whether using the camera icon itself, or trying to go through the 2160hd player app.:mad:. i took the a13 stock rom that was listed on the susposed manufacturers' site and flashed it and ran lsmod, and found that the camera line shows as gc0308, which i dont see in any of the ts files, though i could be wrong. i dont have ANY experience in decompiling and recompiling code so whatever i do will be from tutorials listed on technow's website. but anything to help us trio owners will be worth it in the end:o.
[Upgrading, Modifying and Unlocking] Ilithis:
Incremental Update

The two files I linked above are what I've been using mainly. I have tried using almost all of the drivers on techknow in the thread the ROM is available for download. Nothing has worked for me touchscreen-wise besides the one you recommended (the SolomonSam link in my previous post). If you install the stuff from the Solomon link, then the other one, then solomon's again, does the camera work?

I used the Uberizer 1.4 to backup my previous stuff on the tablet, so I popped open the original init.sun5i.rc file to find that the touchscreen driver is indeed the ft5x_ts while there was both the mma7660 and dmard06 in there. I feel there might be a few ways to fix my problem:

1) Edit my init.sun5i.rc file to include insmod lines for ft5x_ts, mma7660, and dmard06. The problem with this is that my init.sun5i.rc file reverts back and nullifies any changes I have made to it upon reboot. This is presumably done by some recovery process and I was wondering if anyone knows how to disable this process from happening so the changes I make to init.sun5i.rc stay.

2) Find a set of files specifically for ft5x_ts, mma7660, and dmard06 since I can't combine them without stuff not working. I'm not sure what I'm doing wrong when I try and merge the two drivers listed in my previous post.

EDIT: Seems like romkitchen would be the way to modify the rom to add the necessary drivers but romkitchen.org is down :(

EDIT2: miniand kitchen is what was recommended to me on techknow. I'm going to attempt to take Toxicro's ROM and build one for us Trio Stealth A13 people. This should fix all our driver issues, button issues, etc since its a ROM build specifically for us. Now to install a virtual box and linux...

https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images is what I'm following. However, let it be known that I was warned that the guide here is missing a step with the bootloader or something.

https://www.miniand.com/forums/foru...esuit-images-for-flashing-internally-to-mk802 (read the entire thread)
[Upgrading, Modifying and Unlocking] dolorespark:
The root filesystem resides on a ramdisk. It's contents are taken from a compressed file stored in nandc which also contains the kernel. Editing files in the root directory accomplishes nothing because they are recreated every time the system starts. Instead, you have to copy the boot image to a disk, break it apart, make your changes, then reassemble it and copy it back - either directly or via a LiveSuit image.

The miniand tutorial and tools package are invaluable resources - but flawed. Rather than trying to create an entire LiveSuit image & dealing with those flaws now, I'd suggest you focus on recreating the boot (a.k.a. root) partition. You can either use the A10 kitchen to spit up the LiveSuit image so you can get a copy of it (after extraction, the file is named "RFSFAT16_BOOT_00000000000.fex"), or, you can just pull it from your tablet ("cat /dev/block/nandc > /mnt/sdcard/boot.img"), then copy it to your PC.

The miniand package contains the tools you'll need to split up boot.img and to put it back together when you're done. To reinstall it, you just reverse the extraction process: copy it to your internal SD card, then run ("cat /mnt/sdcard/new-boot.img > /dev/block/nandc"). Since the system is running from a ramdisk, you can even do this while it's booted normally. (Note: if you pull the image from nandc, you'll get a 32mb file, even though the actual contents is only about 11mb - the excess will be ignored.)

The drivers for the touchscreen, gsensor, and camera all work independently - changing one should not have an effect on another. Only the gsensor (and other stuff our cheap tablets don't contain) uses sensors.exDroid.so - it plays no part in making the touchscreen work. The only file that will bolix-up everything is script.bin (and script0.bin which is identical and must match). Constantly swapping versions is a sure way to break stuff that was working.

Your best bet is to pull the script.bin from your original stock ROM (which you backed up, I hope), then modify just the entries you need so they match those in the script.bin that got a particular driver to work. The reason for starting with the stock version is that script.bin controls

all

of the hardware, not just a few sensors. For example, it controls RAM timings. The version from some mystery ROM could be running the RAM too slowly, causing needless loss of performance, or too fast, causing all sorts of hard-to-pinpoint instability. Once you have Linux installed, you'll be able to mount the bootloader image as a disk, copy the file elsewhere, decompile it using fexc, etc, etc.