Database Info

How to Root and upgrade from ice cream sandwich to jelly bean??

Dear all,
I received an Asus Transformer Tf101 for Christmas, 16gb internal RAM,
OS 4.0.3 (ice cream). Can someone please guide me how to enable root and upgrade the os?
I tried to rooted with Sparkyroot but, kept getting " exploit not found". Please help!
Sent from my Transformer TF101 using xda app-developers app

Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.

arabic support
do custom roms support foreign languages and fonts, i use to visit arabic web sites and arabic tweets, do CM10, AOSP or Teom eos support such fonts
Pennycake said:
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
Click to expand...
Click to collapse

You should be fine with foreign languages as the custom rom is generally built on what Android uses, so if you can do it on stock than you should be fine on custom.
I use a different recovery than the above post, but if you follow his steps then you should be fine. You don't NEED a custom kernel to run JB per say, but it does give you a bit more power if you want to get into overclocking etc. Also, I try to stress, once you have custom recovery and are ready to flash whatever rom you chose, wipe everything. My first and only real panic was a bootloop from not wiping everything.

Like somebody mentioned above, make sure your device is compatible with each tool. Look at your serial number on the bottom of the tablet next to the usb port. Should see B60blahblah or B70blahblah, or maybe something higher (if it's newer).
I use a nice tool put together by whitekidney called EasyFlasher. It's an all in one package where you can root, install custom recovery, and install new firmware. Check this thread. It works very well for me, and is super easy.
whitekidney says:
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Click to expand...
Click to collapse
It's real easy to use. Put your tablet into apx mode by holding the power button and the volume up button. The screen will look like it's off but if you plug it into your Windows computer, you should hear the sound when a device is plugged it. Then it'll try to install the drivers for an apx device, or some MTP drivers, I believe. If they fail to install, download PDAnet and install it. This will correctly install your drivers. There's also another method of getting your drivers to install correctly. Here's a universal driver package that 1wayjonny put together. To clarify, only use PDAnet or the universal driver package if your drivers didn't install correctly when you plugged your transformer (which should be in apx mode) into your computer.
Now you can use EasyFlasher to install a custom recovery. I left it on the very first option, (a touch recovery, so you don't have to use your buttons to change your selection). During this process, EasyFlasher should first open up a command prompt (it might pop up behind your current programs running so you won't see it until you minimize everything except for EasyFlasher). The cmd prompt will ask you to overwrite some files on your device, just type a for "always" and let it do it's thing. It's really running NVflash which you should also get familiar with too.
After you have a custom recovery installed, flash your ROM of choice. Here's a nice JB 4.1 that I've tried out. Download that file, put it on a micro sd card, pop it in your transformer, and reboot into recovery by holding volume down and the power button. When it reboots, press volume up to enter your new custom recovery (like it should say on the screen). If you installed the same recovery that I recommended above (hopefully these are the correct steps, as I don't have my device in front of me), click on flash .zip, then click on from sd card. You should see the zip that you transferred from your computer, click on it, and it should install.
Once that's finished, reboot your transformer, let it load the new rom, either set it up or skip all the junk in the beginning. Once you're on the main home screen, remove your micro sd card and transfer the superuser zip that you can find inside the tools folder in EasyFlasher's directory (on your computer) to your sd card. Reboot into recovery, and now flash that super user zip the same way you flashed the rom.
Now you have a brand new, 4.1.2 JB rooted device!

Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app

jbusti75 said:
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I am sure it can be done, but most of the tools (like EasyFlasher) use Windoze.
Even if you are getting an MTP error, it should not matter as you will be using the APX device. Just make sure you have the APX driver and update the unknown device that appears after you boot to APX mode.

[Q] Check this out: Att One X - NO OS, SD card wiped and won't mount BUT..

Hello -
I have done weeks worth of research in my spare time before finally caving in and asking for help. I believe my situation irritatingly enough is different than typical no os corrupt sd card issues and I have not been able to find a solution here or on the www unless I am forgetting something simple. Here's why:
I am S-Off
I have super cid
I have access to bootloader
I have access to recovery which is TWRP 2.3.1 and I can access terminal command
My card WONT MOUNT (meaning no fixing permissions, no wiping external sdcard or side loading)
If I reboot system, it freezes at the initial boot screen image with the Viper logo and the red developer caution statement below it
Fastboot and ADB do not recognize my phone and I have used every one click, script, and trick on this website and others using different drivers, Android SDK and all the different drivers I can find. No Dice.
I DO HAVE AN HTC EVO 4G LTE that I htc dev unlocked, s-off, supercid etc on this very laptop (Windows 7) this week so I have a pretty good idea what what doesn't work in terms of drivers/scripts with my current laptop configuration.
I have used Ubuntu as an installed desktop and as a live cd. This is as close as I have been to having my phone recognized in adb or fastboot. I was using the SD FIX see here http://forum.xda-developers.com/showthread.php?t=1942519 (What I don't get is why that thread was closed. Makes no sense to me that since a particular version of TWRP becomes available, that it would render that fix obsolete when its obvious how many scenarios can come up in particular with these HTC One Xs and not everyone is going to have a specific version of recovery. Anyway... this brings me to Ubuntu. And this is as close as I have been to success with getting back into my sdcard so I can command prompt/flash my way outta this mess. It was the only version of the SD fix I could find which of course was for Mac, Linux or Ubuntu. In terminal when the script would initialize it comes back as "Fastboot: Permissions Denied" or something to that effect. That was last night.. or errr.. this morning and I'm determined to do this.
Has anyone heard anything about a way to create a virtual sd card using AVD in an old version of the SDK? From what I can see it looks fairly simple. What I have dug up sounds easy enough but not sure why I haven't come across it here or anywhere else or nobody else has mentioned it? However, I am not a dev and perhaps it being a couple years old, counter measures have been put in place by these phone companies... lol we'll see... Thank you so much for your time.
I have attached a snap shot of my bootloader screen. Yes, I know the screen is cracked lol

The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita

timmaaa said:
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
Click to expand...
Click to collapse
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.

bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk

bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
How did you wipe your sd card to begin with? If you wiped it in the bootloader with the factory restore option then this will currupt your sd and the only option is to connect to your pc or computer and under my computer right click the drive of your phone and format the sd card that way and this will restore your sd card to working order but you must have all the right drivers installed for your phone. Which installing HTC sync will install all the right drivers
Sent from my HTC One XL using xda app-developers app

I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP

31ken31 said:
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you mean literally plugging my phone into my pc...going into device manager, seeing if the sdcard is being picked up.. of course I have. I can freely go between recovery TWRP 2.3.1.0.0. and bootloader and I can even boot the system even tho there isn't an OS and get as far as the VIPER logo with the developers text below it in red. I have both windows and Ubuntu and I have tried everything. I have gone into what files and folders I do have on the phone and using terminal in recovery I have found all the proc contents in tact.. all the dev contents in tact and sub folders... all the usb folders and contents I believe are still there too. Including fastboot. HOWEVER, after days of trying every adb usb driver combination imaginable... including editing .inf files, and taking signature verification off win 7.. I still can't get my phone to be picked up when i plug it in. Every once in a while I will get the bell sound when I plug it in to a usb port but when I look in device manager nothing...but when I plug my evo 4g lte in its whamo... ding ding and no issues. As far as this phone goes...I see all the files and folders there but even even ran htc drivers in compatability mode with XP... nothing.
I am learning how to create virtual sdcard images and how I can potentially be able to attach it to a devices sdcard giving one the ability to transfer or delete files which could help some folks get back into their devices...Also, here is a really cool idea although still in its infancy and how you can mount an sdcard as an mtp device using a fuse filesystem based on libusb. https://github.com/hanwen/go-mtpfs So at this point there are options out there but only pretty heavy manipulation of data and extentions and stuff over my head lol..

dtonshel said:
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
Click to expand...
Click to collapse
Hey thanks. Yup. This is exactly what I need to do. It's just that last time I tried to run the sdfix script in terminal using ubuntu i ran into a permissions issue. fastboot-permission denied or something to that nature. Do you know what that means? Thanks tho I will give this a shot.

TWRP 2.7 Issues

Hi,
I am unable to mount the SD card in TWRP 2.7.0 on my Evita.
Anyone else is having this issue?

+1
doesn't work for me too
only way is to use usb-otg or adb push to push a rom, or be back to an older version .
You can use Recovery switcher

Could someone tell me or post a link to twrp 2.7.0 and how do i install. Thanks

openrecovery-twrp-2.7.0.0-evita.img
Size: 8.9 MB
MD5: 0eb7f3d14d75a019b19757836a1ec805
but better to use recovery switcher (flash in recovery like a rom and choose the recovery you want to install)...

Why are you claiming it's better to use recovery switcher? What's wrong with flashing it the normal way with fastboot?
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-evita.img
Simple. This is the standard method for flashing a recovery to an Android device, it always has been and always will be.
Sent from my Evita

With the switcher you don't need a Pc to switch the recovery and no drivers problems.
Of course for me (and you ) fastboot commands are not a problem...
but for the one who did all the wipes before transferring the zip of the rom and is on TWRP 2.7 and without an usb otg cable ...

Well you'd have to be stupid to perform a wipe before having the ROM zip on your phone, lol. I wasn't trying to diss the recovery switcher, it's great work by Flashalot. I just firmly believe that anyone who is modifying their Android device should be comfortable with using adb & fastboot.
Sent from my Evita

Should be, but in reality

I always had problems with 2.7, I've stuck with 2.6.3 for a while.

sathish804 said:
Hi,
I am unable to mount the SD card in TWRP 2.7.0 on my Evita.
Anyone else is having this issue?
Click to expand...
Click to collapse
bzhmobile said:
+1
doesn't work for me too
only way is to use usb-otg or adb push to push a rom, or be back to an older version .
You can use Recovery switcher
Click to expand...
Click to collapse
Are you guys trying to mount in windows or linux or mac? Also you are hitting "mount > mount Usb storage" correct?
Sent from my SCH-i705 using Tapatalk

hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...

bzhmobile said:
hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...
Click to expand...
Click to collapse
OK...I'll play with it tonight if I can, I only confirmed on Linux.
Sent from my One X using Tapatalk

bzhmobile said:
hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...
Click to expand...
Click to collapse
Same problem on XP x64 and x86. It seems to also affect the new version of CWM and Philz touch. All of them work fine on linux for me though. Good thing I hate windows.

Yep. Confirmed. Pretty glitchy too. I have windows 8 installed on my computer. I noticed when I entered recovery (2.7.0.0) the tray icons in the lower right of my computer screen started "jumping" left and right when I chose to mount the internal storage. The tray icons continued this until I put the phone into bootloader. I flashed 2.6.3.0 and everything was back to normal and working fine. Looks like there are a few kinks to work out.

When trying to wipe USB-OTG, it wouldn't work. So I'm pretty sure it's a general implementation problem
Sent from my HTC One XL using Tapatalk

pandasa123 said:
When trying to wipe USB-OTG, it wouldn't work. So I'm pretty sure it's a general implementation problem
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
You actually had a OTG drive or device attached ? If so that may be by design but i can test and talk it over with the twrp folks if needed
Sent from my One X using Tapatalk

jrior001 said:
You actually had a OTG drive or device attached ? If so that may be by design but i can test and talk it over with the twrp folks if needed
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Yup. I just bought it to see how it is. Total waste of money in retrospect because I can't really see myself using it.
Sent from my HTC One XL using Tapatalk

OK folks, i can confirm i had issues in both win 7 and win 8.1, but removing the device via device manager, and letting it re-install it self on the next plug in i was able to mount with out any more issues.
On the topic of OTG, I was able to Mount OTG and then both flash a ROM from it and wipe it once it was mounted. The big thing with OTG is that you have to manually mount it if you want to utilize it.
Edit: fwiw I was using a 2GB thumb drive formated to NTFS

@jrior001 : is the recovery kernel compiled by you? Could you tell me if it is possible to use the sources of the 3.4.10 kernel that HTC has released, enable SElinux and produce a custom image of the recovery?

AlxMAX said:
@jrior001 : is the recovery kernel compiled by you? Could you tell me if it is possible to use the sources of the 3.4.10 kernel that HTC has released, enable SElinux and produce a custom image of the recovery?
Click to expand...
Click to collapse
For the official 2.7 all device work was done mainly by mdmower ( CM guy for the VZW HTC devices). The kernel is just the base cm11 kernel and the trees are hosted on his github. I only helped with a few things and testing for this.
What you are talking about is twrp based off the last HTC source release...which is exactly what I did on the 4.4 comparable version I posted previously. Stock HTC kernel source modified for selinux built with TWRP 2.6 sources at that time. My thread has the links for kernel source and trees if you want to play with it
Sent from my One X using Tapatalk

[Q] Droid MAXX TWRP Recovery and using USB OTG

I'm currently using TWRP 2.6.x on my XT1080MDEV and have a question specific to the device.
First, my use case: I like backup images... They are wonderful... BUT, they occupy space. To help alleviate this I've started offloading them to a USB OTG device via manually copying them in a file manager after mounting the device in StickMount. I would like to be able to restore from this device directly in recovery, just in case the world burns down.
My issue: attempting to mount in TWRP never finds anything and thus no restore from the USB OTG device works for me. As I understand it, TWRP recovery does support USB OTG.
How do I accomplish mounting a USB OTG device in TWRP on the Droid MAXX?
Thanks in advance for any help anyone can provide.... Its greatly appreciated!!
Sent from my XT1080DEV using Tapatalk

CarnivoreMatt said:
I'm currently using TWRP 2.6.x on my XT1080MDEV and have a question specific to the device.
First, my use case: I like backup images... They are wonderful... BUT, they occupy space. To help alleviate this I've started offloading them to a USB OTG device via manually copying them in a file manager after mounting the device in StickMount. I would like to be able to restore from this device directly in recovery, just in case the world burns down.
My issue: attempting to mount in TWRP never finds anything and thus no restore from the USB OTG device works for me. As I understand it, TWRP recovery does support USB OTG.
How do I accomplish mounting a USB OTG device in TWRP on the Droid MAXX?
Thanks in advance for any help anyone can provide.... Its greatly appreciated!!
Sent from my XT1080DEV using Tapatalk
Click to expand...
Click to collapse
The latest versions of twrp and cwm support USB otg. I would check out dhacker29's versions
Sent from my XT1080 using Tapatalk

BladeRunner said:
The latest versions of twrp and cwm support USB otg. I would check out dhacker29's versions
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
The TWRP I originally installed was from Hashcode here http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850 and is version 2.6.3.1 which I believe supports USB OTG (But, obviously, its not working for me )
I looked around for dhacker29's version and all I can find is his thread in which someone asked about compatibility with Droid MAXX here: http://forum.xda-developers.com/showpost.php?p=49475029&postcount=110 in which a reply has not yet been submitted. The thread includes a broken link to a TWRP img however I think they are housed here http://androidhosting.org/Devs/Dhacker29/MotoX/ even so I cannot validate compatibility and would not know which one to pick... I'm not bold enough to potentially brick either.
Any other ideas or more information anyone can provide?
Is anyone else trying to do images from an off device storage source? I would think this might be a common thing to do, given internal storage and get botched too.
Thanks to anyone who can help in advance!

CarnivoreMatt said:
The TWRP I originally installed was from Hashcode here http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850 and is version 2.6.3.1 which I believe supports USB OTG (But, obviously, its not working for me )
I looked around for dhacker29's version and all I can find is his thread in which someone asked about compatibility with Droid MAXX here: http://forum.xda-developers.com/showpost.php?p=49475029&postcount=110 in which a reply has not yet been submitted. The thread includes a broken link to a TWRP img however I think they are housed here http://androidhosting.org/Devs/Dhacker29/MotoX/ even so I cannot validate compatibility and would not know which one to pick... I'm not bold enough to potentially brick either.
Any other ideas or more information anyone can provide?
Is anyone else trying to do images from an off device storage source? I would think this might be a common thing to do, given internal storage and get botched too.
Thanks to anyone who can help in advance!
Click to expand...
Click to collapse
http://androidhosting.org/Devs/Dhacker29/ look in the MotoX folder
---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------
CarnivoreMatt said:
The TWRP I originally installed was from Hashcode here http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850 and is version 2.6.3.1 which I believe supports USB OTG (But, obviously, its not working for me )
I looked around for dhacker29's version and all I can find is his thread in which someone asked about compatibility with Droid MAXX here: http://forum.xda-developers.com/showpost.php?p=49475029&postcount=110 in which a reply has not yet been submitted. The thread includes a broken link to a TWRP img however I think they are housed here http://androidhosting.org/Devs/Dhacker29/MotoX/ even so I cannot validate compatibility and would not know which one to pick... I'm not bold enough to potentially brick either.
Any other ideas or more information anyone can provide?
Is anyone else trying to do images from an off device storage source? I would think this might be a common thing to do, given internal storage and get botched too.
Thanks to anyone who can help in advance!
Click to expand...
Click to collapse
the moto X ones work for our phones. I like CWM, personally

CarnivoreMatt said:
The TWRP I originally installed was from Hashcode here http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850 and is version 2.6.3.1 which I believe supports USB OTG (But, obviously, its not working for me )
I looked around for dhacker29's version and all I can find is his thread in which someone asked about compatibility with Droid MAXX here: http://forum.xda-developers.com/showpost.php?p=49475029&postcount=110 in which a reply has not yet been submitted. The thread includes a broken link to a TWRP img however I think they are housed here http://androidhosting.org/Devs/Dhacker29/MotoX/ even so I cannot validate compatibility and would not know which one to pick... I'm not bold enough to potentially brick either.
Any other ideas or more information anyone can provide?
Is anyone else trying to do images from an off device storage source? I would think this might be a common thing to do, given internal storage and get botched too.
Thanks to anyone who can help in advance!
Click to expand...
Click to collapse
I don't know if this will help but this is what I do. After unlocking I set up a bone stock ROM and then to nandroid back up. While its quite large, I keep this backup on my SD in its original location. As I move forward with customization, tweaks, ROMs, ect I'll do a nand of that and move the file from the phone to PC. If anything should happen like bootloop or otherwise borking something I have the stock nand immediately available to restore and bail me out. If I want I can then hook up to PC and load the backup I want and restore through TWRP.
Sent from my Dev Ed. Ultra

BladeRunner said:
http://androidhosting.org/Devs/Dhacker29/ look in the MotoX folder
---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------
the moto X ones work for our phones. I like CWM, personally
Click to expand...
Click to collapse
OK... I installed the 2.7 image to no avail.
Do I need to manually mount the drive in a terminal or something ?
I ass/u/me/d it would mount on boot of recovery as external memory or something however perhaps that's not the case and I'm simply missing steps?
Sent from my XT1080DEV using Tapatalk

CarnivoreMatt said:
OK... I installed the 2.7 image to no avail.
Do I need to manually mount the drive in a terminal or something ?
I ass/u/me/d it would mount on boot of recovery as external memory or something however perhaps that's not the case and I'm simply missing steps?
Sent from my XT1080DEV using Tapatalk
Click to expand...
Click to collapse
I'm not sure about TWRP. I'm using CWM 6.4.0.7 and it mounts automatically

BladeRunner said:
I'm not sure about TWRP. I'm using CWM 6.4.0.7 and it mounts automatically
Click to expand...
Click to collapse
Yes, I've now tested CWM 6.4.0.7 and it does automatically mount the drive. I'll use this as a workaround for now and thank you.
Still looking to get TWRP to mount external storage - anyone?

CarnivoreMatt said:
Yes, I've now tested CWM 6.4.0.7 and it does automatically mount the drive. I'll use this as a workaround for now and thank you.
Still looking to get TWRP to mount external storage - anyone?
Click to expand...
Click to collapse
I can't get TWRP to work either

Turbo-X Tablet Hive VI---Google Play Services NEEDED!

Hello guys, I'm looking for Google Play Services for this tablet it's with Intel and Android 4.4.4. Here are some screenshots of all info. I just can't find working Services. I don't need root, but just Services. It was bought without Google Play Store and Services. I hope you can help me. Thanks.

yanis15 said:
Hello guys, I'm looking for Google Play Services for this tablet it's with Intel and Android 4.4.4. Here are some screenshots of all info. I just can't find working Services. I don't need root, but just Services. It was bought without Google Play Store and Services. I hope you can help me. Thanks.
Click to expand...
Click to collapse
How about flashing gapps?

AzrulHisyam said:
How about flashing gapps?
Click to expand...
Click to collapse
Yes i thought about this, but how?? I think i need custom recovery for this, but can't install one. If there is other way of installing I will be happy. Thanks.

I don't know any other way to install gapp except using recovery.
Install recovery and find your phone gapp and flash using recovery

Hello guys, just wanted to let you know that after many hours of hard work I finally managed to get Google Play Services and root working. If anyone ever needs help with this particular model or any x86 based Android tablet/phone with unknown brand you can send me private message or answer in this thread. The problem with this type of devices is that no one makes custom recovery for them that's why I had to load a temporary one. Here is a link. By following the guide there you will get in recovery pretty much 99% of time. From there it's easy just flash SuperSU package and GApps. The best and only working x86 (Intel Processors) GApps with this version of CWM recovery are Franken GApps. You flash them and you are done. You now have working, licensed and usable tablet/phone! Screenshots below! :highfive:

need help plz...
hello my friend, i just bought turbo x hive vi and i would like to help me.. i cant root it alone... from sTART i cant understunt what is the wright trigger... :/

kokkipe said:
hello my friend, i just bought turbo x hive vi and i would like to help me.. i cant root it alone... from sTART i cant understunt what is the wright trigger... :/
Click to expand...
Click to collapse
Hey, I am sorry for the late response. I was away from XDA for a while.
1. To root I can't remember exactly, but there are a few ways I think. First, you can use Framaroot to root it or (recommended) you can directly push SuperSU package from the link I have given.
2. You download this GAPPS package. The download link is in the bottom of the post. You can also download a SuperSU package (ZIP) from here.
3. I see you have followed the instructions to some point. Here let me explain: First you connect your tablet with USB cable to the computer. Second you unzip the downloaded file and run the batch file. You then type "ACCEPT". Then you type "5" to run CWM recovery. Then you type "T4" to chose the forth option to load the recovery. This is basically a program that loads a recovery to your tablet without installing it. Your tablet should now reboot into CWM recovery. Be careful to not disconnect the tablet while you are performing operations since there is almost no way to recover from brick!
4. I guess you are at least a little familiar on how to work with recovery. In case you don't know: First - you very carefully navigate with the volume buttons up and down. You then go to install zip>from sd card>UPDATE-SuperSU-v2.65-20151226141550.zip. You then wait a second for the file to be flashed. You now have root. Second - you again navigate with volume buttons and go to install zip>from sd card>FrankenGApps-x86-20140826.zip. You again wait for a second. Now you will have successfully flashed GAPPS. You then very carefully navigate to reboot command and press the power button.
5. Tips:
- be very careful to not disconnect the tablet while flashing;
- backup any important information;
- ask me before you do anything which I have not described so you can be safe from bricking;
*In case the recovery says something like "Not enough space to install zip" or something similar, please, write in this thread so I can help you.
Good luck!

yanis15 said:
Hey, I am sorry for the late response. I was away from XDA for a while.
1. To root I can't remember exactly, but there are a few ways I think. First, you can use Framaroot to root it or (recommended) you can directly push SuperSU package from the link I have given.
2. You download this GAPPS package. The download link is in the bottom of the post. You can also download a SuperSU package (ZIP) from here.
3. I see you have followed the instructions to some point. Here let me explain: First you connect your tablet with USB cable to the computer. Second you unzip the downloaded file and run the batch file. You then type "ACCEPT". Then you type "5" to run CWM recovery. Then you type "T4" to chose the forth option to load the recovery. This is basically a program that loads a recovery to your tablet without installing it. Your tablet should now reboot into CWM recovery. Be careful to not disconnect the tablet while you are performing operations since there is almost no way to recover from brick!
4. I guess you are at least a little familiar on how to work with recovery. In case you don't know: First - you very carefully navigate with the volume buttons up and down. You then go to install zip>from sd card>UPDATE-SuperSU-v2.65-20151226141550.zip. You then wait a second for the file to be flashed. You now have root. Second - you again navigate with volume buttons and go to install zip>from sd card>FrankenGApps-x86-20140826.zip. You again wait for a second. Now you will have successfully flashed GAPPS. You then very carefully navigate to reboot command and press the power button.
5. Tips:
- be very careful to not disconnect the tablet while flashing;
- backup any important information;
- ask me before you do anything which I have not described so you can be safe from bricking;
*In case the recovery says something like "Not enough space to install zip" or something similar, please, write in this thread so I can help you.
Good luck!
Click to expand...
Click to collapse
Hello there,
Sorry for the off topic.
I also have the same tablet and I managed to do all the things listed above.
I was trying to update the Android on this thing by flashing a ROM of a very similar tablet (hardware-wise) and I semi bricked it but I managed to recover through the ECU shell(!). I have every partition in img using dd.
The thing is. Do you have any resources about a new ROM? I found the anzhen4_mrd7 source files on GitHub and I'm trying to build a CM build. Downloaded the source code etc.
If you want to collaborate send me a PM

ChrisAr said:
Hello there,
Sorry for the off topic.
I also have the same tablet and I managed to do all the things listed above.
I was trying to update the Android on this thing by flashing a ROM of a very similar tablet (hardware-wise) and I semi bricked it but I managed to recover through the ECU shell(!). I have every partition in img using dd.
The thing is. Do you have any resources about a new ROM? I found the anzhen4_mrd7 source files on GitHub and I'm trying to build a CM build. Downloaded the source code etc.
If you want to collaborate send me a PM
Click to expand...
Click to collapse
Hello,
unfortunately I am not that good with Android. I don't know how to build ROMs etc., but I may learn one day. Sorry, but I can't help you.