This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!
asteck said:
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Finally no need for help, made it with KingoRoot.
asteck said:
Hi,
Finally no need for help, made it with KingoRoot.
Click to expand...
Click to collapse
Hey there
I am trying to root my chuwi vi8 dual boot too
Could use some help
I tried KingoRoot but it does not work
Please help me
arkh01droid said:
This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you
Click to expand...
Click to collapse
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance
[email protected] said:
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance
Click to expand...
Click to collapse
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try iROOT (former VRoot)
LS.xD said:
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try
Click to expand...
Click to collapse
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition
[email protected] said:
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition
Click to expand...
Click to collapse
Make sure that both partitions are "primary" 1. Partition "fat32" 2. Partition ext4 (MUST BE PRIMARY NOT LOGICAL!!!)
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL ?
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL ?
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]
resize patition
Hi is it possible resize android partition and use more space on windows partition? is it possible installing only windows or only android?
thanks
Possible...
Can anyone please provide me a copy of the recovery.img file for the Android partition?
god damn it
DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
frieeeeeend please tell me the tool to do that, please please !!!!!!
gomexpeed said:
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
frieeeeeend please tell me the tool to do that, please please !!!!!!
Click to expand...
Click to collapse
Hi,
There is several tool for this, personaly I'm using this one:
Paragon ExtFS for Windows
It is free for personal usage.
I wan to buy this tablet and install xposed and xmultiwindow on it... does it work? is it easy to factory reset the android rom if something goes wrong?
DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
Hi, looking at the above and had a question. That seems like a longer process than on "normal" devices, ie the Terminal Emulator steps. What is the purpose of those steps? Does this mean I will have to repeat this any time I upgrade Xposed? I am curious as to why it differs from a normal install on a rooted device.
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
what did you install in windows to mount and browse android partition. Thanks
bindassever said:
what did you install in windows to mount and browse android partition. Thanks
Click to expand...
Click to collapse
Try this... http://www.paragon-software.com/home/extfs-windows/
Sent using D-Vi8™
hi
I am moderator of a Chinese tablet french site http://tablette-chinoise.net/chuwi-serie-vi-f240
If you have problems with this tablet and want to help no worries
I perceives that there is still a new bios and also another version of android in Vi8 Dual OS since 201504
Let me explain how I came to realize
s / n q32g22150304xxx
bios D86JUBNR01
you can not install on GooglePlay, or manually
Foursquare Google+ and many other applications
s / n q32g22150401xxx
bios D86JHBNR01
Foursquare Google+ OK !
here installation possible also the splash screen before botanimation android was different
but the person who has met with problems with the windows has to reinstall Android repartitioning
My question is the following
Which link the new bios D86JHBNR01 and new ANDROID !!!
Who has the upper android version 20150123
Check your build.prop please
keep me informed
Related
Here I am again...
This time I have written a shell script (linux only) and made a live-cd (for all windows/linux users) to automatically root the stock firmware on the TF101. Every stock firmware.
Today in Europe Asus rolled out the 3.2 upgrade. If you are on stock and you have alredy upgraded then download attached tar file and do as follows:
NOTE: Unfortunately, this script won't work with the latest revision of TF101 (3G version, B80 and some B70)
NOTE2: As someone pointed out (thank you Pieter) you need to be root on your linux box in order to make it work.
Code:
tar -xvf universal.tar
cd universal
./universal.sh
In Ubuntu the last command would be:
Code:
sudo ./universal.sh
Follow the instructions and you're done.
If you have a stock US/DE/TW/JP/TB firmware you can do the same.
If you are running an older version of Honeycomb the process is the same.
When ASUS will pull out another upgrade... same commands as above.
So this probably is the closest thing to one-click-root for the Transformer.
This won't install custom rom/CWM/strange other things (V2 version added the support for CWM); it's only root.
I've tested this morning after the 3.2 upgrade and it worked like a charm.
However this is in testing stage so, as always, if you brick/ruin/burn/crash something don't blame on me.
This package includes the Bootunpack tool, courtesy of Rayman84
LIVE CD INSTRUCTIONS
It's based on slitaz (http://www.slitaz.org/).
Burn the image into a cd or if you want it on a thumb usb drive follow this (http://doc.slitaz.org/en:guides:liveusb).
Put the cd/usb in your pc and reboot.
Follow the indication on screen (for setting locale and keymap).
When the desktop shows up, double click on "Universal Root for ASUS TF101".
Again follow the indication and you'll be ok.
For a guide on how to boot from cd/usb try this: http://www.passwordunlocker.com/knowledge/change-bios-settings.html
or search with google.
The option to install a stock boot/recovery (added on V3) is working even if not fully tested.
The program has correctly rebuilt a stock recovery on my WW version.
From version V4 root checker correctly says that the rom is not rooted after you do an unroot.
If you like the work i did take a look at that funny button under my name with the "donate to me" caption
Seriously, I appreciate even only a "Thanks".
FAQ
[Q] I'm running on Windows, how can I burn the live-cd?
[A] Try with cdburnerxp (it's the easiest way).
You can download one installer frome here:
http://cdburnerxp.se/en/download
or the portable package if you don't want to install other software:
http://download.cdburnerxp.se/portable/CDBurnerXP-4.3.8.2568.zip
Start the program (for the portable version the file is cdbxpp.exe) and click on "Burn iso image". Then select the .iso file you have downloaded and click "burn disk". All Done.
[Q] How can I reboot in APX/recovery mode?
[A] Do as follows:
VOL UP + POWER BUTTON for ~5sec = boot in APX mode. The screen will stay black as if it is turned off. This mode is used only when you use nvflash to flash boot/recovery/data partition (this is the first step in my script).
VOL DOWN + POWER BUTTON ~5sec = will appear a screen where it says to press vol down again to wipe all data (obviously you don't want to do it now), or press up to enter RCK (recovery mode). If you installed CWM you will see the main menu navigable with vol up / vol down / power button.
If you have the stock recovery you will see a green android with a esclamation mark on a yellow triangle.
[Q] Help! I can't reboot in recovery mode!
[A] I think the main problem here is that it is a bit tricky to get into CWM recovery, once you see the small text come up don't try to read anything, just hit volume up.
Hold volume down plus power until the text in upper left shows,if you let go too early it just boots up and you never see the text. If you wait too long you don't get the option to boot into recovery. Hope that helps..
Thx to ckuke4 for this answer http://forum.xda-developers.com/showpost.php?p=16306342&postcount=60
[Q] The live-cd gave me this error: "connection failed NvError 0x8" what is it?
[A] This means that either you are not in APX mode (read above), or that you have one of the latest revision of the tf101 (B7O) which have an unknown (for now) sbk.
For what i know, there's no knew method for rooting your device.
Maybe someone will find a way, but for now you have to be patient.
[Q] I'm running your scripts from my linux box, but it keep me saying "Permission Denied". Why?
[A] You need the root privileges on your local machine.
If you are running Ubuntu:
Code:
sudo ./universal.sh
[I](it will asks for your password)[/I]
If you are running another linux distro:
Code:
su
[I](it will asks for your password)[/I]
./universal.sh
[Q] I have rooted my tablet with this method, but I can't find the superuser app and Titanium Backup says that I am not rooted.
[A] The root script will asks you to reboot your tablet, make sure that usb debugging is turned on and then press any key.
You have to wait until you see a little bee on the bottom right of your tablet's screen, near the clock. Then press any key.
[Q] I've installed CWM but every time i try to do a backup, it says it can't find sdcard. But my microsd card work fine with root explorer!
[A] Don't get me wrong but, are you sure?
In root explorer you see a sdcard folder but it's not your microsd, it's the internal memory (it's weird, i know). In root explorer the microsd card is mounted under the "/removable/microsd" folder. You should also see a little sd card icon in the bottom right, near the clock.
Also you need to make sure the card is formatted correctly. Try reformat it with this: https://www.sdcard.org/consumers/formatter_3/
Thanks to skeeterpro for the link (http://forum.xda-developers.com/showpost.php?p=16385872&postcount=6)
[Q] The live cd stops at the command prompt, I can't see the desktop.
[A]The live cd doesn't include every driver for every video card, mouse, keyboard, etc.. (keep in mind that the original slitaz livecd is only 30MB).
You can do all the process in the text console, it's not much more difficult.
If it asks for a login insert "tux" (without quotes).
At the command line enter the following:
Code:
cd
cd universal
./universal.sh
Then the magic will start. The unroot script is called ./unroot.sh
CHANGELOG:
V4:
- Corrected some text
- Added a link on the Desktop to this thread
- Added stock ramdisk for all SKU (though JP, CN and DE are not the latest versions) (thanks to kovla for the latest TB recovery)
- Added a script on the Desktop to increase the font size on the fly for those who are using a very high dpi monitor/tv.
- Changed compression algoritm. Now the iso is ~10MB smaller.
- Maybe I have found the way to make everyone read the faq...
V3:
- [BETA] added a second script to come back to stock.
V2:
- added the option to install CWM (thanks Roach!)
- more error check
V1:
First version
=====> DOWNLOAD LIVE-CD V4 - (Mirror)<=====
DOWNLOAD LIVE-CD V3 (previous version)
DOWNLOAD LIVE-CD V2
As always, keep your eyes open and
Have Fun!
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
awesome -one root to rule them all!
ondoy1943 said:
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
Click to expand...
Click to collapse
In linux there's no need for drivers to work with tf101.
Windows seems to be problematic with driver (for someone seems to be way too difficult install the right ones).
As i stated above, adding this to a live linux cd will be the final one-click-root (put a live cd/usb-memory on your computer, reboot, follow the easy instructions and you're rooted).
Sincerely I don't know how to modify a livecd to add these scripts and programs.
If anyone wants to try, he is welcome.
Anyway I don't plan to do a windows port of this.
Disappointed! No windows support!
Will probably be trying this method from my PCLOS partition, if I can hold off the OTA update which has just begun pestering me.
Got to find out whether the modded adhoc wpa_supplicant works with 3.2 first, thanks for the effort HF
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
belrik said:
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
Click to expand...
Click to collapse
I was thinking on it, but perhaps it's better no.
Installing cwm means no more ota, since the update relies on the stock recovery.
This script was meant to leave all as stock as possible.
For all the windows folks:
I have added to the first post a live-cd with all the necessary tools.
Just run it and you'll be fine. (anyway, you are always in time to switch to linux)
Hallo and thanks!!!
what about mac's Users?
Can you explain a bit about what it does? So we can all learn.
Thank you,
Hi !
Will it work under wmware or virtual pc ?
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
RayYung said:
Can you explain a bit about what it does? So we can all learn.
Thank you,
Click to expand...
Click to collapse
So you wanna learn? Good!
First i learned how to root the stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1125714 .
Essentially the steps are:
1 - download a modified boot image into the tablet
2 - install the su and superuser packages.
My scripts do these 2 steps. I wrote a small howto that explains how to modify a boot image (http://forum.xda-developers.com/showthread.php?t=1193737)
Caramel said:
Hi !
Will it work under wmware or virtual pc ?
Click to expand...
Click to collapse
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
I really would like to have an answer to these questions...
The Mac should have a layer of compatibility with linux (can't tell you more), but i really don't know the mac world.
*Maybe* the live cd will work under virtual machine; there should be some options to enable the usb feature. In Virtual Box there's an option to enable the usb controller and an option to filter what device will be accessible to the guest os; don't know vmware and virtual pc.
I don't know if an Intel based Macintosh is able to boot from a x86 live-cd, you could try.
I'm sorry i can't help you much more.
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
Oops- no- there is no Nvflash for Mac. Sorry.
Created a live usb, booted via windows, and voila i am looking at a linux desktop, which i have not seen for a long time. Started going to its paces to root my tf, but did not push thru to the end, in as much as my tf is already rooted beforehand. But i can sense that barring any unforeseen miscues by the |op|, this almost one-click rooting procedure should produce its desired result. Highly recommended; good job |op|.
Looks like this calls for an "unrooting" routine to complement the rooting process. How about it?
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
brando56894 said:
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
Click to expand...
Click to collapse
I have already tried this, but seems it doesn't work.
if i write "adb reboot recovery" or "adb reboot bootloader" my tablet reboot in normal mode.
It's more reliable do it manually.
how can install ClockworkMod recovery
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
zulu99 said:
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
Click to expand...
Click to collapse
For now if you are running on windows, you can use one of these methods:
http://forum.xda-developers.com/showthread.php?t=1125714
http://forum.xda-developers.com/showthread.php?t=1185104
you are already rooted, so just need the cwm.
Since i had many requests on adding cwm, i am going to update the scripts and live-cd for adding this feature.
I'll keep you updated.
I decided to create a clean tutorial (as the method started with several bugs and issues) for those who want to root their HTC explorer.
will be editing it as new improvements appear.
btw, this will NOT change anything in your phone, it just make root access possible, if you want overclock and ext-2/3/4 partitions posible look here once you finish rooting with this tutorial.
1. Install HTC Sync on your PC
you can download it from: www.htc.com/www/help/htc-explorer/#download
(needed so computer recognises commands)
2. Unlock your phone's bootloader
- Following the steps in www.htcdev.com/bootloader
Note: HTC Explorer isn´t listed as a working device yet but it has been tested and works perfectly. Choose "all other supported models" when selecting device.
3. Add a recovery
That will allow you to install .zip ROMs. You can access to it in the menu android phones have when booting the phone after removing-inserting the battery and pressing "volume down" and "power" buttons simultaneously. (Other phones have different button combinations).
- Download View attachment 913094
- extract it in any window on your PC (ie: C:\HTC)
- run the recovery.bat with phone in fastboot mode (first option in the "3 android menu" ) and connected with usb.
Note: I edited the recovery.bat and removed any unnecessary commands so no errors occur
Done! You got the recovery installed if no errors, you can now install any compatible .zip ROM or app.
4. ROOT the device
- Place this View attachment Superuser.zip file somewhere in the microSD first.
- Go into Recovery mode ("volume down" + "power")
- install Superuser.zip with the option "install .zip from sd" from the recovery menu.
Note: after rooting dont restore to factory setting if you don´t want to end up in a bootloop, if this or similar happens you have to install a custom rom to fix it.
Click to expand...
Click to collapse
ROOTED !!
once rooted my advice is to install "link2sd". Excellent application after making a fat32 partition of your SD with programs like MiniTool partition wizard
It moves all applications directly to the SD when configuring it in automatic mode. (the entire application, not like the inbuilt phone option). See post # 9 for instructions.
enjoy
tnx,
I'll try asap this guide.
bye!
Thank you very much jaggy jags.
I did a test with superuser, and changing the files you said to "root explorer", but still giving error WIFI.
Definitely use the "plan B" and flashing the ROM China. Now they will wait out a new "European ROM" cooked.
Find the link in this forum for the European RUU, only I have not got the tools and skills to cook.
Sorry for my bad English, I use "go Translator"
al_nadita said:
Thank you very much jaggy jags.
I did a test with superuser, and changing the files you said to "root explorer", but still giving error WIFI.
Definitely use the "plan B" and flashing the ROM China. Now they will wait out a new "European ROM" cooked.
Find the link in this forum for the European RUU, only I have not got the tools and skills to cook.
Sorry for my bad English, I use "go Translator"
Click to expand...
Click to collapse
Sorry about that. I should have mentioned the files permissions have to be the same. I haven't checked this by myself I cannot confirm. I edited main post to say this.
Hello, I am just a beginner in android, what do u mean by the files permissions, u could explain in more detail what is the procedure for doing that ? or someone else that has this knowledge ...and write this step by step for rest of us that have little experience with setting android to be able on succeeding this. I want to get root on my explorer but I am afraid that will lose my wifi connectivity after and i am not sure that I will manage to replace that files with corresponding "matched files attributes".
Another request is if I could make a complete back-up of my original firmware/rom of my phone to have it in case that something vent wrong in process of rooting (to restore my phone on factory condition)? It is doable in any way it is any software for this? The European version will contain all languages or just base english?
thank you!
Reason for WIFI error after rooting
Just jumping in for letting u guyz know the reason reason for why u get wifi error
The zip "A310e_recovery...." has a boot.img in it, which is basically a kernel and if for any android device you flash a kernel you need dhk.ko or similar file (which should be in system/lib/modules) as mention alot earlier by jaggy. (this dhk.ko is a file which acompanies kernel/boot.img to run the data connection and wifi and other stuffs)
So basically to avoid all these, simple step is:
You can open recovery.bat present in the zip with a text editor (i suggest Notepad ++, default windows notepad will mess up the files) and delete the line "fastboot flash boot boot.img". now save and exit.
So, Dont flash the boot.img as it is not giving u guys any benefit. just flash recovery.img
@Jaggy. for link2sd, which ext r u using for sdcard partition , 1 2 3 ??????
jitin02 said:
@Jaggy. for link2sd, which ext r u using for sdcard partition , 1 2 3 ??????
Click to expand...
Click to collapse
Fat32 partition
No other format is supported by our rom.
I will be reuploading the recovery in a while with the .bat edited and clarifying the fat32 format.
So are you sure the recovery will be flashed just as good without the boot.img ?
jaggyjags said:
Fat32 partition
No other format is supported by our rom.
I will be reuploading the recovery in a while with the .bat edited and clarifying the fat32 format.
So are you sure the recovery will be flashed just as good without the boot.img ?
Click to expand...
Click to collapse
to be frank i have not tryd editting and using the .bat again
but the one i am sure is the fastboot method . flashing via adb
the command is "fastboot flash recovery recovery.img"
and the folder inwhich u need to put the recovery.img is the "tools" folder in adb main folder , which on my laptop got made in c drive (the main drive)
---------- Post added at 05:07 PM ---------- Previous post was at 04:30 PM ----------
I am not able to get this link2 sd thing work on my official Asian rom
jaggyjags, can u guide me on this one??
jitin02 said:
---------- Post added at 05:07 PM ---------- Previous post was at 04:30 PM ----------
I am not able to get this link2 sd thing work on my official Asian rom
jaggyjags, can u guide me on this one??
Click to expand...
Click to collapse
Sure! same procedure for both asian and stock rom (and any other y suppose).
using minitool wizard
make two primary fat32 partitions (not logical) of your micro sd. plug to computer using a sd card or usb adapter (dont plug phone by usb). the main partition at the left which will be the one detected by windows and then the second one (the rest of the available space).
And thats it, select the type of partition when opening link2sd and you will need to reboot to start moving apps (the app will ask to reboot).
note that if at anytime you clean rom partition (option in recovery) you will need to format the second partition again as this option makes it a ext-3 format and it is not supported.
Once in automatic, apps will install directly to the partition but if you link them manually you need to reboot to see the changes (at least me )
Recobery.bat error
run the recovery.bat in fastboot mode (first option in the "3 android menu" ) with phone connected with usb.
(Note: I edited the recovery.bat and removed any unnecessary commands so no errors occur)
Done!, you got the recovery installed if no errors, you can now install any compatible .zip rom.
Click to expand...
Click to collapse
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
acasanovas said:
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
Click to expand...
Click to collapse
Try this and report back:
Here i am assuming u have adb installed on ur pc/laptop
take ur device battery out and insert it back.
while long pressing volume down press power button untill u see a menu with 3 androids at the bottom.
now select fastboot option and connect via USB. now u will see fastboot usb or something like that.
now open cmd and enter the path to ur adb folder . for example in my case my folder is in my c drive and i enter
HTML:
cd\
cd android-sdk-windows\tools\
place the recovery.img in adb's tool folder.
Now enter following (this is after u navigated to the adb's tool folder)
HTML:
fastboot flash recovery recovery.img
fastboot reboot
If all went right, so u have the custom recovery (clockworkmod recovery) on the device or if not please post here , we will try help u again
acasanovas said:
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
Click to expand...
Click to collapse
download the recovery again and try. It is a simple problem. Reuploaded de recovery and deleted "adb wait for device" command line because it keeps waiting endlesly. I forgot to delete before, sorry about that.
try it and tell me how it goes
@jitin02 it is simpler than that I already eliminated the adb command and should work with no issues. Recovery reuploaded!
It works and wifi too!
jaggyjags said:
@jitin02 it is simpler than that I already eliminated the adb command and should work with no issues. Recovery reuploaded!
Click to expand...
Click to collapse
Thaks @jitin02 and @jaggyjags it works!!!! so nice!!
now how can I install de superuser?
Where and how i have to put that :
adb push bash /system/bin
adb push profile /system/bin
adb push su /system/bin
adb push busybox /system/xbin
adb push su /system/xbin
I have the superuser folder in the same directory of adb, an then?
Can u help me again?
Thank u very much!
Easy, put it in the Microsd card and then open recovery in the 3 android menu (pressing -volume and power for 10 seconds after taking and placing battery). install it with the "install zip from sd" option and select your .Zip
confirm it moving up and down with volume keys
It works perfectly and wifi too! Thank u so much again!
Sent from my HTC Explorer A310e using XDA App
U can share for me back up this rom?
Don't understand, sorry. what rom do you mean?
Everything worked perfectly on my Italian/Vodafone HTC explorer!
No need to create any partition on my SD card to move apps using Link2SD. Is it advisable to do so?
I moved many useless vodafone apps on SD, wanting an European custom rom
Thanks so much!
jaggyjags said:
Don't understand, sorry. what rom do you mean?
Click to expand...
Click to collapse
This rom which u're using in first post.
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.
After lots of hard work by a great team of people (listed at the end), we have finally made a working Root for the Acer Iconia Tab A110.
Warning:
Code:
*I, nor any of the people involved in the rooting process of this
tablet are responsible for any damage you may cause to your device.
*If you brick your device, we are not to blame.
*Your warranty may be void after doing this.
*By using this guide, you acknowledge that you are fully responsible
for any damage you cause to your device and the device accessories.
ACER ICONIA TAB A110 ROOT GUIDE 4.1.2
UPDATED NOVEMBER 13, 2013; Most Recent Version
You will need to download/install the following before starting:
Acer Iconia Tab A110 USB Drivers (Should install on first connect of tablet)
Android SDK
SuperSU
a110-412-CWM-recovery.img Mirror: a110-412-CWM-recovery.img mirror
___________________________________________________________________________
Once downloaded, extract the Android SDK to a known location, such as the Desktop. (Use an extracting application such as Winrar)
Next, install the Nexus 7 Toolkit.
___________________________________________________________________________
Once that is complete, you can begin the rooting process.
On your device go to:
Code:
Settings > Developer Option
Turn Developer Options on at the top, and enable USB debugging.
Navigate to your Android SDK folder:
Code:
adt-bundle-windows-x86_x64\sdk\platform-tools
Copy and paste the recovery file in this directory, and copy the SuperSU files to the Tablet's SD Card. This will make the process easier later.
___________________________________________________________________________
Bootloader unlock:
The next step will wipe all your data. Remember to create a backup of anything you want to keep before attempting this.
Open a command promt (CMD) window in the directory above by holding shift while right clicking in the window and selecting "Open Command Window Here."
Type in CMD:
Code:
adb devices
Code:
adb reboot bootloader
Wait for the tablet to load into the bootloader, then type:
Code:
fastboot oem unlock
Accept on the tablet via volume and power buttons.
Your bootloader should now be unlocked.
___________________________________________________________________________
Root:
Type:
Code:
fastboot reboot-bootloader
Wait for it to reboot, once again.
Next, type:
Code:
fastboot devices
Code:
fastboot boot a110-412-CWM-recovery.img
Wait for the "OK" notification.
___________________________________________________________________________
Now, you will be booted into the custom recovery.
Right click on the Acer A110, and select install driver. Choose to point to your own path, and point it at the path for the Nexus 7 Toolkit install. (Make sure you have include subfolders checked)
Now, the device should be recognized and the root can continue.[/Code]
___________________________________________________________________________
On the device, use the volume buttons to navigate and power button to choose.
Select Install from SD.
Now type:
Navigate to the CWM-SuperSU-v0.99.zip file.
You should receive a complete message.
Once that is complete, on the tablet, navigate to reboot, select yes at the prompt, and the tablet will reboot.
You are now successfully rooted on 4.1.2!
___________________________________________________________________________
Special Thanks to the following people for their ongoing hard work:
fringle
FriedBacon
Skellums
posterz
heX79
blokenfeffer (New Recovery Image)
Stock Recovery
Here is a link to the Stock recovery pulled off of my tablet.
Not sure if it works or not, but if someone wants to try:
Stock Recovery
Installing Applications/Games to the External SD Card
I spent a long time looking for a program that allows me to do this, and finally found one that fully works.
DirectoryBind works wonders.
Here is a link to the guide:
DirectoryBind
Enjoy your extra storage space!
Reserved for further development..
Reserved for further development...
Reserved for further development
Thanks to the root method ? Could you tell me how to perform full system backup?
DjDom said:
Reserved for further development
Click to expand...
Click to collapse
I am a newbie to android. could anybody tell me how to perfrom full system backup for acer a110 4.1.2?
There is currently no way to make a full nandroid. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
root error！ help！
DjDom said:
There is currently no way to make a full android. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
Click to expand...
Click to collapse
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
cooltravis said:
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
Click to expand...
Click to collapse
Did you download the most recent version of ADB?
Make sure you install all the drivers and follow the beginning of the guide.
Completed process but no root
I finished the process but it did not work with the first img I will try with the other one
francois2012morin said:
Does not work for my tablet. It does not unlock the bootloder so I don't get the recovery file to load.
Is it a problem with the version of my tablet software.
Here are the specifications
Android 4.1.2
Core 3.1.10
Image version Acer_AV051_A110_RV00RC09_WW_CUS1
BUILD NUMBER Acer_AV051_A110_1.049.00_WW_CUS1
Image ref FM.S1RA0.03E
Thank you if you can be of any help.
Francois
Click to expand...
Click to collapse
How did you try unlocking the bootloader?
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
running_onCode said:
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
Click to expand...
Click to collapse
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
DjDom said:
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
Click to expand...
Click to collapse
Yea. Everything. Anyway to get passed it?
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
darthpilsner said:
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
Click to expand...
Click to collapse
Yes i am having the same problem, mine does not see a110 but refers to google galaxy nexus adb interface. I have tried this about half a dozen times with the same result, no root. Oh well try try again. Do i need to factory restore after each failed attempt?
No Root....
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
rocy1971 said:
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
Click to expand...
Click to collapse
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Same
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Model a110
Android 4.1.2
Kernel 3.1.10
image acer_AV051_a110_rv00rc09_pa_cus1
Build acer_AV051_a110_1.049.00_pa_cus1
everytime I do it .... it looks like it will work... then check root with rootchecker or susuperuser.... no luck.....
If the root did work... would app2sd work... or do I have to wait for a custom rom?
Same result here!
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Exactly the same results as the previous guys, every step appears successful, including sideload, but no SU after reboot. My Firmware has WW in name.
Only messages seen during sideload which imply errors are E: can't mount /cache/recovery/log etc etc.
Anyone any idea what may be wrong?
Root & TWRP Lenovo Tab 2 A8-50F (MT8161)
Ok so this is a in depth tutorial on obtaining root and installing twrp for the device in the title. Anything in "quotes" eg, type in cmd "adb devices" quotes should be ignored. This guide is for those who know what root is and know there way around windows and Linux. If you did something wrong i am not liable and maybe you should have read things before trying.
EDIT: for those of you who want to root in one or two clicks i have added support for this device in the ZEUS TOOLKIT wich will root without installing custom recovery.. LINK >> http://forum.xda-developers.com/showthread.php?t=2644166
REQUIREMENTS/DOWNLOADS:
-Windows PC & Linux (Ubuntu. virtual box would be fine although i have my pc dual booting both os's)
-Driver Signing Disabled on Windows 7 and above
-Device Drivers
-SpFlash Tool (including scatter file)
-Adb Tools
-TWRP + SuperSU Files
-Insecure Boot.img
LINK FOR ALL REQUIRED FILES >> DOWNLOAD << DOWNLAOAD AND EXTRACT TO DESKTOP
Downlaod all of the above and extract/move everything to a folder which for this guide i will assume will be called ROOT on your DESKTOP
SOME READING:
The Lenovo Tab 2 A8-50F is a rather locked down device with the ability to reflash the stock rom on every reboot if required. In this guide you can only do things in a specific order to be able to get it rooted and stop the stock recovery reflashing. It took me a few times of (soft)bricking my device before i could get it sorted to a stable rooted system with twrp installed. TWRP recovery was not built from source by me personally (it was obtained from a russian website) although i have had to modify the TWRP image as it was boot looping but its sorted and working now. So roughly this is how things are going to go, we will use SpFlash tool to readback the system partition, then use linux to modify a file in the system.img the use SpFlashtool to refalsh the modified system.img. Then we are going to unlock the bootloader and then flash an insecure boot.img along with twrp and then root using chainfire's latest binarys.
THE GUIDE:
STEP 1 - installing the drivers
For this i will assume you you have already got adb driver installed if not please google it i personally used googles generic adb driver.
Please make sure you have disabled driver signing for windows "GO HERE". Now open device manager and right click on your pc's name at the top of the list and select add legacy hardware > click next > check "install the hardaware that i manually select from a list (advance)" and click next > highlight "show all devices" and click next > click "have Disk" > click "browse" > browse to the desktop\root\MTK Drivers all windows\ and choose the folder to match your windows installation and then choose the 32bit or 64bit driver file depending on your windows install > click open > click ok > highlight "MTK USB PORT" > click next > click next > if a warning pops up click install anyway > click finish. Your drivers are now installed for spflash tool to recognise your device.
STEP 2 - backing up system partition
Make sure your device is truned off and disconnected from your computer. Open SPFlash Tool form "Desktop\ROOT\SPFlash_tool\flash_tool.exe" > click "scatter-loading button > browse to "Desktop\Root\ and open MT6735_Android_scatter.txt > click the readback tab > click add > double click the entry which is now listed >browse to "Desktop\Root" and in the filename box type "system.img" > click save > check "HEX" > for region select EMMC_USER > for start address type "0xb000000" > for length type "0x74000000" > click ok > click readback. now with your device turned off connect the usb and the SPFlash tool will begin to backup your system partition to "Desktop\Root\system.img" wait until its finished and continue to the next step.
STEP 3 - editing the system.img
Now we have the system.img transfer it via usb (or whatever means) to your ubuntu machine place system.img in your ~/Home/ folder eg. ~/Home/System.img now open a terminal by pressing CTRL + T > type "mkdir output" press enter > now type "sudo mount -t ext4 -o loop system.img output/" press enter > type your sudo password > press enter > type " cd output" press enter > type "sudo mv recovery-from-boot.p recovery-from-boot.bak" press enter > type "cd" press enter > type "sudo umount output/" press enter. The system.img has now been modified and can be transfered back to windows. Goto next step.
STEP 4 - unlocking bootloader
With device booted to android and usb debugging enabled open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot bootloader". Your device will now reboot into fastboot mode when it displays "fastboot mode in the bottom left of the screen type into cmd "fastboot oem unlock" > press enter > screen will change and ask you to confirm do this by pressing vol+ > wait and when a screen with three boot options appears DO NOTHING and go to next step.
STEP 5 - flashing insecure boot.img
Now you should have the ability to flash the boot. Type into cmd "fastboot flash boot boot.img" the device will let you know it is done and when it is done flashing just type into cmd "fastboot reboot" and let the device fully boot and goto the next step.
STEP 6 - flashing modified system.img
now open SPFlash tool again it should have remembered the scatterfile if not reload the scatter file. In the main window of the download tab make sure ONLY system is checked then in the location colum click the space in line with system and browse to your modified system.img and click open. At this point before doing anything make sure your device is turned off and not connected to the computer in any way. Now click Download in SPFlash tool then connect your device via usb while turned off and the tool will begin flashing the system.img wait until it is finished and a green tick appears in flash tool and if your device does not boot automatically then unplug it and reboot it wait until it fully rebooted and goto next step. You can close flash tool for now.
STEP 7 - flashing TWRP recovery
with your devfice now booted with a custom boot and system image open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot bootloader" > press enter your device will boot into fastboot mode again when it has type "fastboot flash recovery recovery.img" > press enter > when its done type "fastboot reboot" > press enter now wait for the device to fully boot and goto next step
STEP 8 - flashing Supersu by Chainfire
Now your device has rebooted it will be missing the super user app and all binary's so open file explorer on your computer and copy the SuperSU-v2.46.zip from the ROOT folder on the desktop to the download folder on your device after doing that open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot recovery" > press enter. Your device will now reboot into TWRP recovery check the little box and swipe the arrow at the bottom to continue now touch install > touch Download > touch SuperSU-v2.46.zip and finally swipe to install. when it is finished reboot. Hey presto one rooted device with a fully working twrp. reboot and download busybox from play store and install as some programs like system app remover need some binarys from busybox.
After following the above steps you will have a fully rooted device wich can be backed up via twrp and flashed via twrp. now i have figured this out, i think its someone elses turn to build a rom for it preferably Cyanogenmod Thanks for reading this guide and all the best luck with your new rooted device. please remember to click thanks.
Have you found a way to root it without the need for Linux?
Hi
I would like to know if this guide will work for MT-8735
Thanks in advance,
Dimitris
Anyone found a way to root MT8735 version A8-50L or A8-50LC?
The files seem to be missing...
Any help would be much appreciated. I used the guide fine up until the Step 5.
Now I'm a bit stuck.
Gromit1996 said:
The files seem to be missing...
Any help would be much appreciated. I used the guide fine up until the Step 5.
Now I'm a bit stuck.
Click to expand...
Click to collapse
I used something called Kingroot along with the info and files found here https://forums.lenovo.com/t5/Androi...-to-root-TAB2-A8-50-WiFi-version/td-p/2181021 to help me root without using linux. There is a ROM listed there. If you use Kingroot.apk, you'll have to run it 2 or 3 times to get the ROOT to stick, then you can enable debugging, and oem unlocking in dev options. Afterwards, you can use fastboot to unlock the bootloader and once that's done, use the SP Flash tool to download Max Choen's rom to the device, install SuperSU and Busybox and your gravy!!!
what files? that post does not have any files provided and could someone upload the files that are missing from the post so we could also use them?
keith.valdez said:
I used something called Kingroot along with the info and files found here https://forums.lenovo.com/t5/Androi...-to-root-TAB2-A8-50-WiFi-version/td-p/2181021 to help me root without using linux. There is a ROM listed there. If you use Kingroot.apk, you'll have to run it 2 or 3 times to get the ROOT to stick, then you can enable debugging, and oem unlocking in dev options. Afterwards, you can use fastboot to unlock the bootloader and once that's done, use the SP Flash tool to download Max Choen's rom to the device, install SuperSU and Busybox and your gravy!!!
Click to expand...
Click to collapse
Who is Max Choen and there are no files in the link provided.
Sent from my LG-D852 using Tapatalk
If you guys read the entire post in the link I sent you might be able to get where I got. I'm not a dev and not much for writing tutorials but my process went,
1. KingRoot
2. Unlock boot loader
3. Flash twrp via fastboot or flashify
4. Factory reset
5. Reinstall King root and re root.
6. Format and partition memory card
7. Install apps2sd
8. Install Xposed
9. Install obb to SD module
10. Enjoy tablet with 64gb of space with tons of large data games installed!!!! (Note that this step requires you own a 64 gig memory card)
keith.valdez said:
If you guys read the entire post in the link I sent you might be able to get where I got. I'm not a dev and not much for writing tutorials but my process went,
1. KingRoot
2. Unlock boot loader
3. Flash twrp via fastboot or flashify
4. Factory reset
5. Reinstall King root and re root.
6. Format and partition memory card
7. Install apps2sd
8. Install Xposed
9. Install obb to SD module
10. Enjoy tablet with 64gb of space with tons of large data games installed!!!! (Note that this step requires you own a 64 gig memory card)
Click to expand...
Click to collapse
Where are you getting a twrp build for this tablet?
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Gromit1996 said:
Where are you getting a twrp build for this tablet?
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Click to expand...
Click to collapse
I will post it in the morning, I think it's on my wife's laptop. The link I posted USED TO lead you to a post that had the files I mentioned and the process I followed. Now they are just suggesting you simply root using Kingo... Which is fine and dandy but does not give you the ability to format your memory card. I will post my recovery image for yall in the morning. You would just have to use KingRoot and then flash TWRP using Flashify once you have a successful root. Then you can format your card and install apps2sd of your choice and xposed with the obb2sd module! That's what I got going on, got TONS of large data games on the tablet cause I installed a very fast 64gb memory card, and BIGGITY BAM!!!! Turned this little budget tablet into something decent for the kiddos! Just wish we could do something about that terrible 1gb of memory, but hell, I was able to get this far so I'm pretty happy!:laugh::good:
keith.valdez said:
I will post it in the morning
Click to expand...
Click to collapse
Define morning in your neck of the woods. [emoji2]
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Here it is!
Had some things to take care of first. Got a wife and kids to care for before I do my geek stuff. This is not a flashable zip! You must unzip the .img file and use Flashify after a successful KingRoot.
P.S. all credit goes to the original creators of this build of twrp I originally obtained in This Very XDA post we are conversing in! All I did was download this file, I am not a dev andi do not take credit or responsibility for any of the files I've used to root this device! Cheers!!!!
Okay... Thanks. I have SuperSU installed and working. TWRP installed and working, but I haven't unlocked the bootloader.
Will this prevent me from installing xposed framework, do you know?
And the which apps, by which developers, do you install to move apps to SD card?
Thanks for your help!
Sent from my LG-D852 using Tapatalk
I am using Link2SD, Xposed OBB2SD module. That's about it. Not sure if bootloader unlocking is even necessary for anything.
keith.valdez said:
I am using Link2SD, Xposed OBB2SD module. That's about it. Not sure if bootloader unlocking is even necessary for anything.
Click to expand...
Click to collapse
Just to get the custom recovery to stick.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Can you flash supersu from stock recovery or do i have to flash twrp first?
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip" 2016-04-06 version
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
for those of you who want to root in one or two clicks i have added support for this device in the ZEUS TOOLKIT wich will root without installing custom recovery.. LINK >> http://forum.xda-developers.com/show....php?t=2644166
Hi,
The link does (no longer) work, can you please update it?
Thanks!