Related
Hey everyone, I've been using my hox+ rooted for some time now, never flashed a ROM and was wondering if I update to the new att software will I lose root?
Yes. Just make sure you have a custom recovery and flash the root installer zip. Or if you have TWRP, after a the flash, it will ask to install root.
Hey thanks for the response, I'm running twrp 2.4 the thing is I don't know whether to to let the phone update through its regular way of updating or do I flash this http://forum.xda-developers.com/showthread.php?t=2235248, the problem with flashing this is I don't
Know how to flash boot IMG. Sorry I'm a noob any help would be greatly appreciated.
Use this command in fastboot.
fastboot flash boot /location/of/boot.img
If your bootloader is unlock and your phone has a custom Recovery, the official AT&T update won't install on your phone. If you want the update, or you wait for a custom ROM with the update to be available, or you relock bootloader, and flash the latest RUU to recover the original state of your phone. Then you can still unlock with the same token and install a custom recovery to root your device.
Thanks much fellas, you've been a great help!
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
OTA appears to checksum the entire partitions, so even remount RW could have an effect (with no intentional accesses, depending how the filesystem works). However, this doesn't make a lot of sense since any update is going to struggle to replicate the same raw filesystem data reliable - maybe this is why we are seeing 5.0.2 OTAs fail on 'stock' devices.
fallen2004 said:
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
Click to expand...
Click to collapse
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
cam30era said:
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
Click to expand...
Click to collapse
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
fallen2004 said:
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
Click to expand...
Click to collapse
Do it in the other order. Fastboot flash TWRP, then flash SuperSU from inside TWRP. Very easy.
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
Zentalk forums claims that stock firmware WW_15.0405.1803.99 is released but I can't find it on the Asus support page. Anyone knows where it is?
I spent awhile looking for it as well couldn't find it
Is this update only for OTA devices and those with unlocked boot-loaders excluded from this update?
It's up now
Asus web site is always later then phone OTA, today (11-4-2018) the web site can download the upgrade file.
Now is there an easy way to install this with TWRP?
I use the same TWRP version as the last few updates
How do you do that? Anytime I try and install the stock ROM zip with TWRP, I get some error 7 message and refuses to install.
U can't flash the stock ASUS Rom with twrp. U need to reflash the stock boot.img and the stock recovery. Then update. Then reflash twrp.
How do you get the stock recovery? The one online is outdated and won't update to the latest rom.
someaguy said:
How do you get the stock recovery? The one online is outdated and won't update to the latest rom.
Click to expand...
Click to collapse
Flash these in fastboot mode. Open the archive and copy them to your fastboot directory.
https://drive.google.com/file/d/1NK66Zlaish2sqEsb6ci2ABb9XPN-HDIU/view?usp=sharing
Just unlocked the bootloader , latest MIUI global beta. Here are the questions which needs valid answers
1. Need to flash TWRP and root. Which twrp image will not need any encryption disabler flashed every time I flash a rom? please give the link of the most stable and recent version of it.
2. I will flash magisk. How will it behave with OTA on miui global beta?
3. Will I receive OTA update? If I do, how to flash it properly? I dont want to roll back to stock recovery just to flash an ota and then again flash twrp. And I dont want to flash full rom either.
4. If I am able to flash OTA through twrp, do I have to wipe anything? Im asking if I will loose any data or not.
5. As far as I know, I need to unroot everytime before I flash OTA? what does that mean actually? If im rooted, will I not be notified of the OTA update through the updater app? Or do I have to manually downlaod the ota from the web?
6. And one more thing. I dont want the clock on the top left in any screen, lock or home. Which mod will remove the clock and add regular notification icon? (working with miui beta ofcourse)
Sohan_Saymum said:
Just unlocked the bootloader , latest MIUI global beta. Here are the questions which needs valid answers
1. Need to flash TWRP and root. Which twrp image will not need any encryption disabler flashed every time I flash a rom? please give the link of the most stable and recent version of it.
2. I will flash magisk. How will it behave with OTA on miui global beta?
3. Will I receive OTA update? If I do, how to flash it properly? I dont want to roll back to stock recovery just to flash an ota and then again flash twrp. And I dont want to flash full rom either.
4. If I am able to flash OTA through twrp, do I have to wipe anything? Im asking if I will loose any data or not.
5. As far as I know, I need to unroot everytime before I flash OTA? what does that mean actually? If im rooted, will I not be notified of the OTA update through the updater app? Or do I have to manually downlaod the ota from the web?
6. And one more thing. I dont want the clock on the top left in any screen, lock or home. Which mod will remove the clock and add regular notification icon? (working with miui beta ofcourse)
Click to expand...
Click to collapse
I can answer your questions partially.
2 & 3. Flashing TWRP and Magisk will result in OTA zip not being downloaded. Instead, the full ROM will be downloaded automatically.
4. AFAIK, you can't flash the OTA zip through TWRP.
5. If you want the OTA, you will have to be completely stock, no modifications to system files. Only then the OTA zip will download and only then you can flash it. You will ofcourse be notified of the availability of the OTA zip even if you are rooted but it will not download because it does a check of your system before downloading. Only the full zip will download if you are rooted.
It is much easier (atleast for me) to accept the full download and flash it through TWRP and then boot back to TWRP (to preserve it and to avoid overwriting by stock recovery) before booting into system. If you only wipe Dalvik and cache, there is no need to reflash TWRP and Magisk. Ofcourse if TWRP gets overwritten somehow, then flashing it and Magisk again is not a big thing.
tnsmani said:
I can answer your questions partially.
2 & 3. Flashing TWRP and Magisk will result in OTA zip not being downloaded. Instead, the full ROM will be downloaded automatically.
4. AFAIK, you can't flash the OTA zip through TWRP.
5. If you want the OTA, you will have to be completely stock, no modifications to system files. Only then the OTA zip will download and only then you can flash it. You will ofcourse be notified of the availability of the OTA zip even if you are rooted but it will not download because it does a check of your system before downloading. Only the full zip will download if you are rooted.
It is much easier (atleast for me) to accept the full download and flash it through TWRP and then boot back to TWRP (to preserve it and to avoid overwriting by stock recovery) before booting into system. If you only wipe Dalvik and cache, there is no need to reflash TWRP and Magisk. Ofcourse if TWRP gets overwritten somehow, then flashing it and Magisk again is not a big thing.
Click to expand...
Click to collapse
Thanx a bunch. Now I am ready to flash, but not sure which recovery should I use? and what about that force encryption disabler.zip thing? which recovery wont need that thing? its just too complex to flash various things everytime I update miui rom
Sohan_Saymum said:
Thanx a bunch. Now I am ready to flash, but not sure which recovery should I use? and what about that force encryption disabler.zip thing? which recovery wont need that thing? its just too complex to flash various things everytime I update miui rom
Click to expand...
Click to collapse
OrangeFox Recovery has a feature to disable force encryption without flashing the DFE.zip everytime you flash a custom rom.
And it supports MIUI OTA Updates.
Darklouis said:
OrangeFox Recovery has a feature to disable force encryption without flashing the DFE.zip everytime you flash a custom rom.
And it supports MIUI OTA Updates.
Click to expand...
Click to collapse
can i said like this.
unlock bl and install magisk will not lose any feature of MIUI.
how about custom rom? what feature i need to abandon from stock rom?
locolyric said:
can i said like this.
unlock bl and install magisk will not lose any feature of MIUI.
how about custom rom? what feature i need to abandon from stock rom?
Click to expand...
Click to collapse
unlock bl and install magisk will not lose any feature of MIUI.
Click to expand...
Click to collapse
You will not lose any feature
how about custom rom? what feature i need to abandon from stock rom?
Click to expand...
Click to collapse
Some custom roms are AOSP based so all MIUI bloatware or features are not available in AOSP based custom roms.
Darklouis said:
You will not lose any feature
Some custom roms are AOSP based so all MIUI bloatware or features are not available in AOSP based custom roms.
Click to expand...
Click to collapse
from my last experience unlock bootloader will wipe all f my data. is that same on poco f1?
locolyric said:
from my last experience unlock bootloader will wipe all f my data. is that same on poco f1?
Click to expand...
Click to collapse
Ohh yeah.. Unlocking Bootloader will wipe all data (internal partition and data partition) except on the sdcard partition