Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
zezayer said:
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
Click to expand...
Click to collapse
I would recommend downloading the latest factory image (or whatever version you want to update to) and flashing all of the partitions individually (EXCEPT USERDATA, as that will wipe your device). This is what I've done for years on all my Nexus devices when updating. You'll just have to re-flash TWRP and Xceed after upgrading. Shouldn't be too difficult. Some may say you really only need to flash certain partitions like system, boot, vendor etc., but I always find it better to err on the side of caution to make sure I don't bork anything in the process.
tl;dr
See Step 9 from this post from the Nexus 6P forums (obviously, make sure you replace the angler image files with the appropriate Pixel C images): http://forum.xda-developers.com/showpost.php?p=62924118&postcount=2
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
zezayer said:
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
Click to expand...
Click to collapse
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
SmokinCharger said:
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
Click to expand...
Click to collapse
I'm using the Loliviper flashable zip. Working really well.
zezayer said:
I'm using the Loliviper flashable zip. Working really well.
Click to expand...
Click to collapse
Which specific version. I noticed that there are various loliviper versions that are device specific
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
zezayer said:
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
Click to expand...
Click to collapse
Thank you.
Related
Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!
[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)
The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
https://www.androidfilehost.com/?w=files&flid=43558
k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?
When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.
jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device
i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.
Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.
Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.
Thank you. I tried to find it on the github site and found nothing.
Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.
Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks
Seeing a lot of issues with Android 11 and 12 unlocking the bootloader and applying root. Is now not a good time to upgrade or should I wait for a boot image?
Not quite sure what you're referring to, but there are zero issues with unlocking the bootloader or rooting your device...
I can't speak for TWRP. I have had issues with it the last few versions so I had to make due without it. If I am mistaken about having twrp on the OP9 Pro on the newest LE2125 c61 update, I'd be interested.
Anyway, my response is mostly to address your question regarding root. Here are the steps that worked for me.
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
intense21 said:
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
Click to expand...
Click to collapse
there is no need for TWRP...
Smedslund said:
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
Click to expand...
Click to collapse
How do you root without twrp? or you mean to just boot twrp and not install it?
CtrlValCanc said:
How do you root without twrp? or you mean to just boot twrp and not install it?
Click to expand...
Click to collapse
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Smedslund said:
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Click to expand...
Click to collapse
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
CtrlValCanc said:
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
Click to expand...
Click to collapse
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
vincemue said:
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
Click to expand...
Click to collapse
could you explain better? I never used sideload before. What commands do you use?
CtrlValCanc said:
could you explain better? I never used sideload before. What commands do you use?
Click to expand...
Click to collapse
If you want to install any add-ons, Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence. (GAPPS or Magisk for example)
for example for magisk:
download the newest magisk apk version
after download, rename it and instead of .apk do it .zip
go into revovery and click Apply Update, then Apply from ADB
command is : "adb sideload Magisk-v2X.X.zip"
you must exchange X for your version.
Boot images gets patched
please note that I am not an expert, that is just what I found somewhere and use since then.
if you need more information you could also check the install instructions for lineageOS to get to know some basics: https://wiki.lineageos.org/devices/lemonadep/install