Related
¿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.
I have successfully flashed the flufy_tendo 6pack ROM ( Android 4.4.2 kitkat v1.5.4 AROMA ) on this device and everything is almost ok.
The only problem y have is this one : I can´t connect the mobile with the PC ( Windows 8.1 64 bit ) via USB ( only charge mode is allowed ).
I had a similar problem with a previous ROM (EMUI 2.0 ASAP from flufy_tendo) but connecting the mobile to a PC with windows XP I was able to solve the issue.
Now is impossible to connect via USB, Wifi, PdaNet+ and so on in both operating system.
I´have tried to reinstall drivers in various way without success ( also as suggested here: http://forum.xda-developers.com/android/development/guide-huawei-honor-3c-h30-u10-t2837773 ).
Do you have any idea ?
Thanks in advance.
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?
Hi,
i have a Huawei Mediapad M5 Lite (was a stock Android 8) where i installed a custom AOSP Android 10 rom from here (tried some of there):
Flashing Successfully any GSI to Mediapad M5 Lite 10 [UPDATED]
Requirements: 1. Unlocked Bootloader 2. You need ramdisk of current version. a) Install this program from this link (you need the program installed in order to download the files) https://github.com/ProfessorJTJ/HISuite-Proxy/releases/...
forum.xda-developers.com
The issue is that if i try to install this app: USB AUDIO PLAYER PRO, it seems not be not compatible with those roms. Seems that USB OTG is not working.
So i installed this app: USB OTG CHECKER, it says that USB HOST is not working.
The last rom i installed have root privileges the i created the file android.hardware.usb.host.xml in /system/etc/privilege that was missing.
But issue is not fixed. Please could you help me?
The reason i need to use USB AUDIO PLAYER PRO is the only app to have hi-res audio streaming. Can bypass Android 16 Bit 44.1 KHz limit and go up to 24 bit 192 KHz.
Thank you.
How USB / USB-OTG is implemented is hardware specific, the related drivers are NOT part of Android OS itself, they are provided by OEM.
jwoegerbauer said:
How USB / USB-OTG is implemented is hardware specific, the related drivers are NOT part of Android OS itself, they are provided by OEM.
Click to expand...
Click to collapse
so fot you the only way to have it is to restore stock rom from Huawei?
USB OTG CHECKER app you ran told you the USB-hardware build into phone doesn't support USB-OTG. So what should be the reason to re-flash phone's stock ROM?
jwoegerbauer said:
USB OTG CHECKER app you ran told you the USB-hardware build into phone doesn't support USB-OTG. So what should be the reason to re-flash phone's stock ROM?
Click to expand...
Click to collapse
Sorry but i put stock Huawei android 8 and now USB OST CHECKER app say that is compatible.
And also now i can install USB AUDIO PLAYER PRO app.
Hey, the XDA community and the geniuses out there
I have Phone: IKU A10 - android version: 8.1.0
I want to ROOT it but i don't know how, I try so many things i didn't find anything work
If someone have the same device and he made the root
I hope answer me
please post in proper section moved to q/a
you know What is adb What is fastboot right
@Polluter
Hint: Replace thread's unspecific title by IKU A10 - How to root? thus mainly owners of such a phone get addressed.
In order to root your phone's Android it's required you can access phone's bootloader what additionally requires IKU's USB driver is installed on your destop, too.
IKU USB Driver for all Models
Download IKU USB Driver for all IKU Smartphone, FeaturePhone and Tablets. It helps you to connect your IKU Mobile to the Computer.
androidxda.com