[GUIDE][OSPREY] Moto G3 BEGIN: Unlock bootloader, Flash: TWRP, ROM, Root, Boot logo - Moto G 2015 General

Edited Dec 22 -2017 <-- I may not always change this, but this is a work in progress!
[GUIDE][OSPREY] Moto G3 2015 - BEGIN: How to Unlock bootloader, flash TWRP, flash ROM, flash Root, Flash boot logo.
I started this because while trying to explain it to a user I kept running in to old info.
Code:
/*
* Your warranty is now void.
*
* This may destroy your phone. As with any modification to a phone,
* you must be prepared/willing to THROW IT AWAY without thinking twice.
* If you need it or it is your daily driver, don't mess with it.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the suggestions in this guide
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This may well work on Merlin but I don't have one to test.
--> NOTE: I no longer use LineageOS so can't help there. Using AOSP 8. Should be no difference.
1a) Prep - before you do anything, in stock, go to settings/Development Options (which is turned on by tapping /settings/about phone/Build Number about 10 times.)
turn "OEM unlocking" ON
turn Debugging - "USB debugging" ON.
1b) Now! - To do anything, you must unlock your bootloader: This is done by going to the Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
They want you to "Install the Android SDK.". You only need adb and fastboot on your PC (windows or Linux).
Try this guide to get ADB and FASTBOOT onto your computer: https://forum.xda-developers.com/showthread.php?t=2588979
For Ubuntu Linux simply type fastboot on the terminal and if it's missing a command will pop up as to how to add it - simple. same with adb.
ADDITIONAL THOUGHTS: a very helpful user suggested the following additional for unlock bootloader and getting adb and fastboot: @Dave here - see post 34ff.
Dave here said:
Glad it was helpful! Happy to be able to give something back. Here are some links I used...
LineageOS Osprey install guide:
wiki.lineageos.org/devices/osprey/install
LineageOS Using ADB and fastboot guide:
wiki.lineageos.org/adb_fastboot_guide.html
adb & fastboot: I used this link, which was in the LineageOS ADB guide and I think also the Motorola bootloader unlocking instructions:
Mac: dl.google.com/android/repository/platform-tools-latest-darwin.zip
Windows: dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: dl.google.com/android/repository/platform-tools-latest-linux.zip
Lenovo forum: "THERE IS AN ERROR WITH YOUR REQUEST! MOTO G ROOTING PROBLEM!" (it's actually about bootloader unlocking, not rooting):
forums.lenovo.com/t5/MOTO-G-MOTO-G-...EST-MOTO-G-ROOTING-PROBLEM/m-p/3458979#M27009
European Motorola unlocking URLs:
motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
motorola-global-portal-de.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that in step 4.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
-> Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode on your Osprey, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest.
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP. If you get the dead android it means you still have the stock recovery - boot to fastboot and flash TWRP again.
IMMEDIATELY tap Backup and select to put backup on external storage - your SDcard. NOTE - if your SDcard has been converted to "internal storage" you will have to choose "internal storage" (em0). I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
-- > For TWRP BACKUP I use the default settings of "system,data, and boot". Here is a nice article that explains the differences: https://twrp.me/faq/whattobackup.html .
At this point I recommend you boot back into stock and connect your phone to your PC via USB (slide down) and copy that backup in the TWRP folder to your PC. at least once, maybe twice, for safe keeping. You will need this if you wish to test if a problem exists only on a custom ROM but not on the stock ROM. You will also need this if you simply choose to run stock, instead of a custom ROM. Remember, you are now testing ROMs - nothing is certain!
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
Be aware there are some sites out there with logos that don't work on Moto G3.
5. To flash a custom ROM: Download to PC and put it on your SD card. Do same for gapps. (gapps - g-apps - google apps allow you to log in to your google account, use play store, etc. example http://opengapps.org/ (use arm, 7.1, whatever size you wish)(if you're new use full, mini, or micro until you know what you need. If you're on a 1GB phone, consider nano or pico.) )
https://download.lineageos.org/osprey or whatever ROM you want.
http://opengapps.org/ or whatever gapps you want.
Boot to TWRP.
Clean flash:
tap WIPE,
tap advanced, carefully checkmark:
Dalvic/ARTCache,
System,
Data,
Cache,
and then swipe the bottom swipe button. Takes a few sec. This is what makes a "clean flash".
Generally: Don't wipe "internal storage" or SDcard as this is where TWRP stores its backups/nandroids. - I always copy my TWRP backups to PC for safety.
Then back to menu screen and tap Install, select the rom, and swipe and let it do its thing.
Then back and tap Install, select the gapps and swipe to flash it.
THEN, and only then: tap Reboot (if you're at the main menu you also have to tap System to boot from system.)
The install takes 3 min or so before it starts asking questions.
Be sure to choose "Set up as New" or else you get whatever junk is in your google drive. This has cost errors and much time. <-----
6. Root: If you want to use bank apps, PokemonGo, etc, follow these instructions for Magisk:
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
read the whole thread.
- Else go to https://download.chainfire.eu/1019
and download the zip form of Chainfire's SuperSU 2.79 and boot to TWRP and flash (install) it.
Many thanks to @acejavelin for inspiration and information(which I probably shamelessly stole from him), to @squid2 for his installation guide and his version of TWRP, to @Chainfire for the tons of work that continue to go into superSU, to @coolguy_16 for the safetynet/CTS work, and all the many Devs and helpers who make these ROMs possible, and as clean as they are! And to users like you who find bugs and file bug reports! Thank you!
Remember you are working with a Development ROM - a work in progress! (Even stock isn't perfect!!!)
Enjoy!

KrisM22 said:
I started this because while trying to explain it to a user I kept running in to old info.
As with any modification to a phone, you must be prepared/willing to throw it away without thinking twice. If you need it or it is your daily driver. don't mess with it. It is YOUR responsibility alone. If you break your phone, I will laugh.
1) To do anything, you must unlock your bootloader: This is done by going to a Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that later.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
a) you need to have fastboot support on your PC
Try this guide: https://forum.xda-developers.com/showthread.php?t=2588979
You do not need to put the whole SDK on as s9ome guides would have you do.
Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest - twrp-osprey-3.1.0-r1.img
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP.
IMMEDIATELY tap Backup and select to put backup in internal (em0) storage. I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
5. To flash a custom ROM: Put it on your SD card. Boot to TWRP.
Clean flash: tap WIPE, tap advanced, carefully select Dalvic, Data, System, Cache, and then swip the bottom swipe thing. Takes a few sec. This is what makess a "clean flash".
Then back to menu screen and install, select the rom, and swipe and let it do its thing.
Then back and select gapps and flash it.
Then do supersu and flash that (optional)
Then "reboot".
6. Root:
Click to expand...
Click to collapse
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk

save1

save2

Subins Mani(Tintumonn) said:
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks - hopefully it will help.

A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.

KrisM22 said:
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
Click to expand...
Click to collapse
Yes you are correct, gapps won't get removed for new builds of the same ROM due to a persistent ROM script. However flashing a ROM different than the one currently installed usually ignores such scripts and does a clean wipe. Doing a manual wipe just to be sure is fine, even needed sometimes.
I just wanted to point out that not performing a factory reset (twrp>wipe>swipe to factory reset) can leave potential conflicting files in aforementioned places which can cause unexpected behaviours ranging from FCs to bootloop. The potential issues are rare but I think you know how much trouble it can bring to folks trying to capture real bugs (thanks for hard work at Linage ); it was all about removing the potential factors .
Broadcasted from Zeta Reticuli

The TWRP wipe-swipe does Data, Cache, and Dalvic. That's what I used to do. After messing up some tests this past week and wasting a lot of time, I now recommend adding system to that:
In advanced, checking data, cache, and dalvic/ARTcache, and, now, system. as far as i can see, I am leaving nothing other than internal storage and sd card (and of course whatever is in OTG if there's one attached). TBPro puts its backups on "internal storage". By the way I do appreciate your taking the time to look so closely at this!

KrisM22 said:
[GUIDE]
6. Root: Go to http://www.theandroidsoul.com/supersu-2-79-zip-apk-download/
and download the zip form of Chainfire's SuperSU 2.79 . Use it in step5 above.
NOTES: this has nothing to do with rooting your stock ROM which afaik can't be done.
Click to expand...
Click to collapse
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
Edit: Not necessary anymore, just flash SuperSU zip and you're done
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).

xMotoDA said:
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
Click to expand...
Click to collapse
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not since SuperSU 2.79 - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!

KrisM22 said:
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not after SuperSU 2.78 (or 2.70 or something) - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
Click to expand...
Click to collapse
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.

acejavelin said:
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
Click to expand...
Click to collapse
Huge thanks for that!!! Changed above post.
Never played with Magisk - others (you!) are the authority on that. I think some were saying that was a way to get a custom rom to pass safteynet... Thanks!
Huge thanks for looking in!!!

edited/updated 5-4-17

Problem!
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!

GermanRodriguez said:
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
Click to expand...
Click to collapse
This is possibly a problem with that rom - ask at that thread.
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
or
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845

edited...

edited

update

changed.

Related

OXYGEN OS(Download link ,installation guide & Issues)

Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
DO UNZIP your ZIP before flashing!!! installation ZIP is in ZIP file provided
Plain Aosp Rom
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
manishsharma17 said:
Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Click to expand...
Click to collapse
OMG!!! Is this a Dream???? Is this real?
CM version?
manish.kumar86 said:
CM version?
Click to expand...
Click to collapse
its not based on Cm its based on AOSP its 5.0.2
Yash Kanchhal said:
So when we are factory resetting the phone in recovery is it the same thing like wiping the other thing (cache, dalvik cache etc). I'm new in this so I'm not able to understand that please help me in this & when is the CM12S coming anyone knows?????
Sent from my A0001
Click to expand...
Click to collapse
TWRP has an option for factory reset ...
There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon
Yash Kanchhal said:
Ohk thnx mate it means wiping is every thing????? Right ????
Sent from my A0001
Click to expand...
Click to collapse
yes sir ..use the option of factory reset in twrp and you should be good
timmaaa said:
There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon
Click to expand...
Click to collapse
When i created the thread the thread was not there in present form
manishsharma17 said:
When i created the thread the thread was not there in present form
Click to expand...
Click to collapse
Unfortunately it looks like he created his first.
Transmitted via Bacon
Nice spam indeed. Three threads, three posts, three times begging for thanks. Bah.
Can you add my guide thread to the OP please?
http://forum.xda-developers.com/oneplus-one/general/guide-how-to-install-oxygenos-t3072500
Word of caution! I backuped on the internal sd. Had all my backups of os's and app data completely wiped. Never checked the wipe internal sd box. Use and external backup.
Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?
cyberon said:
Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?
Click to expand...
Click to collapse
Getting neither of those. Main problem I'm having is major Google Play Services drain. It's the same bug we had on CM12 nightlies some time ago and my phone is permanently awake
Sent from my A0001 using Tapatalk
Hello, due to having a similar topic here http://forum.xda-developers.com/oneplus-one/general/oxygen-os-released-download-t3072259, I will have to close this thread.
Please continue the discussion in the one linked.
Regards

Updating To MM from LP (Moto X Pure)

So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment

[VK810.4G] [altev] most reliable way to root and install a custom recovery

Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On the tablet, download the Stump app from http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.
2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.
3. Launch the Stump app.
4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.
5. Choose "Grind".
6. Choose "Brute Force".
7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.
8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".
Credit and much thanks to @Chainfire !!!
9. Launch SuperSU, confirm the prompt to update binaries.
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
1. On the tablet, download the "VK810_twrp_2.7.0.1.zip" from http://forum.xda-developers.com/showthread.php?t=2726707
Credit and thanks teamwin , @Drgravy , @djrbliss , @Dees_Troy , @id10terror and @traccdma !
The link is in the "DOWNLOAD" section below the "DISCLAIMER" towards the bottom of the first post.
Credit @Drgravy for the original instructions but I prefer to run the commands directly on the device instead of from a PC via USB Cable and ADB.
2. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
3. Install "X-plore File Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en
Credit and thanks Lonely Cat Games!
4. While you're in the Play Store, install "Terminal Emulator for Android" https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
5. Launch X-plore.
6. Enable root mode in X-plore:
6A. Click the three-dot menu button in X-plore's upper right corner.
6B. Choose "Configuration".
6C. In the "Root access" section, click the gray area below it and choose "Superuser + mount writable".
6D. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up. It might not open this prompt until a later step when you actually access root.​
7. Find the "VK810_twrp_2.7.0.1.zip" file you downloaded in step 1 above. It should be on your internal storage in the Download folder.
8. Click once on the zip file - this will show you the files contained in it.
9. Navigate to the other file manager pane by choosing "SWITCH PANE" in the upper right corner.
10. Choose "Internal storage".
11. Navigate to the original pane by choosing "SWITCH PANE" again.
12. Select all the files inside the zip.
13. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
14. Now navigate to root. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up.
15. From root, navigate to data/local/tmp.
16. "SWITCH PANE" to where you extracted the files from the zip.
17. Select "loki_flash" and "twrp.lok".
18. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
19. Launch "Terminal Emulator" installed in step 4 above.
20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
reboot recovery
Instead of "reboot recovery" you can use an app such as "Quick Reboot" from the Play Store at https://play.google.com/store/apps/details?id=phongit.quickreboot to reboot to recovery.
21. For getting to custom recovery with the tablet off, press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock-looking recovery and you can let go of both buttons). "Factory Reset" will no longer perform a Factory Reset. That's what you choose to get into custom recovery.
22. Update to to the latest TWRP v2.8.7.0 that you downloaded in step 2 above by (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
You can put a different custom recovery on the same way.
23. You can reboot into the newer TWRP by choosing the reboot recovery option.
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
Flash to the latest stock ROM so that you can have it with root:
1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.​
3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
Thanks to @JBurch/cry for the monetary motivation to finally put this all together in one place!
There are THREE variants of the G Pad 8.3: The Verizon VK810.4G which has LTE, and the V500 and V510 WIFI-only models. These instructions are ONLY for the VK810.4G.
Please don't quote the whole OP.
FAQ: If you use files meant for anything else other than the VK810, you'll brick your tablet. This will be exhibited by the tablet showing up in Windows' Device Manager under "Other devices" as "QHSUSB-BULK". You will have to Google for "QHSUSB-BULK" to find out how to fix that. I've read about some having success doing so and others not. I haven't ever had to fix that so I have no personal experience with it and can only lead you to Google about it.
This requires a Windows PC, preferably Windows 7 or newer, to first downgrade your VK810 variant of the G Pad 8.3 to LG build 11A / Jellybean 4.4.2, to make it easiest to root and to put a custom recovery on.
Disclaimer: I am not responsible for whatever you do to your device. This is my preferred method and what I recommend.
Note: These instructions are still working in order to downgrade from official stock release 36B on the VK810 (codename "altev"), Verizon LG G Pad 8.3 LTE, to official stock release 11A in order to make it easiest to both root and install TWRP. You can then install any ROM you like including my newest stock ROM in my signature at the bottom of this post.
Downgrading/resetting to 100% official stock unrooted release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On a Windows PC, preferably with Windows 7 or higher, download the latest Verizon-LG driver at http://www.lg.com/us/support-mobile/lg-LGVK810 (current version 4.0.3, direct download link if still working http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00520120427).
2. Install the driver.
3. Reboot the PC.
4. While you're continuing to follow the rest of the directions, might as well get the installed driver "loaded":
4A. Put the VK810 in Download mode:
4A1. Preferably using the original USB cable, or alternatively possibly a high-quality cable, connect the one end preferably to a USB 2.0 port on your Windows PC. Note: not all, but most USB 3.0 ports (to avoid for this process under normal circumstances) are blue in color whereas USB 2.0 ports are usually black.
4A2. Turn the VK810 off (within Android, long press the power button and choose "Power off").
4A3. The following is different from other G Pad 8.3 variants:
4A3a. Press and hold the Up Volume button.
4A3b. While continuing to hold it, insert the tablet end of the USB cable.
4A3c. You should feel the tablet vibrate and you can see a very dim, very faint graphic in the very center of the screen that says "Download Mode":
{
"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"
}
Credit and thanks @sevoan for posting the screenshot at http://forum.xda-developers.com/showthread.php?t=2782066
4A3d. Let go of the Up Volume button.​
4B. Windows may take up to 10 minutes to finish loading the driver you previously installed. Every time you connect any USB device to a new/different USB port on a PC, Windows will have to take a longer loading the driver process.​
5. Download the official stock release 11A KDZ for the VK810: https://www.androidfilehost.com/?fid=23991606952610809 (file name "5. VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside - recommended for both ease of rooting and one less step to install the initial TWRP v2.7.0.1.7z")
If the previous link doesn't work, you can find it in my signature at the bottom of this post.
6. Download and install the free 7-Zip Windows program from ttp://www.7-zip.org"]http://www.7-zip.org[/URL]. Any version should work although you can only install the 64-bit version on 64-bit versions of Windows.
7. Use 7-Zip to extract the KDZ from the 7-Zip (7z) file downloaded in step 5 above. If you want to extract the 7-Zip on an Android device instead for some reason, use ZArchiver from the Play Store at https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver&hl=en
8. LG Flash Tool 2014:
8A. On the Windows PC, download "LG Flash Tool 2014" from http://forum.xda-developers.com/showthread.php?t=2797190
Credit and thanks @quangnhut123
The MediaFire link is in step "3. Tutorial"
8B. Run "LGFlashTool2014.exe" as Admin: Right-click on "LGFlashTool2014.exe" and choose "Run as administrator". Provide Administrator credentials if necessary. If you get a UAC (User Account Control) prompt, click "Yes".
8C. If the program doesn't run, install the Visual C++ Runtime Library, also available in step "3. Tutorial" at the link in step 8 above, then repeat step 9.
8D. Screenshots also available at the link in step 8.
8E. "Select Type" should already be at the correct default "CDMA". Same for "PhoneMode" is "DIAG" and "Reset time" is "33000".
8F. Click the yellow folder icon to the right of the "Select KDZ file" field and choose the 11A KDZ file extracted from the 7-Zip archive you downloaded in step 5 above.
For reference: "CSE Flash" is what you should normally always use. "CSE Flash" will wipe your user data including your internal storage so be sure to move/copy anything you want to keep that's currently on your internal storage. "Normal Flash" is like a dirty flash. Your device will be restored completely to stock but will keep all of your user data including your internal storage. If you're downgrading stock ROM versions, you can expect "Normal" to result in a device that'll crash. If you do so, you can attempt a "Factory Reset" from the stock recovery (with the device off - long press the power button for 10 or so seconds until the device shuts off - press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock recovery and you can let go of both buttons). "Factory Reset" will of course wipe all user data including Internal Storage.
8G. Click "CSE Flash".
8H. On the "Read Phone Information" dialog which appears, do NOT press the "Read Phone Information" button. This has always crashed for me.
8I. Click "Start".
8J. On the next dialog, you can change the Country and Language if you like - either way doesn't make a difference. Click "OK".
VERY IMPORTANT: Once you click "OK", ignore any error dialogs that pop up. I mean every single one. Don't click any buttons in them, just drag them out of your way if necessary. 99.9% of the time, given enough time the device will be flashed successfully anyway. On the VK810, usually within 20 minutes. For comparison, on the VS985 Verizon LG G3, usually within 10 minutes.​
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=2
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
General thanks to, for my previous experience:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ. http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108
@Revoe for letting us know the availability of the VK810 36B_00 OTA. http://forum.xda-developers.com/lg-g-pad-83/general/verizon-lg-g-pad-8-3-vk810-altev-ota-t3182449
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use. http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1
@rant for giving a link to the official Verizon PDF detailing 35B. http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
@DeanGibson for giving a link to the official Verizon PDF detailing this release. http://forum.xda-developers.com/showpost.php?p=62413430&postcount=2 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-8-17-15.pdf
@Chainfire for SuperSU! http://forum.xda-developers.com/showthread.php?t=1538053
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading.
@xdabbeb for further knowledge about the partitions!
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.
Reserved
Update
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
JBurch/cry said:
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
Click to expand...
Click to collapse
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
@JBurch/cry I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.
I'm debating whether I should write up directions for checking MD5 hashes on Windows too.
So uh ya
roirraW "edor" ehT said:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
Click to expand...
Click to collapse
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
JBurch/cry said:
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
Click to expand...
Click to collapse
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner.
Maybe I'll separate that into two steps to distinguish them.
Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.
Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.
Thank you, I felt so much better using this than some sketch chinese program.
FL4NKENSTEIN said:
Thank you, I felt so much better using this than some sketch chinese program.
Click to expand...
Click to collapse
You're welcome! I know what you mean.
Hey. Not sure if I am posting in the correct thread so apologises if warranted.
I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.
So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.
A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Soundsofsublime said:
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Click to expand...
Click to collapse
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.
Some people have told about an app called "SuperSU Me" (not by @Chainfire) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.
Thanks and you're welcome!
Lost on step 3.20
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Slingb1ade said:
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Click to expand...
Click to collapse
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
How to unlock boot loader anyone suggest me
zaccheo said:
How to unlock boot loader anyone suggest me
Click to expand...
Click to collapse
No one has done it. Someone more knowledgeable than I would have to tackle it.
roirraW "edor" ehT said:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
Click to expand...
Click to collapse
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"
i was typing temp, needed to type tmp.

[Port] [Recovery] BLU DASH M 2 - CTR Carliv Touch Recovery 6.6.1 - Root not required

We have the first port and root for this highly unpopular BLU phone.
BLU DASH M 2 - Carliv Touch Recovery 6.6.1 aka CTR​I have managed to replace the stock recovery and still keep the stock system since there are no customs roms at the moment. The recovery doesn't require you to be rooted but rooting is possible after flashing or booting this rom. Don't fall for the fake Dash files on youtube, I have downloaded them all and they are copies of similar phones and don't work.. This one is ported over from the D070Q by Carliv.
It will not flash a full custom rom but will flash ZIPs so you can root, recover, flash partitions and hopefully pave the way for a TWRP . I do have a TWRP ported over to the BLU Dash M 2 but the touch doesn't work so you can't pass the first swipe screen.
DOWNLOAD from uploadfiles.io @ https://ufile.io/8oc6k​
Instructions
- Make sure to backup any important files, this will wipe your data pics, vids, etc..
- Enable OEM unlock under developer options and power down phone
- Boot to stock recovery by holding PWR + VOL UP
- In recovery choose "Reboot to Bootloader" ( aka fastboot )
- You should now be at a blank screen with Fastboot mode: at the bottom
Open your terminal and type the following code, obviously replacing your paths with the correct ones.
fasboot devices < --- will return a serial number or something to indicate connection is OK
fastboot oem unlock <--- will prompt your phone screen to accept unlock request, chose VOL Up to accept and make sure it says "Unlock pass" at the bottom
For testing only
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
For permanent flash
fastboot flash recovery CTR_6.6.1_BLU_DASH_M2_D090U.img
Don't power down, instead boot in the same recovery
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
Inside CTR select Wipe cache, Dalvik cache, Userdata / Data.
Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
On first reboot it will reboot twice, then boot the stock system as if it was a factory reset.
This now paves the way for root with Magisk. See my post after this for rooting Blu Dash M2.
Enjoy !
RESERVED
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
73Hn said:
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
Click to expand...
Click to collapse
That will not work for root because Magisk needs the original boot rom. I'm sure it worked for you and that's a good start but wiping the partitions in order does work as well, I probably just left something out or got the order wrong. It's important we don't use CTR to patch because then Magisk complains about boot img being aleady patched and doesn't work.
Anyway you get the idea, it took me a few tries as well but in the end I managed to keep all 3 features intact, the stock rom + CTR + root. If you need to start again you don't need the full rom or sp flash, just flashing system.img to sytem partition works to restore everything.
I'm hoping to find the source code to the kernel and make a TWRP with touch working but the CTR is the only thing we have so far. It does flash zips just not full operating systems. It also flashes boot and recovery partitions.
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
73Hn said:
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
Click to expand...
Click to collapse
I think most can figure out Magisk from here, the real hurdle was the lack of a recovery because the stock rom doesn't allow Magisk to be flashed.
Thanks, I already started checking in on it... I'll update here once I get through.
How to Root Blu Dash M 2 with Magisk​
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6​
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
The only thing left do now is find the Blu kernel source code for the M2 so a working TWRP can be compiled from scratch, then any MT6580 rom should be flashable.
Perfectly... Got it working using your same method after reinstalling the firmware... only difference was.
After installing recovery and booting into it, I then installed Magisk via adb sideload.
Confirmed root works.
Thank you very much for your patience and assistance
graciaaas
romish said:
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
Click to expand...
Click to collapse
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
romish said:
We have the first port and root for this highly unpopular BLU phone.
DOWNLOAD from uploadfiles.io @ https://ufile.io/bj9kk​
Enjoy !​
Click to expand...
Click to collapse
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.​
kirito9 said:
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
Click to expand...
Click to collapse
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
romish said:
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
Click to expand...
Click to collapse
Try this one.. if the host tries to replace it with the original let us know and one of the others who have the file will re upload it to another host. I don't feel like signing up anywhere so that is why I use this host.
https://ufile.io/8oc6k
https://ufile.io/8oc6k
https://ufile.io/8oc6k
kevoncrush said:
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
Click to expand...
Click to collapse
All 'ya 'all are welcome . Unfortunately I can't go any further because there is no source for the kernel so TWRP won't work because there is no touch to get past the first screen. Otherwise if it. did slim rom would flash without any problems, its just these older recoveries don't support a few things that TWRP has to make flashing full roms successful. If someone has source files for the BLU Dash M2 let me know.
I'll just let you guys know, I managed to make a pretty good custom rom with root only by deleteing everything but the core OS. I don't recommend this for everyone but I did get rid of just about everything and made this 6.0 more like 4.4 .. I got it to the point where even the phone and SMS didn't work and the google framework was deleted, then slowly began adding my approved versions of apps. Now its totally de googled but again I realize this isn't for everyone. I just wanted a small rom with camera ad GPS and those are working fine for me.
Custom recovery link taken down again
Could someone please upload the custom recovery again?
[Port] [Recovery] BLU DASH M 2
I tried to fast boot as peryour instructions but I get the error: cannot load ' ctr_6.6.1 etc. :crying:
Please try this link, if you have a better locarion to store it please do so and reshare as this link is only valid for 2 days.
ctr_6.6.1_blu_dash_m2_d090u.img
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
If that recovery does not work, try this one. I have two of different sizes and can't remember which one i used.
recovery.img
Download link
Please repost the download link

upgrade to Android Q & keep twrp and data

Ok here's what I did. To keep my data and twrp when upgrading from "P" to " Q".
1. I downloaded the OTA zip file.
2. Extracted it on your phone.
3. Edit the "Flash-all.bat" file
A. Delete "-w" from one of the last command lines.
B. Add "reboot-bootloader"
"fastboot boot twrp-3.2.3.1-marlin.img"
C. Hit "save"
C. Both the above command lines should be right
before the line "echo press any key to exit"
4. Add the twrp.img to the folder with the above extracted contents.
5. Edit "flash-all.sh" to read the same as you have just edited the "flash-all.bat" file. And then hit "save".
6. Compress the extracted file so as to create a .zip file again.
7. Move this .zip file to your PC.
8. Plug up your phone to your PC and make sure android debugging is active.
9. On your PC extract the .zip file you just created.
10. Make sure you have the twrp installer zip on your phone.
11. Go into the extracted .zip file and double click the "flash-all.bat" windows batch file and sit back and wait.
12. When it finishes it will boot up. 1 out 3 times I tried this it booted then immediately rebooted to the stock recovery with an error saying that my data may be corrupt and if I see this message again then perform a factory reset. And gave me to options "try again" and "factory reset". I clicked "try again". It then booted normally.
13. Power off your phone.
14. While holding vol down press and hold power button for a few seconds and then release the power button but NOT the vol down button. This will put you in bootloader mode.
15. Once in bootloader mode it will then boot twrp.
16. Once once twrp loads click install then navigate to the folder you put the twrp installer.zip and flash the installer. 17. Hit "reboot system"
18. Sit back and wait.
19. All your data will remain on the phone. All your settings stayed the same.
***********NOTICE ***********
1. YOUR BOOTLOADER MUST BE UNLOCKED. IF YOU DONT KNOW HOW TO DO THAT THEN YOU SHOULDNT BE ATTEMPTING THIS. ESPECIALLY IF YOU ASK ME HOW TO UNLOCK YOUR BOOTLOADER.
2. I TRIED THIS 3 DIFFERENT TIMES WITH THE SAME RESULTS. I will post pics of the step by step process later. Just wanted to go ahead and get this out there so those of you who know your way around an android could do it.
3. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
I AM NOT RESPONSIBLE FOR YOU F'ING THIS UP AND NOT FOLLOWING INSTRUCTIONS TO A "T".
4. THIS IS RISKY BUT IF YOU FOLLOW INSTRUCTIONS CAREFULLY YOU SHOULD HAVE NO ISSUES.
Im also posting a pic of my about phone to show I am indeed on "Q" and that this worked for me.
Hope you enjoy
Be patient I'll have step by step screen shots posted in a little bit of the process. To maybe make it easier to understand.
Could this work for official android 10
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Did you try flashing magisk?
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
sinkoo1979 said:
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
Click to expand...
Click to collapse
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
johnblundon said:
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
Click to expand...
Click to collapse
no wipes
Flashed through fastboot.
Steps:
flash bootloader
reboot to bootloader
flash radio
reboot to bootloader
flash system
flash vendor
reboot to system
I was missing OTA function in settings.....
it work for me but can't guarantee it will work for everybody. Best way is to try it.
flashed q beta and went back to pie customs roms by flashing bootloader, radio, and vendor (before official q was released). Have to download all apps but internal storage stayed intact.
salpsuc said:
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Click to expand...
Click to collapse
You're welcome. And sure you could do that I would imagine. May be easier but then I would be explaining a method I did not actually try. And that would suck if by chance some ones phone caused world's to collide. I would feel pretty bad about that. Unless the end result was Nancy pelosi shutting up and resigning.
rahil3108 said:
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
Click to expand...
Click to collapse
I did not have root after flashing twrp.... Seems like, looking back, that I tried and seems like it may have said "successful" but it didn't stick upon reboot. But I imagine it's neither here nor there cuz y'all prolly have root by now...

Categories

Resources