Hi everyone
I have the following tablet made by Mach Speed Technologies:
Trio Stealth G2 7" display
1GB RAM
CPU: Dual Cortex-A9 Dual 1.5GHz Multi-Core (its a dual core with a total of 1.5GHz)
its not rooted yet, I don't know how. If it needs to be rooted for this can someone quick explain that?
It came with Android 4.0 and has never updated through the settings, and the factories website does not even mention this tablet. The guy at Radioshack said I could install the update myself so here I am trying to figure out how.
If possible my original plan was to just instal the newest Android release. But today I just found out about ROM's.
So how do I install the newest Android release or if that's not possible a very secure custom ROM?
On one website it just said to put the rom image on a sd card (or in my case a microsd card) and put it in the tablet, then the tablet would use it as an update after asking you with a pop up. Is that true?
I have a bit of experience with Linux and coding but none with Android
with that update through sd card is true but most of times you need to have specific app or recovery as it may be treated as a rom and in that case you need to be rooted and have recovery. if you have experience u good with android as it is based on unix core
Well, I guess the first step is to be rooted then? How do I go about doing that?
I have the "Root with Restore by Bin4ry" downloaded on my computer and the usb driver installed from the google sdk manager.
But my computer does not see my tablet at all.
I have the same tab I have got adb to somewhat pick it up an it has aml flashtool and safe mode this shows u how to get into all those all but for safe mode copy this an past after youtube.com
/watch?v=TVQS9s3UqRg&feature=plcp
Sent from my G2 using xda premium
Dear Xda-team
First of all, let me congratulate you for the excellent job you do.
It’s a wonder to the eyes to see the degree of professionalism behind the visible side of this site.
I hope you can help me with my issue, having in mind my experience that I don’t have any experience yet installing new android firmwares.
I have a Lenco Tab-720 with the following carateristics:
• Android 4.1
• 8gb internal memory
• 512 MB Ram and 1.2GHZ cpu
and when I connect it to my computer, it says Alcatel Android ADB Interface, somewhere inside the driver details.
The tablet itself is nice in size and the screen is good, but it’s awfully slow, even if I have only facebook, a game or two, some Banking apps and outlook app.
My issue is that I can't find no tutorials or how to that explain to me how can I simply change my sluggish android 4.1 to something more fast.
One good thing about this tablet, is that comes with the following option
“Save and Reboot” ----System Upgrade ----Recovery mode – Reboot into the system in Recovery Mode.Can clear the data or system upgrade.
From what I understood when reading other threads, is that that will allow me to skip a custom recovery mod, correct?
Therefore, could you please explain me which are the necessary steps in order to make this tablet run smoother, while improving the overall software experience?
I honestly don't know if the tablet will handle Android 5.0 , but maybe with kitkat it will be tasty enough.
Thank you so much for your time.:good:
Best regards
Tiedefender
Dear members
I contacted Lenco support team and they send me a firmware file:
A13_86VS_M758CHD_1303086.20130329
But , when I open PhoenixSuit 1.08, it says:
Firmware version = v1.2_13011 A13_86VSH_M758CHD.20130329
Android version = 4.1.1
The A13 that I see above has anything to do with other A13 tablets?
If yes, how can I root and upgrade my tablet?
Thanks
Q&A for Intel Android Devices Root / Temp CWM Session
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Intel Android Devices Root / Temp CWM Session. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will this root method work with ASUS devices?
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
usenametaken said:
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
Click to expand...
Click to collapse
It should work I've tested it on Medfield, Clovertrail, and Baytrail devices, from the Asus fastboot.imgs I've looked at trigger 2 and 3 should work.
the apk you refer to i believe actually uses a function Asus only seems to of built into thier droidboot binary on the Asus when you start droidboot it looks at /factory for a file called .addon and then triggers it Asus uses it for automating things under droidboot I believe and several recoverys have been built to take advantage of it.
As for the exploit the exploit is the the script the binarys are nothing really special just responsible for setting up and starting the recovery session. recovery.trigger is a simple daemon to launch recovery.launcher and recovery.launcher is basically a small subset of cwm recovery its self.
Sent from my XT907 using XDA Free mobile app
Hi,
this worked on an odys intellitab 7, now i got finnaly root . BIG THX!
Btw I trird trigger 2 and 3 and both worked for me
How can i see if the bootloader is locked on my device?
Another possible device
Hello,
in Czech forum where I compiled a native-language short guide how to use your tethered CWM recovery to root Op3n Dott (I see that somebody confirmed that both T2 and T3 triggers work] one Slovak user reported that he was able to use the tool to root Prestigio MultiPad Thunder 7.0i http://www.prestigio.sk/catalogue/M...NDER_7.0i#/product-specs?article=PMT3377_WI_C. I sent him a question concerning which trigger did he use so if he replies I will send more info. Sorry for the Q&A thread, but I got kicked here because of the low post count.
Succesfully rooted Tesla L7 Tablet
Using the method described successfully rooted Tesla L7 tablet. The method used is T3 and supersu used is UPDATE-SuperSU-v2.40
Is the recovery built from source?
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
pm-cz said:
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
Click to expand...
Click to collapse
The actual recovery is built by @vampirefo but i am very interested in adding that feature in and was actually going to ask you about that.
Also have you looked at any of the older update_osip source?
Can you please tell me an easier to understand method.
Because even though i understand what you're talking about, i don't know where to put the files. I understand flashing the session and all but coukd you pleeease explain how to root. Because this the first time i'm rooting a device
Thanks
rooting without voiding warranty
Can you please tell me how to root my dwll venue 8 3830 without voiding the warranty?
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/android/software-hacking/mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Getting Windows 7/8 to Recognize Dell Venue 3740
Fajfie said:
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Click to expand...
Click to collapse
Thanks to Social Design Concepts for the great work. It is appreciated!
Fajfie, thanks for posting. That's awesome. If you used Windows, how did you get Device Manager to identify the Dell Venue 3740? I've downloaded all recommended driver files in this and the previous thread and I can't get Windows to identify the device. When I run launcher.bat I get DEVICE: UNKNOWN.
Any ideas?
Another rooted
Great work, this worked to gain root on Medion (Lenovo) Lifetab S10346 tablet.
Intel Z3735F cpu
2GB ram, 32 GB storage.
I used trigger T3 and it went through smoothly, a Great bit of work.
Works perfectly on the Asus Padfone X Mini. I referenced this thread over in the device specific forum. I used the T3 command in step 3.
Thanks!!!
Worked on my ASUS Padfone X mini (TOOS) used T3 option.
Thanks!
Thanks you. The procedure works with method 3 to GoClever Insignia 700 PRO , Android 4.4.2.
I just installed IntelAndroidDrvSetup 1.5.0 with the drivers for my pc.
hi im having the same problem as GeeKerGurL
" Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help! "
i have a Acer Iconia A1830
Problems with the update surpeuser zip
I followed your guide to rooting Acer iconia tab 8 A1-840FHD with intel chip, (Wich is great by the way thanks) and evrything goes to plan until, i get to Install Zip. I get, E:Can't mount /sdcard/ Update-superSu-v2.40(1).zip Installation aborted. I've downloaded the zip from your link by desk top (windows 7) and transferred it over. Also downloaded from the tablet and just used a file manager to move it over to sd. Same msg for each. I used the T3 option. any ideas how to get the zip to install?
Zip copy to folder on your tablet (download,...) and install from recovery install. zip.
Send from my Samsung Galaxy S2 - RR Lollipop v. 5.2.7
Verified with Acer Iconia A1-830
Firstly, big thanks to the dev, social-design-concepts for making this thing work on Intel device. Thumb up~
It works wonders with my Acer Iconia A1-830 android 4.4.2.
I used option T1 and it works without any problem.
Thanks again.
P/s: Hope this will work on the latest Intel devices like Asus Zenfone 2 ;p
Hello,
I've purchased this one: http://www.dx.com/p/x96-tv-box-andr...-2gb-ram-16gb-rom-us-plug-449347#.WPuxONryuUk
Just wondering what ROMs and recoveries work. I've searched a bunch and found some dead links and conflicting information so I'm hesitant to flash it especially where I do not have a stock image to go back to if it renders it bricked.
If anyone can help out, it would be much appreciated.
Thank you,
Scott
Note: Keeping a repository here as I find more information about this box: https://drive.google.com/open?id=0Bzj6JjnAJZjjczVIbFlHS3VUWlU
Working on it
Custom TWRP and stripped down/modded firmware is on the way.
I hope we can get a pure Android Rom working on it
Again: Working on it
Fully unbranded and hopefully with unlocked custom bootanimation (Original Google would be my prefered option over Mbox).
Give me a bit of time and you will find flashable ZIP soon
All done
Another question about the box: is-it possible to have Android TV instead of a modded android marshmallow? Because the interface would be a lot easier to use.
Android TV is a complete different story and you can't really compare the two like this.
Android TV uses the Leanback launcher if I am not mistaken.
Already tried to include it into a testrom but so far no real luck as it uses a lot more binaries that are not included in the standard system.
Will have to create some symlinks, add binaries and do a lot of testing - not to mention finding all the included apps for android TV and figuring out how to make them work.
If the interface is your only trouble check some nice launchers first, like Apex for example.
Once I have something cooked up that actually works as expected you will find it in this section somewhere
Also interesting to test that , as mine is not even root ^^
Rom
Any news about the firmware for this device?
Nope, still no updates coming from the chinamen, seems they already abandoned firmware updates and moved on to different devices.
See this thread (beta 6 I used for.mine)
https://forum.xda-developers.com/an...gic/rom-x96-2-16gb-root-supersu-twrp-t3596525
I join the thread because because of a storm my X96 looks brick. I've been looking everywhere but I do not find the guide for unbrick. I wanted to save it not to throw it but I do not know where to download the firmware how to do unbrick. I know I'm in the wrong thread but I did not want to open it a lot like this and make it confusing. Thank you all
As long as you get into the TWRP recovery on the SD card all should be fine - assuming the box is a X96.
If that fails only the burn tool or burn card maker can help with a genuine firmware to get going again.
Hi guys sorry to bump an old thread. I'm still trying to find the TWRP zip for these so I can do a complete back up and then paste on other boxes.
Have an X96 Amlogic S905X Quad Core 2G/16G Android 6.0 Wifi HD 4K TV Box.
I flashed the FULLY UNBRANDED Kodi 17, everything looked fine but the box's red light just stays on after the reboot.
Does not go into TWRP at all or nothing on screen.
It now a paperweight?
Downloaded the Stock firmware (Android 6.0.1 X96 Amlogic S905x 20161122) and am trying to start box with a bootable SD-card.
BurnCardMaker asks for an IMG file with all the relevant (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, etc) files in but i cannot find this IMG file.
Without these BurnCardMaker does not work at all or nothing happens on TV box at least.
Must also say, i use a 64gig SD card but it worked for the initial flash.
Am i wasting my time with this box now?
Thanks for help.