I'm sure this issue is affecting lots of people and is probably buried deep within another thread.
I have a Moto X Pure 2015 that I purchased about a month ago. I then successfully rooted the phone (LP5.1.x)
Yesterday I got notification on my phone of OTA Update available.
I attempted to download and install this update and then I ended up in a (TWRP) Teamwin bootloop, with the Teamwin screen flashing overAndoverAndover and could not turn off or reboot my Moto.
Eventually I got out of the bootloop by doing a hard reset and reinstalling my last backup from TWRP.
---- NOW ---
Please explain in simple language and exact steps how to take an already rooted Moto X Pure 2015 running KitKat and upgrade to Marshmallow. Make it simple, like you're explaining this to a 5 year old.
Please provide more information than "flash a new zip through TWRP." This is for newbies like myself who can follow step by step instructions, but we need each step.
Thank you for any assistance!
You're running KitKat? Wowee! :lol: I think you mean Lolipop!
Anyway, if you have TWRP installed I think the simplest way is to flash one of the update Zip's, I think there are some in the dev section.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Pick one of these which best suits your needs, and install it.
OOPS! Yes, I meant I'm running Lollipop!
Okay, HOW does one 'flash' a new zip onto the phone and into TWRP?
Do I connect the phone to my computer?
Seriously, need to be given simple steps that show how to do this.
Remember, there are a lot of noobs reading this and when you say "flash the new file and install with TWRP" that means pretty much nothing.
Simple step by step, please.
lottanookie said:
Okay, HOW does one 'flash' a new zip onto the phone and into TWRP?
Do I connect the phone to my computer?
Seriously, need to be given simple steps that show how to do this.
Remember, there are a lot of noobs reading this and when you say "flash the new file and install with TWRP" that means pretty much nothing.
Simple step by step, please.
Click to expand...
Click to collapse
If you download one of the MM roms from the development thread you can download it directly from your phone. If you're not sure how to flash a rom/file using TWRP you'll probably want to do a lot more research on the process before you screw anything up. Do you have adb/fastboot working on your computer in case anything were to go wrong?
How did you get root to start with?
Step 1: download zip
Step 2: boot into TWRP
Step 3: connect phone to computer
Step 4: move zip to internal storage
Step 5: flash zip
Step 6: say no to TWRP rooting the ROM
Step 7: read up before performing any risky actions like rooting and flashing OTA's
Sent from my XT1575 using Tapatalk
It's simple, unroot, update, what's hard about that? If you're struggling with that, you probably shouldn't be messing with phones in the first place
If you want complete stock marshmallow, then follow these steps:
This is ONLY for the XT1575
Please read all steps before attempting anything.
1. Back up
You will lose all user data with the method I am giving you.
Back up everything, make one in Titanium Backup (save it to a computer or sdcard too) and make a TWRP backup (boot into recovery, select backup and swipe the slider)
2. Download the stock file from @gokart2 's thread
Expand the 6.0 section and then expand "XT1575 stock unrooted TWRP backup". Download the file named "6.0 stock unrooted.zip".
UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3. Boot into TWRP and select "restore". Navigate to the 6.0 stock unrooted backup, select it, then swipe the slider to restore the backup file to your phone..
4. Let the restore finish, then once finished reboot the system. You will get a prompt from TWRP asking if you want to install SuperSu. DO NOT INSTALL IT.
5. Let the phone boot up (It will take some time, possibly even a half hour) then set up Marshmallow .
6. Redownload TItanium Backup and restore your old Titanium Backup, but use caution. I only restored the "User Apps +Data", restoring system data could not go well.
7. Enjoy your new Marshmallowy experience!
7a. If you want root, the method right now is Chainfire's systemless root. Read extensively on systemless root before attempting. But here's a link to Chainfire's thread for systemless Marshmallow root.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Jay794 said:
It's simple, unroot, update, what's hard about that? If you're struggling with that, you probably shouldn't be messing with phones in the first place
Click to expand...
Click to collapse
It;s a little more complicated because if he had modified any other system files while he was rooted, he must restore completely to stock before updating if he wanted to use the OTA update
>asking if you want to install SuperSu. DO NOT INSTALL IT.
Ok, what happens if you do say 'yes' to install SuperSu?
That's what roots the device, yes?
The reason I'm asking for drop dead simple instructions is because many (perhaps most) of the threads manage to skip steps -or- assume the user already knows what each step is. I created this thread for those who root their device, then don't think about it further, don't install ROMs, don't do anything other than have a rooted device, but then when it comes time to install new (OTA) software update months later, don't remember what to do or how to do it because they did it once on their Moto and that was it.
lottanookie said:
>asking if you want to install SuperSu. DO NOT INSTALL IT.
Ok, what happens if you do say 'yes' to install SuperSu?
That's what roots the device, yes?
The reason I'm asking for drop dead simple instructions is because many (perhaps most) of the threads manage to skip steps -or- assume the user already knows what each step is. I created this thread for those who root their device, then don't think about it further, don't install ROMs, don't do anything other than have a rooted device, but then when it comes time to install new (OTA) software update months later, don't remember what to do or how to do it because they did it once on their Moto and that was it.
Click to expand...
Click to collapse
No, TWRP has not been updated to work with rooting marshmallow. It will not install the correct superSu. You must flash chainfires new systemless root supersu if you want root, but even then the root is systemless. Meaning there are some root apps that do not work with systemless root.
The beauty of systemless root is that it doesn't touch /system so if you do a factory reset, root is removed. That way all that needs to be done for an OTA update is factory reset or remove root via another method.
Sent from my XT1575 using Tapatalk
I tried this method and got MM installed, however I could never get any networks to show up to finish the install process. I rolled back to 5.1.1 for now.
I guess my next step is to roll back to stock and try it that way unless someone has a suggestion.
Research! And then do this
I do agree that you need to do more research before even starting a project such as this, and in general if you plan to play with modding your device in any way! You can't always expect step by step instructions and you really shouldn't be messing with anything at all unless you have a decent understanding of how things work. We are all "noob's" at first (or most, at least) so it's totally understandable for someone to ask for help--but it's also a bit impolite to come in demanding step by step guides, considering most (presumably) of us learned how to do most stuff by searching and reading through forums. TL;DR: Make sure you do your research before you start a project!!
That said, there is a fairly detailed and easy enough to follow guide by reformedmusings over at: https://reformedmusings.wordpress.c...ure-2015-to-android-6-0-marshmallow-on-linux/
I am actually in the middle of the process now and things seem to be going smoothly. You can do everything from a windows PC, just ignore "sudo" as that is a linux/unix command... The easiest way to copy stuff to your internal SD is to connect (with device in MTP mode) to your PC and copy files to your devices SD card from File Manager or whatever (root directory).
I hope this helps!
Update: It seems to have worked fine! I was able to update to marshmallow, though I actually chose to copy the update image to my PC and ADB Sideload instead of upgrading from SD Card because I couldn't find the file and the screen wouldn't scroll. Root seems to work fine, also. I didn't reinstall xposed and Android Pay seems to be working with root (as some have noted)--I think Android Pay will stop working if xposed is installed (or even the new dialer).
Related
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
TommyWhite said:
Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
Click to expand...
Click to collapse
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
You probably got stuck in boot animation because you flashed superSU in system mode. It should be installed in system-less mode. Magisk will install only in system-less mode and I think it's better at passing the safetynet.
amageek said:
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
Click to expand...
Click to collapse
Thanks for replying :good:
What do you mean with "Your can error every versions..."? .. Do you mean you can root every version?
I am very new to this. Half of the time I dont know what the H im doing, and all of the time I only have a slight idea of what is going on in the Phone. For example I dont even know what a root file is, could you tell me?
How did you root with Magisk if I may ask? And whats the difference with SuperSu?
I had all kinda errors and issues along the way from B605 to B170 and B123 Android 5 back to 6 and B609. (I could make a thread of it ... maybe it helps others???)
Because today I finaly rooted my Phone.
Weirdly enough root checker basic sais it isnt but other root checkers say it is (and my device itself said after reboot that it was) ... so what to make of that?
Can I update the Phone now its rooted without unrooting it?
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
TommyWhite said:
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
Click to expand...
Click to collapse
You can't update phone which is rooted(as far as I know).
Do you have TWRP recovery installed?
If you had TWRP installed and you rooted by flashing SuperSu(this is what other guy meant with "root file"). By default SuperSu installs in system mode(meaning it does it thing into system partition). You need to install other zip file first to make it install system-less mode(meaning it does it thing into boot partition).
Magisk is also flashable zip and similiar to SuperSU. If you use apps that need to pass safetynet(like netflix) you want to root with magisk.
Don't know did that helped at all. It's hard to explain when I only know how to use it but don't know why/how it works : D
And if you don't mind doing factory reset before updating, you can also install official updates in TWRP.
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
TommyWhite said:
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
Click to expand...
Click to collapse
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
Click to expand...
Click to collapse
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
keikari said:
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
Click to expand...
Click to collapse
Yes but I haven't uploaded the file in my Mega Cloud... He can update it ..
keikari said:
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
Click to expand...
Click to collapse
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
Click to expand...
Click to collapse
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
TommyWhite said:
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
Click to expand...
Click to collapse
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
amageek said:
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
Click to expand...
Click to collapse
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
TommyWhite said:
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
Click to expand...
Click to collapse
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
TommyWhite said:
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
Click to expand...
Click to collapse
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
amageek said:
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
Click to expand...
Click to collapse
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
keikari said:
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
Click to expand...
Click to collapse
Thanks again, I copied some bits to remember. I hope you were not tired of me not understanding things. You said I should just ask so here I go again
I understand most of what you wrote but:
TWPR can make a back up/an image of the device, right? But that image doesnt include apps and app data (or data at all?)? And Titanium doesnt back up firmware I guess.
So how do I make a backup of everything (except of the hardware) then?
Also Im in a dilemma about updating TWPR, because you said it will whipe data (what data actually?) and amageek said I need new TWPR for stock updates. So I need the "backup of everything first" I guess ... what to do? I have TWPR 3.0.2 now by the way.
Also cant I just download Magisk from Google Play now that my phone is rooted ... or is that being stupid?
7: Its strange, coz I remember I had my phone rooted (with the help of some old tutorial they should remove imo) but accidentally downgraded my phone with it to lollipop (one of the many failures I encountered ). But just with local updates B052 to B132 to B170 back to some 2KB B132 to marshmallow B609 ... something like that ... it was unrooted again.
Anyway, by update script you mean a script only TWPR can read?
And therefor TWPR does not check the version allready installed?
Is that correct?
But after this you say: "If you are doing this remember to reboot recovery when installation is done (it will go to stock recovery) and to factory reset.
Then you can flash TWRP and do rooting stuff."
I dont get that, coz that means you have to start all over again ... or do I miss something?
Im sorry, im doing the best I can.
TommyWhite said:
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
Click to expand...
Click to collapse
Do you have have stock recovery or TWRP recovery? If you have TWRP recovery then fish stock recovery and then try updating again...
I just bought the Honor 8 and immediately unlocked and rooted it via Magik. Of course not long after that, I get a notification that there is an update available. You obviously cannot update the phone by simply pressing the "update" button since we have a non-stock recovery. I did a fair amount of research to find out how I could get the update and I wanted to share what I found. All of this information is out there already, but generally speaking it is spread out in many different threads. Hopefully these directions can help someone else.....
First, the usual disclosures.....
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this GUIDE
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
1) Make a NANDroid backup using TWRP: if the new update locks the phone, you will need this backup to restore data after unlocking it
2) Unroot your phone: honestly I did not do this step myself because I simply didn't think about it. The update process worked for me without unrooting but I am also using Magik which doesn't alter the system files. To ensure success I would definitely recommend you unroot. You will have to reroot the phone after the update regardless if you unrooted or not, so you aren't saving any steps by keeping root at this point. If you have used a different root method besides Magik, you must unroot prior to attempting an upgrade.
3) Obtain stock recovery.img file: the update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you already have a copy of the stock recovery skip to step 4. If you are like me you don't have a copy of the stock recovery image on hand and we will need to extract it from the stock ROM image. Using a computer (not your phone) download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
Download the Huawei Update Extractor software and unzip the folder on the computer. Open the HuaweiUpdateExtractor app and use the software to extract the "Recovery.img" file. Here is a Youtube video showing how to do this. Please note, although the video shows several files being extracted you only need to extract the "Recovery.img" file for our use. Move the stock recovery image to your ADB folder so you can flash it in step 4.
4) Flash the stock recovery image: use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 (parts 1-5) of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of the TWRP.img
5) Reboot into system
6) Install Update: go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 2gb, so make sure you are ready to handle that size transfer. After the download is complete, start the update process. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong (like not unrooting the phone prior to attempting the update). It worked fine the second attempt.
7) Reboot: the phone will reboot and you should check the status to make sure you are on the latest version.
8) Flash TWRP recovery: I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update using this method. I was simply able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, then read the note at the bottom of this post.
9) Reboot into system
10) Flash Magik zip: reboot into recovery and flash Magik zip to get SuperSU.
11) Install Magik modules: reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
12) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NANDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.
Thank you for this thread.
Hello sic,
I am having the same issue with my Huawei GR-5 2017 and like you, I have my fair share of researching for weeks now and I was really happy to stumble on this thread.
Before I start with the process, I have a few questions for you. I hope you could help me (even though this thread is half a year ago).
Can you elaborate steps 1 and 2 or could you provide me a link on how to do those?
I got xposed installed im on emui 8 i also tried flashfire but it only turns the phone off.. Ist it eneugh to uninstall xposed? And can i get the recovery img from fullota? And must i restore images in magisk? I will try it without xposed installed. And a theory: is the information abaut bootloader unlock stored in a partition like oeminfo? If it is we could restore oeminfo.
What happens if I have lineage 15.1 and I want to return to 7.0 stock can I do it?
should I do a back up? I read that I could lose the imei :crying: how can I avoid it?
I would use this tutorial
https://www.youtube.com/watch?v=F_6LQr01GhY
thank you all for the help and advice :good::fingers-crossed:
sorry for my bad English
I don't know about lineage 15.1, but I had the OTA 8.1 update on my XT1644, and it broke my speakerphone and made my phone run like crap, so I just rolled back to stock 7.0 and am VERY happy.
I DID lose IMEI (I had IMEI=0), but from what I understand, it was because I manually flashed 7.0 from adb. I think that had I used the TWRP file, it wouldn't have happened.
I got IMEI back by following the directions in this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
I also disabled OTA backups by doing this: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
So that Motorola can't push an OTA on my phone and brick it.
You should make a complete backup following the directions of this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-complete-partition-t3875787
I know virtually nothing about messing with phones or Android. My motivation was that if I couldn't get rid of OTA 8.1, I was going to throw away my phone and get something different. And I didn't want to spend the money on a new phone. I figured I'd brick what I have, before I spent money on a new one.
I pretty much followed the directions on this thread:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Except that by loading 7.0 manually, it caused me to lose IMEI. Knowing what I know now, after flashing TWRP, I would have flashed 7.0 using TWRP. And I don't think I would have lost IMEI then.
Once I had 7.0 loaded, I flashed Magisk to get root.
Once I had root, I used a file explorer to go in and delete the app that pushes the OTA, so Motorola can't screw me. As far as I know, I am now permanently on 7.0.
Do this at your own risk. But you're already running Lineage, so I assume that you know way more about this than I do.
Edit: Just realized I kinda rambled here. So here's the condensed version of what I would do, I think... do at your own risk.
1. Use that thread I linked to back up your *everything*
2. Save stock 7.0 file, Elemental X file, and Magisk file on your SD card (all from XDA)
3. From TWRP, flash 7.0
4. Once you have 7.0, from TWRP flash Elemental X.
5. From TWRP, flash Magisk
6. From that link I posted, delete the file that stops OTA's.
I think you'll now be where I am, with rooted stock 7.0. But you should still have your IMEI. If you have IMEI=0, follow the directions in the link I posted.
slimbobaggins said:
I don't know about lineage 15.1, but I had the OTA 8.1 update on my XT1644, and it broke my speakerphone and made my phone run like crap, so I just rolled back to stock 7.0 and am VERY happy.
Click to expand...
Click to collapse
I am eternally grateful for your help and message!! :good::good::good:
but in the tutorial that you sent me: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
indicate that the installation should be done manually by adb... do you think I should do it for TWRP ??
---------------
[...]
Flashing Stock Firmware:
1) Download the correct firmware for your device from http://www.filefactory.com/folder/c6cdedc45a775d27
2) Download adb and fastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing abd and fastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
[...]
-------------
thanks
That tutorial was written years ago. I think back then, the only way was to manually install.
If you manually install 7.0, you will wipe your IMEI and have to restore it like I did.
I suggested the TWRP install because I *think* it wont wipe the IMEI.
If it does, you should still be able to recover it... but again, I barely know what I'm talking about. So please follow the thread about backing up your entire phone and persist, first. I am merely sharing with you what I did to roll back mine to 7.0, your experience may vary.
And again, if you do roll back, make sure you follow the instructions to disable OTA, because if you accidentally take an OTA, it will brick your phone for sure.
I literally just figured out how to do all this, this weekend. Prior to that I knew *nothing* about this stuff. So please read everything you can to educate yourself... its all here on this very good forum, you just have to piece it together. I am 100% a newbie.
Edit - just an FYI for complete transparency. I have moved from the Pixel 3a XL to the Pixel 6. I no longer own my Pixel 3a XL. While I've been told (thanks @AndDiSa) that the root process for Android 12 is the same as it historically has been, I no longer can test things myself. (The root process for the Pixel 6 is different and more complicated than this phone). If you run into any problems or issues, please post in this thread and someone will hopefully be able to answer them.
I'm assuming you understand how to use ADB on your computer. If you need assistance with installing or using ADB, please refer to this XDA article for more information. However, here are some common issues that people have with ADB if it doesn't work initially for you. 1) Check the Android System Notification that appears in your phone's notifications after you plug in your USB cord. Your phone probably defaults to "No data transfer" and you need to change it to "file transfer" to allow the phone to connect. 2) Make sure you have USB debugging turned on in the Settings/System (advanced)/Developer options. 3) If this is your first time using this phone/computer combination, you will have to accept the connection when it pops up on your phone.
You also need an unlocked bootloader to complete these steps. If you need assistance with unlocking your bootloader, here is decent set of instructions. Those instructions are based on the Pixel 3 phone, but the steps are the same for the 3a devices.
Here are the official Magisk installation instructions. I will walk through them to help everyone understand them. Please note that while TWRP does work with Android 9 (Pie), it does not work currently with Android 10 or 11. If you are still on Pie for some reason you can choose either installation option, but if you have moved to a later Android version, you must use the "Boot Image Patching" installation method.
Custom Recovery Installation Method - (available for Android Version 9/Pie only because TWRP does not work currently with the Android 10/11)
This is the easier installation method IMHO, but it does require using TWRP. If you don't know how to get TWRP for the Pixel 3a, please refer to the official TWRP for Pixel 3a thread
Step 1 - Download and install the Magisk manager app on your phone. (link to the latest stable version can be found here).
Step 2 - Using the Magisk manager app, select "Install Magisk" and select the "Download Zip Only" option. This simply downloads the installation zip to your phone's download folder. It doesn't attempt to install anything.
Step 3 - Boot into TWRP - (because TWRP is not permanent on the stock Pie OS, we must follow these instructions each time we want to boot into TWRP).
Step 3a - Download the latest TWRP image for the 3a to your computer (not your phone) from the official TWRP for 3a thread.Step 3b - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".Step 3c - Boot your phone into the bootloader (type the command "adb reboot bootloader").Step 3d - Boot into TWRP using this command, "fastboot boot twrp-3.x.x-x.img" (where "twrp-3.x.x-x.img" = whatever the name of the TWRP download is). Please note you are not using the "flash" command as we are not permanently installing TWRP.Step 4 - Once the device boots into TWRP, select "Install" and then find the Magisk.zip download from step 2. Swipe to confirm the installation
Step 5 - After the installation is complete, simply reboot system.
Step 6 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 7 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed under the "Taking an OTA Update" section below
The Boot Image Patching Installation method - (the only method currently available under Android 10, 11 or 12, but it also works with Pie).
Use this method if you are on Android 10 or 11 or you are on Android 9/Pie but you don't want to or can't use TWRP.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). If you are early in the Android 12 cycle, you probably need to use a Canary build of Magisk.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img" - Please note, I would suggest double checking the "file modified date" prior to moving the file. Be sure to only move the file if it was last modified on the date you are doing this. I've had a strange situation before where the newly modified file didn't immediately show up and the file showed a modified date of the previous month. If you flash an old version, your phone will bootloop.
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
Step 11 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 12 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed next.......
Taking an OTA update in the future (if you used this method to install Magisk).
Taking OTA updates is very easy with the Pixel devices because of their A/B partition system. It allows us to uninstall Magisk, take the OTA update, and reinstall Magisk - all from the phone and all without rebooting during the process. Here are the offical Magisk OTA instructions. I will go through the steps to help explain them.
Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.
Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.
Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”
Step 4 - Press the Reboot button in Magisk.
That should be all it takes to install an OTA and keep root.
Please note, we are getting reports that users are getting notifications that an OTA update has been installed even when they have "Automatic Updates" turned off. If this happens to you, don't reboot the phone which is suppose to be the final step in the update process. Instead, follow the above instructions on taking an OTA update, but start in step 3. In other words, you shouldn't have to uninstall Magisk because the update has already been installed. All you need to do is install Magisk to the "second/inactive slot (After OTA)”. After completing that step, you can reboot your phone to complete the update process. Be sure to post your experiences in this thread to let us know if this process works or not.
Just remember that many custom parts (like kernels and Magisk modules) may need to be updated to any new OTA version. Please be sure to check out the forums for each custom kernel or module that you may want to install to ensure it has been updated to the lastest OS version. Don't assume anything or you may find yourself in a bootloop.
If you find yourself in a bootloop after upgrading an already rooted phone
If you find yourself in a bootloop after updating to a new OS version and flashing the magisk_modified boot.img again, it is likely due to an installed Magisk module not being compatible with the new update. To uninstall all Magisk modules to fix the bootloop, follow these steps:
Step 1 - Connect your phone to the computer you use ADB on.
Step 2 - In ADB type the command "adb wait-for-device shell magisk --remove-modules"
Step 3 - Start your phone again or wait for it to go through another bootloop cycle.
Step 4 - as soon as ADB is available (which occurs even during a bootloop) the command will activate, the modules will be removed, and the phone will reboot.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on a couple Android 10 images, but most do not require this step.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the initial boot is usually pretty quick, it can take longer. I've occasionally seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that sometimes it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need be patient and let the phone complete the process.
My rant about using these "Pre-patched Boot image" files
I started this thread during a period of time where there was a another thread on this forum started by pbanj that showed users how to root their phone by using some pre-patched boot image files. This method is not the generally accepted method and while it works, there are major shortcomings with it (see explanation below). Because it was the only root thread available at the time and he only showed the "pre-patched boot image" method, many people blindly followed his directions only to be confused when it came time to update the software on their phones. I wrote this thread in an effort to show people the official Magisk installation method. Pbanj has since updated his thread and it now includes the preferred method as well. With his edits, the two threads are sharing the same information now, although Pbanj thread still offers people the "pre-patched boot image" method (which I don't recommend people using).
EDIT - Yet another thread pushing a pre-patched root method has been started. It suffers the same issues as listed below.
Shortcomings with using the "pre-patched boot image" method.
As I already mentioned, there is a huge shortcoming with using the "pre-patched boot image" method described in the other root thread. Because he provides a pre-patched boot.img file, you skip some normal installation steps. In the end you have the exact same patched file (which is why his method works), but you cripple the system when it comes to taking any future OTA. That's because the first step in taking an OTA update is having Magisk reflash the stock boot.img effectively uninstalling itself. This step fails if you used his pre-patched boot image method because you skip the step where Magisk creates the backup of the stock boot.img that it needs to uninstall itself.
I already used the "pre-patched boot image" method to gain root. What can I do?
First, let me clarify and say that there is nothing wrong with your phone or root privileges. Your phone will work exactly as expected and root and Magisk will work exactly as expected. That being said, in the near future you will want to update your phone to the latest Android update and this is where the "pre-patched boot image" method is much more cumbersome. The best option is to simply undo his root method and re-root using the method described above. To do this, flash the correct stock boot.img file to your boot partition and then follow the steps above to reinstall Magisk. Jbanj has confirmed this method will work. The other option is just wait until you need to take an update and then sideload the OTA update following the instructions above. This will remove root and you can then follow one of the two methods to obtain root as outlined in this thread.
Notes
- Please be sure you are on the latest adb and drivers which can be found here.
- You do not need to keep the stock boot.img file (from step 2 of the Boot Image Patching method) on your phone after completing these steps. Magisk saves the stock boot.img backup at /root/data in a file with the name "stock_boot_XXXXXXXXXXXX.img.gz"
Thanks to.......
@ZVNexus for getting TWRP working on the 3a and 3a XL phones
@topjohnwu for making Magisk what it is today
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
sic0048 said:
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
Click to expand...
Click to collapse
Sure. It's the way I do it also. But show some class and don't call out other, helpful members in this fashion and crap all over what they do. I have seen your posts and know your a helpful members also, let's respect each other and be classy.
Sent from my Pixel 3a using Tapatalk
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Bankuu said:
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
Click to expand...
Click to collapse
I've edited the steps and added a few more going into greater detail to try and make it even clearer for users. Let me know if you have any suggestions.
alliance1975 said:
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Click to expand...
Click to collapse
You should be able to use the normal Magisk OTA update instructions for future updates.
I've updated the thread and I think the "step 9" you listed isn't the same anymore, but I think I understand your question. Actually I think my original instructions were inaccurate as far as that step. I've always gone back into Magisk after flashing the modified boot.img and I thought I hit install to install the Magisk framework (if that is the correct term). But after reading some other guides, I think my memory is incorrect and you don't really have to install anything after the flashing portion of the steps.
Once you reboot after flashing, that should be all you have to do. I'll uninstall Magisk here in a while and walk through the steps myself to ensure this is correct howeve.
The OP should be made a sticky.
Cool guide. Can the method be applied to Q beta 4 ?
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
No root for Android q on our devices yet afaik.
Sent from my Pixel 3a using Tapatalk
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
alliance1975 said:
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
Click to expand...
Click to collapse
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
sic0048 said:
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
Click to expand...
Click to collapse
Thanks sic0048. You put up with my dumb questions and helped make my pixel 3a a great phone.
Respect.
Edited - now that jbanj has confirmed we can simply flash the stock boot.img file to the boot partition and start over, the post I originally had here is pointless.
Alliance's question got me to thinking.....
Since Magisk saves the stock boot.img backup at /root/data in a file named "stock_boot_XXXXXXXXXXXX.img.gz" I wonder if we can't simply share a backup file with someone that used jbanj "modified boot image" method and have them copy it to that location. I suspect Magisk will then allow the normal OTA update prceedures to work.
I can share the backup file that I have, but it is for the 3a XL model, Android version 9 (Pie) and the June 5, 2019 security update. That means it will be next month before there will be another OTA update pushed out.
If someone is still on the OEM March update and rooted using the normal directions and is willing to share their backup file, we might be able to try it sooner.
Unfortunately I don't know if Magisk modifies the backup to be some sort of unique file. I doubt it, but I don't know for sure. Of course worse case scenario is that it doesn't work and the person has to flash the OTA manually - which is no different than what they would have to do anyway. So there really isn't much risk in trying this.
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Bankuu said:
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Click to expand...
Click to collapse
Google has changed the file structure in the Q beta 4 release and root is not possible at this time. This is true across all devices (not just the Pixel 3a). I know John Wu (the Magisk developer) is working on a solution and I would expect to see results before Android 10 is released, but only time will tell.
However, at this time there is no root on the Q beta 4. If you need root, you will have to stick to Pie for now.
@sic0048 I've updated my thread
I'm getting weird behavior here that I've been able to replicate.
Bottom line, if you use the Magisk patch method, upon flashing that boot image, your phone will auto-play music every single time it boots up. That's incredibly annoying.
Uninstall and go back to stock boot.img, and it goes away. Flash again, it's right back.
Guess I'll just wait for TWRP instead of going through those steps again, lol.