Related
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"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"
}
I'm trying to root my Rogers One X running 4.1.1 using these instructions, howtorootandroid.org/2013/05/28/how-to-root-htc-one-x-step-by-step-tutorial/ (as a new user I'm restricted from posting actual links).
I've got everything completed to the point where it says to disconnect the USB cable and select Recovery from the HBoot menu. When I select that, the phone reboots to the home lock screen. The next step says to go to Backup and backup the system partition. Problem is, I don't know where they mean when they say go to Backup. The only Backup function I know of is in Settings and that just backs up the Google user account data. How does one backup the system partition? Is the phone supposed to reboot to the lock screen from the Recovery prompt? Or is something going awry in that step?
After that it says go to install and install the SuperSU.zip file. Using a file manager I can locate the apk for the Superuser app and it installs but when I open it I get a message saying "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" That last part seems obvious.
Thoughts appreciated on how to resolve.
Thanks.
Stop what you're doing, you're using a root process for the wrong device. That's for the quad core One X, if your phone is a Rogers phone then it is the dual core version. To be sure, go into your bootloader and tell us what it says there, only the top four or five lines. To get into the bootloader, simply power the phone on by holding the power button and the volume down button at the same time, keep holding until it boots into a white screen, that's your bootloader.
Sent from my Evita
Thanks. Don't need to go into bootloader, just checked the device hardware information and you're right, it's a dual core. Using the volume + power buttons won't go into bootloader. I can get there with the Hanson2000 utility. The items in the Fastboot USB menu are Bootloader, Reboot, Reboot Bootloader and Power Down.
Through the process I used last night, the bootloader is unlocked and I haven't bricked the phone.
What's the process to root a dual core version, then?
Another question. Since the bootloader is now unlocked, do I need to continue to finish rooting the phone? With the bootloader unlocked, I can install custom ROMs, right? That's, ultimately, the goal. I'm trying to be able to update to 4.2 or 4.3 which, I've been led to believe, will also enable full USB host functionality on the phone.
Thanks.
Essentially you've done the hard part now. All that is left to do is install a custom recovery, and then you'll be able to flash custom ROMs from within that recovery. The AIO kit only has the ability to install TWRP 2.5 I believe, and that version is riddled with faults. So below I'll outline how to install a stable version.
Download TWRP 2.6 from here. You'll need to flash it manually using fastboot. So once you've downloaded it, put it in the same directory that adb and fastboot reside in on your pc and connect your phone. Now you need to open a command prompt from within that directory (shift + right click opens the menu, then select open command prompt here). Enter the following command:
fastboot devices
This will make sure you're connected properly, hopefully it will return your device serial number. Now you want to enter the following commands:
fastboot flash recovery "filename.img"
(the exact recovery filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you'll have a custom recovery which you can enter by pressing the recovery option on your screen. Now it's time to select the ROM you want to try and download to your pc. Once you've done that, select mount from the recovery menu, then select mount usb storage. Your phone memory will now show up as a removable drive on your pc and your can copy a ROM across.
Before you flash a ROM, make a backup of your current setup, you can do this by entering the backup option from the main recovery menu. It's essential to backup the system partition in case something goes wrong in the future, you can easily restore it.
In terms of ROMs, only EVER download ROMs you find in our forum. Never download from a different device forum or from another site, that's a surefire way to brick your phone. Your two options are Android Development, where you'll find Sense based ROMs, and Original Android Development, which is where you'll find aosp ROMs.
Once you've copied a ROM to your phone, simply perform a full wipe in recovery (cache/dalvik cache/factory reset/system), do this by going to the wipe option, then advanced wipe. Just don't wipe sd card. Then you can select the install menu, and find the ROM on your sd card, and install it.
Your phone is s-on, so you'll need to perform one extra step. When you download the ROM, within the root folder of the zip file there is a file called "boot.img", you need to extract this and copy/paste into your adb/fastboot directory. After the install process has finished in recovery, go back to the main menu and select reboot, then select bootloader. When the phone reaches bootloader, make sure it's connected again and issue the following command:
fastboot flash boot boot.img
Now you can reboot your phone and enjoy the ROM. Please note, you will need to flash the boot.img from each ROM you want to install. Unless you decide to get s-off, which removes that need.
Sent from my Evita
Actually, AIO allows you to use the TWRP, ClockWorldMod or your own file. I downloaded the file you linked and WinZip says it's an invalid archive. Can I use CWM instead?
It is suggested that you use TWRP, other recoveries are known to have bugs. Don't worry about what WinZip says, just check the md5 and as long as it matches the md5 listed on the download page it's fine.
I'd also suggest doing it the manual way as you actually learn something during the process. The time will come when one day you need to do something manually, and it's better to have a little experience than have to learn at zero hour.
Sent from my Evita
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
Don't get me wrong, AIO kits are convenient, but they're also a big part of the reason why people have absolutely no idea about what they're doing to their phones, or how to recover if something goes wrong.
Sent from my Evita
Problem is that WinZip shows no file when it opens the archive. Can't do anything with it.
I understand your point about doing it manually. I'm a photographer and an end user, not a programmer and don't do code well. I can likely manage getting the recovery installed but took a look at a couple of the custom ROM threads and have no idea what the people posting the threads are talking about insofar as some of the instructions. I just want to get the phone able to operate as a USB host.
It's not a zip file, that's why. You're not meant to be able to do anything with it on your pc. Check the md5 like I said and you'll know the file integrity is good. Then you just need to flash it as per previous instructions.
Sent from my Evita
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
What do you mean by usb host? In what kind of application?
Sent from my Evita
Sounds like he wants a rom with OTG support
Yeah that's what I was thinking.
Sent from my Evita
Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?
RFPhotog said:
Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?
Click to expand...
Click to collapse
That's a bit odd, it shouldn't download as a zip, it should be a file with the ".img" extension. Did you download it from the link I posted? Are you able to check the extension type in file properties?
Also I noticed you had a command return saying 'openrecovery-twrp-2.6.0.0-evita', did you make sure you put the ".img" extension on the end of your fastboot command?
Sent from my Evita
I did include the .img extension. Tried it again now and it worked. I must have made a type when I tried the first time.
So, I have a custom recovery process installed. Now, what ROM would you suggest?
By the way, I do appreciate the help.
I can't really suggest a ROM, as best/favorite ROM threads and questions aren't allowed on XDA. In this case I can probably point you in the right direction though.
The OTG side of things lies within the kernel though, not the ROM itself. The only kernel I can think of that has this support is the Rohan b6 Kernel, which you'll find here.
This means you'll only be able to use 4.1 based ROMs from this section though. The reason for this is because aosp kernels can only be used with aosp ROMs. If you try to use this kernel in conjunction with a sense based ROM, or an aosp ROM from a different android version (4.0, 4.2, 4.3) it won't work.
Keeping all that in mind, there are some great 4.1 aosp ROMs in that section. Development has moved into 4.2 and above but you'll still find the 4.1 ROMs there. Just make sure to look at the android version in the title and features of the ROM.
Flashing a custom kernel is an extra step in the install process too. Do the wipe in recovery like I described earlier, then install the ROM, then install the kernel. Instead of extracting the boot.img from the ROM zip, extract it from the kernel zip and use the same method I outlined before to flash it in fastboot.
Sent from my Evita
---------- Post added at 02:22 AM ---------- Previous post was at 02:22 AM ----------
Oh, and it's no problem at all, always willing to lend a hand.
Sent from my Evita
Well, we're getting there, I think.
I've got the file loaded onto the phone. The filename is rom.zip. I've done the wipe and then from the Install menu I selected the rom.zip file and swiped to start. Got an error message saying 'unable to open zip file'.
Tried a different ROM and it worked.
Which ROM did you end up going for?
Sent from my Evita
Started with Evervolv. That's the one that didn't work. Then went to Cyanogen. It's still booting for the first time so still hoping it all worked.
Did you flash the boot.img via fastboot afterwards?
Sent from my Evita
Yep. The one from the new kernel.
Did a wipe, advanced wipe, installed the ROM, installed GAAPS, installed the kernel, flashed the boot.img from the kernel zip file.
It's at the Cyanogen spinning wheel. My understanding is that it can take a while on the first boot?
If it sits here for much longer, I'll do it again, wipe and reinstall.
It can take a while, not normally longer than five minutes though.
Sent from my Evita
I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.
I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!
I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.
Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip
plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk
That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....
Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....
Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....
I'd like to create a new thread on installing TWRP and rooting Android Nougat (7.x) on version B360 of the Honor 8. All the threads I see are people frantically trying to restore their phone to their previous glory. To keep people from asking "will this work on yada yada model, *I* have a FRD-L04 which is the 32gb unlocked SINGLE SIM variant sold locally at Best Buy here in the states and I'm pretty sure the FRD-L09 is the international DUAL SIM version with 64GB and I believe firmware for both of these are different? If not, please correct me. The process should be the same for all variants, but the files used will be different.
I want to update this OP and keep it as up to date as possible. If we can get 3 or more people to confirm a certain process works in this thread, I will update it with the proper links to all tools/files/versions of TWRP and SuperSU as well as firmware that's needed. I think I currently count eleven different threads all over the place on this and would be nice to have it centralized. Let's help out and get this phone going with a working root on Nougat!!!
Here are the questions I propose:
1. What is the actual steps to root the Honor 8 running a FULL STOCK version of B360 (Android 7.x)?
A. Unlock Bootloader (This process should be the same as always)
B. Flash TWRP (Which version?) This should be a simple flash with fastboot
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
If I can have answered the questions above, I will clean it up and move it over to the guide section. As it stands now we have no guide. We just need clarification on what works, what doesn't and the process.
Also, PLEASE be kind to those who don't speak English as their primary language. The Honor 8 is an international phone and I see many people getting angry because they don't understand or don't follow instructions correctly because the OP didn't clearly state what they did. Let's help each other out!
Here's an example step by step for unlocking the bootloader below. This is what I'd like to do for each of the questions above.
A: Unlocking the bootloader (UNDERSTAND THAT BY UNLOCKING THE BOOTLOADER ALL YOUR DATA ON THE PHONE WILL BE ERASED AS IF YOU'RE PULLING IT OUT OF THE BOX FOR THE FIRST TIME)
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/HiSuite_en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio/releases/platform-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
B. Flash TWRP (Which version?) This should be a simple flash with fastboot. This is already discussed in another post, but I will put here for reference.
1. Grab a working copy of TWRP for the Honor 8 here: https://forum.xda-developers.com/showpost.php?p=70893767&postcount=408
2. Download TWRP into the same folder you used in step A above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP. This is a crazy process because of the encryption on the Data partition. Below is the exact steps I can confirm works from the help of others on here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Once here, you can download root checker and it will verify you have root access - BUT.. see section D below!
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
Some applications like Root Checker will verify that you have root. Other applications will even prompt you (like any of the basic quick reboot apps that easily let you back into recovery) but other major apps like BusyBox and Viper4Audio (when asking to load the driver) will simply fail upon installation. I'm not sure why, since you have R/W access to both the system and the newly unencrypted data partition. I'm really hoping someone can help with this one!
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
I know and have done A, B, and C, but as for the rest I'm not too sure about those.
Maybe in the wrong section but thank you.
joesee said:
14. It will format data using make_ext4fs..
Click to expand...
Click to collapse
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
joesee said:
15. When finished, tap Reboot System
Click to expand...
Click to collapse
When I wipe then reboot I get stuck in the bootup screen
EDIT； Nevermind I just didn't wait long enough for my phone to boot up
KevinN206 said:
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
Click to expand...
Click to collapse
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
faizalotai said:
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
Click to expand...
Click to collapse
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
KevinN206 said:
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
Click to expand...
Click to collapse
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
faizalotai said:
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
Click to expand...
Click to collapse
I am afraid of running into this issue from a fellow xda. The person still doesn't have a solution. https://forum.xda-developers.com/mate-8/help/encrypted-data-mount-t3537645
I'm running into issues with Bluetooth activation, and previously NFC, which i fixed by reflashing the hw_update package, but still no Bluetooth.
I've followed each and every single step on this guide, and BT was working perfectly before.
Any ideas where this may be coming from ?
Still, thanks or the guide
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Hello. Im coming from general topic on Honor 8 rooting but my issue is related to Android MM.
So i had stock EMUI 4.1 (Android 6.0) which i unlocked, flashed TWRP and SuperSU.
Today EMUI 5 (Android 7 ) update came by air so i installed it. After update - no TWPR neither SuperSU.
I enabled Developer options and saw "Enable OEM unlock" switch in OFF state and grayed out (impossible to switch ON).
So now i cannot flash TWPR as fastboot gives error "Command not allowed".
During boot phone says that it is unlocked, FRP lock. Otherwise it boots and works fine but no root.
Any solution possible?
Thank you.
Telperion said:
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Click to expand...
Click to collapse
can u please tell more or make a step by step tutorial on rooting? I'm stuck in rooting, when I format data and boot agai into recovery and flash su It still ends with error 1, dnt know which error it is..
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Is there any way to do this without rooting?
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
ajmdrh said:
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Click to expand...
Click to collapse
Update to latest TWRP and try again
Shehzaan said:
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
Click to expand...
Click to collapse
Indian version?? Frd-l02?
venugopalu007 said:
Indian version?? Frd-l02?
Click to expand...
Click to collapse
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Shehzaan said:
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Click to expand...
Click to collapse
Yes, it is middle east variant
PalakMi said:
Yes, it is middle east variant
Click to expand...
Click to collapse
Do you have any idea how can I get EMUI 5.0 without rooting?
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
cnjax said:
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Yes, that is why i gave them credit. However, It is more noob friendly and takes the time to explain what they are doing to their own phones as well as give them the option for nougat or oreo, something that none of the other guides have.
Ok, so I did it sucessfully, it's was still very complicated for me as some info is vague for a beginner. But after searching and retrying, and retrying, it worked. but go to runningnak3d post to get more info, and he wanted me to use sd card to root, but that did not work for me.. Your method worked for me. Thanks
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming....
Click to expand...
Click to collapse
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
clsA said:
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
Click to expand...
Click to collapse
alright, thank you so much for the advice! 1. i don't want to switch to bullets because when i was trying runningnak3d's guide, it seemed overwhelming. also people can comment on the step number that they were lost at. 2. i will change the kdz to something else if the file does change. i did in fact mention the battery pull step, if you ever need to find something in a page, hit control and f and then search the page.. i will add the 32 bit file. Thanks!
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available
. . .
this guide would not have been possible without users runningnak3d and clsA
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
W O W . . .
What a way to rip-off runningnak3d's guide.
I mean, I can understand rewriting it... I did the same. But, just to parse it out for me to follow better.
But your statement "...there was no root guides available..." is just BS.
Below is my guide... for me to do the process.
Creation date on the text file was November 7, 2017. Just over a week after runningnak3d made the original post.
Difference is, I didn't feel the need to post someone else's work, in an attempt to try claiming credit for it, due to nothing more than a "rewrite".
What you meant to do is this: (FIFY)
Cool guide for rooting your LG V20. Works for 20h, too!
--------------------------------------------------------------------------------------------------------------------
Materials:
8+GB microSD Card - formatted exFAT or ext4
LG Up (patched)
C:\Program Files (x86)\LG Electronics\LGUP <- install here, or it won't read DLL correctly
ADB
DirtySanta root package - (No working Link)
H91510e_00_VTR_CA_OP_1205.kdz - http://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz
h910-10r.zip - https://drive.google.com/open?id=1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X
- Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
Terminal Emulator APK
Root Checker APK
Settings Database Editor APK
1) Copy h910-10r.zip, SuperSU-v2.82.ZIP, SuperSU.Pro.APK, Terminal Emulator, Root Checker, and Settings Database Editor to microSD Card and insert into phone.
2) Put phone into download mode (power off / hold vol. up & plug in USB cable)
Use LG UP to dump phone. When you run it, there will be additional radio buttons.
- Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck "userdata".
3) When finished with the Dump, click the PARTITION DL radio button, pick the H915 v10e KDZ, and click start. Make sure all partitions are checked.
- Select H91510e_00_VTR_CA_OP_1205.kdz, Tick box to set as input file.
- Select all partitions
- Confirm all partition changes
- Once it is complete, phone will reboot into old Freedom Mobile ROM
- Disconnect USB Cable
- Complete Android setup, and you may not have signal (this is normal).
- Enable developer mode, and enable USB debugging.
- Enable Unknown Sources
- Connect USB Cable
- Make sure that your PC is authorized (tick always allow, and then OK).
4) Install Terminal Emulator for Android -- NOT Termux.
5) Extract root kit somewhere that you can run adb and fastboot from.
6) Open [2] Command Prompts in the directory containing ADB.EXE.
A) In first window, execute: adb logcat -s dirtysanta
B) In the secxond window, excute: STEP1.BAT
- Wait until prompt returns (several minutes)
C) Window 2: run-as con
D) Window 2: chmod 0777 /storage/emulated/0/*
E) Open Terminal Emulator on phone, enter: applypatch /system/bin/atd /storage/emulated/0/dirtysanta
- Watch window 1. Wait for "Finished. Please run Step 2 now."
F) Window 2: "exit"
- Window 2. "exit" again.
- STEP2.BAT (adb reboot bootloader)
- Phone now shows FASTBOOT MODE
G) STEP3.BAT
- This flashes TWRP and WW 2.0 kernal
- Phone will reboot on completion
7) If phone reboots to Android, in Window 2 execute: adb reboot recovery
- If phone is stuck at secure start-up, pull battery and boot into TWRP (same as factory reset)
8) In TWRP:
A) Settings: UN-Check Enable Screen timeout
B) Format Data (type "yes" to proceed)
C) Wipe Cache & Dalvic Cache
D) Install (flash) h910-10r.zip
E) Install (flash) SuperSU-v2.82.zip
F) Format Data
G) Reboot Phone
Problem Occured:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
SheMi363 said:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
Click to expand...
Click to collapse
This "run-as con chmod 0777 /storage/emulated/0/*" actually is a two commands:
- first type "run-as con" and press ENTER
- second type "chmod 0777 /storage/emulated/0/*" and press ENTER
Search in You Tube for "How to Root install TWRP for LG V20 H910 Edition!" from user NewTechBegins. This is very good video tutorial, step by step.
Hello, so nothing happens for me after I enter the code into terminal emulator, what am I missing?
After all these done I'm rebooted to secure start-up where I need to enter password. Tried my 4 digit VIN and didn't work. As suggested earlier in this thread I pulled battery and wipe everything and install Oreo_full_rooted.zip, mk2000, and TWRP 3.3.1-0. It boots up the same to the secure start-up.
I might have done differently in process.
1. H91510e_00_VTR_CA_OP_1205.kdz I downloaded did NOT match MD5 on its download page. Tried twice and it was the same. I went ahead and used it.
2. I ran into "adb server is out of date, killing.." message but was able to download an adbfix and somehow got through
3. STEP1.BAT and the rest of BAT were not accepted in Win10 powershell so I had to enter them by hand and it went smoothly with no error
4. I used twrp 3.3.1-0 as suggested in NewTechBegins' youtube clip
5. Phone boots into scramble messages like shattered warning sign before LG logo appeals. It will eventually enter twrp or secure start-up after some wait. Takes longer than it should, 5 minutes or so.
Wish to stay on Oreo but might try the 10R Rom if I have no other choice.
Please help.
(Secure start-up appeared the first time after step 3 where it was supposedly be a green screen and I can pull battery. It didn't. It went to secure start-up. I pulled battery anyways and rebooted into TWRP, I was asked to enter password again. After a few wrong attempts I was able to bypass it and enter TWRP to proceed with install)
edit: Eventually succeed by not installing TWRP after flashing OREO and MK2000. Rebooted into Secured Start-up again, pull battery and rebooted into FACTORY Recovery and deleted all user data from there. Rebooted and Android setup began.
Note: BE SURE TO FORMAT DATA AGAIN in TWRP after flashing OREO and MK2000 to have a clean start. Would be nice if it was mentioned in this tutorial.
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
hey reply to me fast is it ok to flash h915 firmware in my h910 10I cuz already hard bricked the previous h918 motherboard cuz I don't know I accidentally flashed h990 firmware plz tell me also is it necessary to flash h915 in h910 to root and TWRP.
Isn't that what it says in the OP?
pakwarrior said:
hey reply to me fast is it ok to flash h915 firmware in my h910 10I ....
Click to expand...
Click to collapse
MaverickNextDoor said:
Isn't that what it says in the OP?
Click to expand...
Click to collapse
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
pakwarrior said:
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
Click to expand...
Click to collapse
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
jxsilicon9 said:
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
Click to expand...
Click to collapse
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
pakwarrior said:
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
Click to expand...
Click to collapse
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
jxsilicon9 said:
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
Click to expand...
Click to collapse
no no need to downgrade anything just find any video which says TWRP installation for LG v20 h910 dirty Santa and flash it but wait I seen in all zip files of dirty Santa there will a final step in that folder called step 3 that file is a batch file just open it in notepad and you will see there is written TWRP for I think us995 just rename it all of them to that name which TWRP in that folder ok for example if the name of the TWRP in dirty Santa folder is twrph910.img
you have to rewrite the same and exact name with .img in that batch file this ting will not tell any YouTuber or in the website cuz, I find it in curiosity and founded that the TWRP name was wrong so I just renamed it in that batch file and it worked before it it wasn't working also download the exact LG v20 h910 TWRP, not any other model TWRP or you will hard brick it man it feels so bad I one time hard bricked my LG next day I bought the device now I just sold it I change the mobo to LG h910 then I did all that root things and then I sell that phone no I have sony xz3 which is way better and have snapdragon 845 octa-core which is the thing I needed in just 135$ I found that it was japan model refurbished but has all things new and original like poled panel and stuff... well if you need more help just don't reply m on XDA you will not get the answer quickly here my social media account
discord: PAKWARRIOR#6115
Facebook: https://www.facebook.com/hafiz.saad.712161/
Instagram: https://www.instagram.com/zero_saad_sixs/
reply me on that I am online all the time but not online on XDA all the time ok
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Lgv20usr said:
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Click to expand...
Click to collapse
Re-flash the H91510e_00_VTR_CA_OP_1205.kdz with LG UP. And again.