There's a hidden feature in Android 6.0, multi window. It has its warnings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So decide if this is actually for you before following these steps
It's not shown in user builds, so we have to do some messing. You'll either need root or a custom recovery to do this, but as not everyone wants root, here's how you do it with TWRP, a USB cable, and a PC with ADB:
1. Boot your device into recovery
2. Mount your system by going to Mounts > Tick System
3. On your PC open a command line, somewhere like your desktop is useful
4. Type the following command:
HTML:
adb pull /system/build.prop
5. Open the build.prop file with your favourite (decent) editor, I recommend using Notepad++ on Windows
6. Find the "ro.build.type" line
7. Change the text after = to "userdebug" from "user"
BONUS: If you want a nicer DPI here, change the line "ro.sf.lcd_density" to your preferred DPI
8. Save the file
9. Go back to the command line and enter the following command:
HTML:
adb push build.prop /system/
10. Now open a shell doing:
HTML:
adb shell
11. Now a adb shell will open, enter these commands:
HTML:
cd system
chmod 644 build.prop
12. Reboot the device as normal
13. When the device has booted, go to the developer options
14. Scroll down to the bottom of the "Drawing" category
15. Enable multi-window and have some fun!
If you're rooted...
1. Download "Build.prop editor"
2. Find "ro.build.type"
3. Edit it to have the value "userdebug" from "user"
4. Reboot when prompted
5. When the device has booted, go to the developer options
6. Scroll down to the bottom of the "Drawing" category
7. Enable multi-window and have some fun!
Worked ! Thanks
Such a shame the Keynote didn't introduce such feature, it's stable enough. Just think of the use of the feature on a 10" tablet.
works perfect thank you !
How do you use it after enabling?
Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
Go recent menu, on the apps beside the x there's a button to choose the top half or second half.
Multirom users can go /data/media/multirom/roms/ and edit the build prop directly there, no need to use adb. I did it without using a PC
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
I get how to use it, but how do you consistently pick the two apps that you want to appear?
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
elreydenj said:
I get how to use it, but how do you consistently pick the two apps that you want to appear?
Click to expand...
Click to collapse
It seems to be all over the place. I cant figure out how to always get the two apps that i want in multiwindow to show....
prwnd said:
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Click to expand...
Click to collapse
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
is it possible to do that with Wugfresh Nexus Root Toolkit?
jonathanxx1 said:
is it possible to do that with Wugfresh Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
drgonzo712 said:
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
Click to expand...
Click to collapse
I tried also ,,and it doesn't work.
Adr990 said:
I got this message from ADB:
Anything?
Click to expand...
Click to collapse
Open terminal, type
su
cd system
chmod 644 build.prop
exit
and do stages again
Adr990 said:
When I do that, in adb shell:
Click to expand...
Click to collapse
Ow, i forgot ,my mistake sorry can you try this ?
cd system
chmod 777 build.prop
exit
damn.. is there a way to do it if it is a secondary rom on multiboot?
Adr990 said:
Oh and I also tried this:
Kinda wierd how it is not working for some, while we all flashed according to Google's adb flashing method.
Click to expand...
Click to collapse
Can you send your build.prop to me via pm. I can make a flashable zip for you
Hello people, I have multirom installed on my nexus 5, the primary rom is 5.1.1 (LMY48B), and my secondary rom is the developer preview MPZ44Q. I want to know if it's possible to enable multi-window mode since the M preview is installed as secondary rom.
I did it. Reboot into recovery. Swap the Roms. Don't reboot . reboot into recovery again from the reboot tab. Select multiboot tab just to ensure you are OK and the M ROM is the internal.. Mount system and do what the op says. Reboot into recovery again swap Roms again . reboot system and you should be OK. Takes like a half an hour to do though
PS. NEVER FIX SU. ALWAYS SKIP
I understood that if i try to install su on the M rom, it will result in bootloop. And my internal rom is stock ROOTED. So do you think it will work ?
When i will swap the roms, the fact that my primary rom is rooted, will it cause any problem ? Thanks in advance.
Nope my primary is still rooted. And I an typing this from my secondary M ROM with multi window enabled. All you have to do is never fix su for either ROM and never boot the system with M as your primary ROM and you are ok
Help me too
hsay said:
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
Click to expand...
Click to collapse
This is the worst thing to do here but could u please guide me too to the recovery as i searched all i could but still got no answer. Even the Guys in the Discussion group had no answer. Please Help ME,.
Related
1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).
2. Write down the filename of the recovery image EXACTLY as it is written (i.e. recovery-clockwork-2.5.0.1-heroc.img).
3. Put the recovery image file on the SD card (not in any folders).
4. Download Terminal from the Market if you don't already have it and install it (there are a few different terminals in the Market some have an onscreen keyboard and some don't experiment till you get one, also hold down Menu in some of them to bring up the onscreen keyboard if you don't see it).
5. Open the Terminal program and type the following (with hitting enter at the end of each line).
su
flash_image recovery /sdcard/name-of-recovery.img
6. In the above text, replace name-of-recovery.img with the name of your recovery image (make sure the .img is on the end).
7. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM Manager and Clockwork Recovery Image
Superuser Black Screen, Lockup Solution's
Code:
[B][COLOR="Red"]Enable USB Debugging:[/COLOR][/B]
Press the Home button.
Press the Menu button.
Select Settings > Applications > Development.
Make sure that USB Debugging is checked. If not, check it.
[B][COLOR="red"]Clear Superuser data:[/COLOR][/B]
Press the Home button.
Press the Menu button.
Select Settings > Applications > Manage applications.
Find Superuser Permissions on the list. Tap it.
Tap “Clear data” and “Clear cache” if they’re enabled.
Thanks for that!!
forget what i said....found it lol
silverxj said:
Thanks for that!!
Click to expand...
Click to collapse
your welcome i know that not everyone is gonna have access to adb or want's to play with command prompt's
this method is a really simple quick way around using adb that get's the job done
first post updated with link's
ARoiD said:
your welcome i know that not everyone is gonna have access to adb or want's to play with command prompt's
this method is a really simple quick way around using adb that get's the job done
Click to expand...
Click to collapse
is there anyway to do this not using the command prompt? my SU request does not work anymore apparently...
DrededStar87 said:
is there anyway to do this not using the command prompt? my SU request does not work anymore apparently...
Click to expand...
Click to collapse
your phone is not rooted are you running the stock os or a custom rom?
ARoiD said:
your phone is not rooted are you running the stock os or a custom rom?
Click to expand...
Click to collapse
im running fresh 2.0d
DrededStar87 said:
im running fresh 2.0d
Click to expand...
Click to collapse
did you get prompted by Superuser after you entered su?
ARoiD said:
did you get prompted by Superuser after you entered su?
Click to expand...
Click to collapse
my screen just goes black, not the full thing, but i get an error message that says it stopped unexpectedly and must force close
DrededStar87 said:
my screen just goes black, not the full thing, but i get an error message that says it stopped unexpectedly and must force close
Click to expand...
Click to collapse
restart your phone and try again when you get prompted select always allow
ARoiD said:
restart your phone and try again when you get prompted select always allow
Click to expand...
Click to collapse
i still get the black screen after restarting
DrededStar87 said:
i still get the black screen after restarting
Click to expand...
Click to collapse
go into manage applications and clear the cache of Superuser then try again
Superuser solution's added to first post
Re: How To: Flash a New Recovery Image (If You Are Already Rooted) | The Unlockr
thanks for all the help guys, I have the green recovery screen now
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
DrededStar87 said:
thanks for all the help guys, I have the green recovery screen now
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
glad it worked out for ya
YES it worked(yay) i have super fast 728 one btw can i delete the recovery img off sd card now that it worked?
rulyskull said:
YES it worked(yay) i have super fast 728 one btw can i delete the recovery img off sd card now that it worked?
Click to expand...
Click to collapse
it's safe to remove the recovery image from your sdcard after you know it successfully flashed
I'm getting a huge number of read/write errors on this via Terminal - Attempting to flash Amon_RA 1.7 over CM 1.4 on Cyanogen 5.0.7...
kidblue said:
I'm getting a huge number of read/write errors on this via Terminal - Attempting to flash Amon_RA 1.7 over CM 1.4 on Cyanogen 5.0.7...
Click to expand...
Click to collapse
This is for the Sprint CDMA Hero only.
Dear all,
I managed to create a script that enables root!
** WARNINGS **
This has not been tested much... any problems are @ own risk
** Download **
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROOT-A51x.zip (679.1 KB) or http://www.multiupload.nl/8QVEMO3P0R
** Install instructions **
1. First install CWM Recovery (or any other you can find for your device)
2. Upload ROOT-A51x.zip to your external sdcard
3. Run the following command to enter recovery (or power off your device, press Volume- and then Poweron your device):
Code:
adb reboot recovery
4. In the recovery select "install zip from sdcard"
5. Then select "choose zip from sdcard"
6. Choose your "ROOT-A51x.zip" file
7. Choose yes - install ROOT-A51x.zip
8. Wait till the script is ready and reboot your device
If something fails, you can run "adb shell" from the recovery and use "cat /tmp/recovery.log" to provide the output of the scripts.
Enjoy & good luck
Regards,
Nika.
Here's some instructions how to unlock boot loader:
Code:
adb reboot-bootloader
** wait for it to load
fastboot oem unlock
** press Volume- (two dots button) and then Volume+ (one dot button) to unlock
fastboot reboot-bootloader
** you're in the unlocked bootloader :)
I have tried several memory offsets and all return a non-rooted-shell (ie. $ instead of #):
mempodroid 0xd6c4 0xad33
mempodroid 0xd7cc 0xad27
mempodroid 0xd7f4 0xad4b
mempodroid 0xd9ec 0xaf47
mempodroid 0xd9f0 0xaf47
Hi,
i just got the A511 out of the box.
Im very interested if theres a way to root.
mongocliqque said:
Hi,
i just got the A511 out of the box.
Im very interested if theres a way to root.
Click to expand...
Click to collapse
I haven't found a way yet what build number does your device have?
nikagl said:
I haven't found a way yet what build number does your device have?
Click to expand...
Click to collapse
Hi,
I also got an A511. Root is also not working for me
My build number is Acer_AV041_A511_1.028.00_EMEA_DE
I really hope someone will get root working on the A511
Its just annoying that root is still difficult like that.
There are so many things like lbe or pdroid (on other devices) that i never want to miss again on every Android Device.
ACER_AV041_A511_1.028.00_EMEA_DE , @ Kernel 2.6.39.4+
Well... While building a new recovery I killed my recovery and cannot install update.zip's anymore... luckily no brick, but does make it harder to test stuff.
Therefore I cannot test attached root script. It's based on someone else's script to unlock the bootloader first, and then install an update.zip that contains all root files.
Anyone care to test it? It cannot brick your device or kill your recovery, so don't worry. It will probably not work, but doesn't hurt to test it
Furthermore. If there's still someone with a rooted A510, can you dd your recovery and upload it? I can try the stock recovery of A510 to see whether it works on A511
I can think of two commands that may work for exporting recovery on an A510:
Try this:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
Or try this:
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/recovery.img
Or possibly even this:
Code:
dd if=/recovery of=/mnt/sdcard/recovery.img
Regards,
If one of them is successful it will export the recovery to your internal sd...
Nika.
Well, turns out my recovery is not corrupted. Tried installing the 1.011 ROM and it worked without a problem (although I wanted to wait till root would be available so I could do a full backup)... so I guess that root zip provided in the previous post still has some error in it...sorry, will continue investigation, somehow, sometime, somewhere we'll find a way
Would be nice.
Atm im not rly use my Tab, too many Spy Aps around that are confirmed via pdroid.
lbe first for me
Well... my tab is now rooted!! See first post (OP) for the root script & instructions how to do it...
Good luck!
Regards,
Nika.
Sounds nice.
But im waiting if its really secure, that tablet was too expensive to brick
nikagl said:
Well... my tab is now rooted!! See first post (OP) for the root script & instructions how to do it...
Good luck!
Regards,
Nika.
Click to expand...
Click to collapse
Well done, Nika!
mongocliqque said:
Sounds nice.
But im waiting if its really secure, that tablet was too expensive to brick
Click to expand...
Click to collapse
It's never safe if you want safe - don't root, that's what it's for
And yes, first install cwm recovery, then install root-zip from this thread through cwm-recovery.
nikagl said:
It's never safe if you want safe - don't root, that's what it's for
And yes, first install cwm recovery, then install root-zip from this thread through cwm-recovery.
Click to expand...
Click to collapse
Nah, i know that, but first i want to see more rooted devices.
Can this cause issues?
Acer_AV041_A511_1.028.00_EMEA_DE
it really works
Hi nikagl,
thanks, i got root on my brand new, long time awaited A511.
For the bootloader-recovery i had to use the vol button with the two dots (it´s the vol down (-) button in my A511) no matter what direction the turn-look switch had.
Right now did the needed Stock (rooted su 3.1) Backup successfully with the CWM touch.
Really Great Job!
hey guys, i rooted my a511 too thx nikagl
but i did it a lil bit diffrent from your manual
Ah great to hear.
I think that i got issues then with my VB.
So i have to get a real windows pc for flashing recovery, it looks like.
blgblade said:
hey guys, i rooted my a511 too thx nikagl
but i did it a lil bit diffrent from your manual
Click to expand...
Click to collapse
It would be helpful to everyone if you could list what you did.
Thanks.
hmm, i have a problem i can use the su shell, but root applications wont work
EDIT: now it works, with superuser from market
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lieckedeeler & schlex2010
aka SCHLEXEDEELER
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
- Root incl. su & busybox binary (install Superuser from Play Store)
- permanent RW on system folder
- adb root shell
- DVB-T USB support (schlexedeeler Kernel 1.1+)
- CWM Recovery with touch
Click to expand...
Click to collapse
DOWNLOAD SCHLEXEDEELER TOOL V2
=============================================================================================================================
If you want flash back stock kernel or/and stock recovery and stock bootanimation.zip
First step: Copy stcok bootanimation.zip to /system/media
Second step: Flash stock kernel & recovery
It is stock recovery and kernel out of ICS 4.0.4
Download stock bootanimation.zip
Click to expand...
Click to collapse
Download Tool to flash stock kernel & stock recovery
Click to expand...
Click to collapse
Password for the 7zip files:
iknowtherisk!
Click to expand...
Click to collapse
Thank you! Going to try this as soon as i get to my a210.
.... Placeholder ....
And you can just press the 3 point?, Only root, the kernel does not need to unlock me ....
Probably not. It dumps a CWR image to /dev (overwriting the factory recovery?), which is boot, so you have to be unlocked.
CWR is used to mount /system (rw) so that adb can push Superuser and some other binaries.
I got stuck, after loading up CWR. My Windows 7 (x64) couldn't recognize my A210 while CWR was running. Downloaded USB drivers through the Android SDK, and the Acer USB drivers, but neither of them did any good i continued with the rooting process (so that it could clean up after itself) but nothing got pushed to /system (which is no surprise, seeing my tablet was unrecognized). So, now i have an unlocked bootloader, no root, and i'm unable to get into recovery... nothing happens, if i hold volume down, while powering on. I have to press the reset button, to restart it properly.
Could it be that there are no drivers for Windows 7 x64?
Edit: ok, i've read through the topic at android-hilfe.de, and got it working (had to manually install the driver). Now i have root! Thank you!
help for dummies
deleted
deleted
does it give a instruction for this tool, it would be great
Greets
Is anyone working on a ROM or MOD for the Iconia A210 ?
Sent from my A210 using xda app-developers app
Hey 4.1.1 To have?
Alexey71 said:
Hey 4.1.1 To have?
Click to expand...
Click to collapse
What exactly is your question?
I don't know if it will work with 4.1.1, because I do not have 4,1.1 on my tablet! You have?
I get everything back to its factory state, or even be the standard kernel?
Alexey71 said:
I get everything back to its factory state, or even be the standard kernel?
Click to expand...
Click to collapse
Sorry for OT:
Please learn english, or use a better translater tool for your questions!
You use this tool at your own risk, so please stop bugging me with private messages AND forum posts!
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
And when I checked whether I'm root or not, it turns out that I wasn't.
Any ideas or suggestion?
Still, thanks a lot for your job.
Tab acer A210 user said:
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
Click to expand...
Click to collapse
FIRST OF ALL you don't read the thread correctly:
The "How to" of Heroturtle is NOT for V2.0 Final Edition!! Do not use that "how to" !!
So here is what the tool do if you select root:
Start your device into bootloader (fastboot mode)
Flash boot.img to your device via fastboot
Pushing binary files like su and busybox to your tablet
READY!
It's important that you have install all drivers correctly!
The 4 points are from the Versions before and are not necessary anymore now.
If you have done the root process, you must install SuperUser from the PlayStore! After that you have root!
Use only schlexedeeler Tool V2... You are confusing something and write about things that no longer exist in the new version!!! No restore my data. etc...
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Tab acer A210 user said:
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Click to expand...
Click to collapse
If not, please let me know, then we will find a solution for you, but I think if you do only that, what the tool tell you, you're on the right way :good:
Alexey71 said:
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
Click to expand...
Click to collapse
I will talk to lieckedeeler... Maybe he have a solution for that.
Minor Update 2.01:
* correct some missspellings
* correct adb command for flashing CWM recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tutorials and the tools are not my work, so I don't take any credit. However, the tutorial is come from China. I combine my experience and translate them as much as I can to english.
Instructions:
First, download the root files (at the bottom of this post) accroding to your tablet model (at the back of your tablet) and install the driver in the computer.
Please install in the following order:
1) iSocUSB-Driver-Setup-1.2.0.exe
2) IntelAndroidDrvSetup1.5.0.exe
3) PhoneFlashTool_5.3.4.0_win32.exe
Pay attention to the following points
a) you must install those driver in the above order
b) Don't change the install location of those driver
c) Close your antivirus software to avoid unknow problem
Then, go to Settings>Developer Options>USB Debugging. Enable OEM Unlock and enable USB Debugging Mode
Now, connect your X80 Plus to the computer,
Open a Command Prompt window in "Root X80 Plus H6C3" folder (To open a Command Prompt window in any folder, hold down the shift key and right-click on the folder) and enter the following command
Code:
adb reboot bootloader
Press Enter
Wait for the device to enter fastboot mode
Code:
fastboot oem unlock
Press Enter to unlock the oem and enter the following command
Code:
fastboot flash boot boot.img
Press enter to flash the kernal, then enter the following command
Code:
fastboot reboot
This command will restart your tablet.
It is normal that tablet reboot 3 to 4 times automatically, just wait for it. (turn on the tablet yourself if the tablet do not reboot automatically)
After your device is on, check that Wifi and bluetooth works or not. (Wifi and Bluetooth may not works with the replaced kernal, just perform a factory reset)
If everything is ok, enter the following command
Code:
root.bat
Wait for the Command Prompt until it stuck at this command, "adb shell su --daemon"
Now, disconnect the tablet and reboot it manuly
After the device was booted up, Supersu already become a part of system app.
Open Supersu now, it will notify that the SU binary needs to be updated. You must need to install the binary once, but you will fail at 100%(unless there is a miracle, and your tablet is root successfully, congratulations)
Close Supersu and reconnect the tablet, enter the following command again.
Code:
root.bat
Now the command prompt should run all of the command smoothly and Supersu should have no message about the SU binary update !!
Therefore, if your Supersu shows nothing (works properly), your tablet is rooted, thats amazing.
If Supersu keep notifing, please enter the following command again and wait for it to boot up automatically until Supersu have no message about the binary update.
Code:
root.bat
Note that this root method are not stable yet
Known issues:
1) Old version of Titanium Backup was unable to execute the SU command
2) LBE are not 100% compatible with this root
Post reply if you have any requires or problem.
Stock Rom for X80 Plus just in case you need them, and the instruction will be translated later
H6C3 and H5C5
Root files: H6C3 and H5C5
Sorry for my bad english
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
thanks and your thread on teclast's forum where the link was crash, please repair.
Thanks a lot
Can someone confim that this method works?
Jeconxis said:
thanks and your thread on teclast's forum where the link was crash, please repair.
Click to expand...
Click to collapse
You can try to flash xposed using flashify!
woody4165 said:
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
Click to expand...
Click to collapse
Working hard on it now
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
looking forward to this!
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
I tried your method on my H5C6 and it worked beautifully. Thank you!
where can I use the file?
I download the file named X80 plus-win10_20160108.7z from the link. what is this, and where can I use it?
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
woody4165 said:
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
Click to expand...
Click to collapse
Hiatus
H6C4
Great! It works perfectly on H6C4.
Thanks!
Regards
RoroTiti said:
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
Click to expand...
Click to collapse
It's updated from play market with no problem.
May be it is my particular problem ( kernel 3.14.37 firmware assembly ver 3.03.20161109) but.....
WARNING TO H6C4 OWNERS! SD Card becomes unusable with this rooting files. Any SD Card after rooting recognized as 0,9 Mb size and you can't access files on it. You can't use SD Card reader too.
Please report if you do not encounter this issue.
Hi.
I'm stuck on "adb push SUfiles/Superuser.apk /data/superuser" command in root.bat
I've done all the previous steps without problems.
Before executing root.bat I have set again Usb Debug and OEM Unlock, is it correct?
Sometimes I get stuck on "adb remount"
What can I check?
Thanks
Woody
Team Win Recovery Project 3.0.2-0
How it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice : I don't own the device my self, so i need some one to test this method.
This will allow you to install TWRP and flash SuperSU!
Step 1 : Unlocking your bootloader
You need unlock bootloader first before installing twrp.
You will also need adb and fastboot. You can download them in a portable small form factor here :
[ADB FASTBOOT][LINUX&WINDOWS]
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
Enable usb debugging on developer option, and extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
Step 2 : Running recowvery
You can find the recowvery binaries (you need to download all of these) at :
Here
You're now ready to follow the recowvery installation instructions.
See here (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3 : Flashing TWRP & Rooting
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, or you can also just use adb push. (mentioned here)
Download TWRP build here.
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from here to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU : here
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4 : Have fun!
Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄
ModaAli said:
Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄
Click to expand...
Click to collapse
so root is done, then time to try twrp just if u not busy
And then for custom rom ??
But later, I'm so busy sorry ? ?
ModaAli said:
And then for custom rom ??
But later, I'm so busy sorry ? ?
Click to expand...
Click to collapse
Don't hope too much this is still for testing but probably soon will have a custom rom, well good luck for your exam bro :good:
It will be sure
Thanks bro ?
Thread closed per OP request.