Related
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).
If you have already upgraded to Nougat using the manual method I posted, you don't need to flash this. If you do, you will get all the bloat back (again), and have to flash your su bin (again), but it isn't going to break your phone.
This is for the H901. Make SURE you have an ACTUAL H901, and not one of the half / half H901 / F600 phones.
If you are still on MM (any version), NOT LP, then you can use this to upgrade (or clean install -- just do a wipe) to Android 7.0 Nougat. This is from the official KDZ that was released on July 18th.
When you flash this, all the carrier bloat / LG bloat / crap / garbage, will come back. You will also lose root until you flash the su bin of your choice. That is the point of this, you WON'T lose TWRP, so you can still root...
Any questions, don't hesitate to ask.
Lastly, when I have time, I will be releasing a version that is already debloated...
Download v30b_update.zip
SHA1: 4ae9338b9301f4b56437ec761b678c8706c90bc7
If you want the FULL Nougat experience -- that is ALL of the v30b firmware except the stock recovery (we don't want to lose TWRP do we?), then flash this as well.
If you flash this, then you might as well delete all of your MM backups that you made with TWRP because you can no longer restore to MM using your backups (you can flash back to MM -- just not with the backups).
If you choose to ignore this, and decide to restore a MM backup, you will brick your phone.
Download full_nougat.zip
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
Known working (tested by me) SU binary: download SuperSU 2.82.
SHA1: d980effb25a8f23bc944d6b1015923f310038031
It has also been confirmed by multiple users that Magisk 12+ works, but I have not confirmed that myself.
This will not wipe ANY of your data / apps / or anything else you may have on your phone. That is why it is an UPGRADE and not a CLEAN install
If you want to do a clean install, just do a full wipe, and then flash.
If you downloaded any of my failed attempts (really -- a typo in a ui_print line?!?!?), and don't want to download the whole zip again, you can download this zip. It is the META-INF directory. You will need to unzip the broken v30b_update.zip, and then extract this over top of the META-INF dir, and then zip it back up.
Make sure you use recursion, and make sure you unzip it on TOP of the META-INF dir, not inside it -- or you will end up with META-INF/META-INF/com/google/android. Won't break your phone, but won't flash either.
-- Brian
Thank you so much man you just made my day...
it will be nice if you can share the recommended SU zip...
Any of the current SUs will work. I am using SuperSU 2.82 (hell, there may be a newer version, but it works, so I don't bother), but I know that Magisk will work as well.
-- Brian
seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?
having the same problem too bad for me !!
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
Just opened the zip file and notices META-INF folder is empty there are suppose to be some files in there which helps flash a file...
Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian
Well THERES the problem. I uploaded the bad copy. I zipped without recursion the first time. Thought I nuked that copy. I am uploading the proper version now -- ya know -- with an ACTUAL META-INF dir
-- Brian
JiggyTox said:
seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?
Click to expand...
Click to collapse
runningnak3d said:
Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian
Click to expand...
Click to collapse
if you can only share meta-inf folder, I think it will work if you just copy files into the zip. that'll be awesome!!
OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian
Thanks a ton for the work you do helping keep this device alive.
I couldn't wait so I went ahead and unzipped the original update.zip and did the other method of pushing the three images via adb, and it works perfectly! thanks a lot again!
idk
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.
runningnak3d said:
OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian
Click to expand...
Click to collapse
thanks man :highfive:
DroxOh said:
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.
Click to expand...
Click to collapse
Getting the same error as well
Well, what the crap. Edify script is ... or should I say WAS, one of the simplest things in the world. Now that I am off work and don't need my phone, I can actually test this before I post an updated zip.
The only thing I can guess is that the v10 doesn't let you flash from the zip itself, so I am going to extract the files to /tmp and then flash them.....
I will post an update as soon as I have this working. This has never been an issue before.....
-- Brian
Thanks Bro. But, I want to turn off big cores Lg v10 H901 Android 7.0. You can create file off core.zip? Plz....
Help me! when i try to flash it, i get the next msg: Updater process ended with ERROR: 6
---------- Post added at 04:35 AM ---------- Previous post was at 04:23 AM ----------
Tell me something, if i update with LG Bridge.... i will lose the TWRP or Just the root ? I net to update to nougat now :/
You will lose both. I did before I found this thread.
Sent from my LG-H901 using Tapatalk
My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone
Ash.... i hope that we can get a solution to make the zip works....
huy chuong said:
My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone
Click to expand...
Click to collapse
As far as I know you cannot rollback to MM from Nougat. Just have to wait and see if someone is able to create a rooted and debloated kdz or .tot Nougat Rom for our H901. I tried to use Dirtycow method to root but the fastboot commands do not work.
Sent from my LG-H901 using Tapatalk
So, since once a month I find myself having to click a bunch of links and read how to do a bunch of commands, I wanted to create a thread that (rather generically) explains how to manually flash the OTA monthly updates if you're rooted with Magisk. So, minimally, here's a thread for me to review every month... if it helps you all out, all the better!
Pre-requisites:
Download Latest OTA zip file from Google.
Obtain the STOCK boot.img (required) and dtbo.img (optional) of the System ROM you are currently running. This can be done if you already have the full System Image file downloaded, downloading it currently, or just obtaining the stock boot and dtbo image files elsewhere. (NOTE: This can be skipped if you successfully uninstall Magisk BEFORE you start the process and choose to restore the Stock images in the uninstall process.)
Download Latest Magisk Zip file
Download latest TWRP recovery image
If applicable, have latest USB drivers, adb/fastboot/ files etc.
Preparation:
1) Extract or open the Full Image file and locate the boot.img and dtbo.img files. You will want these on your PC in the platform-tools folder (I usually put the Month name at the beginning, ex. - Jan_boot.img). Again, you can skip if you successfully uninstall Magisk prior to all of this.
2) Copy your OTA zip file to the platform-tools folder, again naming it after the month helps (ex. - Feb_Pixel2XL_OTA.zip)
3) Put your TWRP recovery in platform-tools folder.
4) Place the latest Magisk zip on your Pixel's internal storage (what used to be the SDCard on phones so equipped).
Commands:
1) From PC, open command prompt and change directory to your platform-tools folder.
2) If your phone is on, "adb reboot bootloader" If powered off, press power and Vol Down button to get to Bootloader. Plug your phone into your PC.
3) [If Magisk is not uninstalled first] Command: fastboot flash boot {Name_of_boot.img File}
4) [If Magisk is not uninstalled first] Command: fastboot flash dtbo {Name_of_dtbo.img File}
5) On your phone, hit Vol Down until you see Recovery, then press power button.
6) Once in recovery mode, press power and Vol Up to bring up menu
7) Scroll to item: "Apply update from ADB" and press power
8) Command: adb sideload {Name_of_OTA.zip file}
9) After the OTA finishes flashing, exit recovery back into the Bootloader
10) Command: fastboot boot {twrp_filename.img}
11) Install Magisk Zip file (and any other Zip files you want installed... Kernels, etc.) within TWRP
Then after flashing your zip files, reboot to system and you should be all set.
I believe everything above is correct, but if I've made a glaring mistake, please let me know. I also realize there may be other methods to this madness, but this is what works for me.
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
uofirob said:
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
Click to expand...
Click to collapse
Yes. Mine is set to pin, which I had to put in and it let me finish.
Sweet. I'll give this method a try tonight!
WorldOfJohnboy said:
Yes. Mine is set to pin, which I had to put in and it let me finish.
Click to expand...
Click to collapse
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
So I did this, and now I'm bootlooping. I guess I'll re-flash the Jan factory image and wait a little longer... **UPDATE** I fixed the bootloop by re-trying the process again (after re-verifying the MD5 hash on the update.zip. I rebooted after installing the update,
but before the TWRP flash to install MAGISK. Maybe this allowed the "update"
to finish processing. I also had to remove the pin from my lock screen in order to allow me to get into twrp. After rebooting into the system and removing the pin, I adb reboot bootloader and then flashed twrp. Thanks for the guide!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
PuffDaddy_d said:
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
Click to expand...
Click to collapse
You don't need to remove the -w from the .bat file since you aren't using it at all to do the update. That is only if you're flashing your factory image.
Fe Mike said:
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
Click to expand...
Click to collapse
I changed some wording under prerequisite...
I agree with everything on this guide...
just teasing...
I'm actually glad you created this thread...I wanted to create one also and try and help out as much as I could, but I don't have the cahones and didn' t think I had experience enough to start a "guide" thread :silly:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
Well...I can't speak for the OP, but I wrote my extremely similar identical one because, for whatever reason, many users would choose OTAs over flashing full factory images. I/me & you understand the benefits of the factory images over the OTAs; especially understanding the process you must go through to install the OTAs as-of-current is almost the same as flashing the factory images anyways...
But if I were to give a possible explanation to their reasoning is that, like many of them, I come from a non-Google phone (S5 for me), and OTA's were simpler, takes less bandwidth (which still remains true today), they were significantly simpler to install vs. factory images, and with a lot of popular phones you only flash factory images to recover your phone; i.e. muniz_ri's OTA's for the S5 and FlashFire were loads simpler than flashing a whole factory image. But, again, understanding the difference for Pixel 2 and Oreo's OTA & factory images (or the small difference thereof), it's probably better to do a few extra steps and/or downloads to do the whole image than sideloading an OTA.
In the end, this is for people who insist for OTA updates most likely because that's how they are familiar (and therefore more comfortable) with; whether it being explained to them or not...
Cheers!:good:
Fair enough, thanks for the input!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
WorldOfJohnboy said:
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
Click to expand...
Click to collapse
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up ??
Badger50 said:
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up
Click to expand...
Click to collapse
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
WorldOfJohnboy said:
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
Click to expand...
Click to collapse
I'm really happy to see our device has graduated to this level of discussion, instead of the random guessing and 14 different "possible" routes to a solution. Lol
Custom roms abound, once TWRP gets squared away and someone master's the art of turning monthly updates into zip installs we'll pretty much be there!
Btw OP, great write up... Clear and precise!
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Brenneke said:
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Click to expand...
Click to collapse
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
WorldOfJohnboy said:
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
Click to expand...
Click to collapse
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Brenneke said:
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Click to expand...
Click to collapse
For some reason, I don't think it restored the correct (or not corrupted) boot.img version. Then, there were remnants of the Magisk APK and other files so I ended up having to do a full TiBu of my apps and flashed (with wipe) a full System image. It may have been something I did or just my bad luck, but I prefer not to chance it and instead manually flash the Stock image as my "guide" here states.
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
The toolkit guide is probably the easiest one.
Read the whole thread and try again.
Sent from my ZTE A2017U using Tapatalk
runninghamster said:
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
Click to expand...
Click to collapse
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
I will try this today, thank you for your time in typing this
runninghamster said:
I will try this today, thank you for your time in typing this
Click to expand...
Click to collapse
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
raystef66 said:
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
Click to expand...
Click to collapse
Thank you so much, will try today!
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
Followed your steps and managed to unlock the bootloader successfully. Afterwards I tried to flash TWRP using the Axon Toolkit and this error appears. Have 0 clue why. A little help please.
View attached >>>
EDIT: nevermind, tried to boot into recovery and twrp booted, not sure why the error appeared though. thanks for the help!
Currently running 10.0.1 with Magisk, and would like to flash the incremental 10.3.0.
Can I do this safely by restoring the boot image from Magisk, flashing the incremental via local, reboot and reflash Magisk via fastboot? Do I need a patched boot img to flash Magisk via fastboot, and is there such a thing for 10.3.0?
Anything I might be overlooking, or is there a safe and better way?
Here are the instructions for Magisk. Truly, incremental upgrade is a no-no.
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
pbergonzi said:
Currently running 10.0.1 with Magisk, and would like to flash the incremental 10.3.0.
Can I do this safely by restoring the boot image from Magisk, flashing the incremental via local, reboot and reflash Magisk via fastboot? Do I need a patched boot img to flash Magisk via fastboot, and is there such a thing for 10.3.0?
Anything I might be overlooking, or is there a safe and better way?
Click to expand...
Click to collapse
You can't flash incremental, root and bootloader unlocked mean FULL OTA (1.8 GB file)
Why people like to make it complicated?
Go to the source and read A/B devices section here
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
No you don't need to restore stock boot img! This is only meant for devices that perform a boot integrity check before OTA! This it not the case of OnePlus phones.
Flash OTA local upgrade, don't reboot, go to Magisk manager, 'click' install Magisk and choose 'inactive slot' then reboot! No need to torture yourself with fastboot, gosh.
How many times will it be necessary to repeat basics.
This is written in OOS 10.x x thread in Guide section, third post.
This is the way we do updates since months,, and it will be the same with next OOS update no need to ask
Striatum_bdr said:
You can't flash incremental, root and bootloader unlocked mean FULL OTA (1.8 GB file)
Why people like to make it complicated?
Go to the source and read A/B devices section here
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
No you don't need to restore stock boot img! This is only meant for devices that perform a boot integrity check before OTA! This it not the case of OnePlus phones.
Flash OTA local upgrade, don't reboot, go to Magisk manager, 'click' install Magisk and choose 'inactive slot' then reboot! No need to torture yourself with fastboot, gosh.
How many times will it be necessary to repeat basics.
This is written in OOS 10.x x thread in Guide section, third post.
This is the way we do updates since months,, and it will be the same with next OOS update no need to ask
Click to expand...
Click to collapse
Thanks--read the Magisk tutorial, won't have to ask again.
I asked this time because I couldn't find the FULL, just the Incremental.
Also, I looked through what seemed to be relevant guides per your recommendation, but did not find the one I think you are mentioning--would you please link it here?
It will be helpful to others as well as me.
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post 3
It won't help anybody as this conversation will be lost in the limbs in a few hours.
Striatum_bdr said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post 3
It won't help anybody as this conversation will be lost in the limbs in a few hours.
Click to expand...
Click to collapse
HAHAHA--I've already forgotten which one you posted. Thank you--I'm posting it in my question also.