Database Info

3 doubts about flashing CWM and EOS ROM

Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.

All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2

wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...

NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you

Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted

I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2

NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2

You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.

Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

Good luck...
Sent from my MZ601 using Tapatalk 2

Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!

Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2

wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?

Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2

wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.

NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.

Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?

I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).

Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)

Hi all.
A few days ago I entered the Xoom forum asking about how to modify an "unaltered" Spanish/European Xoom (Wifi Only, MZ604) running stock Android Honeycomb (3.2) and flash a custom ROM with Android 4.1.1 (JellyBean), so that I don't have to wait Motorola to release the updates (still in Honeycomb in Europe, while in US they're enjoying JB), and to enjoy the extras that custom ROMs offer (root, overclocking, etc).
Xda users "wesamothman" and "Cubanluke88" answered quickly to my question and this allowed me to unlock my Xoom bootloader, install TWRP Recovery and flash EOS3 ROM (JellyBean for Xoom from TEAM EOS). The results are awesome; the change from Honeycomb to Jellybean, plus the totally stable overclocking at 1.2 and even 1.4 Ghz is worth the fact that you void the Xoom warranty by doing this procedure. It's like having a brand new tablet.
As I found some problems/mistakes in the procedure I was given, I've created a new "Guide for Noobs" (based on wesamothman's) so that anybody can reproduce the same steps and convert an European Xoom (Wifi Model, MZ604) into a modern EOS3-powered Xoom.
NOTE: I initially wrote this tutorial using the EOS-RECOVERY-6.IMG as the CWM Recovery software to install in the Recovery Partition. The recommended recovery software now is TWRP so I've updated the tutorial replacing the download links and filename.img to flash. The procedure remains the same, although I really tested and executed it with eos-recovery-6, not with TWRP. Anyway, it is supposed to be flashed and work the same way than I initially described it.
NOTE THAT THIS PROCEDURE IS FOR EOS3 - (EOS NIGHTLY <= v155).
EOS4 (nightly >= v156) requires a slightly different procedure!!!
Please, remember that by unlocking the bootloader (and flashing non official software) you're voiding the device warranty and that I'm not responsible of any damage that your device can suffer. I'm just explaining how I did the unlocking+flashing to convert my SLOW XOOM in a fully working JellyBean system. Remember also that this procedure is for WIFI ONLY Xooms. 3g xooms need a different rom/procedure.
So, sumarizing, that's what we are going to do:
a.- Unlock the "bootloader" of the Motorola Xoom so that we can "install" custom software in both the "recovery" and the "data" partitions. Please notice that by unlocking the bootloader you void the device warranty.
b.- Flash TWRP software into the recovery partition, (I was flashing EOS-Recovery-v6 software initially but now is deprecated and TWRP must be used) so that we can launch this software pressing a combination of keys during power-on. This software will allow us to make full backup/restore of the device memory, and to install any ROM (EOS2, EOS3, cyanogenmod, EDGE, etc) in the system. Thanks to this recovery we are safe against problems in the O.S. (even if we break it), because we can always recover from backup or flash a new ROM (including the "stock" ROM, I mean, the ROM shipped oficially with the device) and solve the situation.
c.- Once recovery is installed, do a NANDROID backup of the NAND of our device, to have a copy of the "stock" system.
d.- From Recovery, flash the desired ROM (EOS3 in my case) and the Google Apps applications (they can't be included inside the ROM for legal reasons, so they are flashed separately) to the "data" particion.
e.- Restart and enjoy our new system (you can also made another NANDROID backup to save this "working point" for the future).
Steps a). and b). need a working computer with Linux, Windows or Mac. After doing b).- you can do everything from the Xoom itself and you don't need the computer anymore. After doing b)., you'll be able to download ROM images directly under your Xoom in the uSD card and reflash any new ROM directly rebooting the tablet into recovery-mode.
Steps a) and b) can be done from Linux, Windows and Mac. Although I have Linux in my laptop, I found that almost all the tutorials in Internet explain the procedure under Windows so I installed temporary a Windows system to do the "PC dependant" steps, because I didn't want to experiment with the "risky" actions in both steps.
So, let's start with the "PC dependant" actions, which includes steps a). and b).
I'll try to update the thread with screenshots in the future, as I didn't take photos/screenshots of the procedure, I'll check images.google.com to find something that fits the text, and add the later to the tutorial if they are really needed.
PART 1 .- HOW TO INSTALL TWRP RECOVERY:
Here we are going to unlock our Xoom and install a custom recovery software into the recovery partition. The recovery software is launched when you start your Xoom in recovery mode, and this is achieved by pushing Power, VolUP and VolDown key combinations when you power-on the tablet (we'll see how later).
So we'll replace the original "recovery" software by a custom one that allows us to flash NON OFFICIAL software to the data partition.
To do that, first we have to download all the required software in the Xoom enternal uSD card and prepare our PC system to recognize and work with the Xoom. We have to download:
Get the Motorola USB drivers for your system: http://developer.motorola.com/docstools/USB_Drivers/ . This step is only needed under Windows, so that the Windows System recognizes the Xoom and the Android SDK binaries (adb and fastboot) can send data to the tablet. Check that you're downloading the right drivers (32 or 64 bits) for your 32 or 64 bits System, and install them. If the Android SDK in your Linux system can recognize the Xoom, you're ready to use Linux also to do the following steps.
Download and Install in your PC the lastest JavaSE JDK from Oracle's website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download and install the Android SDK for your system: http://developer.android.com/sdk/index.html .
Download the EOS v155 ROM and GoogleAPPS for that version. My final choose was EOS3 ROM Wingray (Jellybean for Xoom), and installed v155 from the nightly compilations (which is the latest nightly in Android 4.1, being v156+ Android 4.2). "Nightly" means that as the software is still not "final version" (it's still in development) a new version is released almost everyday, correcting bugs or adding new features. I personally didn't found any bug in v155 but you can check the EOS3 thread in XDA to check that the latest version has no bugs reported by people in that thread.
ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ (as of date September-2012 - I recommend v141 )
GAPPS: Latest: http://teameos.org/gapps/wingray (I used http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip for v155).
EOS3 THREAD: http://forum.xda-developers.com/showthread.php?t=1764751
And the most important, download TWRP the "recovery software" that will allow you to work without the need of the PC (I was using Team Eos Recovery 6 initially, but now is deprecated and TWRP must be used):
Team Win Recovery Project 2.x, (TWRP): http://forum.xda-developers.com/showthread.php?t=1782235
You should download the IMG file (example: R.A.H.v3_TWRPv2.5.0.img). Check that the size of the downloaded file matches the size that is shown in the above link. This is the most important file because it will allow to install the recovery system and it's CRITICAL that the file is not corrupted..
Steps:
a.- Install in your PC the Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
This will download and install the packages needed so that we can access the Xoom from the PC for "flashing" data purposes; mainly "adb" and "fastboot". Adb allows us to work with the xoom started in the Android System, and fastboot allows us to work with the xoom started in fastboot mode, which is the mode we'll use to "flash" the recovery software.
b.- Enable USB debugging in the XOOM (in settings, development), so that we can use adb with the tablet.
c.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
d.- Plug the Xoom to your PC.
e.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices". You should see that the system identifies your Xoom with a long numbers+letters string. If you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device, so that the system can bind the right USB drivers we installed to that concrete device.
After a While, Windows will fix it and re-executing "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
Now, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup. Fastboot mode is a special bootmode in the xoom that allows the PC to send data to the Xoom and "write" to Recovery and Data partitions. You can also enter that mode starting the Xoom with "Power+Volume Up" pressed simultaneously.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
{
"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"
}
(Photo: fastboot mode, taken from google images)
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because Windows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot".
Issue the following command to unlock the Xoom (you'll void the warranty). If you don't unlock the xoom, data and recovery partitions will be "read only" and you can't send the "new software" to them.
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option. The device will ask you twice if you are sure that you want to unlock the device and void the warranty, and then it will make a "factory reset" of the O.S. .
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc. Enable again "USB debugging" and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the recovery file (the name may vary, with something like R.A.H.v3_TWRPv2.5.0.img) to the android-sdk/platform-tools/ folder with name "recovery.img" and execute:
Code:
fastboot flash recovery recovery.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery recovery.img
sending 'recovery' (XXXXX KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
Now disconnect the USB cable and enter recovery mode with:
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
And you'll start the TWRP Recovery recovery system. If you see the standard Android recovery system instead of TWRP recovery, you can repeat the above "fastboot flash recovery recovery.img". You don't have to unlock the bootloader again, just flash the recovery software and reboot again in recovery mode with "fastboot reboot" and "adb reboot recovery".
(Photo: my Xoom in EOS6 recovery mode, TWRP is different, with better controls and more features )
You can start recovery mode also manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE TWRP RECOVERY
How to enter in recovery mode:
A.- Manually:
- Turn Xoom off.
- Press Power to turn Xoom on.
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
b.- From "adb" in a PC system with Android running on the tablet connected to that PC:
Executing "adb reboot recovery"
c.- With a custom ROM, selecting "reboot" will ask you if you want a normal reboot or a recovery-reboot.
How to use recovery mode:
Use the Volume Up and Volume Down keys to move between options and Power button to select an Option:
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
Available options for a basic CWM / recovery are:
Reboot system now -> exit Recovery mode.
install zip from sdcard -> allows to install ZIPs to data partitions such as ROMs.
wipe data/factory reset -> delete all the contents in the data partition (needed before flashing a ROM)
wipe cache partition -> delete cache partition.
backup and restore -> allows doing "nandroid" backups and restore of our system (FULL MEMORY BACKUPS).
mounts and storage -> allows to mount aditional media to save/read data.
advanced -> extra options.
(Photo: Nandroid backup)
NOTE: TWRP is newer than the OLD EOS-recovery-6, the above capture and options may differ.
PART 3 .- HOW TO INSTALL EOS3 ROM:
Now we've installed recovery, so we don't need the PC anymore. We can enter in recovery mode at any moment and do backup/restores, flash new roms, flash updates, etc.
To install EOS3 ROM (or any other "full install" -not update- ROM, do):
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Install gmail, youtube, etc from Market (not included anymore in gapps).
Enjoy your new rom!
PART 4 .- HOW TO UPDATE EOS3 ROM or install a new different ROM:
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the new rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Enjoy your new rom!
I hope this can help people to unlock their xooms.
Thanks to "wesamothman" and "Cubanluke88" for the initial support given and specially to EOS Team and the people that created ClockWorkMod for sharing their time, work and knowledge with us. They've converted my "slow xoom" in a very powerfull and fully functional tablet.

Couldn't expect less from you. Super great guide...
Sent from my MZ601 using Tapatalk 2

Post reserved for updates in case the initial post gets too large...

I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
Sent from my Xoom using Tapatalk 2

Thanks for your words...
In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".
Thanks.
--
Sent from my Xoom with EOS3 ROM using Tapatalk 2

Updated with some pictures

Updated with links to v141...

eos 6 recovery.img not available
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial

kakrikakri said:
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
Click to expand...
Click to collapse
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.

NoP_Compiler said:
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
Click to expand...
Click to collapse
wow that was a quick reply.. THANKS (Y)

kakrikakri said:
wow that was a quick reply.. THANKS (Y)
Click to expand...
Click to collapse
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).
I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").

Same method for stock ics?
Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?
Thanks !

Help !!! In a lot of trouble
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!

kakrikakri said:
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
Click to expand...
Click to collapse
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard

wesamothman said:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
Click to expand...
Click to collapse
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
First time ROM flashing is longer than normal booting, like 5 min ,
If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
Did you finally succeded "booting" EOS3?

NoP_Compiler said:
Did you finally succeded "booting" EOS3?
Click to expand...
Click to collapse
Yes it did and it works perfectly
Thank you NoP_Compiler and wesamothman
Sent from my Xoom using xda app-developers app

Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup

dead android in step 2
Hi,
Thanks for the great tutorial.
I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"
In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.
Any idea about what I might be missing?
thanks!

[HOW TO] Beginner's Guide to Flashing & Fun on the A700 (Root, ROMs, Etc.)

Installing ROMS & Such on the A700/701
For Extreme A700/Android Neophytes
Read It All BEFORE Beginning!​
Important Links:
http://forum.xda-developers.com/showthread.php?t=1710755 ← Unlock Bootloader
http://forum.xda-developers.com/showthread.php?t=1791165 ← CWM
http://forum.xda-developers.com/showthread.php?t=1806980 ← CM10 Official Thread
http://forum.xda-developers.com/showthread.php?t=2056964 ← CM10.1 Official Thread
http://forum.xda-developers.com/showthread.php?t=2489708 ← CM10.2 Official Thread
-----http://get.cm/?device=a700 ← CM10 Download
-----http://goo.im/gapps ← Google Apps 4.1.2
http://forum.xda-developers.com/showthread.php?t=1995981 ← AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=1952124 ← iconiaN
http://forum.xda-developers.com/showthread.php?t=1953917 ← Vorbeth’s EasyRoot ← Do This to Root!
http://forum.xda-developers.com/showthread.php?t=2004441 ← Vorbeth’s OC GPU Kernel
http://forum.xda-developers.com/showthread.php?t=1994294 ← CoolOne700
http://forum.xda-developers.com/showthread.php?t=2196266 ← IcOdiv for A701 & A700 based on CyanogenMod 10.1
http://forum.xda-developers.com/showthread.php?t=2219575 ← Evil Alex Purgatory A701
http://forum.xda-developers.com/showthread.php?t=2232411 ← 7comp based on RootBox
http://forum.xda-developers.com/showthread.php?t=2510004 ← Official PAC-man 4.3
Software You Will Use/Need (depending on your root method):
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318 ← Acer USB Drivers
http://developer.android.com/sdk/index.html ← Android SDK
General Information:
First off, this was never made adequately clear for new users (without going through a hundred different posts with hundreds of replies): You will be using the Android SDK and the Windows Command Prompt. When installing the Android SDK, change the directory to something easy like C:\SDK because you will be typing it a lot. The directory in that folder you will be using exclusively for this process is the “platform-tools” directory. This is where adb and fastboot are found.
In addition, you will need to activate ADB Debugging on your tablet. This is found by going to Settings -> Developer Options -> USB Debugging. If this isn’t done, you will get nothing accomplished. Yes, you will need to have your tablet connected through USB to your PC for this to work. I know there are other ways, but I’m writing this with brand new users in mind.
After you’ve got that set, you should go ahead and install the Acer USB Drivers. None of my computers could properly identify the tablet without the drivers. Speaking of quirks, 64GB microsd cards are not generally very friendly with CM10 or CWM even when formatted as Fat32. There are lots of issues I can’t find a workaround to. Consider using a 32GB until the kinks are worked out.
I’m also assuming you are currently running the JB OTA that was pushed worldwide in October 2012. If you are not, then there are a few extra steps when installing IconiaN. Although I compiled the instructions you’re reading, I had nothing to do with anything else. In fact, I didn’t write the codes used to install things through the command prompt….I just compiled all the information into one easy-ish to follow paper.
As usual, if anything in this causes a brick to your tablet, it was your decision. I’m just providing the information that has worked for me (repeatedly). Also, as I’m not a developer, nor am I very handy with editing files or trouble shooting things without actually handling them…….Ask your specific questions directly to those people in charge of the files (pawitp, Vorbeth, Moscow Desire, meier2009, odiv81 and alx5962). They’re the gurus at this..I am a plebe in their shadow.
TL;DR:
Install Android SDK to an easy directory.
Install Acer USB Drivers.
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
Code:
adb reboot-bootloader
-- Allow the device to reboot.
4. Type Code:
Code:
fastboot oem unlock
5. Press the + Volume button to select Unlock then - Volume button to confirm.
6. Restart :
Code:
fastboot reboot-bootloader
----- I had issues on step 6. I tried that, and it rebooted to the bootloader screen. To be on the safe side without hard rebooting (not knowing what was going on), I used the command from Step 3. to reboot. This works for ICS and for JB bootloaders, I confirm I used the above steps on both.-----​7. Confirmation of your unlocked status will be seen in the upper left hand corner of the screen.
Install Clockwork Mod Recovery: (all work & codes from pawitp)
Somehow I wasn’t able to install this properly (permanently) until last night (11/09/12). I’m still not entirely sure what I did differently, but I’ll try to document it here. The safest version of CWM is 6.0.1.5. Don’t attempt anything without that version or better. I’ve heard that at this time the touch version isn’t working properly, so be sure to download the original style CWM.
To navigate CWM, the following bit of information will come in handy (especially if you’ve never used it before.) Use the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice. When you have made a choice it will sometimes give a screen with a ton of “NO” options with only one “YES” option (usually near the bottom). Like any good video game, if you scroll upwards, you can get to the bottom of the screen faster.
1. Place the CWM file you downloaded into your “platform-tools” directory. For the sake of being easy to install, I changed the file name to ‘recovery.img.’
2. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
3. Plug your tablet into your computer through USB.
4. At the command prompt, enter the following:
Code:
fastboot flash recovery recovery.img
5. At this point, you have flashed CWM to the system, BUT you will now need to boot into CWM using :
Code:
fastboot boot recovery.img
The caveat here is that you will need to install either a custom ROM or unencumbered boot.img (kernel) NOW. If you do not install one, flashing CWM was pointless because stock recovery will overwrite it at next reboot. When prompted at reboot (leaving CWM after flashing a ROM) you should choose to keep CWM. This was sort of a miscommunication between the devs and myself, but meier2009 and Moscow Desire cleared it up.
-----Step 5. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory.-----​
For Future Reference: Enter recovery…(JB):
a. With system powered off, press and hold ‘Power’ and ‘Vol -‘
b. When the system vibrates, release the ‘Power’ button.
c. When the system vibrates a second time, slide your finger from ‘Vol-‘ to ‘Vol+.”
d. When the system vibrates a third time, release that button.
Install pawitp’s CM10.1 OR IcOdiv (A701): (all work & codes from pawitp)
Download the CM10 nightly from the official Cyanogen page and grab the Google Apps file (optional, but you won’t have market without it) listed in the links section. Despite what people say, I have always been unable to install from my external SD card. Instead, I save the zip files to the root/main directory of the internal SD. Save BOTH FILES to internal SD at this time. This has always worked for me, but your mileage may vary. You do this at your own risk, blah, blah, blah.
1. Boot your A700 into CWM using the steps outlined in Step 5. (or 6) from “Install Clockwork Recovery Mod.”
2. Backup your system by navigating to “backup and restore” by using the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice.
3. At this point, there are two options for you. “backup” and “backup to external_sdcard”…. I have never been able to mount my 64GB Fat32 external_sd in CWM. Try a smaller card if you have one available (I don’t). If you can backup to external, that is probably necessary when coming from stock. I would only backup to internal if you are just updating from an older nightly or previous rom.
4. On the main screen, assuming you’re coming from stock JB or ICS, you will need to do a couple of wipes. I’m positive the first is necessary, and have read in other parts of threads and other forums that the other two wipes are needed, but as they’re both called “cache,” I went ahead and did both (with no ill effects).
Select “wipe data/factory reset”
Select “wipe cache partition”
Select “advanced” and navigate to “wipe dalvik cache”
Go back to the main menu.
5. From the main menu, select “install zip from sdcard”.
6. Select “choose zip from sdcard” and scroll down to the CM10 zip file. Press the ‘Power’ button to select and confirm.
After this has successfully installed, you can choose to install Google Apps or not. I’m assuming you will want to install them because…well…who doesn’t?
7. To install Google Apps, follow Steps 3 and 4 from above, but this time you will choose the gapps zip file instead of the CM10 zip.
8. Reboot Device & Enjoy well sorted Jelly Beans.
Install iconiaN: (all work & codes from Vorbeth)
At the moment this is my favorite. It is one version number (4.1.1) behind CM10 (4.1.2), BUT it is compatible with my SD card, and is similar to the stock experience …. only faster and without the bloatware. The only reason it is second in this guide is because of the alphabet (C before I & P before V).
The latest updates to the ROM bring the latest GAPPS and firmware. meier2009’s 4Way Reboot Mod is also included (and rocks).
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from above if coming from stock JB (or CM10, or CoolOne700) with the exception that you’re installing the iconiaN zip (not CM10, duh). Also, iconiaN comes with v4.2 Google Apps pre-installed, so no need for Step 7.
-----2.a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If coming from an older version of iconiaN, you shouldn’t need to do the wipes, but go ahead and do the backup just to be safe.
4. Reboot Device & Enjoy well sorted Jelly Beans.
-----On a side note, I went ahead and installed BusyBox (https://play.google.com/store/apps/details?id=stericson.busybox) not sure if this was necessary, but I am suffering no ill effects from having it running on my tablet. -----​
Install Vorbeth's OC GPU Kernel: (all work & codes from Vorbeth)
This is a custom kernel (as of this writing available only for the A700) that overclocks the Tegra 3 from 1.3Ghz to 1.5Ghz. There has been a noted improvement in gaming performance using this kernel.
1. Boot your A700 into CWM.
2. From the main menu, select “install zip from sdcard”.
3. Select “choose zip from sdcard” and scroll down to the iconiaN Kernel zip file. Press the ‘Power’ button to select and confirm.
4. Reboot Device PLAY SOME GAMES! WEE!
Install Vorbeth’s EasyRoot: (all work & codes from Vorbeth)
If for some reason you’re happy with stock and just want a very simple way to ROOT, then this is for you. Using this kernel will cause OTA to stop working (or you will have to edit the updater-script) and remove all the file checks. The latest update has made all previous instructions null, and it is now exceedingly easy to install ROOT on your A700. Awesome! Still, this does require an unlocked bootloader.
1. Download and extract the EasyRoot ZIP on your computer.
2. Locate and double click the file 'easyroot.bat'.
3. Follow all onscreen instructions.
4. Profit.
CoolOne700: (all work & codes from meier2009)
This is the new kid on the block. meier2009 has included three different install options in this ROM including Full (rooted stock), Small (all the Acer bloatware removed), and Custom (Choose what you want.) It’s definitely one to keep an eye on. Custom install is very handy. He’s also got his 4Way Reboot Mod which adds all our favorite reboot/recovery features. Sweet! Also, BusyBox and SuperSU are included on install, so you don’t need to worry about that.
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from CM10 Install if coming from stock JB (or CM10, or iconiaN) with the exception that you’re installing the CoolOne700 zip (not CM10, duh). Also, CoolOne700 comes with Google Apps pre-installed, so no need for Step 7.
-----2. a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If updating from an older version of CoolOne700, you won’t need to do any of the wipes, but it is always a great idea to do the backup.
4. Reboot Device & Enjoy well sorted Jelly Beans.

Code:
6. If upon reboot, you hit the old system recovery, you will need to reflash the recovery.img OR just work around it by doing:
Code:
fastboot boot recovery.img
-----Step 6. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory. I had to use this method to install CM10 because I was never able to get CWM to install. Your luck may be different.-----
THAT´s the Trick my Friend !
Install recovery with
Code:
fastboot flash recovery recovery.img
AND THEN
Code:
fastboot boot recovery.img
Install any ROM and if you´re rebooting and asked to FIX Recovery, answer YES, then it will be leaved there !!!
With this way your also able to start CWM Recovery temporary
only use
Code:
fastboot boot recovery.img
then CWM will start, you can flash anything and after that CWM is gone, because the Stock Recovery is always inside the Recovery Partition

Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?

ExtremeRyno said:
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
Click to expand...
Click to collapse
Lost in translation...

ROFLMAO

Added more info last night and have now included the AOSP 4.2 to the links. Keepin' this bumped & updated.

Thanks for posting this excellent How To! I used it to install CM10.
I can confirm the backup to external backup functionality does work with a 8 GB MicroSDHC card. One thing you could do to bypass the external vs internal SD card discussion is to use sideloading. I used it to both install CM10 and the Google Apps and it works nicely. Just select Update through sideload in CWM and then enter 'adb sideload <filename>' on the command line and everything works nicely.
Also for the real beginner you could may be suggest backing up all user applications using Titanium Backup in order to easily restore them after flashing a mod.

Bumping thread back near the top. Lots of people got an A700 for the holiday and it seems many of them are bricking or at least screwing things up using outdated methods or strange new forms of CWM from other forums.
Also, thanks for the info, SanjuroE. Appreciated, and I can honestly say I never knew how to do the sideloading thing. I didn't actually realize that was what it was as on my old tablet (three years ago) sideloading was always in reference to installing from the external SD.

This guide was awesome. Many thanks for this.

I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??

schlex2010 said:
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
Click to expand...
Click to collapse
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.

cfgh said:
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
Click to expand...
Click to collapse
Thanks mate!
I tried another recovery.img and than everything went fine!! :good:

USB driver link is not working.

papars said:
USB driver link is not working.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=58172023
Many files available, including Drivers

I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.

Driver Issues WIN10
goralpm said:
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Click to expand...
Click to collapse
Hi,
I have the same issue and it took me hours to even find a driver from ACER. But even after the installation I cannot get the tablet to work stable. I installed general MTP drivers which gave me access to the "adb reboot-bootloader" command but during the reboot the tablet gets stuck on the Acer logo screen and does not boot into the bootloader. I have to unplug the tablet and only then I get the white text in the top left corner of the screen saying "starting Fastboot USB download protocol". But that is it. I assume that fastboot would use the Acer drivers to access the tablet but I don't have any for windows 10.
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow

realShadow said:
Hi,
... ...
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
Click to expand...
Click to collapse
I had exactly the same problem. The solution was give here: https://forum.xda-developers.com/showthread.php?p=48915118
You don not need Acer driver.
- Wayne

Need help with TF700T with Katkiss 6.0 installed

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....

Lg V20 H910 (up to 20h) (root, twrp, and more!) Noob guide!

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.