Database Info

How to Root Desire w/ HBoot 1.06

Have a US Cellular HTC Desire CDMA.
Android 2.2
HBoot - 1.06.0000
Radio - 2.15.00.11.16
Unrevoked method of Rooting fails.
Other thoughts?

Unfortunately, I do not have an answer. I am having the same issue. If I find anything I will pass it on.

Okay I've got temporary root at least. An app called visionary, not available on the market so google that to find a download, it is a one click solution. Temp Root option works but Permanent Root does not. It takes longer to boot and has to run every time you turn your phone on. Kinda a pain but its steps in the right direction.

So as I was searching the Cyanogen forums I got a suggestion. It ended up working great for me. I ran Z4root. I ran the app selected the permanent option and let it run for about 2 min. It will just stay "rooting". I shut the phone off and restarted it. Once the phone was loaded I ran SuperUser and it ran fine. I ran AdFree, Quickboot, and Titanium backup. the only issue is with Titanium back up and it only restored some apps before closing. Not a big deal because I only wanted a few. I think it would work if I backed up on 2.2 rather than bringing 2.1 saved app with data and try to restore on 2.2. All credit goes to dontbrickit on cyanogen forums. I used the quickboot and rebooted the phone and I still had root, so it does not seem to be temporary.

I tried z4root with no results. It says rooting, goes through the whole process then reboots. No root after. Temp root feature doesn't function either. Are you running the newly released uscell rom?

HBOOT 1.06 fail
Although I have never posted I have followed the works and efforts of the very skilled developers and pro-active user for some time now and I would like to say my hats off to you all, this is by far one of the most productive and progressive communities have seen yet, I digress. I’m having an issue with hboot 1.06 also, I was running CM6 (very happy with it I might add) but when uscc came with the OEM 2.2 I rolled back to 2.1 so that I could go forward with the provider update. This process went fine, I cleared tcash and sys cash wiped and installed OEM. Turns out uscc OEM sucks bad. I only did it for htc sense and it s NOT WORHT IT. HTC sense is cool but not worth the internal memory loss I have taken. CM6 had me at over 275mb free on fresh install, OEM 145ish….FAIL. not to mention its laggy as hell on the surface. So want to go to CM7 the issue is when did the OEM it broke my hboot, when go to recovery it takes me to some blue text I can choose but its update.zip CC, reboot and factory reset. I have used clockwork 15 ways, tried 3 htc syncs that all connect but the same thing happens,,,, when any of these apps get to the hboot it does the same thing BLUE TEXT, I have tried to port old backups as well and nothing can get past this broken hboot 1.06. any suggestions?

have a thread for this going here

rhoover said:
have a thread for this going here
Click to expand...
Click to collapse
.......had

This is how I rooted mine
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?

ethahes said:
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?
Click to expand...
Click to collapse
The reason that this worked for you was because you have previous used revoked and are now s-off. With s-off, you can reflash recovery and superuser without unrevoked being supported. Others will probably still have an issue.

ethahes said:
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?
Click to expand...
Click to collapse
Does not work on USCC HTC Desire CDMA with HBOOT 1.06 that are S-ON.
We need a way for those of us USCC HTC Desire users who have Froyo as a stock ROM with HBOOT 1.06 S-ON to get that set to S-OFF. Currently no product to do so exists and while I was pointed to the #bravoc IRC channel by the users at #unrevokedtest, there wasn't anyone home. Though I have been reading at AndroidForums that someone named Matt is currently working on one. I'm not going to hold my breath at this point...

I think unrevoked is working on it. However, it could be awhile till a new exploit is found.
Sent from my HTC Desire CDMA using XDA Premium App

I was able to gain temporary root with z4root.1.3.0.apk
BravoC DVT2 S-ON
HBOOT-1.06.0000
RADIO-2.15.00.11.16
permanent root didn't work out with this app.

Glad I found this thread. Add me to the list. Ran UnrEVOked and no go. I get a "Failed to Unlock NAND" message. Hope the UnrEVOked guys come up with something.
BRAVOC DVT2 SHIP S-ON
HBOOT-1.06.0000
MICROP-051e
TOUCH PANEL-SYNT0101
RADIO-2.15.00.11.16

Stuck with STOCK Froyo 2.2 and HBOOT 1.06 + S-ON
Aaargh!!! This is so aggravating! I'm in the exact same position, guys. Need some help... Anybody...

I am as well, I use an EVO, but a lot of my friends are picking up Desires cause of a ZERO cost promo.
All ship 1.06
all have S-ON

Anyone with the 1.06 HBOOT should try out this exploit: http://forum.xda-developers.com/showthread.php?t=1044765
It says it may work on some Froyo builds and it is the first new exploit I've seen in awhile. I say give it a shot.
WARNING: CAN CAUSE SDCARD TO BE FORMATTED SO BACK UP FIRST AND READ ALL INSTRUCTIONS!
Post your results if you have any luck!

wont fix the s-on problem according to the first post, so even if you get root access it'll be removed once you reboot :/

grafton1046 said:
wont fix the s-on problem according to the first post, so even if you get root access it'll be removed once you reboot :/
Click to expand...
Click to collapse
It is possible to have permanent root access without s-off. The goal of getting root is so a custom recovery can be installed.

ah, so what can be done with root access when you can't access the system folder to make changes? Or am I missing something about the whole process...
Sent from my HTC Desire using XDA App

Teclast a11 tablet 4.1 jelly bean

¿do you know any procedure for root access for my teclast a11 4.1 jelly bean tablet?
i would like to root it. thanks

duendeskt said:
¿do you know any procedure for root access for my teclast a11 4.1 jelly bean tablet?
i would like to root it. thanks
Click to expand...
Click to collapse
Yes, I rooted my Teclast A11 4.1.1 tablet using the files and methods in this post:
Edit: As a new user I can't seem to post links.
I'll write it out instead.
blog dot sina dot com dot cn slash s slash blog_899fd55d01017nsb.html
Note: The site is in Chinese but google translate worked for me!
The root process was easy - the hard part was finding USB-drivers that worked with the tablet. After browsing through countless Chineese forums I got the advice to install an application called Moborobo. The software itself is quite buggy but the USB-drivers seems to work well.
On a different note - my A11 has a very annoying problem. The numbers in it's MAC address are separated by periods instead of colons. Is that the case with your tablet as well?
This makes the tablet unusable for some applications (i.e. Sonos Controller).
Good luck with your rooting!
Edit 2013-01-04: The latest update fixed my problem with the MAC address. You can get it here: http pan dot baidu dot com / share / link?shareid=147758&uk=489415757&third=0

How to get screen off during hdmi out?
I need to get my tablet screen off during hdmi out. It's kinda irritating and waste of battery with screen on during hdmi out. How to get the tablet off screen during hdmi out to tv?
My tablet (Teclast A11) with stock rom jelly bean 4.1.1 v1.11, dated 20121217.
The previous link you suggested only says N101 and teclast A10. Is A11 applicable too?

Alfred271 said:
I need to get my tablet screen off during hdmi out. It's kinda irritating and waste of battery with screen on during hdmi out. How to get the tablet off screen during hdmi out to tv?
My tablet (Teclast A11) with stock rom jelly bean 4.1.1 v1.11, dated 20121217.
The previous link you suggested only says N101 and teclast A10. Is A11 applicable too?
Click to expand...
Click to collapse
Can't help you with your screen off-problem (you may wanna look in to Tasker as it can do almost everything) but I have successfully rooted my A11 with the instructions in the first link. It's the same chipset so I gave it a go and it worked nicely. No guarantees though...

Verified successfully rooted teclast A11 dual core.
n'Anders said:
Can't help you with your screen off-problem (you may wanna look in to Tasker as it can do almost everything) but I have successfully rooted my A11 with the instructions in the first link. It's the same chipset so I gave it a go and it worked nicely. No guarantees though...
Click to expand...
Click to collapse
Step 1 : Download moborobo. Install it to your laptop/pc.
Step 2 : Download TPSparkyRoot-4.1.1Root.7z use winrar.
Step 3: Check all your resources. Inside [TPSparkyRoot-4.1.1Root] folder you should have:
1: RootExplorer.apk
2. SuperSu.apk
3. TPSparkyRoot.bat
Step 4: Switch on Teclast A11 (with more than 40% of battery) plug into microsd data cable. Wait for moborobo to detect and install tablet driver. Ignore typical windows that ask you for usb device driver. Eventually moborobo will do all the job to connect your tablet to pc.
Step 5: On tablet go to --> setting --> enable usb debugging mode. Click the check box next to it. [USB debugging mode]. Also set display to continuosly ON for 30 mins, to avoid sleep.
Step 6: Launch moborobo. Under --> Home. Click refresh to get your tablet connected.
Step 7: After tablet connected by moborobo. Go to App. Install RootExplorer.apk and SuperSu.apk
Step 8: Launch TPSparkyRoot.bat on your pc. Sit back and wait for tablet to restart.
[ you will get message : Rebooting - 1/3 : Continue once your device finishes rebooting]
Step 9: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : Rebooting - 2/3 : Continue once your device finishes rebooting]
Your tablet rebooting second time.
Step 10: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : uid - 0 (root) gid - 0 (root)
If the uid - 0 then continue (hit any key/enter) if not press control+c.
Suppose you will get uid-0 for both.
Finally done. You've successfully root your device. Enjoy!!
Note: You can check your root access by download "root checker" from google play store.

moborobo has no drivers/ not compatible
Alfred271 said:
Step 1 : Download moborobo. Install it to your laptop/pc.
Step 2 : Download TPSparkyRoot-4.1.1Root.7z use winrar.
Step 3: Check all your resources. Inside [TPSparkyRoot-4.1.1Root] folder you should have:
1: RootExplorer.apk
2. SuperSu.apk
3. TPSparkyRoot.bat
Step 4: Switch on Teclast A11 (with more than 40% of battery) plug into microsd data cable. Wait for moborobo to detect and install tablet driver. Ignore typical windows that ask you for usb device driver. Eventually moborobo will do all the job to connect your tablet to pc.
Step 5: On tablet go to --> setting --> enable usb debugging mode. Click the check box next to it. [USB debugging mode]. Also set display to continuosly ON for 30 mins, to avoid sleep.
Step 6: Launch moborobo. Under --> Home. Click refresh to get your tablet connected.
Step 7: After tablet connected by moborobo. Go to App. Install RootExplorer.apk and SuperSu.apk
Step 8: Launch TPSparkyRoot.bat on your pc. Sit back and wait for tablet to restart.
[ you will get message : Rebooting - 1/3 : Continue once your device finishes rebooting]
Step 9: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : Rebooting - 2/3 : Continue once your device finishes rebooting]
Your tablet rebooting second time.
Step 10: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : uid - 0 (root) gid - 0 (root)
If the uid - 0 then continue (hit any key/enter) if not press control+c.
Suppose you will get uid-0 for both.
Finally done. You've successfully root your device. Enjoy!!
Note: You can check your root access by download "root checker" from google play store.
Click to expand...
Click to collapse
Teclast A11 is not compatible to moborobo (any Teclast is not supported regarding the moborobo compatibility list)
I have tried the whole procedure and always it stucks at installing internal moborobo drivers. So i had no success to root Teclast A11 until now.
There is no real root procedure available which works with Teclast A11.
Has anybody real success to root this device????? Please tell us all how you really done it by yourself.
Thank you very much in advance.
ghostworm

Worked for me
ghostworm said:
Teclast A11 is not compatible to moborobo (any Teclast is not supported regarding the moborobo compatibility list)
I have tried the whole procedure and always it stucks at installing internal moborobo drivers. So i had no success to root Teclast A11 until now.
There is no real root procedure available which works with Teclast A11.
Has anybody real success to root this device????? Please tell us all how you really done it by yourself.
Thank you very much in advance.
ghostworm
Click to expand...
Click to collapse
Well I don't know what to tell you - the drivers that came with Moborobo v2.0.7.501 was the only ones that worked for me. I originally had the Android SDK drivers but they didn't work for me with the Teclast A11. When I uninstalled those drivers and then installed Moborobo I could connect to the tablet.
Btw. I have Windows 7 64bit
Other than that I followed the steps outlined in the link on my first post and my tablet is now rooted.

n'Anders said:
Well I don't know what to tell you - the drivers that came with Moborobo v2.0.7.501 was the only ones that worked for me. I originally had the Android SDK drivers but they didn't work for me with the Teclast A11. When I uninstalled those drivers and then installed Moborobo I could connect to the tablet.
Btw. I have Windows 7 64bit
Other than that I followed the steps outlined in the link on my first post and my tablet is now rooted.
Click to expand...
Click to collapse
hmm i can see that Moborobo is buggy because it allows me now to connect to the teclast over wifi only but it still does not reconize the teclast as teclast a11 over usb, and after Moborobo try to connect, it wants to install drivers but it always stucks at 99% of driver installation. Never installed any driver...
i have win8 pro 64bit

Moboro
ghostworm said:
hmm i can see that Moborobo is buggy because it allows me now to connect to the teclast but it still does not reconize the teclast as teclast a11, and after Moborobo try to connect, it wants to install MoboMarket but it was always denied by the teclast itself, even when i download it manually and try to install.
BTW is it really necessery to install MoboMarket just to root the device???
Click to expand...
Click to collapse
I didn't use any of the Mobo*-applications, the only reason I installed it was the USB-driver.
I see that Alfred271 uses Moboro to install some apps on the tablet - I didn't do that. I only ran TPSparkyRoot.bat as outlined in my first link.
This is the google translated instructions i used (Note that they tested it on a different tablet than the A11 but they share chipset so I tried it).
"1 tablet is turned on
. shut down antivirus, 360 and other similar software download address: file name: TPSparkyRoot-4.1.1Root.7z
Tablet checked USB debugging, to allow the installation of third-party software
PC will be installing a pea pod-like functionality software, connect the USB installation drive
Directly run TPSparkyRoot.bat 6.
Note: In step six. Tablet restart three times, each time you restart Ends need to unlock boot into the desktop, press any key to come back to the computer terminal to the next step.
Test platform:
The original road N101 dual engine 2
Taipower A10 dual-core"

n'Anders said:
I didn't use any of the Mobo*-applications, the only reason I installed it was the USB-driver.
I see that Alfred271 uses Moboro to install some apps on the tablet - I didn't do that. I only ran TPSparkyRoot.bat as outlined in my first link.
This is the google translated instructions i used (Note that they tested it on a different tablet than the A11 but they share chipset so I tried it).
"1 tablet is turned on
. shut down antivirus, 360 and other similar software download address: file name: TPSparkyRoot-4.1.1Root.7z
Tablet checked USB debugging, to allow the installation of third-party software
PC will be installing a pea pod-like functionality software, connect the USB installation drive
Directly run TPSparkyRoot.bat 6.
Note: In step six. Tablet restart three times, each time you restart Ends need to unlock boot into the desktop, press any key to come back to the computer terminal to the next step.
Test platform:
The original road N101 dual engine 2
Taipower A10 dual-core"
Click to expand...
Click to collapse
Ok problem solved
the main problem was Windows 8 !!!!!
I tried it on Windows 7 PC and everything worked well, thank you very much...
:good:

Hi all now i have bought another Teclast A11 with Quad-Core CPU, brand new model with much more power.
The name of the product is the same but the ID is different, before it was "D5S7" and the new is "M5A7". So can i use the same rooting files for???
Thanks in advance
Ghostworm

ghostworm said:
Hi all now i have bought another Teclast A11 with Quad-Core CPU, brand new model with much more power.
The name of the product is the same but the ID is different, before it was "D5S7" and the new is "M5A7". So can i use the same rooting files for???
Thanks in advance
Ghostworm
Click to expand...
Click to collapse
That's unlikely to work as the tablets doesn't share chipset or GPU.

Identify tablet
Hi,
I've bought a generic branded tablet, its make/model is "Hi-Level HLV-T1001W".
It is just like the Teclast A11, say, both of them are the same.
If it is not removed before you see, here is a link of product details: http://www.kare.com.tr/?cmd=UrunDetay&StokNo=28543
i think there is enough english words to understand the page, most of the descriptions are in universal english
I want to root this device. But I'm not sure which rooting procedure is appropriate for this device.
My questions:
How can I compare the firmwares of these devices, and sure they are same each other?
Can/should I use the files and procedure defined in this thread for rooting?
Thanks,
A11: http://www.teclast.org/teclast-a11-dual-core-rk3066-android-4-1-jelly-bean-10-1-inch-ips-16gb.html

atakatas said:
Hi,
I've bought a generic branded tablet, its make/model is "Hi-Level HLV-T1001W".
It is just like the Teclast A11, say, both of them are the same.
If it is not removed before you see, here is a link of product details: http://www.kare.com.tr/?cmd=UrunDetay&StokNo=28543
i think there is enough english words to understand the page, most of the descriptions are in universal english
I want to root this device. But I'm not sure which rooting procedure is appropriate for this device.
My questions:
How can I compare the firmwares of these devices, and sure they are same each other?
Can/should I use the files and procedure defined in this thread for rooting?
Thanks,
A11: http://www.teclast.org/teclast-a11-dual-core-rk3066-android-4-1-jelly-bean-10-1-inch-ips-16gb.html
Click to expand...
Click to collapse
They do look very similar (apart from your tablet having bluetooth) but it's still hard to be sure it will work.
If you're thinking about rooting using the files I linked to I would recommend making sure it has a Rockchip RK3066 chipset.
I'd imagine that the Rockchip batch tool will correctly identify the chipset (and possibly the firmware) for you.
Good luck!

n'Anders said:
They do look very similar (apart from your tablet having bluetooth) but it's still hard to be sure it will work.
If you're thinking about rooting using the files I linked to I would recommend making sure it has a Rockchip RK3066 chipset.
I'd imagine that the Rockchip batch tool will correctly identify the chipset (and possibly the firmware) for you.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply.
It has a Rockchip RK3066 chipset as far as I know from the specifications.
I will give it a try after re-checking with some hardware tools.
So, what is the worst scenario if it is not suitable for my device? Brick it or something like a better case that I can recover it?

atakatas said:
Thank you for your reply.
It has a Rockchip RK3066 chipset as far as I know from the specifications.
I will give it a try after re-checking with some hardware tools.
So, what is the worst scenario if it is not suitable for my device? Brick it or something like a better case that I can recover it?
Click to expand...
Click to collapse
I have read about people that was able to restore their seemingly dead tablets through the Rockchip batch tool but I have (luckily) no experience in that department...

Thank you for your advices.
I think, "Rockchip batch tool" is the best starting point in my case. I found some tutorials on firmware update in other forums, I'll try them later. For now, I can go with it unrooted.

ROM
Hi,
Would any one recommend a good Custom ROM for my Teclast A11? I run on the stock ROM which worked fine till Sunday after which it crashed and i updated with a firmware which is not stable either.
Regards

hello guys, i downloaded the original firmware from:
http://www.teclast.com/tools/pad/putcode.html
just write down your id, it is back on the case.

How to Root and avoid bricking
For those that have an Teclast A11 Dual Core and Quad Core M5A7 I've pass my two last days to make experiments.
I've landed in a Root procedure easy to use, and I have discover how to Unbrick in case of failure of Root.
I'll hope you apreciate the guides. It's took a lot of time to write down them all.
How to Root Teclast A11 Dual Core and Quad Core with Android 4.1.1
How to Unbrick Teclast A11 Quad Core M5A7
How to Update firmware to Android 4.2.2
Sorry for my English, I'm Italian.
Have a nice day.

Intel Android Devices Root / Temp Recovery Session

Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28

Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3

Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .

The Concept / Source Code
The Concept / Source Code

Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates

Generic / Tips for Unbricking
Generic / Tips for Unbricking

Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
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!

GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
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!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?

GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.

recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.

whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app

asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.

Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?

tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app

whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app

Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!

Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?

Teclast T30 [T1Px][Custom ROM][Android 9] -> hybrid ROM 1.04 / 1.05

I have prepared hybrid ROM 1.04 / 1.05 (Android 9) -> its suitable for T1P2, T1P3, T1P4 version of Teclast T30
Its based on official global ROM 1.04 and chinesse 1.05 ROM.
In the folder with firmware 1.05, I replaced the scatter file and system.img from firmware 1.04.
The result is:
Version 1.0: firmware 1.04 with Google Play store and 60 Hz screen frequency, MUCH better touch response, containing all languages.
Version 1.1: same as version 1.0 + Magisk (ROOT) pre-installed
Version 1.2a: same as version 1.0 + TWRP 3.3.1 pre-installed
The big advantage of this procedure is the standard easy installation of the firmware via Flashtool.
Download:
look to attachments
Installation 1.0:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System
Installation1.1:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System
- Install Magisk Manager v7.5.1 or Magisk Manager v8.0.3
Installation 1.2a:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download only"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish
- - Wait aprox. 20 seconds
- Do not start tablet by normal way!!!
- To go to TWRP start the tablet by pressing and holding the Power and Vol+ buttons simultaneously, until text menu on tablet will appears
- On the tablet screen, use Vol+ to select "Recovery Mode", confirm the selection with the Vol-
- To control the TWRP connect the mouse to the tablet, because touch do not work in TWRP
- Click Cancel when prompted for a password
- Click on Wipe / Format Data / Swipe to confirm
- On question enter "yes"
- Click Back (3 times) and click to Reboot / Recovery!!!
- Install "DisableForceEncryption_Treble.zip"
- Install Magisk 21.1
- Click Reboot System
- Install Magisk Manager v8.0.3
- To easy access to TWRP instal Recovery reboot application
Note. Unfortunately, the touch does not work in TWRP, so a mouse and USB adapter must be used
If someone has a problem with Flashtool, fails to burn ROM to tablet, try install drivers " MTK_USB_All_v1.0.8.zip"
- unzip archive
- run file "MTK_USB_All_v1.0.8.exe"
- it will create desktop folder "MTK Usb Driver v1.0.8"
- run file \MTK_Driver_ ext\DriverInstaller.exe
- it will install drivers
- restart PC
- done
Edit 8. january 2021
Because XDA Admid removed my external download links I had to upload all files to attachments.
As a backup, all files are stored here also

to all T30 owners out there that suffer from touch-screen lag: rtb07 did a phenomenal job in creating this hybrid rom that fixes the issue. Installation is easy to do, just follow the above instructions.
I fixed my T1P2 EEA T30 using the 1.2a hybrid rom and could not be happier with the result. It is working like a charm now.
THX to rtb07!!!!

Welcome. Thank goodness I managed to correct that annoying touch mistake.

I would love to do installation 1.0 on my T1P2 but all the download links have been removed :/

Vandal4125 said:
I would love to do installation 1.0 on my T1P2 but all the download links have been removed :/
Click to expand...
Click to collapse
Because the XDA administrator deleted my external links to the files, I had to upload everything to the first post.
So now is all OK.

Thanks for this. I preordered this tab at launch in late 2019 and hated the touch response and just overall laggy feel, so it's been sitting in a drawer for over a year. This firmware actually makes it nice and smooth, also extremely simple to flash.

Yes, in my ROM version the touch finally works fine. It is tragic that Teclast only fixed this in the Chinese version 1.05 ROM and did not release a corrected version of the EEA / Global ROM. When I wanted to work normally with the tablet, I had to make a corrected version of Global ROM 1.04.
It is a pity that the manufacturer does not release new updates.

rbt07 said:
It is a pity that the manufacturer does not release new updates.
Click to expand...
Click to collapse
I bought 3 Chinese tablets from different company’s & not one of them have been updated by the makers, but my 2 years old Samsung S9 South Korean phone still getting updates.
Its really is poor customer service when they can easy fix the problems, thankfully there people like you around to do there job for them!

Hi!
First of all, thanks for your great work. I have ghost touch in my Teclast T30 and I've been looking for a solution for weeks. Some days ago I found this post and installed the 1.0 version, that should fix my touch-screen issue. The installation was succesful, but still having the same problem. Ghost touch in the bottom side. ¿What can I do to fix this? I have the T1P2 version.
Thanks!

Hi, I don't know if anyone else is reporting a problem with a ghost touch on our tablet. I have not encountered this problem. They all reported only a problem with low touch sensitivity, which was solved by this hybrid ROM.
Maybe you could try peeling off the protective film. But I don't guarantee it will help.

Does physical keyboard work with hybrid rom?

Yes!

This hybrid ROM saved my T30. What a fantastic work Sir rbt07! The screen response is now super fast. After installing the version 1.0 I spent over a hour scrolling up and down just trying to believe in what I was seeing. It became a much better tablet now. Btw I got stucked in the 0% format during the flashing process and had to install the MTK drivers on my laptop. I only installed the last driver "we had three folders there" and then I could complete the installation. You should invoice Teclast to pay you for your work. Thanks a lot mate!

jagoooodka said:
Does physical keyboard work with hybrid rom?
Click to expand...
Click to collapse
Yes it does work with the physical keyboard, I tested it myself

I'd like to thank you OP, this made my tablet actually able to play rhythm games to an acceptable degree. I didn't like to flash other ROMs because they all have a common issue: bluetooth connection. This ROM works flawlessly on my T1P3 by using it for 3 days.

Hybrid ROM is just a mix of two original ROMs, so it doesn't have many bugs.

Hi, do I need to unlock or do anything to my device before I can follow these instructions?

fieldmar said:
Hi, do I need to unlock or do anything to my device before I can follow these instructions?
Click to expand...
Click to collapse
It is not necessary to do nothing more, just follow instructions.

Hello @rbt07 ,
Thanks for the awesome rom
Works like a charm

[SOLVED] Thinking of upgrading my Galaxy Tab S T800 - double check help please

Hello all,
I am thinking of upgrading my T800 to android 7 or 8 and need to start somewhere.
The main reason so many apps are either v7 or 8 min recently and I still use this tablet surprisingly lol
I have read a few threads to help me but I keep seeing that old ones I need to be careful and some say ok and some say no - so I need help.
I checked this thread to start rooting my device:
[Root][Port] Cf-Autoroot T800 [Tab S 10.5 ]
CF-AUTO Root By Chainfire Ported To the Tab S 10.5 By:@BeansTown106 First off, Huge Thanks to Chainfire for coming up with AutoRoot & for his SuperSU App Warning: I cannot be held responsible...
forum.xda-developers.com
Now - with my research I need:
Odin 3.13.1 the latest
Download Cf-Autoroot T800 from the link above
load the file to AP Odin and install to tablet
Then do the same again with TWRP with the latest file I found called: twrp-3.5.0_9-0-chagallwifi.img.tar
Reboot and should be rooted with TWRP as far as I have read
Now - do these files still work and is it ok for me to use the above to start? Am I missing anything? I guess SuperUser gets install with the rooting?
I am on Android 6.0.1 currently.
Then I need to choose an Android 7 or 8 or 9 or 10 - but seems only 7 OFFICIAL I can see - would want as close to stock as possible and the most stable I guess - can anyone recommend which ROM to flash, please?
Thank you in advance
Ben

bumping an old question - I guess may be difficult to get an answer for such an old device.
if anyone can help pls reply or PM me.

you are planning to install custom rom right? most custom rom have built in root included just follow the custom rom installation and your pretty much good to go
LineageOS seems the most popular and active custom rom for your device

No you shouldnt use cf auto root as it might brick your device reportedly.
Use magisk v21 instead (again v22 is bricking devices).

ineedroot69 said:
you are planning to install custom rom right? most custom rom have built in root included just follow the custom rom installation and your pretty much good to go
LineageOS seems the most popular and active custom rom for your device
Click to expand...
Click to collapse
Thank you - will follow them instead.

jjgvv said:
No you shouldnt use cf auto root as it might brick your device reportedly.
Use magisk v21 instead (again v22 is bricking devices).
Click to expand...
Click to collapse
Wow - thank you - glad I asked and was patient lol

SUCCESS Went through set up and seems working fine first impressions.
How I did it in 2021:
I have a Samsung Tab S - SM-T800 - on android 6.0.1 not rooted
1: These are the files that I have used
Odin3_v3.14.1
lineage-14.1-20210122-UNOFFICIAL-chagallwifi.zip
addonsu-14.1-arm-signed.zip
open_gapps-arm-7.1-nano-20210224.zip
twrp-3.5.0_9-0-chagallwifi.img.tar
2: I installed the Samsung USB drivers - and checked that I could transfer files to and from the PC - in this step I added the files into my external SD Card:
lineage-14.1-20210122-UNOFFICIAL-chagallwifi
addonsu-14.1-arm-signed
open_gapps-arm-7.1-nano-20210224
3: Once they were copied over - I unplugged the tablet and powered it off.
4: I opened ODIN on my win10 machine
5: I booted the tablet into download mode - by pressing the HOME-VOL:downOWER at the same time
6: I added the twrp-3.5.0_9-0-chagallwifi.img.tar file into the AP of Odin. Go to options, and deselect "auto-reboot"
7: Pressed START in Odin and waited for the Green PASS! to show.
8: Unplugged cable from the tablet
9: This is important -
You need to power off and power on back to the recovery you just flashed - if you miss this you may have to start again from the top here.
When done press HOME-VOL:downOWER for about 5 to 8 seconds - the screen will change and as soon as it changes let go and repress HOME-VOL:upOWER at the same time - the only change is the volume to UP. This will then boot to TWRP.
10: when TWRP first comes on - just swipe right
11: On the home screen of TWRP - I decided to make a backup - so I went to back up - and backed up to my SD Card. This takes a long time
12: when this was done - I went WIPE - and selected Format Data
13: when done go back and select INSTALL - here choose:
lineage-14.1-20210122-UNOFFICIAL-chagallwifi - then add zip and choose
addonsu-14.1-arm-signed - then add zip and choose
open_gapps-arm-7.1-nano-20210224
14: Start flashing. this is quite quick except for the Gapps.
15: When done - you will be asked to format cache and davlik partitions click it and when done - REBOOT
16: Wait a while, you should see the Samsung Logo - then the blue arc of LineageOS and go through the set up. The first boot can take 4 to 6 minutes - in my case, it was about 6 minutes.
17: Optional ROOT
Go to Settings > About Tablet > tap the build number seven times to enable developer options
Then go back and go to > Developer Options > Root Access. and choose what you want - I selected Apps Only.
I hope this helps anyone looking to do the same and wanted to say THANK YOU TO ALL WHO HAS HELPED ME.
Done.

Hi, I'm thinking of doing the same (for security reasons since updates are no longer provided for Android v6).
What version of Android did you end up with?
And have you had any issues since your upgrade?
Thanks

tuvinor said:
Hi, I'm thinking of doing the same (for security reasons since updates are no longer provided for Android v6).
What version of Android did you end up with?
And have you had any issues since your upgrade?
Thanks
Click to expand...
Click to collapse
Ended with Android 7 - and works nice ever since double-check the links though as its been a while now

also check this forum and many replied
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T800
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com

_XSnPX_ said:
Ended with Android 7 - and works nice ever since double-check the links though as its been a while now
Click to expand...
Click to collapse
And do you get ongoing automatic updates for android 7 or does that need you to go through the manual upgrade process again?
(sorry, newb questions)
Thanks

tuvinor said:
And do you get ongoing automatic updates for android 7 or does that need you to go through the manual upgrade process again?
(sorry, newb questions)
Thanks
Click to expand...
Click to collapse
That is ok,
Once you are in Lineage - you will get updates as they release them - and just upgrade from the app - you will have to go to TWRP to upgrade after you download the update but it is an easy and quick process
ill try get some screen prints now for you

The last updates

_XSnPX_ said:
The last updates
Click to expand...
Click to collapse
Perfect, thank you