Related
I know a couple people asked for a guide and I didn't see anything concise had been posted (Mods feel free to remove if it's a duplicate.). Things are still a bit fresh, but this should be a short list of steps to perform the upgrade of your Nexus 7 (2012) WiFi to Lollipop.
As with other guides, I make no expressed or implied warranties - you break it, it's on you.
This is how I was able to get Lollipop working on my own Nexus 7 (2012). I was coming from a rooted factory image of 4.4.4.4 which was the previous most-recent factory image released by Google for this device. I like my device as bone stock as possible and wanted to upgrade and keep it that way.
I assume the following:
You know how to use both adb and fastboot and have already configured your system to use these utilities.
You have already performed an oem unlock on your device.
That out of the way, on to the guide...
It goes without saying, but I'll call it out anyway... Take a backup of your current device setup. Most likely this is within your custom recovery or TiBu. If your not familiar with how to do so, consult the help pages for those apps.
Download & unpack the requisite files
LRX21P factory image from Google.
CF-Auto-Root from Chainfire.
OPTIONAL Only if you're upgrading from a version of Android prior to the JWR66Y Android 4.3 factory image, download the KRT16S factory image from Google.
Start by rebooting your device to the bootloader.
Code:
$ adb reboot bootloader
OPTIONAL If you have ignored my assumption and haven't already done so, now would be the time to oem unlock the bootloader
Code:
$ fastboot oem unlock
Run the following commands to prep your device to install Android L. NOTE:This will erase your device
Code:
$ fastboot erase cache
$ fastboot erase recovery
$ fastboot erase system
$ fastboot erase userdata
OPTIONAL If you are upgrading from a version of Android prior to the 4.23 bootloader release which was originally released along with the Android 4.3 JWR66Y factory image, then you will need to upgrade the bootloader also. The bootloader included in the Android L factory image is not correct and will fail to install. Your best bet is to download the KRT16S factory image from Google and use the bootloader-grouper-4.23.img file from that factory image. Be sure whatever version of the bootloader-grouper-4.23.img file you use has the correct md5sum.
Code:
$ md5sum nakasi-krt16s/bootloader-grouper-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 nakasi-krt16s/bootloader-grouper-4.23.img
$ fastboot erase boot
$ fastboot flash bootloader nakasi-krt16s/bootloader-grouper-4.23.img
Now, install the actual Android L system
Code:
$ fastboot -w update image-nakasi-lrx21p.zip
Your device will automatically reboot at this point and when it does, you will be running Android L (5.0) 100% stock and WITHOUT ROOT. This boot usually takes a very long time (~5-10 minutes) as it's performing the initial setup of the OS. When the device is back up fully, you will have to go through the setup steps as if it were a new device. Once that's done, proceed to the next step.
Now that Android L is freshly-installed, not only have you lost root, but you've also lost the Developer Options menu and the USB Debugging option contained therein. So, before we proceed, we need to enable Developer options & USB Debugging in the settings menu so that adb & fastboot will work recognize the device. Again, if you have any experience with running adb & fastboot, you will know how to do this. The process is exactly the same as with previous versions, so there should not be any surprises here.
Go to the Settings menu and scroll down to and tap on "About Tablet"
On the next screen tap on the "Build Number" field seven (7) times and you'll be presented with a message of "You're now a Developer!"
Hit the back "triangle" and go into the Developer Options menu and turn on USB Debugging.
Just be sure to accept the key on your device when you connect it to your computer.
Now, we can use adb to reboot the device so we can apply the CF-Auto-Root patches and SuperSU from the bootloader
Code:
$ adb reboot bootloader
Once in the bootloader you will need to apply the cf-auto-root. Use the following command.
Code:
$ fastboot boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
NOTE: Windows users have reported that the file is in the same directory so just double-check the path to the file.
This will boot the device onto a custom kernel, install the kernel fix to allow root and also install the latest beta version of SuperSU (2.20) for Android L.
You will now end up with a device running Android L with root. I did not mention at any point about installing a custom recovery. These steps will remove a custom recovery, so if you want to install that, you will need to consult the instructions for your custom recovery of choice. I usually use the CM instructions for installing CWM as they're easy to find. This is not strictly necessary for root. Similarly, my main purpose for rooting was to use Titanium Backup. The current production version of TiBu doesn't support Android L, but the TiBu team has released a test version for L via their twitter feed. Here's a direct link or you can go to their twitter feed for more info...
Questions? Comments? Did I miss something? Let me know.
EDIT: Seems that the performance has really gone down over the past few days. Not really sure what the cause of the performance degradation is but it's quite severe. I noticed last night after having left it plugged in all night that the device wouldn't even turn on or took an inordinately long amount of time (many minutes) to wake from sleep. As it stands I attempted to play a game that's slightly intensive and after a short period of time the device got really hot and started really having performance issues to the point where it rebooted on it's own. Further, I noticed a number of things aren't working that probably should... Bluetooth & "Battery Saver" mode are the first two that come to mind.
Anyone else experiencing similar issues?
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
petenatas said:
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
Click to expand...
Click to collapse
Would you mind pointing me to it?
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
jasoraso said:
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
Click to expand...
Click to collapse
added
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
Click to expand...
Click to collapse
Not sure about on Windows, but on Linux when I unzipped the root zip file, there was a directory layout as such...
Code:
cf-auto-root/
cf-auto-root/image/
cf-auto-root/image/CF-Auto-Root-grouper-nakasi-nexus7.img
cf-auto-root/root-linux.sh
cf-auto-root/root-mac.sh
cf-auto-root/root-windows.bat
cf-auto-root/tools/
cf-auto-root/tools/AdbWinApi.dll
cf-auto-root/tools/AdbWinUsbApi.dll
cf-auto-root/tools/fastboot-linux
cf-auto-root/tools/fastboot-mac
cf-auto-root/tools/fastboot-windows.exe
In any case, you were able to find it. Should be pretty obvious which file I'm referring to...
apocope said:
Would you mind pointing me to it?
Click to expand...
Click to collapse
Added a link in the paragraph at the end.
Yes!
I needed my root. (The stock kernel underclocks like crazy, making the tablet nearly unusable.)
Thanks for the guide brother. You are awesome
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
A very very very very usefull guide!!!!
All working fine!!!!
Thanks!!!!!!!
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
OMG corrupted bootloader AGAIN.
GOOGLE what's wrong with you???
Thanks for the guide! Works fantastically on my aging N7.
Short rundown video by me on YouTube here:
Does it wipe internal storage?
abobobilly said:
Thanks for the guide brother. You are awesome
Click to expand...
Click to collapse
:good:
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
Click to expand...
Click to collapse
:good::good:
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
Click to expand...
Click to collapse
I made a mistake on the version number that I listed in my instructions. When I did my N7, I had originally just tried flashing SuperSU via the standard zip file method. The most recent version of SuperSU available in the SuperSU XDA thread is/was 2.19, so I just assumed that it was the same version being used in the CF-Auto-Root. But as you correctly point out, the process installs 2.20 not 2.19. I updated the version number in the guide. Thanks.
ToucherCD said:
Does it wipe internal storage?
Click to expand...
Click to collapse
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
Added a link to the KRT16S factory image which contains a proper bootloader-grouper-4.23.img file that you could use.
jetsaredim said:
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
Click to expand...
Click to collapse
Hi. Good job on the guide. Very detailed. That's good.
Thanks for the tip with booting CFautoroot img. I was wandering why superSU 2.16 was not working and was looking for modified karnel all morning.
BTW. I know it's not recommended, even my Tapatalk signature says it
but I didn't wipe user data while upgrading. See my post here with details.
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Can I just ask about the bootloader?
I'm seeing alot of users reporting there's an issue within the bootloader that is included on the LRX21P image for Grouper, I performed a clean flash yesterday and flashed the leaked image for grouper, I haven't had any single issue flashing all of the images, even bootloader that came from the lollipop image doesn't seem to cause an issue.
Btw, everyone's suggesting to flash the bootloader from JB & KK on this lollipop build, is there any impact on the performance of why's that recommended to flash the old bootloader?
And I didn't really expect this but lollipop made it worst to run on this device! Even if it's a 2012 device, why's that it can't handle lollipop smoothly? I can't even drop the status bar down at a rate of 60fps as promised by Google, can't even swipe the screen smoothly and it's freezing as hell! It feels like something's wrong with this build.
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
JovieBrett said:
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
Click to expand...
Click to collapse
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Natakranta said:
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Click to expand...
Click to collapse
Yup, I all agree of what have you said. I tried ext4, f2fs etc etc, none of them improves the N7's performance or at least the stock one has the best performance and stability for me.
Heard alot of users blaiming about the tegra chip for this, they said that tegra chips are getting worst every year and if all of these are true, I have doubts about Nexus 9's performance since even the one of the famous 'Android Police' senior editors have found that there are unusual freezes and glitches from the device itself, idk if that happened on the latest build for N9.
The 2011 device I'm currently comparing to is an Xperia Mini, snapdragon chip with 1Ghz single core, 512MB of RAM, I'll look away from tegra based devices...
Btw, do you have an N7 2013? I'm planning to buy one this December to replace my 2011 device. Can I trust this 2013 model with snapdragon processor? I always trust these snapdragon based devices.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Google Nexus 6[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I'm new to Nexus 6, where do I find a thread with guides and useful information?[/SIZE]The sticky roll up thread in the general forum has all of the guides and important information. You can find that HERE.
[SIZE=+1]Q2: Where can I find tools such as USB drivers[/SIZE]You can find the universal Google driver inside of the Android SDK found HERE. Or you can install ADB/fastboot and universal drivers from HERE.
[SIZE=+1]Q3: What does "flashing" my phone mean?[/SIZE]Well, there are a couple of meanings here. "Flashing" a custom ROM means to overwrite your current OS with a new one. "Flashing" can also mean, changing from a carrier to a pre-paid carrier. Example: I need to flash my phone from AT&T to Cricket.
[SIZE=+1]Q4: Bootloader.. What is this?[/SIZE]For an easy explanation of what a bootloader is, look HERE.
The most recent bootloader and radio can be found here : Here is a recovery flashable zip of the 6.0.1 bootloader and 32r radio
[SIZE=+1]Q5: How do I root my device?[/SIZE]There are a few options. The most recommended way is to unlock your bootloader, flash custom recovery, flash superSU zip, install superSU app. Also there are more automated methods, such as toolkits and auto root. HERE is a great place to get that information.
[SIZE=+1]Q6: What is a factory image?[/SIZE]A factory image for Nexus devices is provided directly from Google. They are used to return your device to the state it was in when it was put in the box. They can be found HERE.
Most recent is 6.0.1 (MMB29Q)
[SIZE=+1]Q7: How do I backup my device in case I bork it?[/SIZE]TWRP recovery has the feature of allowing you to backup your device. It is highly recommended to backup your stock image after installing TWRP and before flashing anything else. Simply use the backup option in TWRP. Think of this as a restore point to go back to when things get borked. Also, you can backup all of your files to your PC before beginning the root process because unlocking your bootloader will wipe your device. There are also apps available that will back up your apps and app data Titanium Backup is a great choice if you already have root. Helium is an option for non-rooted users.
Latest recovery is [RECOVERY][shamu] TWRP 3.0.0-0 touch recovery [2016-02-06]
[SIZE=+1]Q8: How do I flash a factory image?[/SIZE]Flashing a factory image is a fairly easy process. You can use the fastboot method or a toolkit. Toolkits can be found in the development section and an excellent guide to the fastboot method can be found HERE.
[SIZE=+1]Q9: Do the carrier versions matter in deciding on root or ROM?[/SIZE]No. there are no carrier specific ROMs or root methods. There are only two versions of the Nexus 6, Domestic (XT1103) and international (XT1100). Device wiki can be found HERE.. Bootloader unlock method is universal as well.
[SIZE=+1]Q10: What is encryption and should I disable it?[/SIZE]First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out.
[SIZE=+1]Q11: What are fastboot and ADB and should I learn how to use them?[/SIZE]You should absolutely have at least some knowledge of fastboot and ADB. These simple yet powerful tools can save you from trouble and do wonders for your device. The basic principles and commands are extremely easy to learn and thankfully, there are plenty of guides that will help you understand and learn how to use them. Fastboot and ADB aren't exclusive to Nexus either, you can use them with Android as a whole. You can find my favorite guide to using fastboot and ADB right HERE.
[SIZE=+1]Q12: Can I install an OTA if I'm rooted/unencrypted?[/SIZE]No. Since the onset of lollipop, absolutely no system or boot img modifications can be present in order for the OTA to flash. HERE is a thread dedicated to OTA related Q&A and instructions for sideloading. HERE is a thread for OTA files available for sideloading.
[SIZE=+1]Q13: What is a toolkit and should I use one?[/SIZE]First, a toolkit is a program that auto runs and makes changes to your android device. Those changes can be very significant and difficult to recover from when things go wrong. With a toolkit, you can obtain root, return to stock, flash recovery, etc. However, once you start to run the program, you have no idea what is happening to your device. It comes highly recommended to have the basic knowledge of ADB and fastboot even if you are using toolkits. So, should you use one? Sure! No one will tell you not to try, just know what you're getting into and that most experienced users will not use them at all. Therefore, you are more likely to get helped quickly if you have a basic understanding of fastboot, and a tested and working fastboot/ADB environment on your PC, should an issue arise where you need help. Toolkits are absolutely awesome and highly useful in some situations, so don't underestimate their usefulness. It is just that with a Nexus, and a few simple fastboot commands, you can obtain root, return to stock, flash recovery, etc. While typing those commands, you can be 100% certain of what is happening to your device.
[SIZE=+1]Q14: What is CMTE(cyanogenmod theme engine?[/SIZE]Here is a better explanation here And please take note, This is only supported by ROMS that has already adopted CMTE instead of Layers.
[SIZE=+1]Q15: What is Layers (RRO)?[/SIZE]Layers is a extension of runtime resource overlay.
RRO is a framework created by sony for use as a way for them to create xperia themes but also for internal quick prototyping. More explaination from the original thread here. And take note, this is only going to work with ROMs that has adopted to use layers instead of CMTE. Stock roms natively support layers. Just need to download necessary apps and your good to go.
[SIZE=+1]Q16: Systemless Root?[/SIZE]A new way of getting root without modifying /system. More news here.
[SIZE=+1]Q17: Android Pay?[/SIZE]If your running stock and not rooted, no doubt its gonna work out of the box. There was a previous discussion on how to run the feature on rooted devices. It was fun while it lasted. And here is the latest story about android pay.
[SIZE=+1]Q18: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]Look HERE for a detailed guide on how to use XDA Search to it's fullest capabilities.*
And here are some terms to ponder
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Click to expand...
Click to collapse
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
Click to expand...
Click to collapse
This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Ask any question/Noob friendly: http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
General question and off topic: http://forum.xda-developers.com/nexus-6/general/google-nexus-6-t3077130
Otherwise, create a new post here: http://forum.xda-developers.com/nexus-6/help
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Excellent suggestion, I will get something together tomorrow. Thank you.
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
rootSU said:
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
Click to expand...
Click to collapse
Done. Thanks!
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Done, thanks again.
rootSU said:
One day we'll rebel
Click to expand...
Click to collapse
Question 18 added to build the rebel forces.
Question 19 added.
Question 20 seems to be a frequent flyer.
Thread has been cleaned per OP request.
Please only post questions with answers, you feel would help your fellow Nexus 6 user.
All other conversion... please bring to a new thread or the lounge:good: Keeping in mind this is not a Q&A thread.
Thank you @Evolution_Tech for continued updates.
Questions 21 and 22 added since we have a new update.
Question 23...toolkits.
Post #2 updated with links to general help threads.
cam30era said:
@Evolution_Tech,
While responding to a thread this morning, I was "asked" to change to the New 2015 XDA thread view (web view). Not sure I like it, but that's not why I'm here. What's the difference between "commenting" on a post and "posting a reply"?
Update: Weirder still, some on the comments aren't even viewable in the XDA Premium app. Just shows a web link....... @danarama 's Black Screen thread.
Click to expand...
Click to collapse
I specifically chose a new template for that thread which allows answers to be "up voted" as you may have seen on many technical sites, most prominently, Microsoft technet.
The apps can't handle it so they make you use a browser.
Reply is an answer or solution. Comments are to a particular answer, so for example, I can say "tried that" without creating a response that is seen as a votable answer.
Question #24 added. How to use XDA Search.
updates coming.. stay tuned
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Any version will work but all marshmallow builds are unified and 29q is the latest factory image
MassiveDynam1c said:
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Click to expand...
Click to collapse
this is not q&a thread. this is for the most common FAQ's..
but to answer ur question. go with 29q. this is the latest stock firmware .
how did u ever got 29u as a stock rom? thats the latest aosp. nexus 6 never had a 29u stock firmeware
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Shplad said:
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Click to expand...
Click to collapse
see the index for correct safestrap version, 3.75 is latest, but you need the Droid 4 one
[INDEX] Development Motorola Droid 4
GApps are android version specific, opengapps.org are good
I haven't used the Droid 4 much since cm11, it's likely still a good option
sd_shadow's How-To Videos for Droid 4
Sent from my XT1254 using XDA Labs
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
The link for safe strap is not dead there are two versions. One from stargo and the other is a modified safe strap for unused partitions redone by some one else. You need to look in the correct posts and thread. Here is the download: http://www.internauta37.altervista....afestrap-maserati-v3.75-unused-partitions.apk
As far as for gsm keep looking you'll probully find something. I can't help you with that because I never needed to use but it shouldn't be to hard to do or figure out.
As far as wich rom you want to use just try a few different ones and see wich one you prefer to use as a daily driver.
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
moodroid said:
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
Click to expand...
Click to collapse
Shplad said:
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
Click to expand...
Click to collapse
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
moodroid said:
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Click to expand...
Click to collapse
Shplad said:
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
Click to expand...
Click to collapse
As far as I understand it (which could be totally wrong), 11 and 12 are no longer being developed and will only receive security updates, so from that point of view, I guess they will be more stable. But 13 and 14 will work, but there may be the odd issue here and there (particularly with 14 which is still quite new). You'd have to have a quick scan through the comments to see if there's anything that's like to be a problem for you.
With reagrds to GSM, I should just try it and see if it works to begin with. If it doesn't, then download the patch, reboot, go into safestrap, install the zip then reboot.
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provides superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Wow, this is a lot to take in. Thanks. So, I don't quite understand the repercussions. Once I root, does that mean any ROM OS that boots is somewhat more vulnerable, cause it's like being logged on as root in Linux, or does it depend which ROM I'm using or something else?
Bobcus Leper said:
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provided superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Click to expand...
Click to collapse
Okay, I figured out after my last post that root status depends on which ROM you are running, and of course installing a ROM without root status would put you back to unrooted status.
I downloaded Lineage OS 13 and verified the MD5SUM. I rooted the phone using Shadow's video.
Now I want to make an image of my NAND or have some other method of restoring the stock ROM before I install a new ROM. At what stage in the process do I do that and what is the safest tool / method to do that? RSDLite? Adding another ROM slot and using Nandroid backup?
Awaiting anxiously...
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Shplad said:
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Click to expand...
Click to collapse
As far as I understand it, and again, this could be wrong, using RSDLite is usually a last resort in the unlikely event that you've completely messed up your phone. You will lose everything, and your phone will back to how it was when you bought it. I've never needed to use RSDLite myself, but from what I've read, it's a pretty reliable way to get your phone working again. As long as you follow all the instructions, and install CM (LOS) 13 into another slot, it's very unlikely that you'll damage your original stock rom and you'll still be able to boot into if ever you need to. Hopefully, someone who knows more about it will comment also...
I got Safestrap 3.75 special version for unused partitions installed. I didn't realize it allows you to make TWRP ROM backups.
I made a backup of the stock ROM. The first time I did that, I got an error stating it couldn't find or access /boot.
Strangely, the second time I tried, it seemed to work fine.
I copied the folder with the stock ROM backup to my PC, just in case. I managed to flash with Lineage OS 13. It booted fine, but I forgot to select the Gapps zip as well. It does not appear to be rooted after bootup.
1. Do I need to reinstall Lineage 13 or is there way to install the apps without reinstalling Lineage?
2. What is the normal state of this ROM? I'm not sure if I have to root Lineage 13. If I don't enable root, will I be unable to run TWRP recovery and add the Gapps zip file and reinstall? I don't want to be stuck with a successful Lineage install and no apps. I'd find another way to install the apps, but I'm guessing you can't without the apps themselves, no?
Help!
Okay, I figured out how to install just gapps 5.1-2015-05-23-24 . However, during configuration, I cannot get the phone to connect to gmail via WiFi (I don't have a data plan).
"Validating Server Settings...
Couldn't open connection to server."
I see other people had this in other version of Android. Is this a particular problem in Lineage 13? Any solutions known?
...AAAANDDD Google Play Services has closed.
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
EDIT:
I tried these suggestions, just in case.
https://productforums.google.com/forum/#!topic/gmail/ACSvDiQoufI
Now, I'm getting the error:
"Problem with account setup
Username or password is incorrect"
Google Play Services keeps closing. Should I uninstall the gapps and install a more compatible one? I think network connectivity is not stable.
Shplad said:
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
Click to expand...
Click to collapse
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
moodroid said:
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
Click to expand...
Click to collapse
Shplad said:
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
Click to expand...
Click to collapse
I meant on this website. In the 'Droid 4 Android Development' section (https://forum.xda-developers.com/droid-4/development), there a thread for each of the roms. The one for CM (LOS) 13 is https://forum.xda-developers.com/droid-4/development/cm13-0-marshmallow-unofficial-builds-t3270938
moo:
Thanks for that. I didn't post there earlier because I thought it was only for developer reports of bugs, and my coding skills are exactly zero. Should I wait to see what happens in that other thread and not post back here until I hear something from there?
I've heard people claim it's 64bit. zcpu isn't saying, and antutu benchmark says 64bit. Wikpedia and motorola/lenovo sites aren't saying. Who are saying it's 32bit and what's their source for this?
If it's true, does that mean that there has to be a full wipe of the apps/data during an upgrade to oreo, or would that only be true if the version of oreo was 64 bit, and that a 32bit upgrade from nougat to orea would be ok?
Please post a reasonable source when replying; i've seem talk either way, and i'm interested in THE answer, not AN answer.
Webern said:
I've heard people claim it's 64bit. zcpu isn't saying, and antutu benchmark says 64bit. Wikpedia and motorola/lenovo sites aren't saying. Who are saying it's 32bit and what's their source for this?
If it's true, does that mean that there has to be a full wipe of the apps/data during an upgrade to oreo, or would that only be true if the version of oreo was 64 bit, and that a 32bit upgrade from nougat to orea would be ok?
Please post a reasonable source when replying; i've seem talk either way, and i'm interested in THE answer, not AN answer.
Click to expand...
Click to collapse
Our phones are 64 bit. Stock software runs in 32 bit mode for Sanders. Oreo custom roms are 64bit for our phone for what's currently available.
Sent from my XT1806 using Tapatalk
treyweez11 said:
Our phones are 64 bit. Stock software runs in 32 bit mode for Sanders. Oreo custom roms are 64bit for our phone for what's currently available.
Click to expand...
Click to collapse
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Webern said:
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Click to expand...
Click to collapse
it's a bad idea to switch rom without a full wipe, i never managed to get a working installation without that
if you wait for motorola's official update instead, that will probably work and keep your data
Webern said:
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Click to expand...
Click to collapse
That my friend is a food question. You should do clean flash any way when flashing different ROMs but you won't know until you try. Some people restore their data that way.
Sent from my XT1806 using Tapatalk
My question is about the stock Oreo update only.
Webern said:
My question is about the stock Oreo update only.
Click to expand...
Click to collapse
there is no stock oreo update at the moment, and nobody knows when it will be released
as it is not out yet, you question cannot have an univocal answer
apparently it will eventually be released as motorola declared about one year ago, but some people, including myself, start to doubt it
btw, normally, no further or previous actions (such as wiping data) are required when installing an official update
i'd rather back up all my files anyway before upgrading, just in case
ElKorki said:
there is no stock oreo update at the moment, and nobody knows when it will be released
as it is not out yet, you question cannot have an univocal answer
apparently it will eventually be released as motorola declared about one year ago, but some people, including myself, start to doubt it
btw, normally, no further or previous actions (such as wiping data) are required when installing an official update
i'd rather back up all my files anyway before upgrading, just in case
Click to expand...
Click to collapse
I know that normally you don't have to wipe/reset the device when updating stock, and I know that normally you wipe when flashing different hobbyist roms, and I know there's no release date for Oreo yet. All great facts and I really appreciate the attempt at helping but none of this addresses my question. I'll try again as I obviously wasn't clear enough:
1) Is this device running 32 bit Nougat?
2) Does/Can there exist anywhere a 32 bit Oreo?
3) If the answers are Yes and No respectively, does that mean that in order to upgrade from 32 bit Nougat to 64 bit Oreo a full wipe of app and user data is required?
Webern said:
I know that normally you don't have to wipe/reset the device when updating stock, and I know that normally you wipe when flashing different hobbyist roms, and I know there's no release date for Oreo yet. All great facts and I really appreciate the attempt at helping but none of this addresses my question. I'll try again as I obviously wasn't clear enough:
1) Is this device running 32 bit Nougat?
2) Does/Can there exist anywhere a 32 bit Oreo?
3) If the answers are Yes and No respectively, does that mean that in order to upgrade from 32 bit Nougat to 64 bit Oreo a full wipe of app and user data is required?
Click to expand...
Click to collapse
ok, i'll try to be more schematic
1) yes it is
2) yes, oreo can be 32 or 64 bit. ATM there are no 32 bit oreo custom roms for our device and nobody knows what version will be the official update
2b) all already oreo updated motorola phones run 64bit android, so probably also g5splus ore update will be 64bit
3) nobody can know the exact answer to your question because the update has not been released yet, so nobody could test it yet.
these are my thoughts on the subject:
- the architecture has nothing to do with data partition: only binaries are specific to a processor architecture, not data.
- a full wipe is strongly advised because between different roms there can have differences in folder structure.
- official update is expected to keep your data intact and to takes care of any possible data structure divergencies under the hood during installation
anyway, on lenovo official forum i found this thread
https://forums.lenovo.com/t5/Moto-G5S-Moto-G5S-Plus/Help-Android-Oreo-32-or-64-bit/td-p/3986111
which suggests that your fears are realistic
so i'm no longer very confident about the "taking care under the hood" possibility...
Here you go!
So, the processor is of x64 but stock latest Oreo rom is running on 32-bit mode.
Moto g5s plus is 32-bit
Yes Motorola Moto g5splus is a 32-bit. Checked now on antutu it does says 32-bit, one more proof is the fortnight installer. Fortnight you can't install on Moto g5splus and if you see installers requirements it says OS 64-bit so that's too a one more proof of that.
I've read all the threads and all the replies but it's just a bunch of people talking in circles giving directions that do not work.
They like to say things like "make sure to download the correct twrp version for your firmware" but don't say how to tell which is the correct version because the twrp site sure doesn't.
I'm stock rooted on the latest android 10 release G973FXXS9DTL1
thanks for any help
im sure by correct twrp version they mean if your device has exynos or snapdragon....you can download to check here
Device Info: System & CPU Info - Apps on Google Play
View details of CPU, RAM, OS, Sensors, Storage, Display, Camera, Battery, Apps
play.google.com
lets start there