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.
Just found out that I have a Mi Mix waiting for me when I get home. I've made a checklist of what I want to do to it to get it setup for my use. I wanted to know if anyone had anything to add or has done any of what I'm planning on.
Unlock Bootloader
This should be relatively simple. I already have my unlock permission and will be using the directions from here: http://en.miui.com/thread-202290-1-1.html
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
I will also follow the top reply to this thread which mentions linking your device to your Mi account before unlocking to prevent errors: https://m.reddit.com/r/Xiaomi/comments/5co8t1/mi_unlock_approval/
Install TWRP
My plan is to follow these instructions: http://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960
This is where I start having questions. I've been out of the rooting and ROMing game for a couple of years. Does anyone recommend rooting with anything other than SuperSU? I'm reading that it was bought by a Chinese company and shouldn't be trusted. I've also read that using Magisk you can have root that is easily turned off. I'll admit I'm pretty lost at the moment when it comes to what Magisk does and how to use it. But if it is the recommended way of doing things I will do the research to learn it.
Flash The EU ROM
I think my plan is to flash this EU ROM which debloats everything and seems to come with gapps and a lot of other nice optimizations: https://xiaomi.eu/community/threads/6-11-10.36056/
My first question is has anyone tried this?
My second question is will I need to reinstall TWRP and re-root? I think I will have to re-TWRP because on the TWRP page there is one version for stock and one for the EU version. I will be on stock first and I can't flash EU until after I flash TWRP. So I think the procedure will have to be:
Flash stock TWRP
Flash EU ROM
Flash EU TWRP
Re-Root?
Turn Off All Battery Optimizations
Don't have a guide for this yet but I'm guessing it's not hard to find. Feel free to reply with one if you have one.
Personalize
Launchers/Themes/Icon Packs/etc. Don't need suggestions here since I already know what I have in mind.
Anything else?
The only other thing I can think of that I might want to install is Xposed. I've never used it and don't know how to install it but I'll learn if I can be convinced that it's something I want.
What else am I missing?
I think right now the biggest thing I'm curious about is if anyone has used the EU ROM and what the procedure is if you use that ROM since there are 2 different versions of TWRP for the Mi Mix. But any other suggestions on what to do with the initial setup or how to make my experience better are welcome. I'd also love to hear about any "gotchas" that aren't mentioned in the guides from people who have actually done it.
Well I took the plunge without waiting for feedback and for anyone who is interested, I'll answer my own questions. Read the posts that I linked in the OP to understand what I'm doing below. I will not cover how to get unlock permission as this has been covered elsewhere.
Unlock Bootloader
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
Click to expand...
Click to collapse
This is not correct. You must install the Dev ROM and connect to WiFi and follow the steps to enable Developer options and login to your Mi account in developer options.
Install TWRP
Before installing TWRP you must update back to the stable ROM. The non-EU version of TWRP will not work with the Dev ROM as of this posting. You can update to the stable ROM using the same steps as updating to the developer ROM. In the TWRP install guide I linked above, I stopped right after step 6 and continued below.
Flash the EU ROM
Instead of flashing SuperSU after installing TWRP, I copied over the EU ROM linked above and flashed that. Then I followed the instructions starting from step 3 of this post to flash SuperSU, Magisk, and suhide: https://www.reddit.com/r/pokemongod...k_v7_systemless_xposed_v866_released/d8d7ziw/
The only change I made is that in between steps 4 and 5, I flashed the EU version of TWRP before continuing because otherwise the touchscreen would not work in TWRP. I used the most recent versions for the SuperSU, Magisk, and suhide and I did not flash Xposed yet but I believe I can do that in the future if I want to.
That's where I'm at now. The rest of my checklist was mostly personal preference so I won't go into that. Hope this helps.
@chimera533
THX for taking the plunge & sharing your results with us.
I'm sure I'll be doing the same once mine arrives, hope you don't mind if I look this way if I have any questions regarding TWRP/Root/etc.....
Thank you for posting this, this is the exact list of what I will be doing when my Mi Mix comes in the mail (C'mon Ibuygou).
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
jim380 said:
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
Click to expand...
Click to collapse
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
It would be nice if you did an edit of your original post, rather than a 'by the way' post below it. It would be much easier to follow the instructions.
I've installed TWRP on multiple phones. The dm-verity stuff is new to me (A xiaomi/MIUI thing I guess),
so the sequence appears to be:
install Official MIUI China developer ROM
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
< Do you reboot now and go back into fastload now? or stay inside TWRP? >
Install EU TWRP
install supersu (again, before you exit TWRP?)
Install Magisk, suhide?
Apologies but I'm away from home at the moment. I'll update the OP with more detail when I have a bit more time. But I'll give you some quick answers below.
install Official MIUI China developer ROM
Remember to log in to your Mi account in the developer options
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
While still in TWRP, install SuperSU in systemless mode.
Boot to system once
Boot back to fastboot and install EU TWRP
Boot to TWRP and install Magisk, suhide
Boot to system and install magisk manager
Got the Mi Mix 128GB overpriced in Thailand, but without any waiting time.
Love your early thread, very helpful.
I also want to get twrp, suhide, magisk and xposed, but I like to stay on the Chinese Dev or official ROM, not xiaomi.eu, because I like the paid themes which are only available on official ROMs.
I've got a MIUI developer account for 4 years, so I can unlock the device directly, being on stable ROM.
Now the steps are a bit unclear for me. Do I understand them correctly?
1. Unlock bootloader
Download and install the developer rom: http://en.miui.com/download-317.html
Create/Login with your MI Account on the device.
Apply for unlocking the bootloader here: http://en.miui.com/unlock/
Install stable ROM if desired
2. Install official TWRP (NON-EU)
Boot into fastboot mode by turning off your device then pressing volume up and power button
Install Minimal ADB and Fastboot on your PC: http://forum.xda-developers.com/showthread.php?t=2317790
Download the correct TWRP image file: https://dl.twrp.me/lithium/twrp-3.0.2-0-lithium.img.html
Copy the twrp file to where minimal adb and fastboot has been installed and rename the twrp file to twrp.img
Open fastboot on your computer and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
3. Install SuperSU in systemless mode
Download newest SuperSU: https://play.google.com/store/apps/details?id=eu.chainfire.supersu / http://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
In ADB shell or TWRP shell, type
Code:
echo SYSTEMLESS=true > /data/.supersu
if you don't already have this file to configure SuperSU to install in systemless mode.
Flash SuperSU.
4. Boot to system
5. Boot into TWRP, install Magisk, suhide, Xposed
suhide: http://forum.xda-developers.com/apps/supersu/suhide-t3450396
systemless xposed 86.2: http://forum.xda-developers.com/attachment.php?attachmentid=3897543&d=1475913773
magisk: http://tiny.cc/latestmagisk
6. Boot to system and install Magistk Manager
magisk manager: http://tiny.cc/latestmanager
7. Install XPosed
chimera533 said:
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
Click to expand...
Click to collapse
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
jim380 said:
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
Click to expand...
Click to collapse
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
underlines said:
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
Click to expand...
Click to collapse
I had a nightmare trying to get to the EU Rom yesterday, I was mostly successful, however after a reboot i'd lose Touch in both TWRP and System. Thanks to this post from Chimera533 I was finally able to do it!
Anyway the main reason for the EU ROM is to get rid of all the Bloat and Chinese throughout the ROM that you cannot get rid of. It also has Google Services baked in properly so everything works correctly.
I also had a few other little niggles while on the Chinese ROM :-
Purchases from Google Play Movies wouldn't work
No Smart Lock while connected to Android Wear
No way to replace BAIDU and set Google as the search
So far i'm loving the EU Rom, i've not seen any lag at all while using it and pretty much everything seems to work exactly as it should - it has enhanced the MIX experience so much for me - love this thing!
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
yakuzlin said:
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
Click to expand...
Click to collapse
Go to the battery section & have a look around, you should find several settings for battery management.
You're gonna need root & an app such as Titanium Backup Pro, or, SD Maid Pro to disable a lot of the MIUI & Cheetah Mobile applications.
Fine tuning on a per app basis isn't enough (do not optimize battery savings for the apps you want to work properly, notifications, messaging, etc) .....
I highly recommend flashing the EU ROM, it seems to have better memory management than the Global ROM, but, you'll still need to disable a lot of the MIUI apps & all of the Cheetah Mobile s***ware to get memory management more to what you're used to experiencing.
One other item, go to Developer Options & disable MIUI Optimization, it should be the last item or close to it....
Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots
reserved
It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.
mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)
good job
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself
Good job man!
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time
You should add that the stereo speakers don't work.
Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?
Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.
I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it
Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...
Hi there. I have the UK varient which is not the same as the us version. I'm looking for info regarding root and custom roms. All info I can find points toward the us (James) varient.
Any info or links greatly appreciated
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
mac_d4di said:
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
Click to expand...
Click to collapse
That's my thread and yes the information is correct.
If you are not sure yourself that the information I have posted is correct, then I suggest you stop thinking about rooting your E5 or flashing custom ROMs.
You have to remember no one has tested the rooting/flashing procedures on PETTYL.
Everything that's listed here on XDA is designed for James/Nora/Hanna devices so no one has tested anything on our devices as it's newer and not many have it.
All the GSIs (custom ROMs) are only listed as working on the James/Nora/Hanna devices, there is currently no support offered for PETTYL, although technically they should work.
The devs of those other devices and the resources for them claim everything should work on our E5 as its treble compatible, but unfortunately that's not quite correct.
If you are really not sure about anything, or don't know if information is correct, you will have problems.
Im not being mean.....I really don't want anyone else to have the problems I have had and really wouldn't advise anyone to go through the process as it's fraught with issues, bad explanations and lacking important information.
Some files are incorrect for our device and some listed procedures for the other devices do not work on our E5.
BTW-my device is an E5 play XT1920-15 PETTYL SIM unlocked purchased from Argos.
Here's a list of the issue I found, it might be different for someone else as two people are saying they successfully rooted their PETTYL, and I couldn't.......
1. I had no issues unlocking the bootloader.
2. There are two versions of TWRP posted on XDA for PETTYL, but neither worked for me.
I used the James version.
3. I could not root my device.
Magisk installed but I could not get v17.3 or v17.2 to flash.
V17.1 did flash but magisk manager showed device not rooted and magisk not installed.
4. Flashing any GSI (Oreo or Pie) causes problems to the system sounds, ringtones, notification tones and music which is totally distorted and very poor quality.
The camera has very poor quality as well.
5. Lineage OS 15.1 is the GO version, you also should flash lineage before flashing other GSIs as you can't flash most GSis over stock.
6. You can use the full Google apps on a couple of android 9 gsis which makes your device a normal android, not an android Go device, but I would recommend not to bother with Android 9.0 GSis for this device as they are very buggy and very slow, and they use three times more battery than android 8.1 Go.
Also, live wallpaper and notification access still don't work on android 9.
Just remember as well the US E5 is much more powerful than our E5, and I assume thats why android 9 runs so crap on our E5.
7. You have a very complicated process to get your Google account working on any GSI, if you do it wrong, you will not be able to use your Google account at all and will get spammed with never ending notification from Google of using an "uncertified device"
8. If you run into problems and decided to return to stock, you cannot download the "retail_GB" stock firmware (SIM unlocked) for PETTYL unless you pay for it....the EE and Tesco SIM locked firmware is free to download, but neither work on the SIM unlocked version if you use non EE or non Tesco SIM cards.
9. Someone has posted a twrp back up of rooted stick for PETTYL.
It did not boot on my device and just kept boot looping.
That could have been a twrp issue and nothing to do with the shared back up - I couldn't get back into a gsi or stock to test it.
My post is warning to other PETTYL users- with my own experience.
What you choose to do is up to you but I really would not bother tampering with it, leave it be.
Stock android Go 8.1 is way better than anything else that's currently available for PETTYL right now, every gsi I tried had an issue of some description that affected performance so badly they were practically unusable.
Even though I'm back on stock now I still have sound issues, and many graphic glitches that makes my screen flash and glitch out randomly.
I'm sorry it's such a long reply, I wanted to give you as much information as possible so you have some idea of what's involved for our device., And let's just hope the situation for our device will get better soon.
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
mac_d4di said:
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
Click to expand...
Click to collapse
Just like you, I've been rooting and flashing phones since like forever, and this device is the first I've ever had issues with.
It's entirety possible that as I'm a "noob" to flashing system images and fastboot flashing as apposed to flashing "ROMs" I may have messed up the procedures or made mistakes.
But not to be outdone, I have just before typing this reply tried again to root my E5 and flash a GSI, and again the process failed for me.
I could not boot into lineage OS 15.1 due to a "decryption error" and also couldn't get twrp to flash anything.
I've read now my issues are down to the DM Verity kernel which seems to be causing a lot of confusion amongst users and It now seems the process to remove forced encryption is what's causing all my issues.
I don't understand the process if I'm honest (it's an age thing lol) and worse, there is a lot of conflicting information, as a few people are saying the DM Verity process isn't necessary!!!
So unfortunately I've given up completely for now and stand by my original advice.
It's best to leave this particular device well alone until we have a proper procedure and tutorial in place for our own devices rather than trying to follow procedures for the US version.
I'm jealous though you only paid £65, as I paid £79.99, but I still think this Moto E is better than the Nokia 3 it replaced.
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
plscotland said:
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
Click to expand...
Click to collapse
That's very generous of you.
Like you, I don't get much time (due to work) but I have two weeks off from 21/12 and can supply as much information as you want.
I would like root if it's possible.
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
plscotland said:
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
Click to expand...
Click to collapse
I have a "working" 3.2.3 version for PETTYL but I'm not sure it's the version you linked
The one I have "works" in that it boots to TWRP fine from fastboot but obviously it doesn't flash.
I can't flash GSIs through that version, where they do flash no problems through fastboot......
Finally, I can flash magisk through that as even though magisk flashes successfully, magisk manager shows magisk is not installed and asks to flash it again.
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
bubba1601 said:
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
Click to expand...
Click to collapse
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
plscotland said:
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
Click to expand...
Click to collapse
Great, thanks
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
plscotland said:
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
Click to expand...
Click to collapse
Yeah, Ive been skipping the mount vendor and pushing Fstab via ADB whilst in twrp.
I'll give this twrp a whirl later this evening when my kids laptop is available
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
bubba1601 said:
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
Click to expand...
Click to collapse
in fastboot enter (use cmd powershell gives erorrs) fastboot -w
And then try rebooting it can take a while and tell me did it fix the problem
Recuperación TWRP 3.3.1-0-Pettyl
Hola buen día soy de Guadalajara México
A mí sí me funcionó está recuperación para rotear con magisk e instalar un mood de píxel.
La instalación de TWRP3.3.1-0-PETTYL Lo hice gracias a la aplicación Root essentials en el apartado flasher flasheando la imagen de la recuperación y ya dentro de la recuperación hice una copia de seguridad e instale magisk
Mi dispositivo es el Moto e5 play go pettyl XT1920-18
Heeeeeelp
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
João klebão (supahjohn64) said:
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
Click to expand...
Click to collapse
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend, i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil:good:
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend,
I already work in some way with custom roms since 2013 when I had my lg l1 2 lmfao... i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.