Related
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.
I flashed twrp on boot using fastboot instead of on recovery and was stuck in a bootloop. So I found a stock boot img online and flashed that back onto boot and now it boots but wifi won't turn on anymore.
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
Found it, will try it now thank you.
oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
I have no idea how to go about using a python script to unpack the OTA images from the file. What should I do?
Don't download the OTA image. Download the fastboot image. Use 7-zip to extract.
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
racer1077 said:
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
Click to expand...
Click to collapse
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
oreo27 said:
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
Click to expand...
Click to collapse
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
racer1077 said:
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
Click to expand...
Click to collapse
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
oreo27 said:
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
Click to expand...
Click to collapse
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
racer1077 said:
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
Click to expand...
Click to collapse
Mi Flash doesn't seem to accept spaces in the path of the firmware so that was probably the issue. No worries! You'll want to update to the latest version using the system updater to get back on your actual version.
I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?
You already took the November OTA or are you still on October?
ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November
Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.
I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks
Yes.... fastboot flash boot boot.img
ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?
TWRP doesn't work with Q. Just use stock recovery to sideload.
ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.
The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk
Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.
MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.
Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?
Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches
What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.
It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.
h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
LinhBT said:
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Click to expand...
Click to collapse
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
karib97 said:
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
Click to expand...
Click to collapse
Yes, if your bootloader is unlocked.
LinkinLover2013 said:
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
Click to expand...
Click to collapse
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
LinhBT said:
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
Click to expand...
Click to collapse
Ye I have IN2015.
LinhBT said:
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
Click to expand...
Click to collapse
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
LinkinLover2013 said:
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
Click to expand...
Click to collapse
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
Click to expand...
Click to collapse
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
LinhBT said:
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
Click to expand...
Click to collapse
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that? Also do you have an app that works for updating with oxygen updater pls? I downloaded a zip but can´t find an working updater app that install zips...
LinkinLover2013 said:
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that?
Click to expand...
Click to collapse
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
LinhBT said:
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
Click to expand...
Click to collapse
Well. Where can I find Vbmeta.img for F15 pls?
LinkinLover2013 said:
Well. Where can I find Vbmeta.img for F15 pls?
Click to expand...
Click to collapse
I used these files!
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
LinkinLover2013 said:
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
Click to expand...
Click to collapse
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
LinhBT said:
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
Click to expand...
Click to collapse
So you do it in this order: Go to magisk and select flash to inactive slot -> do OTA update through OPlocalupdate app -> restart phone? Does it have any effect to select flashing magisk to inactive slot before I start OTA udpate? Because it seems like the incremental OTA udpates can install only on unrooted phone with Stock boot.img if I leave it rooted it always stops due to error.