Hello,
I tried to install the Oreo 8.1 OTA update, OPS28.65-36 on my dad's moto, which is currently running NPSS26.116-26-18.
The boot loader is unlocked but all partitions are unmodified, when I run TWRP I always do that using "fastboot boot twrp.img"
Unfortunately the update fails with an error but does not tell me which error it is.
I tried to side load the appropriate OTA update using fastboot, I got the zip from https://forum.xda-developers.com/showpost.php?p=77963554&postcount=224 which seemed to be the right release channel reteu
This failed with an error indicating that the system partition's checksum was not was was expected.
Strangely after that TWRP 3.1.1 stopped working i.e. it stuck at boot on the boot logo, luckily a newer edition TWRP-3.2.1-r20 (64bit Supported!) worked.
I guess the half done side load updated the boot loader and or the base band firmware before it failed with the system partition
I have a TWRP backup of boot and system from then the phone was new and one from today morning, it seams that when the phone was ne it had NPSS26.116-26-16 so it has installed some OTAs in the mean time. Also the checksum's of boot and system changed between the two backups.
How How can I get the new firmware onto the phone? Is there some were a TWRP instalable Oreo 8.1 image? Or a fastboot flashable full image?
Has someone else experienced similar issues?
First of all this should be in Q&A form not development. Secondly a fastboot flashable file has been available for quite some time. Anytime you've use TWRP even just booting into TWRP leaving stock recovery it modifies the system so that's why the OTA fails. Here is the thread for a fastboot flashable Oreo update.
https://forum.xda-developers.com/mo...t/moto-g5s-plus-moto-stock-firmwares-t3843626
I'm sorry for posting in the wrong section in was in a hurry and did not payed attention to detail, mea culpa.
I see in that listing you've linked only one file "SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" that is for Oreo and it does not say for which release channel it is.
Does the release channel even matter with a full image?
I would also like to inquire about your statement that just booting TWRP from RAM changes partitions, could you please provide a link to corroborate that. I find that very unexpected. IMHO normally it should not auto mount any partition writable unless selected in the mount options or required by the choose operation.
As I reported the phone seams to have installed some minor OTA's between the first and the second update. The version numbers changes and the boot and system partitions are very different.
Related
Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.
Hi, I updated my rooted OnePlus 3t with an OTA update (dumb, I know, I wasn't thinking). It failed and the device needed to be wiped. I've since tried to go through the process to reinstall twrp and supersu and I can no longer get it to boot when TWRP and superSU are installed. The weird thing is, I AM able to use it with the stock recovery and non-root, but any subsequent flashes fail, despite it appearing as if everything has been installed properly.
One last wrench to throw into this: I cannot access recovery (whether TWRP or stock) without running
Code:
fastboot boot recovery.img
. When I run that, I'm able to get into recovery, however if I go through the phone itself on the main menu after unlocking the phone, it just reboots and brings me right back to where I was.
Any ideas on what I may have done wrong and how to fix it? I've been following the guide from the oneplus forums, I've run that process about 5 or 6 times over the past day to no avail.
P.S. Have flashed the newest version of dm-verity
Firstly I need to say that I've read the forums from top to bottom before posting this, so I'm pretty sure no one here experienced this particular issue here on a P9 Plus at least.
I've tried tried to flash TWRP in order to be able to root my P9 Plus.
To do this I did the following steps:
1. Enable Developer Options in settings
2. Enable USB debugging
3. Successfully unlocked my bootloader using a code from Huawei
4. Entered fastboot mode and flashed the latest TWRP 3.1.1 recovery from their website
5. After Huawei's eRecovery kept opening I (after a suggestion in another post in the forums) flashed TWRP on recovery2 as well.
6. Phone stuck in "Your device is booting now..." screen and only booting in fastboot mode is working.
Any ideas what I've broken and how I could possibly fix it?
EDIT: At this point I'm willing to flash everything back to stock, however I'm not sure if I've got the VIE-AL10C00 or VIE-AL10BC00. I'm using the 64GB Dual SIM Chinese version of the phone with Android N and got both firmwares downloaded (updatebc183 for BC00 and 198 for C00 which are the latest for both versions) and ready.
EDIT2: I downloaded the correct latest full update 198 for my VIE-AL10C00 (as it turns out) and extracted the recovery and recovery2 images, then flashed them along with boot.img. Still having the same issue. (I need to say that in fastboot I can't flash anything other than recovery, recovery2 and boot images)
After an android update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
fastboot flash boot_a "boot.img"
fastboot flash boot_b "boot.img"
But now It's in a bootloop,
I tried flashing the unpatched boot.img from redfin-rd1a.200810.021.a1-factory-cd18efdf but that didn't help.
Is there a way to solve this without loosing all my data?
fr0sty said:
After a firmware update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
Click to expand...
Click to collapse
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Edit- you can try flashing over the previous version or reflash the current version. If those all fail, I'm not sure what to suggest and some one with a bit more knowledge maybe can suggest a fix.
Ducter said:
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Click to expand...
Click to collapse
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
fr0sty said:
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
Click to expand...
Click to collapse
If you were promoted with an update, updated, then proceeded to flash the boot image you were running prior to updating, that's not going to work. You'll need to track down a patched boot image for your current version you have flashed or reflash the update via fastboot, you can follow the guide posted and it walks you through the steps to not wipe everything.
I'm in the same position. I took the OTA update, then downloaded the 11.0.0 (RQ1A.210105.003, Jan 2021) from Google. I patched the boot.img with Magisk, put it on my laptop, and flashed it in fastboot. Now I'm getting a bootloop. I tried flashing the unpatched boot.img to try to just get back in, but I'm still bootlooping.
Did you ever find a solution? FWIW, I'm on AT&T. I noticed that sometimes there is an AT&T specific file, but that did not appear to be the case this time.
I finally fixed it. At first I didn't see that the latest factory image was on the end of the list here https://developers.google.com/android/images
I picked 11.0.0 (RQ1A.210105.003, Jan 2021), then i extraced the boot.img file from it and flashed it in fastboot with fastboot flash boot boot.img --slot all.
That resulted in a no command screen when booting. But i was able to boot in safe mode. And from there i could patch the new boot.img file with the latest magisk. After that i patched that in fastboot and now everything is working again!
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
saturday_night said:
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
Click to expand...
Click to collapse
For me my solution is easier, because i don't know all the fastboot commands to do the things you write
Well, you are not the only one with the exact same Problem (wrong boot.img or maybe broken dl) and there are several threads already. Just answering here because it was the newest.
If you or anybody else use the boot.img from your own device there will never ever be a Problem with it. I already wrote a step by step guide (with fastboot comands) for this somewhere on xda for one of my older devices. Just need to find it and i will link it here.
Hi ALL,
any chance that anyone rooted the Pixel 5 or pixel4a 5G then get the NSG working?
the device i have is rooted correctly and checked by (Root checker) however the Diag port is silent and not producing any log, need to get the NSG working...
please help !
Thanks
Hi,
My memory issues and a hard week led me to forget I needed to uninstall magisk manager adn 'restore image'. I've never had a rooted phone before, so I'd never done it before. Got lost in the 'big pile of problems' and google kept nagging to 'update'. Sigh.
Last thing I want to do is try to figure out how to migrate all my data and apps (I'm expecting Google Recorder is likely to prove a PITA to get everything 'moved'). So I'm wondering, is there a simple/easy way to get magisk root back and active without wiping apps/data on my Pixel 4a 5g since it was already rooted prior to the OTA security update?
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Didgeridoohan said:
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Click to expand...
Click to collapse
Ah. Thanks. That's simple enough and sounds like I don't have the emergency I was dreading.
Didgeridoohan said:
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Click to expand...
Click to collapse
Well, I rebooted the Pixel 4a 5g, and then it would get stuck on G logo and wouldn't load the system.
So I couldn't use latest magisk manager to create a new patched boot img. So I tried to flash the patched boot img I still had on my PC from december as the Factory image firmware is still the same right now as it was then. Now when I try to boot I get a boot loop that doesn't get to the G logo even.
Wondering what to do now... I guess it wasn't so simple after all.
Edit: I tried flashing the original boot.img. No change. Near as I can tell next option would be to try to side load an OTA update, but the Pixel 4a 5g doesn't seem to work via ADB...
What's weird is that the pixel was working before I tried to reboot it initially. Now I can't get into recovery or rescue mode either. Just have a boot loop. Can get into fastboot still.
Edit 2:
I had the wrong factory image. Got the right one, for january. Flashed boot.img via fastboot. Back to 'stuck on G logo' like before.
Edit3:
Seems stuck in fastboot mode now. When selecting 'start' fastboot just loads up again.
I tried adb sideloading OTA update. Didn't work.
I tried flashing factory image removing "-w" modifier from flash-all.bat. Stuck in boot loop on googles "G" logo with the loading status bar underneath.
Hoping there's still a way to avoid a factory reset, but wondering what next steps there are.
Is there a subforum better suited to maybe getting this question answered?
Sounds like you've gotten to a point where it's better to ask for help in your device's forum, but I've seen you're doing that already.
Hope you get things sorted...
Edit: since it's always possible that modules mess up a system update, have you tried the adb command to remove modules (if boot reaches a point where adb is recognised), or booted to safe mode to disable all modules? You've got some details here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually